3b9ba1d3a7
In a Manila deployment using the Generic driver, it is possible
that the administrator has deployed manila-share on a machine that
already has access to the admin network used by Manila by being on
the same VLAN for example.
This means that it's not necessary for it to attempt to plug the ports
and do all the wiring due to the fact that it's already reachable,
therefore this patch introduces a new `interface_driver` which is
does nothing in order to avoid plugging/unplugging ports and avoiding
the requirement of running neutron-(openvswitch|linuxbridge)-agent
on the same node as manila-share.
The tests are pretty trivial because there's not much logic, but we
at least make sure that we don't call any ip_lib functions which means
we're not touching anything in host networking.
Change-Id: I2c3d6e4234bf7185b8da3c8e1701069c3a165ffc
(cherry picked from commit
|
||
---|---|---|
api-ref/source | ||
contrib | ||
devstack | ||
doc | ||
etc | ||
manila | ||
playbooks | ||
rally-jobs | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.pylintrc | ||
.stestr.conf | ||
.zuul.yaml | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
README.rst | ||
babel.cfg | ||
bindep.txt | ||
lower-constraints.txt | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
Team and repository tags
MANILA
You have come across an OpenStack shared file system service. It has identified itself as "Manila." It was abstracted from the Cinder project.
- Wiki: https://wiki.openstack.org/wiki/Manila
- Developer docs: https://docs.openstack.org/manila/latest/
Getting Started
If you'd like to run from the master branch, you can clone the git repo:
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: