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
On 12/1/22 13:23, Ancor Gonzalez Sosa wrote:
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).
Having the possibility to run YaST Partitioner / DASD / iSCSI / FcOE within the D-Installer would solve the major issue we currently have: It's not (fully) supported yet. Your approach could give us some more breathing space and the adoption of D-Installer could be smoother. The Partitioner writes states as XML files, they might be used to feed the D-Bus interface with data and D-Installer would just show them? In this way, we could have both Partitioners at the same time. Too simple view :)? Thx Lukas -- Lukas Ocilka, Systems Mgmt & Consulting Team Leader & YaST Product Owner SLE Department, SUSE Linux
Dne 01. 12. 22 v 13:23 Ancor Gonzalez Sosa napsal(a):
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).
Um, for YaST you actually do not need a terminal. Moreover it is really ugly in a web app. :-P We could use the same trick as with the "web" YaST docker image, we could run full YaST in the Xvnc server and in Cockpit (or just the D-Installer) we would just use an <iframe> with URL pointing to that service... That would result in YaST fully integrated into the D-Installer. :-) See https://build.opensuse.org/package/view_file/YaST:Head:Containers/yast-mgmt-... So if you are looking for some ideas for the next HackWeek... ;-) -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8
On 12/19/22 17:17, Ladislav Slezák wrote:
Dne 01. 12. 22 v 13:23 Ancor Gonzalez Sosa napsal(a):
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).
Um, for YaST you actually do not need a terminal. Moreover it is really ugly in a web app. :-P
Maybe it's a matter of taste, but I find uglier to run the Qt UI "embedded" into the web page.
We could use the same trick as with the "web" YaST docker image, we could run full YaST in the Xvnc server and in Cockpit (or just the D-Installer) we would just use an <iframe> with URL pointing to that service...
That would result in YaST fully integrated into the D-Installer. :-)
I personally would find that more alien that a text console. Cheers. -- Ancor González Sosa YaST Team at SUSE Software Solutions
participants (3)
-
Ancor Gonzalez Sosa -
Ladislav Slezák -
Lukas Ocilka