openstack-ansible-os_tempest/releasenotes/notes/tempest-service-setup-host-da08c1d4775ea0d1.yaml
Jesse Pretorius 81f6bda4c0 Execute service setup against a delegated host
In order to reduce the packages required to pip install
on to the hosts, we allow the service setup to be delegated
to a specific host, defaulting to the deploy host.

1. We no longer need tempest_requires_pip_packages,
   so it is removed.
2. The openstack_openrc role is executed in the playbook,
   so we do not need it as a meta-dep any more.
3. All uses of our custom keystone module have been
   replaced with standard Ansible modules.
4. Using the service delegation model, it makes no sense
   to run the resource creation on all hosts, so we
   use run_once instead.
5. Given that we're using developer mode for master
   integrated builds, and pip.conf is present, we need
   to use the CLI to create the virtualenv so that we
   can use the '--never-download' option.

Change-Id: I572db645b64a4a0ac6255bc36eaac1be13336989
2018-08-10 11:57:13 +00:00

26 lines
945 B
YAML

---
features:
- |
The service setup in keystone for tempest will now be executed
through delegation to the ``tempest_service_setup_host`` which,
by default, is ``localhost`` (the deploy host). Deployers can
opt to rather change this to the utility container by implementing
the following override in ``user_variables.yml``.
.. code-block:: yaml
tempest_service_setup_host: "{{ groups['utility_all'][0] }}"
- |
Rather than a hard-coded set of projects and users, tempest can
now be configured with a custom list with the variables
``tempest_projects`` and ``tempest_users``.
deprecations:
- |
The variable ``tempest_requires_pip_packages`` is no longer required
and has therefore been removed.
- |
The variable ``tempest_image_downloader`` has been removed. The image
download now uses the same host designated by the
``tempest_service_setup_host`` for the image download.