It conforms with API_WORKERS default calculation to avoid too much
processes consuming the memory.
Change-Id: If2b483711668715047662a286cb0f0e3b52bbdac
Signed-off-by: Cédric Ollivier <ollivier.cedric@gmail.com>
Fedora-Cloud-Base-29-1.2.x86_64 is removed from openstack local mirror.
Update to use Fedora-Cloud-Base-30-1.2.x86_64 for test jobs.
Change-Id: Id3026a115e3a044b3dc00030fd6d82549dc189b6
It's not enabled by default[1] in devstack, is
deprecated and not needed for glance v2.
[1] https://review.opendev.org/#/c/702709/
Change-Id: I01514d8639e7604cca9846e05904ebe062393550
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
We don't need admin or internal endpoints in a normal devstack setup,
other basic projects are also only creating the public endpoint now.
Change-Id: I9bd6007509214c7a7ed7f7f4e391b609da4408a5
devstack already clones the source from the repo/ref provided to
enable_plugin function.
Having to re-clone heat effectively requires to also set HEAT_BRANCH
separately which is unnecessary repetition and make it less obvious
how to deploy Devstack+Heat from stable branches locally w/o Zuul Cloner
with RECLONE=true.
Change-Id: I91b5048efa4606e86094e0a458e320216f66ce3e
Our cgit instance will be going away and opendev.org is the new
preferred URL for browsing our git repos. Redirects will exist for the
foreseeable future, but it's more efficient to just go directly to the
new locations.
Change-Id: Ic5fa1a8436f57836ad37b752a0cca1cd4f3a21a7
Setting RUN_HEAT_INTEGRATION_TESTS=False disables the Heat
integration tests which are normally executed by Grenade
after the deployment of the base environment and after the upgrade.
This is useful when Heat is used in a Grenade job of another
component, where the focus of the testing is not Heat itself,
thus shortening the run-time of the overall Grenade job.
The default behavior is unchanged.
Change-Id: I47b258fecd45ebc08c82df179625bcfb57a32894
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/
We are updating all Python projects to publish artifacts to PyPI. The
name "heat" is already taken there by another project, and they have
rejected our request to claim the name. We therefore need to change the
dist name used to package heat. We have some other projects publishing
using an "openstack-" prefix, so I propose using the name
"openstack-heat". This will not change the imports or anything else
about how the code works, just how it is packaged.
Add a grenade plugin for upgrading between the packages with different
names so that we can clean up the old version of the code and avoid
discovering the heat plugins multiple times in different locations.
Change-Id: I59b55cffd9e648f842eb286b936f09c5b55a76db
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
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
