BeStMan-gateway Installation and Configuration for OSG Tier-2, Tier-3 sites

Transcription

1 BeStMan-gateway Installation and Configuration for OSG Tier-2, Tier-3 sites (draft) T. Levshina Introduction OSG Storage VDT group has been asked to provide a full support of BeStMan-gateway storage solution. This goal has been set by OSG for the year 3 ( fiscal year). This document is written for system administrators who are planning to use storage that is installed on top of any Posix file system. The goal of this document is to give enough information for system administrators to do initial simple configuration of the storage as well as provide references to the documents that may help to accomplish more sophisticated configuration. Proposed Architecture BeStMan-gateway storage consists of the following components: BeStMan-gateway is a partial implementation of SRM v2.2, developed by LBNL, for disk based storage systems maintenance ( ) GridFTP server provides a high-performance, secure, reliable data transfer ( ) POSIX-compliant FS

2 Configuration decisions The following questions should be answered before you can proceed with installation and configuration of BeStMan-gateway storage solution: Q. How many nodes could be used for storage? The absolute minimum number of nodes is 1: Usually one would prefer to separate GridFtp from BeStMan for better performance. Also, you may want to have multiple GridFtp server. The decision should be based on your load and storage requirements. Q. What authorization mechanism do you prefer? You have to decide if you want to use grid-map-file or GUMS server for users authentication and authorization. More details about GUMS could be found at nagegums Q. Do you need to support space tokens? BeStMan-gateway supports predefined, static space tokens that should be included in configuration. It doesn't keep trace or enforce static space tokens. If you want partition your storage space and have a designated space for some VOs or users you can choose to use space tokens. You will have to decide the names and descriptions of the tokens as well as the size of the area. BeStMan-gateway BeStMan-gateway is a generic SRM v2.2 load balancing frontend for GridFTP servers. It is developed by the Scientific Data Management Group of Lawrence Berkeley National Laboratory. It implements a subset of SRM v2.2 specifications that includes: srmping() srmgettransferprotocols() srmls() srmrm() srmmkdir() srmrmdir() srmpreparetoput() srmpreparetoget() srmputdone() srmreleasefiles() srmgetspacetokens()

3 srmgetspacemetadata() Some of the abovementioned specs are just partially implemented. For more information see BeStMan can be installed from VDT cache. cd $INSTALLATION_DIR/ vdt pacman -get bestman You will need to configure BeStMan to enable gateway-mode. You have to decide if you would like to use static space token reservation, and in this case to come up with a list of token names, description and size of space allocated for each token. Keep in mind that in gateway-mode BeStMan is not managing your space. The example below shows how to configure BeStMan in gateway-mode, enable gums and space token usage: $VDT_LOCATION/vdt/setup/configure_bestman --server y \ --user <user> \ --cert <service_cert> \ --key <service_key> \ --http-port <public_port> \ --https-port <secured_port> \ --gums-host <GUMS hostname> \ --gums-port <GUMS port number> \ --gums-dn <Client DN for GUMS interface> \ --enable-gateway \ --with-tokens-list "<TOKEN_1_NAME>[desc:<TOKEN_1_DESC>][<TOKEN_1_SIZE_GB>];< TOKEN_2_NAME>[desc:<TOKEN_2_DESC>][<TOKEN_2_SIZE>]" \ --with-transfer-servers <GridFTP server list> \ Where user name of the non-privileged user that runs BeStMan, GRIDFtp server list is a list FQDN of your GridFtp servers, separated by ;. e.g. gsiftp://host1.domain.tld;gsiftp://host2.domain.tld GUMS hostname the name of GUMS server, GUMS port number the port of GUMS server, Client DN for GUMS interface is a service certificate subject. If you want to use grid-map-file for user authentication and authorization do not specify the following options: --gums-host --gums-port --gums-dn

