Adopt Anaconda WebUI in ELN #328
Description
We would like to land the WebUI in the ELN compose soon*, so I would like to discuss the requirements and work items needed for the change.
Note: WebUI change does not have an impact on non-interactive installations. Everything which is possible with the kickstart installation now is going to be fully supported in the kickstart installation after the change. WebUI only impacts the interactive installation experience.
Currently WebUI is used by all Fedora 43 Spins which build Live images, but it is still lacking some features required for the server or minimal installation. As such it is not yet ready to be fully adopted by the Fedora Server or Fedora Everything variants. We expect that we will work on adding those features for the next year or longer. But we would like to have the integration environment already available for us, so that existing features can be regularly tested with the latest state of the ELN.
Once the switch is done Installer team will be able to run its own tests for Fedora ELN on a daily basis.
According to our assessment the two core features missing from the current WebUI setup are
- choice of environments and groups of packages aka "DNF payload feature"
- network configuration screen
We are hoping to deliver the DNF payload within a month.
Networking configuration is going to be more complicated.
Question 1: Do you see other features blocking the adoption of WebUI in the main Fedora ELN compose
Question 2: As networking configuration going to be a large topic, we would like to come up with the as minimal as possible version of it for the initial intergration, and then iterate adding new functionality.
The "most minimal" version could be as simple as - having a text field where the nmstate-compatible yaml-file for the network must be entered.
Would you agree with this approach as a temporary solution until we have a properly implemented UI?
*soon = couple of months, a quarter maybe