Jump to: navigation, search

Difference between revisions of "Manila/Program Application"

(Created page with "=== Official Title === Shared Filesystems === Mission Statement === The goal of the Shared Filesystems program is to provide a set of services for management of shared filesy...")
 
Line 1: Line 1:
=== Official Title ===
+
== Official Title ==
 
Shared Filesystems
 
Shared Filesystems
  
=== Mission Statement ===
+
== Mission Statement ==
 
The goal of the Shared Filesystems program is to provide a set of services for management of shared filesystems in a multitenant cloud environment, similar to how OpenStack provices for block-based storage management through the Block Storage program.
 
The goal of the Shared Filesystems program is to provide a set of services for management of shared filesystems in a multitenant cloud environment, similar to how OpenStack provices for block-based storage management through the Block Storage program.
  
 
We aim to provide a vendor neutral management interface that allows for provisioning and attaching shared filesystems such as NFS, CIFS, and more. To the extent possible we aim to mirror the architecture of Block Storage program, with support for a public REST API, multiple backends, and a scheduler that performs resource assignment decisions. When differences are unavoidable, we plan to design solutions that are compatible with the OpenStack ideals of modularity and scalability.  
 
We aim to provide a vendor neutral management interface that allows for provisioning and attaching shared filesystems such as NFS, CIFS, and more. To the extent possible we aim to mirror the architecture of Block Storage program, with support for a public REST API, multiple backends, and a scheduler that performs resource assignment decisions. When differences are unavoidable, we plan to design solutions that are compatible with the OpenStack ideals of modularity and scalability.  
  
=== Deliverables ===
+
== Deliverables ==
 
* A set of services (API server, scheduler, and share manager) that provide an infrastructure for self-sevice provisioning and managing shared filesystems in a multitenant cloud
 
* A set of services (API server, scheduler, and share manager) that provide an infrastructure for self-sevice provisioning and managing shared filesystems in a multitenant cloud
 
* A CLI-based client for users and administrators to interact with the API
 
* A CLI-based client for users and administrators to interact with the API
Line 16: Line 16:
 
* API documentation, Administrator documentation, and Developer documentation
 
* API documentation, Administrator documentation, and Developer documentation
  
=== Repositories ===
+
== Repositories ==
 
* Project code: https://github.com/stackforge/manila
 
* Project code: https://github.com/stackforge/manila
 
* Python client: https://github.com/stackforge/python-manilaclient
 
* Python client: https://github.com/stackforge/python-manilaclient
  
=== ATC Status ===
+
== ATC Status ==
 
The program grants Active Technical Contributor (ATC) status to anyone completing a commit to any program repository during the previous two release cycles. Core project team members may grant ATC to significant, non code contributors for two cycles.
 
The program grants Active Technical Contributor (ATC) status to anyone completing a commit to any program repository during the previous two release cycles. Core project team members may grant ATC to significant, non code contributors for two cycles.
  
=== Project Technical Lead ===
+
== Development Team ==
Ben Swartzlander
+
̈PTLː Ben Swartzlander
  
=== Main Team Members ===
+
The core teamː
* TBD
+
* Yulia Portnova
* TBD
+
* Valeriy Ponomaryov
* TBD
+
 
 +
Significant contributorsː
 +
̽* Vitaly Kostenko
 +
̈* Andrei Ostapenko
 +
* Aleksandr Chirko
 +
* Ramama Raja
 +
̈* Christian Berendt
  
 
=== Why a new program? ===
 
=== Why a new program? ===

Revision as of 23:24, 13 June 2014

Official Title

Shared Filesystems

Mission Statement

The goal of the Shared Filesystems program is to provide a set of services for management of shared filesystems in a multitenant cloud environment, similar to how OpenStack provices for block-based storage management through the Block Storage program.

We aim to provide a vendor neutral management interface that allows for provisioning and attaching shared filesystems such as NFS, CIFS, and more. To the extent possible we aim to mirror the architecture of Block Storage program, with support for a public REST API, multiple backends, and a scheduler that performs resource assignment decisions. When differences are unavoidable, we plan to design solutions that are compatible with the OpenStack ideals of modularity and scalability.

Deliverables

  • A set of services (API server, scheduler, and share manager) that provide an infrastructure for self-sevice provisioning and managing shared filesystems in a multitenant cloud
  • A CLI-based client for users and administrators to interact with the API
  • A Horizon GUI plugin
  • A "generic" sorfware-only driver that runs on any hardware, allowing people to use the service without specialized equipment
  • An example image (cirros-based) that implements part of the "generic" storage service, with documentation on how admins can create their own
  • A set of drivers for commercial NAS storage servers
  • API documentation, Administrator documentation, and Developer documentation

Repositories

ATC Status

The program grants Active Technical Contributor (ATC) status to anyone completing a commit to any program repository during the previous two release cycles. Core project team members may grant ATC to significant, non code contributors for two cycles.

Development Team

̈PTLː Ben Swartzlander

The core teamː

  • Yulia Portnova
  • Valeriy Ponomaryov

Significant contributorsː ̽* Vitaly Kostenko ̈* Andrei Ostapenko

  • Aleksandr Chirko
  • Ramama Raja

̈* Christian Berendt

Why a new program?

We started a new program for two main reasons:

  • Initially we tried to address the above needs by expanding the scope of the Block Storage program, but the Cinder core team didn't want the additional responsibility. This left us with no option other than to start a new program.
  • While there is significantly overlap between Block Storage and Shared Filesystems, the differences are large enough to require a dedicated group of developers to solve the unique problems related to Shared Filesystems. Keeping the programs separate has been greatly advantageous as it allows each group to focus on different problems and ultimately get more done.