Skip to content

mon: Validate CRUSH rule for osd pool stretch set#9

Draft
Ericmzhang wants to merge 2 commits into
aainscow:stretchy-Cfrom
Ericmzhang:wip-validate-pool-stretch-set
Draft

mon: Validate CRUSH rule for osd pool stretch set#9
Ericmzhang wants to merge 2 commits into
aainscow:stretchy-Cfrom
Ericmzhang:wip-validate-pool-stretch-set

Conversation

@Ericmzhang
Copy link
Copy Markdown
Collaborator

@Ericmzhang Ericmzhang commented May 19, 2026

Add validation that pools called for osd pool stretch set with different CRUSH rules must be stretched across the same sites (same bucket_count, bucket_target and bucket_barrier)
Update size and min_size parameters for replica pools but not EC.

Signed-off-by: Eric Zhang emzhang@ibm.com

Contribution Guidelines

  • To sign and title your commits, please refer to Submitting Patches to Ceph.

  • If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.

  • When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an x between the brackets: [x]. Spaces and capitalization matter when checking off items this way.

Checklist

  • Tracker (select at least one)
    • References tracker ticket
    • Very recent bug; references commit where it was introduced
    • New feature (ticket optional)
    • Doc update (no ticket needed)
    • Code cleanup (no ticket needed)
  • Component impact
    • Affects Dashboard, opened tracker ticket
    • Affects Orchestrator, opened tracker ticket
    • No impact that needs to be tracked
  • Documentation (select at least one)
    • Updates relevant documentation
    • No doc update is appropriate
  • Tests (select at least one)
Show available Jenkins commands

You must only issue one Jenkins command per-comment. Jenkins does not understand
comments with more than one command.

Add validation for "osd pool stretch set" when using different CRUSH rules, checking that all stretch pools are stretched across the same sites
Ignore size and min_size for EC stretch set

Signed-off-by: Eric Zhang <emzhang@ibm.com>
Add tests for osd stretch set validating different CRUSH rules and changing size for EC pools

Signed-off-by: Eric Zhang <emzhang@ibm.com>
@Ericmzhang Ericmzhang force-pushed the wip-validate-pool-stretch-set branch from f5ba737 to 2fabfa0 Compare May 20, 2026 22:40
@Ericmzhang Ericmzhang changed the base branch from main to stretchy-C May 21, 2026 16:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant