openstack/manila
Code Issues Proposed changes

Merge "Add doc for an Introduction to Manila"

Browse Source
This commit is contained in:
Jenkins 2014-09-24 17:44:31 +00:00 committed by Gerrit Code Review
commit 559f675e2c
2 changed files with 45 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
doc/source/devref/index.rst
View File

@ -62,6 +62,7 @@ Module Reference
.. toctree::
:maxdepth: 3
intro
services
database
share

44
doc/source/devref/intro.rst Normal file
View File

@ -0,0 +1,44 @@
..
Licensed under the Apache License, Version 2.0 (the "License"); you may
not use this file except in compliance with the License. You may obtain
a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
License for the specific language governing permissions and limitations
under the License.
Introduction to Manila Shared Filesystem Management Service
===========================================================
Manila is the file share service project for OpenStack. Manila provides the
management of file shares for example, NFS and CIFS as a core service to
OpenStack. Manila currently works with NetApp, Red Hat storage (GlusterFS)
and EMC VNX, as well as on a base Linux NFS server. There are a number of
concepts that will help in better understanding of the solutions provided by
Manila. One aspect can be to explore the different service possibilities
provided by Manila.
Manila, depending on the driver, requires the user by default to create a
share network using neutron-net-id and neutron-subnet-id (GlusterFS native
driver does not require it). After creation of the share network, the user
can proceed to create the shares. Users in Manila can configure multiple
back-ends just like Cinder. Manila has a share server assigned to every
tenant. This is the solution for all back-ends except for GlusterFS. The
customer in this scenario is prompted to create a share server using neutron
net-id and subnet-id before even trying to create a share.
The current low-level services available in Manila are:
- manila-api: The manila-api service is a service that authenticates and
routes requests throughout the Shared Filesystem service.
- manila-scheduler: The manila-scheduler is responsible for
scheduling/routing requests to the appropriate share service. It does that
by picking one back-end while filtering all except one back-end.
- manila-share: The manila-share service is responsible for managing Shared
File Service devices, specifically the back-end devices.