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

ceph-osd: add device class to crush rules (bp #4703) #4743

Merged
merged 5 commits into from Jan 13, 2020

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Nov 14, 2019

This is an automated backport of pull request #4703 done by Mergify.io

@dsavineau
Copy link
Contributor

jenkins test centos-non_container-switch_to_containers

@dsavineau
Copy link
Contributor

@guits you must complete the upgrade and 'ceph osd require-osd-release luminous' before using crush device classes
Wondering if we need to add a when: not rolling_update | bool or execute the crush tasks after the command mentioned above. any thoughts ?

@dsavineau dsavineau force-pushed the mergify/bp/stable-3.2/pr-4703 branch 3 times, most recently from bd2e3dc to 942fe36 Compare November 18, 2019 19:25
If we want to create crush rules with the create-replicated sub command
and device class then we need to have the OSD created before the crush
rules otherwise the device classes won't exist.

Signed-off-by: Dimitri Savineau <dsavinea@redhat.com>
(cherry picked from commit ed36a11)
This adds device class support to crush rules when using the class key
in the rule dict via the create-replicated sub command.
If the class key isn't specified then we use the create-simple sub
command for backward compatibility.

Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1636508

Signed-off-by: Dimitri Savineau <dsavinea@redhat.com>
(cherry picked from commit ef2cb99)
When upgrading from jewel to luminous we can execute the crush rule tasks
only when the 'osd require-osd-release luminous' command.

Signed-off-by: Dimitri Savineau <dsavinea@redhat.com>
When creating crush rules with device class parameter we need to be sure
that all OSDs are up and running because the device class list is
is populated with this information.
This is now enable for all scenario not openstack_config only.

Signed-off-by: Dimitri Savineau <dsavinea@redhat.com>
(cherry picked from commit cf8c6a3)
cf8c6a3 moves the 'wait for all osds' task from openstack_config to the
main tasks list.
But the openstack_config code was executed only on the last OSD node.
We don't need to do this check on all OSD node so we need to add set
run_once to true on that task.

Signed-off-by: Dimitri Savineau <dsavinea@redhat.com>
(cherry picked from commit 5bd1cf4)
@dsavineau
Copy link
Contributor

jenkins test centos-container-update

@dsavineau dsavineau added this to the 3.3z3 milestone Dec 3, 2019
@stale
Copy link

stale bot commented Jan 2, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jan 2, 2020
@guits guits merged commit aea4257 into stable-3.2 Jan 13, 2020
@guits guits deleted the mergify/bp/stable-3.2/pr-4703 branch January 13, 2020 15:54
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.

None yet

2 participants