44d053c888
Remove all tasks and variables related to toggling between installation of keystone inside or outside of a Python virtual environment. Installing within a venv is now the only supported deployment. Additionally, a few changes have been made to make the creation of the venv more resistant to interruptions during a run of the role. * unarchiving a pre-built venv will now also occur when the venv directory is created, not only after being downloaded * virtualenv-tools is run against both pre-built and non pre-built venvs to account for interruptions during or prior to unarchiving Change-Id: Ic0a0dac84a26aba2ef0ce5410dc7c722570cd410 Implements: blueprint only-install-venvs |
||
---|---|---|
.. | ||
keystone-fernet-rotate.sh.j2 | ||
keystone-httpd-mpm.conf.j2 | ||
keystone-httpd.conf.j2 | ||
keystone-paste.ini.j2 | ||
keystone-ports.conf.j2 | ||
keystone-wsgi.py.j2 | ||
keystone.conf.j2 | ||
keystone.domain.conf.j2 | ||
policy.json.j2 | ||
shibboleth2.xml.j2 | ||
shibboleth-attribute-map.xml.j2 |