In openSUSE they also want their own WebUI installer

After it was announced andAnnouncement of the change to the Anaconda installer web interface used in Fedora and RHEL, the developers of the YaST installer revealed that they too plans to develop the «D-Installer» project and create an interface to manage the installation of openSUSE and SUSE Linux through a web interface.

Unlike the news about the work they started with the Anaconda installer, it should be noted that el project that they disclosed in openSUSE has been developing the WebYaST web interface for a long time.

The main reason why it has not been released to the public despite having already been in development for quite some time is because it is limited by remote administration and system configuration capabilities, it is not designed to be used as an installer, and it is rigidly tied to code. of YaST.

Regarding the plans that were announced about the new installer "D-Installer" this is seen as a platform that provides various installation interfaces (Qt GUI, CLI and Web) in addition to YaST. Associated plans include work to shorten the installation process, separate the user interface from the YaST internals, and add a web interface.

As you may know, YaST is not only a control center for (open) SUSE Linux distributions, but it is also the installer. And, in that sense, we believe that he is a competent installer. However, time passes and YaST is showing its age in some respects.

Technically, D-Installer is an abstraction layer implemented on top of the libraries of YaST and provides a unified interface to access features such as package installation, hardware verification, and disk partitioning over D-Bus.

Console and graphical installers will be migrated to the specified D-Bus API as well as a browser-based installer that interfaces with D-Installer via a proxy service providing access to D-Bus calls via of HTTP.

It is worth mentioning that the development of D-Installer is still in the initial prototype stage. D-Installer and proxies are developed in the Ruby language, in which YaST is written, and the web interface is built in JavaScript using the React framework (the use of Cockpit components is not excluded).

Providing an alternative web-based interface is just the tip of the iceberg. Before we do that, we need to do a lot of internal changes, like decoupling the code from the UI or adding a D-Bus interface.

Fortunately, we have already improved YaST's internals in several vital areas (storage, networking, etc.). However, we are not there yet: much work remains to be done.

While on the part of the benefits it is mentioned that following this approach it is expected that YaST can improve even more. To name a few:

• A better user interface:Reusability: YaST contains a lot of useful logic that would be available to other tools.
• better integration: It should be easier to integrate YaST parts into your own workflows by providing a D-Bus interface.
• Multilanguage: Eventually, using D-Bus could allow us to use other programming languages.

In a few words, the objectives pursued by the D-Installer project are: to eliminate the existing limitations of the graphical interface, to expand the possibilities of using the YaST functionality in other applications, a unified D-Bus interface that simplifies the integration with its own workflows, no longer being tied to one programming language (D-Bus API will allow you to create plugins in different languages), encouraging the creation of alternative configurations by members of the community.

Besides that, the developers hope that more people will contribute to the project making the code more accessible and using widely known technologies.

Finally If you are interested in being able to know more about it about the note, you can check the details in the original post by going to following link