1. German Cancio – WP4 developments Partner Logo System Management: Node Configuration & Software Package Management German.Cancio@cern.ch

2. German Cancio – WP4 developments - n° 2 System management Architecture u The pillars: n Central Configuration Database n Node Configuration Management n Base system installation n Software Package Management n Monitoring

3. German Cancio – WP4 developments - n° 3 Node Configuration Management

4. German Cancio – WP4 developments - n° 4 ClientServer XML HLDL PAN DBM Notification + Transfer Low Level API High Level API Component Access API GUI Node Configuration Management

5. German Cancio – WP4 developments - n° 5 Node Configuration Management (NCM) u Client software running on the node which takes care of “implementing” what is in the configuration profile u Sits on top of the low-level Config access library (NVA-API) u Modules: n “Components” n Component support libraries n Framework

6. German Cancio – WP4 developments - n° 6 NCM: Components u “Components” (like SUE “features” or LCFG ‘objects’) are responsible for updating local config files, and notifying services if needed u Components register their interest in configuration entries or subtrees, and get invoked in case of changes u Components do only configure the system n Usually, this implies regenerating and/or updating local config files (eg. /etc/sshd_config) One method only: Configure() u Use standard system facilities (SysV scripts) for managing services n Reuse the standard facilities: most services come with a SysV script. n Components can notify services using SysV scripts when their configuration changes. n Components are kept small&simple

