This will handle corner cases of RAID devices that are a little smaller
than expected (300GB -> 293GB), which were a little outside the 2%
range, while still being close enough.
For preseed installs with pvcbootstrapd, implement "detect" strings,
which can be used instead of fixed block paths to determine the required
disk from a fixed set of information available to a human provisioning
the servers, or from Redfish.
The basic idea is thus:
1. The user specifies some physical attributes of the disk, either
manually in a detect string of the preseed configuration, or by a
physical identifier that Redfish can identify.
2. Redfish takes this and either passes it, or crafts a detect string
itself based on its storage information, which is then passed to the
installer preseed as the target_disk value.
3. The installer uses the provided values along with the output of the
"lsscsi" command to determine which block device to use for the system
disk.
This supersedes and enhances the original "model-based" detection with
far greater reliability and the ability to specify specific indexes.
Prevents having to pick a bunch, which can break if more than one serial
is present for example. Also automates this based on what the installer
has/detects as active.
Converts the option that the preseed file gives into a supplemental
package list by default to avoid accidentally overwriting required
packages.
Also add ipmitool to the supplemental packages list.
1. Remove the respawning and replace with a restart, since it never
worked properly. Also add a "DONE" flag to prevent repeated triggering
during cleanup.
2. Promote the skip_blockcheck to a requested configuration item and a
fully-featured key in the tftp preseed file.
Joshua Boniface