Ian Wienand 9e2d9f6aef bridge: switch OSC from container to local install
Currently "openstack" command on bridge doesn't work, because we need
cinder client pinned to an older version for RAX support.  The
upstream container uses the latest versions of everything and it fails
to parse the "volume_api_version: 2" pin for RAX in the config file.

In general, the version of openstackclient we can probably most likely
rely on to work is the one from the launch-node virtualenv.  It also
means we just have one place to manage a broadly-compatible version,
instead of trying to manage versions in separate containers, etc.

This converts the /usr/local/bin/openstack command from calling into
the container, to calling into the launch venv.

Change-Id: I604d5c17268a8219d51d432ba21feeb2e752a693
2022-11-25 09:37:40 +00:00

23 lines
706 B
YAML

- name: Create launcher venv
include_role:
name: create-venv
vars:
create_venv_path: '/usr/launcher-venv'
- name: Install node launcher
pip:
name: 'file:///home/zuul/src/opendev.org/opendev/system-config/launch'
virtualenv: '/usr/launcher-venv'
# Admins use openstackclient on the bastion host to deal with cloud
# issues. The best version to use is the one from launch node, as
# whatever workarounds we need to talk to all clouds should be in that
# environment. For convenience link this version globally
- name: Link openstack client globally
file:
src: /usr/launcher-venv/bin/openstack
dest: /usr/local/bin/openstack
owner: root
group: root
state: link