Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "Fedcloud-tf:WorkGroups:Scenario1"

From EGIWiki
Jump to navigation Jump to search
Line 60: Line 60:


OCCI was selected for the FedCloud environment for multiple reasons, chief among them its simplicity, extensibility and the fact that other standards of that kind (such asi CIMI) have not been published until well after the initiative started.
OCCI was selected for the FedCloud environment for multiple reasons, chief among them its simplicity, extensibility and the fact that other standards of that kind (such asi CIMI) have not been published until well after the initiative started.
For protocol details, please, read:
* OGF OCCI 1.1 Core Specification -- [http://ogf.org/documents/GFD.183.pdf GFD-183]
* OGF OCCI 1.1 Infrastructure Specification -- [http://ogf.org/documents/GFD.184.pdf GFD-184]
* OGF OCCI 1.1 HTTP Rendering Specification -- [http://ogf.org/documents/GFD.185.pdf GFD-185]


== Available OCCI implementations ==
== Available OCCI implementations ==

Revision as of 17:26, 23 February 2015

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 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, extensibility and the fact that other standards of that kind (such asi CIMI) have not been published until well after the initiative started.

For protocol details, please, read:

  • OGF OCCI 1.1 Core Specification -- GFD-183
  • OGF OCCI 1.1 Infrastructure Specification -- GFD-184
  • OGF OCCI 1.1 HTTP Rendering Specification -- GFD-185

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].

Activities

Ongoing Issues

Interoperability

Aligning behavior between different implementations and CMFs.

See Fedcloud-tf:WorkGroups:Scenario1#Interoperability_Table

Authentication

Introducing the support for Keystone-like authentication protocol in every available implementation and CMF.

See Keystone-VOMS docs

Deployment

Continuous deployment of maintenance updates and new versions for every implementation and CMF.

Support for new platforms & public providers

Introducing support for new CMFs and public cloud providers.

Support for native interfaces

Exploring the possibility of exploiting native CMF interfaces as well as inter-operable interfaces.

Interoperability Table

Please note that this table is work in progress!

Compatibility of different OCCI implementations – this table sums up basic tasks that can be performed over OCCI in different cloud management frameworks
Task Subtask rOCCI-server OCCI-OS
OpenStack
snf-occi
Synnefo
OpenNebula AWS MS Azure
Retrieving model Category Classes
(Kind, Action, Mixin)
OK OK
Core Kinds
(Entity, Resource, Link)
OK OK
Infrastructure Kinds
(Compute, Network, Storage)
OK OK
Infrastructure Mixins
(os_tpl, resource_tpl)
OK OK
Creating Compute OK OK NO OK OK
Querying Compute OK OK NO OK OK
Destroying Compute OK OK NO OK OK
Creating Storage OK OK
Querying Storage OK OK
Destroying Storage OK OK
Attaching Storage to Compute On creation OK OK
In run-time OK OK
Detaching Storage from Compute OK OK
Creating Network NO NO NO NO NO
Querying Network NO NO NO NO NO
Destroying Network NO NO NO NO NO
Attaching Network to Compute On creation OK OK
In run-time OK OK
Detaching Network from Compute OK OK
Actions on Resources Compute – start OK OK
Compute – stop OK OK
Compute – restart OK OK
Compute – suspend OK NO
Storage – online OK NO
Storage – offline OK NO
Storage – backup OK NO
Storage – snapshot NO OK
Storage – resize NO NO
Network – up NO NO
Network – down NO NO
Contextualization on Compute OK OK