REX-Ray / libStorage Scope fixes #411
Merged
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
This patch should fix some issues with the daemon modules in REX-Ray not getting the correct scope.
akutz
added a commit
to akutz/rexray
that referenced
this pull request
May 10, 2016
REX-Ray 0.4.0 introduces centralized configuration and control along with a new client/server architecture -- features made possible by [libStorage](https://github.com/emccode/libstorage). Users are no longer required to configure storage drivers or store privileged information on all systems running the REX-Ray client. The new client delegates storage-platform related operations to a remote, libStorage-compatible server such as REX-Ray or [Poly](https://github.com/emccode/polly). Please note that the initial release of REX-Ray 0.4 includes support for only the following storage platforms: * ScaleIO * VirtualBox Support for the full compliment of drivers present in earlier versions of REX-Ray will be reintroduced over the course of several, incremental updates, beginning with 0.4.1. NEW FEATURES * Distributed architecture (rexray#399, rexray#401, rexray#411, rexray#417, rexray#418, rexray#419, rexray#420, rexray#423) * Volume locking mechanism (rexray#171) * Volume creation with initial data (rexray#169) ENHANCEMENTS * Improved storage driver logging (rexray#396) * Docker mount path (rexray#403) BUG FIXES * Fixed issue with install script (rexray#409) * Fixed volume ls filter (rexray#400) * Fixed panic during access attempt of offline REX-Ray daemon (rexray#148)
akutz
added a commit
to akutz/rexray
that referenced
this pull request
May 10, 2016
REX-Ray 0.4.0 introduces centralized configuration and control along with a new client/server architecture -- features made possible by libStorage (https://github.com/emccode/libstorage). Users are no longer required to configure storage drivers or store privileged information on all systems running the REX-Ray client. The new client delegates storage-platform related operations to a remote, libStorage-compatible server such as REX-Ray or Poly (https://github.com/emccode/polly). Please note that the initial release of REX-Ray 0.4 includes support for only the following storage platforms: * ScaleIO * VirtualBox Support for the full compliment of drivers present in earlier versions of REX-Ray will be reintroduced over the course of several, incremental updates, beginning with 0.4.1. NEW FEATURES * Distributed architecture (rexray#399, rexray#401, rexray#411, rexray#417, rexray#418, rexray#419, rexray#420, rexray#423) * Volume locking mechanism (rexray#171) * Volume creation with initial data (rexray#169) ENHANCEMENTS * Improved storage driver logging (rexray#396) * Docker mount path (rexray#403) BUG FIXES * Fixed issue with install script (rexray#409) * Fixed volume ls filter (rexray#400) * Fixed panic during access attempt of offline REX-Ray daemon (rexray#148)
akutz
added a commit
to akutz/rexray
that referenced
this pull request
May 10, 2016
REX-Ray 0.4.0 introduces centralized configuration and control along with a new client/server architecture -- features made possible by libStorage (https://github.com/emccode/libstorage). Users are no longer required to configure storage drivers or store privileged information on all systems running the REX-Ray client. The new client delegates storage-platform related operations to a remote, libStorage-compatible server such as REX-Ray or Poly (https://github.com/emccode/polly). Please note that the initial release of REX-Ray 0.4 includes support for only the following storage platforms: * ScaleIO * VirtualBox Support for the full compliment of drivers present in earlier versions of REX-Ray will be reintroduced over the course of several, incremental updates, beginning with 0.4.1. NEW FEATURES * Distributed architecture (rexray#399, rexray#401, rexray#411, rexray#417, rexray#418, rexray#419, rexray#420, rexray#423) * Volume locking mechanism (rexray#171) * Volume creation with initial data (rexray#169) ENHANCEMENTS * Improved storage driver logging (rexray#396) * Docker mount path (rexray#403) BUG FIXES * Fixed issue with install script (rexray#409) * Fixed volume ls filter (rexray#400) * Fixed panic during access attempt of offline REX-Ray daemon (rexray#148)
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 patch should fix some issues with the daemon modules in REX-Ray not getting the correct scope.