Goutham Pacha Ravi 22d25e834d Configure per backend availability zones in devstack
Every enabled backend gets assigned to its own AZ.
Test cases in manila-tempest-plugin already exercise
creating shares (and replicas) across AZs when
multiple AZs are available.

This is done for all back-end drivers that are not
the Generic driver. Configuring backend AZ for each
Generic driver based back end will require configuring
Nova and Cinder in a similar fashion.

Partially-implements: bp per-backend-availability-zones
Depends-On: https://review.openstack.org/#/c/630886/
Depends-On: https://review.openstack.org/#/c/629958/
Change-Id: I1b6ff535a22f10e70d379377767c8ffac3ef5286
2019-01-23 14:30:18 -08:00
2019-01-08 19:05:53 +00:00
2017-03-30 15:12:22 +03:00
2018-10-11 15:13:49 -04:00
2017-10-25 11:57:46 -04:00
2014-09-19 21:23:02 +00:00
2018-10-11 15:13:49 -04:00
2013-08-08 10:34:06 -04:00
2013-08-08 10:34:06 -04:00
2017-03-03 22:51:04 +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/

Description
Shared filesystem management project for OpenStack.
Readme 180 MiB
Languages
Python 99.3%
Shell 0.7%