OCCI 1.2

We are very happy to announce, that thanks to a lot of help from the community, the documents which will become OCCI rev 1.2 are ready:

  • Our core document has been update with minor tweaks. [pdf]
  • We’ve update the Text rendering document – propose however that this will be deprecated over time. [pdf]
  • As a substitute to the Text rendering we now suggest using JSON. [pdf]
  • To allow for the deprecation of the Text rendering, and addition of the JSON rendering we’ve moved the generic protocols pieces to this new recommendation. [pdf]
  • We’ve captured some minor tweaks in the Infrastructure document. [pdf]
  • A new addition is the support for machine readable SLA. [pdf]
  • Furthermore OCCI now also support PaaS/CaaS. [pdf]
  • We’re very happy to announce a profile for OCCI. [pdf]

The OCCI revision 1.1 documents can still be found on the Specification page.

OCCI 1.2 revision in public comment

Thanks to the help of many helpers a set of documents describing OCCI revision 1.2 is now in public comment. Similar to IETF OGF uses a very open policy – so this is the point in time where we need your help. Please read the docs and provide us with comments and suggestions.

OCCI 1.2 targets to be backwards compatible with OCCI rev 1.1. An overall of 9 documents is now ready for your comments at the OGF website.

The 9 documents are:

  • A updated core model – which includes minor updates and e.g. refinements about the usage of Attributes in the Meta-model.
  • A updated Infrastructure model – which minor tweaks on the state models of the kind descriptions
  • The HTTP text rendering document has been split:
    • in a protocol definition defining how OCCI is RESTfully modeled over HTTP, and
    • a text rendering document containing the text rendering
  • A newly defined JSON rendering based on the new protocol document
  • A newly defined extension to render Service Level Agreements
  • A newly defined extension to deal with Platform as a Service Service Providers over OCCI
  • A Profile which is a recommendation driven by the EGI project.
  • and last – but definitely not least – and informal document describing how OCCI can be used to Monitor resources.

Again – many thanks to those who helped to achieve this milestone. And already many thanks in advance to the community for helping forming OCCI 1.2 through this public comment phase.