Browse code
Remove multi-region workaround
When keystone API v3 was introduced, filtering regions when listing
endpoints was not supported (see [1]). This caused multi-region devstack
deployments to fail (see [2]). A workaround was introduced to devstack
to enable for multi-region deployments until region filtering would work
in keystone API v3.
Now that the bug related to region filtering in keystone is resolved,
the workaround should be removed.
[1]: https://bugs.launchpad.net/keystone/+bug/1482772
[2]: https://bugs.launchpad.net/devstack/+bug/1483784
Closes-Bug: #1511745
Related-Bug: #1483784
Related-Bug: #1482772
Change-Id: I52d13c3f5e7b77a7f8fb1be4dcea437988ebddfe
Daniel Gonzalez authored on 2015/10/30 22:25:41Showing 1 changed files
| ... | ... |
@@ -913,16 +913,11 @@ function get_or_create_service {
|
| 913 | 913 |
# Usage: _get_or_create_endpoint_with_interface <service> <interface> <url> <region> |
| 914 | 914 |
function _get_or_create_endpoint_with_interface {
|
| 915 | 915 |
local endpoint_id |
| 916 |
- # TODO(dgonzalez): The check of the region name, as done in the grep |
|
| 917 |
- # statement below, exists only because keystone does currently |
|
| 918 |
- # not allow filtering the region name when listing endpoints. If keystone |
|
| 919 |
- # gets support for this, the check for the region name can be removed. |
|
| 920 |
- # Related bug in keystone: https://bugs.launchpad.net/keystone/+bug/1482772 |
|
| 921 | 916 |
endpoint_id=$(openstack endpoint list \ |
| 922 | 917 |
--service $1 \ |
| 923 | 918 |
--interface $2 \ |
| 924 | 919 |
--region $4 \ |
| 925 |
- -c ID -c Region -f value | grep $4 | cut -f 1 -d " ") |
|
| 920 |
+ -c ID -f value) |
|
| 926 | 921 |
if [[ -z "$endpoint_id" ]]; then |
| 927 | 922 |
# Creates new endpoint |
| 928 | 923 |
endpoint_id=$(openstack endpoint create \ |