This patch defines the specified set of tests & runs these during
upgrade in grenade-multinode job.
Change-Id: I99fa1717f4bf46afc8dd989a3aae129e5c4ab9d7
* Change transport_url to test Heat's upgrade strategy [1] in gate.
[1] https://review.openstack.org/475853/
Change-Id: I08770d2ae09891d7983345616186cff7c26df4ce
We won't have policy.json file by default anymore, so we don't need
this `cp` command.
Implements: bp policy-in-code
Change-Id: I84c99e38c34dc41cc33126291563ea90038ce107
Add cloudformation and cloudwatch policy in code rules.
Remove policy.json. We don't keep any default policy rules in
policy.json from now. Still they can create policy.json file and
add any rules they try to override.
Partially-Implements: bp policy-in-code
Change-Id: I610115dc1974b2182ce673bb086a1da15b022de3
Removing the uwsgi config files on stop breaks upgrades when using
uwsgi, so let's not do that. Keeping the file deletes in cleanup
makes sense and those calls remain.
Change-Id: I603754c3f5ed5d2f143cf789df96018ec99ad692
- Call create_heat_accounts irrespective of whether keystone
is enabled or not.
- Use hardcoded auth_encryption_key
Change-Id: I03fab7f986ec2a9703044f4bff31d477e2e7fe6a
This adds uwsgi sample configs and documentation for
deploying api services with httpd.
This moves the existing mod_wsgi sample configs from devtsack
folder as they are not specific to devstack.
Change-Id: I91fd64d9deba3371b62c00ba8b01a7aca21b2393
This change ensures that api services deployed with apache+uwsgi
by default with devstack. User can still deploy apache+mod_wsgi
by setting WSGI_MODE=mod_wsgi in local.conf.
Using HEAT_USE_APACHE=False or HEAT_USE_MOD_WSGI=False
(for backward compatibility) would deploy the services
without apache.
Change-Id: Ia5e28e2987b4aeab6c049a3bde3a956204ddc5d9
Depends-On: I3b77aafc6104119503363e5db36b0379964daba5
Now that sevices run with systemd at the gate, use the common
function to make it compatible(i.e colorized_logging).
Change-Id: Ieb65618c1bcda3f56201ba3d3c49f6ef1c02c650
- Use domain ids along with domain names
It's possible that either the domain_id or domain_name
is set in the env.
- Adds an workaround for bug #1662911
- Fix shutdown script for apache
Change-Id: Ib9d3c14327d73d8cb0e0cddcc9d16191797ffffa
Closes-Bug: #1663105
We recently changed devstack to use httpd+mod_wsgi as the
default and split the access logs. However, we don't seem
to tail the correct log files.
Change-Id: I3aaefc92e6dbf4721b6a979fc72835abe9b54f14
Closes-Bug: #1661495
Run api services with httpd+mod_wsgi in devstack.
This also skips sighup tests conditionally.
Change-Id: I6631f1fecb906ae0c4bb96a2f868117eff045aa0
Closes-Bug: #1656617
When setting up additional devstack instances with heat, don't
recreate the database and do db_sync, as it would point to some
existing database.
Change-Id: I65fb33b0ad69bc4e5ff390e2b110779178b957ce
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
Now that the apache job is fixed, change the plugin to use
apache config templates from local tree. Else, it would
not work when the devstack tree code is removed.
Change-Id: I9a8627ad85821001968948dd7798999c8db14023
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 base and target releases are incremented in grenaderc,
we should run the integration tests using tempest plugin before
upgrade.
Change-Id: I39b7758798ff94401fda042ff6954de75821e8bb
Closes-Bug : #1627297
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
We seem to be running quite a few neutron tests during
upgrade and it seems to result in neutron quotas for
resources being exceeded, when tests run in parallel.
We should avoid running them.
Change-Id: I0a88f509af05a98ddd4811ea920a81cc997a0c6a
Closes-Bug: #1618789
Falling back to environment variable credentials is convenient for
development but could lead to unexpected credentials being used during
tests. Also this is not a known practice for tempest tests.
This change removes the env var defaults and explicitly sets the
credentials to use in prepare_test_env.sh.
Pre and post grenade tests also get their config from the conf file
rather than the environment.
blueprint tempest-plugin-support
Change-Id: Icf9fb4c58ed11483106c2b62d1e1093223f7dc51
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
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