Loading...

XML

Word

Printable

Type: Epic
Resolution: Done
Priority: Major
Fix Version/s: openshift-4.11
Affects Version/s: None
Component/s: None
Labels:

Epic Name:
Configure static networking
Blocked:
False
Ready:
False
Epic Status:
Done
Feature Link:
OCPPLAN-8150 - Agent-Based Installer GA
Flagged:

Impediment
Parent Link:
OCPPLAN-8150Agent-Based Installer GA
Hierarchy Progress Bar:

0% To Do, 0% In Progress, 100% Done
Release Note Text:

Hide
With the Agent-based {product-title} Installer, you can configure static IP addresses for IPv4, IPv6, or dual-stack (both IPv4 and IPv6) for all the hosts prior to creating the Agent ISO image. You can add the static addresses to the `hosts` section of the `agent-config.yaml` file or in the `NMStateConfig.yaml` file if you are using the ZTP manifests. Note that the configuration of the addresses must follow the syntax rules for nmstate as described in link:https://nmstate.io/examples.html[NMState state examples].
For more information, see xref:../../installing/installing_with_agent_based_installer/preparing-to-install-with-agent-based-installer.adoc#agent-install-networking_preparing-to-install-with-agent-based-installer[About networking].

Show
With the Agent-based {product-title} Installer, you can configure static IP addresses for IPv4, IPv6, or dual-stack (both IPv4 and IPv6) for all the hosts prior to creating the Agent ISO image. You can add the static addresses to the `hosts` section of the `agent-config.yaml` file or in the `NMStateConfig.yaml` file if you are using the ZTP manifests. Note that the configuration of the addresses must follow the syntax rules for nmstate as described in link: https://nmstate.io/examples.html [NMState state examples]. For more information, see xref:../../installing/installing_with_agent_based_installer/preparing-to-install-with-agent-based-installer.adoc#agent-install-networking_preparing-to-install-with-agent-based-installer[About networking].
Release Note Type:
Feature
Release Note Status:
Done
Target Version:

openshift-4.11

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

Epic Goal

As an OpenShift infrastructure owner, I want to specify static networking inputs to the installer, where hosts can receive their network settings dynamically, in disconnected, on-premises settings.

Why is this important?

Customers want to specify static network configurations, such as Static IPs, VLANs, and NICs bonding when deploying OpenShift in disconnected, on-premises settings (and DHCP servers are not available for security reasons).
Partners need a way to feed in their static network configurations, such as Static IPs, VLANs, and NICs bonding for automated OpenShift deployments in disconnected, on-premises settings (and DHCP servers are not available for security reasons).

Acceptance Criteria

Bonds/LACP/Nic Teaming, VLANs and Static IP must work
CI - MUST be running successfully with tests automated
Release Technical Enablement - Provide necessary release enablement details and documents.

Previous Work (Optional)

Done Checklist

CI - CI is running, tests are automated and merged.
Release Enablement <link to Feature Enablement Presentation>
DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
DEV - Downstream build attached to advisory: <link to errata>
QE - Test plans in Polarion: <link or reference to Polarion>
QE - Automated tests merged: <link or reference to automated tests>
DOC - Downstream documentation merged: <link to meaningful PR>