- glue-wg - lists.ogf.org

New version of GLUE 2.1 draft
by Salvatore Pinto 19 Sep '14

19 Sep '14

Dear GLUErs, attached to this mail you will find the latest version of the draft for GLUE 2.1, with the inclusion of the Cloud entities. Respect to the last draft sent, I have performed the following changes (all changes/additions are highlighted in yellow in the document): - I reviewed the representation of the virtual resources available to the VM, and decided to adopt the OpenStack model+GPU, so RAM,CPU,GPU,Network (public or private),OS Disk and Ephemeral disk. This model is the more general I could find between the open source middlewares and should fit almost all of them. - I reviewed the representation of service pricing (costs). The overall pricing issue is quite complex, and a comprehensive standardization of pricing schemes is way out of our scope. Anyway, for brokers and markeplaces to consume this information and select the "best" site for the user, I have included a simple representation via price entities which are associated to the VM image disk and resource. The final price for the VM is calculated as the sum of all the associated price elements (eg. RAM, CPU, OS License, etc...). - I added SLA (service level agreements) related to the cloud service. This is important for brokers (eg. you may select the site with lower price, but only if it provides the SLA you need). I did not standardize SLA representation, but just added a string to represent the SLA, which can be an URL or a short nametag (eg. 99% Avaliability, best effort, etc...). - I added a service ToC parameter as an URL reference to the ToC per the site. When you program a cloud broker, you need your user to accept the ToC of each of the cloud providers at first use. I think GLUE is a nice way for the broker to access the ToC of all the different sites in an uniform way. - I added the possibility to specify pre-set access credentials for the VM images. This information is relevant to the broker system if cloud-init is not supported by the provider or the image. Cheers, Salvatore.

4 4

Call for minor non-distruptive updates to GLUE 2.0
by Salvatore Pinto 08 Sep '14

08 Sep '14

Dear GLUErs, since we are going to revision GLUE 2.0 to GLUE 2.1, I would like to ask the mailing list to point me to some changes which, in your opinion, should be incorporated in this revision. I will collect these changes and then organize a discussion for the GLUE WG meetings. Changes submitted shall be NOT-DISTRUPTIVE and ensure full retro-compatibilty with GLUE 2.0. Example of such changes may be fixing of typos, making description of attributes more clear (without changing the attribute meaning), updating enumerations by adding new fields, etc... >From my side, beside, of course, the addition of the cloud entities, I would like to propose: #1. Put a link to the Open Enumerations procedure. I propose to add a short text with the link in appendix B (Data types), explaining that, before defining a new enumerations, it is recommended to apply the Open Enumerations best practices. #2. Fix the broken link to VOMS website ( http://voms.forge.cnaf.infn.it/) I propose to replace it with the WikiPedia link ( http://en.wikipedia.org/wiki/VOMS) which is the closest one to a "persistent identifier" I can find, or remove it entirely. #3. Add to EndpointHealthState_t (closed enumeration) a state named "downtime", this would be much simpler to signal current downtime status to the users or cloud brokers than via the DowntimeStart/End times. #4. Add GPU resources to the Execution Environment. This can be important for the EGI-ENGAGE and other sister projects in H2020, were we are planning to integrate GPGPU computing in both Cloud and Grid. #5. Add to the StorageShare a Maximum and Minimum object (file) size allowed. THis would be of interest in the cloud, there the object stored can be for example an additional virtual disk which size can be restricted between given boundaries (eg. for most of the EGI FedCloud sites from 1GB to 100GB). #6. For the storage elements descriptions, replace the word "file" with "data object". The idea is that the storage service may support multiple data objects types (eg. files, images, documents, etc...). The kind of objects supported will be included the service capabilities. Cheers, Salvatore.

5 9

Fwd: Re: Call for minor non-distruptive updates to GLUE 2.0
by Paul Millar 08 Sep '14

08 Sep '14

