ReadinessControl, multiple BMC support for BMC/BIOS Settings/Version CRD

[nagadeesh-nagaraja]

Which component does this relate to?
BMC Settings/Version and partly to BIOS Settings/Version

What is the reason for this feature request or change?

• Provide ability to define the flow of maintenance -> BMCSettings first and then BMCVersion and then BIOSVersion
  • Need: To support onboarding new server, which comes with blank BMC Settings. Hence not being able to perform BMCVersion upgrade without DNS entry to download the firmware.
  • Need: BIOSVersion might have dependency on BMCVersion which might have dependency on others
• Ability to Control the version Upgrade example going from v1.0 to v10.0 might need a hop to v5.0

Describe the feature

• Ability to control the flow of maintenances.
• Ability to define the prerequisite to a maintenance.
• Ability to apply multiple BMCSettings, some version independent (to unblock other tasks like BMCVersion upgrade) and other version dependent (to be applied after the Version upgrade).

Proposed API or behavior changes

bmcsettings-redesign.md

samples:

• New server, which need some default BMCSettings to complete BMCVersion upgrade and then apply version specific BMCSettings: sample_crd
• a Server BMCVersion need to hope multiple Version to reach a version X: sample_crd