4 If you do not want to use statically reserved space tokens do not specify the following options: --with-tokens-list If you would like to run BeStMan on the Please, make the appropriate modification to /etc/sudoers described in BeStMan documentation, namely add the following lines to this file: Cmnd_Alias SRM_CMD = /bin/rm, /bin/mkdir, /bin/rmdir, /bin/mv, /bin/ls Runas_Alias SRM_USR = ALL,!root <user_name> ALL=(SRM_USR) NOPASSWD: SRM_CMD If you are running your BeStMan-gateway on the node that doesn t have an access to your FS, you will have to create the corresponding root directory that should be owned by user you have specified while configuring BeStMan-gateway, and you will have to modify the following attributes in $VDT_LOCATION/bestman/config/bestman.rc configuration file: checksizewithfs=false checksizewithgsiftp=true GridFtp GridFtp server comes with BeStMan installation. If you want to install stand alone GridFTP server you will need to install the following packages from VDT: cd $INSTALLATION_DIR mkdir vdt cd vdt pacman -get pacman -get If you want to use the grid-map-file for user authentication and authorization ignore the rest of this section. If you want to use GUMS for user authorization you will need to install PRIMA package from VDT cd $INSTALLATION_DIR/ vdt export VDT_GUMS_HOST=<GUMS hostname> pacman -get Where GUMS hostname is a GUMS server and VDT_LOCATION is root directory of VDT installation. Then copy two files from $VDT_LOCATION/post-install to in /etc/grid-security: cp $VDT_LOCATION/post-install/prima-authz.conf /etc/grid-security cp $VDT_LOCATION/post-install/gsi-authz.conf /etc/grid-security

5 You can have multiple installation of GridFtp servers located on the nodes you have specified in BeStMan-gateway configuration. You will need to make sure that users have write permission in to the storage area. Start the system You have to be root to start each service. You have to start all the components in the following order (this is order is optional but seems logical): 1. Start BeStMan. Login on BeStMan node, then: cd <VDT_LOCATION> vdt-control on bestman 2. Start GridFtp servers. Login on each GridFtp server node, then: cd <VDT_LOCATION> vdt-control on gridftp Stop the system You have to be root to stop each service. You have to stop all the components in the following order (this is order is optional but seems logical): 1. Stop BeStMan. Login on BeStMan node, then: cd <VDT_LOCATION> vdt-control off 2. Stop GridFtp servers. Login on each GridFtp server node, then: cd <VDT_LOCATION> vdt-control off gridftp System sanity check In order to verify that the system is functional you will need to download VDT-client package: cd $INSTALLATION_DIR mkdir vdt_client cd vdt_client pacman pacman -get You will need to get your voms-proxy certificate: voms-proxy-init voms <voname>:/<voname>

6 Execute srm-ping: srm-ping srm://<bestman_host>:8443/srm/v2/server Expected results: ########################################### SRM_HOME is /usr/local/osg-client/srm-client-lbnl JAVA_HOME is /usr/local/osg-client/jdk1.5 X509_CERT_DIR = /usr/local/osg-client/globus/trusted_ca GSI_DAEMON_TRUSTED_CA_DIR = /usr/local/osg-client/globus/trusted_ca ########################################### SRM-CLIENT: got remote srm object SRM-PING: Thu Sep 18 11:55:50 CDT 2008 Calling SrmPing Request... Ping versioninfo=v2.2 Extra information Key=backend_type Value=BeStMan Key=backend_version Value= Key=GatewayMode Value=Enabled Key=gsiftpTxfServers Value=gsiftp://osg-ress-2.fnal.gov Key=clientDN Value=/DC=org/DC=doegrids/OU=People/CN=Tanya Levshina Key=localIDMapped Value=fnalgrid Key=staticToken(0) Value=DISK1 desc=data1 size= Key=staticToken(1) Value=DISK2 desc=data2 size= If you have reasonable result you may try to srm copy. In order to do so create a file test1 in /tmp directory and execute: srm-copy file:////tmp/test1 srm://<bestman_host>.gov:8443/srm/v2/server\?sfn=<fs_root_dir>/test1 - spacetoken <TOKEN_1_NAME> You should get back something like that: srm-copy file:////tmp/test1_1 srm://fapl118.fnal.gov:8443/srm/v2/server\?sfn=/home/tlevshin/cache/tes t_4 -spacetoken DISK1 ########################################### SRM_HOME is /usr/local/vdt_client/srm-client-lbnl JAVA_HOME is /usr/local/vdt_client/jdk1.5 X509_CERT_DIR = /etc/grid-security/certificates GSI_DAEMON_TRUSTED_CA_DIR = /etc/grid-security/certificates ########################################### SRM-CLIENT: Mon Nov 03 11:32:03 CST 2008 Connecting to httpg://fapl118.fnal.gov:8443/srm/v2/server

