Jump to: navigation, search

Difference between revisions of "Manila"

(Getting Started with Manila)
(Introduction)
(30 intermediate revisions by 13 users not shown)
Line 1: Line 1:
 
== Introduction ==
 
== Introduction ==
This page documents the concept and vision for establishing a shared file system service for OpenStack.  The development name for this project is Manila.  We propose and are in the process of implementing a new OpenStack service (originally based on Cinder).  Cinder presently functions as the canonical storage provisioning control plane in [[OpenStack]] for block storage as well as delivering a persistence model for instance storage.  The File Share Service prototype, in a similar manner, provides coordinated access to shared or distributed file systems.  While the primary consumption of file shares would be across OpenStack Compute instances, the service is also intended to be accessible as an independent capability in line with the modular design established by other OpenStack services. The design and prototype implementation provide extensibility for multiple backends (to support vendor or file system specific nuances / capabilities) but is intended to be sufficiently abstract to accommodate any of a variety of shared or distributed file system types.  The team's intention is to introduce the capability as an OpenStack incubated project in the Juno timeframe, graduate it and submit for consideration as a core service as early as the as of yet unnamed "K" release.
+
This page documents the concept and vision for the shared file system service for OpenStack -- ManilaManila derived from the Cinder project and provides a canonical storage provisioning control plane in [[OpenStack]] for shared or distributed file systems similarly to the way Cinder provides such a canonical control plane for block storage.
 +
The design and implementation of Manila provide extensibility for multiple backends (to support vendor or file system specific nuances / capabilities) but is sufficiently abstract to accommodate any of a variety of shared or distributed file system types.
  
 
[[File:Shares_Service.png]]
 
[[File:Shares_Service.png]]
  
