openSUSE / agama / 8374097791 / 1 – service
72%
master: 72%

DEFAULT BRANCH: master
Ran
Files 326
Run time 11s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 85.511%. First build
service – 8374097791.1

push

github

web-flow 
[Service] Alternative location for volumes (#1105)

## Problem

The storage proposal allows to specify what to do in order to allocate
any volume:

- Use the default location (new partition or new LV)
- Create it in a given disk as a new partition
- Create it as a new LV in a new dedicated VG on top of a given disk
- Reformat an existing device
- Mount an existing device

Everything is possible, no matter whether the default target is a disk
or a new LVM VG.

So far, it was not possible to use the Agama D-Bus settings to specify
that to the proposal, so all volumes always used the default location.

## Solution

This adds two new attributes to the D-Bus definition of a volume:
`Target` and `TargetDevice`.

Internally, this is represented by a new class `VolumeLocation` with two
attributes:
  - `target`: which specifies how to allocate the volume
- `device`: the name of the target device, the exact meaning depends on
`target`

The new class and the possible targets follow the same approach of
`SpaceSettings` and its policies.

## Testing

- Added several unit tests
- Tested manually by hacking the web UI a bit (see screenshots below)

## Screenshots

Hacking the web UI to set Target to `filesystem` and TargetDevice to
`/dev/vdb5` (which contains a Btrfs file system).


![mount-new](https://github.com/openSUSE/agama/assets/3638289/9a8d83ea-b946-4fe6-b850-3058fdd353ca)

Hacking the web UI to set Target to `new_vg` and TargetDevice to
`/dev/vdc`.


![vg-new](https://github.com/openSUSE/agama/assets/3638289/ed90a87d-ac8e-45d0-85cf-4eff9f62f890)

9620 of 11250 relevant lines covered (85.51%)

17.11 hits per line

Source Files on job service - 8374097791.1