Changes between Version 9 and Version 10 of Download/QWGTemplates/Install
- Timestamp:
- Mar 30, 2007, 9:19:53 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Download/QWGTemplates/Install
v9 v10 9 9 == Initial Installation == 10 10 11 For an initial installation of QWG templates, you first need to initialize you repository with a base configuration database. If you want to use [wiki:Doc/SCDB SCDB], you need : 12 * Setup [wiki:Doc/SCDB/Usage#GettingStarted basic structure] of SCDB. 13 * Export QWG templates (e.g. use `svn export` or download the tarball) in your SCDB. 11 For an initial installation of QWG templates, you first need to initialize you repository with a base configuration database. If you want to use [wiki:Doc/SCDB SCDB], follow instructions on how to [wiki:Download/SCDB#SCDBInitialization configure] your Quattor server with SCDB, in particular [https://trac.lal.in2p3.fr/LCGQWG/wiki/Download/SCDB#SCDBInitialization SCDB initialization]. 14 12 15 13 == Upgrading an existing repository == … … 18 16 19 17 We do our best to ensure that new versions are backward compatible. This means that if you made site customization using the [wiki:Doc 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... 18 19 Standard templates are made of 3 areas (see [wiki:Doc/TemplateCustom template layout]) : 20 * OS templates : they are never modified, except for fixes. The only modifications apply to errata RPM list. These errata are not installed by default. 21 * Middleware templates (if using them) : they bring both changes and fixes at each release. They are intended to be backward compatible : that means the resulting configuration should be the same if you don't change your local configuration. As part of QWG releases, they deliver gLite updates : `GLITE_UPDATE_VERSION` allows to control deployment of gLite updates as part of QWG templates update. 22 * Standard templates : all modifications in this area are entirely backward compatible 23 24 There are 2 methods to upgrade QWG templates, according to the structure and constraints of your site : 25 * In place upgrade : in this scenario, existing templates will be upgraded and the changes will be deployed on all clusters of your site. You can control the gLite updates you deploy on a per node basis. 26 * Fresh installation of new middleware templates : this allows to control on a per cluster basis the deployement of new QWG templates. 27 20 28 21 29 For an easy upgrade, the recommended method is :
