The Open Cloud Computing Interface (OCCI) specification set defines a general protocol and API applicable to many different cloud resource management tasks. OCCI began as a remote management API for IaaS model based Services, allowing for the development of interoperable tools for common tasks including deployment, autonomic scaling and monitoring. It has since evolved into a general-purpose flexible RESTful API framework with a strong focus on integration, portability, interoperability and innovation while still remaining highly extensible. OCCI is suitable to serve many other models in addition to IaaS, including e.g. PaaS and SaaS. The current release (v1.1) of OCCI has achieved a high degree of adoption and implementation in production in a wide variety of languages, projects, software products and application areas. The OCCI working group is in the process of developing an update of the OCCI specifications as version 1.2 with improvements that result from nearly four years of successful field experience. This version will be backwards compatible with v1.1 and will include: - A new JSON rendering to accompany updates to the existing HTTP and text renderings. - Minor updates of current OCCI core infrastructure model and specification. - New extensions that will include PaaS support, notifications support and SLA support. ?In addition, the OCCI group is considering best methods for support of additional features, including monitoring, key management and security, interdomain networking and direct interface support for popular batch systems through the Distributed Resource Management Application API (DRMAA) standard.

1. The Open Cloud Computing Interface
(OCCI): Flexible, Portable, Interoperable,
Extensible and Innovative
Alan Sill
VP of Standards, OGF
1
On behalf of the OCCI Working Group

2. OCCI Version 1.1
• Base documents published in 2011.
• Very stable standard set.
• Implemented quite extensively since then.
• Initial documents include: Core (GFD.183),
Infrastructure (GFD.184), RESTful HTTP
Rendering (GFD.185).
• As per the established (IETF-like) OGF process,
these are Proposed Recommendations awaiting
experience documentation and refinement for the
group to advance them to full recommendations.
2

3. • Projects:
OCCI: Extensively Implemented
• Languages:
- Java
- Ruby
- Python
- Javascript
- Erlang
- Perl
- …
• Implementations:
- rOCCI
- OpenNebula
- OCCIware
- OpenStack (occi-os)
- CompatibleOne
- ACCORDS
- EGI Federated Cloud
- FogBow
- etc…
3
Source: occi-wg.org

4. OCCI: Extensively Implemented
(Dozens of repositories in GitHub)
4
GitHub search Google search
Many projects use OCCI on a production basis.

5. Example: EGI Federated Cloud
5
www.egi.eu'EGI+InSPIRE'RI+261323'
Selection of new Communities since
launch
• Education – Cranfield University distributed systems course
• Cultural Heritage – DCH-RP management of preservation services in the cloud
• Hydrological Modelling – Running Hydrological models to support real time analysis
• Bioinformatics – ELIXIR execution of the Ensamble application in the Federated Cloud
environment
• Systems implementations – deployment of FTK developed tools and services and data
preservation
• Internet of Things – Smart Grid systems investigation
• Software Development – deployment of research PaaS
• RNA Sequencing – deployment of analysis engines in the cloud
• Physiological Modelling – Calibration, scenario mapping and development
More%info:%h+ps://wiki.egi.eu/wiki/Fedcloud89:Users%
15
www.egi.eu'EGI+InSPIRE'RI+261323'
EGI FedCloud Communities 9/2014
• Ecology – BioVeL: Biodiversity Virtual e-Laboratory
• Structural biology – WeNMR: a worldwide e-Infrastructure for NMR and structural biology
• Linguistics – CLARIN: ‘British National Corpus’ service (BNCWeb)
• Earth Observation – SSEP: European Space Agency’s Supersites Exploitation Platform for
volcano and earthquakes monitoring (Collaboration with Helix Nebula)
• Software Engineering – SCI-BUS: simulated environments for portal testing
• Software Engineering – DIRAC: deploying ready-to-use distributed computing systems
• Software Engineering – Catania Science Gateway Framework
• Musicology – Peachnote: dynamic analysis of musical scores
• Earth Observation – ENVRI: Common Operations of Environmental Research
infrastructures (collaboration with EISCAT3D)
• Geology – VERCE: Virtual Earthquake and seismology Research
• Ecology – LifeWatch: E-Science European Infrastructure for Biodiversity and Ecosystem
Research
• High Energy Physics – CERN ATLAS: ATLAS processing cluster via HelixNebula
More%info:%h+ps://wiki.egi.eu/wiki/Fedcloud89:Users%
14
Production multi-
technology cloud with
approximately 20
resource providers
supporting over 2 dozen
research communities!
Source: User Engagement in the EGI Federated Cloud, David Wallom, OeRC / UCC 2014

6. OCCI Version 1.2
• Based on extensive experience in the field
following OGF Recommendations-track process.
• Backwards compatible. Aim: Better completeness.
• Changes & new documents to be posted as a
complete set. Timescale: mid to late 2015.
• Updates and new documents will include: Core,
Infrastructure, HTTP Protocol Rendering, Text
Rendering, JSON Rendering, Platform As A
Service, SLA Framework, and new Notification
and Monitoring extensions.
6

7. 7
Contact us…
http://www.occi-wg.org
occi-wg@ogf.org
Twitter: @occiwg
IRC: #OCCI at freenode
https://www.ogf.org
standards@ogf.org
Twitter: @OGFStandards