1a0d1e0f32## Problem - Local DVD cannot be used for installation, offline installation is not possible - We have a [special branch](https://github.com/openSUSE/agama/compare/install_from_2nd_DVD?expand=1) with this feature and build special ISO but I think it should work out of box with upstream Agama - Sooner or later we will need to support installation from the local media anyway ## Solution - A disk label defines the installation repository name for each product - If such disk label is found then that disk is used as the installation repository - If no label is found in the system it uses the online repositories - If multiple labels are found then the DVD device is preferred ## Testing - Tested manually, when the Tumbleweed DVD is present it is automatically used instead of the online repositories - When the product is switched to MicroOS and the DVD is not present it uses the online repositories --------- Co-authored-by: Imobach González Sosa <igonzalezsosa@suse.com>
95 lines
2.7 KiB
Markdown
95 lines
2.7 KiB
Markdown
YAML Config
|
|
-----------
|
|
|
|
Why YAML
|
|
========
|
|
|
|
With our previous experience we discard at the start XML due to its poor readability.
|
|
JSON format we also consider has serious disadvantage - lack of comments.
|
|
So we decide to go with YAML which is still comfortable to read and also machine read.
|
|
Only disadvantage we found is lack of mature schema support for YAML.
|
|
|
|
Rules for Config
|
|
================
|
|
|
|
1. No default values in code. All values have to be defined in yaml config.
|
|
2. No objects, just built-in data types.
|
|
|
|
Structure
|
|
=========
|
|
|
|
Top level config element is map. Each key is described here in following sections.
|
|
|
|
### software
|
|
|
|
Software manager related options. It is map with following keys:
|
|
|
|
#### installation\_repositories
|
|
|
|
Array of url for installation repositories. Map can be used instead of string.
|
|
In such case map should contain url and archs keys. Archs key is used to limit
|
|
usage of repository on matching hardware architectures.
|
|
|
|
#### installation\_labels
|
|
|
|
Array of disk labels used for finding the local installation repository. Instead
|
|
of array of strings it is possible to use an array of maps with `label` and
|
|
`archs` keys where `archs` is a string with comma separated list of supported
|
|
hardware architectures.
|
|
|
|
If the matching disk label is not found then the online installation repository
|
|
from the `installation_repositories` section is used.
|
|
|
|
#### mandatory\_patterns
|
|
|
|
Array of patterns that have to be selected.
|
|
|
|
#### optional\_patterns
|
|
|
|
Array of patterns that should be selected but can be deselected or skipped if not available.
|
|
|
|
#### user\_patterns
|
|
|
|
Array of patterns that are displayed in the pattern selector UI and user can
|
|
select them to install.
|
|
|
|
If the list is empty then the pattern selector is not displayed. If the key is
|
|
not defined or the value is missing or is `null` then all available user visible
|
|
patterns are displayed.
|
|
|
|
### security
|
|
|
|
Options related to security
|
|
|
|
#### lsm
|
|
|
|
Default linux security module. Currently supported values are `selinux`, `apparmor` and `none`.
|
|
|
|
#### available\_lsms
|
|
|
|
Map for available linux security modules. If only one module is
|
|
available it means that lsm is not configurable.
|
|
|
|
##### patterns
|
|
|
|
Required patterns for given lsm to be selected.
|
|
|
|
##### policy
|
|
|
|
Default policy. Only applicable for selinux lsm.
|
|
|
|
|
|
### distributions
|
|
|
|
List of supported distros that can be offered in installer. Archs key is used
|
|
for products that is not available for all hardware architectures.
|
|
|
|
## storage
|
|
|
|
Options related to management of storage devices. It is map with the following keys:
|
|
|
|
### volumes
|
|
|
|
List of volumes used by the proposal. Each volume contains the very same fields described at the
|
|
[corresponding section](https://github.com/yast/yast-installation/blob/master/doc/control-file.md#the-volumes-subsection)
|
|
of the YaST configuration.
|