limestone
/
ci-cloud-config
Code Issues Proposed changes

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:
Logan V 2019-03-17 20:25:07 -05:00
parent 8ace4d260e
commit e8889868e9
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
openstack_deploy/user_variables.yml
View File

@ -14,6 +14,13 @@ lxc_container_ssh_key: "{{ lookup('file', '/etc/openstack_deploy/ssh/id_rsa.pub'
# Configure SSH keys on hosts
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
# With the base services deployed, OSA exceeds this threshold resulting in connection
# contention in the database cluster