| 1 |
--- |
| 2 |
features: |
| 3 |
- | |
| 4 |
Added two new configuration options to support region filtering in multi-region |
| 5 |
OpenStack deployments: ``backup_swift_region_name`` in the ``[DEFAULT]`` section |
| 6 |
for Swift backup driver region selection, and ``region_name`` in the ``[glance]`` |
| 7 |
section for Glance client region selection. These options allow Cinder to |
| 8 |
correctly connect to services in the specified region when multiple regions are |
| 9 |
configured in the Keystone service catalog. |
| 10 |
|
| 11 |
upgrade: |
| 12 |
- | |
| 13 |
Two new configuration options have been added for multi-region deployments: |
| 14 |
``backup_swift_region_name`` in the ``[DEFAULT]`` section and ``region_name`` in |
| 15 |
the ``[glance]`` section. These options are optional and default to not filtering |
| 16 |
by region (backward compatible behavior). Deployers in multi-region environments |
| 17 |
should configure these options to ensure Cinder connects to the correct regional |
| 18 |
endpoints for Glance and Swift services. |
| 19 |
|
| 20 |
fixes: |
| 21 |
- | |
| 22 |
Fixed the Glance client endpoint selection logic to properly filter endpoints |
| 23 |
by region when ``region_name`` is configured in the ``[glance]`` section. The |
| 24 |
previous implementation could incorrectly append endpoints when region_name |
| 25 |
was not configured. Now, when ``region_name`` is set, Cinder will only use |
| 26 |
endpoints that match the specified region. If no matching endpoint is found, |
| 27 |
it falls back to the first available endpoint. When ``region_name`` is not |
| 28 |
configured, Cinder uses the first endpoint (backward compatible behavior). |
| 29 |
This ensures correct behavior in multi-region OpenStack deployments. |