Difference between revisions of "Adding a new VO"
| Line 34: | Line 34: | ||
'''grid/vo/params/''voname''.tpl''' | '''grid/vo/params/''voname''.tpl''' | ||
| − | Configuration of VO settings like the VOMS server, | + | Configuration of VO settings like the VOMS server, Unix pool account and group for 1 user, various FQAN for groups and roles, location of the software installation directory, the default storage element etc. It is recommended to copy an existing template, rename it and customize its contents. |
'''cluster/''facility-name''/local/pro_config_lcg2_site.tpl''' | '''cluster/''facility-name''/local/pro_config_lcg2_site.tpl''' | ||
| Line 40: | Line 40: | ||
This file defines variable VOS, which is a list of all supported VO names. | This file defines variable VOS, which is a list of all supported VO names. | ||
Also, the name of the VOMS server can be added to variable VOMS_SERVER_CERTIFICATES to isntall the certificate for the VOMS server. | Also, the name of the VOMS server can be added to variable VOMS_SERVER_CERTIFICATES to isntall the certificate for the VOMS server. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
'''cluster/''facility-name''/local/pro_config_queues.tpl''' | '''cluster/''facility-name''/local/pro_config_queues.tpl''' | ||
| Line 56: | Line 48: | ||
Add a line to the Maui configuration to specify the fair share and priority of the VO. | Add a line to the Maui configuration to specify the fair share and priority of the VO. | ||
| + | |||
| + | Note: it is no longer needed to add user and group information to Yaim. The contents of those files are now derived from the VO parameters defined above. Via variable USE_DYNAMIC_POOL_ACCOUNTS=true all VOs are mapped to the same dynamic pool account range (dyn00000 and up, group dynamic). | ||
=== In some cases - adding the new VO to some of our RBs and/or DPM - additional Quattor profiles have to be modified === | === In some cases - adding the new VO to some of our RBs and/or DPM - additional Quattor profiles have to be modified === | ||
| Line 61: | Line 55: | ||
add VO-Name to variable: VOS = list | add VO-Name to variable: VOS = list | ||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 17:23, 25 February 2010
Collect information about the new VO
Go to the CIC portal ([1]) to collect information about the new VO.
Relevant information are the VOMS server(s), the content for the vomses file, possible VOMS roles and groups to be supported, indications of the number of required pool accounts etc.
Create pool accounts and the gridmapdir
Find a free Unix group ID and user ID range for the pool accounts. This can be achieved with via an ldapsearch query, or easier by using the ldap browser (LBE). LBE is available at the Nikhef desktops via /global/ices/toolset/bin/lbe.
Create pool accounts, home directories for the pool accounts and gridmapdir entries using the procedure described at the following page: [[2]].
The LFC no longer needs a gridmapdir. The Resource Brokers, WMS servers and DPM servers (head node and disk servers) use a dynamic pool account range (dynXXXXX) that is independent of the VO. This gridmapdir is managed by Quattor and does not need modification when adding a new VO.
Create a software installation area
This section is only needed if the VO requires a software installation area.
The software installation areas are located under /export/data/esia at host hoeve. The areas should be created manually, as user root at hoeve.
mkdir /export/data/esia/voname chgrp unixgroup /export/data/esia/voname chmod g+wrs /export/data/esia/voname chmod +t /export/data/esia/voname
If there is a group of pool accounts for sgm users for the VO, unixgroup should match the group for the sgm users.
Add the VO configuration to Quattor profiles
All modifications to the Quattor set up are located in the template hierarchy under directory $L/cfg where $L points to the conf-ns directory under the Quattor root directory. The basic VO definition is (by default) independent of the facility. The rest of the configuration is specific per VO.
grid/vo/params/voname.tpl
Configuration of VO settings like the VOMS server, Unix pool account and group for 1 user, various FQAN for groups and roles, location of the software installation directory, the default storage element etc. It is recommended to copy an existing template, rename it and customize its contents.
cluster/facility-name/local/pro_config_lcg2_site.tpl
This file defines variable VOS, which is a list of all supported VO names. Also, the name of the VOMS server can be added to variable VOMS_SERVER_CERTIFICATES to isntall the certificate for the VOMS server.
cluster/facility-name/local/pro_config_queues.tpl
Add the name of the new VO to the appropriate queues in the variables (type: nlist) QUEUE_ACCESS and QUEUE_GROUP_ENABLE. The former defines ACLs for Torque, the latter for VO views in the information system, which may also contain any specific VOMS groups or roles.
cluster/facility-name/local/pro_config_maui.tpl
Add a line to the Maui configuration to specify the fair share and priority of the VO.
Note: it is no longer needed to add user and group information to Yaim. The contents of those files are now derived from the VO parameters defined above. Via variable USE_DYNAMIC_POOL_ACCOUNTS=true all VOs are mapped to the same dynamic pool account range (dyn00000 and up, group dynamic).
In some cases - adding the new VO to some of our RBs and/or DPM - additional Quattor profiles have to be modified
cluster/facility-name/profiles/profile_RB-Name.tpl
add VO-Name to variable: VOS = list
