March 2014 - glue-wg - lists.ogf.org

glue2 cloud examples
by Warren Smith 17 Jun '14

17 Jun '14

Hi all, I put some examples of how I'm representing an IaaS cloud using GLUE 2 into https://github.com/OGF-GLUE/JSON/tree/master/examples. Look for the files ending in openstack.json and the file images.json. I use a few extensions, but not very many. My approach is: Instance/Virtual Machine - ComputingActivity Physical Node - ExecutionEnvironment Virtual Machine Image - ApplicationEnvironment/Handle I haven't done anything with storage at this point, but my approach would be to handle an object or image store the same as a shared/parallel file system. I also haven't done anything related to describing virtual networks - GLUE 2 doesn't have much support for describing networks in general. VLANs, overlay networks, etc. are used outside of cloud environments as well as in cloud environments, so I don't know if there would be any need for separate entities/schemas for cloud vs non-cloud environments. Warren

4 20

New Endpoint and Service types
by stephen.burke＠stfc.ac.uk 08 Apr '14

08 Apr '14

Hi, The QCG project (http://www.qoscosgrid.org/trac/qcg) is implementing GLUE 2 publication and would like to use the following EndpointInterfaceName values: org.qcg.broker - QCG-Broker web service interface org.oasis.notification - OASIS WS-Notification standard and ServiceTypes: org.qcg.computing - QosCosGrid computing element org.qcg.notification - QosCosGrid notification broker org.qcg.broker - QosCosGrid metacheduling service Can we add them to the relevant lists? The people in CC should be able to provide more information if necessary. Stephen -- Scanned by iCritical.

7 57

GLUE WG teleconference, Tuesday, March 25, 2014
by Navarro, John-Paul F. 04 Apr '14

04 Apr '14

Greetings GLUE WG, Based on a preferences expressed by some, our next GLUE WG teleconference will be: : Tuesday, March 25, 2014 : 15:30-17:00 Central Europe, 8:30-10:00 AM US Central Teleconference and screen sharing: : https://webconf.vc.dfn.de/ogf-glue-wg/ (Adobe Connect) : Login as Guest using your real name 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. 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 3) Enumerations (All: 1 hour) Enumerations process, policies, and guidelines. Specific proposed new enumerations. BES/JSDL related enumerations and attributes needs (Andrew) Regards, JP and Shiraz

4 9

Notes: GLUE WG session at OGF 40
by Navarro, John-Paul F. 25 Mar '14

25 Mar '14

Notes from the Wednesday January 15, 2014, OGF 40 GLUE WG session. Describing Clouds ----------------- We revisited the debate on whether Cloud infrastructure should be described using the existing HPC/Grid Compute entities, using new custom Cloud entities that follow the conceptual model as closely as possible, of with a hybrid. Although we recognize there are many similarities, the consensus was that Clouds will benefit from the freedom to describe what they need independently of HPC/Grid at least for the next few years as cloud continue to rapidly evolve. If at some future point it became clear that HPC/Grid and Cloud were very similar and could be merged, that could happen in the context of GLUE 3, whenever that happens. We recognized that naming in the HPC/Grid data models would have to be further generalized if merging happens. Some differences noted between HPC/Grid and Cloud are that: HPC/Grid ApplicationHandle and ApplicationEnvironment have no equivalent in Cloud, and CloudComputeImage has no equivalent hp HPC/Grid. 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. Enumerations ------------ We discussed our current enumerations, ServiceType and InterfaceName, and the proposed change process circulated just prior to the meeting. We anticipate the need to use the same process to maintain all other Enumerations relevant to GLUE. We noted that the group has agreed to publish approved Enumerations lists is CSV format so that they are software consumable. We agreed to discuss and possibly approve enumerations and the enumeration process at our next call currently scheduled for January 28. LDAP rendering -------------- Difference between Stephen and Florido have now been resolved. 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 BES/JSDL update --------------- Andrew shared a preview of the aspects of GLUE that are being adopted by BES/JSDL. Andrew was going to present that material in separate BES/JSDL OGF 40 sessions. ACTION: Andrew will submit 5 Enumeration requests to the GLUE list. Finally, if anyone else that was present remembers other significant discussions please reply and share them with the group. Regards, JP

5 8

guse.ws-pgrade SE type request
by david.meredith＠stfc.ac.uk 25 Mar '14

25 Mar '14

Dear all, EGI/GOCDB has had a new service type request for 'guse.ws-pgrade' (submitted on behalf WS-PGRADE collaboration). We would also like to agree on this service type for the GLUE2 enum list[1]. FYI: 'gUSE' represents the whole service ecosystem, including WS-PGRADE. There are other components in gUSE (DCI Bridge, WFI) that we expect will be requested later. Can we add this to the agenda for tomorrow's meeting for approval? Cheers, David https://github.com/OGF-GLUE/Enumerations/blob/master/ServiceType_t.csv ========================== David Meredith Scientific Computing Dept Daresbury Laboratory Tel: +44 (0) 1925 603762 Fax: +44 (0) 1925 603100 (Site) Email: david.meredith(a)stfc.ac.uk Skype name: davidismeredith -- Scanned by iCritical.

3 3

Next GLUE WG meetings, March 12 and/or 25?
by Navarro, John-Paul F. 11 Mar '14

11 Mar '14

Greetings GLUE WG, Shiraz and I would like to offer our apologies for the extended GLUE WG meeting holiday, and for not being able to attend OGF-40 in Oxford. It's time to restart our work. We propose two meetings: 1) Wednesday, March 12 at 4 PM Central Europe/9 AM US Central (as an exception to our usual Tuesday) 2) Tuesday, March 25 at the usual time Please reply if you are a regular teleconference participant informing the group which of the above dates you are available. Based on participant availability we will have one or both of these meetings. Proposed agenda for our next meeting: 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. 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 3) Enumerations (All: 1 hour) Enumerations process, policies, and guidelines. Specific proposed new enumerations. BES/JSDL related enumerations and attributes needs (Andrew) 4) Can we move future meetings to start 30 minutes sooner? (5 minutes) 3:30-5 PM Central Europe 8:30-10 AM US Central Any other suggested topics? Regards, JP and Shiraz

4 3

Update WebDAV proposal
by Paul Millar 06 Mar '14

06 Mar '14

Hi all, Here's an updated version of the proposal: --- A service that supports HTTP or any extension based on HTTP MAY publish StorageAccessProtocol objects to represent this. If a StorageAccessProtocol object is published to represent HTTP access then the Type SHOULD|MUST be 'http'. If a StorageAccessProtocol object is published to represent WebDAV access then the Type SHOULD|MUST be 'webdav'. When publishing an Endpoint that supports HTTP (or any extension based on HTTP) without encryption then the URL SHOULD start 'http://'. If an Endpoint the endpoint supports HTTP (or any extension based on HTTP) with SSL or TLS encryption then the URL SHOULD start 'https://' If the endpoint supports WebDAV then an InterfaceExtension of 'http://www.ietf.org/rfc/rfc4918.txt' SHOULD be published. --- Is this any better? Cheers, Paul.

2 1