1. If the load balancer host is not the same as the control
plane hosts, then 'Ensuring haproxy runs' fails unless
facts are gathered.
2. The value for 'repo_release_path' is set in the vars file
'defaults/source_install.yml', so the repo check fails
without reference to that vars file.
3. When running 'Sanity checks for all containers' not all
host and container facts are gathered, so the play fails
due to missing facts unless facts are set to gather.
4. Instead of verifying both localhost and the utility
containers for being ready to run the os_* modules, we
only need to verify whichever one is the designated
'openstack_service_setup_host'.
5. The memcache server connectivity test should have a short
timeout, otherwise the task hangs for ages if it isn't
working.
6. The rabbitmq vhost name is corrected and set consistently,
otherwise those tests do not work.
7. The rabbitmq test venv fails to build for two reasons. One
is that the venv creation fails, because virtualenv tries
to download the latest pip/setuptools and fails due to the
pip.conf restricting it. The second is that the python
package 'pika' is not on the repo server. The task is changed
to make use of the common python_venv_build role and to make
use of pypi as an index when building the wheel.
Change-Id: I6f5f4a1bd55abc78ad5993076719a3ac5914af1d
This adds a playbook, oriented for users, to automatically test
their installation after the setup infrastructure test.
These are connectivity tests to the infrastructure, and ensure
that containers would behave properly when running the openstack
playbooks.
These are based on the general assumption that ppl would use
a container management network.
Change-Id: Idb331dd6a72439c838708216500039f628b2760c
