cinder fix issue mapping device name on Xen hypervisor #1306
Conversation
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
The fix must be refactored into the cinder interface itself
use of parameter to configure the device pattern
Add mappingType parameter to enable support of different device mapping pattern Implemented support for ebs mapping type (where device name is /dev/xvd... but reported as /dev/sd...) and virtio mapping type (taken from Nokia fork)
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request fixed an issue I encountered on the Flexible Engine Cloud provided by Orange (based on Huawei cloud solution). On this cloud when using Xen hypervisors the volumes would be mounted like the EBS volumes: mapping is done with the /dev/xdv[b-z] pattern instead of the /dev/sd[b-z] pattern reported by cinder.
When using KVM hypervisors (virtio) I have taken the change proposed by the nokia fork to retrieve the mount point using the device id.
The behavior of the device resolution name can be controlled with the mappingType parameter which can take the following values: