As Nova's CI jobs can call the ironic-tempest-dsvm-bfv job,
it seemed to only make sense to keep that job name and have it
leverage the ipxe boot interface instead.
The newer named job, ironic-tempest-dsvm-ipxe-bfv only exists
in the ironic repository according to codesearch.openstack.org.
This removes one un-necessary check in the ironic check gate.
Change-Id: I55bd2e7e5fa5d10ca6ed3093ebabf7dc3be07fb9
This reverts commit e1272cb19b2d8d5fc660f3f81de72058c1b96e13.
This is handled generically now with this change and its dependency:
https://review.openstack.org/#/c/606853/
Change-Id: I8fff93c920bc39202fa12cbff612005cf1339865
A long time ago, in a galaxy not so far away,
the ironic comunity reached consensus that we
should refactor the PXE interface such that we
had separate PXE and iPXE interfaces.
In looking at what it would take for something like
a standalone deployment to have multiarchitecture
support in their environment, it seems even more
urgent and necessary that we begin to make this
delineation. This is because while some ARM iPXE
support exists, the binary is not a commonly
shipped artifiact, so operators are largely
only left with grubaa64.efi as their bootloader.
A similar issue exists with ppc64le deployments
where they must disable iPXE, as the ppc64le
hardware expects reading a syslinux compatible
file, similarlly no iPXE loader exists.
To start this effort, we need to promote iPXE
functionality to a dedicated interface,
and remove the necessity of setting the
[pxe]ipxe_enabled setting.
Next steps, beyond this patch, would be to
begin to tease out the common private method
code in the underlying PXE interface that both
the iPXE and PXE interfaces use, and appropriately
relocate and refactor that code as necesary.
During this process, we can create an [ipxe]
configuration section, and migrate settings.
Finally, once the deprecation cycle is complete,
we will be able to remove the ipxe logic with-in
the PXE interface.
Change-Id: I392616417c48986e84e50a3ddc7567344bfe3571
Story: #1628069
Task: #10516
In order to get openstack/placement installed as part of the
ironic grenade jobs, we have to list it as a required project.
Needed by https://review.openstack.org/604454/
Change-Id: I3922ef15ef8b4517f653a37ca137ba30c8ca5643
These have existed since the jobs were migrated into
this repository (almost a year). They don't currently
work and I don't think they are being worked on, so
remove them to avoind trying to port them to zuulv3
native jobs.
Change-Id: Ied056b91d78b5644ac5d87020325b65af1d86ff4
Small cleanups:
* Use openstack-tox-cover template, this runs the cover job
in the check queue only. Remove individual cover jobs.
* Use openstack-lower-constraints-jobs template, remove individual
jobs.
* Sort list of templates
Change-Id: I36081bfcc9e4cd393110c3fb6027048d57f925ad
This template is only used on older branches and should not have been
imported, remove it again. It should stay in project-config.
Change-Id: Icdaa0f7102074be97e73d4361387084ec4bf5ae1
Currently direct deploy only works if temp urls are enabled or if a
HTTP image URL is given. This patch enables Ironic to serve images
directly from the conductor's HTTP server to the agent so that we can
enable agent deploy with out temp urls.
This also has the added benefit for standalone that the conductors will
cache the HTTP URL images and serve them into the provisioning network
meaning the provisioning network has no need for connectivity to the
outside world.
Story: #1598852
Task: #24639
Co-Authored-By: Kaifeng Wang <kaifeng.w@gmail.com>
Change-Id: Iae6798616f29d876b274d9e0b44a1eb0f24e1747
This is a mechanically generated patch to switch the documentation
jobs to use the new PTI versions of the jobs as part of the
python3-first goal.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: Ie32ae736784a1f2617cbe4a31f8131d2f5e34a60
Story: #2002586
Task: #24302
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: I66427df9182973328fa13b29dd580b67814baf8b
Story: #2002586
Task: #24302
Switch ironic-tempest-dsvm-ipa-partition-pxe_ipmitool-tinyipa-python3
to zuulv3 native.
Also ensure phygmi and virtualbmc are always installed with python2
as pyghmi is still not compatible with python3.
Depends-On: I413ea7ec5db3316f985c38900aa46b8cdfd5d138
Change-Id: I11ad26c354bcbc2a0ed8e2bc78c9403dbcf85326
These lists are not merged with their parent, so need to
be complete. The list for the legacy standalone job was
slightly different to the others.
Change-Id: I15ada31e78697f6f4403fef09d5d261fd9fd337f
The new CI DSVM wrappers with zuul lack passing
a BUILD_TIMEOUT, thus the default value of 196
seconds is taking effect in devstack.
Explicitly setting to 600 should improve CI reliability.
Change-Id: If39f33d4f5e8e649729ecc9e5be33f9529d7b488
Sets rescue interface to 'agent' for testing rescue mode in most jobs.
The rescue mode is tested in test_baremetal_server_ops.
Also adds support for the new config option in ironic tempest plugin
default_rescue_interface.
Story: #1526449
Depends-On: I6b62724711ddbe17b59dad30283e544272d9c1f3
Change-Id: Ica26aa96978d22a681d69e7e1e4acd72182a4981
Move ironic-dsvm-standalone away from using the legacy
format converted fromt the project-config repository.
Also enables 3 more tempest jobs(BaremetalAgentIpmitool*)
that were being skipped as agent_ipmitool wasn't configured.
Change-Id: Ic01bf1849620c6d095f130e445c92888548d00c5
It becomes increasingly harder to maintain functional tests using the fake
hardware type and integration tests in the same jobs. This change creates
two new jobs (for Python 2 and Python 3) and makes API tests run only in them.
Change-Id: I3570323b22d8d4f19635f26733b3ae92bd0c661d
The dsvm jobs were not being run if only test-requirements.txt was
modified. However, devstack installs test-requirements so we should
run those jobs if that file changes.
The grenade multinode jobs were not being run if requirements.txt
was modified -- this was due to an extra '|' which caused it to be
considered an irrelevant file :-(
Change-Id: I1a49915ca52a93e77849dc5ead655656ad1bb34e
Create a tox environment for running the unit tests against the lower
bounds of the dependencies.
Create a lower-constraints.txt to be used to enforce the lower bounds
in those tests.
Add openstack-tox-lower-constraints job to the zuul configuration.
See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html
for more details.
Change-Id: I50af6344c8de6fae3602e6d0f5267623ce492dc9
Depends-On: https://review.openstack.org/555034
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This job installs ansible from the driver-requirements.txt file, but we
aren't running the job on changes to this file. Override
irrelevant-files for this job to ensure updates to the ansible
dependency are tested.
Change-Id: I7fca8123ecffe24087db25aff4cd9c41560cf2be
The multinode, multitenant grenade job seems healthy again, lets
have it vote in gate as well as in check.
This is a follow up to Iab5fc999fcfa427549192ec73bd076a588f37e20.
Change-Id: Ib3d8c3cf1c906c6e958650ad7b1a1942e5d9a9c3
There isn't a need to run non-voting jobs in gate, as it ends up just
wasting CI resources. Results can be obtained from the check pipeline
results.
Comment out job, over running as non-voting.
Change-Id: I02e9dcafdb6e91451f630bb78be702009726a1ea
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
The job scripts are purged of shell conditions that are never true
and variables that no longer have effect.
The resourceclasses job is removed completely, as all jobs now run
with resource classes.
Change-Id: I66a5e4f5f7214bcf9aeab8ee8d46a323610ff333
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: Iff03f999769671adafdb46b22c64e80708d62d0e
As the mutlinode job is failing and is failing
in ways that cannot currently be easily and cleanly
rectified, we should disable voting for the job until
we are able to fully identify the cause and proper
solution in order to allow the project contributors
to continue to land code and have it reviewed while
we work to resolve the multinode grenade job issues.
Change-Id: If204c7b979baa71b3b9bbb7e79d13741f580ba8b
Related-Bug: #1744139
This seems to run quite reliably, and making it voting is required
for the openstack-wide python 3 goal.
Change-Id: If885612c4c07c06c9e7846536c55e8c92fca50eb
All the 'post.yaml' files are identical. Put them in the two parent
jobs so we only have two copies instead of ~14 copies.
Change-Id: Ic8e519d597ec8423ad1040b4f4671fae0662f2db
Follow-on patch will delete the
openstack/ironic/ironic_tempest_plugin/ directory. But this will need
to be done after this patch has been backported to the stable
branches, otherwise the stable branches will break.
Change-Id: I31bb088679ea122efaa91d362e613edb74c14254
We inherit from legacy-dsvm-base. Remove projects that have already
been required by legacy-dsvm-base.
Also sort the list of required projects.
Change-Id: I4c0b88858ce620dd46c83f40d8623eb3d46bb908