- glue-wg - lists.ogf.org

Suggestion for splitting the StorageShare.
by Laurence Field 01 May '08

01 May '08

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.

7 16

Reminder: Glue 2.0 Schema Phone Conference
by Felix Nikolaus Ehm 28 Apr '08

28 Apr '08

Dear all, there will be a telephone conference for the Glue Schema 2.0 tomorrow morning at 11 AM CEST for the computing part: http://forge.ogf.org/sf/wiki/do/viewPage/projects.glue-wg/wiki/PhoneMeet ing20080429_11 and a storage part at 2 PM: http://forge.ogf.org/sf/wiki/do/viewPage/projects.glue-wg/wiki/PhoneMeet ing20080429 Please let me know if you can't make it. There is the possiblity of shifting the storage session later into the afternoon (3pm) if preferred. Cheers, Felix --- Felix Ehm IT-GD tel : +41 22 7674580 CERN, Switzerland -----------------------------------------

1 0

How to kill Glue! WRT OGF
by Owen Synge 28 Apr '08

28 Apr '08

Dear all, The best way to destroy Glue, is to use poorly defined objects, and untested entities relations, that are proprietary to a single or small and legacy subset of Grids, particularly with untested ideas. This will invalidate the purpose of taking your Grid specific views to the OGF. Can I please request that members of Glue trail their ideas on their own grids. I fear some members are unwilling to separate the context of their grids from the greater grid community. Examples include, binding a minority standard (SRM 2.2 and only its static spaces) into the Glue schema when numerous other examples exist such as GPFS, and NFS v4. Binding a minority authentication mechanism (VOMS) when SAML and numerous other standards are more commonly used. This may be forgivable if the people involved had tested these representations, I know from the threads on the mailing list that these ideas are new. I wish to complement Laurence on trying to stop the destruction of his work on the Glue standard, but this continued tight coupling to minority Grid services (VOMS/SRM 2.2) will lead to a legacy standard that all future grids should abandon in favour of something workable for them, if you have not even tested your ideas you should not be proposing them as a standard, that's your Grid's research work and not for OGF, which is for consolidating the Engineering objectives of interoperability. Please consider rolling out these suggestions on your own information systems AND get them WORKING before adding them to a inter grid standard. Regards Owen Synge I do not represent Dcache or DESY in my above objections, just my education as an engineer. Engineering is often about rejecting use cases so more important objectives can be achieved.

5 10

Minutes and Actions
by Laurence Field 25 Apr '08

25 Apr '08

Hi, I have added the minutes to the wiki page. http://forge.gridforum.org/sf/wiki/do/viewPage/projects.glue-wg/wiki/PhoneM… The meeting resulted in 9 Actions, please check and let me know if anything is missing or incorrect. Thanks Laurence

1 0

Storage schema meeting during WLCG at CERN
by Felix Nikolaus Ehm 24 Apr '08

24 Apr '08

