Proposed agenda:
1) LDAP rendering: assess final wg comments and votes and perhaps forward for public comment Previous:
ACTION 1: JP/Shiraz will call for a working group e-mail vote by July 25 to release LDAP rendering document for public comment. Changes should be submitted as change tracked word updates. NOTE: Given that the call for vote will not go out till July 23, WG chairs will extend the vote thru July 31st.
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.
2) Enumerations: approve enumerations process document Previous:
We discussed managing separate enumeration files for each enumeration and distributing a shell script to download and concatenate all of them. This will eliminate the overhead of having to maintained a merged file. Andrew (BES/JSDL) will submit some requested enumerations. Will also submit a request for a new enumeration type coprocessor that we will probably want to include in GlUE 2.1. He wants us to figure out what entity it belongs in within the abstract information model. Discussed requesting for volunteers thru e-mail list to work on missing enumerations. 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
3) Cloud Extensions: compare benefits and disadvantages of both approaches Previous:
ACTION 1: Shiraz/JP will call for an e-mail vote on using GLUE 2.1 for interoperable clouds. ACTION 2: Salvatore will include new Horizon 2020 requirements in the draft 2.1 specification. ACTION 3: Salvatore will call for an e-mail vote to approve GLUE 2.1 for release for public comment, and request for non-disruptive additions/corrections to be applied before releasing for public comment. We plan to release GLUE 2.1 with cloud support for public comment around December and (possible) OGF 43 in London. Discussed whether XSEDE produce a 2.0 community profile? Opinions: fine either way. Perhaps a community practice isn't necessary if XSEDE's implementation is public (which it will be). 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
4) JSON: continue rendering discussions, discuss next steps. Previous:
ACTION 1: Warren will cleanup document and schema (including dates) and send draft to working group for review and e-mail vote on releasing for public comment. If working group approves release for public comment: ACTION 2: Shiraz will export draft to word, enable change tracking, and apply OGF formatting for release for public comment. Public comment announcement will include details of existing and planned implementations. Discussed creating a wiki page with implementor details pointing to github, mentioning relevant tools, and other guidelines to help implementors. Agreed to publish to schema.ogf.org, for example: http://schemas.ogf.org/glue/2013/05/spec_2.0_r1/Activity.json The schema path date will be the month of release for public comment. In appendix where JSON schema documents are included, precede each schema document with the URL to the above schema.ogf.org publishing location.
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.
5) Future meetings In 2 weeks? December 12 morning in London
London meeting will be FREE Availability: - Shiraz available till 11:30 or Noon - David not available unless he re-arranges - Stephen will be available - Florido will teleconference available till 1. - JP arriving at 7 AM to Heathrow, available 8:30 thru end of day - Paul, is likely to be available - Warren, unlikely because of workshop later in the day
Regards,
JP and Shiraz