-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Linstor 4.22 shared storagepool support #13910
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
rp-
wants to merge
15
commits into
apache:4.22
Choose a base branch
from
LINBIT:linstor-4.22-shared-storagepool-support
base: 4.22
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
15 commits
Select commit
Hold shift + click to select a range
3154a87
linstor: support shared (thick LVM) storage pools
rp- 5137aed
linstor: update java-linstor to 0.8.1
rp- 6038c26
linstor: use make-available/unmake-available for live migration
rp- 88b40f1
linstor: support snapshots on thick LVM (shared) storage pools
rp- 7229399
linstor: activate inactive resources for snapshot backup and revert
rp- 739bcf6
linstor: return expected device path for inactive shared resources
rp- 901109c
linstor: don't register backup snapshot LVs with dmeventd
rp- 39a2969
linstor: activate inactive template resources for cloning
rp- 85c0423
kvm: connect source volume for copy to secondary storage
rp- 0ae3acd
linstor: pin clone target layer stack to the resource group
rp- 35919fe
linstor: spawn resources with the resource group's layer stack
rp- 7822fe5
linstor: count shared storage only once for capacity
rp- f24f49d
linstor: no over-provisioning for thick storage pools
rp- be4f1ef
linstor: only send auto_manage_dual_primary when migrating
rp- 4150e40
linstor: consider all diskful copies when picking a host
rp- 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
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.
@rp- , this comment is a bit over the top, i think (ai aided?) 3 lines for 1 statement. If the statement really needs explanation it should be renamed I think. or extracted to a method with a clarifying name.