Merge "Use nova_api DB for [placement_database] -> connection"
This commit is contained in:
commit
2027b1af8c
|
@ -293,10 +293,10 @@ outputs:
|
||||||
nova::placement_database_connection:
|
nova::placement_database_connection:
|
||||||
make_url:
|
make_url:
|
||||||
scheme: {get_param: [EndpointMap, MysqlInternal, protocol]}
|
scheme: {get_param: [EndpointMap, MysqlInternal, protocol]}
|
||||||
username: nova_placement
|
username: nova_api
|
||||||
password: {get_param: NovaPassword}
|
password: {get_param: NovaPassword}
|
||||||
host: {get_param: [EndpointMap, MysqlInternal, host]}
|
host: {get_param: [EndpointMap, MysqlInternal, host]}
|
||||||
path: /nova_placement
|
path: /nova_api
|
||||||
query:
|
query:
|
||||||
read_default_file: /etc/my.cnf.d/tripleo.cnf
|
read_default_file: /etc/my.cnf.d/tripleo.cnf
|
||||||
read_default_group: tripleo
|
read_default_group: tripleo
|
||||||
|
|
|
@ -0,0 +1,12 @@
|
||||||
|
---
|
||||||
|
fixes:
|
||||||
|
- |
|
||||||
|
With OOO we configure a separate DB for placement for the undercloud and
|
||||||
|
overcloud since the beginning.
|
||||||
|
But the placement_database config options were reverted with
|
||||||
|
https://review.openstack.org/#/c/442762/1 , which means so far even if
|
||||||
|
the config option was set, it was not used. With rocky the options were
|
||||||
|
introduced again which is not a problem on a fresh installed env, but on
|
||||||
|
upgrades from queens to rocky.
|
||||||
|
We should use the same DB for both fresh deployments on and upgrades to
|
||||||
|
rocky before we switch to the new DB as part of the extraction of placement.
|
Loading…
Reference in New Issue