According to IDC in its “[http://www.idc.com/getdoc.jsp?containerId=235910 Worldwide File-Based Storage 2012-2016 Forecast]", file-based storage continues to be a thriving market, with spending on File-based storage solutions to reach north of $34.6 billion in 2016. Of the 27 Exabyte’s (EB) of total disk capacity estimated to have shipped in 2012, IDC projected that nearly 18 EB were file-based capacity, accounting for over 65% of all disk shipped by capacity. A diversity of applications, from server virtualization to relational or distributed databases to collaborative content creation, often depend on the performance, scalability and simplicity of management associated with file-based systems, and the large ecosystem of supporting software products.  OpenStack, as the leading open IaaS capability, is increasingly contemplated as an option for deploying classic infrastructure in an "as a Service" model, but without specific accommodation for shared file systems represents an incomplete solution.
+
File-based storage continues to be a thriving market.   Diverse applications, from server virtualization to relational or distributed databases to collaborative content creation, can leverage the performance, scalability and simplicity of management associated with file-based systems, and the large ecosystem of supporting software products.   
 +
 
 +
While manila was designed to provide self-service provisioning and access control of file-shares to compute instances in multi-tenant OpenStack clouds, since it serves up storage over the network it can provide file-share infrastructure for clients running in other clouds or for bare-metal or VM hosts that themselves may provide shares for consumption by container workloads.
  
 
== Projects==
 
== Projects==
Line 12: Line 15:
 
{| border="1" cellpadding="2"
 
{| border="1" cellpadding="2"
 
| Source code
 
| Source code
| https://github.com/stackforge/manila
+
| https://github.com/openstack/manila
 
|-
 
|-
 
| Bug tracker
 
| Bug tracker
Line 24: Line 27:
 
{| border="1" cellpadding="2"
 
{| border="1" cellpadding="2"
 
| Source code
 
| Source code
| https://github.com/stackforge/python-manilaclient
+
| https://github.com/openstack/python-manilaclient
 
|-
 
|-
 
| Bug tracker
 
| Bug tracker
Line 32: Line 35:
 
| https://blueprints.launchpad.net/python-manilaclient
 
| https://blueprints.launchpad.net/python-manilaclient
 
|}
 
|}
 +
 +
=== Core Team ===
 +
 +
[https://review.openstack.org/#/admin/groups/213,members Current Core Team members]
  
 
=== Meetings ===
 
=== Meetings ===
  
 
[[Manila/Meetings|Project Agenda & Meetings]]
 
[[Manila/Meetings|Project Agenda & Meetings]]
 +
 +
[[Manila/JunoSummitPresentation|Overview Presentation from Juno (Atlanta) Summit]]
  
 
=== Getting Started with Manila ===
 
=== Getting Started with Manila ===
  
Instructions for getting started with Manila using Devstack are available at: [[Manila/IcehouseDevstack|Manila on Devstack]]
+
Instructions for getting started with Manila using Devstack are available at: [[Manila/KiloDevstack|Manila on Devstack]]
  
 
Developer documentation is still in progress, but is available in a draft state: [[Manila/docs|Manila Documentation]]
 
Developer documentation is still in progress, but is available in a draft state: [[Manila/docs|Manila Documentation]]
 +
 +
For general installation instructions, see the [http://docs.openstack.org/developer/manila/adminref/ Manila Administrator Reference].
 +
 +
Learn more about Shared File Systems from an [http://docs.openstack.org/admin-guide-cloud/shared_file_systems.html Administration] and [http://docs.openstack.org/security-guide/shared-file-systems.html Security] perspective.
  
 
=== Project Plan & Progress ===
 
=== Project Plan & Progress ===
  
[[Manila/ProjectPlan|Manila Project Plan]]<br />
+
[[Manila/SteinCycle|Manila Work for Stein Cycle]]<br />
Track progress towards [[Manila/Graduation|Manila Incubation & Graduation]].
 
  
 
== Design & Use Cases ==
 
== Design & Use Cases ==
Line 52: Line 64:
 
[[Manila/design|Manila Component Design]]<br />
 
[[Manila/design|Manila Component Design]]<br />
 
[[Manila/usecases|Manila Use Cases]]
 
[[Manila/usecases|Manila Use Cases]]
 +
{{Special:PrefixIndex/:Manila/design|hideredirects=1 }}
 +
 +
== Known issues ==
 +
 +
[[Manila/issue-neutron-on-localhost-ipv6|Connection to neutron failed.]]
  
 
== Subpages ==
 
== Subpages ==
  
{{Special:PrefixIndex/:Manila/}}
+
{{Special:PrefixIndex/:Manila/|hideredirects=1 }}
 +
 
 +
 
 +
[[Manila/ManilaWithGREtunnels]]
 +
 
 +
[[Manila/ManilaWithVXLANtunnels]]
 +
 
 +
[[Manila_devstack_script|Manila/Manila Devstack Script]]
 +
 
 +
[[Setting up Manila Network Plugins|Manila/Setting up Manila Network Plugins]]
  
[[Category:Manila]]
+
[[Category:Manila]]

Revision as of 14:04, 7 February 2019

Introduction

This page documents the concept and vision for the shared file system service for OpenStack -- Manila. Manila derived from the Cinder project and provides a canonical storage provisioning control plane in OpenStack for shared or distributed file systems similarly to the way Cinder provides such a canonical control plane for block storage. The design and implementation of Manila provide extensibility for multiple backends (to support vendor or file system specific nuances / capabilities) but is sufficiently abstract to accommodate any of a variety of shared or distributed file system types.

Shares Service.png

File-based storage continues to be a thriving market. Diverse applications, from server virtualization to relational or distributed databases to collaborative content creation, can leverage the performance, scalability and simplicity of management associated with file-based systems, and the large ecosystem of supporting software products.

While manila was designed to provide self-service provisioning and access control of file-shares to compute instances in multi-tenant OpenStack clouds, since it serves up storage over the network it can provide file-share infrastructure for clients running in other clouds or for bare-metal or VM hosts that themselves may provide shares for consumption by container workloads.

Projects

Manila

Source code https://github.com/openstack/manila
Bug tracker https://bugs.launchpad.net/manila
Feature tracker https://blueprints.launchpad.net/manila

Python Manila Client

Source code https://github.com/openstack/python-manilaclient
Bug tracker https://bugs.launchpad.net/python-manilaclient
Feature tracker https://blueprints.launchpad.net/python-manilaclient

Core Team

Current Core Team members

Meetings

Project Agenda & Meetings

Overview Presentation from Juno (Atlanta) Summit

Getting Started with Manila

Instructions for getting started with Manila using Devstack are available at: Manila on Devstack

Developer documentation is still in progress, but is available in a draft state: Manila Documentation

For general installation instructions, see the Manila Administrator Reference.

Learn more about Shared File Systems from an Administration and Security perspective.

Project Plan & Progress

Manila Work for Stein Cycle

Design & Use Cases

Manila Component Design
Manila Use Cases

Known issues

Connection to neutron failed.

Subpages


Manila/ManilaWithGREtunnels

Manila/ManilaWithVXLANtunnels

Manila/Manila Devstack Script

Manila/Setting up Manila Network Plugins