I'm lately a bit busy to take what we, at the YaST Team, call a
"learning & innovation day". So I decided to write here a brain-dump of
the things I would like to try so others can explore the ideas.
First of all, it would be cool to somehow add to D-Installer the
possibility to trigger an in-browser terminal like the one offered by
Cockpit. When you are using the test ISO you can simply do ctrl+alt+F1.
But wouldn't it be cool to have it better integrated and to be able to
use it even when you are remotely accessing the web interface of
D-Installer (maybe from a tablet or any other system in which you don't
have a capable ssh client)?.
Moreover, that would imply you would be able to use YaST with its
n-curses interface. That should never be needed once D-Installer is
feature complete but... let's say you need to format a DASD device to
then use it during installation. D-Installer does not yet offer DASD
management. Wouldn't be cool to do something like this?
1) Access to D-Installer web interface
2) Open the in-browser terminal
3) Run "yast dasd" there to comfortably manage devices
4) Trigger a device re-scan in D-Installer UI (we don't have such a
button yet, but we will need it sooner than later).
5) Adjust the D-Installer storage settings to install in a fresh DASD.
The only missing parts would be the terminal (which looks easy to
implement using[1] and taking inspiration from Cockpit) and the re-scan
button at storage.
But, why to stop there? ;-) What if we could make it possible to run
YaST modules in a way that is better integrated with D-Installer? I know
it's a much crazier idea that makes little sense but, what if I could
execute the YaST Partitioner in a terminal in a way in which the
resulting staging devicegraph is reflected in the instance of
D-Installer (that is, effectively configuring D-Installer storage setup
from YaST).
Ok, enough. I will go back to work. ;-)
Cheers
[1] https://www.npmjs.com/package/xterm
--
Ancor González Sosa
YaST Team at SUSE Software Solutions
