Changes between Version 12 and Version 13 of Obsolete/Doc/OS/Errata

Timestamp:

Aug 28, 2009, 11:07:32 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. 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:
@@ -70 +70 @@
 ''Note: never try to remove the RPM from the base templates used to configure the OS. First it may break some things when the errata are not deployed. Also one specific RPM is often added by several templates. But the main reason is that these templates are entirely [/wiki/Development/Templates/Generated#OSTemplates generated] from distribution official list. You obtain the same result with the line described above, except its effect is only in the context of these errata.''
 
-A good place to add this type of modifications to the base template for the errata, is the errata fix template described above.
+A good place to add this type of modifications to the base template for the errata, is the [/wiki/DOC/OS/Errata#DeployingOSErrata errata fix] template described above.