a88adc4101
We previously auto updated nodepool builders but not launchers when new container images were present. This created confusion over what versions of nodepool opendev is running. Use the same behavior for both services now and auto restart them both. There is a small chance that we can pull in an update that breaks things so we run serially to avoid the most egregious instances of this scenario. Change-Id: Ifc3ca375553527f9a72e4bb1bdb617523a3f269e
24 lines
628 B
YAML
24 lines
628 B
YAML
- hosts: nodepool-builder:!disabled
|
|
name: "Configure nodepool builders"
|
|
strategy: free
|
|
roles:
|
|
- iptables
|
|
- install-docker
|
|
- nodepool-base
|
|
- configure-openstacksdk
|
|
- nodepool-builder
|
|
|
|
- hosts: nodepool-launcher:!disabled
|
|
name: "Configure nodepool launchers"
|
|
# The nodepool-launcher role will restart launchers if new container
|
|
# images are available. Run serially to ensure we don't kill the entire
|
|
# cluster if something is terribly wrong.
|
|
serial: 1
|
|
roles:
|
|
- iptables
|
|
- install-docker
|
|
- nodepool-base
|
|
- configure-openstacksdk
|
|
- configure-kubectl
|
|
- nodepool-launcher
|