7. German Cancio – WP4 developments - n° 7 Component example sub Configure { my ($self) = @_; # access configuration information my $config=NVA::Config->new(); my $arch=$config->getValue('/system/architecture’); # low-level API $self->Fail (“not supported") unless ($arch eq ‘i386’); # (re)generate and/or update local config file(s) open (myconfig,’/etc/myconfig’); … # notify affected (SysV) services if required if ($changed) { system(‘/sbin/service myservice reload’); … }

8. German Cancio – WP4 developments - n° 8 Existing component taxonomy u Components can be classified into basic, service-specific and Grid components u Basic components: Manage basic system configurations n eg. network,NFS, printers, security, time… u Service specific components: For batch nodes, servers (provided by service managers) n Eg. LSF, PBS, Castor, accounting, root mail, … u Grid components (provided by Grid middleware WP’s) n Eg. Globus, GDMP, LCAS, Resource Broker… u Existing components are available both from SUE and LCFG n SUE features: Basic and Service specific n LCFG components: Basic and Grid components è Need complete classification (which components to port, which ones to rewrite) è Functionality -> component

9. German Cancio – WP4 developments - n° 9 NCM: Component support libraries Component support libraries for recurring tasks: u Logging and error reporting u Template processor (for fast config file generation) u SUE sysmgt libraries n Eg. check/edit files, system information, regexps, crontab, (x)inetd… u Monitoring integration

10. German Cancio – WP4 developments - n° 10 NCM: framework A light weight framework ( cdisp ) glues the components to the Configuration Client. Overall functionality: 1.Register which components are interested in which configuration entries/subtrees 2.Upon a config update, look up the components which need to be invoked 3.Ordering of component invocations according to dependencies 4.Invocation of components

11. German Cancio – WP4 developments - n° 11 NCM Architecture cdisp server client NVA API DBM Cache Invocation registration & notification CCConfig Components XML Component libs SUE sysmgt Logging Template processor Monitoring interface Configure() Node Config Client Node Config Mgmt “Low-level” API “High-level” API

12. German Cancio – WP4 developments - n° 12 Base System Installation

13. German Cancio – WP4 developments - n° 13 Base System Installation u Nodes are installed using the default system installer. n Use standard installation infrastructure (DHCP, install servers, repositories) u Configuration information stored in the CDB, generate ks or js files n A NCM component generates ks/js files out of node profiles. n Template ks/js files used for substituting partition, network, timezone, and other miscellaneous information n Keep the installation simple: installation server should not need any tweaking excepting adding the NCM required packages. n Can be used in combination with existing environment, eg. AIMS for updating NFS & DHCP servers n Site-specific databases should not directly be accessed, only CDB (instead, update CDB with LANDB and CCDB information) u Hook into Node Configuration Management afterwards (‘post-install’) n Start the NCM which downloads the latest node profile n It will bring the machine to its state as reflected in the CDB. n (Monitoring can be activated at this moment).

14. German Cancio – WP4 developments - n° 14 Software Package Management

15. German Cancio – WP4 developments - n° 15 Software Distribution Architecture u A packaging tool takes care of installing/deinstalling/upgrading packages on a computer node and keeps an inventory of currently installed packages. u The packages themselves are stored on a managed Software Repository accessible via multiple protocols (eg. HTTP, FTP, shared file system,..) u Information on which packages are to be deployed on which nodes, and which packages are available on which repositories, is kept in the fabric-wide Configuration Database. u A 'glue' application (running on the target nodes) computes the necessary package upgrade operations and invokes the packaging tool. u (The SW generation and packaging process is outside the scope.)

16. German Cancio – WP4 developments - n° 16 Software Package Manager (SPM) u The SPM is the glue application. Functionality: 1.Compares the packages currently installed on the local node with the packages listed in the configuration 2.Computes the necessary install/deinstall/upgrade operations 3.Invokes the packager with the right operation transaction set u The SPM is driven via a local configuration file n For batch/servers: A component generates/maintains this cf file out of CDB information n For desktops: Possible to write a GUI for locally editing the cf file u The SPM core is independent of which packaging format is used.

17. German Cancio – WP4 developments - n° 17 Software Package Manager (II)  Packager: the standard system packaging format is used ( rpm for Linux, pkg for Solaris) rpmt (for rpm ‘transactional’) used for transactions handling Packager (rpmt) functionality: 1.Read operations (transaction) 2.downloads new packages from Repository 3.orders the transaction operations taking into account dependency information 4.Executes the operations (installs/removes/upgrades)

18. German Cancio – WP4 developments - n° 18 SPM Architecture Componentrpmt Repository packages GUI SPM Packages (RPM, pkg) RPM db Local Config file Transaction set filesystem Package files HTTP(S), NFS, FTP Central Config DB Installed pkgs “desired” configuration Desktops external SPM

19. German Cancio – WP4 developments - n° 19 Software Package Management u Package config flags: n Ignore locally installed packages (useful for desktops) s Local exception list, or backup of previous configuration n Reboot when package is upgraded n Do not upgrade package when node is in production (eg. runlevel X) n Standard RPM flags (no dependencies, force, no pre/post installs, etc..) s Issue: per-package flags not supported by standard RPM libraries!

20. German Cancio – WP4 developments - n° 20 SPM and the CDB u SW packages are modelised in the Global Schema as follows: n Repository configuration: List of available repositories, repository directories, and packages n Node configuration: list of used repositories, and list of selected packages. u (see next slides) u The CDB template inclusion mechanism allows to define multiple default profiles which can then be refined n Production-packages-rh72.tpl -> lxplus7.tpl -> lxplus043 n More flexibility than current ASIS profiles (Certified, InProduction)

21. German Cancio – WP4 developments - n° 21 SW repository structure (maintained by repository managers): /sw/known_repositories/Arep/url = (host, protocol, prefix dir) /owner = /extras = /directories/dir_name_X/path = (asis) /platform = (i386_rh61) /packages/pck_a/name = (kernel) /version = (2.4.9) /release = 31.1.cern /architecture = (i686) /dir_name_Y /path = (sun_system) /platform = (sun4_58) /packages/pck_b/name = (SUNWcsd) /version = 11.7.0 /release = 1998.09.01.04.16 /architecture = (?) SPM and Global Schema (I)

22. German Cancio – WP4 developments - n° 22 Node information (maintained by node administrator) /sw/used_repositories/0/rep_name_A = /1/rep_name_B = /sw/packages/package_name/version = /arch = /flags = /sw/packages/package_name/version = /arch = /flags = SPM and Global Schema (II)

23. German Cancio – WP4 developments - n° 23 Issues u Multiplatform support n How to manage components for multiple platforms (now: RH62, RH72, in the future: RH X.Y, Solaris?) n Is the global schema adequate for Solaris? n Is the SPM concept adequate for Solaris? u Backwards compatibility: LCFG, SUE n Probably not high priority. u Reusing existing software n SUE libraries and features n LCFG component libraries and components n ASIS libs u Dependencies between software package management and node configuration management