openstack/manila
Code Issues Proposed changes
Shared filesystem management project for OpenStack.
2,225 Commits 11 Branches 78 Tags 178 MiB
Python 99.3%
Shell 0.7%
dcbdcf3534
Go to file
Valeriy Ponomaryov dcbdcf3534 Implement export location metadata feature 
Some upcoming features require more than one export location and
possibility to mark them with specific labels like fast/slow or
rw/ro.

So, implement 'export locations metadata' feature:
- It allows to set any key-value pairs for each export location.
- These key-value pairs can be set only by share manager using
  response from various share driver methods.
- Example of update is implemented using Generic driver
  "create_instance" method.
- Metadata can be updated for any export location in any place
  of share manager where db function "share_export_locations_update"
  is called.
- Keys from export location metadata table will be added to 'share' and
  'share instances' views as export location attributes.

Also:
- Add new attr 'is_admin_only' for existing export locations model.
  If set to True, then only admins will be able to see them. Unless
  policy is changed.
- Add APIs for reading export locations by share and share instance IDs.
- Remove 'export_location' and 'export_locations' attrs
  from 'share' and 'share instance' views.
- Bump microversion as new APIs implemented.

APIImpact

Implements bp export-location-metadata

Change-Id: I36d1aa8d9302e097ffb08d239cf7a81101d2c1cb
2016-01-15 12:29:12 +02:00
contrib Use new approach for setting up CI jobs 2016-01-08 18:02:59 +02:00
devstack Make Manila UI be installed after Horizon 2016-01-08 22:56:37 +02:00
doc Merge "QoS support for shares" 2016-01-15 07:18:11 +00:00
etc Implement export location metadata feature 2016-01-15 12:29:12 +02:00
manila Implement export location metadata feature 2016-01-15 12:29:12 +02:00
manila_tempest_tests Implement export location metadata feature 2016-01-15 12:29:12 +02:00
releasenotes Implement export location metadata feature 2016-01-15 12:29:12 +02:00
tools Last sync to Manila from oslo-incubator 2015-11-20 19:20:21 +00:00
.coveragerc Fix 'cover' tox job 2015-09-21 15:09:22 +03:00
.gitignore Add reno for release notes management 2015-11-26 07:16:03 +01:00
.gitreview Move from stackforge to openstack 2014-09-19 21:23:02 +00:00
.testr.conf Use oslotest.base.BaseTestCase as test base class 2015-01-04 08:43:52 +01: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 Performance: leverage dict comprehension in PEP-0274 2015-12-11 19:24:56 -05:00
LICENSE Initialize from cinder 2013-08-08 10:34:06 -04:00
openstack-common.conf Remove unused manila/openstack/common/eventlet_backdoor.py 2015-06-25 11:47:37 +02:00
pylintrc docs 2013-09-17 10:57:47 +03:00
README.rst Adapt readme to usual structure 2015-01-23 08:18:06 +01:00
requirements.txt Updated from global requirements 2016-01-07 14:00:43 +00:00
run_tests.sh Enable bashate during pep8 run 2015-03-18 13:40:03 +01:00
setup.cfg Remove version per M-1 release instructions 2015-12-03 14:22:13 -05:00
setup.py Updated from global requirements 2015-09-18 20:43:19 +00:00
test-requirements.txt Updated from global requirements 2015-12-11 15:20:17 +00:00
tox.ini Add debug testenv in tox 2016-01-11 19:39:08 +08:00

README.rst

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://github.com/openstack/manila.git

For developer information please see HACKING.rst

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

Python client

https://github.com/openstack/python-manilaclient.git