Fedcloud-tf:WorkGroups:Scenario1

Main

Roadmap and Innovation

Technology

For Users

For Resource Providers

Media

Workbenches:

Open issues

Scenario 1 VM Management

Scenario 2 Data Management

Scenario 3 Information Systems

Scenario 4 Accounting

Scenario 5 Monitoring

Scenario 6 Notification

Scenario 7 Federated AAI

Scenario 8 VM Image Management

Scenario 9 Brokering

Scenario 10 Contextualisation

Scenario 11 Security

Scenario 1: Virtual Machine Management

Role	Institution	Name
Scenario leader	CESNET	Boris Parák
Collaborator	CESNET	Zdeněk Šustr
Collaborator	GWDG	Piotr Kasprzak
Collaborator	IFCA	Enol Fernández
Collaborator	GRNET	Kostas Koumantaros

Available Open Standards

OCCI

Developed by the Open Grid Forum, OCCI is a boundary protocol and API that acts as a service front-end to a provider’s internal management framework by exposing its resources. As of this writing (early 2015) the specification consist of three documents:

• OCCI Core describing the formal definition of the the OCCI Core Model
• OCCI Infrastructure defining the OCCI Infrastructure extension for the IaaS domain, defining additional resource types, their attributes and the actions that can be taken on each resource type
• OCCI HTTP Rendering defining interaction with the OCCI Core Model using the RESTful OCCI API

The OCCI Working Group is also working on additional specification, currently in various stages of progress:

• OCCI XML Rendering
• OCCI JSON Rendering
• OCCI Billing and Monitoring
• OCCI PaaS extension
• OCCI SLAs extension

CIMI

The Cloud Infrastructure Management Interface is a standard released by DMTF. Similarly to OCCI, it also consists of multiple specifications:

• CIMI Primer (DSP2027) v. 1.0.0
• CIMI (DSP0263) v. 1.1.0
• CIMI-CIM (DSP0264) v. 1.0.0

CIMI is a highly specific IaaS protocol, defining a wide range of attributes applicable in the context of IaaS. This is what mainly distinguishes it from OCCI, which is a much more light-weight, generic boundary-level protocol, relying on its extensibility to cover specific areas.

OGF's Open Cloud Computing Interface

OCCI was selected for the FedCloud environment for multiple reasons, chief among them its simplicity and the fact that other standards of that kind (such asi CIMI) have not been published until well after the initiative started.

Available OCCI implementations

Server

rOCCI-server

rOCCI-server, part of the rOCCI Framework, is a stand-alone service providing "translation" between OCCI and proprietary cloud management frameworks, which are not otherwise OCCI-compatible. Individual types of clod management framework are provided through specific backends. The list of currently available backends is available in the ROCCI-server_Backend_development_status page.

rOCCI-server can be obtained as source from GitHub or in the form of packages from EGI's AppDB.

Common documentation for the whole rOCCI framework is available at the EGI Wiki.

OCCI-OS

OCCI-OS provides a python egg which can be easily deployed in OpenStack and will thereby add OCCI support and interface to OpenStack. Available and documented at [1].

snf-occi

snf-occi implements the OCCI specification and maps it to the Synnefo OpenStack API, so it acts as a translation bridge between OCCI and Synnefo, providing an OCCI compatibility layer. [2]

Client

rOCCI-cli

rOCCI-cli, another part of the rOCCI Framework, is a command-line client capable of communicating with any OCCI-enabled server. It supports several methods of authentication, including X.509 certificates and proxy certificates.

rOCCI-cli can be obtained as source from GitHub or in the form of packages from EGI's AppDB.

Common documentation for the whole rOCCI framework is available at the EGI Wiki.

Library

rOCCI-core and rOCCI-api

Core parts of the rOCCI framework, the rOCCI-core library implements the OCCI class structure in Ruby, which allows developers to work with OCCI concepts natively. rOCCI-api takes care of transporting OCCI messages, currently supporting HTTP as the only transport protocol.

pyssf

pyssf is a set of python modules developed by Platform Computing, man contributors to the OCCI standard. Source as well as documentation is available from GitHub [3].

jOCCI-core and jOCCI-api

jOCCI is an independent OCCI implementation by the authors of rOCCI. It satisfies the demand for a Java library, replacing the previous alternative based on JRuby. Currently in development, is is available as source from Github [4] [5].

Interoperability Table

Main tasks identified in Scenario1, supported by various server-side OCCI implementations.

Task		rOCCI-server OpenNebula	rOCCI-server AWS	rOCCI-server MS Azure	OCCI-OS OpenStack	snf-occi Synnefo
Creating VMs		OK	OK	OK	OK	OK
Querying VMs
Destroying VMs
Triggering basic actions on VMs
Creating block storage
Destroying block storage
Attaching block storage to VMs
Detaching block storage from VMs
Attaching network interfaces to VMs
Detaching network interfaces from VMs
Using contextualization to modify VMs on boot
Attaching storage or networks on boot (in-line links)