CMDB in Snow Part 6 Zhechka Toteva IT/DI-SM

Conclusions from last meeting Snow table column Snow table Source for Puppet Source for CDB From where Comment s How on demand Status Cluster Server/Clus ter/Cluster Node Puppet_nod es CDBforeman push single Work on- going ImportanceServer Puppet_nod es CDBPuppet_db Yes/no for puppet push single Work on- going Last Modified in CDB Server-CDB Not need in the future for push Push! Via ? JSON. Pull of a single host information from hwdb. Not needed LocationServerCDB?CDB LANDB- >INFOR Better from LANDB. Later from INFOR. pull database view Done NameServer Puppet_nod es CDBLANDB pull database view Done Rack Server/Rac k LANDBCDB LANDB- >INFOR Null for VM ? pull database view Done Serial Number ServerCDB hwdb incremental pull HWDBDone VendorServer-CDBhwdb incremental pull HWDBDone WarrantyServerCDB hwdb incremental pull HWDBDone Retired flagServerhwdbfull pullHWDB Done for warranties Discussion last meeting

Conclusions from last meeting Snow table column Snow table Source for Puppet Source for CDB From where Comment s How on demand Status Cluster Server/Clus ter/Cluster Node Puppet_nod es CDBforeman push single In progress ImportanceServer Puppet_nod es CDBPuppet_db Yes/no for puppet push single Done in DEV Last Modified in CDB Server-CDB Not need in the future for push Push! Via ? JSON. Pull of a single host information from hwdb. Not needed LocationServerCDB?CDB LANDB- >INFOR Better from LANDB. Later from INFOR. pull database view Done NameServer Puppet_nod es CDBLANDB pull database view Done Rack Server/Rac k LANDBCDB LANDB- >INFOR Null for VM ? pull database view Done Serial Number ServerCDB hwdb incremental pull HWDBDone VendorServer-CDBhwdb incremental pull HWDBDone WarrantyServerCDB hwdb incremental pull HWDBDone Retired flagServerhwdbfull pullHWDB Done for warranties Status today

HWDB -> Snow: Status  Automatic push via the Snow JSON interface using user certificate  Synchronise the warranty information  Synchronise the host information  Incremental synchronisation  Feed Snow production  Retire machines for retired contracts Done Full data pull on regular basis

HWDB -> Snow: Future plan  TO BE FINISHED:  Pull the retired flag per host  Run the code with a service account certificate To be finished

Puppet/Forman -> Snow: Status  Automatic push via the Snow JSON interface using user certificate  Modular code  Retrieve from Puppet/Forman  hostname and cluster  hostname and essential (flag)  Incremental synchronisation  Feed Snow DEV  Essential flag Full data pull on regular basis Done

Puppet/Forman -> Snow: Status II  Automatic push via the Snow JSON interface using user certificate  Feed Snow DEV  Cluster  Host-Cluster assignment To be finished by the end of the week Full data pull on regular basis

Puppet/Forman -> Snow: Future plan  Automatic push via the Snow JSON interface using user certificate  Feed Snow PROD (15 July)  Pull from Snow on demand (per host)  Create a proxy code running at CERN that  Provide SOAP interface for Snow via basic authentication  Pull data from Puppet using certificate  Maybe basic authentication will be possible? Need to start Pull on demand

Pending questions  Retired information:  From where?  HWDB warranty information  How?  Marked with by retired flag - wait  Still synchronised with CDB:  Importance - will stop once we start synch with Puppet  Cluster – will stop once we start synch with Puppet  IT Contact – change the “Add CI Contacts to Watch List” action; combine with main / responsible  Contract type, Model number  Department/Group ? – future: puppet master  Operating system ?

What else  Enclosure information  From INFOR

THANKS TO  Alexandre who helped with the certificate usage and who provided us with final version of the two puppet views containing the essential flag and the host_group.  Steve who tries to make the Snow people life easier with special views and basic authentication access  Daniel who did the job on the Snow side  Afroditi who gave us all hwdb world