Hi all,
Yesterday I tested the changes mandated by the new version of the LDAP
document in a test environment and I didn't see any issue.
I didn't see any bad error in slapd logs, and the objects that were
affected by changes are published as expected.
I attach the latest schema and kindly ask Maria and Paul to test the
impact on their products:
GLUE20.schema.20140508
A list of diffs between the current distributed version of the schema
(2.0rc5) against the new version (2.0rc6) that is included in this email:
distro2.0rc5_diff_2.0rc6.changes
I suggest you check them with some nice editor that colors things up so
you can easily spot differences.
I pushed the source schemas in my git-hub area temporarily, if we're
fine with that I will push it to the official repos:
https://github.com/floridop/LDAPWIP
I would say that we should put recommendations in the release notes that
I added in the README files on git-hub. I didn't do it yet, but the
issues I can imagine we should add are the following:
1) ABSTRACT classes to be in sync with XML realisation:
Objects like Entity, Resource, Share, Policy have been declared ABSTRACT
to be in sync with the XML schema. This means these cannot be
instantiated as is; only their specialization can (i.e. Computing-
Storage- or others like Benchmark etc.) are objects that can be published.
2) Boolean type changed to DirectoryString
This means that if the boolean values that are mandatory in the schema
are not defined, the information providers MUST publish them and MUST
present the value "undefinedvalue"; GFD.147 Appendix B.17.
These are:
ExecutionEnvironment.ConnectivityIn
ExecutionEnvironment.ConnectivityOut
If you spot any problem, let me know.
Regards,
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
==================================================
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, May 6, 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
Meeting materials folder:
: http://redmine.ogf.org/dmsf/glue-wg?folder_id=6585
Proposed agenda:
1) LDAP rendering (JP/Shiraz: 10 minute status update)
Previous action items:
> Agreed to embed the normative LDAP schema in an appendix (based on XML precedence).
> Action item 1: Florido will clarify the wording on Page 6 based on Shiraz Comment[10].
> Action item 2: Florido will upload a new normative schema and e-mail diffs to the list along with a bulleted summary of the changes
> Action item 3: Shiraz/JP will update authors, embed the schema in the appendix, accept all changes, and share with wg for review
> Action item 4: Shiraz/JP will submit new document for public comment after one week of wg comment/discussion
2) Enumerations (Florido: 10 minute status update)
Enumerations process, policies, and guidelines.
Specific proposed new enumerations.
Previous action items:
> Everyone provide feedback thru list on Florido's process document
> Florido will update document with modified format to enable cat'ing of multiple numerations into a single file
3) Cloud extensions (Salvatore, Warren, and others: 70 minute status update)
Discuss two proposed approaches of using new entities (EGI/Salvatore), existing entities (FutureGrid/XSEDE, Warren).
Request Salvatore and Warren each produce lists of benefits and disadvantages of both their own proposed approach and the alternative (placed in above folder).
Suggest we discuss and merge these lists to produce a summary we can use to reach a decision.
Regards,
JP and Shiraz
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