Dear all, I'd like to remind of the glue schema meeting at 2pm CEST ( in 15min). For people at CERN: We'll meet in 513-1-023 ( the computer centre, first floor - http://building.web.cern.ch/map/building?bno=513 ). Please find more details here http://forge.ogf.org/sf/wiki/do/viewPage/projects.glue-wg/wiki/PhoneMeet ing20080424 Cheers, Felix --- Felix Ehm IT-GD tel : +41 22 7674580 CERN, Switzerland -----------------------------------------

3 3

glue 2.0 spec comments
by Gerson Galang 23 Apr '08

23 Apr '08

Hi, I've quickly browsed through the current GLUE schema spec and want to get some clarification on the items below: 1. ComputingResource has TotalSlots and TotalLogicalCPUs. What's the difference between the two? Aren't they the same? 2. I couldn't find the Parallel attribute from ApplicationEnvironment. Have you forgotten to include this in the schema? http://forge.ogf.org/sf/wiki/do/viewPage/projects.glue-wg/wiki/PhoneMeeting… Thanks, Gerson

3 2

minutes of the today telecon + spec draft 40
by Sergio Andreozzi 22 Apr '08

22 Apr '08

Dear all, here you can find the minutes of the today telecon: http://forge.ogf.org/sf/wiki/do/viewPage/projects.glue-wg/wiki/PhoneMeeting… The update GLUE 2.0 spec (draft 40) is in the doc repository: http://forge.ogf.org/sf/docman/do/listDocuments/projects.glue-wg/docman.roo… The next telecon is next Thursday: * 24 Apr 2008 - 11 AM CEST - 1,5h - computing * 24 Apr 2008 - afternoon - F2F meeting at CERN - storage Cheers, Sergio -- Sergio Andreozzi INFN-CNAF, Tel: +39 051 609 2860 Viale Berti Pichat, 6/2 Fax: +39 051 609 2746 40126 Bologna (Italy) Web: http://www.cnaf.infn.it/~andreozzi

2 1

Today telecon - from 2 PM CEST to 4 PM CEST (?)
by sergio.andreozzi＠cnaf.infn.it 21 Apr '08

21 Apr '08

Dear all, today we have a telecon on the computing entities. It was scheduled for 2 PM CEST. I'd like to move it to 4 PM CEST. Please, let me know if this is fine. Best regards, Sergio ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

2 1

LDAP Rendering
by Laurence Field 21 Apr '08

21 Apr '08

Hi, I have started the LDAP rendering of the Glue schema. The schema file and example LDIF for the Domains are attached to this mail. Please take a look and let me know what you think. I would especially like someone to check whether I have done the abstract inheritance between the Domain and AdminDomin correctly. I would suggest that we use the gridforge code repository for such files and have made a request via grid forge. Once I have some feedback, I will start working on the Service entities. Laurence # # DIT # # --+ 1 GlueDomain # |-- 1.2.1 DomainUniqueID # |-- 1.2.2 DomainName # |-- 1.2.3 DomainDescription # |-- 1.2.4 DomainWWW # |-- 1.2.5 DomainOtherInfo # --+ 2 GlueLocation # |-- 2.2.1 LocationLocalID # |-- 2.2.2 LocationName # |-- 2.2.3 LocationAddress # |-- 2.2.4 LocationPlace # |-- 2.2.5 LocationCountry # |-- 2.2.6 LocationPostCode # |-- 2.2.7 LocationLatitude # |-- 2.2.8 LocationLongitude # --+ 3 GlueContact # |-- 3.2.1 ContactLocalID # |-- 3.2.2 ContactURL # |-- 3.2.3 ContactType # |-- 3.2.4 ContactOtherInfo # --+ 4 GlueAdminDomain # |-- 4.2.1 AdminDomainDistributed # |-- 4.2.2 AdminDomainOwner # --+ 5 GlueUserDomain # |-- 5.2.1 UserDomainLevel # |-- 5.2.2 UserDomainManagerEndpoint # # attributetype ( 1.3.6.1.4.1.6757.100.1.1.1.2.1 NAME 'DomainUniqueID' DESC 'A global unique ID' EQUALITY caseIgnoreIA5Match SUBSTR caseIgnoreIA5SubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE ) attributetype ( 1.3.6.1.4.1.6757.100.1.1.1.2.2 NAME 'DomainName' DESC 'Human-readable name' EQUALITY caseIgnoreIA5Match SUBSTR caseIgnoreIA5SubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE ) attributetype ( 1.3.6.1.4.1.6757.100.1.1.1.2.3 NAME 'DomainDescription' DESC 'A description of the domain' EQUALITY caseIgnoreIA5Match SUBSTR caseIgnoreIA5SubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE ) attributetype ( 1.3.6.1.4.1.6757.100.1.1.1.2.4 NAME 'DomainWWW' DESC 'The URL identifying a web page with more information about the domain' EQUALITY caseIgnoreIA5Match SUBSTR caseIgnoreIA5SubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE ) attributetype ( 1.3.6.1.4.1.6757.100.1.1.1.2.5 NAME 'DomainOtherInfo' DESC 'Placeholder to publish info that does not fit in any other attribute. Free-form string, comma-separated tags, (name, value ) pair are example of syntax' EQUALITY caseIgnoreIA5Match SUBSTR caseIgnoreIA5SubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE ) attributetype ( 1.3.6.1.4.1.6757.100.1.1.2.2.1 NAME 'LocationLocalID' DESC 'An opaque identifier local to the associated Service or Domain' EQUALITY caseIgnoreIA5Match SUBSTR caseIgnoreIA5SubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE ) attributetype ( 1.3.6.1.4.1.6757.100.1.1.2.2.2 NAME 'LocationName' DESC 'A human-readable name ' EQUALITY caseIgnoreIA5Match SUBSTR caseIgnoreIA5SubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE ) attributetype ( 1.3.6.1.4.1.6757.100.1.1.2.2.3 NAME 'LocationAddress' DESC 'Street address' EQUALITY caseIgnoreIA5Match SUBSTR caseIgnoreIA5SubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE ) attributetype ( 1.3.6.1.4.1.6757.100.1.1.2.2.4 NAME 'LocationPlace' DESC 'Name of town/city' EQUALITY caseIgnoreIA5Match SUBSTR caseIgnoreIA5SubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE ) attributetype ( 1.3.6.1.4.1.6757.100.1.1.2.2.5 NAME 'LocationCountry' DESC 'Country name' EQUALITY caseIgnoreIA5Match SUBSTR caseIgnoreIA5SubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE ) attributetype ( 1.3.6.1.4.1.6757.100.1.1.2.2.6 NAME 'LocationPostCode' DESC 'Postal code' EQUALITY caseIgnoreIA5Match SUBSTR caseIgnoreIA5SubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE ) attributetype ( 1.3.6.1.4.1.6757.100.1.2.2.7 NAME 'LocationLatitude' DESC 'The position of a place north or south of the equator measured from -90Â° to +90Â° with positive values going north and negative values going south' EQUALITY caseIgnoreIA5Match SUBSTR caseIgnoreIA5SubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE ) attributetype ( 1.3.6.1.4.1.6757.100.1.1.2.2.8 NAME 'LocationLongitude' DESC 'The position of a place east or west of Greenwich, England measured from -180Â° to +180Â° with positive values going east and negative values going west' EQUALITY caseIgnoreIA5Match SUBSTR caseIgnoreIA5SubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE ) attributetype ( 1.3.6.1.4.1.6757.100.1.1.3.2.1 NAME 'ContactLocalID' DESC 'An opaque identifier local to the associated Service or Domain' EQUALITY caseIgnoreIA5Match SUBSTR caseIgnoreIA5SubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE ) attributetype ( 1.3.6.1.4.1.6757.100.1.1.3.2.2 NAME 'ContactURL' DESC 'URL embedding the contact information. The syntax of URI depends on the communication channel' EQUALITY caseIgnoreIA5Match SUBSTR caseIgnoreIA5SubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE ) attributetype ( 1.3.6.1.4.1.6757.100.1.1.3.2.3 NAME 'ContactType' DESC 'Type of contact' EQUALITY caseIgnoreIA5Match SUBSTR caseIgnoreIA5SubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE ) attributetype ( 1.3.6.1.4.1.6757.100.1.1.3.2.4 NAME 'ContactOtherInfo' DESC 'Placeholder to publish info that does not fit in any other attribute. Free-form string, comma-separated tags, (name, value ) pair are example of syntax' EQUALITY caseIgnoreIA5Match SUBSTR caseIgnoreIA5SubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE ) attributetype ( 1.3.6.1.4.1.6757.100.1.1.4.2.1 NAME 'AdminDomainDistributed' DESC 'True if the services managed by the admindomain are considered geographically distributed by the administrators themselves.' EQUALITY booleanMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 SINGLE-VALUE ) attributetype ( 1.3.6.1.4.1.6757.100.1.1.4.2.2 NAME 'AdminDomainOwner' DESC 'Owner of the managed resources' EQUALITY caseIgnoreIA5Match SUBSTR caseIgnoreIA5SubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE ) attributetype ( 1.3.6.1.4.1.6757.100.1.1.5.2.1 NAME 'UserDomainLevel' DESC 'The number of hops to reach the root for hierarchically organized domains described by the composed by association (0 is for the root).' SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 SINGLE-VALUE ) attributetype ( 1.3.6.1.4.1.6757.100.1.1.5.2.2 NAME 'UserDomainManagerEndpoint' DESC 'The Endpoint ID managing the users part of the domain and the related attributes such as groups or roles' EQUALITY caseIgnoreIA5Match SUBSTR caseIgnoreIA5SubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE ) objectclass ( 1.3.6.1.4.1.6757.100.1.1.1 NAME 'GlueDomain' DESC 'A collection of actors that can be assigned with roles and privileges to entities via policies. A domain may have relationships to other domains.' ABSTRACT ) objectclass ( 1.3.6.1.4.1.6757.100.1.1.2 NAME 'GlueLocation' DESC 'A geographical position' STRUCTURAL MUST LocationLocalID MAY ( LocationAddress $ LocationCountry $ LocationLongitude $ LocationPostCode $ LocationName $ LocationPlace $ LocationLatitude ) ) objectclass ( 1.3.6.1.4.1.6757.100.1.1.3 NAME 'GlueContact' DESC 'Information enabling to establish a communication with a person or group of persons part of a domain' STRUCTURAL MUST ContactLocalID MAY ( ContactOtherInfo $ ContactType $ ContactURL ) ) objectclass ( 1.3.6.1.4.1.6757.100.1.1.4 NAME 'GlueAdminDomain' DESC 'A collection of actors that can be assigned with administrative roles and privileges to services via policies. An AdminDomain manages services that can be geographically distributed, nevertheless a primary location should be identified.' STRUCTURAL MUST DomainUniqueID MAY ( LocationPostcode $ AdminDomainDistributed $ AdminDomainOwner $ DomainDescription $ DomainName $ DomainOtherInfo $ DomainWWW ) ) objectclass ( 1.3.6.1.4.1.6757.100.1.1.5 NAME 'GlueUserDomain' DESC 'A collection of actors that can be assigned with user roles and privileges to services or shares via policies' STRUCTURAL MUST DomainUniqueID MAY ( UserDomainLevel $ UserDomainManagerEndpoint $ DomainDescription $ DomainOtherInfo $ DomainName $ DomainWWW ) )

1 0

GLUE 2.0 Spec - draft 39
by Sergio Andreozzi 18 Apr '08

18 Apr '08

Dear all, draft 39 is online: http://forge.ogf.org/sf/go/projects.glue-wg/docman.root.drafts it contains the following changes: 1. fix association between storage resource and data store 2. fix definition of data store 3. added directionality to storageservice2computingservice association I'm in the process of updating the XSD mapping. This is time to start with a rich set of use cases to be described using the current GLUE so that we can validate our concepts on a large number of use cases. Please, spend some of your time on examples. We are collecting them in this page: http://forge.ogf.org/sf/wiki/do/viewPage/projects.glue-wg/wiki/GLUE2XMLSche… Cheers, Sergio -- Sergio Andreozzi INFN-CNAF, Tel: +39 051 609 2860 Viale Berti Pichat, 6/2 Fax: +39 051 609 2746 40126 Bologna (Italy) Web: http://www.cnaf.infn.it/~andreozzi

1 0