opendev/system-config
Code Issues Proposed changes
99342db824
system-config/playbooks/zuul/templates/group_vars/control-plane-clouds.yaml.j2

59 lines
2.3 KiB
Plaintext
Raw Normal View History

Add control plane clouds to nodepool builder clouds.yaml In order to have nodepool build images and upload them to control plane clouds, add them to the clouds.yaml on the nodepool-builder hosts. Keep them out of the launcher configs by splitting the config templates. So that we can keep our copies of things to a minimum, create a group called "control-plane-clouds" and put bridge and nb0* in it. There are clouds mentions in here that we no longer use, a followup patch will clean those up. NOTE: Requires shifting the clouds config dict from host_vars/bridge.openstack.org.yaml to group_vars/control-plane-clouds.yaml in the secrets on bridge. Needed-By: https://review.opendev.org/640044 Change-Id: Id1161bca8f23129202599dba299c288a6aa29212
2019-02-28 12:10:49 +00:00
# Necessary for fake clouds.yaml to be written
clouds:
openstackci_ovh_username: user
openstackci_ovh_password: password
openstackci_ovh_project_name: project
openstackci_rax_username: user
Switch rackspace clouds to api key auth After this merges, the temporary credential set opendevci_rax_* and opendevzuul_rax_* can be removed from hostvars. Depends-On: https://review.opendev.org/911163 Change-Id: I2e9067aa2f11100d311c86beb4df5bf15c72db69
2024-03-07 09:05:12 -08:00
openstackci_rax_key: apikey
Add control plane clouds to nodepool builder clouds.yaml In order to have nodepool build images and upload them to control plane clouds, add them to the clouds.yaml on the nodepool-builder hosts. Keep them out of the launcher configs by splitting the config templates. So that we can keep our copies of things to a minimum, create a group called "control-plane-clouds" and put bridge and nb0* in it. There are clouds mentions in here that we no longer use, a followup patch will clean those up. NOTE: Requires shifting the clouds config dict from host_vars/bridge.openstack.org.yaml to group_vars/control-plane-clouds.yaml in the secrets on bridge. Needed-By: https://review.opendev.org/640044 Change-Id: Id1161bca8f23129202599dba299c288a6aa29212
2019-02-28 12:10:49 +00:00
openstackci_rax_project_id: project
openstackjenkins_rax_username: user
Switch rackspace clouds to api key auth After this merges, the temporary credential set opendevci_rax_* and opendevzuul_rax_* can be removed from hostvars. Depends-On: https://review.opendev.org/911163 Change-Id: I2e9067aa2f11100d311c86beb4df5bf15c72db69
2024-03-07 09:05:12 -08:00
openstackjenkins_rax_key: apikey
Add control plane clouds to nodepool builder clouds.yaml In order to have nodepool build images and upload them to control plane clouds, add them to the clouds.yaml on the nodepool-builder hosts. Keep them out of the launcher configs by splitting the config templates. So that we can keep our copies of things to a minimum, create a group called "control-plane-clouds" and put bridge and nb0* in it. There are clouds mentions in here that we no longer use, a followup patch will clean those up. NOTE: Requires shifting the clouds config dict from host_vars/bridge.openstack.org.yaml to group_vars/control-plane-clouds.yaml in the secrets on bridge. Needed-By: https://review.opendev.org/640044 Change-Id: Id1161bca8f23129202599dba299c288a6aa29212
2019-02-28 12:10:49 +00:00
openstackjenkins_rax_project_id: project
openstackjenkins_ovh_username: user
openstackjenkins_ovh_password: password
openstackjenkins_ovh_project_name: project
openstackjenkins_vexxhost_username: user
openstackjenkins_vexxhost_password: password
openstackjenkins_vexxhost_project_name: project
openstackci_vexxhost_username: user
openstackci_vexxhost_password: password
openstackci_vexxhost_project_name: project
Move clouds definitions into control-planes-clouds group 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
2022-10-13 12:59:00 +11:00
openstackci_citycloud_username: user
openstackci_citycloud_password: password
openstackzuul_citycloud_username: user
openstackzuul_citycloud_password: password
Add control plane clouds to nodepool builder clouds.yaml In order to have nodepool build images and upload them to control plane clouds, add them to the clouds.yaml on the nodepool-builder hosts. Keep them out of the launcher configs by splitting the config templates. So that we can keep our copies of things to a minimum, create a group called "control-plane-clouds" and put bridge and nb0* in it. There are clouds mentions in here that we no longer use, a followup patch will clean those up. NOTE: Requires shifting the clouds config dict from host_vars/bridge.openstack.org.yaml to group_vars/control-plane-clouds.yaml in the secrets on bridge. Needed-By: https://review.opendev.org/640044 Change-Id: Id1161bca8f23129202599dba299c288a6aa29212
2019-02-28 12:10:49 +00:00
openstackci_linaro_london_username: user
openstackci_linaro_london_password: password
openstackci_linaro_london_project_name: project
openstackzuul_linaro_london_username: user
openstackzuul_linaro_london_password: password
openstackzuul_linaro_london_project_name: project
Add Linaro US cloud Add the credentials for the newly provisioned us.linaro.cloud cloud Change-Id: I0b81a8eeabec4e0b00258dc4e499c1d449b21681
2020-01-21 13:57:47 +11:00
openstackci_linaro_us_username: user
openstackci_linaro_us_password: password
openstackci_linaro_us_project_name: project
openstackzuul_linaro_us_username: user
openstackzuul_linaro_us_password: password
openstackzuul_linaro_us_project_name: project
Add airship CI cloud This is a new cloud provided via citycloud that will add resources capable of running Airship jobs. The goal is to use this as a stepping stone to having Airship jobs run on our generic CI resources. This cloud will provide both generic and larger resources to support this. Change-Id: I63fd9023bc11f1382424c8906dc306cee5b3f58d
2020-01-30 15:50:58 -08:00
opendevci_airship_username: user
opendevci_airship_password: password
opendevzuul_airship_username: user
opendevzuul_airship_password: password
Linaro: initial cloud config This is just enough to get the cloud-launcher working on the new Linaro cloud. It's a bit of a manual setup, and much newer hardware, so trying to do things in small steps. Change-Id: Ibd451e80bbc6ba6526ba9470ac48b99a981c1a8d
2022-12-21 10:17:55 +11:00
opendevci_linaro_username: user
opendevci_linaro_password: password
opendevci_linaro_project_name: project
opendevzuul_linaro_username: user
opendevzuul_linaro_password: password
opendevzuul_linaro_project_name: project
Move clouds definitions into control-planes-clouds group 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
2022-10-13 12:59:00 +11:00
opendevci_osuosl_username: user
opendevci_osuosl_password: password
opendevci_osuosl_project_id: project
opendevzuul_osuosl_username: user
opendevzuul_osuosl_password: password
opendevzuul_osuosl_project_id: project
opendevci_inmotion_username: user
opendevci_inmotion_password: password
opendevci_inmotion_project_id: project
opendevzuul_inmotion_username: user
opendevzuul_inmotion_password: password
opendevzuul_inmotion_project_id: project
Copy Permalink