On 05. 06. 24 10:05, Richard W.M. Jones wrote:
On Tue, Jun 04, 2024 at 12:08:45PM -0500, Jason L Tibbitts III wrote:
Jiri Konecny <jkonecny@xxxxxxxxxx> writes:
Hi, the only change should be that you will change "vnc --connect"
with the new API we will provide and also use RDP as your client
instead of VNC.
Thanks. I don't particularly care about VNC itself; I just wanted to
make sure that it was known that someone does use "--connect" to do a
"client-initiated" display connection.
Off topic, I know, but what I really wish existed was some kind of
deployment console. Early in the kickstart process, the machine being
installed would contact a server, pass hardware info and wait. The
server would pass back the rest of the kickstart file (after potentially
getting admin input) and the installation would continue. Output would
be logged in a way that the server can present to the admin, and
potentially the graphical (or perhaps the text) UI could be passed
through.
This is similar to what The Foreman does I think?
https://www.theforeman.org/introduction.html
There are various other things in the same world such as:
https://docs.openstack.org/ironic/latest/
Rich.
IIRC Foreman is doing this by not optimal way currently and they asked
us some time ago about using %pre section as you said. Not sure what
happened then.
Anyway, the pre section should be fine to use for this in Anaconda.
Also a question, is kickstart command for RDP requirement for you? Or is
inst.rdp (replacement of inst.vnc) enough to work with?
We are trying to find out if we can drop the kickstart command.
Best Regards,
Jirka
Years ago I had hacked something implementing a little of this which
just worked in %pre but it ended up being less useful than the system I
use now. And really, I don't think that deployments like mine (maybe a
couple hundred machines) are very common so there's probably no point.
But it's an interesting problem to think about.
- J<
--
_______________________________________________
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
--
_______________________________________________
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
