Skip to content
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.

Sign up for GitHub

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

Jump to bottom

mon: more aggressively convert crush rulesets -> distinct rules #17508

Merged
merged 3 commits into from Sep 19, 2017
Merged

mon: more aggressively convert crush rulesets -> distinct rules #17508

merged 3 commits into from Sep 19, 2017

Commits on Sep 14, 2017

  1. osd: s/crush_ruleset_in_use/crush_rule_in_use/ 

    Signed-off-by: John Spray <john.spray@redhat.com>
    @liewegas
    John Spray authored and liewegas committed Sep 14, 2017
    Copy the full SHA
    675483e View commit details
    Browse the repository at this point in the history

  2. mon: more forceful renumbering of legacy ruleset IDs 

    Previously, the rules were only modified in the trivial case,
so we continued to potentially have CRUSH maps with the
legacy ruleset functionality in use.

In order to ultimately remove rulesets entirely, we need
to do this more aggressively, renumbering all the rules
and then updating any pools as needed.

Signed-off-by: John Spray <john.spray@redhat.com>
    @liewegas
    John Spray authored and liewegas committed Sep 14, 2017
    Copy the full SHA
    71d4b2b View commit details
    Browse the repository at this point in the history

  3. mon/OSDMonitor: improve crush map validation 

    - move into OSDMap method
- ensure that rules exist for each pool
- ensure pool type matches rule type
- ensure rule mask min/max size cover the pool size

Signed-off-by: Sage Weil <sage@redhat.com>
    @liewegas
    liewegas committed Sep 14, 2017
    Copy the full SHA
    8f8f0b2 View commit details
    Browse the repository at this point in the history