From fb6965116d567a061a42d077d51c3ca2d220f46d Mon Sep 17 00:00:00 2001 From: Dan Prince Date: Mon, 13 Feb 2017 10:07:24 -0500 Subject: Configure authtoken in Nova Placement The Nova Placement API's configuration currently relies on the nova-api profile for its keystone authtoken configuration. This means that Nova Placement would fail if it got installed on an isolated node or docker container (this currently breaks TripleO's deployment of placement via docker). This patch creates a new authtoken profile and calls it via the api and placement roles. Change-Id: I7b38ab6ba5cae41689ac500d97dec4d09c73d387 Co-Authored-By: Alex Schultz --- spec/classes/tripleo_profile_base_nova_api_spec.rb | 3 +++ 1 file changed, 3 insertions(+) (limited to 'spec/classes/tripleo_profile_base_nova_api_spec.rb') diff --git a/spec/classes/tripleo_profile_base_nova_api_spec.rb b/spec/classes/tripleo_profile_base_nova_api_spec.rb index 070a1f1..3a2a685 100644 --- a/spec/classes/tripleo_profile_base_nova_api_spec.rb +++ b/spec/classes/tripleo_profile_base_nova_api_spec.rb @@ -26,6 +26,9 @@ describe 'tripleo::profile::base::nova::api' do oslomsg_rpc_username => 'nova', oslomsg_rpc_password => 'foo' } + class { '::tripleo::profile::base::nova::authtoken': + step => #{params[:step]}, + } eos end -- cgit 1.2.3-korg