Shared filesystem management project for OpenStack.
Go to file
Goutham Pacha Ravi a75fe3d7cc Allow configuration of a back end specific availability zone
"storage_availability_zone" in the [DEFAULT] section of
manila's configuration file has allowed deployers to configure
and manage both service (scheduler, share manager) and storage
system availability. However, quite often manila's services
(api, scheduler, share and data managers) are run on a dedicated
control plane that is a different failure domain from that of
the storage that manila manages.

Also, when using share replication, deployers would need to
run multiple manila share manager services with different
configuration files, each with their own
"storage_availability_zone".

To allow flexibility of separating service and storage
availability zones, we introduce a new configuration option
"backend_availability_zone" within the share driver/backend
section. When this option is used, it will override the value
of the "storage_availability_zone" from the [DEFAULT] section.

Change-Id: Ice99a880dd7be7af94dea86b31a6db88be3d7d9b
Implements: bp per-backend-availability-zones
2019-01-23 17:13:24 +00:00
api-ref/source [api-ref] Added share servers show and corrected path to details 2018-11-20 11:34:27 +01:00
contrib Convert dummy job to py3 2019-01-08 19:05:53 +00:00
devstack devstack: Do a vgscan before checking if the VG is there 2019-01-04 12:01:34 +01:00
doc Allow configuration of a back end specific availability zone 2019-01-23 17:13:24 +00:00
etc [LVM] Run filesystem check before assigning UUID 2018-10-16 16:52:04 -07:00
manila Allow configuration of a back end specific availability zone 2019-01-23 17:13:24 +00:00
playbooks Convert dummy job to py3 2019-01-08 19:05:53 +00:00
rally-jobs [Rally] fix jobs 2017-03-30 15:12:22 +03:00
releasenotes Allow configuration of a back end specific availability zone 2019-01-23 17:13:24 +00:00
tools Simplify running pylint 2018-10-11 15:13:49 -04:00
.coveragerc Impove coverage job accuracy 2017-10-25 11:57:46 -04:00
.gitignore Remove the nonexistent install-guide directory 2018-02-24 10:45:01 +08:00
.gitreview Move from stackforge to openstack 2014-09-19 21:23:02 +00:00
.pylintrc Simplify running pylint 2018-10-11 15:13:49 -04:00
.stestr.conf tests: replace .testr.conf with .stestr.conf 2017-09-13 07:56:21 -04:00
.zuul.yaml Merge "Publish sample config file in the genconfig job" 2019-01-08 11:37:41 +00:00
babel.cfg Initialize from cinder 2013-08-08 10:34:06 -04:00
CONTRIBUTING.rst Added CONTRIBUTING file in .rst format 2015-11-15 23:45:38 +05:30
HACKING.rst Fix the duplicate hacking check M312 and H203 2017-08-13 08:01:42 +08:00
LICENSE Initialize from cinder 2013-08-08 10:34:06 -04:00
lower-constraints.txt Add manila-status upgrade check command framework 2018-10-19 12:53:03 +05:30
README.rst Use the canonical URL for Manila repositories 2018-12-17 13:56:17 +01:00
requirements.txt Add manila-status upgrade check command framework 2018-10-19 12:53:03 +05:30
run_tests.sh Remove --omit argument in run_tests.sh 2017-07-04 18:21:48 +07:00
setup.cfg Change openstack-dev to openstack-discuss 2018-12-03 21:23:31 -05:00
setup.py Updated from global requirements 2017-03-03 22:51:04 +00:00
test-requirements.txt Updated from global requirements 2018-03-23 01:06:24 +00:00
tox.ini Merge "change tox envlist from 3.5 to 3" 2018-10-17 02:05:40 +00:00

Team and repository tags

image

MANILA

You have come across an OpenStack shared file system service. It has identified itself as "Manila." It was abstracted from the Cinder project.

Getting Started

If you'd like to run from the master branch, you can clone the git repo:

git clone https://git.openstack.org/openstack/manila.git

For developer information please see HACKING.rst

You can raise bugs here https://bugs.launchpad.net/manila

Python client

https://git.openstack.org/cgit/openstack/python-manilaclient.git

  • Release notes for the project can be found at:

https://docs.openstack.org/releasenotes/manila/