User guide: migrate BMC addressing information from BMO

metal3-io / metal3-docs

Architecture documentation that describes the components being built under Metal³.

http://metal3.io

Apache License 2.0

263 stars 111 forks source link

User guide: migrate BMC addressing information from BMO #428

Closed dtantsur closed 1 month ago

dtantsur commented 1 month ago

Adds a new page "Supported hardware" with information loosely based on the BMO docs with these modifications:

Split one large table into sections based on the underlying technology.
Copy supported Dell firmware versions from OpenShift docs.
Write clarifications on Redfish support status.
Highlight supporting iLO 6.
Highlight which iLO 5 drivers support hardware RAID.

Signed-off-by: Dmitry Tantsur dtantsur@protonmail.com

metal3-io-bot commented 1 month ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lentzi90

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/metal3-io/metal3-docs/blob/main/OWNERS)~~ [lentzi90] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

dtantsur commented 1 month ago

@lentzi90 my thinking was: this information is based on the code in baremetal-operator: both the URL format and the list of available drivers is defined there. So it's sort of a property of BareMetalHost API rather than something Metal3-wide (indeed, Ironic supports more drivers and uses a different format).

lentzi90 commented 1 month ago

That makes sense, but on the other hand it also propagates to CAPM3 since that builds on top of BMO. So CAPM3 won't work with any other hardware either.