Hello Philippe,
thank you!
I will add these to our Trello board for discussion.
Cheers, Boris
On Fri, Dec 18, 2015 at 4:51 PM, Philippe Merle <philippe.merle(a)inria.fr> wrote:
> Hello,
>
> In the context of the OCCIware project (www.occiware.org) I implemented the
> OCCI Infrastructure 1.2 specification draft.
> Good news: OCCI Infrastructure 1.2 specification is implementable.
>
> During the implementation, I saw some typos into the specification draft but
> also some potential semantics issues:
>
> 1) Typos and minor semantics issues are corrected in
> https://github.com/occiware/occi-wg/commit/ce730cb74428d93a8bafb0b8b033b9d6…
>
> 2) In Figure 1 page 4:
> - the type of occi.storage.size attribute is int when it is Float in
> Table 8 page 8.
> - there is an occi.compute.speed attribute which is not present in Table
> 3 page 5.
> - the occi.compute.share attribute of Table 3 page 5 is not present.
> - *.state.message attributes are not present.
>
> 3) Figure 2 page 6 does not contain the new save action, i.e., a transition
> from active state to active state.
>
> 4) The default of attributes is not explicitly defined in Table 5, 8, 10,
> and 12.
> Especially, the default value of *.state attributes must be defined, it
> could be defined to inactive.
>
> 5) In Figure 10 page 12, there are two occi.compute.speed attributes. But
> this attribute has been removed from Table 3.
>
> 6) At Line 262 and 272, it seems that the schema should contain
> 'infrastructure/' in order to be coherent with other schemas defined in this
> specification.
>
> 7) In Table 14, occi.compute.userdata must be immutable (not mutable) when
> reading the associated description ("It cannot be updated").
>
> 8) Page 17, the item "Removed occi.compute.speed attribute to Compute."
> should be added.
>
> Hoping this could help to improve in progress OCCI 1.2 specifications.
>
> Best regards
> Philippe Merle
> Inria
>
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(a)inria.fr<mailto:philippe.merle@inria.fr>>
Date: December 17, 2015 at 3:55:32 PM CST
To: Boris Parak <xparak(a)mail.muni.cz<mailto:xparak@mail.muni.cz>>, "Sill, Alan" <alan.sill(a)ttu.edu<mailto:alan.sill@ttu.edu>>, <thijs.metsch(a)intel.com<mailto:thijs.metsch@intel.com>>, <andrew.edmonds(a)zhaw.ch<mailto:andrew.edmonds@zhaw.ch>>, <jens.jensen(a)stfc.ac.uk<mailto:jens.jensen@stfc.ac.uk>>, <Wolfgang.Ziegler(a)scai.fraunhofer.de<mailto:Wolfgang.Ziegler@scai.fraunhofer.de>>, "jean.parpaillon(a)inria.fr<mailto:jean.parpaillon@inria.fr>" <jean.parpaillon(a)inria.fr<mailto:jean.parpaillon@inria.fr>>, <enol.fernandez(a)egi.eu<mailto:enol.fernandez@egi.eu>>, <aloga(a)ifca.unican.es<mailto:aloga@ifca.unican.es>>, <sustr4(a)cesnet.cz<mailto:sustr4@cesnet.cz>>, <michel.drescher(a)egi.eu<mailto:michel.drescher@egi.eu>>, <David.Wallom(a)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(a)inria.fr><mailto:philippe.merle@inria.fr>
Pour : occi-wg(a)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.cl…> https://github.com/occiware/ecore/tree/master/clouddesigner/org.occiware.cl….
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/c049165ae45d90ca0ad36037df22ce64…
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
