b72c034885
OS-Brick uses file locks to ensure single access to critital sections, and uses the oslo concurrency "lock_path" configuration option to determine where to create these locks. This is fine when each host has a single service using os-brick, which is the case of Compute nodes and Controller nodes where Glance is not using Cinder as its backend. The problem happens when we have an HCI deployment where Cinder and Nova are collocated on the same host or when Glance uses Cinder as its backend and is running on the same host. In those scenarios os-brick will create file locks in different paths for each service, which is not the intended behavior. A possible solutions is to set the "lock_path" of all the services to the same location, which is not great, not only because we'll have all nova, cinder, glance, and os-brick locks mixed in a single location (service prefixes help a bit here), but also because then Cinder will have permissions on the Nova and Glance locks, which doesn't seem right. This patch introduces a new mechanism in os-brick to have its own "lock_path" configuration option in the "os_brick" group. It defaults to the current behavior if not explicitly defined, so it will use olso concurrency's "lock_path". To do this the patch introduces the oslo.config dependency and adds a new "setup" method that sets the default of the os_brick "lock_path". This new "setup" method is required because the order in which configuration options for the different namespaces are imported cannot be guaranteed, so the setup must be called *after* the service has already imported all (or at least the ones os-brick cares about) configuration option namespaces. In other words, when os-brick files are loaded the value for oslo concurrency's "lock_path" is not yet known, so it cannot be used as a default, and the oslo_config substitution feature does not support values from other namespaces, so we cannot default the "lock_path" from the os_brick namespace to the value in "oslo_concurrency". Since the value that is going to be used as the "lock_path" is not known until the "setup" method is called, we cannot use the standard "synchronized" method from "oslo_concurrency.lock_utils" and we need to use our own. In the current os-brick code, each connector that requires a lock is importing and creating its own "synchronized" instance, but this patch changes this behavior and creates a single instance, just like Cinder does. This feature requires changes in multiple projects -os-brick, cinder, nova, glance, glance_store, devstack- to be fully supported, but this is the base of all this effort. Change-Id: Ic52338278eb5bb3d90ce582fe6b23f37eb5568c4
19 lines
651 B
Plaintext
19 lines
651 B
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
|
|
pbr>=5.8.0 # Apache-2.0
|
|
eventlet>=0.30.1,!=0.32.0 # MIT
|
|
oslo.concurrency>=4.5.0 # Apache-2.0
|
|
oslo.config>=8.1.0 # Apache-2.0
|
|
oslo.context>=3.4.0 # Apache-2.0
|
|
oslo.log>=4.6.1 # Apache-2.0
|
|
oslo.i18n>=5.1.0 # Apache-2.0
|
|
oslo.privsep>=2.6.2 # Apache-2.0
|
|
oslo.serialization>=4.2.0 # Apache-2.0
|
|
oslo.service>=2.8.0 # Apache-2.0
|
|
oslo.utils>=4.12.1 # Apache-2.0
|
|
requests>=2.25.1 # Apache-2.0
|
|
tenacity>=6.3.1 # Apache-2.0
|
|
os-win>=5.5.0 # Apache-2.0
|