rus: resource usage service
DESCRIPTION
RUS: Resource Usage Service. Steven Newhouse ( [email protected] ) James Magowan ( [email protected] ). Agenda. Welcome & Introduction Charter & WG Goals Review of Grid Resource Usage activities UK e-Science: The Level 2 Grid … Recording Resource Usage - PowerPoint PPT PresentationTRANSCRIPT
www.gridforum.org
RUS: Resource Usage Service
Steven Newhouse ([email protected])
James Magowan ([email protected])
www.gridforum.org
Agenda
•Welcome & Introduction •Charter & WG Goals •Review of Grid Resource Usage activities
UK e-Science: The Level 2 Grid…
•Recording Resource UsageService interface overview - define functionality not specifics. Define contents of XML [ Detailed definition of these can be postponed to post GGF on the list ]
•Extraction of Resource Usage Information Service interface overview - define functionality not specifics. Discuss security model for extracting data (Who can access what of whom?)
•Way ahead...
www.gridforum.org
OGSA Resource Usage Service (RUS)
•Chairs:Steven Newhouse ([email protected])James Magowan ([email protected])
•Admin:http://www.doc.ic.ac.uk/~sjn5/GGF/rus-wg.htmlMailing list: [email protected]
•Met at GGF 6•Define an OGSA Resource Usage Service (RUS) that will track resource usage:Define a service interface to add & search stored accounting records.Define a security model for the data stored within the RUSTo support a (minimal but extensible) set of commonly understood attributes to describe resource usage (from the Usage Record WG).
www.gridforum.org
Charter
•To define a Resource Usage Service (RUS) for deployment within an OGSA hosting environment that will track resource usage (accounting in the traditional UNIX sense) and will not concern itself with payment for the use of the resource.Definition of service interface to add & search records for accounting information to support use by grid services, individual user clients or service managers.
Defining a security model for the data stored within the RUS, that protects and individuals right to privacy relating to how they used a service, by building upon the standard OGSA security infrastructure.
To support a (minimal but extensible) set of commonly understood attributes to describe resource usage (leveraging work undertaken by the Record Usage Format WG).
www.gridforum.org
Charter: Goals & Milestones
•GoalsTo enable the tracking of resource usage within Grid Services deployed within an OGSA environment. As the ‘resources’ that need to be tracked (e.g. CPU, time, memory) may be vary between services and over time an extensible schema will be used to structure this information.
• MilestonesGGF 5: Initiate discussion of this activity with a BOF and a move to produce a WG charter.
GGF 6: Contribute resource usage cases as GWD-I’s to build on existing information in this area within GGF.
GGF 6: Initiate detailed discussion on an initial specification of this service with the intention of producing a GWD-C that defines current activity and interfaces.
GGF 7: Present a revised specification for further discussion and continued iteration of the GWD-C.
GGF 8: Aim to complete the GWD-C with a proposed service specification and report on its use through a GWD-E. Examine current group activity with the intention of initiating a standard recommendation within a GWD-R.
www.gridforum.org
Architecture
OGSA Grid ServiceService InterfaceService Data
Service InterfaceService Data
OGSA ChargeableGrid
Service
Grid EconomicService Interface
RecordResource
Usage
OGSAResource
UsageService
ContractNegotiation
EconomicService
Data
ContractVerification
ServiceCharging
OGSA GridBankingService
GridUser
www.gridforum.org
Interface Outline (1)
•Store Resource UsageResource Identifier (GSR?)Sequence/Invocation Identifier (GSH?)User Name (X.509 DN?)When executedWhere executed (Human readable form of GSH) What has been used?
Attribute & Value pairs (UR-WG/CRM-WG) Schema based for resources? (CRM-WG) Application invocation? Comment Field? Is this enough? Need to have extensible attribute structure?
• Allow the undefined to be expressed!Encapsulate as XML document.UR-WG defines the contentCan the data be updated?
Update every 10 minutes… incremental updates of resources that are consumed Do we always treat it as an incremental update or a new record (a failure?) Upload document: Exception if not unique?
www.gridforum.org
Interface Outline (2)
•What approach to use?Expose the back end database using OGSA-DAI: expose structure not contentExpose the RUS content through the FindServiceData SDE’sHigh-level service interface (new port type(s)) to extract RUS data that is implemented internally with, say, SQL commands. Restricts supported queries
•Extract Resource UsageReturn information relating to a specific service invocationReturn information relating to a particular serviceRequest Failure: Due to internal authorisation processOptions:
Return complete or partial record data?
•Query Resource UsageOn any attribute within the UR and the overall meta-dataEG:
Usage for a jobUsage for a particular machineAll those jobs using 4->16 processors.Memory request greater than 16MB!
www.gridforum.org
Interface Outline (3)
Do we handle charging? Allow updating – should the record be immutable?Logging: Use OGSA logging to capture state transition to build RUS XML docs.
Is there lifetime to this data? Need a mechanism to purge records? But when?
www.gridforum.org
Service Data
•Define who can store information in the serviceBy VO?By Host Domain?
•Define who can extract information from the serviceA user can extract their own job informationAn administrator can access their own resources informationAllow general
•Define what information is storedList the resource types stored by the service