Commit Graph

15 Commits

Author SHA1 Message Date
Jiri Podivin ef4979fcd8 Deprecation notices for FS 004 and 011.
Both featuresets were superceded by standalone jobs
and are no longer used within the CI.

Furthermore, the scenario they refer to is no longer available.
It is therefore dubious if the FS in question can even be used.

Signed-off-by: Jiri Podivin <jpodivin@redhat.com>
Change-Id: If42239fbc306e62b8047e7497ffe1fb8d4c8e4d3
2021-11-09 12:55:13 +01:00
Arx Cruz c301c85f12 Replace run_tempest with use_os_tempest
The variable run_tempest was used by validate-tempest. Since now we use
only os_tempest, this variable is no longer required, however, since
use_os_tempest is default to true, we must change it where the
run_tempest is false, like in the upgrade/update jobs, since we don't
run tempest on those.

Change-Id: Idb8166992976ce6303f95f72011aa65fe536931e
2021-01-13 12:19:31 +01:00
Jose Luis Franco Arza 7445fc3cb7 Clean up upgrades/updates featureset.
Once [0] got merged, there is no chance that the
overcloud-upgrade role will run. Upgrade job have
all been moved to use the new tripleo-upgrade, so
we can dispense all overcloud-upgrade related
variables from the featuresets.

[0] - Iaf30244187d27909ab803175843056e0827d0b24

Change-Id: Ibe715cc4f604ba554db8dd4ab2d95391e4b1f311
2018-07-02 12:27:06 +02:00
Jose Luis Franco Arza 012d69bcdc Remove use_tripleo_upgrade and add var into fs037.
As part of the upgrades/updates playbook refactor
it has been removed the existence of a 'legacy'
and 'new' upgrades playbook, which was being
controlled by the 'use_tripleo_upgrade' variable
Iaf30244187d27909ab803175843056e0827d0b24.

Also, it's been moved the parameter container_registry_file
from the overcloud update's playbook into its
corresponding fs.

Related-Bug: #1749740

Depends-On: Iaf30244187d27909ab803175843056e0827d0b24
Depends-On: Iec42b574d697f3acfd668636e3dd11217a3ea25e
Change-Id: I27f13b164bb78619f8830b875ec9f04445ce1e26
2018-04-25 15:55:17 +02:00
Jose Luis Franco Arza efbacd05f5 Update overcloud-prep-containers script name.
After merging [0], the name set to the script
used to prepare containers before the upgrade
step hast changed. This patch sets the right
name in the featureset, so O->P job doesn't
fail.

[0] - https://review.openstack.org/#/c/540473/

Depends-On: I033ec0d0dd4fbf26b7231ca48d73f28c12e78b0f
Change-Id: I8cc94500c317c49cb68567f79f65f0e12fcd75ea
Closes-Bug: #1759060
2018-03-28 07:48:15 +02:00
Jose Luis Franco Arza 43770ba494 Set tripleo-upgrade vars in featureset.
To enable a more dynamic way of calling the tripleo_upgrade role in
oooq, we specify the variables used by the role in the corresponding
featureset file.

Co-Authored-By: Sofer Athlan-Guyot <sathlang@redhat.com>

Change-Id: I5a383d09b2c1cef04d95d0b7a626e8828c428130
2018-02-22 14:07:15 +01:00
Wes Hayutin bab0f87196 remove deployed_server from common args
deployed_server is no longer common
through out the multinode featuresets.
deploy_steps_ansible_workflow is an
alternative now.

Related-Bug: #1748315
Change-Id: I28988d30338527669da25bc764143cf57a995af9
2018-02-09 14:05:30 +00:00
Emilien Macchi 0a9929d16c Remove tempest_config (obsolete)
Depends-On: Ie3b37b17bf41b5f36bc60bfd0e4607ed4a3aaf6d
Change-Id: If51721ac720843fa81a7e20ae37a5ac702c3f6c5
2017-11-24 04:46:16 +00:00
Martin André cbeb7b84f0 Use different variables for deploy and upgrade scenarios
Use the new upgrade_composable_scenario variable from oooq-extra to set
the composable scenario file used during upgrade.

Closes-Bug: #1714905

Change-Id: Ie0e8de54794a9259c0aeb8c67ae0f6a908844093
2017-10-15 06:49:39 +00:00
John Trowbridge 3ed912bd91 Move common multinode role setup from tripleo-ci
This configuration was previously in tripleo-ci in the
testenv/multinode.yml file, but it is not specific to tripleo-ci.

This would be nice to add to the common multinode config and only
override where needed, but our current code does not allow for
overriding what is in the common config.

Change-Id: Ia042fc578ade2c073504ceb117b1da3ff0a4e051
2017-08-19 06:52:13 +00:00
Emilien Macchi f2219bba24 Enable pingtest on containers-multinode-upgrade
This patch enables the pingtest on containers-multinode-upgrade job,
so we can see if upgrades work and if we still have a running OpenStack
cloud.

Change-Id: Ibc7f6f04bfdef8a2bc6a399ddf8ece56919d4b48
2017-08-18 04:24:14 +00:00
Jiri Stransky 3fa2214be9 Add missing deploy_composable_scenario in featuresets
There were still a couple of featuresets that needed
deploy_composable_scenario variable set, and it caused the upgrade CI
job to start failing recently.

As explained in commit message of change
I7e7c13b9151607233f1159ed91c455dcec37e230 we were setting this
variable elsewhere previously, but seems like we aren't doing that
anymore.

Change-Id: I8303a8d90a756512a8cfb0ac23984c58183138a2
Closes-Bug: #1710112
2017-08-12 10:41:59 +00:00
Jiri Stransky b68f2b9845 Use multinode-containers scenario in featureset011
This is the same as the current multinode-container-upgrade.yaml, but
we're changing the name to reflect better that the scenario isn't
specific to upgrades. After this commit is merged, we can delete
multinode-container-upgrade.yaml from t-h-t.

Change-Id: Ib04e2ccb330d73df464ad97a20908f20426a4249
2017-05-30 14:19:40 +02:00
Jiri Stransky 5c4aaf3d6f TripleO CI mixed release master UC / ocata OC
For testing upstream upgrades O -> master(P).

Related-Bug: #1685795
Co-Authored-By: Mathieu Bultel <mbultel@redhat.com>
Change-Id: I2c30c560f7e0b5ffd9fff3b567b3c80f65698e89
2017-05-03 17:25:27 +02:00
Jiri Stransky 25e76f5cc0 Add featureset011 - upgrade from BM to containerized
This featureset deploys a non-containerized overcloud first, and then
upgrades it to a containerized one.

Change-Id: Ia013fe331d84adce7d36af6bd4e33d37c0755fdd
2017-04-27 10:39:25 +02:00