gLite 3.0: How to install a production VO (by lorentey@elteNOSPAMPLEASE.hu)

This procedure may be used to set up a new VOMS server host, and also to install a new VO on an existing host.

BEWARE! All this is for gLite 3.0 only. We expect that some of the workarounds described here will become unnecessary or even downright harmful in later releases. This is especially relevant for the voms.massage script.

(1) Set up the site.config.url parameter in
    /opt/glite/etc/config/glite-global.cfg.xml.

    I have set up a site config file on lxb2051 at

   .../voms.2006-03-15.newHW/voms.config.xml

    The configuration sets up VOs to use the normal (_w-less) accounts
    on the production database.  As the XML config does not yet
    support the long connection strings, the configuration is for a
    single database host, not the entire high availability cluster.

    If you want to create a new VO, you'll simply need to add it to
    the site config.


(2) Log in to the VOMS server host.  Make sure there are no defined
    VOs yet.  If the command

   ls -l /var/glite/etc/voms-admin/*/voms.database.properties

    finds any files, then execute step (3), else continue with step (4).=20=
    (glite-voms-server-config.py is unable to reconfigure
    existing VOs due to bug #10434.)


(3) Stop the gLit service and 
    Remove all existing VO definitions by running
    glite-voms-server-config.py with the --remove-vo option.  Don't
    worry, this will not touch the database.

   /opt/glite/etc/config/scripts/glite-voms-server-config.py --remove-vo alice
   /opt/glite/etc/config/scripts/glite-voms-server-config.py --remove-vo atlas
   /opt/glite/etc/config/scripts/glite-voms-server-config.py --remove-vo cms
   /opt/glite/etc/config/scripts/glite-voms-server-config.py --remove-vo dteam
   /opt/glite/etc/config/scripts/glite-voms-server-config.py --remove-vo geant4
   /opt/glite/etc/config/scripts/glite-voms-server-config.py --remove-vo lhcb
   /opt/glite/etc/config/scripts/glite-voms-server-config.py --remove-vo ops
   /opt/glite/etc/config/scripts/glite-voms-server-config.py --remove-vo sixt
   /opt/glite/etc/config/scripts/glite-voms-server-config.py --remove-vo test
   /opt/glite/etc/config/scripts/glite-voms-server-config.py --remove-vo unosat

(4) Run glite-voms-server-config.py with the --configure option.

   /opt/glite/etc/config/scripts/glite-voms-server-config.py --configure

    It will not run successfully, and create all configured VOs due to the 
'enableD' variable in the gliteRgmaServicetool.py script.

(5) Logout to update env

(6) Run the voms.massage script, a copy of which is attached to this
    message.  The script will fix the Oracle library paths, fix the above
    var. typo 
    and set up
    the VOs to use the production database cluster (instead of a
    single unreliable database host, as described in the site config).
    It will also automatically set up the *_W accounts with the
    correct grants and change the core service to use the _W accounts.

    The voms.massage script will change/create the following files:

   /opt/glite/etc/voms/tnsnames.ora
   /etc/glite/profile.d/glite_setenv.sh
   /etc/glite/profile.d/glite_setenv.csh
        /opt/glite/etc/voms/*/voms.conf
        /var/glite/etc/voms-admin/*/voms.database.properties

(7) Logout to update env.

(8) Re-run the voms-server-config.py script

(9) Start glite

-- AndreaCeccanti - 27 Mar 2006