Agreement Signalling for Resource Reservation

1. Agreement Signalling for Resource Reservation Work Package 4 Work Package 4 Agreement Signalling for Resource Reservation

2. Service Level Agreement (SLA) signalling for reservation of different types of resource: Instrument exclusive access to instrument partitions Data storage reservation of space prior to execution of jobs (output files) and transfer of large amounts of data Computing  timely execution of high-priority jobs Network resources (e.g. bandwidth)  guaranteed data throughput on shared paths Agreement Service (AS): Based on WS-Agreement specification from the GGF [WSAG] Signalling protocol independent from content of a SLA request Standard “agreement offer” structure (XML schema) Development in the framework of a EGEE-GRIDCC collaboration Fully integrated with the gLite Workload Management System (integration work is currently ongoing) [WSAG] The Grid Resource Allocation and Agreement Protocol Working Group; Global Grid Forum (https://forge.gridforum.org/projects/graap-wg) SLA Signalling Work Package 4 Agreement Signalling for Resource Reservation

3. Instrument/partition reservation: whole IE - all partitions (accept guaranteed lease only) partition(s) by ID (accept guaranteed lease only) partition(s) by type (number of partitions, type of partition needed) partition(s) by metric (number of partitions, level of quality for specific metric) Get information on partitions and reservations: Reservations in place (attributes and status) Partitions (ID, Type) Get accounting information on instrument/partition usage Instrument reservation:IE operations Work Package 4 Agreement Signalling for Resource Reservation

4. Agreementoffer: the “description” of the requested reservation, including the reservation attributes, standard XML structure AgreementInitiator: the entity responsible of triggering the SLA signalling protocol (WMS, data scheduler, user, etc) Agreement Responder  Agreement Service checks compliance of the offer to some internal templates capable of interacting with multiple resource service providers and the related interfaces (e.g. the Instrument Element, StoRM for storage space – SRM 2.1 interface, etc.) Service Consumer: the entity making use of the reserved resources Service Provider: the entity responsible of enforcing a reservation according to resource-specific mechanisms Terminology Work Package 4 Agreement Signalling for Resource Reservation

5. Functionality: Interacts with one or more service providers Translateshigh-level service description terms (from initiator) to low level service-specific terms Advertises the Service Provider capabilities through agreement templates. The template is an XML document that describes the contract skeleton. Handles the agreement negotiation (agreement offer attributes from the initiator are tuned during the negotiation phase) Provides information about: status of the agreement negotiation process and attributes of a specific agreement instance Benefits: It hides the complexity of the service providers’ interfaces from the agreement initiator (the client). It exposes a single operation which can be used independently of the nature of the agreement type (createAgreement). Scalability: new Service Providers can be easily integrated by advertising the corresponding templates (clients can be notified when new templates are added). No need of a-priori knowledge about services available to users. Agreement Service Work Package 4 Agreement Signalling for Resource Reservation

6. Agreement Service for storage space reservation The Agreement Service is a space storage Agreement Responder: • In C++ • gSoap 2.7.0  gSoap 2.7.6b • storage space service provider interface: • Storage Resource Management (SRM) v. 2.1 (Grid Resource Management WG, GGF) [SRM] • Operations: • createAgreement()  srmReserveSpace() • agreementKill() • agreementUpdate() • getAgreementStatus() • getAgreementProperties() [SRM] Grid Storage Management WG; GGF (https://forge.gridforum.org/projects/gsm-wg/) Work Package 4 Agreement Signalling for Resource Reservation

7. Name Context Terms Service Description Terms Guarantee Terms Agreement Offer for storage space reservation (1/2) <ns3:Terms xsi:type="ns3:TermCompositorType"> <ns3:All xsi:type="ns3:TermCompositorType"> <ns3:ServiceDescriptionTerm xsi:type="ns3:ServiceDescriptionTermType" ns3:ServiceName="spaceManagement:resourceType"> <ns3:-type xsi:type="xsd:string">StorageElement</ns3:-type> </ns3:ServiceDescriptionTerm> <ns3:ServiceDescriptionTerm xsi:type="ns3:ServiceDescriptionTermType" ns3:ServiceName="spaceManagement:serviceProviderURI"> <ns3:-type xsi:type="ns2:AttributedURI"> http://ladyoscar.cnaf.infn.it/<path> </ns3:-type> </ns3:ServiceDescriptionTerm> <ns3:ServiceDescriptionTerm xsi:type="ns3:ServiceDescriptionTermType" ns3:ServiceName="spaceManagement:serviceProviderURI"> <ns3:-type xsi:type="ns2:AttributedURI"> http://testbed006.cnaf.infn.it/<path> </ns3:-type> </ns3:ServiceDescriptionTerm> Agreement Work Package 4 Agreement Signalling for Resource Reservation

8. <ns3:ServiceDescriptionTerm xsi:type="ns3:ServiceDescriptionTermType" ns3:ServiceName="spaceManagement:duration"> <ns3:-type xsi:type="xsd:int">2000</ns3:-type> </ns3:ServiceDescriptionTerm> <ns3:ServiceDescriptionTerm xsi:type="ns3:ServiceDescriptionTermType" ns3:ServiceName="spaceManagement:typeOfSpace"> <ns3:-type xsi:type="xsd:string">durable</ns3:-type> </ns3:ServiceDescriptionTerm> <ns3:ServiceDescriptionTerm xsi:type="ns3:ServiceDescriptionTermType" ns3:ServiceName="spaceManagement:sizeOfTotalSpaceDesiredInBytes"> <ns3:-type xsi:type="xsd:int">2000000</ns3:-type> </ns3:ServiceDescriptionTerm> <ns3:ServiceDescriptionTerm xsi:type="ns3:ServiceDescriptionTermType" ns3:ServiceName="spaceManagement:sizeOfGuaranteedSpaceDesiredInBytes"> <ns3:-type xsi:type="xsd:int">100000000</ns3:-type> </ns3:ServiceDescriptionTerm> </ns3:All> </ns3:Terms> Agreement Offer for storage space reservation (2/2) Work Package 4 Agreement Signalling for Resource Reservation

9. StoRM: space reservation • based on GPFS File System features for pre-allocation • space created identified by a token (i.e., reservation handle) • for every srmPrepareToPut call and a certain space handler, the space previously created is partitioned to the desired size and an endpoint to a file with desired amount of pre-allocated blocks is returned • gpfs_prealloc( ) subroutine for storage space allocation • “The gpfs_prealloc( ) function is used to preallocate disk storage for a file that has already been opened, prior to writing data to the file.” [StoRM] “StoRM: grid middleware for disk resource management”; in Proc. of the Conference on Computing in High Energy and Nuclear Physics (CHE0P 2004), Interlaken, CH, Sep 2004, Vol. 2, pp. 1238-1242 Work Package 4 Agreement Signalling for Resource Reservation

10. Demo setup INFN LNL / Legnaro Agreement Service Initiator (gridcc01.lnl.infn.it) gLite WMS createAgreement() Agreement offer (3) INFN CNAF / Bologna (1) Reservation handle Storage Space Reservation Agreement Service (gridcc02.lnl.infn.it) StoRM backend - SRM interface v.2.1 - (ladyoscar.cnaf.infn.it) (2) srmReserveSpace() Work Package 4 Agreement Signalling for Resource Reservation

11. Demo (1/4) Work Package 4 Agreement Signalling for Resource Reservation

12. Demo (2/4) Work Package 4 Agreement Signalling for Resource Reservation

13. Demo (3/4) Work Package 4 Agreement Signalling for Resource Reservation

14. Demo (4/4) Work Package 4 Agreement Signalling for Resource Reservation