4ad010a5a6
Based on the discussions from recent Kolla meetings [1][2][3], we established that, to avoid the DockerHub pull limit issues in our CI, we will try using quay.io. The images have already been published via Kolla CI for master/Wallaby [4] and Victoria [5]. This change applies only to CI. The user-facing move is yet to be discussed. [1] http://eavesdrop.openstack.org/meetings/kolla/2021/kolla.2021-03-17-15.00.log.html#l-102 [2] http://eavesdrop.openstack.org/meetings/kolla/2021/kolla.2021-03-24-15.00.log.html#l-137 [3] http://eavesdrop.openstack.org/meetings/kolla/2021/kolla.2021-03-31-15.01.log.html#l-50 [4] https://review.opendev.org/c/openstack/kolla/+/781130 [5] https://review.opendev.org/c/openstack/kolla/+/781899 See related Kolla Ansible change I22e11a994801447526ac26fc2815a1679876225e Change-Id: Id6690dc9a486af0ed7d42555d84cf77d6de0b6af
22 lines
716 B
Django/Jinja
22 lines
716 B
Django/Jinja
---
|
|
# Use HTTPS opendev quay.io registry proxy.
|
|
docker_registry_insecure: no
|
|
|
|
# Most development environments will use nested virtualisation, and we can't
|
|
# guarantee that nested KVM support is available. Use QEMU as a lowest common
|
|
# denominator.
|
|
nova_compute_virt_type: qemu
|
|
|
|
# Reduce the control plane's memory footprint by limiting the number of worker
|
|
# processes to one per-service.
|
|
openstack_service_workers: "1"
|
|
openstack_service_rpc_workers: "1"
|
|
|
|
{% if tls_enabled %}
|
|
# TLS
|
|
kolla_copy_ca_into_containers: "yes"
|
|
kolla_enable_tls_backend: "yes"
|
|
openstack_cacert: "/etc/pki/tls/certs/ca-bundle.crt"
|
|
kolla_admin_openrc_cacert: "{% raw %}{{ '{{' }} kolla_certificates_dir }}{% endraw %}/ca/root.crt"
|
|
{% endif %}
|