-
Notifications
You must be signed in to change notification settings - Fork 1.4k
storage: KVM - enable RBD/Ceph volume encryption support #13556
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
Open
calvix
wants to merge
12
commits into
apache:main
Choose a base branch
from
calvix:feature_rbd_encryption
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
a908fd3
storage: enable RBD/Ceph volume encryption support (shared base)
8c692ca
kvm: Ceph-native LUKS2 encryption for RBD volumes (engine='librbd')
e547f86
kvm: gate host encryption probe on librbd support for RBD
864731c
kvm: resize support for librbd-encrypted RBD volumes (#5)
a8de6a7
kvm: route online resize of encrypted RBD through virsh blockresize
3b68ab7
kvm: encrypted RBD root disks (thin CoW clone + full-copy fallback)
fc60197
kvm: harden and align librbd-encrypted RBD volume code
ef726a0
kvm: add RbdEncryption unit tests
a17b777
kvm: refuse encrypted RBD hot-plug on libvirt < 10.1.0
ad357f5
docs: add PendingReleaseNotes entry for librbd-encrypted RBD volumes
a8a9652
kvm: route the encrypted RBD template import through QemuImg
calvix 8c39464
Merge remote-tracking branch 'upstream/main' into feature_rbd_encryption
calvix File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although I do not think this is a huge issue, I think it would be best if we could differentiate the two kinds of encryption support. Maybe we could have a flag that is specific to RBD encryption.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that's a good idea actually. WDYT about this:
host.volume.encryption- same as before, qemu-native LUKS only volumeshost.volume.encryption.rbd- new flag, reports whether the host's rbd CLI supports rbd encryption formatin
DeploymentPlanningManagerImpl.java- checks the flag that matches the volume's pool type - an encrypted volume on RBD pool requires the rbd flag, any other pool type requires the qemu oneOr did you have anything else in mind?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This idea seems ok :)