120 likes | 262 Views
CMDB in Snow Part 7. Zhechka Toteva IT/DI-SM. Conclusions from last meeting. Discussion last meeting. Conclusions from last meeting. Status today. HWDB -> Snow: Status. Done. Automatic push via the Snow JSON interface using user certificate Synchronise the warranty information
E N D
CMDB in SnowPart 7 Zhechka Toteva IT/DI-SM
Conclusions from last meeting Discussion last meeting
Conclusions from last meeting Status today
HWDB -> Snow: Status Done • 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 Full data pull on regular basis
HWDB -> Snow: Future plan • TO BE FINISHED: • Pull the retired flag per host • Decided that it is not possible. Check in LANDB instead? When should the check be run? • From the HWDB or from INFOREAM • Run the code with a service account certificate • Work in progress To be finished
Puppet/Forman -> Snow: Status Done • Automatic push via the Snow JSON interface using user certificate • Synchronise the cluster information • Synchronise the essential flag • Incremental synchronisation • Feed Snow production Full data pull on regular basis
Puppet/Forman -> Snow: Status II Done • Snow pulls from Puppet 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 • Enhance Snow to calls the SOAP interface, whenever an alarm for unknown machine arrives • Synchronise on demand with LANDB and HWDB for the future? (for the future) To be tested Pull on demand
Others… Done • IT Contact – change the “Add CI Contacts to Watch List” action in order to merge the CDB IT Contact with the LANDB main/responsible user/e-group • Operating system is retrieved from LANDB for all network devices (going in production on Monday)
Pending questions • Retired information: • From where? • HWDB warranty information • How? • Marked with by retired flag - wait • Still synchronised with CDB: • Contract type, Model number – to be stopped • Department/Group ? – future: puppet master – not needed, retrieved from the FE
What else • Puppet will provide Default FE per host or host_group • Will be sent to Snow in the alarm (for special alarms). • Will be exported to Snow. In case of a new alarm coming without an FE, the incident will be assigned to the Default FE. • Could be done in LANDB maybe? • Accounts to be defined in Snow as CIs • Enclosure information • From INFOR
THANKS TO • Gavin, Miguel and Michal for the new fresh ideas and collaboration. • 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