action #49823
closed
[sle][functional][y] Implement automated AY installation with bcache
Added by riafarov about 5 years ago.
Updated about 4 years ago.
Target version:
SUSE QA - Milestone 31
Description
Starting with yast2-storage-ng 4.1.21, it's possible to create new bcache devices with the Expert Partitioner. It would be nice to have some test for it.
More information at https://trello.com/c/BnP4shXJ/308-3-fate-325346-create-bcache-devices
https://lizards.opensuse.org/2019/02/27/yast-sprint-71-72/
epic
dev task
QA task
In the attachment we have profile for bcache with encrypted lvm. Setup requires 2 disks.
One contains bios boot partition, /boot and not formatted native linux partition.
Bcache uses not formatted native linux partition as backing device and second disk as a whole as caching device.
bcache is experimental on other archs (AFAIR), so we aim 64bit only.
Acceptance criteria¶
- New test using bcache installation based on attached profile is running for SLES distribution with storage-ng
- Partitionining is validated by the end of installation
- Generation of the profile is also validated for bcache specific parts (partitioning)
- https://gitlab.suse.de/qsf-y/qa-sle-functional-y/ is updated and contains new test suite description
Files
- Copied from action #41876: [sle][functional][y][feature:dev:done][timeboxed:8h] jsc#SLE-3170 fate#325346 YaST2: disk module to support caching / Add bcache through the Partitioner added
- Subject changed from [sle][functional][y] Immplement automated AY installation with bcache to [sle][functional][y] Implement automated AY installation with bcache
I've attached profile on which we can base our test with 2 disks.
Following setup: sda with bios boot, /boot and un-formatted partition (sda3), unpartitioned vda disk
Bcache uses sda3 as backing device and whole vda as backing device.
- Due date set to 2019-07-09
- Target version changed from Milestone 25 to Milestone 26
- Due date changed from 2019-07-09 to 2020-01-28
- Target version changed from Milestone 26 to Milestone 30+
- Target version changed from Milestone 30+ to Milestone 30
bulk moved to M30 for revisiting
- Description updated (diff)
- Due date changed from 2020-01-28 to 2020-02-11
- Target version changed from Milestone 30 to Milestone 31
- Description updated (diff)
- Status changed from New to Workable
- Estimated time set to 8.00 h
- Due date changed from 2020-02-11 to 2020-02-25
- Status changed from Workable to In Progress
- Assignee set to ybonatakis
So far some basic testing have been implemented. The testing doent considering the performance and checks mainly that AY has installed the expected setup and that it actually has cache hits. there are two rotational disks, one with the system + separate /home as backing partition and another disk that is used as caching device. Now the focus is on AC3 that i will try to modify the generate_expressions in autoyast.pm. That will give an extra overhead in the task as i will have to verify that it doesnt break other relative jobs
- Due date changed from 2020-02-25 to 2020-03-10
Let's focus first in the main goal in the task, to have a minimal AutoYaST profile to use and verification of partitioning in bcache and if there is time to do the extra mile to improve cloned profile verification.
- Status changed from In Progress to Feedback
As requested, it would be preferable to set the / as a backing partition but this didnt work so far. With legacy boot, that should require just separate boot partition. I am investigating this as the yast installer can let you continue installation(fresh install) without any warning. In case of re-installation the installation overview shows "Activate flag is not set by installer. if it is not set at all, some BIOSes could refuse to boot". i am planning to continue tomorrow the investigation, but from my side the PR can be merged if there are not objections
Finally, the bcache configured to have the whole operating system as backing device. To do so, we need additional partition for /boot. one partition is needed for stage1 to be able to find grub2 modules at all and the second one is needed as grub2 currently cannot boot bcache directly as it does not have bcache module that understands its structure.
During the manual testing, issues have discovered and filed. one relative to the bcache is that a fresh install doesnt stop you to perform installation without the required /boot partition which winds up with a broken boot as it cant find the grub
- Status changed from Feedback to Resolved
Also available in: Atom
PDF