1. Zhechka Toteva IT/DI-SM
CMDB in Snow Part 3
Zhechka Toteva
IT/DI-SM

2. Conclusions from last meeting
Snow table column
Snow table
Source for Puppet
Source for CDB
From where
Comments
How
on demand
Status
Cluster
Server/Cluster/Cluster Node
Puppet_nodes
CDB
foreman
push single
Not started
Importance
Server
Puppet_db
Yes/no for puppet
Last Modified in CDB -
Not need in the future for push
Push! Via ? JSON. Pull of a single host information from hwdb.
Location
CDB?
LANDB->INFOR
Better from LANDB. Later from INFOR.
pull database view
Done
Name
LANDB
Rack
Server/Rack
Null for VM ?
Serial Number
hwdb ?
take from HWDB
Partially
Vendor
? Script by ServiceNow
Warranty
Retired flag
Conclusions from last meeting
Discussion last meeting

3. Conclusions from last meeting
Snow table column
Snow table
Source for Puppet
Source for CDB
From where
Comments
How
on demand
Status
Cluster
Server/Cluster/Cluster Node
Puppet_nodes
CDB
foreman
push single
Not started
Importance
Server
Puppet_db
Yes/no for puppet
Last Modified in CDB -
Not need in the future for push
Push! Via ? JSON. Pull of a single host information from hwdb.
Location
CDB?
LANDB->INFOR
Better from LANDB. Later from INFOR.
pull database view
Done
Name
LANDB
Rack
Server/Rack
Null for VM ?
Serial Number
hwdb ?
take from HWDB
Partially
Vendor
? Script by ServiceNow
Warranty
Retired flag
Conclusions from last meeting
Status today

4. HWDB -> Snow: Status
Automatic push via the Snow JSON interface using basic authentication
Modular code
Verification of the Warranty and Vendor
Insertion in DEV
Update in DEV
Problem with memory dump (while processing 9K hosts)
Automatic pull via the HWDB JSON interface using authentication – maybe will be done, not clear yet
Has be tested with a host certificate
Progressed
Full data pull on regular basis

5. HWDB -> Snow: Future plan
TO BE FINISHED: the push via JSON to Snow and consuming the HWDB via certificate (?)
Pull the warranty information
Pull the retired flag
NEW NEEDED: Pull the last updated date
Incremental synchronisation (via file diff)
Try to consume directly the Snow JSON from HWDB (?)
Try to create a SOAP based Proxy for Snow to pull HWDB data on demand (e.g. when an alarm for non-existing machine is raised)
Need work on
Have to progress
Have to progress
Data push on demand
Data pull on demand

6. Puppet/Forman -> Snow: Future plan
Try to consume directly the Snow JSON from Puppet (?)
Data push on demand
Need to start

7. What else Enclosure information
From INFOR
Puppet/Forman -> Snow (full data pull is needed)
Need to start

8. Discussion last meeting – full table
Snow table column
Snow table
Source for Puppet
Source for CDB
From where
Comments
How
on demand
Cluster
Server/Cluster/Cluster Node
Puppet_nodes
CDB
foreman
push single
Contract Type
Server
Can it disappear? Rename?
Department
CDB/SDB
Importance
Puppet_db
Yes/no for puppet
IT Contact
Last Modified in CDB -
Not need in the future for push
Push! Via ? JSON. Pull of a single host information from hwdb.
Location
CDB?
LANDB->INFOR
Better from LANDB. Later from INFOR.
pull database view
Hardware Model
Name
LANDB
Operating System
Not needed.
Rack
Server/Rack
Null for VM ?
Serial Number
hwdb ?
take from HWDB
Vendor
? Script by ServiceNow
Warranty