Loading...

XML

Word

Printable

Type: Story
Resolution: Done
Priority: Normal
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Story Points:
5
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Epic Link:
Support user input consisting of just InstallConfig and AgentConfig
Feature Link:
OCPPLAN-8150 - Agent-Based Installer GA

Sprint:
Agent Sprint 222

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

Modify the agent-config to accept NMState config for each host.

This could be directly inline, or referenced from a file (either explicitly or by implicitly inferring the filename). ~~This is TBD~~. We decided to go with `AgentConfig embeds install time node-specific configuration` option https://docs.google.com/document/d/1vCy0LikVPhbGIHF494NHTYsfu85fOiOicR3oB1vlEWI/edit#

Using the NMState data provided, generate the equivalent NMStateConfig manifests in cluster-manifests.

depends on

AGENT-136 Create a pseudo-asset to allow an optional dependency on the install-config

Closed

is duplicated by

AGENT-236 Generate nmstateconfig.yaml from agent-config (in create cluster-manifests cli command)

Closed

relates to

AGENT-137 Convert the install-config to ZTP assets

Closed

links to

openshift/installer#6164: AGENT-281: Generate the NMStateConfig manifests from the agent-config

Assignee:: pawan pinjarkar

Reporter:: Zane Bitter

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2022/07/08 4:34 PM

Updated:: 2022/07/29 3:02 PM

Resolved:: 2022/07/29 3:02 PM