Changes between Version 34 and Version 35 of Obsolete/Development/Templates/Generated


Ignore:
Timestamp:
Feb 10, 2011, 5:45:26 PM (15 years ago)
Author:
/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Obsolete/Development/Templates/Generated

    v34 v35  
    5151
    5252Trusted CAs are described in a set of RPMs, updated regularly. There is one template describing all the trusted CAs RPMs that must be loaded. This is :
    53  * For gLite : [source:templates/trunk/grid/glite-3.0.0/common/security/cas.tpl common/security/cas.tpl]
     53 * For gLite : [source:templates/trunk/grid/glite-3.2/common/security/ca-policy-egi-core.tpl common/security/ca-policy-egi-core.tpl]
    5454
    55 This template is generated from the contents of the RPM repository containing CAs RPMS with the tools [source:SCDB/trunk/src/utils/misc/createPackagesTemplate src/utils/misc/createPackagesTemplate] which is part of [source:SCDB SCDB base].
     55This template is maintained by EGI and new versions are announced trough EGI broadcast. At the time of this writing (10/2/2011), the source is http://egi-igtf.ndpf.info/distribution/egi/current/meta/ca-policy-egi-core.tpl but look at URL in announcements.
    5656
    57 Before running this tools, it is necessary to download the new CA RPMs from the location indicated in the announcement. In QWG templates, these RPMs are stored in a specific RPM repository. 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.9 (replace the directory in the example by the directory corresponding to CA RPMs repository) :
     57I 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 stored in a specific RPM repository. 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.9 (replace the directory in the example by the directory corresponding to CA RPMs repository) :
    5858{{{
     59cd /your/scdb/top/level/dir
    5960mv /www/htdocs/packages/ca /www/htdocs/packages/ca.old
    6061mkdir /www/htdocs/packages/ca
    61 cd /www/htdocs/packages/ca
    62 wget http://glitesoft.cern.ch/LCG-CAs/current/RPMS.production/index.html
    63 wget --force-html --no-directories --base  http://glitesoft.cern.ch/LCG-CAs/current/RPMS.production/index.html -A.rpm -i index.html
     62# Look at URL mentionned in the announcemet
     63utils/misc/rpmUpdate /www/htdocs/packages/ca http://repository.egi.eu/sw/production/cas/1/current/RPMS/
    6464}}}
    6565
    66 Then run [source:SCDB/trunk/src/utils/misc/createPackagesTemplate src/utils/misc/createPackagesTemplate]. For example, for gLite 3.0 and with previous directories :
    67 {{{
    68 src/utils/misc/createPackagesTemplate --namespace common/security \
    69                                       --template cfg/grid/glite-3.0.0/common/security/cas.tpl \
    70                                       /www/htdocs/packages/ca
    71 }}}