It was supposed to be made voting shortly after the split, but we
sort of forgot. It provides coverage for things (like ansible deploy)
that we used to have voting jobs for.

Change-Id: Id99586d5e01b940089d55c133d9181db05bfdc7e

The minimum amount of disk space on CI test nodes
may be approximately 60GB on /opt with now only 1GB
of available swap space by default.

This means we're constrained on the number of VMs and
their disk storage capacity in some cases.

Change-Id: Ia6dac22081c92bbccc803f233dd53740f6b48abb

Infra's disk/swap availability has been apparently
reduced with the new focal node sets such that we
have ~60GB of disk space and only 1GB of swap.

If we configure more swap, then naturally that means
we take away from available VMs as well.

And as such, we should be able to complete grenade
with only four instances, I hope.

Change-Id: I36f8fc8130ed914e8a2c2a11c9679144d931ad73

In the devstack plugin, we identify RAX hosts and change the settings
slightly to help ensure CI job passage. This is because the machines are
fully emulated as opposed to paravirtualized which causes a performance
impact with our test VMs that we create. Since we can hit issues
while scheduling on RAX in general, it only makes sense to also
swap the job out for centos based IPA jobs that some how happen on
to a RAX node. Since the CI jobs have largely been "de-typed" name
wise, this should be fine.

Change-Id: I63fc5de05c3975433c12ddd9ba21ebb676de2e6c

IPA will retry any heartbeats anyway, by not retrying on the ironic side,
we 1) make heartbeats quicker, 2) avoid several heartbeats queuing up on
a really busy systems with short heartbeating interval.

Change-Id: If030340a780c759f6433d37b6423d17b72e1a548
Story: #2008167
Task: #40918

Change-Id: I224eca4d8b331711369b17903098daa9fec27d7d
Story: #2008073
Task: #40761

Based on the native 'grenade-multinode' job

Change-Id: I4d0a23c371bc42c5bf18e79ea7920bd77b066154

Negotiation fails for some hardware, let's allow an explicit setting.

Change-Id: I04a3391f85412dcabc6105bd91beb1da25bdfc19

Per discussions with stendulker, the Edgeline servers are not
recognized by proliantutils which means they are not handled
properly and the wrong devices can be set/selected for setting
the next boot device. This is largely because proliantutils
thinks Edgeline hardware is 8th generation instead of 10th
generation hardware.

Since the docs explicitly state Proliant line of rackmount
servers, it seems logical to clarify the Edgeline servers
as it is a different line of servers with a different
market focus.

Change-Id: I75062be1799ea5dd906e675d1b53c10d4f23ce3a

Change-Id: I594323976f9441ad85ad965908901a4b44cfb0b6

We have a check in the code that is never true for manual power
actions because of what happens in the conductor manager. Remove it.

Change-Id: I50b7b78a41188c41e4944894851f1d12684f824a

The docs and releasenotes requirements migrated to doc/requirements.txt
we need not install things from requirements.txt.

Change-Id: I2633cd68b45d27ef3c964216a7d97cd442919101

Change-Id: Id3cc2d1b619790813b94b0cfd52ff6590aff060c

The initial release note for the node object change doesn't
provide full context, and since it has received basic testing
we should be good to go at this point.

Change-Id: Iabb09b7087c400e2d0a278cc3add79bb8b0f3f62

First, use default_boot_mode in get_boot_mode instead of BIOS.

Second, call sync_boot_mode for all ramdisk types in the PXE boot,
not only during deployment.

Change-Id: I3f13bacbdcb319c191eeb8ae93aecf8fba68f9ec

Updates the API ref to include the 'agent_token' value in a
heartbeat request (from IPA). New since v1.62
(9341ca4ef7/ironic/api/controllers/v1/versions.py (L102)).

Change-Id: I5eea9704c1bf62561a5505227735159dad7a8e49

This commit addresses remaining comments on the One Button
Secure Erase clean step patch for iLO5 based Gen10 servers.

Change-Id: I606991b77dfc409a4ab0b966afdbb368fe8c2b54

Accepts the certificate from a heartbeat and stores its path in
driver_internal_info for further usage by the agent client (or
any 3rd party deploy implementations).

Similarly to agent_url, the certificate is protected from further
changes (unless the local copy does not exist) and is removed
on reboot or tear down (unless fast-tracking).

Change-Id: I81b326116e62cd86ad22b533f55d061e5ed53e96
Story: #2007214
Task: #40603

In pxe_utils.py/create_pxe_config function, mac pxe configs will always
be created, so when we clear pxe configs, no matter whether the ip
address is None or not, we need to clear them.

Change-Id: I5cee9c4465630b162baf911ef9efef5f471671c0
Signed-off-by: Armstrong Liu <vpbvmw651078@gmail.com>

As part of the plan to deprecate the iSCSI deploy interface, changing
this option to a value that will work out-of-box for more deployments.

The standalone CI jobs are switched to http as well, the rest of jobs
are left with swift. The explicit indirect jobs are removed.

Change-Id: Idc56a70478dfe65e9b936006a5355d6b96e536e1
Story: #2008114
Task: #40831

Change-Id: Idf85dfd110de6181c6592644fd57e109ba87b971
Story: #2007214
Task: #40822

While validating and downloading image references, allow HttpImageService
to use config parameters to enable/disable TLS verification and to use custom
certificates on the secured connections.

Change-Id: I5f308271004a24203ecbbc1718ba9070ed65b960
Story: #2007939
Task: #40404

This patch adds few of the security dashboard parameters
to iLO capabilities. It adds :
 - overall_security_status
 - last_firmware_scan_result
 - security_override_switch

Story: 2008024
Task: 40678

Change-Id: I7ef2ce1a20fbc1b258fce0f8ebd53661b24e66ff