Fwd: OCCI Platform 1.2 specification draft
Re-forwarding the following message with OCCI Platform specification 1.2 comments that came during the mailman outage. Alan Begin forwarded message: From: Philippe Merle <philippe.merle@inria.fr<mailto:philippe.merle@inria.fr>> Date: December 17, 2015 at 3:55:32 PM CST To: Boris Parak <xparak@mail.muni.cz<mailto:xparak@mail.muni.cz>>, "Sill, Alan" <alan.sill@ttu.edu<mailto:alan.sill@ttu.edu>>, <thijs.metsch@intel.com<mailto:thijs.metsch@intel.com>>, <andrew.edmonds@zhaw.ch<mailto:andrew.edmonds@zhaw.ch>>, <jens.jensen@stfc.ac.uk<mailto:jens.jensen@stfc.ac.uk>>, <Wolfgang.Ziegler@scai.fraunhofer.de<mailto:Wolfgang.Ziegler@scai.fraunhofer.de>>, "jean.parpaillon@inria.fr<mailto:jean.parpaillon@inria.fr>" <jean.parpaillon@inria.fr<mailto:jean.parpaillon@inria.fr>>, <enol.fernandez@egi.eu<mailto:enol.fernandez@egi.eu>>, <aloga@ifca.unican.es<mailto:aloga@ifca.unican.es>>, <sustr4@cesnet.cz<mailto:sustr4@cesnet.cz>>, <michel.drescher@egi.eu<mailto:michel.drescher@egi.eu>>, <David.Wallom@oerc.ox.ac.uk<mailto:David.Wallom@oerc.ox.ac.uk>> Subject: Fwd: OCCI Platform 1.2 specification draft -------- Message transféré -------- Sujet : OCCI Platform 1.2 specification draft Date : Thu, 17 Dec 2015 12:24:10 +0100 De : Philippe Merle <philippe.merle@inria.fr><mailto:philippe.merle@inria.fr> Pour : occi-wg@ogf.org<mailto:occi-wg@ogf.org> Hello all, In the context of the OCCIware project (<http://www.occiware.org>www.occiware.org<http://www.occiware.org>), I implemented the OCCI Platform 1.2 specification draft. This implementation is freely available at <https://github.com/occiware/ecore/tree/master/clouddesigner/org.occiware.clouddesigner.occi.platform> https://github.com/occiware/ecore/tree/master/clouddesigner/org.occiware.clo.... Good news: OCCI Platform 1.2 specification is implementable and already implemented. During the implementation, I saw some typos into the specification draft but also some potential semantics errors. I corrected most of these issues in my copy of the specification draft. See corrections at https://github.com/occiware/occi-wg/commit/c049165ae45d90ca0ad36037df22ce641... About semantics issues: 1) At Line 78, the spec. defines that "ComponentLink Connects an Application instance to a hosting Component or connects two components.". Is it really wanted that a component link could connect two components? If yes, this intention must be explicitly written again in Section 3.3. If no, text "connects two components" must be removed. 2) Figure 1 at Page 4 must be updated (sorry I have not the right software to do the job): - Text "links" must be placed at the right side of the UML association betwen Resource and Link classes. - Text "source" must be placed at the left side of the UML association betwen Resource and Link classes. - Text "(from occi-core)" must be added into the Link class as it is already present in the Resource class. - The attribute 'state.message: String' may be added to the Application class. - The attribute 'state.message: String' may be added to the Component class. - ComponentLink class contains a 'state: Enum' attribute but this attribute is not discussed in Section 3.3 at Page 6. This attribute must be removed from the figure or discussed in Section 3.3. 3) At Line 97, 'application/' must be added into the scheme of actions of the Application kind. At Line 109, 'component/' must be added into the scheme of actions of the Component kind. If not done, then the two start actions (ditto for stop) will have the same identity (scheme+term) then this creates an ambiguity. 4) In Table 2, 4, 6 and 7, the default attribute of each attribute is not defined. Implicitly, I supposed that all these attributes have no default. But it will be better to specify this point explicitly in the OCCI Platform specification. 5) At Line 102, Application must be replaced by Component as this section talks about components. 6) In all other OCCI specification documents, schemes and terms are in lower case: - At Line 108, replace #Component by #component - At Line 116, replace #componentLink by #componentlink - At Line 157, replace #databaseLink by #databaselink 7) Lines 129 and 142, 'the applies attribute' must be replaced by 'the depends attribute'. 8) Figure 4 page 7: - replace 'term = apllication' by 'term = application' (this is just a typo) - replace 'related' by 'depends' two times (In OCCI Core 1.2, related has been replaced by depends and applies) Best regards Philippe Merle Inria
Thanks Alan! These items are no tracked in our board as well. Cheers, -Thijs From: occi-wg [mailto:occi-wg-bounces@ogf.org] On Behalf Of Sill, Alan Sent: Monday, December 21, 2015 7:09 AM To: occi-wg@ogf.org Subject: [occi-wg] Fwd: OCCI Platform 1.2 specification draft Re-forwarding the following message with OCCI Platform specification 1.2 comments that came during the mailman outage. Alan Begin forwarded message: From: Philippe Merle <philippe.merle@inria.fr<mailto:philippe.merle@inria.fr>> Date: December 17, 2015 at 3:55:32 PM CST To: Boris Parak <xparak@mail.muni.cz<mailto:xparak@mail.muni.cz>>, "Sill, Alan" <alan.sill@ttu.edu<mailto:alan.sill@ttu.edu>>, <thijs.metsch@intel.com<mailto:thijs.metsch@intel.com>>, <andrew.edmonds@zhaw.ch<mailto:andrew.edmonds@zhaw.ch>>, <jens.jensen@stfc.ac.uk<mailto:jens.jensen@stfc.ac.uk>>, <Wolfgang.Ziegler@scai.fraunhofer.de<mailto:Wolfgang.Ziegler@scai.fraunhofer.de>>, "jean.parpaillon@inria.fr<mailto:jean.parpaillon@inria.fr>" <jean.parpaillon@inria.fr<mailto:jean.parpaillon@inria.fr>>, <enol.fernandez@egi.eu<mailto:enol.fernandez@egi.eu>>, <aloga@ifca.unican.es<mailto:aloga@ifca.unican.es>>, <sustr4@cesnet.cz<mailto:sustr4@cesnet.cz>>, <michel.drescher@egi.eu<mailto:michel.drescher@egi.eu>>, <David.Wallom@oerc.ox.ac.uk<mailto:David.Wallom@oerc.ox.ac.uk>> Subject: Fwd: OCCI Platform 1.2 specification draft -------- Message transféré -------- Sujet : OCCI Platform 1.2 specification draft Date : Thu, 17 Dec 2015 12:24:10 +0100 De : Philippe Merle <philippe.merle@inria.fr><mailto:philippe.merle@inria.fr> Pour : occi-wg@ogf.org<mailto:occi-wg@ogf.org> Hello all, In the context of the OCCIware project (www.occiware.org<http://www.occiware.org>), I implemented the OCCI Platform 1.2 specification draft. This implementation is freely available at https://github.com/occiware/ecore/tree/master/clouddesigner/org.occiware.clo.... Good news: OCCI Platform 1.2 specification is implementable and already implemented. During the implementation, I saw some typos into the specification draft but also some potential semantics errors. I corrected most of these issues in my copy of the specification draft. See corrections at https://github.com/occiware/occi-wg/commit/c049165ae45d90ca0ad36037df22ce641... About semantics issues: 1) At Line 78, the spec. defines that "ComponentLink Connects an Application instance to a hosting Component or connects two components.". Is it really wanted that a component link could connect two components? If yes, this intention must be explicitly written again in Section 3.3. If no, text "connects two components" must be removed. 2) Figure 1 at Page 4 must be updated (sorry I have not the right software to do the job): - Text "links" must be placed at the right side of the UML association betwen Resource and Link classes. - Text "source" must be placed at the left side of the UML association betwen Resource and Link classes. - Text "(from occi-core)" must be added into the Link class as it is already present in the Resource class. - The attribute 'state.message: String' may be added to the Application class. - The attribute 'state.message: String' may be added to the Component class. - ComponentLink class contains a 'state: Enum' attribute but this attribute is not discussed in Section 3.3 at Page 6. This attribute must be removed from the figure or discussed in Section 3.3. 3) At Line 97, 'application/' must be added into the scheme of actions of the Application kind. At Line 109, 'component/' must be added into the scheme of actions of the Component kind. If not done, then the two start actions (ditto for stop) will have the same identity (scheme+term) then this creates an ambiguity. 4) In Table 2, 4, 6 and 7, the default attribute of each attribute is not defined. Implicitly, I supposed that all these attributes have no default. But it will be better to specify this point explicitly in the OCCI Platform specification. 5) At Line 102, Application must be replaced by Component as this section talks about components. 6) In all other OCCI specification documents, schemes and terms are in lower case: - At Line 108, replace #Component by #component - At Line 116, replace #componentLink by #componentlink - At Line 157, replace #databaseLink by #databaselink 7) Lines 129 and 142, 'the applies attribute' must be replaced by 'the depends attribute'. 8) Figure 4 page 7: - replace 'term = apllication' by 'term = application' (this is just a typo) - replace 'related' by 'depends' two times (In OCCI Core 1.2, related has been replaced by depends and applies) Best regards Philippe Merle Inria Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Christian Lamprechter Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928
participants (2)
-
Metsch, Thijs -
Sill, Alan