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
This commit is contained in:
parent
8ace4d260e
commit
e8889868e9
|
@ -14,6 +14,13 @@ lxc_container_ssh_key: "{{ lookup('file', '/etc/openstack_deploy/ssh/id_rsa.pub'
|
||||||
# Configure SSH keys on hosts
|
# Configure SSH keys on hosts
|
||||||
ssh_key_url: https://git.openstack.org/cgit/openstack/limestone-ci-cloud/plain/ssh/authorized_keys
|
ssh_key_url: https://git.openstack.org/cgit/openstack/limestone-ci-cloud/plain/ssh/authorized_keys
|
||||||
|
|
||||||
|
# Use the utility container for bootstrapping openstack services
|
||||||
|
openstack_service_setup_host: "{{ groups['utility_all'][0] }}"
|
||||||
|
openstack_service_setup_host_python_interpreter: "/openstack/venvs/utility-{{ openstack_release }}/bin/python"
|
||||||
|
# NOTE(logan): It should be possible to remove shade once ansible 2.6 is used in Stein
|
||||||
|
utility_pip_packages:
|
||||||
|
- shade
|
||||||
|
|
||||||
# Galera max_connections default is 100*VCPU. On our controllers, this is 800 connections
|
# Galera max_connections default is 100*VCPU. On our controllers, this is 800 connections
|
||||||
# With the base services deployed, OSA exceeds this threshold resulting in connection
|
# With the base services deployed, OSA exceeds this threshold resulting in connection
|
||||||
# contention in the database cluster
|
# contention in the database cluster
|
||||||
|
|
Loading…
Reference in New Issue