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 "VT OCCI for CMF"

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


* '''[Done]''' Action 1.1: Mini-project setup (Official start, introduction, Web page setup, team establishment and team internal procedures)
* '''[Done]''' Action 1.1: Mini-project setup (Official start, introduction, Web page setup, team establishment and team internal procedures)
* Action 1.2: Progress report at EGI TF 13
* '''[Done]''' Action 1.2: Progress report at EGI TF 13


<!-- Additional details in [http://www.asana.com Asana] -->
<!-- Additional details in [http://www.asana.com Asana] -->
Line 43: Line 43:
=== Task 2: rOCCI Framework Changes ===
=== Task 2: rOCCI Framework Changes ===


Getting rid of unmaintained dependencies, refactoring to core+client gems, code cleanup
Remove unmaintained dependencies, refactor core and client gems, do code cleanup.


==== Actions ====
==== Actions ====


Details curently only in [http://www.asana.com Asana]
*  '''[Done]''' Action 1.1: rOCCI refactoring (split the code base into core, api and client)
*  '''[Done]''' Action 1.2: Update core classes (attribute handling, actions etc.)
*  '''[Done]''' Action 1.3: Implement support for modular client-side authentication (add native Keystone support)
*  '''[Done]''' Action 1.4: Provide documentation for rOCCI-core (to help future developers utilizing rOCCI framework)
 
<!-- Details curently only in [http://www.asana.com Asana] -->


=== Task 3: rOCCI-server refactoring ===
=== Task 3: rOCCI-server refactoring ===


Frontends, interoperability
Re-implement the rOCCI-server to provide a stable base for further development and increase interoperability.


==== Actions ====
==== Actions ====


Details curently only in [http://www.asana.com Asana]
*  '''[Done]''' Action 1.1: Design the new rOCCI-server
*  <!-- '''[Done]''' --> Action 1.2: Provide detailed documentation of the new design
*  <!-- '''[Done]''' --> Action 1.3: Implement the new rOCCI-server
 
<!-- Details curently only in [http://www.asana.com Asana] -->


=== Task 4: Backends + documentation ===
=== Task 4: Backends + documentation ===


Support for widely used virtualization stacks in general, and for OpenNebula (through <code>fog.io</code>) in particular.
Implement support for widely used virtualization stacks in general, primarily for OpenNebula.


==== Actions ====
==== Actions ====

Revision as of 20:11, 7 October 2013

General Project Information

  • Full title: Providing OCCI support for arbitrary Cloud Management Frameworks
  • Leader: Boris Parak, CESNET
  • Mailing List: inspire-mp-rocci@mailman.egi.eu
  • Status: active
  • Start Date: 01/04/2013
  • End Date: 31/03/2014
  • Meetings: INDICO
  • Workflow and Task management: Asana.com (private)

Motivation

The mini-project aims at providing an ability to control the life-cycle of virtual machines at multiple sites of EGI's federated cloud environment using standardized tools. As different cloud management platforms are already actively used at different sites, enforcing a particular platform across all sites at this point is neither practical nor desirable. Therefore there is a need for an interoperability layer to bridge this gap. The OCCI protocol, an OGF standard, has been chosen to provide a uniform interface for the management of virtual machines.

For implementation, the rOCCI framework and the rOCCI-server have been selected to add OCCI support to existing applications and cloud management platforms. By using their existing features, and extending their architecture to include an interoperability layer based on the fog.io abstraction library for cloud services, this project will provide OCCI support for a large number of open source and commercial cloud platforms including OpenNebula, OpenStack, RackSpace, CloudStack and AWS with focus on extended support for cloud platforms used within the EGI Federated Clouds Task Force.

See also Mini-project introduction talk at EGI CF 2013: https://indico.egi.eu/indico/materialDisplay.py?contribId=152&sessionId=29&materialId=slides&confId=1222


Output

Actions out of Scope or left Open after Mini-Project Ends

N/A

Tasks

Only higher-level tasks are supposed to be listed here. Day-to-day tasks are tracked at Asana.com

Task 1: Mini-Project Management

Not only leadership but also general work that moves the mini-project along, such as publishing and reporting

Actions

  • [Done] Action 1.1: Mini-project setup (Official start, introduction, Web page setup, team establishment and team internal procedures)
  • [Done] Action 1.2: Progress report at EGI TF 13


Task 2: rOCCI Framework Changes

Remove unmaintained dependencies, refactor core and client gems, do code cleanup.

Actions

  • [Done] Action 1.1: rOCCI refactoring (split the code base into core, api and client)
  • [Done] Action 1.2: Update core classes (attribute handling, actions etc.)
  • [Done] Action 1.3: Implement support for modular client-side authentication (add native Keystone support)
  • [Done] Action 1.4: Provide documentation for rOCCI-core (to help future developers utilizing rOCCI framework)


Task 3: rOCCI-server refactoring

Re-implement the rOCCI-server to provide a stable base for further development and increase interoperability.

Actions

  • [Done] Action 1.1: Design the new rOCCI-server
  • Action 1.2: Provide detailed documentation of the new design
  • Action 1.3: Implement the new rOCCI-server


Task 4: Backends + documentation

Implement support for widely used virtualization stacks in general, primarily for OpenNebula.

Actions

Details curently only in Asana

Members

  • Boris Parak, CESNET
  • Zdenek Sustr, CESNET
  • Maik Srba, GWDG, unfunded participation
  • Florian Feldhaus, unfunded participation
  • Piotr Kasprzak, GWDG, unfunded participation

Resources


Progress

Only higher-level progress statemets will be listed here. Day-to-day tasks are tracked at Asana.com


  • Task 1 (CONTINUOUS)
    • Progress report at EGI TF 13 in preparation
  • Task 2 (In PROGRESS)
  • Task 3 (In PROGRESS)
    • Ongoing
  • Task 4 (In PROGRESS)
    • Fog.io rejected for lack of versatility.
    • Backends (starting with OpenNebula) will be implemented in the rOCCI-server