After much deliberation and multiple design summit discussions, we have the impression that this is not to be treated as a bug. We will introduce a mechanism to provide distributed locking management underneath manila. However, deployers today have an option of using file locks living on a shared file system across distributed services.
It will not be back ported to the releases where this "bug" exists;
Please note, that tooz can also be used with no further configuration, i.e, default to using file locks as is the current behavior for the share replication feature to work as intended.
After much deliberation and multiple design summit discussions, we have the impression that this is not to be treated as a bug. We will introduce a mechanism to provide distributed locking management underneath manila. However, deployers today have an option of using file locks living on a shared file system across distributed services.
The tooz abstraction is proposed here: https:/ /review. openstack. org/#/c/ 318336
It will not be back ported to the releases where this "bug" exists;
Please note, that tooz can also be used with no further configuration, i.e, default to using file locks as is the current behavior for the share replication feature to work as intended.