1. © 2006 Open Grid Forum RUS Core Specification v1.8 OGF Resource Usage Service WG

2. © 2006 Open Grid Forum 2 OGF IPR Policies Apply “ I acknowledge that participation in this meeting is subject to the OGF Intellectual Property Policy. ” Intellectual Property Notices Note Well: All statements related to the activities of the OGF and addressed to the OGF are subject to all provisions of Appendix B of GFD-C.1, which grants to the OGF and its participants certain licenses and rights in such statements. Such statements include verbal statements in OGF meetings, as well as written and electronic communications made at any time or place, which are addressed to: the OGF plenary session, any OGF working group or portion thereof, the OGF Board of Directors, the GFSG, or any member thereof on behalf of the OGF, the ADCOM, or any member thereof on behalf of the ADCOM, any OGF mailing list, including any group list, or any other list functioning under OGF auspices, the OGF Editor or the document authoring and review process Statements made outside of a OGF meeting, mailing list or other function, that are clearly not intended to be input to an OGF activity, group or function, are not subject to these provisions. Excerpt from Appendix B of GFD-C.1: ” Where the OGF knows of rights, or claimed rights, the OGF secretariat shall attempt to obtain from the claimant of such rights, a written assurance that upon approval by the GFSG of the relevant OGF document(s), any party will be able to obtain the right to implement, use and distribute the technology or works when implementing, using or distributing technology based upon the specific specification(s) under openly specified, reasonable, non- discriminatory terms. The working group or research group proposing the use of the technology with respect to which the proprietary rights are claimed may assist the OGF secretariat in this effort. The results of this procedure shall not affect advancement of document, except that the GFSG may defer approval where a delay may facilitate the obtaining of such assurances. The results will, however, be recorded by the OGF Secretariat, and made available. The GFSG may also direct that a summary of the results be included in any GFD published containing the specification. ” OGF Intellectual Property Policies are adapted from the IETF Intellectual Property Policies that support the Internet Standards Process.

3. © 2006 Open Grid Forum 3 Outline RUS Spec. (v1.7) RUS Spec. (v1.8) Discussion RUS and UR

4. © 2006 Open Grid Forum 4 RUS Spec (v1.7) Review Implementation Specific MCS-RUS (Manchester Univ.); Based on old [UR-SPEC] (UR v1.0 final just come up); Need more clarifications on Distributed storages; RBAC (Role and UR extension framework) e.g. OSG and EGEE want VOManager role described by UR extensions; Finer-granularity authorisation on the content of usage properties; RUS Usage Record undermines the standardisation of [UR-SPEC] ? Single usage record per file for implementation-specific environment (Xindice requires the XML size less than 5MB How about other Database Systems and implementation runtime);

