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

allow crush map bucket definition or don't start OSDs #226

Open
abonillabeeche opened this issue Apr 26, 2017 · 0 comments
Open

allow crush map bucket definition or don't start OSDs #226

abonillabeeche opened this issue Apr 26, 2017 · 0 comments
Labels

Comments

@abonillabeeche
Copy link

If buckets (racks, dc, row, etc) are created post deployment, additional nodes added post-deployment will not have those attributes and the cluster will not re-deploy to a healthy state. Options I see:

  • We need to have a hierarchical system to define placement of hosts, or;
  • When new/additional nodes are added to the storage after the initial deployment, the OSDs should be created BUT not started - this to allow the administrator to move those OSDs/hosts to the correct bucket before starting the OSD processes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants