Jesse Pretorius 46258cc435 Ensure that upper constraints are always applied ... When the upper constraints are not applied, the resulting build for the same tag may be different from one day to the next. This results in an inconsistent experience for deployers. This patch sets the upper constraints to be used by the following: - https://review.openstack.org/388159 (lxc hosts) - https://review.openstack.org/388072 (pip install) - https://review.openstack.org/388230 (keystone install) This is a pattern to establish across other roles. As some pip installs happen before the repo server is up a common set of tasks is added to a few of the plays to verify if there is a local copy of constraints available. If not it will then source the upstream constraints based on the OpenStack requirements SHA that's been pinned. Change-Id: I7ddd44be30c610609c1429147646dcb1d3e6ca59		2016-10-21 19:31:07 +00:00
..
mysql-db-user.yml	Cleanup/standardize common tasks	2016-07-21 17:18:26 -05:00
os-log-dir-setup.yml	Cleanup/standardize common tasks	2016-07-21 17:18:26 -05:00
os-lxc-container-setup.yml	Fix container log bind mount regression	2016-10-13 05:28:39 +00:00
package-cache-proxy.yml	Change the common proxy cache manage tasks to be stateful	2016-10-12 23:43:57 +00:00
rabbitmq-vhost-user.yml	Support multiple rabbitmq clusters	2016-08-25 10:40:45 +00:00
set-upper-constraints.yml	Ensure that upper constraints are always applied	2016-10-21 19:31:07 +00:00