The backend_url option can sometimes contain secrets.
For example when redis coordination backend is used and authentication
is enabled in redis, the plain redis password is put as an URL element.
[coordination]
backend_url=redis://:password@127.0.0.1:6379
Closes-Bug: #2012246
Change-Id: Ia815720cedda2f5c70205ffda5c765364cee8f8c
When old coordination options were deprecated [1]
the wrong release version for manila Pike was used,
so fix this.
TrivialFix
[1] I86ef7a092a3ab7fd0a90ab664b7f9f62a275901b
Change-Id: I245ddd52894e37d9fd3c968e05550a2aa7fc2180
Since a few versions, tooz can manage the heartbeat entirely
internally.
Use that feature and simplify the manila code.
See Cinder change [1].
Closes-Bug: #1691323
[1] I7fa654caf6620d410d4e297d3d8af2215e27ed12
Change-Id: I86ef7a092a3ab7fd0a90ab664b7f9f62a275901b
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
Takashi Kajinami