Quattor tutorial Introduction German Cancio, Rafael Garcia, Cal Loomis

n° 2 Introduction u Agenda page Agenda page u Laptop registration issues? u Notes: n You will work in pairs during the practical exercises (limited dvp nodes) n Use only one laptop per pair please s limited power bars! s Potentially limited wireless network!!! n Laptops will be required only for terminal (SSH) connections s No need to install any quattor software unless you really want to :-) u There are less practical exercises than theory slides ;-( u Your feedback will be most welcome for improvements! u Who did the homework?

n° 3 Quattor in CERN context: ELFms ELFms stands for ‘Extremely Large Fabric management system’ Subsystems: u : configuration, installation and management of nodes u : system / service monitoring u : hardware / state management u ELFms manages and controls most of the nodes in the CERN CC n ~2300 nodes out of ~ 3000 n Multiple functionality and cluster size (batch nodes, disk servers, tape servers, DB, web, …) n Heterogeneous hardware (CPU, memory, HD size,..) n Supported OS: Linux (RH7, RHES2.1, RHES3 / Scientific Linux 3 – IA32&IA64) and Solaris (9) Node Configuration Management Node Management

n° 4 Improvements wrt EDG-LCFG u New and powerful configuration language n True hierarchical structures n Extendable data manipulation language n (user defined) typing and validation u SQL query backend u Portability n Plug-in architecture -> Linux and Solaris u Enhanced components n Sharing of configuration data between components now possible n New component support libraries n Native configuration access API (NVA-API) u Stick to the standards where possible n Installation subsystem uses system installer n Components don’t replace SysV init.d subsystem u Modularity n Clearly defined interfaces and protocols n Mostly independent modules n “light” functionality built in (eg. package management) u Improved scalability n Enabled for proxy technology n NFS mounts not necessary any longer u Enhanced management of software packages n ACL’s for SWRep n Multiple versions installable n No need for RPM ‘header’ files u Last but not least…: Support! n EDG-LCFG is frozen and obsoleted (no ports to newer Linux versions) n LCFG -> EDG-LCFGng -> quattor

n° 5 Differences with ASIS/SUE SUE: u Focus on configuration, not installation u Powerful configuration language n True hierarchical structures n Extendable data manipulation language n (user defined) typing and validation n Sharing of configuration data between components now possible u Central Configuration Database u Supports unconfiguring services u Improved depenency model n Pre/post dependencies u Revamped component support libraries ASIS: u Scalability n HTTP vs. shared file system u Supports native packaging system (RPM, PKG) u Manages all software on the node u ‘real’ Central Configuration database u (But: no end-user GUI, no package generation tool)

n° 6 Differences with ROCKS u Rocks: better documentation, nice GUI, easy to setup u Design principle: reinstall nodes in case of configuration changes n No configuration or software updates on running systems n Suited for running long production jobs? Efficiency on batch nodes, upgrades / reconfigs on 24/24,7/7 servers (eg. gzip security fix, reconfig of CE address on WN’s) u Assumptions on network structure (private,public parts) and node naming u No indication on how to extend the predefined node types or extend the configured services u Limited configuration capacities (key/value) u No multiple package versions (neither on repository, nor simultaneously on a single node) n Eg. different kernel versions on specific node types u Works only for RH Linux (Anaconda installer extensions)

n° 7 Welcome Back! u Please sit at the same place as yesterday! u We will continue working in pairs, connecting to the same nodes as yesterday. u If you don’t remember your node name, check the handouts. u If you don’t have the handouts anylonger… come and talk to us.

n° 8