02ab18c5df
Manila currently uses file locks from oslo_concurrency to coordinate operations racing with each other to perform a particular action. In many situations, deployers may need a distributed lock to a local file lock (or even a file lock living on a shared file system). This need is accentuated if they were running Manila services in HA or if they were using Share Replication across AZs where manila-share services were running off different controllers that would not be able to share a common oslo_concurrency file lock or be protected against service/lock management failures. Integrate Tooz library with helper methods to create a locking coordinator and allow deployers to make the choice between file and distributed locks. Start the manila share service with Tooz backed coordination. Replace the locks used for Share Replication work-flows in the share manager to use Tooz based locks. Co-Authored-By: Goutham Pacha Ravi <gouthampravi@gmail.com> Co-Authored-By: Szymon Wroblewski <szymon.wroblewski@intel.com> Co-Authored-By: Tom Barron <tpb@dyncloud.net> Related-Bug: #1585241 Partially-implements: bp distributed-locking-with-tooz Change-Id: I710e86bd42034fa3b93b87ff77fa48ada8661168 |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| test_all.py | ||
| test_api.py | ||
| test_data.py | ||
| test_manage.py | ||
| test_scheduler.py | ||
| test_share.py | ||