Changes between Version 4 and Version 5 of Doc/gLite/Updates
- Timestamp:
- Apr 6, 2012, 8:06:30 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Doc/gLite/Updates
v4 v5 19 19 Both are normally maintained centrally by a grid organization, for example EGI or a specific NGI. '''They are updated regullarly and each update needs to be deployed in a timely fashion on every site.''' 20 20 21 The [source:templates/trunk/ grid/glite-3.2/common/security/ca-policy-egi-core.tpl EGI default policy] is provided in QWG templates. This template is '''maintained by EGI''' and new versions are announced trough EGI broadcast. At the time of this writing (10/2/2011), the official source is http://egi-igtf.ndpf.info/distribution/egi/current/meta/ca-policy-egi-core.tpl but look at precise URL in announcements.21 The [source:templates/trunk/standard/security/ca-policy-egi-core.tpl EGI default policy] is provided in QWG templates. This template is '''maintained by EGI''' and new versions are announced trough EGI broadcast. At the time of this writing (10/2/2011), the official source is http://egi-igtf.ndpf.info/distribution/egi/current/meta/ca-policy-egi-core.tpl but look at precise URL in announcements. It is also available from [source:External/CAs QWG repository] which contains one directory for each version of the IGTF trusted CA releases. This template must be placed in directory [source:templates/trunk/standard/security standard/security]. 22 22 23 23 In addition to downloading the template, it is necessary to download the new CA RPMs from the location indicated in the announcement. In QWG templates, these RPMs are generally stored in a specific RPM repository for easier management. It is a good practice to rename the corresponding directory, create a new one with the same name and download the new RPMs in this empty directory. For example, for CA 1.38 (replace the directory in the example by the directory corresponding to CA RPMs repository) : … … 30 30 }}} 31 31 32 33 The template is called [source:templates/trunk/grid/glite-3.1/common/security/cas.tpl cas.tpl] and is available from [source:External/CAs QWG repository] which contains one directory for each version of the IGTF CA releases. This template must be placed in directory `common/security` of every gLite version under `grid` directory (this is the same template for each version).34 32 35 33 As an alternative to renaming CA repository, you may have one directory per version of the CA trust policy (eg. `ca-1.37`, `ca-1.38`...) and define a symlink (eg. `ca`) pointing to the version currently in production. This may reduce the risk of mistake. In this case, ensure your Apache configuration allows the use of symlinks for the URL/directory corresponding to the symlink. You may need to update your Apache configuration with something like: … … 44 42 == gLite Updates == 45 43 46 To be written. In the meantime you may have a look to wiki:Download/QWGTemplates/Install.44 Look to wiki:Download/QWGTemplates/Install. 47 45 48 46 Keep in mind that the normal and easiest procedure to install a gLite update is to get the [wiki:Download/QWGTemplates/Install last version] of the templates from the appropriate branch.