Difference between revisions of "Manila"
(→Meetings) |
(→Design & Use Cases) |
||
Line 83: | Line 83: | ||
The following wiki documents are design specifications. They should not be treated as documentation. Since the Newton release, design specifications are hosted [http://specs.openstack.org/openstack/manila-specs/ here] | The following wiki documents are design specifications. They should not be treated as documentation. Since the Newton release, design specifications are hosted [http://specs.openstack.org/openstack/manila-specs/ here] | ||
− | [[Manila/design|Manila Component Design]] | + | * [[Manila/JunoSummitPresentation|Overview Presentation from Juno (Atlanta) Summit]] |
− | [[Manila/usecases|Manila Use Cases]] | + | * [[Manila/design|Manila Component Design]] |
+ | * [[Manila/usecases|Manila Use Cases]] | ||
+ | |||
{{Special:PrefixIndex/:Manila/design|hideredirects=1 }} | {{Special:PrefixIndex/:Manila/design|hideredirects=1 }} | ||
Revision as of 07:52, 25 April 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://opendev.org/openstack/manila |
Bug tracker | https://bugs.launchpad.net/manila |
Feature tracker | https://blueprints.launchpad.net/manila |
Documentation | https://docs.openstack.org/manila/latest/ |
Python Manila Client
Source code | https://opendev.org/openstack/python-manilaclient |
Bug tracker | https://bugs.launchpad.net/python-manilaclient |
Feature tracker | https://blueprints.launchpad.net/python-manilaclient |
Documentation | https://docs.openstack.org/python-manilaclient/latest/ |
Manila UI Plugin
Source code | https://opendev.org/openstack/manila-ui |
Bug tracker | https://bugs.launchpad.net/manila-ui |
Feature tracker | https://blueprints.launchpad.net/manila-ui |
Documentation | https://docs.openstack.org/manila-ui/latest/ |
Core Team
Meetings
Documentation
- Contributor Guide
- Installation Guide
- User Guide
- Administrator Guide
- API Reference
- Configuration Reference
- Security Guide
Project Plan & Progress
Design & Use Cases
The following wiki documents are design specifications. They should not be treated as documentation. Since the Newton release, design specifications are hosted here
- 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