The Platform resource types that we defined are derived from Resource entity at OCCI core level whereas platform resource mixins are derived from the Mixin entity and the interfaces, which links resources between them, are derived from Link entity.

The main defined OCCI platform resources are:

• Database which are data store resources for platform applications processing persistent Data.
• Container which are engines to host and run applications
• Router which are resources that provide protocols, message format transformations and routing

We also define a set of links to connect and interact with these resources:

• ContainerLink to connect to Container resources
• RouterLink to connect to Router resources,
• DatabaseLink to connect a Container resource to a Database resource

Examples of defined mixins:

• Service micro-container mixin
• WSO2 ESB router mixin

For more details regarding this extension, please download the documentation available through the correspondent link in the right column of the Web page.

The Application resource types that we defined are derived from Resource entity at OCCI core level and the interfaces, which links resources between them, are derived from Link entity.

The main defined OCCI Application resources are:

• Environment which which represents a set of "settings" needed to host and run an Application
• Application which is the software or program that can be deployed on top of a PaaS
• Deployable which represents the Application deployables

We also define the ContainerLink resource to connect an Environment to an Application

For more details regarding this extension, please download the documentation available through the correspondent link in the right column of the Web page.

We define XML Schemas to describe both Platform and Application OCCI resources according to our proposed extensions.

The structure of these XML Schemas is inline with XML Schemas introduced by the OGF.OCCI working group to describe OCCI core resources and extensions.

Defined XML schemas and valid examples can be downloaded from the Documents and sources section on the top of this Web page. For more informations, please refer to the XML Schemas HTML documentations below:

• Platform resource instances XML Schema documentation
• Application resource instances XML Schema documentation

We propose an implementation of our description model based on OCCI4Java.

This implementation consists of a Java OCCI server that can interact with CF-PaaS API which is a Cloud Foundry implementation of our COAPS API.

This implemntation is open source under Apache 2.0 licence. Needed documentations are also available.

Since February 2014, OCCI WG begin to work on a new standard on Platform and Application models.

We are in contact with them and we aim at actively participating in the development of this model

The working document is available at: https://docs.google.com/document/d/1gQmvVd9T9yMoS-9Vb3gBJ3N-OSNvgtzHWC8Di0VpB98/edit?usp=sharing

For more details, please contact the OCCI WG coordinator, Thijs_DOT_Metsch_AT_intel_DOT_com.