1. www.gridforum.org GESA: Grid Economic Services Architecture Steven Newhouse (s.newhouse@doc.ic.ac.uk)s.newhouse@doc.ic.ac.uk Jon MacLaren (jon.maclaren@man.ac.uk)jon.maclaren@man.ac.uk Kate Keahey (keahey@mcs.anl.gov)keahey@mcs.anl.gov

2. www.gridforum.org Grid Economic Service Architecture (GESA) Chairs:  Steven Newhouse (s.newhouse@doc.ic.ac.uk)s.newhouse@doc.ic.ac.uk  Jon MacLaren (jon.maclaren@man.ac.uk)jon.maclaren@man.ac.uk  Kate Keahey (keahey@mcs.anl.gov)keahey@mcs.anl.gov Admin:  http://www.doc.ic.ac.uk/~sjn5/GGF/gesa-wg.html  Mailing list: gesa-wg@gridforum.orggesa-wg@gridforum.org Define the protocols and service interfaces needed to support the charging of Grid Services within the OGSA.  To define a Grid Banking Service (GBS) that records these financial transactions.  To define a Chargeable Grid Service (CGS) that encapsulates an existing Grid Services with the functionality necessary for it to be purchased.  To enable a variety of economic models with these services but not to explore the economic models themselves.

3. www.gridforum.org GGF 7 Sessions GESA 1: 10-11.30am Wednesday  Fuji  Agenda:  Introduction & Welcome  GESA: Aims & motivation  Use Cases GESA 2: 4-5.30pm Thursday  Fuji  Agenda  Introduction  GESA Scheduling Architecture

4. www.gridforum.org Session 1 Meeting at GGF 6 Discussion & production of use cases as an informational document  Computational Provider Use Case  Application Service Provider  Software Application Provider  Brokering Service Provider  Computational Reseller Use Case

5. www.gridforum.org Charter To purpose of this working group is to define the protocols and service interfaces needed to extensibility support a variety of economic models for the charging of Grid Services in the OGSA.  To define an open extensible economic service architecture (based around OGSA Grid Services) to enable the provision and consumption of Grid Services.  To define a Grid Banking Service (GBS) that records these financial transactions.  To define a Chargeable Grid Service (CGS) that encapsulates an existing Grid Services with the functionality necessary for it to be purchased.  To enable a variety of economic models with these services but not to explore the economic models themselves. Web site:  http://www.doc.ic.ac.uk/~sjn5/GGF/gesa-wg.html  Mailing list: gesa-wg@gridforum.orggesa-wg@gridforum.org

6. www.gridforum.org Charter: Goals To provide the supporting infrastructure to enable Computational and Data Grids operated by different organisations to ‘trade’ services between each other. The purpose of the working group is to specify the protocols and service interfaces that will enable the exploration of these economic models but not to concentrate on the development of the economic models themselves. It is recognised by the WG that the trading of grid services is an emerging research area that has attracted considerable interest but not yet delivered substantive results. It is impossible for entities to ‘trade’ services with one another, as there are no standards to define the trade. Our goal within this WG is therefore to define an initial set of service interfaces and protocols to enable further research activity elsewhere within GGF of the Grid community. After this activity it is envisaged that new GGF working group(s) will be required to develop the initial work completed within GESA. To provide an extensible infrastructure to enable economic activity in the Grid Environment

7. www.gridforum.org Overview We wish the GBS and CGS to contain a minimal feature set that enables further research activity within grid economies, which we see as outside the scope of this WG. We therefore define a CGS as a standard Grid Service with any additional ports or service data elements (as required) to allow:  The CGS provider to define acceptable GBS with which they are willing to undertake transactions.  Their own GBS to record their transactions.  Supported transactions mechanisms (e.g. auction, fixed price). The GBS is focused on recording the cost of a CGS transaction with a CGS for future reconciliation and may itself be a CGS. It therefore needs to:  Validate a transaction - is this transaction acceptable to all? NB. This stage could involve a 'credit' check to see if sufficient funds are available with this implementation of the GBS to cover the transaction.  To implement a transaction - to 'pay' for the service not only in a secure but also a reliable way (two phase commit etc).

