Data Centre Infrastructure – SNOW Forum Meeting
CERN, 04/07/2013 (28-S-029)
6th Session - Minutes
Present: Olof Barring, Daniel Garcia Martinez, Alexandre Lossent, Patricia Mendez Lorenzo,
Giacomo Tenaglia, Fabio Trevisani, Zhechka Toteva
Minutes: Patricia Mendez Lorenzo
Indico Page: http://indico.cern.ch/conferenceDisplay.py?confId=261138
Topic of the meeting  CMDB: Current Status
Initial comments: Two different views provided by Alex for both the server cluster and the
essential (old importance) flag. This new implementation has been deployed in the development
instance of ServiceNow and will be deployed in production on the 15 th of July. Latest
synchronizations implemented by Daniel.
Today’s current summary of the variables recorded in ServiceNow:

HWDBSNOW: Nothing new
The HWDBSNOW data registration is basically completed. Fabio reported some tickets with no
vendor information. These particular tickets need to be checked on an individual basis and to be
reported to Afroditi for further checking.
Concerning the code execution based on a service account certificate the same approach that will
be used for Puppet information will be used for the HWDB. Therefore no news implementations
Puppet  SNOW: see slide, many advances there.



Feed of SNOW CMDB with the cluster and essential flag information to be put in
production by the 15th of July (currently available in the development instance of SNOW)
o Information update frequency: We will start with an hourly synchronization
that will be also available on the 15th of July. However the final goal is to provide
an on demand synchronization at alarm ticket creation time. This approach will
be implemented after the 15th of July.
No news concerning basic authentication for JSON
Pending questions  Information about the following variables:
 IT contact  combined information as we agreed the last time. The combination will
be done in in SNOW when clicking “Add contact persons” action
 Contract type/model number  Information is maintained in the system we
maintain it. Concerning the model number it is not existing in puppet and it should
be replaced by the warranty ID
 Department  The first idea discussed during the meeting was that Puppet was
intended to provide the puppet master information associated to each machine. This
would be an indicator of the department (for the moment pure puppet machines
have this department info empty).
o Modification after the meeting: Puppet master information idea discarded.
The department/group could be resolved from the LanDB owner, however
the link between the LanDB owner and the department still remains
pending. To be discussed at the next meeting.
Next meetings:


Middle of August (it will be announced in advance)
Beginning of September