-
Couldn't load subscription status.
- Fork 0
Description
Is your feature request related to a problem? Please describe.
Process: A measure of success includes, given a similarly trained individual, can they independently follow (or orchestrate) the bootstrap process you have created? Without this, the project has missed the opportunity to reduce the key-person-risk found in these environments
Describe the solution you'd like
Via the server-bootstrap README, I MUST be able to practically realise the litmus test goals of the server bootstrap project. The process MUST use an automated programatic approach and SHOULD NOT rely on many manual steps. The README SHOULD explicity guide the reader on how to practically kick off the automated process, and SHOULD NOT focus only only theoretical details except where theory MAY support the readers understanding.
The README, MAY for example, make reference to a bootstrap program which MUST fail if the required information for bootstrapping is not present or invalid (see additional context).
Describe alternatives you've considered
Additional context
- Reducing margin for human error
- What information, configuration is required, present useful, clear errors and example valid config should config be invalid. (e.g. "
Error: Invalid Config" vs "Error: required key(s) 'lom_password' not found (Str) line 3, column 1, settings.toml See settings.toml.example for valid config example")
- What information, configuration is required, present useful, clear errors and example valid config should config be invalid. (e.g. "
See Litmus test
stateDiagram
Rack_Server --> Cable_Server
state Cable_Server {
[*] --> Public_Network
[*] --> LOM_Network: Management Network
}
Cable_Server --> Power_On
Power_On --> Begin_Redfish_Bootstap
state Begin_Redfish_Bootstap {
Connect_To_LOM --> Establish_VPN_TO_LOM
Establish_VPN_TO_LOM --> Redfish_API_Calls
}
state Redfish_API_Calls {
[*] --> Mount_Virtual_Media
Mount_Virtual_Media --> ...
}