-
Notifications
You must be signed in to change notification settings - Fork 136
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
resilience v2 (1/45): Add support for resilience attributes to pool s…
…election unit and related classes Motivation: In order to enable resilience handling on the basis of storage units, additional properties must be defined. Modification: To the pool group, a simple resilience marker is added. This is necessary for the resilience system to distinguish between pools which are under its control and pools which are not. For storage units, two properties are defined: required = number of non-removable copies needed onlyOneCopyPer = a comma-delimited list of pool tag names used to partition copies among pools in the pool group. These are understood to constitute an "AND" clause for matching. Changes in support of these additional properties are propagated to the selection unit and its commands. In addition, several minor adjustments are necessary to accommodate the extra array slots in the info service handlers. The storage unit has been also turned into a separate class for convenience. Result: The selection unit (pool manager configuration) now supports the definition of resilience on a storage unit basis. NOTES: 1. The storage unit default for 'required' is 1. 2. A storage unit with required=1 can be linked to a pool group with resilience=true without conflicts. 3. A storage unit with required>1 *cannot* be linked to a pool group with resilience=false. This logic currently resides in the pool selection unit decorator logic provided by the resilience system [an upstream patch]; I was undecided whether to incorporate it into the actual V2 implementation layer or not. Target: master Acked-by: Dmitry Acked-by: Gerd
- Loading branch information
alrossi
committed
Feb 10, 2016
1 parent
72ddf8f
commit d1aa11d
Showing
11 changed files
with
317 additions
and
408 deletions.
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
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
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
Oops, something went wrong.