Hi,
do you know any good server inventory open source products?
I want information like, server hostnames, ram, cpu, os, filesystems, volume groups, disks, adapters, installed software versions, firmware levels and so on
os: aix, solaris, linux, hpux
data should be kept in a database, web front end and history functions would be good
I can load the data directly into the db, something agent based is ok too
thanks in advance
cheers funksen
Best one is the one I wrote for IBM. But they'll never let you have it.
ZenOSS is a popular choice. If you use ServiceNow, they are touting their new discovery product. Dell's KACE might be interesting... there's a ton of products to look at and evaluate.
thank you, these are all very powerful products, unfortunately not open source and very feature heavy, was looking for something really lightweight without the whole itil implementation, impact, problem management and so on
I really really really need to rewrite the one I made and push it out (I'm an open source developer, IBM doesn't do open source, so glad I'm out of there).
How about Nagios. It might not be as lightweight as you like but it is open source. As far as i know (lucky me, i'm in a pure AIX shop) it supports all the platforms you want and you do not need to use the monitoring partif you only need an inventory service.
I hope this helps.
bakunin
Nagios is primarily a monitoring tool. Of course you can (mis-)use it for an inventory.
Maybe facter from Puppet Labs is more appropriate...
Hi.
Possibilities:
1) lf337, SystemAdministration: shivalik -- simple configuration backup (defying Murphy's laws)
2) https://www.novell.com/communities/coolsolutions/cool_tools/sysinfo/
Good luck ... cheers, drl
Just for fun (my old inventory tool... belongs to IBM). Sample run done against one host, in this case, an oVirt VM.
Host_Class:OVirt-Node
Host_FullHostname:linux-host
Host_Hostname:linux-host
Host_HWSubType:Server
Host_HWType:Virtual
Host_OEM:oVirt
Host_Owner:Unknown
Host_Product:oVirt-Node
Host_Serial:Virtual
Host_Type:Normal
Host_Virtual:Yes
Host_Manufacturer:oVirt
Host_Product:oVirt Node
Host_Version:6-5.el6.centos.11.2
Host_Serial:6b2f210c-2a90-42ce-8b8c-04495deccfce
Host_UUID:D808ADDA-3889-4CA3-B7BF-C9E3FDF3E253
Host_Wake-up_Type:Power Switch
Host_SKU_Number:Not Specified
Host_Family:Red Hat Enterprise Linux
Os_HwArch:64-bit
Os_Class:Linux
Os_OsArch:64-bit
Os_SubClass:CentOS
Os_Update:CentOS Linux release 7.2.1511
Os_Version:CentOS Linux release 7.2.1511
Os_Type:UNIX
Mem_EmptySlots:0
Mem_Class:Memory-4G-8G
Mem_SizeG:3.7
Mem_Size:3878696K
Mem_Slot_Size_1:4096 MB
Mem_Slot_Location_1:DIMM 0
Mem_Slot_Speed_1:
Mem_Slot_Type_1:RAM
Mem_Slot_COUNT:1
Mem_Slot_ELEMENTS:Size,Location,Speed,Type
Cpu_Cache:4096 KB
Cpu_Capable64:Yes
Cpu_Proc_Num_1:0
Cpu_Proc_Vendor_1:GenuineIntel
Cpu_Proc_Type_1:Intel Core i7 9xx (Nehalem Class Core i7)
Cpu_Proc_Speed_1:2266.740
Cpu_Proc_Cache_1:4096 KB
Cpu_Proc_Id_1:6
Cpu_Proc_Coremap_1:P 0,C 0
Cpu_Proc_Num_2:1
Cpu_Proc_Vendor_2:GenuineIntel
Cpu_Proc_Type_2:Intel Core i7 9xx (Nehalem Class Core i7)
Cpu_Proc_Speed_2:2266.740
Cpu_Proc_Cache_2:4096 KB
Cpu_Proc_Id_2:6
Cpu_Proc_Coremap_2:P 0,C 1
Cpu_Proc_COUNT:2
Cpu_Proc_ELEMENTS:Num,Vendor,Type,Speed,Cache,Id,Coremap
Cpu_SubClass:Core-Duo
Cpu_Class:Intel
Cpu_CapableVirt:No/Unknown
Cpu_EmptySockets:31
Cpu_Freq:2266.740
Cpu_LNumber:2
Cpu_Name:Intel Core i7 9xx (Nehalem Class Core i7)
Cpu_PCores:2
Cpu_FreqG:2.27
Cpu_Vendor:GenuineIntel
Cpu_PNumber:1
Cpu_Siblings:2
Cpu_Sockets:32
Net_PrimDev:eth0
Net_DHCP:no
Net_Gatewayv4:10.20.0.1
Net_IPv4:10.20.1.17
Net_IPv4DNSName:linux-host.example.com
Net_DNS:10.20.1.45 10.20.1.16
Net_Devices:eth0 lo
Net_DNSSearch:example.com
Fs_Df_Device_1:/dev/mapper/centos-root
Fs_Df_Size_1:6645760
Fs_Df_Used_1:5735544
Fs_Df_Available_1:910216
Fs_Df_Capacity_1:87%
Fs_Df_Mountpoint_1:/
Fs_Df_Type_1:xfs
Fs_Df_Options_1:rw, relatime, attr2, inode64, noquota
Fs_Df_Dumpfreq_1:0
Fs_Df_Fsckpass_1:0
Fs_Df_Device_2:/dev/mapper/centos-tmp
Fs_Df_Size_2:1038336
Fs_Df_Used_2:33004
Fs_Df_Available_2:1005332
Fs_Df_Capacity_2:4%
Fs_Df_Mountpoint_2:/tmp
Fs_Df_Type_2:xfs
Fs_Df_Options_2:rw, relatime, attr2, inode64, noquota
Fs_Df_Dumpfreq_2:0
Fs_Df_Fsckpass_2:0
Fs_Df_Device_3:/dev/mapper/centos-var_log
Fs_Df_Size_3:1038336
Fs_Df_Used_3:109540
Fs_Df_Available_3:928796
Fs_Df_Capacity_3:11%
Fs_Df_Mountpoint_3:/var/log
Fs_Df_Type_3:xfs
Fs_Df_Options_3:rw, relatime, attr2, inode64, noquota
Fs_Df_Dumpfreq_3:0
Fs_Df_Fsckpass_3:0
Fs_Df_Device_4:/dev/mapper/postgres_vg-postgres_lv
Fs_Df_Size_4:103076792
Fs_Df_Used_4:61496
Fs_Df_Available_4:97756240
Fs_Df_Capacity_4:1%
Fs_Df_Mountpoint_4:/postgres
Fs_Df_Type_4:ext4
Fs_Df_Options_4:rw, relatime, data=ordered
Fs_Df_Dumpfreq_4:0
Fs_Df_Fsckpass_4:0
Fs_Df_Device_5:/dev/vda1
Fs_Df_Size_5:508588
Fs_Df_Used_5:211292
Fs_Df_Available_5:297296
Fs_Df_Capacity_5:42%
Fs_Df_Mountpoint_5:/boot
Fs_Df_Type_5:xfs
Fs_Df_Options_5:rw, relatime, attr2, inode64, noquota
Fs_Df_Dumpfreq_5:0
Fs_Df_Fsckpass_5:0
Fs_Df_COUNT:5
Fs_Df_ELEMENTS:Device,Size,Used,Available,Capacity,Mountpoint,Type,Options,Dumpfreq,Fsckpass
Disk_Dev_Device_1:sr0
Disk_Dev_Type_1:-
Disk_Dev_RAID_1:
Disk_Dev_Vendor_1:QEMU
Disk_Dev_Model_1:QEMU-DVD-ROM
Disk_Dev_Revision_1:0.12
Disk_Dev_Serial_1:-
Disk_Dev_Size_1:1.00GB
Disk_Dev_Device_2:vda
Disk_Dev_Type_2:-
Disk_Dev_RAID_2:
Disk_Dev_Vendor_2:0x1af4
Disk_Dev_Model_2:-
Disk_Dev_Revision_2:-
Disk_Dev_Serial_2:-
Disk_Dev_Size_2:10.00GB
Disk_Dev_Device_3:vdb
Disk_Dev_Type_3:-
Disk_Dev_RAID_3:
Disk_Dev_Vendor_3:0x1af4
Disk_Dev_Model_3:-
Disk_Dev_Revision_3:-
Disk_Dev_Serial_3:-
Disk_Dev_Size_3:100.00GB
Disk_Dev_COUNT:3
Disk_Dev_ELEMENTS:Device,Class,Vendor,Model,Revision,Serial,Size
Disk_Features:Linux-LVM
This is bit incomplete (and just the raw data, full product has friendly web presentation) and needs some freshening up... it was an awesome bit of IP (handles Linux (x86, x86_64, mainframe), Windows, AIX, HPUX, Solaris, SCO, Digital Unix, VMS, SANs, Xen/ESXi/KVM, some network equipment and IBM and HP blade enclosures) you'll never get to see (IBM refused to open source it).
The hypervisor handling is nice in that it showed you the VMs defined on a node and each VM knew what node it was hosted on (something you normally cannot get). It also supported dynamic data overriding and augmentation for cases where the tool wasn't enough. Memories.
I no longer have access to a plethora of equipment, so if rewritten and open sourced, it won't handle as much initially, but will be "better" in many ways. I may output JSON for example instead of the weird tuples and pseudo arrays.
Sorry about boasting about the past....