This patch starts removing codes related to ipxe support from the pxe interface,
and extract common logic to the PXEBaseMixin.

Story: 2007003
Task: 37779

Change-Id: Ia621f38d9b6c4570ba6a62ddb8c72244ff3fe33b

This change covers changes to meet the goal of establishing contributor
documentation, which Ironic largely already had, but required some
enhancement and clarification.

This also includes rough context of the PTL duties and revision to the
primary repository CONTRIBUTING document, as suggested in some of the
goal related discussions.

Change-Id: Ia47eb56d7eb3c19c99fa7a61fb5605037dd9ebee
Story: #2007236
Task: #38528

There is no longer a common vendor passthru, so the current name
does not make much sense.

Change-Id: I1610e54774826de369be0fef88e98bdf3f64ae1d

On systems in FIPS mode MD5 is not available, just use SHA256.

NOTE: I'm not sure if this changes makes ironic fully operational
      in FIPS mode, merely fixing an immediate issue.

Story: 2007306
Task: 38792

Change-Id: I9a9e0286c88ed5a1a05e405d251b46a4708dd556

This reverts commit e1e89f8831.

The commit was a temporary change to allow us to unblock
the ironic CI gate as we had cross-repository fixes that
needed to land before we would be able to have a passing
and stable ironic-standalone job.

Change-Id: Ib1ed0a35955ab7c53b814048887e725234699d9a

Let's keep standalone non-voting till we can stabilize the
failures on it.

Change-Id: I5c0d23f8cf9f377f013a96bfe30189df25f9c7c5

The `redfish_system_id` property of redfish hardware type has been
made optional. If not specified in `driver_info`, and the target BMC
manages a single ComputerSystem, ironic will assume that system.

Otherwise, ironic will fail requiring explicit `redfish_system_id`
specification in `driver_info`.

Also bumpted sushy dependency to >= 3.1.0.

Change-Id: I425baa7c7294c6c8a707e89df63a17da8e49b666
Story: 2007258
Task: 38619

Let's only run 2 concurrency tempest tests to see if we can
decrease the failure ratio for ironic-standlone job

Change-Id: Ifb6258df26236cf376742a051602321e9b67a52c

This change splits ConductorManager.do_node_deploy into two new
functions: validate_node and start_deploy. The only small behavior
change is validating that an FSM action is possible before making
any changes (previously we did it in the very end, potentiall after
modifying a node).

Change-Id: I635a30264f25d758850fd57c0f07e7a68b332fe3

Change-Id: I10286c48ddf3b7fba020db6175d5faa1c0911141

Currently the DIB element unconditionally clones it.

Change-Id: I096940d6e0801200276f952ae5afc05402f9e473

Change-Id: Ic8b019f9e02d41e128015859423c2e0b7b1562a2

Introduces [console]port_range configuration option and implements
the feature of automatic port allocation for IPMI based serial console.

The ipmi_terminal_port in driver_info takes precedance if specified,
otherwise ironic will allocate free port from configured port range
for underlying serial proxy tools.

The implementation deviation with the original proposal is this patch
doesn't validate whether user specified ipmi_terminal_port falls in the
range, based on following considerations:
a. ipmi_terminal_port is considered a resort for backwards compatibility,
we will remove this eventually.
b. different conductors may have different port range configured (rare,
but could happen).
c. force ipmi_terminal_port in the port range could raise the
possibility of conflicts with ports in the configured range, this is not
a desired result, so leave the choice to the end users.

Change-Id: If8722d09dc74878f4da2e4a7f059d9b079c3e472
Story: 2007099
Task: 38135

The ipxe_enabled configuration option was deprecated for quite a while,
this patch removes it. However the code impact by simply removing the
configuration option is quite large, so the strategy here is to register
the option dynamically but sticks to False, which essentially disabled
the ipxe support in the pxe interface.

Story: 2007003
Task: 37779

Change-Id: I499e627f780b577e351fd39be5fa93a34d384e64

When reno 3.x runs under setuptools, it scans all of the branches it
can find, including any that look like they're closed and have an -eol
tag. The old kilo branch in this repository has a jumbled history that
somehow makes it look like it should include tags that it doesn't. We
know that there are no release notes in that branch, because reno
wasn't adopted while it was open. The releasenotes/source/index.rst
links to separate release notes in the wiki.

This patch tells reno to ignore that branch so that it doesn't throw
an exception when it gets confused about the old tag.

Story: #2007274
Task: #38710

Change-Id: I8047d805b0a3da4051a6d618ed9ac40875b8636a
Signed-off-by: Doug Hellmann <doug@doughellmann.com>

Change-Id: Ie39054aaae1b7092c68e9d22ceecc26ee55bbfbb

Follow up for https://review.opendev.org/#/c/703981/

Change-Id: I020f11844260e8c9b86c93122d229c2edb8ec19e

With more than 4000 lines of code (more than 8000 of unit tests) the
current manager.py is barely manageable. In preparation for the new
deployment API, this change moves the internal cleaning-related
functions to the new cleaning.py.

Change-Id: I13997af2246327bd11b6aaf7029afb20923e64bc
Story: #2006910

With more than 4000 lines of code (more than 8000 of unit tests) the
current manager.py is barely manageable. In preparation for the new
deployment API, this change moves the free-standing deploy-related
functions to utils.py and the new deployments.py.

Change-Id: Ic3f369a7fa72d09263b0670ae78980913b024962
Story: #2006910

Disable the debug output, we don't need 10s of lines to display the RST
file during normal builds.

Change-Id: I3c53ca2591d92e3354efb9da99cf2ee19ea51b7d

It seems, however variables are getting set with grenade
in native zuulv3 jobs, the environment variables are no
longer comparing as they once did in standard bash jobs.

What worked previously, was [ "$VAR" == 'value' ], however
when comparing the newer grenade node jobs we see things like
[[ subnode != \s\u\b\n\o\d\e ]] returning true when single
quotes are used.

Comparison in the logs to where double quotes were used for
functionally the same comparision, revealed proper processing
and execution as expected.

As such, changing our single quotes to double quotes where
applicable.

For the record, I also quickly checked codesearch and it looks
like we were the only project to use single quotes for this
comparison.

Change-Id: I2db2e870e2c5f32aa061af025ee7ce12c4f7c049

Latest release of jsonpatch fixed an issue with array boundaries[1]
but broke tests since JsonPatchConflict is now correctly raised
when a patch tries to replace an item that doesn't exist.
This patch fixes the issue with the tests including
JsonPatchConflict in the json exceptions intercepted by the method
apply_jsonpatch.

[1] b3726f3a8b

Change-Id: I6edf6eb7ae1e9f3aa7bc3220cd943a4849f4997c

When ipxe hardware interface is in use, the node should always be boot
with iPXE disregards the deprecated configuration option [pxe]ipxe_enabled.

Story: 2007003
Task: 37779

Change-Id: Ia658ddc966e13a7ce973eccd9c42e40a3da406f4

Removing a $ sign that shouldn't be there and can cause trouble.

Change-Id: I59a046c06334a3366d0c7070114446efa832df23

This change adds support for node retirement: nodes can
have additional properties 'retired' and 'retired_reason'
which change the way the nodes (can) traverse the FSM
and which operations are allowed. In particular:
- retired nodes cannot move from manageable to available;
- upon instance deletion, retired nodes move to manageable
  (rather than available).

Story: #2005425
Task: #38142

Change-Id: I8113a44c28f62bf83f8e213aeb6704f96055d52b