73a9acc7ad
This used to be called "bridge", but was then renamed with Ia7c8dd0e32b2c4aaa674061037be5ab66d9a3581 to install-ansible to be clearer. It is true that this is installing Ansible, but as part of our reworking for parallel jobs this is the also the synchronisation point where we should be deploying the system-config code to run for the buildset. Thus naming this "boostrap-bridge" should hopefully be clearer again about what's going on. I've added a note to the job calling out it's difference to the infra-prod-service-bridge job to hopefully also avoid some of the inital confusion. Change-Id: I4db1c883f237de5986edb4dc4c64860390cc8e22
24 lines
1.3 KiB
YAML
24 lines
1.3 KiB
YAML
- hosts: bridge.openstack.org:!disabled
|
|
name: "Bridge: bootstrap the bastion host"
|
|
become: true
|
|
roles:
|
|
- pip3
|
|
# Note for production use we expect to take the defaults; unit
|
|
# test jobs override this to test with latest upstream ansible.
|
|
# For example, if there is a fix on the ansible stable branch we
|
|
# need that is unreleased, you could do the following:
|
|
#
|
|
# install_ansible_name: '{{ bridge_ansible_name | default("git+https://github.com/ansible/ansible.git@stable-2.7") }}'
|
|
# install_ansible_version: '{{ bridge_ansible_version | default(None) }}'
|
|
- role: install-ansible
|
|
install_ansible_name: '{{ bridge_ansible_name | default("ansible") }}'
|
|
install_ansible_version: '{{ bridge_ansible_version | default("4.0.0") }}'
|
|
install_ansible_openstacksdk_name: '{{ bridge_openstacksdk_name | default("openstacksdk") }}'
|
|
install_ansible_openstacksdk_version: '{{ bridge_openstacksdk_verison | default("latest") }}'
|
|
# NOTE(ianw): At 2018-12, ARA is only enabled during gate
|
|
# testing jobs as we decide if or how to store data on
|
|
# production bridge.o.o
|
|
install_ansible_ara_name: '{{ bridge_ara_name | default("ara[server]") }}'
|
|
install_ansible_ara_version: '{{ bridge_ara_version | default("latest") }}'
|
|
- root-keys
|