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
Greetings GLUE WG,
Our next GLUE WG teleconference will be:
: Tuesday, April 8, 2014
: 15:30-16:30 Central Europe, 8:30-9:30 AM US Central
Teleconference and screen sharing:
: https://webconf.vc.dfn.de/ogf-glue-wg/ (Adobe Connect)
: Login as Guest using your real name
NOTE: we only have one hour!
Proposed agenda:
1) Cloud extensions (Salvatore, Warren)
March 25th action items:
> 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
Warren posted glue2 cloud examples March 26.
If Salvatore is available we will discuss the factors that motivated separate entities and attempt to reach consensus.
2) LDAP rendering
Review Shiraz's and JP's feedback on rendering document and agree on changes to final document:
http://redmine.ogf.org/dmsf/glue-wg?folder_id=6569
3) Enumerations (Florido)
Review enumeration process
Recent recent enumerations discussions
Next steps
Regards,
JP and Shiraz
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.
Hi all,
Today, while fixing the enumerations as decided last time, I found myself facing two problems:
Problem 1) how to communicate what-obsoletes-what or what-is-recommended-instead. In short, how does a consumer find out what to use if a string she's using is deprecated.
I'll give you an example with these records:
IntefaceName_t | Description | Status |
=============================================================================
org.globus.gram | job submission service for Globus | Recommended |
-----------------------------------------------------------------------------
GRAM5 | job submission service for Globus version | Deprecated |
| 5.x (GRAM5) | |
Problem: I search for GRAM5, i see is deprecated, how do I find out what to use instead?
Solution: My solution will be to enrich the CSV this way:
IntefaceName_t | Description | Status | Recommended | Deprecates |
============================================================================================================
org.globus.gram | job submission service for Globus | Recommended | | GRAM5 |
------------------------------------------------------------------------------------------------------------
GRAM5 | job submission service for Globus version | Deprecated | org.globus.gram | |
| 5.x (GRAM5) | | | |
that is, adding two fields (that can be multilined)
This will also allow me to speedup the process of reviewing existing InterfaceName_t overlaps, as I will send
to the list a list of services with multiple names with a proposed deprecated/recommended set.
Problem 2)
Warren once requested me to provide a single file containing all the enumerations. The problem with
the current CSV is that, if I just merge them, one will loose the reference to what Enumeration Type
the merged document refers to. Thus, I need to add an additional field with the enumeration type name for that.
Two ways:
Solution a) Keep the single files as they are, and generate a merged file.
If you consider InterfaceName in Problem 1 above, an example of merged file
including ServiceType_t would be:
EnumerationType | EnumerationName | Status | Recommended | Deprecates |
================================================================================
InterfaceName_t | GRAM5 | Deprecated | org.globus.gram | |
--------------------------------------------------------------------------------
ServiceType_t | egi.GRIDVIEW | Recommended | | |
Solution b) Change all existing files to the above format.
I would prefer solution b), as it makes consistent to use either the big file or
a sigle file with the same parser. There is no strictural difference between the
partial files and the big file. This will require also a change in the document
I wrote on enumerations.
Your opinions are very welcome. If no objections I will follow the solutions
shown up here and document all of them in the changelog file.
Cheers,
Florido
--
==================================================
Florido Paganelli
ARC Middleware Developer - NorduGrid Collaboration
System Administrator
Lund University
Department of Physics
Division of Particle Physics
BOX118
221 00 Lund
Office Location: Fysikum, Hus B, Rum B313
Office Tel: 046-2220272
Email: florido.paganelli(a)REMOVE_THIShep.lu.se
Homepage: http://www.hep.lu.se/staff/paganelli
==================================================
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
