Difference between revisions of "How to work with our Quattor setup"
m (→Overview) |
m (→Overview) |
||
| Line 10: | Line 10: | ||
If the compilation was successful, i.e., without errors or warnings, the modified templates can be checked in into the Subversion repository. Note: modified templates should only be checked in if they are to be deployed immediately! Checking in templates but not deploying them could cause surprises for the next person to deploy his changes (well, that's what he might think!). | If the compilation was successful, i.e., without errors or warnings, the modified templates can be checked in into the Subversion repository. Note: modified templates should only be checked in if they are to be deployed immediately! Checking in templates but not deploying them could cause surprises for the next person to deploy his changes (well, that's what he might think!). | ||
| − | The deployment phase consists of a checkout on the Quattor server using a dedicated account, followed by a compilation and deployment procedure. The details of this process are given in section [[How_to_work_with_our_Quattor_setup#Deploying]]. | + | The deployment phase consists of a checkout on the Quattor server using a dedicated account, followed by a compilation and deployment procedure. The details of this process are given in section [[How_to_work_with_our_Quattor_setup#Deploying|Deploying]]. |
== Using the repository == | == Using the repository == | ||
Revision as of 16:07, 17 November 2008
This article describes how to perform basic and essential tasks with the current setup of Quattor at Nikhef.
Overview
Everyone who wants to make changes in the Quattor setup, should make them in his private working area. The working area can be created by checking out from the repository; see section Using the repository for details.
After making the changes in the private working copy, the templates should be compiled. How this is done is described in the section Compiling.
If the compilation was successful, i.e., without errors or warnings, the modified templates can be checked in into the Subversion repository. Note: modified templates should only be checked in if they are to be deployed immediately! Checking in templates but not deploying them could cause surprises for the next person to deploy his changes (well, that's what he might think!).
The deployment phase consists of a checkout on the Quattor server using a dedicated account, followed by a compilation and deployment procedure. The details of this process are given in section Deploying.
Using the repository
The Quattor setup, comprising the template hierarchy and the SCDB setup, are stored on the Subversion server ndpfsvn.nikhef.nl in repository ndpf. Access to this repository is limited to selected administrators. See the Wiki article on SVN access for details.
Checking out
Details on checking out.
Checking in
Details on checking in
Compiling
Building and deploying templates is easiest with the shell scripts makexprof and pushxprof, respectively. Note that the latter is a symlink to the former. Syntax:
makexprof -f <facility-name> [template1] [template2] [...] pushxprof -f <facility-name> [template1] [template2] [...]
The option -f with argument <facility-name> is required to select one of the facility names. Currently defined facilities: itb (Installation Test Bed), prd (Production cluster) and generic (miscellaneous Quattor-managed servers).
Updating the templates that describe the contents of the package repositories is done by directly executing the task update.rep.templates in the Ant script:
( cd $L ; ant update.rep.templates )
