Maite Barroso - 10/05/01 - n° 1 WP4 PM9 Deliverable Presentation: Interim Installation System Configuration Management Prototype

Maite Barroso – 10/05/01 - n° 2 Interim Installation System Tool for automated system installation and application distribution on testbed nodes. Purpose: u Automatically install the system through the network. u Configure the system parameters and apply site policies. u Make available the needed applications. u Run maintenance tasks and perform upgrades whenever needed.

Maite Barroso – 10/05/01 - n° 3 Interim Installation System SCOPE u Scale to allow automatic installation and maintenance of the largest testbed in PM9. u Linux clusters are prime target, but implemented in a portable way. u It will use the Configuration Management Prototype to get all the configuration information. u The deliverable does not include the Software Repository, nor the OS images, or configuration files. But means and instructions how to setup them will be provided.

Maite Barroso – 10/05/01 - n° 4 Interim Installation System SELECTED TOOLS: u VACM (VA Linux) to provide console control for system preparation. Image based. u LCFG (Edinburgh University) for software installation, upgrade, verification and maintenance tasks. Package based.

Maite Barroso – 10/05/01 - n° 5 Interim Installation System How to prepare application SW to be installed in the testbed for PM9: u RPM format n No pre/post-install scripts n Documentation files: %doc n Configuration files: %config n Versioning similar to RedHat distribution u Additional rules for daemons, permanently running processes…

Maite Barroso – 10/05/01 - n° 6 Configuration Management Prototype Purpose: Provide the low level language and API for fabric components to reliably retrieve their configuration information.

Maite Barroso – 10/05/01 - n° 7 Configuration Management Prototype SCOPE  Scale to allow configuration of the largest testbed in PM9.  Linux clusters are prime target, but implemented in a portable way.  It should be used by PM9 Interim Installation System to get all the configuration information.

Maite Barroso – 10/05/01 - n° 8 Configuration Management Prototype DETAILS:  The configuration information will be stored in XML.  The task to add/modify configuration information shall be done by the users/administrators, manually or via scripts or using their own developed applications.  Every node will have a cache-copy of its configuration information, accessible via an API.

Maite Barroso – 10/05/01 - n° 9 Configuration Management Prototype OVERVIEW Entering of the configuration profiles (manual or through scripts for this prototype) LLD (XML) CLLD ( Cached LLD) Applications (e.g. PM9 IIS) Fetching (read-only) API (read-only) Client machine CDB Web server giving access to one configuration file per host HTTP Host profile

Maite Barroso – 10/05/01 - n° 10 Configuration Management Prototype OVERVIEW Web servers distribute the configuration data as XML strings over HTTP. Client requests a profile from one of the web servers. LLD (XML) CLLD ( Cached LLD) Applications (e.g. PM9 IIS) Fetching (read-only) API (read-only) Client machine CDB Web server giving access to one configuration file per host HTTP

Maite Barroso – 10/05/01 - n° 11 Configuration Management Prototype OVERVIEW LLD (XML) CLLD ( Cached LLD) Applications (e.g. PM9 IIS) Fetching (read-only) API (read-only) Client machine CDB Web server giving access to one configuration file per host HTTP The client maintains a cache copy of the profile and auxiliary resources allowing for disconnected operation and optimized resource lookup.