openstack/openstack-ansible
Code Issues Proposed changes

Restart horizon when package/venvs change

Browse Source 
Currently, upgrading a horizon package/venv does not explicitly trigger
a restart.  A restart will only occur if an explicit or implicit config
change occurs.

This commit adds several restart notifiers such that a horizon package
upgrade or venv replacement will force a restart.

Note that this issue exists in all OpenStack roles at the moment, but
the remaining roles are being addressed in their re-deploy venv
reviews.  The horizon re-deploy venv change was merged a while back
which is why we need the separate review for this.

Change-Id: I890e46bb7a2973c3582be7a37ee70730d1e3ffef
This commit is contained in:
Matt Thompson 2016-01-28 09:28:07 +00:00
parent 8c0c41b8b3
commit 023f73d3a9
2 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
playbooks/roles/os_horizon/tasks/horizon_install.yml
View File

@ -52,6 +52,7 @@
when:
- horizon_venv_enabled | bool
- horizon_get_venv | failed
notify: Restart apache2
tags:
- horizon-pip-packages
@ -66,5 +67,6 @@
delay: 2
with_items: horizon_pip_packages
when: not horizon_venv_enabled | bool
notify: Restart apache2
tags:
- horizon-pip-packages

1
playbooks/roles/os_horizon/tasks/horizon_pre_install.yml
View File

@ -149,6 +149,7 @@
when:
- horizon_venv_enabled | bool
- horizon_get_venv | changed
notify: Restart apache2
tags:
- horizon-install
- horizon-pip-packages