Present: Florido, Stephen, Shiraz, Warren, JP Meeting notes: 1) LDAP rendering: public comment is closed, discuss next steps
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.
Agreed on the following public schema URL: https://schemas.ogf.org/glue/2014/07/GLUE20.schema.ldap Action (JP): Request GFD number <NNN> So that we now the final spec url: http://www.ogf.org/documents/GFD.<NNN>.pdf Action (JP/Florido): Add spec URL to schema and schema URL to spec; add final schema to spec AGREED: Proceed to Final Review with the above changes
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
Action (Shiraz): Update enumeration management document with Git process AGREED: Group approves promoting InterfaceName_t from draft to official. Action (Florido): Update enumerations as discussed on the call and check-in to Git as official. Action (Florido): Discuss clashing names and how to resolve with David and post what they decide to the list.
3) Cloud Extensions: Do we have champions to move forward with GLUE 2.1? Champions: Francisco Brasileiro and Abmar Barros from Federal University of Campina Grande - www.ufcg.edu.br Peter Solagna and anyone else from EGI? 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
Action (JP/Shiraz): Ask Peter if EGI is ready to resume the lead on GLUE 2.1 If EGI is not ready we will ask Francisco and Abmar if they are willing to take the lead with support the rest of the WG.
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
AGREED: Release it for public comment. Action (JP/Shiraz): Submit it for public comment. Warren shared recent JSON rendering efforts. Shared bindings he developed that should be very useful to developers. Shiraz volunteered to upgrade Warren's bindings to Maven.
5) Future meetings Should we meet at OGF44 co-located with the EGI Conference 2015 May 18-22, 2015, in Lisbon, Portugal?
Action (JP): If Peter and EGI are ready to take the lead ask if a face-to-face meeting at OGF44 will be useful. Otherwise, no face-to-face meeting at OGF44. We agreed that our next meeting would be May 12. Regards, JP and Shiraz