5. © 2006 Open Grid Forum 5 RUS Spec. (v1.7) Review (cont..) Operation Result Document-orient result “Batch-like” operation status on overall execution status; As well as fault details on individual usage record operations; Fault Three faults (Use not authorised fault, internal processing fault, and Input Fault specific to invalidate RUSUsageRecord inputs); Contradict to the five faults (Record not existent fault and duplicate record fault) defined in “RecordIdList”; Does not allow extensions for more faults; SIDs Modification allows XUpdate expression but restricts implementations on modifications on numeric contents of usage properties; Dangerous on “append/insert” nodes on usage records (This would result in the invalidation of against UR-SPEC schema; Need clarifications on “context” node of XPath statement; Do we really need “incrementUsageRecordPart” Overall SIDs still needs formatted naming conventions e.g. [Operation]+SpecUsageRecords & [Operation]+UsageRecords

6. © 2006 Open Grid Forum 6 RUS Spec. 1.8 RUS Spec 1.8 improvement based on reviews; Context Usage Records in pure [OGF-UR] final version 1.0 format; Usage Storage can be either centralized or distribute; Modified “ByAndWhen” information ensured by implementation runtime environment (Logging system or service container?) The core specification should concentrate on minimum operation requirements. Separate specification bundles can provide guides for extensions and normative extensions on aggregation and data replication; More clarifications on various implementation environment; Namespace types (http://www.gridforum.org/2007/rus-wg/types);http://www.gridforum.org/2007/rus-wg/types rus(http://www.gridforum.org/2007/rus-wg/core);http://www.gridforum.org/2007/rus-wg/core ext(http://www.gridforum.org/2007/rus-wg/extensions) ? ;http://www.gridforum.org/2007/rus-wg/extensions

7. © 2006 Open Grid Forum 7 General Types Operation Result Common properties for overall operation status processed number of usage records; Individual Fault details; Schema

8. © 2006 Open Grid Forum 8 General Types (1) Faults and Extensions Abstract “general fault”; Five predefined RUS faults (see spec. documents) substitute to “general fault” group; New faults can be extended but substitute to “general faults” soasto be recognised by operation result; Schema

9. © 2006 Open Grid Forum 9 Role and Authorisation Two required Roles (as V1.7) Resource Manager; Service Administrator; Role and UR extensions properties OSG defines VO as resource extension property: CMS The possible VO manager is then should provide mapping between user DN and VO name resource property; Clarification on fine-granularity access control (see section 3.2);

10. © 2006 Open Grid Forum 10 Service Interface Definition XPath expression V1.8 only accepts xpath expression to set the anchor for designated context node for update and extraction; Any invalid XPath expression will result in the throw of RusInvalidFault(#type=“invalidXPath”); The syntax error for XPath expression results in the throw of RusProcessingFault with embedded error message from runtime (DB engine); UserNotAuthorisedFault will be thrown before any usage record processing;

11. © 2006 Open Grid Forum 11 Storage Contribute usage records to RUS; Interface Definition [Normative] Name: rus:InsertUsageRecords Input: One or more [OGF-UR] Usage Records (root element MUST be urf:UsageRecords) Output: Operation Result encapsulates total status and fine-granularity faults for each usage record; Faults: Duplicate Fault (rus:RUSDuplicateFault); Runtime Faults (rus:RUSProcessingFault); Invalid Faults (rus:RUSInvalidFault#type=‘invalidSchema’); Authorisation Fault (rus:RUSUserNotAuthorisedFault);

12. © 2006 Open Grid Forum 12 Extraction (1) Extract specific usage records by identifier list Interface Definition [Normative] Name: rus:extractSpecUsageRecords Input Record identifier (string) list; Output Single usage record file (urf:UsageRecords) Operation Result document; Faults Unauthorised user (RUS:UserNonauthorisedFault); Runtime fault (RUS:RUSProcessingFault); Record Not Found Fault (RUS::RUSRecordNotFoundFault);

13. © 2006 Open Grid Forum 13 Extraction (2) Extract usage records that match the specific criteria expressed in XPATH statement; Clarification of XPATH expression XPATH Must be in one of the form as following to ensure the context node is urf:UsageRecord or urf:JobUsageRecord; Interface Definition [Normative] Name: RUS::extractUsageRecords Input XPath Statement as clarified, malformed xpath expression may results in the throw of rus:RUSInvalidFault; Output Single usage record file (urf:UsageRecords) encapsulates matched usage record context elements; Operation Result document indicates the batch processing status of multiple usage records and fault information (if any) of matched usage records; Faults Unauthorised user (RUS:UserNonauthorisedFault); Runtime fault (RUS:RUSProcessingFault); Invalid XPATH expression fault (RUS:InvalidFault#type=“invalidXPATHExp”);

14. © 2006 Open Grid Forum 14 Extraction (3) Extract usage record identifier of usage records that match the specific criteria expressed in XPATH statement; Clarification of XPATH expression XPATH Must be in one of the form as following to ensure the context node is urf:UsageRecord or urf:JobUsageRecord; Interface Definition [Normative] Name: RUS::extractUsageRecordIds Input XPath Statement as clarified, malformed xpath expression may results in the throw of rus:RUSInvalidFault; Output A list of record Identifiers; Operation Result document indicates the batch processing status of multiple usage records and fault information (if any) of matched usage records; Faults Unauthorised user (RUS:UserNonauthorisedFault); Runtime fault (RUS:RUSProcessingFault); Invalid XPATH expression fault (RUS:InvalidFault#type=“invalidXPATHExp”);

15. © 2006 Open Grid Forum 15 Update As with update, the specification needs to clarify its scope and implementation details (very important) Common use scenarios Use Case 1: modify the value of specific element(s) but ensuring the usage record instance is valid; (e.g. when a VO/Site/Resource name changed, associated resource properties corresponding to Use Case 2: replace of an overall usage record (urf:UsageRecord element) in a usage record file; I didn’t see any real use case that requires insert elements and delete element from a usage record. Now the usage records are mainly for query purpose. If there is I am pleased to know but we can still concentrate on common requirements and keeps the core specification minimum and leaves extension specifications or implementation to realised special usage scenarios. So there are two main operations provided with two use cases above. Modification; Replacement;

16. © 2006 Open Grid Forum 16 Modification Modification operations allows authorised users to “batch-update” a list of usage records relating to certain search terms; Modify specific usage records identified by record identifier [Normative]; Name: rus:ModifyUsageRecords Input XPath expression; Value as string; Output Operation Result document indicates the batch update processing status of usage record(s) and fault information (if any) of specific usage record(s); Fault Unauthorised user (RUS:UserNonauthorisedFault); Runtime fault (RUS:RUSProcessingFault); Invalid XPATH expression fault (RUS:InvalidFault#type=“invalidXPATHExp”); The modification implementation SHOULD protect the record identifier (urf:RecordIdentity#recordId attribute) and creation timestamp to be modified. Any operation that tries to perform modifications on these properties will result in the throw of “invalid fault”;

17. © 2006 Open Grid Forum 17 Replacement Replacement operation allows authorised users to replace a list of usage records with specific record identifier; Replace specific usage records; [Normative] Name: rus:ReplaceUsageRecords Input A single usage record file (urf:UsageRecords) with a number of usage records embedded; Output Operation Result document indicates the replacing operation status and fault information (if any) of specific usage record(s); Fault Unauthorised user (RUS:UserNonauthorisedFault); Runtime fault (RUS:RUSProcessingFault); Invalid XPATH expression fault (RUS:InvalidFault#type=“invalidXPATHExp”); Record Not Found Fault (rus:RUSRecordNotFoundFault”); The replacement implementation SHOULD protect the record identifier (urf:RecordIdentity#recordId attribute) and creation timestamp to be replaced. Any operation that tries to perform modifications on these properties will result in the throw of “invalid fault”;

18. © 2006 Open Grid Forum 18 Deletion (1) Delete specific usage records by usage identifiers; Interface Definition [Normative] Name: rus:deleteSpecificUsageRecords Input Record identifier (string) list; Output Operation Result document; Faults Unauthorised user (RUS:UserNonauthorisedFault); Runtime fault (RUS:RUSProcessingFault); Record Not Found Fault (RUS::RUSRecordNotFoundFault);

19. © 2006 Open Grid Forum 19 Deletion (2) Delete usage records that match the specific criteria expressed in XPATH statement; Service Interface Definition [Normative] Name: rus:deleteUsageRecods Input XPath Statement as clarified, malformed xpath expression may results in the throw of rus:RUSInvalidFault; Output A list of record Identifiers; Operation Result document indicates the batch processing status of multiple usage records and fault information (if any) of matched usage records; Faults Unauthorised user (RUS:UserNonauthorisedFault); Runtime fault (RUS:RUSProcessingFault); Invalid XPATH expression fault (RUS:InvalidFault#type=“invalidXPATHExp”);

20. © 2006 Open Grid Forum 20 Other promising RUS specifications RUS Access Control Profile Based on XACML 2.0 XACML RBAC profile XACML hierarchical resource profile; XACML multiple resource profile; RUS Extensions Extension Profile ? Aggregation Extension Specification

21. © 2006 Open Grid Forum 21 Full Copyright Notice Copyright (C) Open Grid Forum (2006-2007). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. The limited permissions granted above are perpetual and will not be revoked by the OGF or its successors or assignees.