• Date: 14 April 2008
• Time: 2 PM CEST (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: 1404

Agenda

• Storage
  • high-level aggregated Capacity information
  • agreement on Share definition!
  • Collection of use cases for datastore entity
  • AOB

Participants

• Sergio Andreozzi (CNAF)
• Felix Ehm (CERN)
• Maarten Litmaath (CERN)
• Stephen Burke (RAL)

Minutes

Actions:

• Maarten to provide definition for accessLat/RetPol/ExpMode values to be added in 18.33/34/35

Open issues

• where to get summary size info
  • think of a summary class to be related to the storageService

• add class to summarize available capacity at the global service level
  • StorageCapacity
  • LocalID
  • Type: (online, nearline, offline)
  • TotalSize
  • FreeSize
  • UsedSize
  • ReservedSize

• space can be free/used/reserved
  • reserved is a state that applies to SRM implementations

• how to discover types of AccessLatency/RetentionPolicy
  • it should aggregate info from StorageShare level

• why ExpirationMode is multi-value?
  • because they are the possible supported by the SRM implementation
  • expirationMode values are taken from SRM v.3
  • when putting a file, a user can specify which expirationMode to assign to a file

• What about an ExpirationMode default value?
  • SRM states "volatile"
  • we do not feel the need to publish the default

• do we need a maximumLifeTime/defaultLifeTime?
  • ADDED

• Maarten: RetentionPolicy, why not multi-value?
  • Agree that can be multi-value

current SRM does not support it, but in the future, it can be that a share can support e.g., both custodial and replica

• Why Tag multi-value?
  • added a comment, to verify later

• still to discuss what to privilege in the design
  • unnormalized-> implies redundancy, but simpler schema and easier query
  • normalized-> more complex relationships, complex queries, less redundancy