Something are introduced in this patch:
* As devstack-gate/devstack-vm-gate-wrap.sh is not really zuul v3
native, we move all configs in to `devstack/lib/heat` and .zuul.yaml.
* Remove extra configs process in devstack. Like setup tempest(which
is well covered by tempest itself.) or overlapping heat test configs setup.
Use tempest config for all heat_integration tests. Also remove
heat_integrationtests/common/configs since they're no longer required.
* copy post.yaml for grenade jobs. As we migrate to zuul v3 for
functional tests but not grenade (not yet), the post.yaml should exists
under grenade dir. since it's only required by grenade jobs.
* Use post.yaml in functional tests for cleanup test environments.
Story: #2007056
Task: #37908
Depends-On: https://review.opendev.org/701105
Change-Id: I4f531161a7222e2c2a21f8d483f9c2a1d91dc38d
Tempest's service_availability config option includes all the service
availability which is further used by tests to take decision of skip
or run the test.
For example, [service_availability].heat is true then, heat test will run
or if [service_availability].heat is false then, all the heat related tests either
in heat tempest plugin or any other plugins will be skipped.
Currently this setting for heat service[1] is in devstack lib/tempest
which is being removed by - https://review.openstack.org/#/c/619973/
For better maintenance, we are moving all tempest non-owned service setting
to service devstack plugin side.
This commit add the setting of heat service on ceilometer devstack plugin.
Related-Bug: #1743688
[1] d6b253502a/heat_tempest_plugin/config.py (L15)
Depends-On: https://review.openstack.org/#/c/619990/
Change-Id: I5013ce8be1a4fb5219ea89a63add812558191025
Needed-By: https://review.openstack.org/#/c/619973/
- Call create_heat_accounts irrespective of whether keystone
is enabled or not.
- Use hardcoded auth_encryption_key
Change-Id: I03fab7f986ec2a9703044f4bff31d477e2e7fe6a
This reverts the workaround for the devstack plugin,
as now the gate jobs pass(with the plugin and no devstack
tree heat code) and make it only a devstack plugin.
Change-Id: Ia8d88eca2dec301b692bbef3e1d8988f00e1936a
Depends-On: I5b60422bf1f5fa78aa8f3383f7a222e0356d9e42
Remove the redundant code for bulding a pip mirror
for heat agents. At present it's used by
test_server_software_config.py, which is disabled.
We may use RDO packages for the agents in the future,
when we plan to enable these tests.
Change-Id: I94e46927b0d0d7e93d8bf5e58eb27310f443a8bf
Closes-Bug: #1634717
Now that we've the devstack plugin in-tree let's use
the functions from the plugin for upgrade, so that
we can remove the devstack tree heat code.
Change-Id: Ic392bcc24bc374ee8511a94f1d8f6ac23131c7e3
When heat is enabled, both stack.sh and plugin try to do account
creation (as part of keystone startup which fails as heat is not yet
installed), intialize the db and start the services. In this patch
(which is a workaround), we'll use a set of dummy function calls to
avoid it. We'll remove these functions later(once we clean up devstack
stack.sh) and rename the currently used functions.
Change-Id: I84250d598ba76deae2a5bad6bbf3f0acfe1cfbe6
This adds the actual devstack plugin, devstack should not run the heat code
in the devstack project.
Note that this is not yet configured to run in the gate.
Change-Id: I8d0918a8f8bb8399793c7164d26739953710b3ec