opendev/system-config
Code Issues Proposed changes
d292d853e9
system-config/zuul.d/infra-prod.yaml

624 lines
19 KiB
YAML
Raw Normal View History

Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
# Make sure only one run of a system-config playbook happens at a time
- semaphore:
name: infra-prod-playbook
max: 1
- job:
name: infra-prod-playbook
Use infra-prod-base in infra-prod jobs This uses a new base job which handles pushing the git repos on to bridge since that must now happen in a trusted playbook. Depends-On: https://review.opendev.org/742934 Change-Id: Ie6d0668f83af801c0c0e920b676f2f49e19c59f6
2020-07-24 09:03:36 -07:00
parent: opendev-infra-prod-base
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
description: |
Run specified playbook against productions hosts.
This is a parent job designed to be inherited to enabled
CD deployment of our infrastructure. Set playbook_name to
specify the playbook relative to
/home/zuul/src/opendev.org/opendev/system-config/playbooks
on bridge.openstack.org.
abstract: true
semaphore: infra-prod-playbook
run: playbooks/zuul/run-production-playbook.yaml
required-projects:
- opendev/system-config
vars:
infra_prod_ansible_forks: 5
infra_prod_playbook_collect_log: false
nodeset:
nodes: []
- job:
name: infra-prod-install-ansible
parent: infra-prod-playbook
description: Install ansible on bridge.
vars:
playbook_name: install-ansible.yaml
files:
- inventory/
- roles/
- install_modules.sh
- modules.env
- playbooks/install-ansible.yaml
- playbooks/roles/pip3/
- playbooks/roles/install-ansible/
- playbooks/roles/logrotate/
- playbooks/roles/root-keys/
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- inventory/service/host_vars/bridge.openstack.org.yaml
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/zuul/run-production-playbook.yaml
- job:
name: infra-prod-base
parent: infra-prod-playbook
description: Run the base playbook everywhere.
dependencies:
- name: infra-prod-install-ansible
soft: true
vars:
playbook_name: base.yaml
infra_prod_ansible_forks: 50
files:
- inventory/
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- inventory/service/host_vars/
- inventory/service/group_vars/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/base.yaml
Move base roles into a base subdir If we move these into a subdir, it cleans up the number of things we nave to files match on. Stop running disable-puppet-agent in base. We run it in run-puppet which should be fine. Change-Id: Ia16adb96b11d25a097490882c4c59a50a0b7b23d
2020-05-26 14:24:20 -05:00
- playbooks/roles/base/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- job:
Rename service-letsencrypt to just letsencrypt This isn't a service, it's a meta thing that we run for different hosts at different times. Change-Id: Ib65665c98afb3ddb94b15346931be88a4b1757d8
2020-05-28 16:43:14 -05:00
name: infra-prod-letsencrypt
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
parent: infra-prod-playbook
Rename service-letsencrypt to just letsencrypt This isn't a service, it's a meta thing that we run for different hosts at different times. Change-Id: Ib65665c98afb3ddb94b15346931be88a4b1757d8
2020-05-28 16:43:14 -05:00
description: Run letsencrypt.yaml playbook.
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
vars:
Rename service-letsencrypt to just letsencrypt This isn't a service, it's a meta thing that we run for different hosts at different times. Change-Id: Ib65665c98afb3ddb94b15346931be88a4b1757d8
2020-05-28 16:43:14 -05:00
playbook_name: letsencrypt.yaml
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
dependencies:
- name: infra-prod-install-ansible
soft: true
files:
- inventory/
Rename service-letsencrypt to just letsencrypt This isn't a service, it's a meta thing that we run for different hosts at different times. Change-Id: Ib65665c98afb3ddb94b15346931be88a4b1757d8
2020-05-28 16:43:14 -05:00
- playbooks/letsencrypt.yaml
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
# Any touching of host_vars or group_vars can substantively
# change the certs we're doing, so be greedy here.
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- inventory/service/host_vars/
- inventory/service/group_vars/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/letsencrypt
- playbooks/roles/logrotate/
- job:
name: infra-prod-manage-projects
parent: infra-prod-playbook
description: |
Create and update projects in gerrit and gitea.
allowed-projects:
- opendev/system-config
- openstack/project-config
required-projects:
- opendev/system-config
- openstack/project-config
vars:
playbook_name: manage-projects.yaml
infra_prod_ansible_forks: 10
infra_prod_playbook_collect_log: true
- job:
name: infra-prod-service-base
parent: infra-prod-playbook
description: Base job for most service playbooks.
abstract: true
dependencies:
- name: infra-prod-install-ansible
soft: true
Rename service-letsencrypt to just letsencrypt This isn't a service, it's a meta thing that we run for different hosts at different times. Change-Id: Ib65665c98afb3ddb94b15346931be88a4b1757d8
2020-05-28 16:43:14 -05:00
- name: infra-prod-letsencrypt
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
soft: true
- job:
name: infra-prod-service-bridge
parent: infra-prod-service-base
description: Run service-bridge.yaml playbook.
vars:
playbook_name: service-bridge.yaml
files:
- inventory/
- playbooks/service-bridge.yaml
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- inventory/service/host_vars/bridge.openstack.org.yaml
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/logrotate/
- playbooks/roles/edit-secrets-script/
- playbooks/roles/install-kubectl/
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- playbooks/roles/iptables/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/configure-kubectl/
- playbooks/roles/configure-openstacksdk/
- playbooks/templates/clouds/bridge_all_clouds.yaml.j2
- job:
name: infra-prod-service-gitea-lb
parent: infra-prod-service-base
description: Run service-gitea-lb.yaml playbook.
vars:
playbook_name: service-gitea-lb.yaml
files:
- inventory/
- playbooks/service-gitea-lb.yaml
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- inventory/service/group_vars/gitea-lb.yaml
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/pip3/
Run iptables in service playbooks instead of base It's the only part of base that's important to run when we run a service. Run it in the service playbooks and get rid of the dependency on infra-prod-base. Continue running it in base so that new nodes are brought up with iptables in place. Bump the timeout for the mirror job, because the iptables addition seems to have just bumped it over the edge. Change-Id: I4608216f7a59cfa96d3bdb191edd9bc7bb9cca39
2020-05-26 17:41:54 -05:00
- playbooks/roles/iptables/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/install-docker/
- playbooks/roles/haproxy/
- job:
name: infra-prod-service-nameserver
parent: infra-prod-service-base
description: Run service-nameserver.yaml playbook.
vars:
playbook_name: service-nameserver.yaml
files:
- inventory/
- playbooks/service-nameserver.yaml
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- inventory/service/host_vars/adns1.opendev.org.yaml
- inventory/service/host_vars/ns1.opendev.org.yaml
- inventory/service/host_vars/ns2.opendev.org.yaml
- inventory/service/group_vars/adns.yaml
- inventory/service/group_vars/ns.yaml
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/master-nameserver/
- playbooks/roles/nameserver/
Run iptables in service playbooks instead of base It's the only part of base that's important to run when we run a service. Run it in the service playbooks and get rid of the dependency on infra-prod-base. Continue running it in base so that new nodes are brought up with iptables in place. Bump the timeout for the mirror job, because the iptables addition seems to have just bumped it over the edge. Change-Id: I4608216f7a59cfa96d3bdb191edd9bc7bb9cca39
2020-05-26 17:41:54 -05:00
- playbooks/roles/iptables/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- job:
name: infra-prod-service-nodepool
parent: infra-prod-service-base
description: Run service-nodepool.yaml playbook.
vars:
playbook_name: service-nodepool.yaml
required-projects:
- opendev/system-config
- openstack/project-config
files:
- inventory/
- playbooks/service-nodepool.yaml
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- inventory/service/host_vars/nb
- inventory/service/host_vars/nl
- inventory/service/group_vars/nodepool
- inventory/service/group_vars/puppet
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/install-ansible-roles/
- playbooks/roles/run-puppet/
- playbooks/roles/configure-kubectl/
- playbooks/roles/configure-openstacksdk/
- playbooks/roles/install-docker/
Run iptables in service playbooks instead of base It's the only part of base that's important to run when we run a service. Run it in the service playbooks and get rid of the dependency on infra-prod-base. Continue running it in base so that new nodes are brought up with iptables in place. Bump the timeout for the mirror job, because the iptables addition seems to have just bumped it over the edge. Change-Id: I4608216f7a59cfa96d3bdb191edd9bc7bb9cca39
2020-05-26 17:41:54 -05:00
- playbooks/roles/iptables/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/nodepool
- playbooks/templates/clouds/nodepool_
- job:
name: infra-prod-service-etherpad
parent: infra-prod-service-base
description: Run service-etherpad.yaml playbook.
vars:
playbook_name: service-etherpad.yaml
files:
- inventory/
- playbooks/service-etherpad.yaml
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- inventory/service/host_vars/etherpad01.opendev.org.yaml
- inventory/service/group_vars/etherpad
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/install-docker/
- playbooks/roles/pip3/
- playbooks/roles/etherpad
- playbooks/roles/logrotate
Run iptables in service playbooks instead of base It's the only part of base that's important to run when we run a service. Run it in the service playbooks and get rid of the dependency on infra-prod-base. Continue running it in base so that new nodes are brought up with iptables in place. Bump the timeout for the mirror job, because the iptables addition seems to have just bumped it over the edge. Change-Id: I4608216f7a59cfa96d3bdb191edd9bc7bb9cca39
2020-05-26 17:41:54 -05:00
- playbooks/roles/iptables/
Run our etherpad prod deploy job when docker updates We want to pick up changes to our docker setup in production. Without this we don't get the infra-prod-service-etherpad job running when we update the etherpad docker image. Change-Id: I25aee457b7c0547fc11439301054bb5aef799476
2020-07-17 13:20:48 -07:00
- docker/etherpad/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- job:
name: infra-prod-service-meetpad
parent: infra-prod-service-base
description: Run service-meetpad.yaml playbook.
dependencies:
- name: infra-prod-install-ansible
soft: true
Rename service-letsencrypt to just letsencrypt This isn't a service, it's a meta thing that we run for different hosts at different times. Change-Id: Ib65665c98afb3ddb94b15346931be88a4b1757d8
2020-05-28 16:43:14 -05:00
- name: infra-prod-letsencrypt
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
soft: true
- name: system-config-promote-image-jitsi-meet
soft: true
vars:
playbook_name: service-meetpad.yaml
files:
- inventory/
- playbooks/service-meetpad.yaml
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- inventory/service/host_vars/meetpad01.opendev.org.yaml
- inventory/service/group_vars/meetpad.yaml
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/pip3/
- playbooks/roles/install-docker/
Run iptables in service playbooks instead of base It's the only part of base that's important to run when we run a service. Run it in the service playbooks and get rid of the dependency on infra-prod-base. Continue running it in base so that new nodes are brought up with iptables in place. Bump the timeout for the mirror job, because the iptables addition seems to have just bumped it over the edge. Change-Id: I4608216f7a59cfa96d3bdb191edd9bc7bb9cca39
2020-05-26 17:41:54 -05:00
- playbooks/roles/iptables/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/jitsi-meet/
- job:
name: infra-prod-service-mirror-update
parent: infra-prod-service-base
description: Run service-mirror-update.yaml playbook.
vars:
playbook_name: service-mirror-update.yaml
files:
- inventory/
- playbooks/service-mirror-update.yaml
- playbooks/roles/kerberos-client/
- playbooks/roles/openafs-client/
- playbooks/roles/mirror-update/
reprepro: run deploy job on role changes This was missed so the deploy job doesn't run automatically on changes to the reprepro role. Change-Id: I8e40926bd5bbb2836c63704ba02a43e45c12b4c4
2020-10-27 16:29:48 +11:00
- playbooks/roles/reprepro/
Run iptables in service playbooks instead of base It's the only part of base that's important to run when we run a service. Run it in the service playbooks and get rid of the dependency on infra-prod-base. Continue running it in base so that new nodes are brought up with iptables in place. Bump the timeout for the mirror job, because the iptables addition seems to have just bumped it over the edge. Change-Id: I4608216f7a59cfa96d3bdb191edd9bc7bb9cca39
2020-05-26 17:41:54 -05:00
- playbooks/roles/iptables/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/logrotate/
- job:
name: infra-prod-service-mirror
parent: infra-prod-service-base
description: Run service-mirror.yaml playbook.
vars:
playbook_name: service-mirror.yaml
files:
- inventory/
- playbooks/service-mirror.yaml
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- inventory/service/group_vars/mirror.yaml
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/kerberos-client/
- playbooks/roles/openafs-client/
- playbooks/roles/mirror/
- playbooks/roles/afs-release/
- playbooks/roles/afsmon/
Run iptables in service playbooks instead of base It's the only part of base that's important to run when we run a service. Run it in the service playbooks and get rid of the dependency on infra-prod-base. Continue running it in base so that new nodes are brought up with iptables in place. Bump the timeout for the mirror job, because the iptables addition seems to have just bumped it over the edge. Change-Id: I4608216f7a59cfa96d3bdb191edd9bc7bb9cca39
2020-05-26 17:41:54 -05:00
- playbooks/roles/iptables/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/logrotate/
- job:
name: infra-prod-service-static
parent: infra-prod-service-base
description: Run service-static.yaml playbook.
vars:
playbook_name: service-static.yaml
files:
- inventory/
- playbooks/service-static.yaml
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- inventory/service/host_vars/static01.opendev.org.yaml
- inventory/service/group_vars/static.yaml
Run iptables in service playbooks instead of base It's the only part of base that's important to run when we run a service. Run it in the service playbooks and get rid of the dependency on infra-prod-base. Continue running it in base so that new nodes are brought up with iptables in place. Bump the timeout for the mirror job, because the iptables addition seems to have just bumped it over the edge. Change-Id: I4608216f7a59cfa96d3bdb191edd9bc7bb9cca39
2020-05-26 17:41:54 -05:00
- playbooks/roles/iptables/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/kerberos-client/
- playbooks/roles/openafs-client/
- playbooks/roles/static/
- playbooks/roles/zuul-user/
- job:
name: infra-prod-service-backup
parent: infra-prod-service-base
description: Run service-backup.yaml playbook.
vars:
playbook_name: service-backup.yaml
files:
- inventory/
- playbooks/service-backup.yaml
- playbooks/roles/backup/
- playbooks/roles/backup-server/
Run iptables in service playbooks instead of base It's the only part of base that's important to run when we run a service. Run it in the service playbooks and get rid of the dependency on infra-prod-base. Continue running it in base so that new nodes are brought up with iptables in place. Bump the timeout for the mirror job, because the iptables addition seems to have just bumped it over the edge. Change-Id: I4608216f7a59cfa96d3bdb191edd9bc7bb9cca39
2020-05-26 17:41:54 -05:00
- playbooks/roles/iptables/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
Add borg-backup roles This adds roles to implement backup with borg [1]. Our current tool "bup" has no Python 3 support and is not packaged for Ubuntu Focal. This means it is effectively end-of-life. borg fits our model of servers backing themselves up to a central location, is well documented and seems well supported. It also has the clarkb seal of approval :) As mentioned, borg works in the same manner as bup by doing an efficient back up over ssh to a remote server. The core of these roles are the same as the bup based ones; in terms of creating a separate user for each host and deploying keys and ssh config. This chooses to install borg in a virtualenv on /opt. This was chosen for a number of reasons; firstly reading the history of borg there have been incompatible updates (although they provide a tool to update repository formats); it seems important that we both pin the version we are using and keep clients and server in sync. Since we have a hetrogenous distribution collection we don't want to rely on the packaged tools which may differ. I don't feel like this is a great application for a container; we actually don't want it that isolated from the base system because it's goal is to read and copy it offsite with as little chance of things going wrong as possible. Borg has a lot of support for encrypting the data at rest in various ways. However, that introduces the possibility we could lose both the key and the backup data. Really the only thing stopping this is key management, and if we want to go down this path we can do it as a follow-on. The remote end server is configured via ssh command rules to run in append-only mode. This means a misbehaving client can't delete its old backups. In theory we can prune backups on the server side -- something we could not do with bup. The documentation has been updated but is vague on this part; I think we should get some hosts in operation, see how the de-duplication is working out and then decide how we want to mange things long term. Testing is added; a focal and bionic host both run a full backup of themselves to the backup server. Pretty cool, the logs are in /var/log/borg-backup-<host>.log. No hosts are currently in the borg groups, so this can be applied without affecting production. I'd suggest the next steps are to bring up a borg-based backup server and put a few hosts into this. After running for a while, we can add all hosts, and then deprecate the current bup-based backup server in vexxhost and replace that with a borg-based one; giving us dual offsite backups. [1] https://borgbackup.readthedocs.io/en/stable/ Change-Id: I2a125f2fac11d8e3a3279eb7fa7adb33a3acaa4e
2020-07-16 13:43:18 +10:00
- job:
name: infra-prod-service-borg-backup
parent: infra-prod-service-base
description: Run service-borg-backup.yaml playbook.
vars:
playbook_name: service-borg-backup.yaml
files:
- inventory/
- playbooks/service-borg-backup.yaml
borg : match install-borg role to run deploy job This was forgotten in the original addition. Change-Id: I0725b99e938b993e68106f6ba1b2704e9413e902
2020-10-12 13:06:10 +11:00
- playbooks/roles/install-borg/
Add borg-backup roles This adds roles to implement backup with borg [1]. Our current tool "bup" has no Python 3 support and is not packaged for Ubuntu Focal. This means it is effectively end-of-life. borg fits our model of servers backing themselves up to a central location, is well documented and seems well supported. It also has the clarkb seal of approval :) As mentioned, borg works in the same manner as bup by doing an efficient back up over ssh to a remote server. The core of these roles are the same as the bup based ones; in terms of creating a separate user for each host and deploying keys and ssh config. This chooses to install borg in a virtualenv on /opt. This was chosen for a number of reasons; firstly reading the history of borg there have been incompatible updates (although they provide a tool to update repository formats); it seems important that we both pin the version we are using and keep clients and server in sync. Since we have a hetrogenous distribution collection we don't want to rely on the packaged tools which may differ. I don't feel like this is a great application for a container; we actually don't want it that isolated from the base system because it's goal is to read and copy it offsite with as little chance of things going wrong as possible. Borg has a lot of support for encrypting the data at rest in various ways. However, that introduces the possibility we could lose both the key and the backup data. Really the only thing stopping this is key management, and if we want to go down this path we can do it as a follow-on. The remote end server is configured via ssh command rules to run in append-only mode. This means a misbehaving client can't delete its old backups. In theory we can prune backups on the server side -- something we could not do with bup. The documentation has been updated but is vague on this part; I think we should get some hosts in operation, see how the de-duplication is working out and then decide how we want to mange things long term. Testing is added; a focal and bionic host both run a full backup of themselves to the backup server. Pretty cool, the logs are in /var/log/borg-backup-<host>.log. No hosts are currently in the borg groups, so this can be applied without affecting production. I'd suggest the next steps are to bring up a borg-based backup server and put a few hosts into this. After running for a while, we can add all hosts, and then deprecate the current bup-based backup server in vexxhost and replace that with a borg-based one; giving us dual offsite backups. [1] https://borgbackup.readthedocs.io/en/stable/ Change-Id: I2a125f2fac11d8e3a3279eb7fa7adb33a3acaa4e
2020-07-16 13:43:18 +10:00
- playbooks/roles/borg-backup/
- playbooks/roles/borg-backup-server/
- playbooks/roles/iptables/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- job:
name: infra-prod-service-registry
parent: infra-prod-service-base
description: Run service-registry.yaml playbook.
vars:
playbook_name: service-registry.yaml
files:
- inventory/
- playbooks/service-registry.yaml
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- inventory/service/group_vars/registry.yaml
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/pip3/
- playbooks/roles/install-docker/
Run iptables in service playbooks instead of base It's the only part of base that's important to run when we run a service. Run it in the service playbooks and get rid of the dependency on infra-prod-base. Continue running it in base so that new nodes are brought up with iptables in place. Bump the timeout for the mirror job, because the iptables addition seems to have just bumped it over the edge. Change-Id: I4608216f7a59cfa96d3bdb191edd9bc7bb9cca39
2020-05-26 17:41:54 -05:00
- playbooks/roles/iptables/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/registry/
- job:
name: infra-prod-service-zuul-preview
parent: infra-prod-service-base
description: Run service-zuul-preview.yaml playbook.
vars:
playbook_name: service-zuul-preview.yaml
files:
- inventory/
- playbooks/service-zuul-preview.yaml
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- inventory/service/group_vars/zuul-preview.yaml
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/pip3/
- playbooks/roles/install-docker/
Run iptables in service playbooks instead of base It's the only part of base that's important to run when we run a service. Run it in the service playbooks and get rid of the dependency on infra-prod-base. Continue running it in base so that new nodes are brought up with iptables in place. Bump the timeout for the mirror job, because the iptables addition seems to have just bumped it over the edge. Change-Id: I4608216f7a59cfa96d3bdb191edd9bc7bb9cca39
2020-05-26 17:41:54 -05:00
- playbooks/roles/iptables/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/zuul-preview/
- job:
name: infra-prod-service-zookeeper
parent: infra-prod-service-base
description: Run service-zookeeper.yaml playbook.
vars:
playbook_name: service-zookeeper.yaml
files:
- inventory/.*
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- inventory/service/group_vars/zookeeper.yaml
- ^inventory/service/host_vars/zk\d+\..*
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/pip3/
- playbooks/roles/install-docker/
Run iptables in service playbooks instead of base It's the only part of base that's important to run when we run a service. Run it in the service playbooks and get rid of the dependency on infra-prod-base. Continue running it in base so that new nodes are brought up with iptables in place. Bump the timeout for the mirror job, because the iptables addition seems to have just bumped it over the edge. Change-Id: I4608216f7a59cfa96d3bdb191edd9bc7bb9cca39
2020-05-26 17:41:54 -05:00
- playbooks/roles/iptables/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/zookeeper/
- job:
name: infra-prod-service-zuul
parent: infra-prod-service-base
description: |
Run service-zuul.yaml playbook.
This configures the main Zuul cluster. It will perform a
smart-reconfigure of the scheduler if the tenant configuration
is changed.
vars:
playbook_name: service-zuul.yaml
dependencies:
- name: infra-prod-install-ansible
soft: true
Rename service-letsencrypt to just letsencrypt This isn't a service, it's a meta thing that we run for different hosts at different times. Change-Id: Ib65665c98afb3ddb94b15346931be88a4b1757d8
2020-05-28 16:43:14 -05:00
- name: infra-prod-letsencrypt
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
soft: true
- name: infra-prod-manage-projects
soft: true
files:
- inventory/.*
- playbooks/install-ansible.yaml
- playbooks/service-zuul.yaml
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- inventory/service/group_vars/zuul
- inventory/service/group_vars/zookeeper.yaml
- inventory/service/host_vars/zk\d+
- inventory/service/host_vars/zuul01.openstack.org
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/install-docker/
Run iptables in service playbooks instead of base It's the only part of base that's important to run when we run a service. Run it in the service playbooks and get rid of the dependency on infra-prod-base. Continue running it in base so that new nodes are brought up with iptables in place. Bump the timeout for the mirror job, because the iptables addition seems to have just bumped it over the edge. Change-Id: I4608216f7a59cfa96d3bdb191edd9bc7bb9cca39
2020-05-26 17:41:54 -05:00
- playbooks/roles/iptables/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/zookeeper/
- playbooks/roles/zuul
- job:
name: infra-prod-service-review
parent: infra-prod-service-base
description: Run service-review.yaml playbook.
vars:
playbook_name: service-review.yaml
dependencies: &infra_prod_service_review_deps
- name: infra-prod-install-ansible
soft: true
Rename service-letsencrypt to just letsencrypt This isn't a service, it's a meta thing that we run for different hosts at different times. Change-Id: Ib65665c98afb3ddb94b15346931be88a4b1757d8
2020-05-28 16:43:14 -05:00
- name: infra-prod-letsencrypt
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
soft: true
Fix the infra-prod-service-review image dependency We were still soft depending on gerrit 2.13 image builds but those jobs don't exist anymore. Update this to 3.2 image builds which is what we are doing now. Change-Id: I0f5c02d69c199a605278318b93162437b7539547
2020-11-22 12:25:08 -08:00
- name: system-config-promote-image-gerrit-3.2
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
soft: true
files:
- inventory/
- playbooks/service-review.yaml
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- inventory/service/group_vars/gerrit.yaml
- inventory/service/host_vars/review01.openstack.org.yaml
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/pip3/
- playbooks/roles/install-docker/
Run iptables in service playbooks instead of base It's the only part of base that's important to run when we run a service. Run it in the service playbooks and get rid of the dependency on infra-prod-base. Continue running it in base so that new nodes are brought up with iptables in place. Bump the timeout for the mirror job, because the iptables addition seems to have just bumped it over the edge. Change-Id: I4608216f7a59cfa96d3bdb191edd9bc7bb9cca39
2020-05-26 17:41:54 -05:00
- playbooks/roles/iptables/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/gerrit/
- job:
name: infra-prod-service-review-dev
parent: infra-prod-service-base
description: Run service-review-dev.yaml playbook.
vars:
playbook_name: service-review-dev.yaml
dependencies: *infra_prod_service_review_deps
files:
- inventory/
- playbooks/service-review-dev.yaml
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- inventory/service/group_vars/gerrit.yaml
- inventory/service/host_vars/review-dev01.opendev.org.yaml
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/pip3/
- playbooks/roles/install-docker/
Run iptables in service playbooks instead of base It's the only part of base that's important to run when we run a service. Run it in the service playbooks and get rid of the dependency on infra-prod-base. Continue running it in base so that new nodes are brought up with iptables in place. Bump the timeout for the mirror job, because the iptables addition seems to have just bumped it over the edge. Change-Id: I4608216f7a59cfa96d3bdb191edd9bc7bb9cca39
2020-05-26 17:41:54 -05:00
- playbooks/roles/iptables/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/gerrit/
- job:
name: infra-prod-service-gitea
parent: infra-prod-service-base
description: Run service-gitea.yaml playbook.
vars:
playbook_name: service-gitea.yaml
dependencies:
- name: infra-prod-install-ansible
soft: true
Rename service-letsencrypt to just letsencrypt This isn't a service, it's a meta thing that we run for different hosts at different times. Change-Id: Ib65665c98afb3ddb94b15346931be88a4b1757d8
2020-05-28 16:43:14 -05:00
- name: infra-prod-letsencrypt
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
soft: true
- name: system-config-promote-image-gitea-init
soft: true
- name: system-config-promote-image-gitea
soft: true
files:
- inventory/
- playbooks/service-gitea.yaml
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- inventory/service/group_vars/gitea.yaml
- inventory/service/host_vars/gitea[0-9][0-9]
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/install-docker/
- playbooks/roles/pip3/
- playbooks/roles/gitea/
Run iptables in service playbooks instead of base It's the only part of base that's important to run when we run a service. Run it in the service playbooks and get rid of the dependency on infra-prod-base. Continue running it in base so that new nodes are brought up with iptables in place. Bump the timeout for the mirror job, because the iptables addition seems to have just bumped it over the edge. Change-Id: I4608216f7a59cfa96d3bdb191edd9bc7bb9cca39
2020-05-26 17:41:54 -05:00
- playbooks/roles/iptables/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/logrotate/
- docker/gitea/
- docker/gitea-init/
- docker/jinja-init/
- docker/python-base/
- job:
name: infra-prod-service-eavesdrop
parent: infra-prod-service-base
description: Run service-eavesdrop.yaml playbook.
required-projects:
- opendev/ansible-role-puppet
- opendev/system-config
- openstack/project-config
dependencies:
- name: infra-prod-install-ansible
soft: true
Rename service-letsencrypt to just letsencrypt This isn't a service, it's a meta thing that we run for different hosts at different times. Change-Id: Ib65665c98afb3ddb94b15346931be88a4b1757d8
2020-05-28 16:43:14 -05:00
- name: infra-prod-letsencrypt
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
soft: true
- name: system-config-promote-image-accessbot
soft: true
vars:
playbook_name: service-eavesdrop.yaml
files: &infra_prod_eavesdrop_files
- inventory/
- playbooks/service-eavesdrop.yaml
- playbooks/run-accessbot.yaml
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- inventory/service/group_vars/eavesdrop.yaml
- inventory/service/group_vars/puppet.yaml
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/run-puppet/
- playbooks/roles/install-ansible-roles/
- playbooks/roles/zuul-user
- playbooks/roles/install-docker
Run iptables in service playbooks instead of base It's the only part of base that's important to run when we run a service. Run it in the service playbooks and get rid of the dependency on infra-prod-base. Continue running it in base so that new nodes are brought up with iptables in place. Bump the timeout for the mirror job, because the iptables addition seems to have just bumped it over the edge. Change-Id: I4608216f7a59cfa96d3bdb191edd9bc7bb9cca39
2020-05-26 17:41:54 -05:00
- playbooks/roles/iptables/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/puppet-install/
- playbooks/roles/disable-puppet-agent/
- playbooks/roles/accessbot
- playbooks/roles/logrotate
- modules/openstack_project/manifests/eavesdrop.pp
- manifests/eavesdrop.pp
- docker/accessbot/
- job:
name: infra-prod-run-accessbot
parent: infra-prod-service-base
description: Run run-accessbot.yaml playbook.
required-projects:
- opendev/system-config
- openstack/project-config
dependencies:
- infra-prod-service-eavesdrop
vars:
playbook_name: run-accessbot.yaml
Run accessbot less frequently We already run accessbot in project-config when the accessbot script changes. We don't need to run it whenever any of the puppet or other config on eavesdrop runs, not do we need to run it hourly. Just run it nightly and on changes to the actual accessbot config. Change-Id: Idd47f7c96f677fd1e1c8da3be262a52a70646acd
2020-05-08 08:12:37 -05:00
files:
- accessbot/channels.yaml
- playbooks/run-accessbot.yaml
- playbooks/roles/accessbot
- docker/accessbot/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
Migrate codesearch site to container The hound project has undergone a small re-birth and moved to https://github.com/hound-search/hound which has broken our deployment. We've talked about leaving codesearch up to gitea, but it's not quite there yet. There seems to be no point working on the puppet now. This builds a container than runs houndd. It's an opendev specific container; the config is pulled from project-config directly. There's some custom scripts that drive things. Some points for reviewers: - update-hound-config.sh uses "create-hound-config" (which is in jeepyb for historical reasons) to generate the config file. It grabs the latest projects.yaml from project-config and exits with a return code to indicate if things changed. - when the container starts, it runs update-hound-config.sh to populate the initial config. There is a testing environment flag and small config so it doesn't have to clone the entire opendev for functional testing. - it runs under supervisord so we can restart the daemon when projects are updated. Unlike earlier versions that didn't start listening till indexing was done, this version now puts up a "Hound is not ready yet" message when while it is working; so we can drop all the magic we were doing to probe if hound is listening via netstat and making Apache redirect to a status page. - resync-hound.sh is run from an external cron job daily, and does this update and restart check. Since it only reloads if changes are made, this should be relatively rare anyway. - There is a PR to monitor the config file (https://github.com/hound-search/hound/pull/357) which would mean the restart is unnecessary. This would be good in the near and we could remove the cron job. - playbooks/roles/codesearch is unexciting and deploys the container, certificates and an apache proxy back to localhost:6080 where hound is listening. I've combined removal of the old puppet bits here as the "-codesearch" namespace was already being used. Change-Id: I8c773b5ea6b87e8f7dfd8db2556626f7b2500473
2020-11-17 17:13:46 +11:00
- job:
name: infra-prod-service-codesearch
parent: infra-prod-service-base
description: Run service-codesearch.yaml playbook.
vars:
playbook_name: service-codesearch.yaml
files:
- docker/hound/
- inventory/
- playbooks/service-codesearch.yaml
- inventory/service/host_vars/codesearch01.opendev.yaml
- inventory/service/group_vars/codesearch
- playbooks/roles/install-docker/
- playbooks/roles/pip3/
- playbooks/roles/codesearch
- playbooks/roles/logrotate
- playbooks/roles/iptables
Grafana container deployment This uses the Grafana container created with Iddfafe852166fe95b3e433420e2e2a4a6380fc64 to run the grafana.opendev.org service. We retain the old model of an Apache reverse-proxy; it's well tested and understood, it's much easier than trying to map all the SSL termination/renewal/etc. into the Grafana container and we don't have to convince ourselves the container is safe to be directly web-facing. Otherwise this is a fairly straight forward deployment of the container. As before, it uses the graph configuration kept in project-config which is loaded in with grafyaml, which is included in the container. Once nice advantage is that it makes it quite easy to develop graphs locally, using the container which can talk to the public graphite instance. The documentation has been updated with a reference on how to do this. Change-Id: I0cc76d29b6911aecfebc71e5fdfe7cf4fcd071a4
2020-06-23 11:41:27 +10:00
- job:
name: infra-prod-service-grafana
parent: infra-prod-service-base
description: Run service-grafana.yaml playbook.
vars:
playbook_name: service-grafana.yaml
files:
- inventory/
- playbooks/service-grafana.yaml
- inventory/service/host_vars/grafana01.org.yaml
- inventory/service/group_vars/grafana
- playbooks/roles/install-docker/
- playbooks/roles/pip3/
- playbooks/roles/grafana
- playbooks/roles/logrotate
- playbooks/roles/iptables/
Graphite container deployment This deploys graphite from the upstream container. We override the statsd configuration to have it listen on ipv6. Similarly we override the ngnix config to listen on ipv6, enable ssl, forward port 80 to 443, block the /admin page (we don't use it). For production we will just want to put some cinder storage in /opt/graphite/storage on the production host and figure out how to migrate the old stats. The is also a bit of cleanup that will follow, because we half-converted grafana01.opendev.org -- so everything can't be in the same group till that is gone. Testing has been added to push some stats and ensure they are seen. Change-Id: Ie843b3d90a72564ef90805f820c8abc61a71017d
2020-06-26 10:23:16 +10:00
- job:
name: infra-prod-service-graphite
parent: infra-prod-service-base
description: Run service-graphite.yaml playbook.
vars:
playbook_name: service-graphite.yaml
files:
- inventory/
- playbooks/service-graphite.yaml
- inventory/service/host_vars/graphite02.opendev.org.yaml
- inventory/service/group_vars/graphite
- playbooks/roles/install-docker/
- playbooks/roles/pip3/
- playbooks/roles/graphite/
- playbooks/roles/iptables/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
# Run AFS changes separately so we can make sure to only do one at a time
# (turns out quorum is nice to have)
- job:
openafs-server : add ansible roles for OpenAFS servers This starts at migrating OpenAFS server setup to Ansible. Firstly we split up the groups and explicitly name hosts, as we will me migrating each one step-by-step. We split out 1.8 hosts into a new afs-1.8 group; the first host is afs01.ord.openstack.org which already has openafs 1.8 installed manually. An openafs-server role is introduced that does the same setup as the extant puppet. The AFS job is renamed to infra-prod-afs as the puppet component will eventually disappear. Otherwise it runs in the same way, but also runs the openafs-server role for the 1.8 servers. Once this is merged, we can run it against afs01.ord.openstack.org to ensure it works and is idempotent. We can then take on upgrading the other file servers, and work further on the database servers. Change-Id: I7998af43961999412f58a78214f4b5387713d30e
2021-01-18 15:30:35 +11:00
name: infra-prod-service-afs
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
parent: infra-prod-service-base
openafs-server : add ansible roles for OpenAFS servers This starts at migrating OpenAFS server setup to Ansible. Firstly we split up the groups and explicitly name hosts, as we will me migrating each one step-by-step. We split out 1.8 hosts into a new afs-1.8 group; the first host is afs01.ord.openstack.org which already has openafs 1.8 installed manually. An openafs-server role is introduced that does the same setup as the extant puppet. The AFS job is renamed to infra-prod-afs as the puppet component will eventually disappear. Otherwise it runs in the same way, but also runs the openafs-server role for the 1.8 servers. Once this is merged, we can run it against afs01.ord.openstack.org to ensure it works and is idempotent. We can then take on upgrading the other file servers, and work further on the database servers. Change-Id: I7998af43961999412f58a78214f4b5387713d30e
2021-01-18 15:30:35 +11:00
description: Run AFS playbook.
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
vars:
openafs-server : add ansible roles for OpenAFS servers This starts at migrating OpenAFS server setup to Ansible. Firstly we split up the groups and explicitly name hosts, as we will me migrating each one step-by-step. We split out 1.8 hosts into a new afs-1.8 group; the first host is afs01.ord.openstack.org which already has openafs 1.8 installed manually. An openafs-server role is introduced that does the same setup as the extant puppet. The AFS job is renamed to infra-prod-afs as the puppet component will eventually disappear. Otherwise it runs in the same way, but also runs the openafs-server role for the 1.8 servers. Once this is merged, we can run it against afs01.ord.openstack.org to ensure it works and is idempotent. We can then take on upgrading the other file servers, and work further on the database servers. Change-Id: I7998af43961999412f58a78214f4b5387713d30e
2021-01-18 15:30:35 +11:00
playbook_name: service-afs.yaml
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
infra_prod_ansible_forks: 1
required-projects:
- opendev/ansible-role-puppet
- opendev/system-config
files:
- inventory/
openafs-server : add ansible roles for OpenAFS servers This starts at migrating OpenAFS server setup to Ansible. Firstly we split up the groups and explicitly name hosts, as we will me migrating each one step-by-step. We split out 1.8 hosts into a new afs-1.8 group; the first host is afs01.ord.openstack.org which already has openafs 1.8 installed manually. An openafs-server role is introduced that does the same setup as the extant puppet. The AFS job is renamed to infra-prod-afs as the puppet component will eventually disappear. Otherwise it runs in the same way, but also runs the openafs-server role for the 1.8 servers. Once this is merged, we can run it against afs01.ord.openstack.org to ensure it works and is idempotent. We can then take on upgrading the other file servers, and work further on the database servers. Change-Id: I7998af43961999412f58a78214f4b5387713d30e
2021-01-18 15:30:35 +11:00
- playbooks/service-afs.yaml
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- inventory/service/group_vars/afs
- inventory/service/group_vars/mirror-update
- inventory/service/group_vars/puppet
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/run-puppet/
- playbooks/roles/install-ansible-roles/
- playbooks/roles/puppet-install/
- playbooks/roles/disable-puppet-agent/
Run iptables in service playbooks instead of base It's the only part of base that's important to run when we run a service. Run it in the service playbooks and get rid of the dependency on infra-prod-base. Continue running it in base so that new nodes are brought up with iptables in place. Bump the timeout for the mirror job, because the iptables addition seems to have just bumped it over the edge. Change-Id: I4608216f7a59cfa96d3bdb191edd9bc7bb9cca39
2020-05-26 17:41:54 -05:00
- playbooks/roles/iptables/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/vos-release/
openafs-server : add ansible roles for OpenAFS servers This starts at migrating OpenAFS server setup to Ansible. Firstly we split up the groups and explicitly name hosts, as we will me migrating each one step-by-step. We split out 1.8 hosts into a new afs-1.8 group; the first host is afs01.ord.openstack.org which already has openafs 1.8 installed manually. An openafs-server role is introduced that does the same setup as the extant puppet. The AFS job is renamed to infra-prod-afs as the puppet component will eventually disappear. Otherwise it runs in the same way, but also runs the openafs-server role for the 1.8 servers. Once this is merged, we can run it against afs01.ord.openstack.org to ensure it works and is idempotent. We can then take on upgrading the other file servers, and work further on the database servers. Change-Id: I7998af43961999412f58a78214f4b5387713d30e
2021-01-18 15:30:35 +11:00
- playbooks/roles/openafs-server/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- modules/
- manifests/
- job:
name: infra-prod-remote-puppet-else
parent: infra-prod-service-base
description: Run remote-puppet-else.yaml playbook.
vars:
playbook_name: remote_puppet_else.yaml
infra_prod_ansible_forks: 50
required-projects:
- opendev/ansible-role-puppet
- opendev/system-config
files:
- hiera/
- inventory/
- playbooks/remote_puppet_else.yaml
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- inventory/service/group_vars/
- inventory/service/host_vars/
- inventory/service/group_vars/puppet
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- playbooks/roles/run-puppet/
- playbooks/roles/install-ansible-roles/
- playbooks/roles/puppet-install/
- playbooks/roles/disable-puppet-agent/
Run iptables in service playbooks instead of base It's the only part of base that's important to run when we run a service. Run it in the service playbooks and get rid of the dependency on infra-prod-base. Continue running it in base so that new nodes are brought up with iptables in place. Bump the timeout for the mirror job, because the iptables addition seems to have just bumped it over the edge. Change-Id: I4608216f7a59cfa96d3bdb191edd9bc7bb9cca39
2020-05-26 17:41:54 -05:00
- playbooks/roles/iptables/
Organize zuul jobs in zuul.d/ dir Our .zuul.yaml file has grown quite large. Try to make this more manageable by splitting it into zuul.d/ directory with jobs organized by function. Change-Id: I0739eb1e2bc64dcacebf92e25503f67302f7c882
2020-05-07 12:37:26 -07:00
- modules/
- manifests/
- job:
name: infra-prod-run-cloud-launcher
parent: infra-prod-service-base
description: Run cloud launcher playbook
vars:
playbook_name: run_cloud_launcher.yaml
infra_prod_ansible_forks: 1
required-projects:
- opendev/ansible-role-cloud-launcher
- opendev/system-config
dependencies:
- name: infra-prod-service-bridge
soft: true
files:
- playbooks/run_cloud_launcher.yaml
Split inventory into multiple dirs and move hostvars Make inventory/service for service-specific things, including the groups.yaml group definitions, and inventory/base for hostvars related to the base system, including the list of hosts. Move the exisitng host_vars into inventory/service, since most of them are likely service-specific. Move group_vars/all.yaml into base/group_vars as almost all of it is related to base things, with the execption of the gerrit public key. A followup patch will move host-specific values into equivilent files in inventory/base. This should let us override hostvars in gate jobs. It should also allow us to do better file matchers - and to be able to organize our playbooks move if we want to. Depends-On: https://review.opendev.org/731583 Change-Id: Iddf57b5be47c2e9de16b83a1bc83bee25db995cf
2020-05-26 15:46:41 -05:00
- inventory/service/host_vars/bridge.openstack.org.yaml
Copy Permalink