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 CDMI in CMF"

From EGIWiki
Jump to navigation Jump to search
m
 
(5 intermediate revisions by the same user not shown)
Line 8: Line 8:
*Start Date: 01/04/2013
*Start Date: 01/04/2013
*Duration: 31/03/2014
*Duration: 31/03/2014
*Task tracking: [https://opennode.atlassian.net]
*Task tracking: [https://opennode.atlassian.net/browse/STOX]
== Motivation  ==
== Motivation  ==


The introduction should explain what the issue/problem that needs to be addressed is, the background to the project, the motivation as to why something is being done about it. Go on to explain any other relevant points, including the project mandate - who has directed the formation of the project, what has been defined as the project objective.  Who is the project leader/manager, who are the stake holders (this is vitally important as you need to be clear on what it is that is expected of you), who are the recipients of the project output and when is this required by.  Describe the formation of the project team (how why and where), the allotted resources (time, people, stuff, money etc). There could be a number of sub paras. You should also make clear that the scope of the task is realistic and that you can achieve it – as such, complete this introduction at the start of the project and re-check it periodically as you progress.
SNIA Cloud Data Management Interface (CDMI, http://www.snia.org/cdmi) is a well established open standard for providing storage services which recently became an ISO standard. The goal of this activity is to implement support of CDMI specifically for the requirements of EGI cloud infrastructures, both for handling the data files and orchestration of the block devices and their attachment to VMs. This would lead to a multi purpose storage solution that would seamlessly fit into EGI's Cloud Infrastructure platform and integrate with EGI's Core Infrastructure platform.
 
The main beneficiaries include sites and communities that want to serve or consume resources using standards’ based cloud APIs. An additional benefit for the communities is the ability to migrate between EGI and public cloud offerings more easily due to the existence of similar services.


== Objectives  ==
== Objectives  ==
Line 19: Line 21:
== Tasks  ==
== Tasks  ==


List and describe the specific tasks with target dates for completion.
Tasks are managed in a private Jira. For access please contact livenson@kth.se
 
== Security  ==
 
(Update) It was decided that integration with X.509/VOMS-based infrastructure will happen via VOMS-enabled OpenStack Keystone.
 


==Outcomes/Deliverables ==
==Outcomes/Deliverables ==


* Deliverable 1 description and target date
=== Planning phase: '''end of May''' ===
* Deliverable 2 description
# Documentation of the expected use cases
# Development infrastructure configuration


== Members  ==
=== Execution phase: '''End of January''' ===
# CDMI Storage (aka Stoxy)  component packages
# Administrator’s documentation
# Functional test suite
# Integration test suite
# CLI & SDK
## Python
## Java


* Member 1 Name and Role in team
=== Testing and bugfix phase: '''end of March''' ===
* Member 2 Name and Role in team
# Source Code
# Results of the stress tests
# Validation feedback.
# Developer’s guide.


* Stake holder 1 and reason for interest
* Stake holder 1 and reason for interest




== Emerging Information ==
== Members ==


if relevant - may change the nature and objectives of the project
* Ilja Livenson, KTH, project lead, developer, livenson@kth.se
* Andrei Sosnin, OpenNode, developer


== Resources  ==
== Resources  ==


How is the Project Team to be resourced and how will members work?  How much effort will be required from each individual, how will this effort impact contributing organisations? – do not confuse VT participants with stakeholders. VT participants do work for the project – others don’t have to do any work for the project. How will your funds be consumed?
* Task tracking: Jira
 
* CDMI specification: [cdmi.sniacloud.com]
* Code control: [https://github.com/stoxy]
* Documentation: [https://stoxy.readthedocs.org/]
* Original CDMI Proxy: [https://github.com/livenson/vcdm]
* Python SDK: https://github.com/livenson/libcdmi-python
* Java SDK:https://github.com/livenson/libcdmi-java


== Progress Reporting ==
== Progress Reporting ==


How will you measure your progress and how will you report this? To whom?  The objective here is to assure others that your project is on track, but if there are problems then this is the path to getting help and more resources (time, funding, effort).
The Project Leader will provide a short emailed progress report on a bi-weekly basis.  The report will be due by 17:00 on Mondays and is to contain details of:
 
* Work achieved during the last two weeks
The Project Leader will provide a short emailed progress report on a weekly basis.  The report will be due by 17:00 on Fridays and is to contain details of:
* Work planned for next two weeks
* Work achieved that week
* Work planned for next week
* Progress against the goals in the project plan
* Progress against the goals in the project plan
* Issues that the virtual team leader needs help with (e.g. non-responsive partners, more resources, support from EGI.eu teams, etc.)
* Issues that the virtual team leader needs help with (e.g. non-responsive partners, more resources, support from EGI.eu teams, etc.)
Line 57: Line 76:
The Team project manager will also provide a more comprehensive input for the EGI InSPIRE quarterly reporting.
The Team project manager will also provide a more comprehensive input for the EGI InSPIRE quarterly reporting.


== Documents ==
1. [[Questions to potential CDMI adopters]]


[[Category:Virtual_Teams]]
[[Category:Virtual_Teams]]

Latest revision as of 09:55, 3 September 2013

General Project Information

  • Full title: CDMI support in Cloud Management Stacks
  • Leader: Ilja Livenson, KTH
  • Mailing List: <none-yet>
  • Meetings: <skype weekly PPP>
  • Status: in progress
  • Start Date: 01/04/2013
  • Duration: 31/03/2014
  • Task tracking: [1]

Motivation

SNIA Cloud Data Management Interface (CDMI, http://www.snia.org/cdmi) is a well established open standard for providing storage services which recently became an ISO standard. The goal of this activity is to implement support of CDMI specifically for the requirements of EGI cloud infrastructures, both for handling the data files and orchestration of the block devices and their attachment to VMs. This would lead to a multi purpose storage solution that would seamlessly fit into EGI's Cloud Infrastructure platform and integrate with EGI's Core Infrastructure platform.

The main beneficiaries include sites and communities that want to serve or consume resources using standards’ based cloud APIs. An additional benefit for the communities is the ability to migrate between EGI and public cloud offerings more easily due to the existence of similar services.

Objectives

An outcome of the project will be a prototype, which will integrate the EGI Federated AAI model for authentication and authorization and will offer object and block storage proxy to OCCI-compliant services. These services include cloud stacks used in EGI FedCloud TF if they are accessed either via native or translated (e.g. by rOCCI) OCCI interface. A browser friendly interface will be developed on the basis of the CDMI HTTP based RESTful protocol to enable end users to access and manage their files in a user friendly way.

Tasks

Tasks are managed in a private Jira. For access please contact livenson@kth.se

Security

(Update) It was decided that integration with X.509/VOMS-based infrastructure will happen via VOMS-enabled OpenStack Keystone.


Outcomes/Deliverables

Planning phase: end of May

  1. Documentation of the expected use cases
  2. Development infrastructure configuration

Execution phase: End of January

  1. CDMI Storage (aka Stoxy) component packages
  2. Administrator’s documentation
  3. Functional test suite
  4. Integration test suite
  5. CLI & SDK
    1. Python
    2. Java

Testing and bugfix phase: end of March

  1. Source Code
  2. Results of the stress tests
  3. Validation feedback.
  4. Developer’s guide.


Members

  • Ilja Livenson, KTH, project lead, developer, livenson@kth.se
  • Andrei Sosnin, OpenNode, developer

Resources

Progress Reporting

The Project Leader will provide a short emailed progress report on a bi-weekly basis. The report will be due by 17:00 on Mondays and is to contain details of:

  • Work achieved during the last two weeks
  • Work planned for next two weeks
  • Progress against the goals in the project plan
  • Issues that the virtual team leader needs help with (e.g. non-responsive partners, more resources, support from EGI.eu teams, etc.)

The Team project manager will also provide a more comprehensive input for the EGI InSPIRE quarterly reporting.

Documents

1. Questions to potential CDMI adopters