Difference between revisions of "Manila"
m (→Subpages) |
(→Introduction) |
||
(13 intermediate revisions by 6 users not shown) | |||
Line 1: | Line 1: | ||
== Introduction == | == Introduction == | ||
− | This page documents the concept and vision for | + | 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. | ||
[[File:Shares_Service.png]] | [[File: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== | == Projects== | ||
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 === | ||
Line 44: | Line 51: | ||
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/ | + | [[Manila/SteinCycle|Manila Work for Stein Cycle]]<br /> |
− | |||
== Design & Use Cases == | == Design & Use Cases == | ||
Line 54: | 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 == | == Known issues == | ||
Line 62: | Line 72: | ||
== Subpages == | == Subpages == | ||
− | {{Special:PrefixIndex/:Manila/}} | + | {{Special:PrefixIndex/:Manila/|hideredirects=1 }} |
+ | |||
+ | |||
[[Manila/ManilaWithGREtunnels]] | [[Manila/ManilaWithGREtunnels]] | ||
Line 69: | Line 81: | ||
[[Manila_devstack_script|Manila/Manila Devstack Script]] | [[Manila_devstack_script|Manila/Manila Devstack Script]] | ||
− | [[Setting up Manila Network Plugins|Setting up Manila Network Plugins]] | + | [[Setting up Manila Network Plugins|Manila/Setting up Manila Network Plugins]] |
− | + | [[Category:Manila]] |
Revision as of 14:04, 7 February 2019
Contents
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.
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
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
Design & Use Cases
Manila Component Design
Manila Use Cases
- Manila/design
- Manila/design/
- Manila/design/access groups
- Manila/design/manila-auth-access-keys
- Manila/design/manila-ceph-native-driver
- Manila/design/manila-generic-groups
- Manila/design/manila-liberty-consistency-groups
- Manila/design/manila-liberty-consistency-groups/api-schema
- Manila/design/manila-mitaka-data-replication
- Manila/design/manila-newton-hpb-support
Known issues
Subpages
- Manila/API
- Manila/Concepts
- Manila/Debugging
- Manila/Etherpads
- Manila/Graduation
- Manila/IPv6
- Manila/IcehouseDevstack
- Manila/Ideas Backlog
- Manila/Incubation Application
- Manila/JunoSummitPresentation
- Manila/Kilo Network Changes
- Manila/Kilo Network Spec
- Manila/ManilaFileShareAccessOfAD
- Manila/ManilaWithGREtunnels
- Manila/ManilaWithVXLANtunnels
- Manila/Manila Storage Integration Patterns
- Manila/Meetings
- Manila/MountAutomation
- Manila/Networking
- Manila/Networking/Gateway mediated
- Manila/Program Application
- Manila/ProjectPlan
- Manila/Provide private data storage API for drivers
- Manila/QoS
- Manila/Quobyte
- Manila/Replication Design Notes
- Manila/Replication Use Cases
- Manila/SAP enterprise team
- Manila/SteinCycle
- Manila/TrainCycle
- Manila/design
- Manila/design/
- Manila/design/access groups
- Manila/design/manila-auth-access-keys
- Manila/design/manila-ceph-native-driver
- Manila/design/manila-generic-groups
- Manila/design/manila-liberty-consistency-groups
- Manila/design/manila-liberty-consistency-groups/api-schema
- Manila/design/manila-mitaka-data-replication
- Manila/design/manila-newton-hpb-support
- Manila/docs
- Manila/docs/API-roadmap
- Manila/docs/HOWTO use manila with horizon
- Manila/docs/HOWTO use tempest with manila
- Manila/docs/Manila Developer Setup Fedora19
- Manila/docs/Setting up DevStack with Manila on Fedora 20
- Manila/docs/db
- Manila/issue-neutron-on-localhost-ipv6
- Manila/specs/scenario-tests
- Manila/specs/split-storage-actions-computing-and-networking
- Manila/usecases