Difference between revisions of "HOWTO12 Globus Online cookbook for EGI VOs"
Line 1: | Line 1: | ||
<p><br /> | |||
</p> | |||
<table align="right"> | |||
<tr> | |||
<td> __TOC__ | |||
</td></tr></table> | |||
<h2> About </h2> | |||
<p>This page provides guidance for Virtual Organisations (VO) of the European Grid Infrastructure (EGI) on how to use the Globus Online service that is available at http://www.globusonline.eu. The services provides robust and easy to use file transfer capabilities for EGI users. Globus Online manages file transfers for you, monitoring performance, retrying failures, auto-tuning and recovering from faults automatically where possible, and reporting status. The Cookbook demonstrates how SRM storages of EGI could be used as endpoints for file transfers in Globus Online. | |||
</p><p>The Cookbook consists of two parts: | |||
</p> | |||
<ul><li> The first part provides step-by-step instructions for VO Managers on how to register SRM storage services in Globus Online in such a way, that these appear as endpoints that VO members can find and use for file tranfers. Although these steps could be performed by any member of a VO, we assume that for most VOs the VO Manager is the most suitable person to complete the steps, because the VO Managers have sufficient knowledge on storage sites of the VO and about using the BDII information system to obtain detailed information about these storages. | |||
</li></ul> | |||
<ul><li> The second part provides step-by-step instructions for VO members on how to use storage endpoints in Globus Online. These steps can be carried out by any VO member. | |||
</li></ul> | |||
<p>The "biomed" VO is used as an example in the Cookbook to demonstrate Globus Online usage. | |||
</p><p><b>Please email any feedback about this Cookbook to the EGI.eu User Community Support Team: ucst@egi.eu.</b> | |||
</p><p><b>ATTENTION</b>: in the examples we use Glue v1.3 and Glue 2.0. Currently there several discussions ongoing about what storage managers must publish to information system and make easier way of querying the information. REF: https://ggus.eu/tech/ticket_show.php?ticket=94264 | |||
</p> | |||
<h2> VO Managers </h2> | |||
<p>1. Get all storage managers (Glue 2.0): | |||
</p> | |||
<pre> | <pre> | ||
-bash-3.2$ ldapsearch -x -h lcg-bdii.cern.ch -p 2170 -b o=glue '(&(objectclass=GLUE2StorageService))' |perl -p00e 's/\r?\n //g'|grep ^dn:|cut -d | -bash-3.2$ ldapsearch -x -h lcg-bdii.cern.ch -p 2170 -b o=glue '(&(objectclass=GLUE2StorageService))' |perl -p00e 's/\r?\n //g'|grep ^dn:|cut -d" " -f2 > GLUE2StorageServiceDN | ||
</pre> | </pre> | ||
<p>2. Filter out only storage managers for your VO (Glue 2.0): | |||
2. Filter out only storage managers for your VO (Glue 2.0): | </p> | ||
<pre> | <pre> | ||
-bash-3.2$ for i in `cat GLUE2StorageServiceDN`;do ldapsearch -LLL -x -H ldap://lcg-bdii.cern.ch:2170 -x -b | -bash-3.2$ for i in `cat GLUE2StorageServiceDN`;do ldapsearch -LLL -x -H ldap://lcg-bdii.cern.ch:2170 -x -b "$i" "(&(objectClass=GLUE2AccessPolicy)(GLUE2PolicyRule=*:biomed))" GLUE2PolicyRule| grep -q GLUE2PolicyRule && echo $i;done > GLUE2AccessPolicyDN | ||
</pre> | </pre> | ||
<p><br /> | |||
3. Get all GridFTP endpoints for your VO (Glue 2.0): | 3. Get all GridFTP endpoints for your VO (Glue 2.0): | ||
</p> | |||
<pre> | <pre> | ||
-bash-3.2$ for i in `cat GLUE2AccessPolicyDN`; do ldapsearch -LLL -x -H ldap://lcg-bdii.cern.ch:2170 -x -b | -bash-3.2$ for i in `cat GLUE2AccessPolicyDN`; do ldapsearch -LLL -x -H ldap://lcg-bdii.cern.ch:2170 -x -b "$i" "(&(objectClass=GLUE2Endpoint)(GLUE2EndpointInterfaceName=gsiftp))" GLUE2EndpointURL | grep ^GLUE |tail -n 1;done | ||
GLUE2EndpointURL: gsiftp://gaeds023.ciemat.es:2811 | GLUE2EndpointURL: gsiftp://gaeds023.ciemat.es:2811 | ||
GLUE2EndpointURL: gsiftp://se001.ipp.acad.bg:2811 | GLUE2EndpointURL: gsiftp://se001.ipp.acad.bg:2811 | ||
GLUE2EndpointURL: gsiftp://juliet.zih.tu-dresden.de:2811 | GLUE2EndpointURL: gsiftp://juliet.zih.tu-dresden.de:2811 | ||
GLUE2EndpointURL: gsiftp://sedsk58.grid.hep.ph.ic.ac.uk:2811 | GLUE2EndpointURL: gsiftp://sedsk58.grid.hep.ph.ic.ac.uk:2811 | ||
</pre> | </pre> | ||
5. Go to http://www.globusonline.eu/ | 5. Go to http://www.globusonline.eu/ | ||
Line 193: | Line 178: | ||
== Additional materials == | == Additional materials == | ||
Tests have been carried out while creating this Cookbook: [[GO_testing]] | Tests have been carried out while creating this Cookbook: [[GO_testing]]--> | ||
</p><a _fcknotitle="true" href="Category:Community_Engagement">Community_Engagement</a> |
Revision as of 11:17, 23 May 2013
About
This page provides guidance for Virtual Organisations (VO) of the European Grid Infrastructure (EGI) on how to use the Globus Online service that is available at http://www.globusonline.eu. The services provides robust and easy to use file transfer capabilities for EGI users. Globus Online manages file transfers for you, monitoring performance, retrying failures, auto-tuning and recovering from faults automatically where possible, and reporting status. The Cookbook demonstrates how SRM storages of EGI could be used as endpoints for file transfers in Globus Online.
The Cookbook consists of two parts:
- The first part provides step-by-step instructions for VO Managers on how to register SRM storage services in Globus Online in such a way, that these appear as endpoints that VO members can find and use for file tranfers. Although these steps could be performed by any member of a VO, we assume that for most VOs the VO Manager is the most suitable person to complete the steps, because the VO Managers have sufficient knowledge on storage sites of the VO and about using the BDII information system to obtain detailed information about these storages.
- The second part provides step-by-step instructions for VO members on how to use storage endpoints in Globus Online. These steps can be carried out by any VO member.
The "biomed" VO is used as an example in the Cookbook to demonstrate Globus Online usage.
Please email any feedback about this Cookbook to the EGI.eu User Community Support Team: ucst@egi.eu.
ATTENTION: in the examples we use Glue v1.3 and Glue 2.0. Currently there several discussions ongoing about what storage managers must publish to information system and make easier way of querying the information. REF: https://ggus.eu/tech/ticket_show.php?ticket=94264
VO Managers
1. Get all storage managers (Glue 2.0):
-bash-3.2$ ldapsearch -x -h lcg-bdii.cern.ch -p 2170 -b o=glue '(&(objectclass=GLUE2StorageService))' |perl -p00e 's/\r?\n //g'|grep ^dn:|cut -d" " -f2 > GLUE2StorageServiceDN
2. Filter out only storage managers for your VO (Glue 2.0):
-bash-3.2$ for i in `cat GLUE2StorageServiceDN`;do ldapsearch -LLL -x -H ldap://lcg-bdii.cern.ch:2170 -x -b "$i" "(&(objectClass=GLUE2AccessPolicy)(GLUE2PolicyRule=*:biomed))" GLUE2PolicyRule| grep -q GLUE2PolicyRule && echo $i;done > GLUE2AccessPolicyDN
3. Get all GridFTP endpoints for your VO (Glue 2.0):
-bash-3.2$ for i in `cat GLUE2AccessPolicyDN`; do ldapsearch -LLL -x -H ldap://lcg-bdii.cern.ch:2170 -x -b "$i" "(&(objectClass=GLUE2Endpoint)(GLUE2EndpointInterfaceName=gsiftp))" GLUE2EndpointURL | grep ^GLUE |tail -n 1;done GLUE2EndpointURL: gsiftp://gaeds023.ciemat.es:2811 GLUE2EndpointURL: gsiftp://se001.ipp.acad.bg:2811 GLUE2EndpointURL: gsiftp://juliet.zih.tu-dresden.de:2811 GLUE2EndpointURL: gsiftp://sedsk58.grid.hep.ph.ic.ac.uk:2811
5. Go to http://www.globusonline.eu/
a) Create an account with your VO name e.g. lsgrid. (Note that usernames can include only letters and numbers. The name of your VO may need to be altered!)
b) Go to "Manage Endpoints" and click "Add Endpoint".
c) Filling the endpoint details:
Name lsgrid# < enter name of the Storage > (e.g. SARA) Short Description: < enter description > (add VO default path for this storage, e.g. /pnfs/grid.sara.nl/data/lsgrid/) Server Address gsiftp:// < storage hostname with GridFTP access > (e.g. wasp9.grid.sara.nl) Visible To: Anyone (public) Set the Identity Provider to be used with this endpoint. Type: MyProxy MyProxy Hostname: < myproxy server for your VO > (e.g. px.grid.sara.nl)
VO Members
Commands are performed from the command line of a gLite User Interface (UI). The "lsgrid" VO is used as an example.
1. Generating credentials.
Generate VOMS proxy:
-bash-3.2$ voms-proxy-init --voms lsgrid Enter GRID pass phrase: Your identity: /O=dutchgrid/O=users/O=egi/CN=Karolis Eigelis Creating temporary proxy .............................................................................................................. Done Contacting voms.hellasgrid.gr:15004 [/C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr] "lsgrid" Done Creating proxy ............................................................ Done Your proxy is valid until Fri Nov 2 02:16:10 2012
Upload VOMS proxy to MyProxy.
-bash-3.2$ myproxy-init --voms lsgrid Enter GRID pass phrase: Your identity: /O=dutchgrid/O=users/O=egi/CN=Karolis Eigelis Creating temporary proxy ............................. Done Contacting voms.hellasgrid.gr:15004 [/C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr] "lsgrid" Done Creating proxy ........................................... Done Your proxy is valid until Thu Nov 8 14:17:47 2012 verify OK Enter MyProxy pass phrase: Verifying - Enter MyProxy pass phrase: A proxy valid for 168 hours (7.0 days) for user karolise now exists on px.grid.sara.nl.
2. Go to to http://www.globusonline.eu/
a) Create account for yourself
b) Go to "Manage Endpoints" and click "View All".
c) Search for your VO name e.g. lsgrid
You could see something like:
lsgrid#SARA activate
d) Click on "activate"
Fill in the details for your credentials to retrieve.
MyProxy Server: < myproxy server you have credentials at > (e.g. px.grid.sara.nl) Username: < your user on a myproxy machine > (e.g. karolise) Passphrase: < you chosen password > (e.g. You used to Enter MyProxy pass phrase in step 1.)
e) Click "Authenticate"
f) Go to "Start Transfer"
Choose your endpoint which is: lsgrid#SARA
Look for your VO path directory in the endpoint description: /pnfs/grid.sara.nl/data/lsgrid/
That is it. Now using Globus Online you can access Storage Element in EGI which is used also by SRM and FTS.
What you can do ?
- Transfer files from your laptop using GlobusConnect client to SRM storage endpoint in EGI using GO.
- Transfer files from SRM endpoint in EGI using GO to your laptop using GlobusConnect client.
- Transfer files from one SRM endpoint in EGI to another SRM endpoint in EGI or to any other Infrastructure using GO and receive nice notifications by email
Additional materials
Tests have been carried out while creating this Cookbook: GO_testing-->
<a _fcknotitle="true" href="Category:Community_Engagement">Community_Engagement</a>