Developers of the Opensuse suggested that you take part in users to take part in Testing the new installer d-staller . Installation images prepared for architectures x86_64 (598MB) and AARCH64/ARM64 (614MB). The proposed unified images allow you to set three platforms: a stable release opensuse leap 15.4 , continuously updated assembly Opensuse TumbleWeed and the editors leap micro 5.2 , built on the basis of isolated containers. In the future, the new installer is planned to be used in products based on the ALP platform (Adaptable Linux Platform), which is being replaced by the distribution of SUSE Linux Enterprise.
The new installer is notable for the user interface department from the internal components of YAST and the possibility of using various frontants, including the front-end installation through the Web Interface. For installation of packages, equipment checking, disks breakdown and other functions necessary during installation, Yast libraries continue to be used, on top of which a layer is implemented that abstracts access to libraries through a unified D-Bus interface.
Among goals D-ICTALLR Development mentions the elimination of existing restrictions on the graphic interface, expanding the possibilities of using the functionality of Yast in other applications, Avoiding one language of programming (D-BUS API will create superstructures in different languages) and stimulating the creation of alternative settings by representatives of the community.
The base interface for managing the installation is built using Web technologies and includes a processor that provides access to the D-BUS calls through the HTTP, and directly the Web interface. The Web interface is written on JavaScript using the framework react and the components patternfly . Service for linking the interface to D-BUS, as well as the built-in HTTP server, written in the Ruby language and built using ready-made modules developed by the project COCKPIT , which are also used in Red Hat Web Configurators.
in new version d-staller implemented multiprocessing architecture, thanks to which the interaction interface with the user is now not blocked During other work on the installer, such as reading metadata from the repository and installing packages. Three internal stages of installation were introduced: starting the installer, setting up installation parameters and installation.