Detection of underlying openstack ladbalancer mechanism should consider region

[Hemanth Nakkina]

Currently the function to detect if Octavia is present in the underlying openstack [1] gets catalog across all regions and if octavia is detected in any one of the region then openstack-integrator considers Octavia is active. However the LB creation/deletion fails further if Octavia is not present in the same region as trust parameters passed to openstack-integrator.

The Octavia detection should return True only when Octavia is present in the same region as openstack creds/trust passed to the charm.

Usecase:
Cloud deployed with 2 regions. Region1 has Neutron LBaaS (older mechanism) and Region 2 has Octavia.
When openstack-integrator charm is deployed with openstack credentials of Region1, the charm detects Octavia is present in the cloud and tries to create Octavia LBs on Region1 and further fails.
The expectation in this case is openstack-integrator charm should default to NeutronLBaaS Implementation since Octavia is not present in that particular region and try creation of LBs with NeutronLBaaS mechanism.

[1] https://github.com/juju-solutions/charm-openstack-integrator/blob/9b805567c4d5d2dd4da7a33ecaa4ad7504d7e0ed/lib/charms/layer/openstack.py#L136-L140

[Hemanth Nakkina (hemanth-n)]

PR submitted for code review:
https://github.com/juju-solutions/charm-openstack-integrator/pull/49

[Hemanth Nakkina (hemanth-n)]

PR merged and so changing the status to Fix Committed

[George Kraft (cynerva)]

Cherry-pick to stable branch: https://github.com/charmed-kubernetes/charm-openstack-integrator/commit/e1eecb5a9b78a4c2b2a5fcece120e579fcf59e83

[Kevin W Monroe (kwmonroe)]

1.20+ck2 is no longer planned; this will go out with the upcoming 1.21 release.