-
Notifications
You must be signed in to change notification settings - Fork 5
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
feat(storage/linstor): Enhance multi-disk support and provisioning flexibility in Linstor SR tests #270
Open
rushikeshjadhav
wants to merge
1
commit into
xcp-ng:master
Choose a base branch
from
rushikeshjadhav:feat-storage-linstor
base: master
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
feat(storage/linstor): Enhance multi-disk support and provisioning flexibility in Linstor SR tests #270
Changes from all commits
Commits
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 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 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 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
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.
You use
disks
as a list (which it is) but it only give multiple members when called independently.Meaning
--sr-disk=nvme1n1 --sr-disk=nvme2n1
result in["nvme1n1", "nvme2n1"]
.But a call like
--sr-disk=nvme1n1,nvme2n1
result in["nvme1n1,nvme2n1"]
.We expect the list on the command line to be given in the latter way, you will need to split the member of disks.
You can look at the
hosts
fixture that do the same things with its input.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.
Yes, we can update code and handle disks for
--sr-disk=nvme1n1,nvme2n1
scenario.However, it seemed
sr-disk
is used in other places as well and did not want to break/alter that for compatibility.Also, if we are handling multiple disks in one option then the option will become
--sr-disks
instead of--sr-disk
on same line ashosts
. And this will cause ripple effect at other places.. The current code will gracefully handle both cases, so can I put a different PR for this (--sr-disks
) or you prefer to change in current one?In
jobs.py
,"--sr-disk": "auto"
is used which lets the current code pick multiple available disks and stay intact.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.
It's mostly used in auto, it's just that if we are expected to give multiple disks to a test, using
--sr-disk
with comma separated value make more sense.If we use multiple value, we expect the test to be run multiple time using the values one after the other like it is doing with
--vm
.For this case, we don't have to go further than having comma-separated value working on
sr-disk
for your new fixture and (maybe) ignore the other value after the first disk for the already existing fixtures usingsr-disk
expecting only one disk.For renaming the parameter completely, I'm summoning @Wescoeur and @stormi to give their idea on the matter.
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.
What's the benefit of parsing a comma-separated list, whereas
pytest
already gives us a way to specify--sr-disk=nvme1n1 --sr-disk=nvme2n1
?