Changes between Version 8 and Version 9 of Software/eAM/aInventory/InventoryGathering

Timestamp:

Jun 16, 2013, 6:18:53 PM (11 years ago)

Author:

seskar

Comment:

—

Software/eAM/aInventory/InventoryGathering

@@ -1 @@
-= Inventory Gathering =
+=== Inventory Gathering ===
 
  * [#data Data Structure]
@@ -5 +5 @@
  * Expirment details
 
-== Data Structure == #data
+===== Inventory Attribute Structure ===== #data
 Our layout will try to capture the relationship between nodes (which for our current purposes means motherboards) and devices (any network/communication device). The relationship hierarchy looks like this:
 {{{
@@ -28 +28 @@
 ||USB connected device || Device || FQDNofNode_DEV_unique# || mac (if it exists), device id, device string, bus type, device tag ||
 
-== Inventory Gathering == #gather
+==== Inventory Gathering ==== #gather
 
-Inventory collection is now done via a diskless netboot. 
-
-There are two scripts that are copied to /root directory of the node, gatherer.rb and inventory.sh. Inventory.sh is merely a launchers that specifies where to redirect logs, and where the lspci/lsusb binaries are (set via flags when invoking gatherer.rb). Inventory.sh is added to the node startup routine at priority s99. When the node boots it should immediately begin the inventory process.  
+Inventory collection is now done via a diskless netboot. The PXE links are set for the whole domain and a script that works with CMC service to boot the nodes (usually in multiple waves); the netboot image automatically starts the gathering procedure. The two scripts,gatherer.rb and inventory.sh are the core of the process and stored in the /root directory of the image. Inventory.sh is merely a launchers that specifies where to redirect logs, and where the lspci/lsusb binaries are (set via flags when invoking gatherer.rb). Inventory.sh is added to the node startup routine at priority s99. When the node boots it should immediately begin the inventory process.