Configure authtoken in Nova Placement
authorDan Prince <dprince@redhat.com>
Mon, 13 Feb 2017 15:07:24 +0000 (10:07 -0500)
committerAlex Schultz <aschultz@redhat.com>
Tue, 21 Feb 2017 21:40:43 +0000 (14:40 -0700)
commitfb6965116d567a061a42d077d51c3ca2d220f46d
tree4c5894fbb32b2ea4820374a7233d0d41eb15eea0
parent71f655326be5eee7e030946fb6dd6cd4ba03b640
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 <aschultz@redhat.com>
Puppetfile_extras
manifests/profile/base/nova/api.pp
manifests/profile/base/nova/authtoken.pp [new file with mode: 0644]
manifests/profile/base/nova/placement.pp
spec/classes/tripleo_profile_base_nova_api_spec.rb
spec/classes/tripleo_profile_base_nova_authtoken_spec.rb [new file with mode: 0644]
spec/classes/tripleo_profile_base_nova_placement_spec.rb [new file with mode: 0644]