36db3f3917
Several things are implemented: - Allocation/deallocation now handled by drivers instead of share manager. It provides flexibility for drivers. - Network plugin interface was updated to support new approach for configuration options setting. Config opts for network plugin can be defined via three sources: a) using separate config group b) using config group of back end c) using DEFAULT config group Variants (a) and (b) are mutually exclusive, there are switched by opt 'network_config_group' that belongs to share driver interface. Implements bp network-helper Change-Id: I3b05369f01777675c1b834af5ee076d8b7219a0f |
||
---|---|---|
bin | ||
contrib | ||
doc | ||
etc | ||
manila | ||
tools | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
CONTRIBUTING.md | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
babel.cfg | ||
openstack-common.conf | ||
pylintrc | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
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