Move the ec2-api queue declaration from the pipeline level (where it
is no longer valid) to the project level.
https: //lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html
For stable/yoga: Amended to actually drop the queue definition from the
gate pipeline, which was no longer present for the original patch.
Change-Id: I3103c4ecb803e784c87ed4cff5124d303620d4a5
(cherry picked from commit 16b27e67ea)
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: I4706c90003aeae3529077d26185a58cf27acdb93
Non-containerized multinode scenario jobs are no longer supported
and should be removed from zuul config.
Change-Id: I2420e22f9016d62023f732b29cfc3803a6f5a0be
The install-guide-jobs template needs to stay in project-config, remove
it from zuul file.
See also https://review.openstack.org/597618
Change-Id: I572743ee994e74e4d43de29991c0634bb296cd9a
(cherry picked from commit dc5480d940)
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: Ia8b18f7c7a69537c1a33b56e70301647b001a537
Story: #2002586
Task: #24295
According to [1], "auth_uri" has been deprecated.
This patch replace it by using "www_authenticate_uri" instead.
[1] https://review.openstack.org/#/c/508522
Change-Id: I3242394fd4ebfa7eda390be872372a53b5311a46
(cherry picked from commit 8a3358e2d1)
when two clients come for functions where check_default_vpc
is present then one goes to create default vpc and other fails.
it fails because vpc with is_default flag is already in DB
but children objects (like subnets) are not yet created.
For we will lock check_default_vpc function.
Another way is to rework _create_vpc. It can create VPC
without is_default flag. And at the end it can set the flag.
First thread will pass this. And second thread will fail at flag set
operation and will revert all created object. Then second thread
can check presence of default VPC again.
This way is better cause it can work across several controllers.
Change-Id: I5586fa234257b72721e328a9fa2375a56d1553c2
remove link to metadata configuration from
devstack section. metadata is configured by plugin's
script for devstack and user doesn't require to
configure it by himself.
Add information how to configure metadata over SSL
Change-Id: I9ecfc10fed15a73417e840ddecac8a8a56d18601
Closes-Bug: #1739479
ec2api tempest plugin is ready to use for testing the
ec2-api in gate.
This patch moves the 'ec2-api-functional-neutron-full' job
to run test from plugin.
After this we can remove the in-tree ec2-api tempest plugin.
Change-Id: I87698147d644b615f5941db5a6bf4810e9110a58
ec2api tempest plugin[1] is ready to use for testing the
ec2-api in gate.
This patch moves the 'functional-neutron-dsvm-ec2api'
job to run test from plugin.
next patch will use the plugin for other job too if needed
and remove the in-tree tests on successful execution.
.. 1 https://github.com/openstack/ec2api-tempest-plugin
Change-Id: I31b59008f76981b832cb2f7a651858c5c02d494f
This patch moves the zuulv3 jobs for ec2-api repo.
This is first step to switch jobs to ec2 tempest plugin.
There is already gate broken due to switching neutron_vpnaas
to neutron-tempest-plugin whichy stop any further updates to merge
in ec2-api repo.
This commit also fix that.
To make this merge, legacy job needs to be remopved first. Done in below
dependent patch:
Depends-On: I0e5a1c37b407497fd9e60e58bac7c7a89e14dc75
Needed-By: I0c342072f7d749b0243889e2bedd636347df23ef
Change-Id: I9c88ac1ecf0368c9ea7a8b20c84995ea29487184
current version of migration API doesn't allow to
pass several commands to one execute
Depends-On: I9f1f39b30d43dc16a474febcf6549cf1901732ec
Change-Id: I0a74c87c4c782a7a26aa0e67fada994cb3e31434
cinder introduced a new status 'reserved' for volume.
It means that volume has reserved for attaching.
Cause AWS doesn't know such status then we need to convert
it to status 'attaching'.
Change-Id: I84ee29eefc8a9db3982c61820e2cf72a56946132
add argument to call of scenario.configure
use classes for scenarions instead of methods
change client for describe images
Change-Id: I4e53027dcd0cb35b886f97dfe47293be8a322bde