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

CERN IT Department CH-1211 Genève 23 Switzerland 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 2

CERN IT Department CH-1211 Genève 23 Switzerland 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 3

CERN IT Department CH-1211 Genève 23 Switzerland M.Schröder, Hepix Vancouver 2011 OCS Inventory OSS Multi-platform – Various Linux, Windows, MacOS Some users with large number of nodes – Biggest: > 100k 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” 4

CERN IT Department CH-1211 Genève 23 Switzerland 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 5

CERN IT Department CH-1211 Genève 23 Switzerland 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 6

CERN IT Department CH-1211 Genève 23 Switzerland 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 – V2 of server can handle v1 & v2 clients 7

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

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

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

CERN IT Department CH-1211 Genève 23 Switzerland 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 11

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

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

CERN IT Department CH-1211 Genève 23 Switzerland 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 14