microvm disk support code is messy #351
Labels
No labels
Compat/Breaking
Difficulty/Architectural
Difficulty/Easy
Difficulty/Hard
Help Wanted
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Security
Silenced Alert
Status/Abandoned
Status/Blocked
Status/Need More Info
Status/Postponed
Tracking Issue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
afnix/infra#351
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
MicroVM disk support code has one volume type: zvol with journal, those are a couple of zvols with different block sizes property to accommodate the general purpose VM usecase and have nice performance properties.
The code is very ad-hoc and it's very much desireable to support more volume type, e.g. a Garage should probably have a data volume type with no journal.
We should split off all that code into its own file and rework a bit some of the deep technical debt in a way that separates:
One important thing to watch for is the impedence mismatch between ordering disks and naming disks.
We should perhaps consider to use list everywhere to avoid this problem and rely on module system mechanisms to order things.