• Date: 27 Mar 2008
• Time: 2 PM CET (conversion to other timezones)
• Duration: 1,5h
• Calling number: +41 22 76 77000 (ask to be connected to "GLUE Meeting")
• Shared screen session information:
  • URL: http://glue-wg.glance.net
  • Key: 2703

Agenda

• Quick issues
  • EndpointCapability
  • Nordugrid example : Share-localID, why "LocalID" instead of "ID"
  • Architecture: multivalued ? open numeration ?(tape, disk, multidisk, DVD, ...)
  • Use case for scenario; tape system down, disk ok: are associated shares using both should be marked as down, too?

Examples :

• INFN issues
  • StorageShare.State, does not better fit environment?
  • StorageShare.Tag/Path, why if they are in StorageMappingPolicy? not needed?

• GSSD

Participants

• Flavia Donno (CERN)
• Maarten Litmaath (CERN)
• Paul Miller (DESY)
• Felix Ehm (CERN)

Minutes

• StorageCapacity - StorageEnvironment:
  • Environments should be homogenous and should NOT overlap in order to retrieve meaninful (no double counting) space usage information. Must be mentioned in the GLUE specification.
  • Action: Felix, clearify with other Grid Infrastructures if this collides with their requirements
  • SCHEMA: removed Aggregation of Resource and Capacity

• Architecture attribute (StorageEnvironment):
  • not clear if this is the right place
  • Maarten : strong (non-operational) use case for WLCG
  • Paul: drop architecture in favour of having anyway a type in the assigned storage capacity which reflects this information
  • Paul: natural place is the 'Capacity' - but then it must be published with every capacity entity (redundant information)
  • SCHEMA: Architecture goes into Capacity as optional single valued attribute

• Flavia : Use Case for having a status in the AccessProtocol entity
  • most suitable attribute type: ServingState_t

• StorageCapacity - MappingPolicy relationship:
  • suggestion in order to have the possiblity for VO accounting info
  • does this make the schema overcomplex and does it lead to misunderstanding ?
  • not necessary a all if a Share is assigned to one VO (WLCG)
  • however, use case #3 for NorduGrid
  • Understand the impact of Sergios's suggestion for final decision

• SCHEMA: Capacity size attributes all optional

• SCHEMA: MaxStreams (AccessProtocol) optional