Re: F39 Change Proposal: Anaconda WebUI for Fedora Workstation by default (System-Wide)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





Dne 26. 06. 23 v 20:39 Hans de Goede napsal(a):
Hi,

On 6/26/23 18:00, Aoife Moloney wrote:
https://fedoraproject.org/wiki/Changes/AnacondaWebUIforFedoraWorkstation

This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.


== Summary ==
The new PatternFly-based UI has been developed by the Anaconda team
for some time now and we would like to make it available for users of
Fedora to enhance and modernize installation experience. As the first
step in this user adoption process, we are targeting Fedora
Workstation only.
<snip>

This all sounds great, thank you for working on this.

=== Additional information ===
* We are not planning to add support for spins with this change, they
will use the existing GTK UI.
* We don’t support remote connections to the WebUI yet.
Hmm, this really is going to be a problem for low memory machines.

I regularly install Fedora Workstation on 2G (not an issue atm)
and 1G (requires some trickery) RAM systems. I know this is not
a lot of RAM but generally speaking these systems work fine
for non demanding work after the install.

I'm pretty sure that not only the 1G but also the 2G RAM installs,
which currently barely fit in RAM will become a problem with
the new web installers. I was actually hoping the web-installer
would help here since one can then just setup networking in
the live environment and then have the browser showing the UI
run somewhere else, hopefully reducing memory consumption
compared to the gtk installer.

Is there any chance this (remote installs) can at least be
enabled with a commandline option for advanced users?

I realize that making something for remote installs which works
well for average users (and is also somehow using an authenticated
connection) is quite a bit of work.

But in the interim a cmdline option to start listening on
other interfaces then the loopback device (and to not start
the local browser) would be nice to have for power users.

Note related to this ATM:

https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/welcome/Hardware_Overview/

"Minimum System Configuration"

Says 2G is the supported minimum. It would be good to see if
that can actually be made to / kept working.

Has anyone already tested the new installer on a system with its
RAM limited to 2G ?

As said I have some tricks to help with this which currently
allow me to go down to 1G. We should probably look into making
some of those the default on the livecd.

E.g. changing a few things to not run evolution-data-services
on the livecd (no calendering will be configured anyways)
is an easy win of at least 50 MB of RAM.

Regards,

Hans
If you need low memory footprint you probably don't want to use Live image for installation. It's the biggest one because it needs to have whole Gnome environment in memory. For that, I would suggest you to use Fedora Server network installation ISO. It has much smaller memory footprint for installation and still can install workstation system in the Software Selection. The Fedora Server ISO is not part of this change so still GTK UI. If you want even smaller memory footprint then you can run the Server ISO in the text mode by setting 'inst.text' kernel boot parameter in the grub menu.

We did some testing for the memory footprint of the web UI but it was some time ago and I don't remember the results. We can definitely verify it.

To answer your question, remote installations work (probably not great on Live environment). We have 'inst.webui.remote' kernel boot parameter to enable that, however, we decided to not officially support it from a few reasons: - we don't have support for HTTPS connections yet (we are looking on the security aspects of this) - it will not work on Live out of the box because Anaconda is not autostarted there (something needs to start the Anaconda backend). This is the same reason why we don't support VNC installations on Live.

About the improvements on the Live ISO, that should be a question on Fedora Workstation SIG. Anaconda team is not in charge of the environment on the Live ISO.

Best Regards,
Jirka
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux