XML

Word

Printable

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

Epic Name:
Interactively choose Node0
Work Type:
BU Product Work
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Color Status:
Green
Epic Status:
Done
Feature Link:
OCPSTRAT-1874 - [Dev Preview] Agent-Installer Installation UI for OpenShift Virtualization
Parent Link:
OCPSTRAT-1874[Dev Preview] Agent-Installer Installation UI for OpenShift Virtualization
Hierarchy Progress Bar:

0% To Do, 0% In Progress, 100% Done
Size:
M
Status Summary:

Hide

April 7, 2025 Green

PRs to perform host connectivity checks and disable release image checks are in review. Minor UX update in progress.

March 27, 2025 Green

PR to disable release image checks for disconnected interactive workflow is in review. Finishing up host connectivity checks.

March 19, 2025 Green

Form to enter Rendezvous IP through agent_tui merged. Host connectivity check and disabling release image checks for disconnected interactive workflow is in progress.

March 4, 2025 Green

rendezvous IP form PR submitted and is in review. There will be another iteration to the form to improve UX.

Feb 20, 2025 - Green

Updated agent_tui with form to enter rendezvous node IP. The IP address entered is validated and error dialog is show if it is not valid. Updated agent_tui flow to show rendezvous IP flow only if NODE_ZERO_IP is unset. IP address is saved to file system. Next up is improving the UI to allow user to select a host IP as the rendezvous node IP, adding connectivity check to rendezvous IP, and creating tests to exercise this new interface and flow.

January 29, 2025 - Green

Starting to modify agent_tui to check if rendezvous IP address is in the image. If not, the tui will present a form for the user to enter the IP address.

Show
April 7, 2025 Green PRs to perform host connectivity checks and disable release image checks are in review. Minor UX update in progress. March 27, 2025 Green PR to disable release image checks for disconnected interactive workflow is in review. Finishing up host connectivity checks. March 19, 2025 Green Form to enter Rendezvous IP through agent_tui merged. Host connectivity check and disabling release image checks for disconnected interactive workflow is in progress. March 4, 2025 Green rendezvous IP form PR submitted and is in review. There will be another iteration to the form to improve UX. Feb 20, 2025 - Green Updated agent_tui with form to enter rendezvous node IP. The IP address entered is validated and error dialog is show if it is not valid. Updated agent_tui flow to show rendezvous IP flow only if NODE_ZERO_IP is unset. IP address is saved to file system. Next up is improving the UI to allow user to select a host IP as the rendezvous node IP, adding connectivity check to rendezvous IP, and creating tests to exercise this new interface and flow. January 29, 2025 - Green Starting to modify agent_tui to check if rendezvous IP address is in the image. If not, the tui will present a form for the user to enter the IP address.
Target Version:

openshift-4.19

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

Epic Goal

Allow the user to select a host to be Node 0 interactively after the booting the ISO. On each host the user would be presented with a choice between two options:

Select this host as the rendezvous host (it will become part of the control plane)
The IP address of the rendezvous host is: [Enter IP]

(If the former option is selected, the IP address should be displayed so that it can be entered in the other hosts.)

Why is this important?

Currently, when using DHCP the user must determine which IP address is assigned to at least one of the hosts prior to generating the ISO. (OpenShift requires infinite DHCP leases anyway, so no extra configuration is required but it does mean trying to manually match data with an external system.) ~~AGENT-385~~ would extend a similar problem to static IPs that the user is planning to configure interactively, since in that case we won't have the network config to infer them from. We should permit the user to delay collecting this information until after the hosts are booted and we can discover it for them.

Scenarios

In a DHCP network, the user creates the agent ISO without knowing which IP addresses are assigned to the hosts, then selects one to act as the rendezvous host after booting.

Acceptance Criteria

CI - MUST be running successfully with tests automated
Release Technical Enablement - Provide necessary release enablement details and documents.
...

Dependencies (internal and external)

~~AGENT-7~~

Previous Work (Optional):

Open questions::

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>