Comment 2 for bug 1585241

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to manila (master)

Reviewed: https://review.openstack.org/318336
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=02ab18c5dfa8d49631052d9951b27d57a5340968
Submitter: Jenkins
Branch: master

commit 02ab18c5dfa8d49631052d9951b27d57a5340968
Author: Goutham Pacha Ravi <email address hidden>
Date: Tue May 17 10:55:20 2016 -0400

    Tooz integration

    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 <email address hidden>
    Co-Authored-By: Szymon Wroblewski <email address hidden>
    Co-Authored-By: Tom Barron <email address hidden>

    Related-Bug: #1585241
    Partially-implements: bp distributed-locking-with-tooz
    Change-Id: I710e86bd42034fa3b93b87ff77fa48ada8661168