Adding a new cluster to BalticGrid

BalticGrid VO and relevant setup

 

In order to configure your site to support BalticGrid VO you should set up several variables in your site-info.def and users.conf

file.

 

• Add BalticGrid VO to the list of supported VOs:
  

VOS="balticgrid"

• Set up the VO-related services:
  

VO_BALTICGRID_SW_DIR=$VO_SW_DIR/balticgrid 
VO_BALTICGRID_DEFAULT_SE=$SE_HOST
#VO_BALTICGRID_SGM=vomss://voms.balticgrid.org:8443/edg-voms-admin/balticgrid?/balticgrid/Role=sgmadmin
#VO_BALTICGRID_USERS=vomss://voms.balticgrid.org:8443/edg-voms-admin/balticgrid?/balticgrid/
VO_BALTICGRID_STORAGE_DIR=$CE_CLOSE_SE1_ACCESS_POINT/balticgrid
VO_BALTICGRID_QUEUES="balticgrid"
VO_BALTICGRID_VOMS_SERVERS="vomss://voms.balticgrid.org:8443/voms/balticgrid?/balticgrid/"
VO_BALTICGRID_VOMSES="'balticgrid voms.balticgrid.org 15000 /DC=org/DC=balticgrid/OU=eenet.ee/CN=host/voms.balticgrid.org balticgrid'"

• Set up a poll of local accounts that will be used for BalticGrid VO in your users.conf file e.g.
  

20001:balticgrid01:1521:balticgrid:balticgrid::
20002:balticgrid02:1521:balticgrid:balticgrid::
20101:balticgridsgm:1521:balticgrid:balticgrid:sgm:

We recommend to create at least 50 accounts.

• Set up mappings to BalticGrid accounts in group.conf file i.e.

"/VO=balticgrid/GROUP=/balticgrid/ROLE=lcgadmin":::sgm:
"/VO=balticgrid/GROUP=/balticgrid"::::

• Additionally you may consider setting BalticGrid central service like e.g. Resource Broker which are:

RB_HOST=grid3.mif.vu.lt
PX_HOST=grid3.mif.vu.lt
WMS_HOST=wms.mif.vu.lt
BDII_HOST=bdii.mif.vu.lt

• Now, you can reconfigure your machines by running

        /opt/lcg/yaim/scripts/configure_node <site-info.def> <machine-type>

New!

• At the last step you have to go to your CE and SE machines and copy BalticGrid VOMS certificate to /etc/grid-security/vomsdir i.e.

cd /etc/grid-security/vomsdir; wget http://voms.balticgrid.org/voms/voms_balticgrid_org.pem
wget http://voms.balticgrid.org/voms/bg-vomscerts-1.3.0-1.noarch.rpm
rpm -hvi bg-vomscerts-1.3.0-1.noarch.rpm

Registering your site with the BalticGrid Resource Broker

In order to be able to receive jobs to your cluster through BG Resource Broker your cluster have to be registered as a valid site. To do that, you send the mail to BalticGrid SA1 mailing list with the following contents:

1. Site name (the value of SITE_NAME variable from site configuration)
2. Site BDII fully qualified domain name (often this shares the host with computing element)
3. The port number the site information service is accessible at (typically "2170")

These three parameters are composed into the GIIS URL:

ldap://<site BDII FQDN>:<port>/mds-vo-name=<site name>,o=grid

The list of all existing sites can be retrieved from

http://voms.balticgrid.org/lcg2-all-sites.conf

 

 

The BalticGrid SA1 mailing list address is: balticgrid-sa1 AT balticgrid DOT org.

After a day or so you will receive an e-mail confirming that your cluster has been added to the list of RB-accepted sites. You can also check by yourself on the current list of sites available in BalticGrid which can be found here.

Appendix:

Manual procedure of setting up the RB in BalticGrid VO scope.

 

If you want to use more than one Resource Broker e.g. one for BalticGrid VO and other RB for others VO, you can set it up manually, although the procedure is not perfect, sorry.

There are two files that need to be edited, first is responsible for Resource Broker and Logging and Bookkeeping service references the latter is for Local Logger destination.

   

Edit /opt/edg/etc/balticgrid/edg_wl_ui.conf to contain:
[
VirtualOrganisation = "balticgrid";
NSAddresses = "grid3.mif.vu.lt:7772";
LBAddresses = "grid3.mif.vu.lt:9000";
MyProxyServer = "voms.balticgrid.org"
]

Edit /opt/edg/etc/edg_wl_ui_cmd_var.conf to set the "LoggingDestination" value to "grid3.mif.vu.lt:9002" i.e.
LoggingDestination = "grid3.mif.vu.lt:9002";

(Don't do that. R.Naujikas)    

    Note: The last action directs all logging to grid3.mif.vu.lt. Consider edg-job-submit with --config option followed by local copy of edg_wl_ui.conf

file.

 

Troubleshooting

BalticGrid users not in /etc/grid-security/grid-mapfile, "peer has no cipher" error. That error indicates the problem with host certificate. Please make sure that:

• Your machine has a valid host certificate installed (is signed by some official CA - EUGridPMA approved)
  
• BalticGrid CA package is installed at the machine (check with: rpm -qa | grep ca_BalticGrid)