OCS Inventory at CERN Matthias Schrder ITOIS CERN

OCS Inventory at CERN Matthias Schröder (IT-OIS) CERN IT Department CH-1211 Genève 23 Switzerland www. cern. ch/it M. Schröder, Hepix Vancouver 2011

Motivation: Know thy clients • • • How many nodes do we support Which hardware type are they Which version of OS are they using How many still use model X Who will suffer if we drop driver Y Configuration of node with issue Z CERN IT Department CH-1211 Genève 23 Switzerland www. cern. ch/it 2 M. Schröder, Hepix Vancouver 2011

In the past • New machines need to register – But who de-registers a box that gets retired? • Network DB gives upper limit on nodes – Essentially no HW info • Count # boxes sold – Lifetime varies – People buy outside – Don’t know which OS they use • Count nodes doing yum updates – Little details, just good as a global count CERN IT Department CH-1211 Genève 23 Switzerland www. cern. ch/it 3 M. Schröder, Hepix Vancouver 2011

OCS Inventory • OSS • Multi-platform – Various Linux, Windows, Mac. OS • Some users with large number of nodes – Biggest: > 100 k nodes • Relies on standard tools – Perl, php, mysql • • • Produces very detailed reports Little load on clients Easy to extent Reasonable data presentation Some documentation – But somewhat “distributed” CERN IT Department CH-1211 Genève 23 Switzerland www. cern. ch/it 4 M. Schröder, Hepix Vancouver 2011

Our client configuration – added CERN specific collector for • • Boot time Architecture Location (not yet in production) OS UUID (tracking for multi-boot systems) – Dropped unwanted collectors • Users • Processes • IPDiscover – Ignored • Download feature • Central configuration feature CERN IT Department CH-1211 Genève 23 Switzerland www. cern. ch/it 5 M. Schröder, Hepix Vancouver 2011

Getting it on the nodes • Desktops: – Added as a dependency of config tool • Next yum-autoupdate installed it – Configuration done by tool • Ncm-ocsagent • Only for nodes that are inside CERN GPN • Computer Center nodes: – Added sw and settings to basic quattor templates CERN IT Department CH-1211 Genève 23 Switzerland www. cern. ch/it 6 M. Schröder, Hepix Vancouver 2011

Our Server configuration – Add display of CERN specific info – Added links into network DB – OCS DB and webserver on same node • Virtualised • Little load in normal operation • Schema evolution very slow – Due to virtualisation? – Better drop everything and start from scratch – V 2 of server can handle v 1 & v 2 clients CERN IT Department CH-1211 Genève 23 Switzerland www. cern. ch/it 7 M. Schröder, Hepix Vancouver 2011

OCS host listing CERN IT Department CH-1211 Genève 23 Switzerland www. cern. ch/it 8 M. Schröder, Hepix Vancouver 2011

OCS Summary Example CERN IT Department CH-1211 Genève 23 Switzerland www. cern. ch/it 9 M. Schröder, Hepix Vancouver 2011

OCS Node Info Example CERN IT Department CH-1211 Genève 23 Switzerland www. cern. ch/it 10 M. Schröder, Hepix Vancouver 2011

And the history? • OCS Server keeps snapshot only • We feed that do our desktopdb – Keeps track of full history – Is fed by OCS (Linux) and CMF (Windows) – Can handle multi-boot • When was which OS used on node CERN IT Department CH-1211 Genève 23 Switzerland www. cern. ch/it 11 M. Schröder, Hepix Vancouver 2011

Desktopdb: History of SLC CERN IT Department CH-1211 Genève 23 Switzerland www. cern. ch/it 12 M. Schröder, Hepix Vancouver 2011

Status • Deployment started spring 2011 – Now ~10 k clients • Currently preparing Mac client – Many problems with Mac. OS > 10. 5 – Deployment will require user cooperation – Might get ~2 k additional clients • Next: – Develop queries for data mining – Extend CERN specific info – Automate “garbage collection” CERN IT Department CH-1211 Genève 23 Switzerland www. cern. ch/it 13 M. Schröder, Hepix Vancouver 2011

Conclusion • • • OCS easy to extent Easy deployment on SLC Little load on client and server Documentation could be more central We know our SLC nodes due to OCS CERN IT Department CH-1211 Genève 23 Switzerland www. cern. ch/it 14 M. Schröder, Hepix Vancouver 2011