Hi, I am spending some time to define an example of storage with the current Glue Schema draft. Unfortunately, I have some difficulties to represents the Data Store and the Storage Resource as you have defined into Glue Schema. Suppose a site with storage system organized with a SAN and cluster file system, like GPFS. Using the same SAN and cluster file system, I could define and mount different file systems upon the same infrastructure. For example, GPFS cluster can contain up to 256 mounted file systems. I can define some StorageShares using quota GPFS tools. In this case, the SS sizes are based on GPFS metadata. Therefore, I define StorageShare using file system feature. I imagine one StorageResource per each file system created on GPFS. In this case every StorageResource could have a size and quality properties. Some StorageShares could share the same StorageResource (i.e. file system) entity. When I try to describe how StorageResource is composed some doubts appears. I could lists all volumes composing the file system.. For example in the figure attached, you can see that 16 volumes compose the file system named ‘gpfs_storm’. In any case, heterogeneous disk devices could compose each volume... and then DataStore description appears incorrect. Are you sure that Storage Service administrator knows every details of underlying storage system? Moreover, if the admin knows, are you sure that he wants describe all these details? I think we have to improve DataStore-StorageResource concepts. Perhaps, we can go on to try to merge both concepts in only one entity with multi-valued quality properties. Cheers, Riccardo -- ------------------------------------------------------------------------------- Riccardo Zappi Istituto Nazionale di Fisica Nucleare - CNAF Viale Berti Pichat, 6/2, 40127 BOLOGNA - ITALY Phone: +39-051-609-2868 Fax: +39-051-609-2746 e-mail: riccardo.zappi@cnaf.infn.it -------------------------------------------------------------------------------