Hardware inventory update #49

New issue

Closed

opened 2019-08-28 21:02:48 +02:00 by ThomasADavis · 6 comments

ThomasADavis commented

2019-08-28 21:02:48 +02:00

(Migrated from github.com)

So, memory, disk, network, CPU all nice and neat.. NVME is also partially included - I have another node that has this..

It doesn't use dmi to do this, it uses the output of lshw to collect it.

I think I need to make the asset tags unique, so I was going to make it 'hostname:part'

thomas

![Screenshot from 2019-08-28 12-00-10](https://user-images.githubusercontent.com/12158973/63884664-76116780-c98b-11e9-8d1d-a7e36ee67bee.png) So, memory, disk, network, CPU all nice and neat.. NVME is also partially included - I have another node that has this.. It doesn't use dmi to do this, it uses the output of lshw to collect it. I think I need to make the asset tags unique, so I was going to make it 'hostname:part' thomas

Solvik commented

2019-08-29 09:53:25 +02:00

(Migrated from github.com)

That's really better than the first version I've done, nice !
Personally I wouldn't use the asset tag in the case of server hardware

I've tried lshw -json when you previously mentionned it, and it's really better

Do you have a PR for this ?

That's really better than the first version I've done, nice ! Personally I wouldn't use the asset tag in the case of server hardware I've tried `lshw -json` when you previously mentionned it, and it's really better Do you have a PR for this ?

ThomasADavis commented

2019-08-29 17:21:14 +02:00

(Migrated from github.com)

This is using the asset tag more as a locator than a tag..

I will have a PR shortly, still more cleanup is needed on my side.

This is using the asset tag more as a locator than a tag.. I will have a PR shortly, still more cleanup is needed on my side.

Solvik commented

2019-08-29 17:34:07 +02:00

(Migrated from github.com)

Awesome, looking forward to it :)

Solvik commented

2019-09-03 11:42:30 +02:00