Occi

• Launchpad Entry: NovaSpec:bexar-open-cloud-compute-interface
• Created: 11/10/2010
• Contributors: Thijs Metsch (tmetsch), Andy Edmonds (dizz)

Summary

This will implement the open cloud compute interface within nova/api. Specification for the OCCI API can be found here: http://forge.ogf.org/sf/go/projects.occi-wg/wiki

Implementation details

Most probably we gonna use the pyocci module from http://pyssf.sf.net. It is a WSGI compliant service currently running on Tornado - but that can/should be changed for an OpenStack implementation.

We are targetting the Bexar release of OpenStack for a first shot of an OCCI implementation for OpenStack. Most probably full support of OCCI will be available in the following release. Ideal would be if this work is in aligmnent with an CDMI implementation in OpenStack.

Next steps:

• Workout integration of pyocci in OpenStack (Messaging - Input coming from Soren)
• Create branch and start working on a simple first provisioning of VMs
• Integrate CDMI with OCCI
• Interop testing with help of jClouds

Release Note

This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)

It is mandatory.

Design

You can have subsections that better describe specific parts of the issue.

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

UI Changes

Should cover changes required to the UI, or specific UI that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.

Migration

Include:

• data migration, if any
• redirects from old URLs to new ones, if any
• how users will be pointed to the new way of doing things, if necessary.

Test/Demo Plan

This need not be added or completed until the specification is nearing beta.

Unresolved issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

BoF agenda and discussion

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.

---