The network configuration UI is required for boot.iso (Server, Fedora ELN) deliverable as there are no Live Environment tools for network configuration.

Based on scoping in INSTALLER=4218 and its outcome in the comment (Analysis document)

GOAL: Create MVP of wired WebUI network configuration with focus on integration. The MVP should be POC of this approach:

• The state (configuration) is stored in NM profiles
• No profile (via Anaconda backend) management at this point (as opposed to Anaconda backend managing profiles for Gtk UI).

Check integration with (need and difficulty of modifications to) current Anaconda backend

• (CI1) Passing the configuration to installed system - this issue
• (CI2) Imposing ONBOOT policies
  • https://issues.redhat.com/browse/INSTALLER-4519 

• Ideally we want to check (as a followup) seamless integration with
  • (CI3) boot options / intiramfs configuration () - requires boot.iso webui for testing
    • https://issues.redhat.com/browse/INSTALLER-4517
    • https://issues.redhat.com/browse/INSTALLER-4518
  • (CI4) kickstart configuration () - requires boot.iso webui + kickstart support in webui
    • TBD very later
• (CI5) Check seamless integration with network configuration tool in Live Environment. (current Gtk UI is turned off there)
  • https://issues.redhat.com/browse/INSTALLER-4520
• (CI6) Check possibility of the current Cockpit UI integration - this issue

Feature requirements:

• The functionality is basic (not the focus), one of or similar to
  • what Cockpit network module supports - doc
  • what Agama network configuration supports - doc
  • Gnome tool seems to be too advanced for MVP

Implementation

• (I1) First stab should be trying to embed cockpit UI Interfaces part.

UX design:

• (UI1) Accessible from each page (not part of wizard flow) as it may be required on multiple steps (for example software selection, storage). Also aligns with current solution (Live Environment toolbar applet). So similar place as Cockpit storage.
• (UI2) Only Interfaces part of the Cockpit network screen is used in Installer 
  • https://issues.redhat.com/browse/INSTALLER-4521 

NON-GOALS

• UI layout usability, user experience refinement. Which is hopefully largely independent of the POC goals.

Acceptance criteria:

• (T1) It is possible to configure and activate/deactivate wired network devices in the installer environment (test exists)
  • https://issues.redhat.com/browse/INSTALLER-4524 
• (T1.1) It is possible to create a configuration without applying it immediately in installer (refer to the Gtk UI)
  • may be followed on in scope of https://issues.redhat.com/browse/INSTALLER-4523 

• (T2) The configuration is passed to installed system and applied after reboot as expected (e2e test exists) - this issue
  • by default everything is passed to the system, may be configurable in future
• (T3) Support for multiple devices (test exists)
  • https://issues.redhat.com/browse/INSTALLER-4522