8. www.gridforum.org Architecture OGSA Grid Service Service InterfaceService Data Service InterfaceService Data OGSA Chargeable Grid Service Grid Economic Service Interface Record Resource Usage OGSA Resource Usage Service Contract Negotiation Economic Service Data Contract Verification Service Charging OGSA Grid Banking Service Grid User

9. www.gridforum.org

10. GESA: Grid Economic Services Architecture Steven Newhouse (s.newhouse@doc.ic.ac.uk)s.newhouse@doc.ic.ac.uk

11. www.gridforum.org Grid Economic Service Architecture (GESA) Define the protocols and service interfaces needed to support the charging of Grid Services within the OGSA.  To define a Grid Banking Service (GBS) that records these financial transactions.  To define a Chargeable Grid Service (CGS) that encapsulates an existing Grid Services with the functionality necessary for it to be purchased.  To enable a variety of economic models with these services but not to explore the economic models themselves. Chairs:  Steven Newhouse (s.newhouse@doc.ic.ac.uk)s.newhouse@doc.ic.ac.uk  Jon MacLaren (jon.maclaren@man.ac.uk)jon.maclaren@man.ac.uk  Kate Keahey (keahey@mcs.anl.gov)keahey@mcs.anl.gov Admin:  http://www.doc.ic.ac.uk/~sjn5/GGF/gesa-wg.html  Mailing list: gesa-wg@gridforum.orggesa-wg@gridforum.org

12. www.gridforum.org Open Grid Services Architecture From Web services:  Standard interface definition mechanisms: multiple protocol bindings, multiple implementations, local/remote transparency Building on Globus Toolkit:  Preserve GT2 features (i.e. retain client side API)  Grid service: semantics for service interactions  Management of transient instances (& state)  Factory, Registry, Discovery, other services  Reliable and secure transport Multiple hosting targets: J2EE,.NET, “C”, … Service orientated architecture enables resource virtualisation

13. www.gridforum.org For Computational Markets Expose Resources through a Factory Service  Factory has the ability to spawn transient services  This is a highly extensible entry point  Equivalent to invoking a Java constructor Service Data Elements (XML)  Contains & expose meta-data relating to the service  Static elements provided from GSS  Dynamic elements from the service or elsewhere

14. www.gridforum.org OGSA in GESA GESA enabled client ‘obtains’ a GSH  Grid Service Handle (GSH) provides unique service ID GSH passed to an existing client  Retain existing client interface with an economic service Key Issues:  Information needed to make the selection (SDE)  Two (Multi?) stage commit to support pricing  Enable wide ranging exploration of grid economic models

15. www.gridforum.org Grid Economic Brokering Multi-stage resource selection  Requirements & Rank Requirements:  Do I want a minimum SLA?  Do I need a legal option on failure?  Will the resource accept TonyHeyDollars? Rank by Cost:  What is the resource worth?  How do I set the price? (Auction, Fixed price) Within the SDE Generated by the Service

16. www.gridforum.org New Service Data Elements Trust, Reputation & Reliability (0+)  Can I rely on this service? Will it do what it says on the tin?  Who has ‘audited’ this service for performance & integrity?  Do we (the UK) need an OfGrid?  Allow SDE to updated by signed statements? Compensation & Liability (0+)  Who can I complain to and can I prosecute?  How could the contract be broken? Grid Banking Services (1+)  Declare which GBS are acceptable Resource Usage Service (1)  Declare which RUS is used by the service

17. www.gridforum.org How it might work… User Container Factory Container Factory Request a price for users (…) to run jobs over 16 processors for the next 2 hours using auctioning. 30s lifetime to complete auction Request use of software library For the next 2 hours. Accept Flat rate fee of £2/hour.

18. www.gridforum.org Architecture OGSA Grid Service Service InterfaceService Data Service InterfaceService Data OGSA Chargeable Grid Service Grid Economic Service Interface Record Resource Usage OGSA Resource Usage Service Contract Negotiation Economic Service Data Contract Verification Service Charging OGSA Grid Banking Service Grid User

19. www.gridforum.org Summary GESA underway… Builds on and exploits abstractions within OGSA Draft Documents:  Use cases describing:  Computational Provider  Application Service Provider  Software Application Provider  Brokering Service Provider  Computational Reseller  Architecture defining interfaces and services Meeting here at 4pm Thursday