7 SRM-CLIENT: Mon Nov 03 11:32:04 CST 2008 Calling SrmPrepareToPutRequest now... request.token=put:5 status=srm_success explanation=null SRM-CLIENT: RequestFileStatus for SURL=file:////tmp/test1_1 is Ready. SRM-CLIENT: received TURL=gsiftp://fg0x5.fnal.gov//home/tlevshin/cache/test_4 >>>Total Memory= >>>Free Memory= >>>Memory in use= SRM-CLIENT: Mon Nov 03 11:32:08 CST 2008 start file transfer. SRM-CLIENT:Source=file:////tmp/test1_1 SRM-CLIENT:Target=gsiftp://fg0x5.fnal.gov//home/tlevshin/cache/test_4 SRM-CLIENT: Mon Nov 03 11:32:10 CST 2008 end file transfer. SRM-CLIENT: Mon Nov 03 11:32:10 CST 2008 Calling putdone for srm://fapl118.fnal.gov:8443/srm/v2/server?sfn=/home/tlevshin/cache/test _4 SRM-CLIENT: Mon Nov 03 11:32:18 CST 2008 end file transfer. SRM-CLIENT: Mon Nov 03 11:32:18 CST 2008 end file transfer. SRM-CLIENT: Request completed with success SRM-CLIENT: Printing text report now... SRM-CLIENT*REQUESTTYPE=put SRM-CLIENT*TOTALFILES=1 SRM-CLIENT*TOTAL_SUCCESS=1 SRM-CLIENT*TOTAL_FAILED=0 SRM-CLIENT*REQUEST_TOKEN=put:5 SRM-CLIENT*REQUEST_STATUS=SRM_SUCCESS SRM-CLIENT*SOURCEURL[0]=file:////tmp/test1_1 SRM- CLIENT*TARGETURL[0]=srm://fapl118.fnal.gov:8443/srm/v2/server?SFN=/home /tlevshin/cache/test_4 SRM- CLIENT*TRANSFERURL[0]=gsiftp://fg0x5.fnal.gov//home/tlevshin/cache/test _4 SRM-CLIENT*ACTUALSIZE[0]=16 SRM-CLIENT*FILE_STATUS[0]=SRM_SUCCESS SRM-CLIENT*EXPLANATION[0]=SRM-CLIENT: PutDone is called successfully ExitCode=0 Log file and configuration locations

8 If any of the tests described above have failed or you are just curious to see what s going on you could find log and configuration files for each of the module in the following location on a relevant node: Module Configuration files Log files Name BeStMan $VDT_LOCATION/bestman/conf/bestman.rc $VDT_LOCATION/vdt-appdata/betsman/logs/event.srm.log GridFtp $VDT_LOCATION/services/vdt-run-gsiftp.sh.env $VDT_LOCATION/globus/var/log/gridftp.log $VDT_LOCATION/globus/var/log/gridftp-auth.log Looking for help? The detailed information about each component can found on the following web sites: BeStMan - GridFTP - The information related to current VDT cache, installation and confirmation is at Numerous documents about storage solutions supported by OSG as well as other useful links could be found at See if your question is already answered under the FAQ section If not, please send all your questions to osg-storage@opensciencegrid.org Acknowledgments Many thanks to the following people who have helped to understand the configuration and installation procedure and BeStMan-gateway inclusion in VDT: Alain Roy (OSG Software coordinator) Scot Kronenfeld (VDT team member) Alex Sim and Junmin Gu - BeStMan developers