Use versionless keystone endpoint for barbican-related configurations
authorJuan Antonio Osorio Robles <jaosorior@redhat.com>
Wed, 7 Dec 2016 07:15:47 +0000 (09:15 +0200)
committerJuan Antonio Osorio Robles <jaosorior@redhat.com>
Wed, 25 Jan 2017 21:00:13 +0000 (23:00 +0200)
castellan (the key manager interface used by nova and cinder) is no
longer tied to keystone v3 [1]. So now it's possible to use versionless
endpoints for keystone.

[1] I124c0ea2d9403d6b530b33f18896c4e7bf4eabb5

Change-Id: Id5d893a6a41077ab76ca59295593a27be5c3004c

puppet/services/barbican-api.yaml

index 1f220e6..4e42075 100644 (file)
@@ -136,13 +136,13 @@ outputs:
           nova::compute::barbican_endpoint:
             get_param: [EndpointMap, BarbicanInternal, uri]
           nova::compute::barbican_auth_endpoint:
-            get_param: [EndpointMap, KeystoneV3Internal, uri]
+            get_param: [EndpointMap, KeystoneV3Internal, uri_no_suffix]
         cinder_api:
           cinder::api::keymgr_api_class: >
             castellan.key_manager.barbican_key_manager.BarbicanKeyManager
           cinder::api::keymgr_encryption_api_url:
             get_param: [EndpointMap, BarbicanInternal, uri]
           cinder::api::keymgr_encryption_auth_url:
-            get_param: [EndpointMap, KeystoneV3Internal, uri]
+            get_param: [EndpointMap, KeystoneV3Internal, uri_no_suffix]
       metadata_settings:
         get_attr: [ApacheServiceBase, role_data, metadata_settings]