OSDOCS-19126_RN#adding BM RN#111483
Conversation
83d8260 to
e6e2060
Compare
|
🤖 Wed May 13 14:22:51 - Prow CI generated the docs preview: |
4a993f5 to
004db90
Compare
|
@sgoveas @MahnoorAsghar, PTAL |
| Instructions: Add entries in the following format: | ||
|
|
||
| Item description:: | ||
| With this release, the `BareMetalHost` resource now includes the Peripheral Component Interconnect (PCI) address for each network interface controller (NIC) in the `HardwareData` object. An example value for the `pciAddress` field is `0000:00:03.0`. |
There was a problem hiding this comment.
The PCI address info for a NIC may be found in these 2 separate CustomResources:
- in the BMH status.hardware.nics[] section
- in the HardwareData CR, in the spec.hardware.nics[] section
Note: The information in the BMH status.hardware section is the same as the info in the HardwareData spec.hardware, but these are 2 separate CRs.
This statement makes it sound like the HardwareData 'object' is in the BMH status, which is incorrect.
There was a problem hiding this comment.
@MahnoorAsghar, I've updated the draft text. PTAL.
004db90 to
908a84c
Compare
10e4c7f to
a00b28e
Compare
|
@brendan-daly-red-hat: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/lgtm |
|
/label merge-review-needed |
ShaunaDiaz
left a comment
There was a problem hiding this comment.
an extras space in there, but beyond minor
LGTM
| Instructions: Add entries in the following format: | ||
|
|
||
| Item description:: | ||
| With this release, the Peripheral Component Interconnect (PCI) address for each network interface controller (NIC) is available in two separate custom resources (CRs). The PCI address is located in the `status.hardware.nics[]` section of the `BareMetalHost` CR and in the `spec.hardware.nics[]` section of the `HardwareData` CR. While these are separate resources, the values in the `pciAddress` fields, for example `0000:00:03.0`, are identical. |
There was a problem hiding this comment.
| With this release, the Peripheral Component Interconnect (PCI) address for each network interface controller (NIC) is available in two separate custom resources (CRs). The PCI address is located in the `status.hardware.nics[]` section of the `BareMetalHost` CR and in the `spec.hardware.nics[]` section of the `HardwareData` CR. While these are separate resources, the values in the `pciAddress` fields, for example `0000:00:03.0`, are identical. | |
| With this release, the Peripheral Component Interconnect (PCI) address for each network interface controller (NIC) is available in two separate custom resources (CRs). The PCI address is located in the `status.hardware.nics[]` section of the `BareMetalHost` CR and in the `spec.hardware.nics[]` section of the `HardwareData` CR. While these are separate resources, the values in the `pciAddress` fields, for example `0000:00:03.0`, are identical. |
Version:
4.22
Issue:
https://redhat.atlassian.net/browse/OSDOCS-19126
Link to docs preview:
Support for the PCI addresses of NICs in BareMetalHost hardware data
QE review:
Additional information:
Doc PR for this release note: #110891.