ironic 20.0.0 release

meta:version: 20.0.0
meta:diff-start: -
meta:series: yoga
meta:release-type: release
meta:pypi: no
meta:first: no
meta:release:Author: Iury Gregory Melo Ferreira <iurygregory@gmail.com>
meta:release:Commit: Iury Gregory Melo Ferreira <iurygregory@gmail.com>
meta:release:Change-Id: I3829580bf175d1c6667b3c96e980b835a5477715
meta:release:Code-Review+1: Riccardo Pittau <elfosardo@gmail.com>
meta:release:Code-Review+1: Dmitry Tantsur <dtantsur@protonmail.com>
meta:release:Code-Review+2: Elod Illes <elod.illes@est.tech>
meta:release:Code-Review+2: Hervé Beraud <herveberaud.pro@gmail.com>
meta:release:Workflow+1: Hervé Beraud <herveberaud.pro@gmail.com>

The standalone job changes boot_option in runtime, so local boot
can be used even when the default boot option is netboot.

Change-Id: Ia538907f3662e8cd84d988ea5d862c7f488558e1

Cirros partition images are not compatible with local boot since they
don't ship grub (nor a normal root partition). This change adds a script
that builds a partition image with UEFI artifacts present. It still
cannot be booted in legacy mode, but it's a progress.

Set the tempest plugin's partition_netboot option. We need it to inform
the tempest plugin about the ability to do local boot. This option
already exists but is never set.

Also set the new default_boot_option parameter, which will be introduced
and used in Iaba563a2ecbca029889bc6894b2a7f0754d27b88.

Remove netboot from most of the UEFI jobs.

Change-Id: I15189e7f5928126c6b336b1416ce6408a4950062

Change-Id: I2f7f467afcfd0290d239e90af3daac7ec8fa57a9

We have some backward incompatible changes, so we need a major bump
See [1] for more details

[1] https://zuul.opendev.org/t/openstack/build/e5174d1d8d68491aa01d9a2e3e020a4b/log/tox/list-changes-results.log#1932-1944

Change-Id: Ia3fb13d7f6c29904cf9e1ffe446e3473fdbeecef

Change-Id: I9fe5cd295df33dd3af9bcbdc3fc5f35bd0c6df1b

In the bugfix/19.0 we forgot to update our release_mappaings
This commit adds the missing mapping for 19.0 and also adds the
mapping for 19.1 (our upcoming bugifx branch)

Change-Id: Iffb75a5e6e2412b6e43629ae46f9e98926236b24

At present, the boot interface pxe and irmc-pxe of the iRMC type machine
are based on PXE, not iPXE. Correct the wrong description.

Signed-off-by: Zhou Hao <zhouhao@fujitsu.com>
Change-Id: Idcedc851d75e95222c2c7ce8cb816a1b5a361285

iPXE derives its "file names" from the last component of the URL path.
In case of the conductor's local server it's {mode}_{component} where
mode = deploy/rescue and component = kernel/ramdisk. However, in case
of Swift/Ceph, the last component will be different. This patch accounts
for it.

Change-Id: I7ba5545032069509a9c302abe1c21537ccb5ec8a

Change-Id: I5fa4b9f876be9e4f0276f123d5355cb2299517ec

This is a price to pay for using private API and not having unit tests :)

Change-Id: Ie400a73eb2036678ed9446e0b499301cc2b690dd

Not everyone on the team even knows what pxe_ipmitool used to mean :)
Furthermore, we don't need "ipa" in job names, everything uses IPA
for... even longer than pxe_ipmitool does not exist.

While here, one job was clearly meant to use BIOS boot, but it does not.

Change-Id: I8a37efa0f222361f30ddb7fa621548685a40f961

Change-Id: Ieefdfc0ec287b5fed42f7c7d6d213cbd2f8cd927

The standalone job is failing because of a bug in IPA. To fix it we need
to make DIB jobs operational, and they're failing because of CentOS repos.

Change-Id: I8bd051ea709d328cb5efa2c2cbd5a226bdb4cfd3

Using kernel/ramdisk makes no sense with local boot, we need a better
way. We already have an internal image_type instance parameter, let's
make it public.

Glance support will be added in the next patch.

Change-Id: I4ce5f7a2317d952f976194d2022328f4afbb0258

Other image services cannot have them, not use making a network call.

Change-Id: I691ae5b67358ced5f0aa860b9ca6ccec58c897ad

Change-Id: Ic25eb356d1bc86c1dc4b09df7fc0df42b3821cf3

Noticed we're missing some test coverage in regards to booting from
ramdisks when I was investigating an issue which was reported against
wallaby.

Adds tests which *should* catch the issue I'm chasing in wallaby.

Change-Id: I4965d0cc3966c50fa0485b5e194248dd2072f7a8

Currently, the launcher first notifies systemd, then starts checking the
services (RPC and WSGI). So any failures will be reported, but only
after systemd declares the service ready.

This change adds a polling loop to make sure RpcService.start() finishes
successfully.

Change-Id: Ib460622d69a9cb1cb82e796a6ab294bbbb40c359