[glue-wg] Notes: GLUE WG teleconference, Tuesday, March 25, 2014

[Navarro, John-Paul F.]

> Proposed agenda:
> 
> 1) Cloud extensions (Salvatore: 10 minute status update)
> 
> OGF 40 ACTION: The group agreed to request that the GLUE Specification v 2.1 submitted with Cloud extensions be RE-SUBMITTED by the authors with change tracking enabled so that all the changes with respect to the current Specification v2.0 are clearly visible.  All other editing by anyone in the group should be change tracked until the group approves, submits, and officially releases v 2.1.

Action items:
1) Salvatore to send draft with changes tracked to the list
2) JP/Shiraz to post to appropriate Redmine location
3) Salvatore to collect other proposed changes, thru the e-mail list
4) Future e-mails referencing the draft will point to the document stored in the appropriate Redmine location

Motivation for a separate set of cloud entities:
- Enables clouds to evolve on their own
- Doesn't change the structure and definition of compute entities
- Currently the cloud object(s) are quite different from the compute object(s), cloud extends abstracts
- There was a new "cost" abstract entity, but no change to existing ones
Warren is already publishing cloud using compute entities (not storage).

Action:
5) Warren will post to list information on his use of compute entities for clouds and areas he sees/needs improvement
6) Salvatore will post the list the main factors that motivated separate entities rather than leveraging compute entities
7) Salvatore will contact CERN on whether they want to participate in federated cloud discovery effort in the GLUE WG
8) Shiraz/JP will make discussing items 5) and 6) above the main topic our next GLUE WG call

EVERYONE: Please reply if you are interested in participating in a discussion of 5) and 6) above and are not available April 8 or 25 at 15:30 Central European time/8:30 AM Central US.

> 2) LDAP rendering (JP/Shiraz: 10 minute status update)
> OGF 40 ACTION: The group agreed that the final editing for comprehensibility should be done by JP and Shiraz: 1. Make sure the purpose of the DIT Appendix is clear and who the target audience (people writing implementation and/or users) 2. Make it clear that the main purpose of the document is to define the LDAP rendering of the schema. Reference to the schema should be included, perhaps in an Appendix. 3. JP and Shiraz should report back to working group with a change tracked version for final review

If the document is approved there will be implementation changes.
Action:
9) Shiraz/JP to review LDAP document by next meeting.

> 3) Enumerations (All: 1 hour)
    Salvatore has produced a draft process, policies, and guidelines document.
    We discussed some aspects of the document and then applied it the process to some proposed Enumeration changes.
Action:
10) Everyone review and comment thru the glue list to the document attached here:
    http://redmine.ogf.org/dmsf/glue-wg?folder_id=6583
    
>  BES/JSDL related enumerations and attributes needs (Andrew)

Future meetings all at 15:30 Central Europe, 8:30 Central US.

Thanks,

JP