EMI INFSO-RI Towards URF 2.0 From a storage perspective Jon Kerr Nilsen Dept. of Physics, Univ. of Oslo On behalf of the EMI StAR team

EMI INFSO-RI EMI and storage accounting Storage accounting vs. job accounting EMI StAR proposal Conclusion/way forward Outline Jon Kerr Nilsen 2

EMI INFSO-RI From EMI Description of Work: – EMI will address known UR issues and extend accounting records to include VO-aware storage usage accounting – The refined and extended standard UR format, service interface and data transport protocol will be implemented in gLite, ARC, dCache and UNICORE – EMI will thus contribute to the definition of UR 2.0 of OGF Not just an academic exercise for EMI Storage accounting in EMI Jon Kerr Nilsen 3

EMI INFSO-RI If there is no standard for storage accounting yet, do anyone actually need it? Note: Storage resources are shared between VO’s – more than one owner Developing a storage infrastructure – We need to know how much storage space is used, by which group/user, on which storage media – To know where to put the money when increasing the storage space – To know who to ask for the money to increase the storage space Basis for billing – Storage is expensive – Some non-academic resource owners may not like to give it away for free Why storage accounting? Jon Kerr Nilsen 4

EMI INFSO-RI Accounting is the recording and summarizing of the consumption of a resource by an individual user or a group of users Typically used to find out who uses how much of a set of resources Typically not used to find out how individual resource components are used Accounting Jon Kerr Nilsen 5

EMI INFSO-RI Storage vs. job accounting Job accounting Job accounting is the recording and summarizing of the consumption of computing resources Recording wall-time, cpu-time, etc. – strictly increasing values. When a job finishes it stays finished Typically measured per job – information readily available from local batch system Standardized through UR 1.0 Storage accounting Storage accounting is the recording and summarizing of the consumption of a storage resource Storage usage varies in time – recorded usage is only relevant in a given time frame Data is rarely in finished state and can live for a long time Typically recorded through (in)frequent usage snapshots – high fluctuation rate No standardized record Jon Kerr Nilsen 6

EMI INFSO-RI Storage vs. job summary Jon Kerr Nilsen 7 Storage records must be treated different than job records wrt. aggregation Storage records need special treatment – Only valid between measurement time and expiration time – Can be invalidated if newer record is registered for same resource – Nontrivial processing model

EMI INFSO-RI Processing model Jon Kerr Nilsen 8 Storage records can overlap in time – cannot simply sum up to identify total consumption May be event based records – or taken every hour/day/month Must ask for a certain point in time and sum up the most recent, still- valid records To get usage per time, you must choose a set of timestamps and repeat process per time stamp – numerical integration

EMI INFSO-RI Storage vs. job commonalities Jon Kerr Nilsen 9 Both job records and storage records have subject ID – URF 1.0 has no way to include VO info – URF 2.0 should support VOs None of them care about network

EMI INFSO-RI UR1 not readily extendable and is missing VO information No draft for service record in UR 2.0 yet EMI needs record format now to implement before end of EMI project Decided to keep the StAR format close to OGF UR 1.0, but still separate Merge with UR 2.0 when available Why a separate storage record? Jon Kerr Nilsen 10

EMI INFSO-RI EMI is now finalizing a proposal for a storage accounting record (StAR) Contacted and received input from organizations and potential user groups – NDGF, OGF, EGI, OSG, INFN, CMS, ATLAS, … – Not only an EMI in-house production Current draft: StAR-EMI-tech-doc-v7.pdfStAR-EMI-tech-doc-v7.pdf Final version will be proposed to OGF as a standard Will be implemented by EMI storage providers Work already started outside EMI (SGAS) EMI StAR Jon Kerr Nilsen 11

EMI INFSO-RI Resource – Fields describing the system the resource was consumed on –StorageSystem, StorageShare Consumption details – Fields describing what is consumed –StorageMedia, StorageClass, DirectoryPath, … Identity – Describes the person or group accountable for the consumption –SubjectIdentity block ( UserIdentity, Group, GroupAttribute, …) Resource consumption – How much of the described resource has been used –ResourceCapacityUsed, LogicalCapacityUsed Record identity and duration StAR structure Jon Kerr Nilsen 12

EMI INFSO-RI Local example Jon Kerr Nilsen 13 <sr:StorageUsageRecord xmlns:sr=" <sr:RecordIdentity sr:createTime=" T09:06:52Z" sr:recordId="host.example.org/sr/ "/> host.example.org johndoe tape T09:31:40Z PT3600S

EMI INFSO-RI <sr:StorageUsageRecord xmlns:sr=" <sr:RecordIdentity sr:createTime=" T09:06:52Z" sr:recordId="host.example.org/sr/ "/> host.example.org binarydataproject.example.org ukusers tape T09:31:40Z PT3600S Grid example Jon Kerr Nilsen 14

EMI INFSO-RI Full example Jon Kerr Nilsen 15 <sr:RecordIdentity sr:createTime=" T09:06:52Z” sr:recordId="host.example.org/sr/ "/> host.example.org pool-003 disk replicated 42 /home/projectA johndoe projectA /O=Grid/OU=example.org/CN=John Doe binarydataproject.example.org ukusers T09:31:40Z PT3600S

EMI INFSO-RI Definition of StAR is a first step to establish common storage accounting record May be a step forward to establish a common URF Next jump (two steps in one go) – Propose StAR to OGF to start standardization process Will take time Will include further discussions May lead to changes in StAR EMI will take active part in this process – Implement StAR record into EMI storage middleware Standardization process may take longer than EMI Important to gain user experience with the definition if aiming for grid standard Comments and input more than welcome! Way forward Jon Kerr Nilsen 16

EMI INFSO-RI THANK YOU! Contact: Web page: Current StAR draft: Jon Kerr Nilsen 17