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

crush: update tunable docs. change default profile to jewel. #7964

Merged
merged 6 commits into from Mar 14, 2016
Merged

crush: update tunable docs. change default profile to jewel. #7964

merged 6 commits into from Mar 14, 2016

Commits on Mar 8, 2016

  1. crush: make default tunables 'firefly' 

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

  2. doc/rados/operations/crush: rewrite crush tunables section 

    - break it down by tunable profile
- explicitly call out the migration impact for each profile jump.

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

  3. mon: warn on straw_calc_version=0 

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

  4. crush: remove straw_calc_version check from has_*_tunables() 

    Since we do not set this when we set tunables, we should not check it
when we report which tunables they have set.  For example, a savvy
operator on firefly tunables should set straw_calc_version to 1 but we
still want the cluster to report that they are on firefly tunables.

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

Commits on Mar 11, 2016

  1. crush: report minimum_required_version when dumping tunables 

    This mimics the feature bit enforcement in OSDMap.cc but it does it based
on the version string.  This is useful when you have CRUSH tunables that
aren't mapped to a named profile.

Signed-off-by: Sage Weil <sage@redhat.com>
    @liewegas
    liewegas committed Mar 11, 2016
    Copy the full SHA
    565d1c7 View commit details
    Browse the repository at this point in the history

  2. mon: make the minimum crush tunables configurable 

    If they cluster is using very old tunables, as inferred by whether it
requires a newer version of CRUSH, issue a health warning.

Signed-off-by: Sage Weil <sage@redhat.com>
    @liewegas
    liewegas committed Mar 11, 2016
    Copy the full SHA
    9e83f5b View commit details
    Browse the repository at this point in the history