Epic Name:
Deploy with datacenter provided network configuration
Blocked:
False
Ready:
False
Color Status:
Green
Epic Status:
Done
Feature Link:
OCPPLAN-8150 - Agent-Based Installer GA
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 deploy to environments where you rely on DHCP to configure networking for all the nodes, as long as you know the IP that at least one of the systems will receive. This IP is required so that all nodes use it as a meeting point. For more information, see
xref:../../installing/installing_with_agent_based_installer/preparing-to-install-with-agent-based-installer.adocl#dhcp[DHCP].

Show
With the Agent-based {product-title} Installer, you can deploy to environments where you rely on DHCP to configure networking for all the nodes, as long as you know the IP that at least one of the systems will receive. This IP is required so that all nodes use it as a meeting point. For more information, see xref:../../installing/installing_with_agent_based_installer/preparing-to-install-with-agent-based-installer.adocl#dhcp[DHCP].
Release Note Type:
Enhancement
Release Note Status:
Done
Target Version:

openshift-4.12

Epic Goal

As an OpenShift deployer, I want to be able to generate the installation image and boot it on the target machines without needing to pre-populate any node network configuration

Why is this important?

Providing the detailed network configuration needed for nmstate is a significant barrier of entry to deploy OpenShift as NMStateConfig, while accessible, doesn't exactly roll off the tongue

I want to boot the baremetal node that will run the assisted service and the nodes that will be worker nodes all at once without needing to care about their IPs/VLANs, etc
I want to make an "AMI" of the tool generated ISO to create my openshift clusters in my no-name cloud and I don't know which IP I am going to get (This scenario will need other work in other epics)

CI - MUST be running successfully with tests automated
Release Technical Enablement - Provide necessary release enablement details and documents.
Deployment completes successfully without providing NMStateConfig for any node.

If we don't know what IP the assisted service is going to get, how do the agents know where to register to? asegurap1@redhat.com node0 agent-config must be provided
If all the ISOs are the same and there's no prior knowledge of the IP configuration for the nodes, how do we decide which is going to run the assisted service? asegurap1@redhat.com the node that finds itself to match node0 config will set itself to be node0.

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>

is blocked by

AGENT-234 Take node0 selection from agent-config if it exists and set it on the ISO

links to