New EBS config parameter for using larger device ranges #996
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 proposed change has been previously discussed on these issues:
/dev/xvd[f-p]
to/dev/xvd[b-c][a-z]
: Support for more device nodes with EBS volumes thecodeteam/libstorage#598I've now rebased the libstorage-specific change to the current REX-Ray
master
, since libstorage will be merged into this project. This change is targeted to the next REX-Ray version, which will be 0.10. Large device range has been introduced as a EBS configuration parameteruseLargeDeviceRange
which isfalse
by default.In order to workaround possible ghost device issues the device namespace is now iterated in a random order. This affects default behaviour as well.
In order to test this change both server and client-side re-configuration is required. Server configuration (in terms of EBS) should look like this:
Client configuration:
Pre-built binary for amd64 architecture is available here: https://github.com/vtorhonen/rexray/releases/tag/v0.10.0-lds
Let me know if there's anything to fix/add.