First of all, I would like to say that swift has its own definition of region: regions are used to store replicas in different geographical locations [1]. Swift regions configuration is stored in swift ring.
On the other hand, openstack looks at a region as a separate openstack deployments with some common services (like Horizon and Keystone) [2]
It is essential to note that it is impossible to configure an openstack region for swift with fuel, since we use the region only to describe keystone's connection. [3]
IMO this bug is kind of incomplete, since there is no information about the way the customer configured a region for swift. I will ask Nikita to comment on it.
I have few remarks about this bug. IMO it is not as simple as it looks like. It is easy to change add something like https:/ /github. com/openstack/ solum/blob/ master/ contrib/ lp-cedarish/ docker/ swift-handler. py#L46 to sahara's code, but this will not fix original issue.
First of all, I would like to say that swift has its own definition of region: regions are used to store replicas in different geographical locations [1]. Swift regions configuration is stored in swift ring.
On the other hand, openstack looks at a region as a separate openstack deployments with some common services (like Horizon and Keystone) [2]
It is essential to note that it is impossible to configure an openstack region for swift with fuel, since we use the region only to describe keystone's connection. [3]
IMO this bug is kind of incomplete, since there is no information about the way the customer configured a region for swift. I will ask Nikita to comment on it.
[1] https:/ /www.swiftstack .com/docs/ admin/cluster_ management/ regions. html /docs.openstack .org/arch- design/ arch-requiremen ts/arch- requirements- ha.html /github. com/fuel- infra/puppet- swift/blob/ 8.2.0/manifests /keystone/ auth.pp
[2] https:/
[3] https:/