Difference between revisions of "VO-specific software and modules"
From PDP/Grid Wiki
Jump to navigationJump to search| Line 5: | Line 5: | ||
In this HOWTO the VO <tt>vlemed</tt> was chosen as the example. This VO has a role | In this HOWTO the VO <tt>vlemed</tt> was chosen as the example. This VO has a role | ||
/Role=sgm | /Role=sgm | ||
| − | available, which gives users who possess that role the right to install software in the VO specific software area, normally denoted using the | + | available, which gives users who possess that role the right to install software in the VO specific software area, normally denoted using the environment variable <tt>VO_<VO>_SW_DIR</tt> e.g. |
| − | |||
| − | e.g. | ||
VO_VLEMED_SW_DIR | VO_VLEMED_SW_DIR | ||
Revision as of 17:51, 11 December 2009
Introduction
VOs sometimes have a need to deploy their own software at a particular site. For this the Software Group Manager VOMS role is available. Not all VOs have this role and not all VOs with this roles are supported at each site. However, if you are an SGM for a VO which is supported at Nikhef then this HOWTO will explain how you can deploy your own software and add your own module to the available modules for the modules command.
In this HOWTO the VO vlemed was chosen as the example. This VO has a role
/Role=sgm
available, which gives users who possess that role the right to install software in the VO specific software area, normally denoted using the environment variable VO_<VO>_SW_DIR e.g.
VO_VLEMED_SW_DIR
