| Version 9 (modified by , 18 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 :
http://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 version of the templates. This is not necessarily the most stable... And it generally works only with the most recent version of the middleware.
- branches : contains one branch per middleware version. For every middleware version, what's here is something reasonnably stable, not necessarily the most recent...
- 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.
You can browse each of these areas using button browse of the current web interface.
Download
You have the choice between 2 methods to download the templates :
- Subversion client : this is the preferred method. Using a SVN client of your choice you 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... With this method, you can use SVN commands to update your local copy of QWG templates rather than doing a full download at each version.
- QWG release tarball : if you don't have access to a SVN client, you can download the tarball we produce for each official release of the QWG templates. Tarball are located at the end of this pages and are named according to the official release name.
Upgrade
If you are using the recommended template layout with separate areas for standard templates in your configuration database, upgrading should be no more than replacing the previous version of the templates.
We do our best to ensure that new versions are backward compatible. This means that if you made site customization using the described method (pro_lcg2_config_site, pro_site_cluster_info...) and didn't modify standard templates, no changes should be required to use new version of the templates. When this is really required to introduce a new feature or bring more flexibility for configuring a service, it can happen that this full compatibility cannot be retained. This is normally stated in release announcement. You are always better to check...
Recent Changes
Tags
Changelog not available
Branch LCG 2.7.0
Changelog not available
Branch LCG 2.7.0
Changelog not available
Trunk
Changelog not available
