|
|
| (4 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | == Introduction ==
| + | #REDIRECT [[Manila]] |
| − | 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.
| |
| − | | |
| − | [[File:Shares_Service.png]]
| |
| − | | |
| − | According to IDC in its “Worldwide File-Based Storage 2012-2016 Forecast” (doc#235910, July 2012), 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 of 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.
| |
| − | | |
| − | == Projects==
| |
| − | | |
| − | === Project Plan ===
| |
| − | | |
| − | [[Manila/ProjectPlan|Manila Project Plan]]
| |
| − | | |
| − | === Manila ===
| |
| − | | |
| − | {| border="1" cellpadding="2"
| |
| − | | Source code
| |
| − | | https://github.com/stackforge/manila
| |
| − | |-
| |
| − | | Bug tracker
| |
| − | | https://bugs.launchpad.net/manila
| |
| − | |-
| |
| − | | Feature tracker
| |
| − | | https://blueprints.launchpad.net/manila
| |
| − | |}
| |
| − | | |
| − | === Python Manila Client ===
| |
| − | {| border="1" cellpadding="2"
| |
| − | | Source code
| |
| − | | https://github.com/stackforge/python-manilaclient
| |
| − | |-
| |
| − | | Bug tracker
| |
| − | | https://bugs.launchpad.net/python-manilaclient
| |
| − | |-
| |
| − | | Feature tracker
| |
| − | | https://blueprints.launchpad.net/python-manilaclient
| |
| − | |}
| |
| − | | |
| − | === Meetings ===
| |
| − | | |
| − | [[Manila/Meetings|Manila Project Agenda & Meetings]]
| |
| − | | |
| − | === Contributing to Manila ===
| |
| − | | |
| − | Developer documentation is still in progress, but is available in a draft state: [[Manila/docs|Manila Documentation]]
| |
| − | | |
| − | === Incubation / Graduation ===
| |
| − | | |
| − | Track progress towards [[Manila/Graduation|Manila Incubation & Graduation]].
| |
| − | | |
| − | == Design & Use Cases ==
| |
| − | | |
| − | [[Manila/design|Manila Component Design]]
| |
| − | [[Manila/usecases|Manila Use Cases]]
| |
| − | | |
| − | == Subpages ==
| |
| − | | |
| − | {{Special:PrefixIndex/:Manila/}}
| |
| − | | |
| − | [[Category:Manila]]
| |
