ecefc7d67a
As a new feature, os-brick now supports setting the location of file locks in a different location from the locks of the service. The functionality is intended for HCI deployments and hosts that are running Cinder and Glance using Cinder backend. In those scenarios the service can use a service specific location for its file locks while only sharing the location of os-brick with the other services. To leverage this functionality the new os-brick code is needed and method ``os_brick.setup`` needs to be called once the service configuration options have been loaded. The default value of the os-brick ``lock_path`` is the one set in ``oslo_concurrency``. This patch adds support for this new feature in a non backward compatible way, so it requires an os-brick version bump in the requirements. The patch also ensures that ``tox -egenconfig`` includes the os-brick configuration options when generating the sample config. Change-Id: I9f3e46c262f5b2b72fed5a4927165b3834a1c383
13 lines
530 B
YAML
13 lines
530 B
YAML
---
|
|
features:
|
|
- |
|
|
os-brick file lock location can be specified independently of the Cinder
|
|
service lock location using ``lock_path`` in the ``[os_brick]``
|
|
configuration section. Useful for HCI deployments and when running Cinder
|
|
and Glance with Cinder backend on the same host.
|
|
upgrade:
|
|
- |
|
|
On HCI deployments and when running Cinder and Glance with Cinder backend
|
|
on the same host an os-brick shared location can be configured using the
|
|
``lock_path`` in the ``[os_brick]`` configuration section.
|