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.

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

crimson/osd: use single-pg peering ops #30372

Merged
merged 3 commits into from Sep 13, 2019

Commits on Sep 13, 2019

  1. crimson/osd: pass octopus to PeeringCtx's constructor

    to accommodate the change of 77ecc32
    
    classic OSD started to use single-pg peering ops since ce05c17, and it
    switched over to these ops since octopus. and it's assumed that
    crimson-osd won't be GA until octopus+2 release, so it's not needed to
    support pre-octopus releases. hence "octopus" is passed to PeeringCtx's
    constructor.
    
    Signed-off-by: Kefu Chai <kchai@redhat.com>
    tchaikov committed Sep 13, 2019
    Copy the full SHA
    5a851c6 View commit details
    Browse the repository at this point in the history
  2. crimson/osd: use single-pg peering ops

    classic OSD started to use single-pg peering ops since ce05c17, and it
    switched over to these ops since octopus. and it's assumed that
    crimson-osd won't be GA until octopus+2 release, so it's not needed to
    support pre-octopus releases.
    
    Signed-off-by: Kefu Chai <kchai@redhat.com>
    tchaikov committed Sep 13, 2019
    Copy the full SHA
    260ab1a View commit details
    Browse the repository at this point in the history
  3. crimson/osd: require_osd_release >= octopus to boot

    we assume that crimson will GA after octopus+2, so no need to be
    compatible with pre-octopus releases.
    
    Signed-off-by: Kefu Chai <kchai@redhat.com>
    tchaikov committed Sep 13, 2019
    Copy the full SHA
    406522d View commit details
    Browse the repository at this point in the history