Changes between Version 105 and Version 106 of Download/SCDB


Ignore:
Timestamp:
Dec 3, 2009, 2:34:48 PM (16 years ago)
Author:
/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Download/SCDB

    v105 v106  
    476476wget --no-check-certificate "https://svn.lal.in2p3.fr/LCG/QWG/SCDB/trunk/src/hooks/post-commit.py" -O /var/svn/quattor/hooks/post-commit
    477477chmod 755 /var/svn/quattor/hooks/post-commit
    478 wget --no-check-certificate "https://svn.lal.in2p3.fr/LCG/QWG/SCDB/trunk/src/hooks/build-tag.pl" -O /root/quattor/scripts/build-tag.pl
    479 chmod 755 /root/quattor/scripts/build-tag.pl
     478wget --no-check-certificate "https://svn.lal.in2p3.fr/LCG/QWG/SCDB/trunk/src/hooks/build-tag.py" -O /root/quattor/scripts/build-tag.py
     479chmod 755 /root/quattor/scripts/build-tag.py
    480480}}}
    481481
     
    484484=== Creation of SSH Keys ===
    485485
    486 Currently, deployment of new version of the templates is done by the hook script triggered by `ant deploy` executing the server script `build-tag.pl` through ssh. There is no way to enter a password at this time, thus ssh must be configured in such a way that the Apache account on the Subversion server can do a ssh connection as root on the Quattor server, without password. The easiest is to use ssh keys to do that.
    487 
    488 ''Note: if you run SVN server on the Quattor server, an alternative to SSH is to use `sudo`. This currently requires to use a specific variant of the `post-commit` script, [source:SCDB/tags/pro/src/hooks/post-commit.sudo post-commit.sudo]. After installing the script, instead of configuring SSH keys, you need to add the following configuration lines (customize them to reflect your local configuration) to `sudo` with `visudo` utility:''
    489 {{{
    490 Cmnd_Alias   QUATTORDEPLOY=/root/quattor/scripts/build-tag.pl *
     486''Note: this step is necessary only if you use `ssh` for the communication between the SVN server and the Quattor deployment server. If they run on the same machine, it is recommended to use [#sudoConfiguration sudo] instead.''
     487
     488When using `ssh` as the communication method between the SVN server and the Quattor server, it is necessary to configure SSH keys to allow a password-less ssh connection (there is no way to enter a password in the script).
     489
     490=== sudo Configuration ==
     491
     492''Note: this step is necessary only if you use `sudo` for the communication between the SVN server and the Quattor deployment server. This requires both service to run on the same machine and is the recommended communication method in this situation. If both services run on different machines, you need to use [#CreationofSSHKeys ssh] instead.''
     493
     494To configure `sudo` for SCDB, use the `visudo` utility and enter the following lines in the  `sudo ` configuration (be sure to use the appropriate path and account in your configuration):
     495{{{
     496Cmnd_Alias   QUATTORDEPLOY=/root/quattor/scripts/build-tag.py *
    491497apache ALL = NOPASSWD: QUATTORDEPLOY
    492498Defaults:apache !requiretty
    493499}}}
     500
    494501''The last line is required on later versions of RHEL-like operating systems.  If it is not given, the sudo will silently fail.''
    495502