1 / 6

Data Management and service discovery

Data Management and service discovery. David Smith JRA1 All Hands Meeting 8 -10 November 2006. Service discovery in DM. Service Discovery used in FTS and Hydra, on the client side FTS within the service Service Discovery not used in lcg_utils or GFAL Seen as most important:

bree
Download Presentation

Data Management and service discovery

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Data Management and service discovery David Smith JRA1 All Hands Meeting 8 -10 November 2006

  2. Service discovery in DM • Service Discovery used in • FTS and Hydra, on the client side • FTS within the service • Service Discovery not used in • lcg_utils or GFAL • Seen as most important: • Any changes in SD should not break what is being using now Data Management Summary

  3. To use SD elsewhere… • To use SD in lcg_utils and GFAL • Currently SD deals the GlueService part of the GLUE Schema • But GFAL also uses other parts, e.g. GlueSE • Possibly: • Add specific methods to SD to allow for the calls GFAL needs • OR • Add the necessary objects: • Eventually cover the whole schema • Question • Is the service discovery just for discovering services or do we want it to approach a general information system interface? Data Management Summary

  4. GFAL Queries • GFAL Queries • Find the SE type of given host • ‘(GlueSEUniqueID=lxb2003.cern.ch)’ GlueSEName • Discover version and endpoint for SE Service of Type SRM for given host. Discover also the VO FQAN that has access to the service • ‘(&(GlueServiceName=StorageElement)(GlueChunkKey=GlueSEUniqueID=lxb2003.cern.ch)(GlueServiceType=srm))’ GlueServiceVersion GlueServiceEndpoint GlueServiceAccessControlRule • Find the SE endpoint for given host • ‘(&(GlueServiceURI=*castorgridsc.cern.ch*)(GlueServiceType=srm_v1))’ GlueServiceURI Data Management Summary

  5. GFAL Queries • Find SE port for host (for classic SE) • ‘(GlueSEUniqueID=lxb2003.cern.ch)’ GlueSEPort • Find SA Root for VO on host • ‘(&(GlueSARoot=LHCB:*)(GlueChunkKey=GlueSEUniqueID=lxb2003.cern.ch))’ GlueSARoot • Find SA Path for VO on host • ‘(&(GlueSALocalID=ATLAS)(GlueChunkKey=GlueSEUniqueID=lxn1183.cern.ch))’ GlueSARoot GlueSAPath • Find SE access protocol for host • ‘(&(ObjectClass=GlueSEAccessProtocol)(GlueChunkKey=GlueSEUniqueID=srm.cern.ch))’ GlueSEAccessProtocolPort Data Management Summary

  6. GFAL Queries • Find CE access point for host (for “file” protocol or for Classic SE) • ‘(GlueCESEBindSEUniqueID=srm.cern.ch)’ GlueCESEBindCEAccessPoint • See: Glue Schema proposal for Storage Element for version 1.3 and Storage Element Model for SRM 2.2 and GLUE schema description Data Management Summary

More Related