Browse Source

Use utility container for service bootstrapping

Configure OSA to use the utility container for bootstrapping OpenStack
services. In Rocky, OSA began using the deployment host by default
instead of the utility container. This breaks our deployment model
because the deployment host does not have access to the internal
OpenStack API endpoints.

Revert back to the previous behavior of using the utility container
for bootstrapping services.

Change-Id: Iebfb6583c1b02bdc7422fb7c3fbdaf3a851aec43
Logan V 1 month ago
parent
commit
e8889868e9
1 changed files with 7 additions and 0 deletions
  1. 7
    0
      openstack_deploy/user_variables.yml

+ 7
- 0
openstack_deploy/user_variables.yml View File

@@ -14,6 +14,13 @@ lxc_container_ssh_key: "{{ lookup('file', '/etc/openstack_deploy/ssh/id_rsa.pub'
14 14
 # Configure SSH keys on hosts
15 15
 ssh_key_url: https://git.openstack.org/cgit/openstack/limestone-ci-cloud/plain/ssh/authorized_keys
16 16
 
17
+# Use the utility container for bootstrapping openstack services
18
+openstack_service_setup_host: "{{ groups['utility_all'][0] }}"
19
+openstack_service_setup_host_python_interpreter: "/openstack/venvs/utility-{{ openstack_release }}/bin/python"
20
+# NOTE(logan): It should be possible to remove shade once ansible 2.6 is used in Stein
21
+utility_pip_packages:
22
+  - shade
23
+
17 24
 # Galera max_connections default is 100*VCPU. On our controllers, this is 800 connections
18 25
 # With the base services deployed, OSA exceeds this threshold resulting in connection
19 26
 # contention in the database cluster

Loading…
Cancel
Save