Skip to content

OSDOCS#9736: Agent 4.15 feature RNs #71931

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 22, 2024
Merged

OSDOCS#9736: Agent 4.15 feature RNs #71931

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions release_notes/ocp-4-15-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -138,6 +138,21 @@ You can now move etcd from a root volume (Cinder) to a dedicated ephemeral local

//For more information, see < insert link to Deploying OpenStack with rootVolume and etcd on local disk when docs merge>.

[id="ocp-4-15-agent-vsphere-credentials"]
==== Configure vSphere integration with the Agent-based Installer

You can now configure your cluster to use vSphere while creating the `install-config.yaml` file for an Agent-based Installation.
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 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.

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.


These fields are not used during the initial provisioning of the cluster, but they eliminate the need to set the fields after installation.
For more information, see xref:../installing/installing_with_agent_based_installer/installation-config-parameters-agent.adoc#installation-configuration-parameters-additional-bare_installation-config-parameters-agent[Additional bare metal configuration parameters for the Agent-based Installer].

[id="ocp-4.15-postinstallation-configuration"]
=== Postinstallation configuration

Expand Down