Remove the usage of KEYSTONE_CATALOG_BACKEND
It was removed from DevStack before the Ocata release, see https://review.openstack.org/#/c/391380/ The support for the only alternative (templated catalog) was removed even earlier, before Mitaka: https://review.openstack.org/#/c/278333/ This means that the entry points for Swift can always be configured when RadosGW is enabled. Change-Id: I25c1f963665fab1dc77db40a2742dc29a9c1ee0b
This commit is contained in:
parent
1731d2364c
commit
6d1ef658c9
|
@ -609,9 +609,7 @@ function configure_ceph_embedded_rgw_paths {
|
||||||
function configure_ceph_embedded_rgw {
|
function configure_ceph_embedded_rgw {
|
||||||
configure_ceph_embedded_rgw_paths
|
configure_ceph_embedded_rgw_paths
|
||||||
# keystone endpoint for radosgw
|
# keystone endpoint for radosgw
|
||||||
if [[ "$KEYSTONE_CATALOG_BACKEND" = 'sql' ]]; then
|
_create_swift_endpoint
|
||||||
_create_swift_endpoint
|
|
||||||
fi
|
|
||||||
|
|
||||||
# Create radosgw service user with admin privileges
|
# Create radosgw service user with admin privileges
|
||||||
create_service_user "radosgw" "admin"
|
create_service_user "radosgw" "admin"
|
||||||
|
|
Loading…
Reference in New Issue