- Drop Cockpit dependency.
- Replace Cockpit login by own solution.
- Check proposed solution with security team.
- Replace Cockpit translation system by own solution.
Agama uses yast2-packager and yast2-pkg-bindings API for selecting patterns/packages and solving dependencies, calling to the libzypp C++ library under the hood.
Sometimes there are conflicts with the selected packages/patterns. In that cases, the zypp resolver fails and reports a list of problems. In that cases, the YaST Packager UI shows the poblems to the user, allowing to select a solution for each problem.
Agama needs something similar to YaST Packager in order to notify and fix the solver problems. This document analyzes how to bring that feature to Agama.
This document analyses different approaches for registering a product and exposes some possible solutions for implementing registration in Agama.
An installer like Agama (or YaST) needs to know any repository from which to get the packages of the product to install.
SUSE repositories are only known after registering a product, but SUSEConnect CLI (i.e., the official tool for registering) cannot register a product unless it is already installed. So, how is the system actually installed by YaST?
Manager
Probe(product)
Software#SelectProduct
Storage#Probe ?
Storage#Calculate
Software#Probe
Storage
Probe
This document proposes a possible solution for defining the new storage settings for Agama. The result is based on this other document, which uses the VolumeTemplate concept for representing the settings of a volume coming from the control file.
The definition of the storage settings in the control file, and its transcription to Agama code by means of the VolumeTemplate approach seem to have some flaws.
One thing to consider is the repetition of fields. A VolumeTemplate and the resulting Volumes created from them have some fields in common. Repetition is not a problem per se, but it does not sound totally correct. Moreover, it seems that a VolumeTemplate is used for several things at the same time:
This document highlights how sudo
and openssh
are configured for (open)SUSE products and points some proposed improvements.
Currently sudo
is configured to always ask for the root password, and this could have some problems:
- The behavior might be unexpected:
sudo
typically asks for the current user password.