Use nova_api DB for [placement_database] -> connection

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.

Closes-Bug: #1797119

Change-Id: I6eb8cb62d337fa4f6e6542391de251519e246923

puppet/services/nova-base.yaml

@@ -295,10 +295,10 @@ outputs:
           nova::placement_database_connection:
             make_url:
               scheme: {get_param: [EndpointMap, MysqlInternal, protocol]}
-              username: nova_placement
+              username: nova_api
               password: {get_param: NovaPassword}
               host: {get_param: [EndpointMap, MysqlInternal, host]}
-              path: /nova_placement
+              path: /nova_api
               query:
                 read_default_file: /etc/my.cnf.d/tripleo.cnf
                 read_default_group: tripleo

releasenotes/notes/nova_use_nova_api_db_for_placement-eea44dd48c768f04.yaml

@@ -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.