Version 35 (modified by 15 years ago) (diff) | ,
---|
Where to Get QWG Templates ?
TracNav
Table of Contents
QWG Repository
Main source for LCG QWG templates is the Subversion repository, located at URL :
https://svn.lal.in2p3.fr/LCG/QWG/templates
There are 3 areas in the repository, located under this URL :
- trunk : this is where you can get the most recent changes to the templates. The structure of this branch is a little bit different from other branches, this is a log of every modification made to the templates. Every change is first done in the trunk. This is not guaranteed to work... This branch should not be used as a source for a production SCDB.
- branches : contains one branch per middleware version. These branches contain changes merged from the trunk and the branch revision log link to the trunk revisions where the the changes were introduced. What's here is something reasonnably stable, very often announced as pre-releases. This is the recommended version to use for production, in particular for grid templates. It allows to get last updates for critical services like patches, VO parameters, certificates...
- tags : contains one tag per stable version of the templates. The tag name starts with the middleware release, so it is quite easy to identify what you are looking for. Versions in the tag area are what we call QWG releases. They link to the corresponding branch revision. By definition they are outdated as soon as they are released...
You can browse each of these areas using button browse of the current web interface.
Download
The standard method to download the templates is using a Subversion client : checkout or export URL corresponding to the version you need. Avoid to download all versions as it can be quite a large (and long) download... It is recommended to do a checkout you keep somewhere on your disk : then you can use SVN commands to update your local copy of QWG templates rather than doing a full download at each version.
If you don't have a Subversion client, we can provide a tarball of a specific QWG release on demand. To request it, open a ticket in ELFms Savanah portal.
RPMs required by Templates
In addition to the templates, you also need to get the RPMs. The easiest is to get them from GRIF site, using the URLs in the comments at the beginning of repository template examples. The easiest way to download the new RPMs in an existing RPM repository is to use src/utils/misc/rpmUpdates.pl :
# Redirect stdout to /dev/null as the template produced is not needed src/utils/misc/rpmUpdates.pl /your/RPM/repository/path http://source.node.example/source/url > /dev/null
If you want to download the templates from the official gLite repositories, you must use wget
.
- For gLite 3.0, there are 3 separates areas :
- Base RPMs provided by gLite : http://glitesoft.cern.ch/EGEE/gLite/APT/R3.0/rhel30/RPMS.Release3.0/
- External products used by gLite : http://glitesoft.cern.ch/EGEE/gLite/APT/R3.0/rhel30/RPMS.externals/
- Updates : http://glitesoft.cern.ch/EGEE/gLite/APT/R3.0/rhel30/RPMS.updates/
- For gLite 3.1, there are 3 separate areas for each architecture (
i386
orx86_64
). Replacei386
byx86_64
in the URLs below to get 64-bit RPMs :- Base RPMs provided by gLite : http://glitesoft.cern.ch/EGEE/gLite/R3.1/generic/sl4/i386/RPMS.release
- External products used by gLite : http://glitesoft.cern.ch/EGEE/gLite/R3.1/generic/sl4/i386/RPMS.externals
- Updates : http://glitesoft.cern.ch/EGEE/gLite/R3.1/generic/sl4/i386/RPMS.updates
- For gLite 3.2, there are 3 separate areas for each architecture (
i386
,x86_64
).x86_64
is the main architecture (and for some services the only one] in gLite 3.2. gLite 3.2 requires SL5 :- Base RPMs provided by gLite : http://glitesoft.cern.ch/EGEE/gLite/R3.2/glite-GENERIC/sl5/x86_64/RPMS.release
- External products used by gLite : http://glitesoft.cern.ch/EGEE/gLite/R3.2/glite-GENERIC/sl5/x86_64/RPMS.externals
- Updates : http://glitesoft.cern.ch/EGEE/gLite/R3.2/glite-GENERIC/sl5/x86_64/RPMS.updates
Note : In gLite 3.1 and higher, there is actually one distribution point per node type but they are currently all aliases to generic
. In Quattor, because SPMA
install an explicit version and architecturre, there is no need to have separate RPM repositories for each service and each architecture.
In addition to RPMs provided by gLite, templates need RPMs provided by JPackages for several Java utils packages. These RPMs are easily identified as their version ends with jpp
. These packages can generally be retrieved with wget
from http://mirrors.dotsrc.org/jpackage/1.7/generic/free/RPMS/. In case of problem use JPackage repository browser.
For ncm-components, the official distribution point for component RPMs is http://eticssoft.web.cern.ch/eticssoft/repository/quattor-compiler/ncm-components. This URL is updated daily with the last sources available. As an alternative, you can use GRIF RPM repository, http://quattorsrv.lal.in2p3.fr/packages/ncm-components or you can rebuild the component? from CVS.
Upgrade
Look at page on QWG templates installation.
Recent Changes
Tags
Changelog not available
Branch gLite-3.0.0
Changelog not available
Click here for more details.
Branch gLite-3.1
Changelog not available
Click here for more details.
Branch no-grid
Changelog not available
Trunk
Changelog not available
Click here for more details.