James is working on a second generation inventory script.

Currently on: Gatherer

It's plan is to be simpler and less ambitious than it's predecessor, but still respect the sql table structure ("as much as possible.")

As I see it there should be 3 parts to this script:

1. executer: runs either wget or apt-get install and copies the latest version of the other parts of the scripts then executes them
2. gatherer: collects information using only operating system based facilities (dmesg, lsusb, lspci, ifconfig, /sys).
3. Writer: checks the mysql repository for changes from the current state. If different changes them.

The sql structure is a bit of a bit mess, the major tables of interest are:

1. motherboards - List of things that can be connected to, has its own id used to tie other tables to it
2. devices - List of deviced "connected" to mother boards
3. device_kinds - type identifier for connected devices (an attribute of a device).
4. locations - Converts x,y coordinates to a single integer that maps directly to a mother board.
5. inventories - records the start and stop time of the inventory pass.

A lot of the tables are full of unused colums. I guess we'll just ignore them for now. The basic crux of an update should be the following:

1. examine our IP to determine our current location
2. We gather information about the mother board:
   1. Disk Size (dmesg)
   2. Memory Size (dmesg)
3. Gather information about attached devices:
   1. 2 wired Ethernet addresses (ifconfig, /sys)
   2. 2 wireless Ethernet addresses (ifconfig, /sys)
   3. any usb devices (lsusb, /sys)
4. get the mother board id from the location table
5. update mother board information if diffrent, and stamp with current inventory number
6. update devices if diffrent and stamp with inventory number
7. profit.

---

Gatherer: The disk size and memory size are a quick scan from dmesg. The disk size matches, but the memory size is a little off. It probably has to do with the way dmesg reports memory vs /sys reports memeory. It would be nice to find the /sys entry for consistency.

In /sys/devices/pci0000:00 are the sub directories correlated with the specific Ethernet hardware. In each directory that correlated to an Ethernet device there will be a symbolic link with the operating system name of the device. This will allow us to match up the pci address(name of the subdirectory of /sys/devices/pci0000:00) to the mac address (from ifconfig). lspci can tell us the associated pci address and a hardware identifier string.

lsusb on the otherhand offers a direct correlation to the device kind table, the ordered pair of numbers xxxx:yyyy directly correlated to the tables vendor and device ids. And the Bus xxx Device yyy number fits into the addres category of the device table.

9/29/09

I may have discovered the cause of the device / vendor discrepancy. Joe seems to be looking at /sys/class/net/devincename/device… perhaps this points to a different device id. I'll have to check it out.

That being said I have a working protoype:

ssugrim@external2:~/scripts$ ruby gatherer.rb
ssugrim@external2:~/scripts$ more /tmp/external2.xml
<external2>
 <ip_adds>
  <10.50.0.12 iface='eth1' host='external2.orbit-lab.org'/>
  <127.0.0.1 iface='' host=''/>
 </ip_adds>
 <motherboard mem_size='1048512' disk_size='156301488' cpu_num='4'/>
 <Devices>
  <pci>
   <eth0 device='1229' bus_add='01:03.0' mac='00:e0:81:26:70:16' str='Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet Controller (Copper) (rev 01)' vendor='8086'/>
   <eth1 device='1010' bus_add='04:01.0' mac='00:e0:81:26:76:9c' str='Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet Controller (Copper) (rev 01)' vendor='8086'/>
   <eth2 device='1010' bus_add='04:01.1' mac='00:e0:81:26:76:9d' str='Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet Controller (Copper) (rev 01)' vendor='8086'/>
  </pci>
  <usb>
   <0 device='0001' bus_add='001:001' str='Linux Foundation 1.1 root hub' vendor='1d6b'/>
  </usb>
 </Devices>
</external2>
ssugrim@external2:~/scripts$

---

10/2/09

Minus error chechking for failed commands, the gatherer is complete. I'm now moving onto writer. I'm going to keep them in the same script for now, so I don't have to deal with reimporting the data and extracting it from xml, at some point that'll be a todo, so that way we can call just the gatherer if we want to.

Fow now, I need to determine what node I am based on the resolved host name. The scheme is nodex-y.testbedname# I can extract the x and y cooridnates from the node part, and then The testbed name will have to be a lookup. (this should probably be in gatherer as parameters.

Once I have that I can look up my unique mysql id from the mysql databse. This id will then allow me to correlate devices with the ones I have.