Project

General

Profile

Actions

action #88311

closed

Automate scenario multi-btrfs in interactive installation

Added by JERiveraMoya about 3 years ago. Updated 3 months ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Target version:
-
Start date:
2021-01-28
Due date:
% Done:

0%

Estimated time:
Tags:

Description

As a result of research in #52733 using a default installation, we could do the following in Expert Partitioning:

  • Start with current proposal
  • Add Partitions on vdb: vdb1 with role 'raw' with most of the space and vdb2 with role 'swap'.
  • Add Partitions on vdd: vdd1 with role 'raw' with most of the space and vdd2 with role 'swap'.
  • Edit vdc: select role 'raw' and select encrypt.
  • Select Btrfs multidevice vda2, go to tab Used Devices and Change: add vdb1.
  • Select Btrfs and Add Btrfs with devices vdc and vdd1 and mount /home.
  • Additionally we could check recent feature that displays partitions belonging Btrfs, for example in vda in the table in column type for vda2: "Part of btrfs(vda2..)"
  • Optionally we could change some options like Enable Subvolume Quotas by editing any of the Btrfs multi-devices.
  • Validate the system (lsblk, encryption, btrfs filesystem show /mount point, etc)

Note: the general idea is to minimize number of clicks while exercising the UI related with multi-btrfs and avoid create unnecessary partitions like BIOS Boot Partition for each disk.

Actions #1

Updated by JERiveraMoya about 3 years ago

  • Tracker changed from coordination to action
Actions #2

Updated by JERiveraMoya about 3 years ago

  • Description updated (diff)
Actions #3

Updated by oorlov almost 3 years ago

Let's implement this in scope of SP4, as YaST team is planning to introduce new changes.

Actions #4

Updated by JERiveraMoya almost 3 years ago

  • Target version changed from SLE 15 SP3 to Current
Actions #5

Updated by JERiveraMoya almost 2 years ago

  • Tags set to YaST
  • Priority changed from Normal to Low

We have a lot of test coverage for Expert partitioning comparing with other areas, but we can consider it in the future.

Actions #6

Updated by JERiveraMoya over 1 year ago

  • Target version changed from Current to future
Actions #7

Updated by JERiveraMoya over 1 year ago

  • Target version deleted (future)
Actions #8

Updated by JERiveraMoya 3 months ago

  • Status changed from New to Rejected

Rejecting due for complex UI interaction we should focus in Agama in the near future.

Actions

Also available in: Atom PDF