04a3db2f9a
A series of enhancements can be performed in the share server migration operation, and share backends might support nondisruptive share server migrations, which was not covered in the previous approach. - Skip the destination share server network allocation if the driver is capable of reusing the source share server allocation. Manila will switch the allocations in the migration complete phase. - Allow share backends to reuse the share servers in case they are able to do so in a share server migration scenario. - Nondisruptive migration is now feasible depending on whether the share driver supports it and if the share network parameters have not changed. - Share servers will be always deleted whe the share server migration complete operation is finished. Depends-On: I43bd3fdafea02eb8e853114a57bfb863a441f3ed Co-Authored-By: Fabio Oliveira <fabioaurelio1269@gmail.com> Change-Id: I48bafd92fe7a4d4ae0bafd5bf1961dace56b6005
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:
git clone https://opendev.org/openstack/manila
For developer information please see HACKING.rst
You can raise bugs here https://bugs.launchpad.net/manila
Python client
https://opendev.org/openstack/python-manilaclient
- Documentation for the project can be found at:
https://docs.openstack.org/manila/latest/
- Release notes for the project can be found at:
https://docs.openstack.org/releasenotes/manila/
- Source for the project:
https://opendev.org/openstack/manila
- Bugs:
https://bugs.launchpad.net/manila
- Blueprints:
https://blueprints.launchpad.net/manila
- Design specifications are tracked at: