33e6a2a98672377f845c1a354e049758.ppt
- Количество слайдов: 11
WP 4 PM 9 Deliverable Presentation: Interim Installation System Configuration Management Prototype Maite. Barroso. Lopez @cern. ch Maite. Barroso. Lopez@cern. ch Maite Barroso - 10/05/01 - n° 1
Interim Installation System Tool for automated system installation and application distribution on testbed nodes. Purpose: u. Automatically u. Configure u. Make install the system through the network. the system parameters and apply site policies. available the needed applications. u. Run maintenance tasks and perform upgrades whenever needed. Maite Barroso – 10/05/01 - n° 2
Interim Installation System SCOPE u. Scale to allow automatic installation and maintenance of the largest testbed in PM 9. 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° 3
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° 4
Interim Installation System How to prepare application SW to be installed in the testbed for PM 9: u RPM format n No pre/post-install scripts n Documentation files: %doc n Configuration files: %config n Versioning similar to Red. Hat distribution u Additional rules for daemons, permanently running processes… Maite Barroso – 10/05/01 - n° 5
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° 6
Configuration Management Prototype SCOPE u. Scale to allow configuration of the largest testbed in PM 9. u. Linux clusters are prime target, but implemented in a portable way. u. It should be used by PM 9 Interim Installation System to get all the configuration information. Maite Barroso – 10/05/01 - n° 7
Configuration Management Prototype DETAILS: u. The configuration information will be stored in XML. u. The task to add/modify configuration information shall be done by the users/administrators, manually or via scripts or using their own developed applications. u. Every node will have a cache-copy of its configuration information, accessible via an API. Maite Barroso – 10/05/01 - n° 8
Configuration Management Prototype OVERVIEW Host profile Entering of the configuration profiles (manual or through scripts for this prototype) • Web server giving access to one configuration file per host LLD (XML) CDB HTTP API (read-only) Fetching (read-only) CLLD Applications (e. g. PM 9 IIS) (Cached LLD) Client machine Maite Barroso – 10/05/01 - n° 9
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. • Web server giving access to one configuration file per host LLD (XML) CDB HTTP API (read-only) Fetching (read-only) CLLD Applications (e. g. PM 9 IIS) (Cached LLD) Client machine Maite Barroso – 10/05/01 - n° 10
Configuration Management Prototype OVERVIEW • The client maintains a cache copy of the profile and auxiliary resources allowing for disconnected operation and optimized resource lookup. Web server giving access to one configuration file per host LLD (XML) CDB HTTP API (read-only) Fetching (read-only) CLLD Applications (e. g. PM 9 IIS) (Cached LLD) Client machine Maite Barroso – 10/05/01 - n° 11
33e6a2a98672377f845c1a354e049758.ppt