Sorry it took over 2 months to get these MINUTES I had drafted out. Glad I had a draft otherwise I would not have remembered what we discussed. JP
Proposed agenda:
Brief updates followed by a more detailed discussion of proposed cloud extensions.
1) LDAP rendering: assess final wg comments and votes and perhaps forward for public comment Previous:
Action: Florido will send LDAP schema to merge into document, recommend publish path Action: JP/Shiraz will merge Florido's 9/2/2014 comments, LDAP document and release for public comment Agreed that we would publish the LDAP compiled schema at a specific URL Action: JP to confirm schemas.ogf.org versus www.ogf.org/schemas/ (prefer schemas.ogf.org) CONFIRMED that we can use schema.ogf.org/ to publish LDAP and JSON schema We do not think there will be technical conflicts for XML, LDAP, and JSON schemas co-existing under the same URL namespace. http://www.ogf.org/documents/GFD.84.pdf defines standard XML namespace. OGF doesn't have equivalent standards for LDAP or JSON.
Schema will be published as "*.schema.ldap" Shiraz/JP review our main wiki page and make sure there are links to all the published schemas.
2) Enumerations: approve enumerations process document Previous:
Florido posted script to merge, it's on Github. David volunteers to help manage enumerations, including add missing enumerations. We need define the enumerations described in GFD.147. ACTION: Warren will post proposed job state enumerations from XSEDE ACTION: David/Warren/Shiraz will explore Git tools/ pull requests for maintaining enumerations and propose changed enumeration management process documentation
No updates.
3) Cloud Extensions: compare benefits and disadvantages of both approaches Previous:
Our next meeting on November 25 will focus on GLUE 2.1 Cloud changes We discussed extensively what we mean by compatibility between GLUE 2.0 and 2.1. No conclusion reached and needs to be further discussed. We didn't have time to discuss Paul's proposal to add a View attribute in 2.1 David will explore pricing policies in the context of GLUE2 and OGF SLA (WS-Agreement, GRAP) working group
Terminology: Call this GLUE 2.1 specification, 100% compatible with 2.0 with additional optional cloud extensions
4) JSON: continue rendering discussions, discuss next steps. Previous:
JSON schema is ready for WG review before release for public comment. ACTION: Warren will post schema pointer to the working group this week, we will vote on 25th to release for public comment.
Moved to release for public comment after correcting schema reference URL. XSEDE is implementing JSON GLUE2 David funding supports his work on XML and JSON UNICORE implementing REST services and may implement JSON if their is a need Shiraz/JP will review wiki page for tools and/or deployments
5) Future meetings Discuss December 12th meeting in London.
Who will present: JP, Shiraz, David?, Stephen?, Salvator (remote), Warren (not available) JP, Who will be present and responsible for the Cloud Schema Peter Soladana Greater priority early next year Not sure who could attend December 12 2.1 high-level approach Actual extensions themselves We were going to do GLUE 2.1
Regards,
JP and Shiraz