Sorry, I mistakenly replied only to Alan, but I meant to reply to the list. -------- Forwarded Message -------- Hi Alan, On 08/09/14 15:25, Sill, Alan wrote: >> On Sep 8, 2014, at 2:13 PM, Paul Millar <paul.millar(a)desy.de> >> wrote: >> 1. create a registry where people can add CA bundle along with >> some canonical name, > > This type of registry, if created, would be meaningless without > secure links to the CA bundles and an accompanying description of > policy for each. This in fact is what the IGTF provides for each of > its published bundles. I'm not sure what you mean by "meaningless", but certainly the registry entry for some CA-bundle should allow a user to navigate to the list of certificates and a description of the bundle's policy. (Be aware that this is not a security-related issue: the published information only provides a hint whether or not a client's X.509 certificate is from a CA the server trusts.) > TACAR maintains a list of individual CAs along with secure links to > download their individual CA trust anchor files, but only for a > subset of academic CAs. > > I suggest generic language that refers to both as examples. My point is that we shouldn't include these kinds of examples; they're point to a problem in the GLUE document that can be fixed for GLUE 2.1 The problem is that we (the people writing GLUE 2.x documents) might know what "IGTF-SLCS" should mean but unless it's written down we risk: a. someone will use an incompatible value to refer to the same thing ("igtf slcs", "urn:ogf:glue:ca-bundles:igtf:slcs", ...) b. someone won't understand what "IGTF-SLCS" means. HTH, Paul.

1 0

VOTE by 7/31: GLUE 2.0 LDAP Rendering release for public comment
by JP Navarro 02 Sep '14

02 Sep '14

GLUE Working Group: As agreed to at OGF 41. By July 31, please review the following document and reply with a vote to APPROVE or REJECT to release for public comment. http://redmine.ogf.org/dmsf_files/13302?download= If you vote to REJECT, please summarize your concerns. If you have minor editorial corrections or improvements, please reply and attach your change tracked edits and appending your initial to the file-name. Regards, JP and Shahbaz

6 11

GLUE WG sessions at UCC 2014?
by JP Navarro 07 Aug '14

07 Aug '14

Neither Shiraz or myself will be able to attend OGF 42 in September in London. OGF is considering having meetings during or immediately after UCC 2014 December 8-11 in London. http://computing.derby.ac.uk/ucc2014/ We have discussed having the GLUE 2.1 abstract data model with cloud support ready for vote and release for public comment at that time. That would be a great time a public presentation of the new GLUE 2.1 cloud data model. How many of you would be able to attend GLUE session in person at UCC 2014 December 8-12? Thanks, JP

2 1

updated GLUE2 JSON schema
by Warren Smith 01 Aug '14

01 Aug '14

Hey - I've updated the JSON schema and examples (https://github.com/OGF-GLUE/JSON) based on our last discussions. Please take a look and give it a try. There is enough detail in there that I wouldn't be surprised if there are a few mistakes. The main change is that at least one direction of every association must be represented in a document conforming to the schema. If there is no association to represent, the attribute must still be present, but it will have null or an empty list as the value. I think this was the last issue that has come up in our discussions. So, we'll be finalizing the associated rendering document in the next few weeks for review. What I propose to do (which I think agrees with the discussions we had at OGF) is once we approve the schema and rendering document, I'll update the dates in the schema to match that approval date, and then we can upload the document and the schema to OGF for public comment. Warren

1 0

VOTE by 8/1: GLUE 2.1 for describing cloud resources?
by JP Navarro 01 Aug '14

01 Aug '14

GLUE Working Group: We have been discussing two options for using the GLUE schema to describe cloud services. You may review these options here: - http://redmine.ogf.org/dmsf_files/13294?download= By August 1, please vote for one of the following options: 1) Use GLUE 2.0 with a Community Practice Profile that details how to describe cloud infrastructure using the existing 2.0 entities 2) Develop GLUE 2.1 adding new Cloud Computing entities (would be 100% backward compatible with GLUE 2.0 for non-Cloud entities) For reference, a preliminary GLUE 2.1 Specification is available here: - http://www.ogf.org/pipermail/glue-wg/2014-January/001527.html Regards, JP

9 35

Redmine or forge?
by Salvatore Pinto 31 Jul '14

31 Jul '14

Hi all, I saw around that some reference for GLUE documents points to GridForge (https://forge.ogf.org/sf/docman/do/listDocuments/projects.glue-wg/docman.ro…) eg. the one in https://github.com/OGF-GLUE/LDAP , while here in the mailing list we refer usually to http://redmine.ogf.org/dmsf/glue-wg . What is the difference between the two? Which one has the latest info? Cheers, Salvatore. -- Salvatore Pinto Cloud Technologist, EGI.eu e-mail: salvatore.pinto(a)egi.eu skype: salvatore.pinto0 Science Park 140, Amsterdam, The Netherlands

4 6

Notes: GLUE WG sessions at OGF 41
by JP Navarro 28 Jul '14

28 Jul '14

Notes from July 16-17, 2014, OGF 41 GLUE WG sessions. LDAP rendering -------------- 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. JSON rendering -------------- 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. Describing Clouds ----------------- 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). Enumerations ------------ 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. Miscellaneous ------------- Peter Solagna is replacing Salvatore in EGI GLUE effort. There is an OGF 42 in London, September 8-13. There may be an OGF 43 also in London, the second week in December. If anyone has a preference for a face-to-face in September OGF 42 or possible December OGF 43, please let the group know. Regards, JP

1 1

Maintaining http://schemas.ogf.org/glue/ content
by JP Navarro 26 Jul '14

26 Jul '14

Andre, What is the proper way for the GLUE WG to manage files under http://schemas.ogf.org/glue/? We want to publish new JSON schemas. Thanks, JP

2 1