RETIRED, further work has moved to Debian project infrastructure
6c04272429
Add filtering share-network list by creation date, associated security service ID, project ID (for admin context only). Limit share network list using 'offset' and 'limit' options. Add policy rule for 'get_all_share_networks' action. Remove 'status' field from returned share nerwork's view, as share_network model doesn't have such attribute. So, None was always returned as a status. Fix DB api function share_network_get_all_by_security_service - second param should be named 'security_service_id' instead of 'share_network_id'. Add unit and tempest tests. Implements bp improve-share-network-list-filtering Change-Id: I7c3e44068fb39672d1d6c9e06527fde2604672a9 |
||
---|---|---|
bin | ||
contrib | ||
doc | ||
etc | ||
manila | ||
tools | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
babel.cfg | ||
CONTRIBUTING.md | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
openstack-common.conf | ||
pylintrc | ||
README.rst | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
The Choose Your Own Adventure README for Manila
You have come across an OpenStack shared filesystem service. It has identified itself as "Manila." It was abstracted from the Cinder project.
To monitor it from a distance: follow @openstack on twitter.
To tame it for use in your own cloud: read http://docs.openstack.org
To study its anatomy: read https://wiki.openstack.org/wiki/Manila
To dissect it in detail: visit http://github.com/openstack/manila
To taunt it with its weaknesses: use http://bugs.launchpad.net/manila
To watch it: http://jenkins.openstack.org
To hack at it: read HACKING.rst
To cry over its pylint problems: http://jenkins.openstack.org/job/manila-pylint/violations