kolla-ansible

  1. Bug #1530319
  2. Comment #10

Comment 10 for bug 1530319

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (master)

Reviewed: https://review.openstack.org/434917
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=dbc5967f7364489ba9a590969c3bba1a553b64fb
Submitter: Jenkins
Branch: master

commit dbc5967f7364489ba9a590969c3bba1a553b64fb
Author: Mark Goddard <email address hidden>
Date: Thu Feb 16 13:42:21 2017 +0000

    Support kolla-ansible installed in a virtualenv

    Currently it is not possible to use kolla-ansible when it has been
    installed in a virtualenv. Virtualenv-based installation may be
    desirable when a suitable system package (e.g. RPM, .deb) is not
    available, as it allows the user to install kolla-ansible and its
    dependencies without affecting the system-wide packages.

    This change checks for the presence of the $VIRTUAL_ENV environment
    variable to determine whether we are running in an virtualenv. Since
    kolla-ansible is not a python script, this comes with the caveat that we
    must source the virtualenv activation script ($VIRTUAL_ENV/bin/activate)
    before executing kolla-ansible.

    Change-Id: I19efb96605bee3b16df3a0b78cd681e5f15499f6
    Closes-Bug: #1530319