
Rename install_openstacksdk to install_ansible_opensatcksdk to make it clear this is part of the install-ansible role, and it's the openstacksdk version used with ansible (might be important if we switch to virtualenvs). This also clears up inconsistency when we add ARA install options too. Change-Id: Ie8cb3d5651322b3f6d2de9d6d80964b0d2822dce
30 lines
1.3 KiB
YAML
30 lines
1.3 KiB
YAML
- hosts: bridge.openstack.org
|
|
name: "Bridge: configure 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("2.7.3") }}'
|
|
install_ansible_openstacksdk_name: '{{ bridge_openstacksdk_name | default("openstacksdk") }}'
|
|
install_ansible_openstacksdk_version: '{{ bridge_openstacksdk_verison | default("latest") }}'
|
|
- root-keys
|
|
- ansible-cron
|
|
- cloud-launcher-cron
|
|
tasks:
|
|
- name: Allow Zuul to trigger Ansible
|
|
authorized_key:
|
|
state: present
|
|
user: root
|
|
key: "{{ item }}"
|
|
loop:
|
|
- "https://zuul.openstack.org/api/project-ssh-key/openstack-infra/system-config.pub"
|
|
- "https://zuul.openstack.org/api/project-ssh-key/openstack-infra/project-config.pub"
|