• Date: 25 Jan 2008
• Time: 9 AM Chicago, 3 PM London, 4 PM Rome (conversion to other timezones)
• Duration: 1,5h
• Calling number: +41 22 76 77000 (ask to be connected to "Glue Schema Meeting")
• Shared screen session information:
  • URL: http://glue-wg.glance.net
  • Key: 2501

Agenda

• Check the revised storage schema entities and relationships
  • Service - Share relationship
    • Discuss : publish a Service (resource) containing all the Share(s) it manages ?
    • What is the search use case ?
  • Endpoint - Share relationship
    • Discuss : publish endpoints with the Shares they make accessible

• Define the StorageShare entity

• Discuss main issues arised last time:
  • do we need to support Classic SE?
  • how is the information about a local available transfer protocol published?

• Missing
  • CESEBind relation
    • Comment from ML: what about if rfio can be used from a UI? the CESEBind won't work - is this an major issue?
    • Suggestion: New Entity which keeps the ComputingShare and StorageShare Relation.

• Attached : Storage schema UML diagram

Participants

• Sergio Andreozzi (INFN)
• Riccardo Zappi (INFN)
• Luca Magnoni (INFN)
• Laurence Field (CERN)
• Felix Ehm (CERN)
• Maarten (CERN)
• Jens Jensen (RAL)
• Paul Millar (DESY)
• Stephen Burke (RAL)

Minutes

Check the revised storage schema entities and relationships

Sergio: can we say that a StShare is associated to at most one StorageEndpoint as manager? Answer: no, e.g. SRMv1 and SRMv2 managing same share

Summary:

• StorageEndpoint can be used for manager endpoint, transfer.. etc, depends on Capabililty
• StorageEndpoint(1..*)---(0..*)StorageShare
• StorageService (AGGR) --- (0..*) StorageShare
• StorageEndpoint to be renamed Endpoint if we do not find any storage-specific attribute
• Keep StorageEnvironment and StorageShare separated
  • evaluate impact on implementation
• Move the ExpirationMode to StorageShare

• For ComputingEndpoint, remove Capabilities from Suspend/Staging

Jens: we have lightpath between two sites; we may want to discover which endpoint has access to the fast link

Paul: Share: logical separation of storage space; two identified flavours:

• as partitioning
• as reservation

Maarten: we do not want to publish dymanically reserved space; we should publish only as partition/quotas

Main Entities::Share: A utilization target for a set of resources offered via related endpoints defined by policies and characterized by status information StorageShare: (? Specialize ?) A utilization target for a set of resources offered via related endpoints defined by policies and characterized by status information

StorageShare(0..*)---StorageShareEnvironment: discussion about if we should merge the attributes of shareenvironment in storageshare; if not, the share

• in a storage system, we can have different storage share environments
• a storage share belongs to one and only one type of share environment

Attachments:

Class_Diagram__Storage.jpg [PhoneMeeting20080125/Class_Diagram__Storage.jpg]