
As a short history diversion, at one point we were trying building diskimage-builder based images for upload to our control-plane (instead of using upstream generic cloud images). This didn't really work because the long-lived production servers led to leaking images and nodepool wasn't really meant to deal with this lifecycle. Before this the only thing that needed credentials for the control-plane clouds was bridge. Id1161bca8f23129202599dba299c288a6aa29212 reworked things to have a control-plane-clouds group which would have access to the credential variables. So at this point we added zuul/templates/group_vars/control-plane-clouds.yaml.j2 with stub variables for testing. However, we also have the same cloud: variable with stub variables in zuul/templates/host_vars/bridge.openstack.org.yaml.j2. This is overriding the version from control-plane-clouds because it is more specific (host variable). Over time this has skewed from the control-plane-clouds definition, but I think we have not noticed because we are not updating the control-plane clouds on the non-bridge (nodepool) nodes any more. This is a long way of saying remove the bridge-specific definitions, and just keep the stub variables in the control-plane-clouds group. Change-Id: I6c1bfe7fdca27d6e34d9691099b0e1c6d30bb967
10 lines
209 B
Django/Jinja
10 lines
209 B
Django/Jinja
gitea_kube_key: Z2l0ZWFfazhzX2tleQ==
|
|
|
|
ansible_cron_disable_job: true
|
|
cloud_launcher_disable_job: true
|
|
extra_users: []
|
|
|
|
rackspace_dns_username: user
|
|
rackspace_dns_project_id: 1234
|
|
rackspace_dns_api_key: apikey
|