As of 988243c93fb87190e1867ef913136ecf139e7cb8 in ipxe
"[virtio] Add virtio-net 1.0 support", VMs don't attempt
to boot over the network when using the virtio-net rom.
The ipxe-qemu package used in the grenade jobs contains
this problem. Switch to e1000 to avoid baremetal VMs
working on some hosts and not others.
Change-Id: I4ec297281380896ffe9004c4de7117586ded7149
Story: #2003808
Task: #26603
Downgrade ipxe-qemu during grenade job
Temporary workaround while we find the problem with the
newer ipxe-qemu package.
Task: #26553
Switch grenade job to wsgi
Now that grenade is using Rocky as its base we
can switch to WSGI for ir-api. Also now required
for CI as IRONIC_USE_WSGI was getting flipflopped
from False -> True -> False during the grenade job.
Task: #26594
Disable the ironic-api redirect as it doesn't work with wsgi
Task: #26595
Increase the keystone token timeout, for grenade jobs only
Task: #26596
Story: #2003808
Change-Id: Icc380e6e5128f15f90b3a86cb773e7bb8d60d076
Depends-On: Ib7d68d1360e3cdbfdc2ff185a9760461e75ac8c4
This patch switches ironic API to run under uwsgi,
and drops support for running ironic API under mod_wsgi
from ironic's devstack plugin.
It also effectively moves all jobs except grenade ones to
run ironic-api under UWSGI as we start to honor the devstack's
ENABLE_HTTPD_MOD_WSGI_SERVICES variable (which is True by default).
The new variable in devstack plugin to toggle deployment with uwsgi
is IRONIC_USE_WSGI, which defaults to (now confusingly named)
IRONIC_USE_MOD_WSGI for backward compatibility.
Related-Bug: #1719260
Co-Authored-By: anascko <ovoshchana@mirantis.com>
Change-Id: I9ef3aa48db6efe8e2216af785cc13fdb7f754a02
Instead, use the common_settings file to source all the variables
we need at the early stages of devstack setup and during the upgrade
itself. This also fixes an issue with the networking-generic-switch
upgrade script, which is run from the old release instead of the new
one.
It depends on a patch from an older release, as grenade is setup
using settings from an older release, we need common_setting to be
populated there.
Change-Id: I0d6d3e9e60785bb9b6a10c8c7a07867a5b2a5e6e
Depends-On: I34fb68c150b753824bd2687a1f522ac87771a5e3
The reschedule, that happens in multinode jobs quite often, does not
work with multicell setup. Don't use multicell setup for our Ironic
jobs.
Increase the http timeout for clients in order to work around neutron
issue.
Change-Id: I2bbdac5cd431e72517cb1c72bb925660ec8e868b
Multi-node grenade jobs will fail if we upgrade nova as the minimum
required API for nova to communicate with ironic was upgraded.
Our goal for multi-node grenade is to test rolling upgrades. The
scenario we envision for rolling upgrades to be done is:
1) Upgrade ironic-conductor services one by one. This means old
ironic-api services communicating with new and old
ironic-conductor services. This is what the multi-node grenade job
tests.
2) Upgrade ironic-api services.
3) Upgrade nova
In this upgrade procedure we should not be running updated nova with
old ironic-api services. This patch fixes that.
Closes-Bug: #1706418
Change-Id: I85c607ae7d031e4cabcb505915aca7e88df166aa
We enable plugin and services in project-config.
Drop those duplications from devstack/upgrade/settings
Change-Id: I95d83d6b1f2914cbb0373099e128ab462fc3b492
Depends-On: Icdd89453ec3ebecd8375a5f2efd1a0d4bf6b4064
To support multi-node grenade jobs we need to move enabling of the
ironic devstack plugin out of the ironic grenade settings file
devstack/upgrade/settings. But if we add enabling of the ironic devstack
plugin to project-config it will cause the gate to break as the plugin
will be enabled twice.
This checks to see if the ironic devstack plugin has already been
enabled:
* If it has already been enabled it will not enable it again.
* If it has not yet been enabled it will enable it.
This will allow us to update project-config to enable the ironic
devstack plugin and not break the gate.
After all the changes have landed we will propose a follow-up patch to
remove all this additonal logic and the enabling of the ironic devstack
plugin.
Change-Id: I09ed78ef918eb0359045350e89d42c6df9f3e490
We set global variables in Ironic devstack plugin like
DEFAULT_IMAGE_NAME. Ensure that grenade uses them by
sourcing lib/ironic from upgrade/settings.
Set IRONIC_DEPLOY_DRIVER by default to pxe_ipmitool. As we no longer
add IRONIC_DEPLOY_DRIVER to IRONIC_ENABLED_DRIVERS and defaults are
conflicting.
Closes-Bug: #1663371
Change-Id: I462ac792ad7920beff64c15a7c005406fcfa5cce
This reverts commit cb7d8d7f4e.
We will be running smoke tests anyway after upgrade, no need to do this twice.
Change-Id: I9452e0be44a038b37e2d26ffa32d5d012e9c1bad
tempest is looking for project name in enabled_services to mark service as
enabled in tempest.conf [0]
This patch adds ironic to enabled_services to update value in
tempest.conf
Reference:
[0] 59ed73a3d4/lib/tempest (L500)
Co-Authored-By: John L. Villalovos <john.l.villalovos@intel.com>
Co-Authored-By: Jim Rollenhagen <jim@jimrollenhagen.com>
Change-Id: I525a3816f8b9c71d4ae97afd18c4ddbc2a1aca13
Enable Grenade to run tests for Ironic using the plugin method.
Also provide some documentation on the fact that
openstack-infra/project-config will need to be updated for these changes
to take effect.
Change-Id: I49cf37333c55dbbdbb75737f1c7fd2ecaf983f21
This is a straight copy of the ironic code in grenade's tree to here.
This is necessary to drop ironic code from devstack and complete the
devstack plugin work, as well as just the right thing to do, and will
help us move faster on grenade work.
Note that I'm not sure if this will or will not, and it may make our
grenade jobs explode during the transition. However, our grenade jobs
don't work right now anyway, so nothing of value was lost. :)
Change-Id: I8b065c60e9e06cd7fc10749c49bdf79d878fcc12
ZhongShengping