Changes between Version 15 and Version 16 of Obsolete/Doc/OS/Errata

Timestamp:

Sep 25, 2009, 5:43:53 PM (15 years ago)

Author:

/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin

Comment:

--

Obsolete/Doc/OS/Errata

@@ -49 +49 @@
 Errata deployment is controlled through variable `PKG_DEPLOY_OS_ERRATA`. By default, to avoid any problem at a site, errata deployment is disabled. But sites are '''strongly''' encouraged to define this variable to `true` to enable errata deployment. The most usual places to define this variables are [source:templates/trunk/clusters/example-3.1/site/cluster-info.tpl site/cluster-info.tpl] to control it at a cluster level or in [source:templates/trunk/sites/example/site/config.tpl site/config.tpl]  in your site-specific templates to control it at the site level. It is recommended to define a default value (using operator `?= `) to allow further redefinition in a node profile.
 
-When enabled, OS errata deployement uses by default template `rpms/errata.tpl` (or whatever the variable `PKG_OS_ERRATA_TEMPLATE_DEFAULT` refers to)  in OS templates to find out the actions to do. This template is normally empty or non existent. It is the site responsability to produce the template with all the package replacements and other configuraction actions required to deploy the errata. See previous section. The templates produced are generally put in `rpms/errata` in OS templates. The name is at the site discretion but it is recommended to choose a name reflecting the errata data for easier tracking and support of multiple errata versions.
+When enabled, OS errata deployement uses by default template `rpms/errata.tpl` (or whatever the variable `PKG_OS_ERRATA_TEMPLATE_DEFAULT` refers to)  in OS templates to find out the actions to do. This template is normally empty or non existent. It is the '''site responsability''' to produce the template with all the package replacements and other configuraction actions required to deploy the errata (QWG templates contains some errata related templates for major vulnerabilities). See previous section. The templates produced are generally put in `rpms/errata` in OS templates. The name is at the site discretion but it is recommended to choose a name reflecting the errata data for easier tracking and support of multiple errata versions.
 
 The actual errata version deployed on a given node is controlled by a two variables:
- * `OS_ERRATA_TEMPLATE`: this nlist defines the default OS errata version to use for a given OS version. The key is usual version+architecture combination (e.g. `sl470-x86_64`), the value is the name of the errata template to execute (the same name you would use in an `include` statement to execute the same template).
- * `NODE_OS_ERRATA_TEMPLATE`: this nlist defines the OS errata version to use for a specific node. The key is escaped node name, the value is the name of the errata template to execute (the same name you would use in an `include` statement to execute the same template). If a given node has an entry matching its name in this variable, this overrides the default defined for the OS.
+ * `OS_ERRATA_TEMPLATE`: this nlist defines the default OS errata version to use for a given OS version. The key is usual version+architecture combination (e.g. `sl470-x86_64`), the value is the name of the errata template to execute (the same name you would use in an `include` statement to execute the same template). This variable is typically defined in a site specific template that must be included by [source:templates/trunk/sites/example/site/os/version_db.tpl sites/example/site/os/version_db.tpl]: look at [source:templates/trunk/sites/example/site/os/errata-defaults.tpl sites/example/site/os/errata-defaults.tpl] for an example.
+ * `NODE_OS_ERRATA_TEMPLATE`: this nlist defines the OS errata version to use for a specific node. The key is escaped node name, the value is the name of the errata template to execute (the same name you would use in an `include` statement to execute the same template). If a given node has an entry matching its name in this variable, this overrides the default defined for the OS. This variable is typically defined in [source:templates/trunk/sites/example/site/os/version_db.tpl sites/example/site/os/version_db.tpl] or another template it includes.
 
 ''Note: direct definition of  variable `PKG_OS_ERRATA_TEMPLATE` to control the errata version to deploy is discouraged, even though it used to be the standard practice. Use the method describe above instead.''