openstack
/
openstack-ansible
Code Issues Proposed changes

Add release note for services in venvs 

There is a known issue and an educational concern for operators who
work in OSA-based environments upgraded to Liberty from a prior
release.

Change-Id: Id63d28b357674dd4b1c821feba9f94ba1e8c81e6
Related-Bug: #1563377
This commit is contained in:
Steve Lewis 2016-03-29 15:07:27 -07:00 committed by Robb Romans
parent a2651186da
commit 9b04c517e4
1 changed files with 20 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
releasenotes/notes/services-deploy-in-venvs-4f573e5788370526.yaml Normal file
View File

@ -0,0 +1,20 @@
---
features:
- Services deploy into virtual environments by default
when the service relies on Python. Find the virtualenv
for each service under ``/openstack/venvs/`` on the
host or in the container where the service is
deployed. Disable the use of virtualenv by overriding
the service-specific variable (for example
``cinder_venv_enabled``) which defaults to ``True``.
issues:
- Services deploy into virtual environments by default
when the service relies on Python. On upgrade any
Python packages installed on the host or container are
not upgraded with the release unless the virtualenv
for that service is disabled. There might be older and
possibly broken packages left on the system outside of
the virtualenv, which can cause confusion for those
who attempt to use Python-based tools or services
without using the virtualenv. These left over packages
can be manually removed at the operator's discretion.