Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extract device description and filesystem label #1373

Merged
merged 5 commits into from
Mar 8, 2024

Conversation

joseivanlopez
Copy link
Contributor

@joseivanlopez joseivanlopez commented Mar 7, 2024

Problem

The partitioner implements some logic to generate the content of the columns (e.g., for generating the descrition of the device, the label of a file system, etc). Such information is useful for other projects like Agama, but reusing that logic is not possible as it is because it is directly implemented in the partitioner columns (UI stuff).

Solution

Extract the logic for generating useful information to separate classes, making possible to reuse it.

Testing

  • Unit tests adapted.
  • Tested manually

@joseivanlopez joseivanlopez marked this pull request as ready for review March 7, 2024 16:45
@coveralls
Copy link

coveralls commented Mar 7, 2024

Coverage Status

coverage: 97.81%. remained the same
when pulling b67ea7d on joseivanlopez:extract-device-description
into 5707135 on yast:master.

Copy link
Member

@dgdavid dgdavid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

test/y2partitioner/device_description_test.rb Outdated Show resolved Hide resolved
Copy link
Contributor

@ancorgs ancorgs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@joseivanlopez joseivanlopez changed the title Extract device description Extract device description and filesystem label Mar 8, 2024
@joseivanlopez joseivanlopez merged commit b3e7d0d into yast:master Mar 8, 2024
7 checks passed
@yast-bot
Copy link

yast-bot commented Mar 8, 2024

✔️ Internal Jenkins job #1148 successfully finished
✔️ Created OBS submit request #1156335

joseivanlopez added a commit to agama-project/agama that referenced this pull request Mar 8, 2024
## Problem

More information is required to properly represent the storage proposal
result:

* Device description
* Filesystem label

This is a follow-up of #1071.

## Solution

Add new D-Bus interfaces `Device` , `Partition`, `LVM.LogicalVolume` and
adapt `Filesystem` interface.

This changes require yast/yast-storage-ng#1373.

NOTE: This PR goes to a feature branch instead of master.

## Testing

* Added unit tests
* Tested manually
dgdavid added a commit to agama-project/agama that referenced this pull request Mar 19, 2024
As part of the Storage UI changes described at
https://github.com/openSUSE/agama/blob/master/doc/storage_ui.md
document, this PR aims to merge into master the changes already
available in the `storage_ui` feature branch, which has been already
tested and validated. Namely,

* #1071

   Added the following information to D-Bus:

    * The list of actions includes the SID of the affected device.
    * The partition table exports the unused slots.
* The LVM devices (volume groups, physical volumes and logical volumes)
are exported.
* The block devices includes their start block and also indicates
whether the device is encrypted.
    * The staging devices are exported.
    
* #1079 

Adapt the storage client to the changes in the D-Bus API and adapt
`ProposalPage` component to read the information about the devices if
needed.


* #1082

Added new D-Bus interfaces `Device` , `Partition`, `LVM.LogicalVolume`
and adapt `Filesystem` interface.

  It requires yast/yast-storage-ng#1373.

* #1088

Replaced the `Planned Actions` section in the storage proposal for a
`Result` one which presents how the storage would look after
installation instead of just the list of actions.

* #1090

  Moved the space policy configuration to a popup.


* #1098

Replace a `Resize` by `Before` label as it was suggested during the
presentation of the UI in a review meeting.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants