Fix Blazar Nova aggregate in multi-region setup

The Nova aggregate was always defaulting to some region (usually first
in the Keystone endpoint list) when registering the Nova aggregate for
Blazar. Add in a region override to ensure we are always writing to the
region being deployed.

Change-Id: I3f921ac51acab1b1020a459c07c755af7023e026
This commit is contained in:
Jason 2019-03-07 17:28:58 -06:00 committed by Jason Anderson
parent 114521ccba
commit f20cbf4958
No known key found for this signature in database
GPG Key ID: 9207452BF63947DD
1 changed files with 1 additions and 0 deletions

View File

@ -41,6 +41,7 @@
--os-username admin
--os-password {{ keystone_admin_password }}
--os-user-domain-name default
--os-region-name {{ openstack_region_name }}
aggregate create {{ blazar_aggregate_pool_name }}
register: blazar_host_aggregate
changed_when: blazar_host_aggregate is success