Merge "Use a virtualenv for remote operations by default"

This commit is contained in:
Zuul 2018-10-09 16:54:27 +00:00 committed by Gerrit Code Review
commit 175eb3c891
5 changed files with 27 additions and 0 deletions

View File

@ -132,3 +132,7 @@ If kayobe detects that ``ansible_python_interpreter`` is set and references a
virtual environment, it will create the virtual environment if it does not
exist. Typically this variable should be set via a group variable for hosts in
the ``seed``, ``seed-hypervisor``, and/or ``overcloud`` groups.
The default Kayobe configuration in the ``kayobe-config`` repository sets
``ansible_python_interpreter`` to ``{{ virtualenv_path }}/kayobe/bin/python``
for the ``seed``, ``seed-hypervisor``, and ``overcloud`` groups.

View File

@ -0,0 +1,3 @@
---
# Use a virtual environment for remote operations.
ansible_python_interpreter: "{{ virtualenv_path }}/kayobe/bin/python"

View File

@ -0,0 +1,3 @@
---
# Use a virtual environment for remote operations.
ansible_python_interpreter: "{{ virtualenv_path }}/kayobe/bin/python"

View File

@ -0,0 +1,3 @@
---
# Use a virtual environment for remote operations.
ansible_python_interpreter: "{{ virtualenv_path }}/kayobe/bin/python"

View File

@ -0,0 +1,14 @@
---
fixes:
- |
Fixes an issue introduced by the release of ``pip`` version 10, whereby the
Python ``docker`` package would fail to install. This is resolved by using
a remote Python virtual environment for executing Kayobe Ansible tasks by
default. See `Story 2002010
<https://storyboard.openstack.org/#!/story/2002010>`__ for details.
upgrade:
- |
Modifies the default ``kayobe-config`` configuration to use a remote Python
virtual environment for executing Kayobe Ansible tasks. This affects hosts
in the ``seed``, ``seed-hypervisor``, and ``overcloud`` groups. See `Story
2002010 <https://storyboard.openstack.org/#!/story/2002010>`__ for details.