The SNARL Service: Standards-based Naming for Accessing Resources in an LFC
description
Transcript of The SNARL Service: Standards-based Naming for Accessing Resources in an LFC
![Page 1: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/1.jpg)
Karolina SarnowskaCERN Openlab Summer Program 2008
![Page 2: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/2.jpg)
Introduction and Background
SNARL Development
Conclusion
2
![Page 3: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/3.jpg)
Interoperability, Grid Standards, and SNARL
3
![Page 4: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/4.jpg)
4
![Page 5: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/5.jpg)
Community of users, developers, and vendors
Leading global standardization effort
Efforts strive to accelerate grid adoption
5
![Page 6: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/6.jpg)
Need means of accessing resources
What’s in a name? human-readable refers to specific resource
6
![Page 7: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/7.jpg)
Describes standard way of mapping names to grid endpoints
RNS 1.0 Operations: Add List Remove Query Update
7
![Page 8: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/8.jpg)
Handles: Convey information needed to address Web service endpoint
<Address> <Reference Parameters> <Metadata>
<Security Context>
8
![Page 9: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/9.jpg)
SRM srmLs srmMkdir srmPrepareToPut srmRm srmMv
RNS add list remove query update
9
![Page 10: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/10.jpg)
Catalog of data files on storage elements
Each logical file entry can correspond to multiple physical files (replicas)
Provides mapping between logical file names and storage URLs
10
![Page 11: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/11.jpg)
Standards-based Naming for Accessing Resources in an LFC
RNS implementation for LFCs
11
SNARLService
(1) RNS Requests
(3) RNS Resonses
LFC/grid /atlas /alice /cms /dteamGrid
Client (2) LFC API Calls
SESE
SE
![Page 12: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/12.jpg)
Creating an RNS compliant web service with Axis2/C
12
![Page 13: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/13.jpg)
1. Setup web services framework with Axis2/C
2. Create RNS compliant service with WSDL2C
3. Implement RNS operations with LFC API calls
4. Create clients for (interoperability) testing
13
![Page 14: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/14.jpg)
Web services engine implemented in C
Handles SOAP message processing
Built-in support includes: WS-Addressing WS-Policy WS-SecurityPolicy
14
![Page 15: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/15.jpg)
1. Specify RNS compliant web service in WSDL
2. Use WSDL2C tool to generate web service skeleton in C
15
![Page 16: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/16.jpg)
Need to map RNS operation to LFC API calls Add List Remove Query Update
Naming dilemma: should replicas appear in namespace?
16
![Page 17: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/17.jpg)
17
SNARLService
(1) RNS List
(3) EPR
LFC•lfn: /grid/foo
GridClient
(2) LFC API Calls
SE•fooReplicaA
SE•fooReplicaB
![Page 18: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/18.jpg)
If new logical file name: lfc_creatg
If new replica: lfc_addreplica(name specified by storage URL)
18
![Page 19: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/19.jpg)
REQUEST: specify name of new entry
<soap:Envelopexmlns:soap=‘http://www.w3.org/2003/soap-envelope’xmlns:wsa=‘http://www.w3.org/2005/03/addressing’><soap:Header> <wsa:Action> http://schemas.ggf.org/rns/2006/03/rns/add </wsa:Action></soap:Header>
<soap:Body> <rns:add xmlns:rns=‘http://schemas.ggf.org/rns/2006/05/rns’>
<rns:entry_name> /grid/foo </rns:entry_name> </rns:add>
</soap:Body></soap:Envelope>
19
![Page 20: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/20.jpg)
RESPONSE: EPR of newly created entry <soap:Envelope
xmlns:soap=‘http://www.w3.org/2003/soap-envelope’xmlns:wsa=‘http://www.w3.org/2005/03/addressing’><soap:Header> <wsa:Action> http://schemas.ggf.org/rns/2006/03/rns/add Response </wsa:Action></soap:Header>
<soap:Body> <rns:addResponse xmlns:rns=‘http://schemas.ggf.org/rns/2006/05/rns’>
<rns:entry_reference> <wsa:Address> http://pcitgd02.cern.ch:9090/axis2/services/snarl
</wsa:/Address> <wsa:ReferenceParameters> /grid/foo </wsa:ReferenceParameters> </rns:entry_reference>
</rns:addResponse> </soap:Body></soap:Envelope>
20
![Page 21: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/21.jpg)
Genesis IIGenesis II
21
(3) RNS Resonse
LFC/grid /atlas /alice /cms /dteam
GridClient
(2) LFC API Calls
SESE
SE
(1) RNS Request
SNARLService
![Page 22: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/22.jpg)
22
![Page 23: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/23.jpg)
Add security contextUpdate for RNS 2.0Add ByteIO implementation for data accessExplore use as interface between LFC and
other tools
23
![Page 24: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/24.jpg)
Implementation of RNS specification for existing grid system is possible
Interoperability using RNS specification is achievable
RNS operations are very basic
24
![Page 25: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/25.jpg)
Akos FrohnerErwin LaureDM TeamAndrew GrimshawMark Morgan
25
![Page 26: The SNARL Service: Standards-based Naming for Accessing Resources in an LFC](https://reader033.fdocuments.us/reader033/viewer/2022042822/56813afd550346895da392de/html5/thumbnails/26.jpg)
1. "Open Grid Forum," http://www.ogf.org.2. M. Pereira, O. Tatebe, L. Luan, and T. Anderson, "Resource
Namespace Service Specification," https://forge.gridforum.org/sf/docman/do/downloadDocument/projects.gfswg/docman.root.working_drafts/doc8272/5, World Wide Web Consortium, 2006.
3. M. M. Morgan and A. S. Grimshaw, "Genesis II – Standards Based Grid Computing," Seventh IEEE International Symposium on Cluster Computing and the Grid, 2007.
4. “Apache Axis2/C,” http://ws.apache.org/axis2c
26