c61c1977c2
In order to ensure that a share existed, we used to send the same request to Ceph as we would do with the share creation. In that request, we will set the share mode, which is a value set by the deployer through the `cephfs_volume_mode` config option. If the share was already created, Ceph would not override the value we were forwarding for the permission mode. After a bugfix [1], the value of mode started being reinforced when sent, even if the subvolume was already created. If the value for `cephfs_volume_mode` changed after the share was created, the mode is now being overwritten after manila startup on ensure_shares. Fixed this issue by modifying the ensure_shares to only confirm if the export exists. [1] https://tracker.ceph.com/issues/54375 Closes-Bug: #2002394 Change-Id: Ic5b5b42b882ce1346b4b46d1b29aa31740933e0e
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: