Support for external swift proxy
Users may have an external swift proxy already available (i.e. radosgw from already existing ceph, or hardware appliance implementing swift proxy). With this change user may specify an environment file that registers the specified urls as endpoint for the object-store service. The internal swift proxy is left as unconfigured. Change-Id: Ia568c3a5723d8bd8c2c37dbba094fc8a83b9d67e
This commit is contained in:
parent
77f45d6bf3
commit
da1cae2f84
|
@ -321,7 +321,7 @@ class tripleo::profile::base::keystone (
|
|||
if hiera('sahara_api_enabled', false) {
|
||||
include ::sahara::keystone::auth
|
||||
}
|
||||
if hiera('swift_proxy_enabled', false) {
|
||||
if hiera('swift_proxy_enabled', false) or hiera('external_swift_proxy_enabled',false) {
|
||||
include ::swift::keystone::auth
|
||||
}
|
||||
if hiera('tacker_enabled', false) {
|
||||
|
|
Loading…
Reference in New Issue