Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stage out plugin for xrood on CAF #717

Closed
ericvaandering opened this issue Oct 31, 2013 · 9 comments
Closed

stage out plugin for xrood on CAF #717

ericvaandering opened this issue Oct 31, 2013 · 9 comments
Assignees

Comments

@ericvaandering
Copy link
Member

Original Savannah ticket 83930 reported by fanzago on Mon Jul 4 04:24:04 2011.

CAF has to use the xrootd protocol to read input data and to perfom the stageout of produced files.

It needs to write a new SEAPI plugin for xrootd and some changes in the client.

Changed files

  1. in crab/python:
    cmscp.py
    Scheduler.py
    SchedulerCaf.py
    PhEDExDatasvcInfo.py
    crab_template.py
  2. in ProdCommon/Storage/SEAPI:
    SElement.py
    and added ProtocolXrootd.py

Some notes to use xrootd at caf:

  1. In the SchedulerCaf the "pool" parameter is not more necessary
  2. the setup of the environment is done sourcing the file
    /afs/cern.ch/cms/caf/test.sh in the UI and at WN level
  3. in the PhEDExDatasvcInfo
    *) the forced path is now '/store/eos/user/'
    *) to get the complete endpoint, the query of phedex api has to be done using "stageout" and not "direct" --> root://eoscms//eos/cms/store/eos/user/fanzago/FEDE_TEST_DEL_9/
    *) currently to get the se_path we split the endpoint assuming root://eoscms// is a fixed value
    *) for test up, waiting the update of phedex api, the first part of the endpoint is harcoded
  4. in the protocolXrootd
    *) the command for the copy is xrdcp that needs the complete
    endpoint for the destination file
    *) other command are performed using something similar to:
    xrd eoscms <command> <file>

and currently we are assuming eoscms is the name of remote xrd server (so eoscms is hardcoded)

I don't commit in cvs the code, waiting for the crab_2_7_8_patch2 release.
If you want to test the code, I can provide the patched tgz.

Federica

@ericvaandering
Copy link
Member Author

Comment by belforte on Mon Jul 4 04:24:04 2011

This item has been reassigned from the project CRAB task tracker to your tracker.

The original report is still available at task #21096

Following are the information included in the original report:

It needs to write a new SEAPI plugin for xrootd and some changes in the client.

Changed files

  1. in crab/python:
    cmscp.py
    Scheduler.py
    SchedulerCaf.py
    PhEDExDatasvcInfo.py
    crab_template.py
  2. in ProdCommon/Storage/SEAPI:
    SElement.py
    and added ProtocolXrootd.py
    #######################

Some notes to use xrootd at caf:

  1. In the SchedulerCaf the "pool" parameter is not more necessary
  2. the setup of the environment is done sourcing the file
    /afs/cern.ch/cms/caf/test.sh in the UI and at WN level
  3. in the PhEDExDatasvcInfo
    *) the forced path is now /store/eos/user/
    *) to get the complete endpoint, the query of phedex api has to be done using "stageout" and not "direct" --> root://eoscms//eos/cms/store/eos/user/fanzago/FEDE_TEST_DEL_9/
    *) currently to get the se_path we split the endpoint assuming root://eoscms// is a fixed value
    *) for test up, waiting the update of phedex api, the first part of the endpoint is harcoded
  4. in the protocolXrootd
    *) the command for the copy is xrdcp that needs the complete
    endpoint for the destination file
    *) other command are performed using something similar to:
    xrd eoscms

and currently we are assuming eoscms is the name of remote xrd server (so eoscms is hardcoded)

I don t commit in cvs the code, waiting for the crab_2_7_8_patch2 release.
If you want to test the code, I can provide the patched tgz.

Federica

@ghost ghost assigned fanzago Oct 31, 2013
@ericvaandering
Copy link
Member Author

Comment by fanzago on Mon Jul 4 05:00:35 2011

/afs/cern.ch/user/f/fanzago/public/CRAB_2_7_8_patch2_pre1_XROOTD.tgz

@ericvaandering
Copy link
Member Author

Comment by fanzago on Wed Jul 13 08:24:18 2011

patch installata in afs:

/afs/cern.ch/cms/ccs/wm/scripts/Crab/CRAB_2_7_8_patch1_CAF/

@ericvaandering
Copy link
Member Author

Comment by fanzago on Wed Jul 13 08:28:35 2011

the patch is related only the source of file at WN level, not stageout

@ericvaandering
Copy link
Member Author

Comment by fanzago on Fri Jul 22 11:12:52 2011

The CRAB version to work at CAF with XROOTD protocol also for stageout is prepared and installed at cern for test.

TO use this release you have only to source the file
/afs/cern.ch/cms/ccs/wm/scripts/Crab/CRAB_2_7_8_patch_XROOTD/crab.(c)sh

Warning: to create jobs it is necessary to check the DBS that requieres the user grid proxy.
So before creating jobs you have to create your grid proxy.

@ericvaandering
Copy link
Member Author

Comment by fanzago on Mon Aug 29 05:11:42 2011

Changes to allow the switch between rfio and xrootd protocol.
Committed code in cvs:

  1. in crab/python
    Scheduler.py
    SchedulerLocal.py
    SchedulerCAF.py
    cmscp.py
    PhEDExDatasvcInfo.py

  2. in prodcommon/Storage/SEAPI
    SElement.py
    ProtocolRfio.py
    ProtocolXrootd.py

Please test the code

@ericvaandering
Copy link
Member Author

Comment by fanzago on Mon Aug 29 05:19:58 2011

In the crab.cfg in the section [USER] the parameter caf_lfn has to be added.
This parameter allows to select the first part of LFN, needed to query the PhEDEx api.

The default value is /store/caf/user.
The value to test eos area is

caf_lfn = /store/eos/user

The endpoint returned by the query contains the protocol (rfio or xrootd at caf) for the output copy.

@ericvaandering
Copy link
Member Author

Comment by fanzago on Mon Aug 29 05:33:22 2011

Updated crab/python
full_crab.cfg
crab_help.cfg

adding the caf_lfn parameter in [USER]

@ericvaandering
Copy link
Member Author

Closed by belforte on Tue Nov 1 18:49:20 2011

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants