[glue-wg] Suggestion for splitting the StorageShare.

[Laurence Field]

On further investigation of the Storage Schema an unmet use case has 
been found.

Use Case: Consider two VOs who use two different paths to access the 
same StorageShare or alternatively one VO who can access the same 
StorageShare via two different paths. Where there could be an asymmetry 
with the ACLs for the SRM v2.2 space and the Path.

The latest schema would require a StorageShare to be instantiated for 
each combination of path and SRM v2.2 space ACL, leading to n*m storage 
shares duplicating a great deal of information.

The suggested solution is to split the StorageShare into the 
StorageShare and StorageEnvironment where there is a one to many 
relationship between the Environment and the Share. Both entities 
inherit the ACLs from the AccessPolicy

StorageShare
LocalID
Path
Tag

StorageEnvironment
LocalID  
ServingState
AccessLatency
RetentionPolicy
ExpirationMode
DefaultLifeTime
MaximumLifeTime

At the same time this allows the AggregationID to be removed.