Skip to content

Conversation

skopacz1
Copy link
Contributor

@skopacz1 skopacz1 commented Feb 20, 2024

OSDOCS-9736

Version(s): 4.15

QE review:

  • QE has approved this change.

Preview:

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 20, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 20, 2024

@skopacz1: This pull request references OSDOCS-9736 which is a valid jira issue.

In response to this:

OSDOCS-9736

Version(s): 4.15

QE review:

  • QE has approved this change.

Preview:

Instructions 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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Feb 20, 2024
@skopacz1
Copy link
Contributor Author

@mhanss can you PTAL when you have a chance? I'm also not sure whether or not to mention AGENT-704 since the docs for this aren't added to our regular OCP docs, but I can add a section for it if you'd like. Thanks!

@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Feb 20, 2024

🤖 Wed Feb 21 20:21:12 - Prow CI generated the docs preview: https://71931--ocpdocs-pr.netlify.app

@bmanzari
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 21, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 21, 2024

@skopacz1: This pull request references OSDOCS-9736 which is a valid jira issue.

In response to this:

OSDOCS-9736

Version(s): 4.15

QE review:

  • QE has approved this change.

Preview:

Instructions 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 openshift-eng/jira-lifecycle-plugin repository.

@skopacz1
Copy link
Contributor Author

@bmanzari Thanks so much for helping with QE review!!

@skopacz1 skopacz1 changed the title OSDOCS-9736: Agent 4.15 feature RNs OSDOCS#9736: Agent 4.15 feature RNs Feb 21, 2024
@openshift-ci-robot openshift-ci-robot removed the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 21, 2024
@openshift-ci-robot
Copy link

@skopacz1: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to this:

OSDOCS-9736

Version(s): 4.15

QE review:

  • QE has approved this change.

Preview:

Instructions 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 openshift-eng/jira-lifecycle-plugin repository.

@skopacz1
Copy link
Contributor Author

/label peer-review-needed

@openshift-ci openshift-ci bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Feb 21, 2024
@bscott-rh bscott-rh added peer-review-in-progress Signifies that the peer review team is reviewing this PR branch/enterprise-4.15 and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Feb 21, 2024
@bscott-rh bscott-rh added this to the Planned for 4.15 GA milestone Feb 21, 2024
Copy link
Contributor

@bscott-rh bscott-rh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two small nits, otherwise LGTM.

/remove-label peer-review-in-progress
/label peer-review-done

For more information, see xref:../installing/installing_with_agent_based_installer/installation-config-parameters-agent.adoc#installation-configuration-parameters-additional-vsphere_installation-config-parameters-agent[Additional VMware vSphere configuration parameters].

[id="ocp-4-15-agent-baremetal-configuration"]
==== Additional bare metal configurations on Day 1 with the Agent-based Installer
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
==== Additional bare metal configurations on Day 1 with the Agent-based Installer
==== Additional bare metal configurations during Agent-based installation

simplified to avoid "day 1" language

You can now make additional configurations for bare metal platforms while creating the `install-config.yaml` file for an Agent-based Installation.
These new options include host configuration, network configuration, and baseboard management controller (BMC) details.

These fields are not used during the initial provisioning of the cluster, but they eliminate the need to set the fields as a Day 2 operation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
These fields are not used during the initial provisioning of the cluster, but they eliminate the need to set the fields as a Day 2 operation.
These fields are not used during the initial provisioning of the cluster, but they eliminate the need to set the fields after installation.

@openshift-ci openshift-ci bot added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Feb 21, 2024
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 21, 2024
Copy link

openshift-ci bot commented Feb 21, 2024

New changes are detected. LGTM label has been removed.

[id="ocp-4-15-agent-baremetal-configuration"]
==== Additional bare metal configurations during Agent-based installation

You can now make additional configurations for the bare metal platform while creating the `install-config.yaml` file for an Agent-based Installation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change LGTM.

Copy link

openshift-ci bot commented Feb 21, 2024

@skopacz1: all tests passed!

Full PR test history. Your PR dashboard.

Instructions 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/test-infra repository. I understand the commands that are listed here.

@skopacz1
Copy link
Contributor Author

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Feb 21, 2024
@JoeAldinger JoeAldinger added merge-review-in-progress Signifies that the merge review team is reviewing this PR and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Feb 22, 2024
Copy link
Contributor

@JoeAldinger JoeAldinger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

quick question

==== Additional bare metal configurations during Agent-based installation

You can now make additional configurations for the bare metal platform while creating the `install-config.yaml` file for an Agent-based Installation.
These new options include host configuration, network configuration, and baseboard management controller (BMC) details.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Quick question: are host configuration, network configuration, and BMC all fields in a configuration? If so, I think these would need backticks.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question! I meant these terms in a general sense and not to refer to specific fields. And I checked the parameters themselves just now. There is a field for hosts and bmc, but nothing specifically for network.

Since I mean these terms in a general sense and not to refer to any specific fields, can I keep it this way?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it is ok as is. Referring to them as fields in the following sentence makes it seem like you are referring to specific fields if that makes sense? Again, no need to change.

@JoeAldinger JoeAldinger merged commit 429ec60 into openshift:enterprise-4.15 Feb 22, 2024
@skopacz1 skopacz1 deleted the OSDOCS-9736 branch March 11, 2025 17:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.15 merge-review-in-progress Signifies that the merge review team is reviewing this PR peer-review-done Signifies that the peer review team has reviewed this PR size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants