the purpose of upgrade script is to upgrade service,
and heat shouldn't run any jobs inside of that. moreover
there is no benefit in executing these tests after upgrade
because it doesn't test anything related to upgrades:
if heat is correctly configured after upgrade it will be ready
to run tests (but this can be covered by usual integration job).
heat should be testing specific things like
updating stacks after migration to the new openstack code,
deleting stacks and so on.
Co-authored-by: Vitaly Gridnev <vgridnev@mirantis.com>
Change-Id: Ie600dfc09db0ffa91609f92be4b9ef27259b5314
cinder-backup service is optional, and currently not discoverable with
non-admin scoped tokens.
This patch introduces a new config option `volumes.backups_enabled`
(defaults to True for backward compat).
When set to False, it will fail validation of stacks containing volume
resources with deletion_policy set to Snapshot,
as such stacks will be undeletable in the absence of cinder-backup
service.
Change-Id: I10c4787870e7b240d775aa5d66eb1d0a6d837d8d
Partial-Bug: #1595159
Config auth_plugin in trustee group is deprecated.
Change to use auth_type in trustee group instead.
Closes-Bug: 1592482
Change-Id: I57d2fbbc426b0ce0478f7b8dfac7533c7d513bf0
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
This begins work toward moving the devstack code to a devstack plugin within
heat tree. This allows us to experiment with the devstack code more easily,
as well as take some load off of the devstack team.
Note that the plugin is not enabled until we enable it in project-config,
so this doesn't actually affect devstack runs yet. The files that exist in
devstack are listed below.
$ find . -name *heat*
./lib/heat
./files/apache-heat-api-cfn.template
./files/debs/heat
./files/apache-heat-pip-repo.template
./files/apache-heat-api-cloudwatch.template
./files/apache-heat-api.template
All of these files are copied to heat tree.
Change-Id: Ie7f16eff554e6cc2c62823cd49b6f726d96f25b4
Some echo message contain error or warning message which better be contain in
stderr. And futher more some error message already contain in stderr, but for
error message reader, the following information for that echo should be
contained as well.
Change-Id: I2aac631df19829218d446150c91cf6d50aa5e7e7
This includes lib/apache from devstack as the devstack heat plugin now
requires it.
Change-Id: Ie48e417f2b36ce79c3485e559b6141a1499b6eb1
Closes-Bug: #1511369
Due to some fix in devstack, using the old lib/heat library doesn't work
anymore, so let's replicate the stop_heat function.
Change-Id: I8e7c62962cef29e35c37ad98a1646630388fb4ab
Closes-Bug: #1506462
Ceilometer services are now enabled and controlled via a plugin
with this change Ie3219a41a3d371d9ac21552e3d8b15775ea696f6. This
means we can remove all ceilometer specific manual config entries
in the grenade plugin.
Related-Bug: #1489436
Change-Id: I2fbff1fed38ac8acc8a7950024714abea049aeb8
Only a few tests are run because these tests only verify the
sanity of the build rather than doing the upgrade tests itself.
Closes-Bug: #1482152
partial blueprint upgrade-tests
Change-Id: I8fed19bd25cc3a62c03c35afafe2b662551dbd4e
The following implements in tree support for grenade upgrade testing
for heat. It includes the expected directory structure to be used for
the external plugin.
For now, we create a simple OS::Heat::RandomString resource
and check whether the stack survives the upgrade.
We should add better tests for upgrades in the future.
Co-Authored-By: Steven Hardy <shardy@redhat.com>
Co-Authored-By: Sergey Kraynev <skraynev@mirantis.com>
Co-Authored-By: Emilien Macchi <emilien.macchi@enovance.com>
partial blueprint upgrade-tests
Change-Id: I0847004a8ac023a113cabaee46896abc823a01da
Michael Ionkin
Pavlo Shchelokovskyy
ricolin
xiaolihope
Rabi Mishra
Thomas Herve
Sirushti Murugesan