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

doc/cephadm: Co-location of daemons #44801

Merged

Conversation

sebastian-philipp
Copy link
Contributor

@sebastian-philipp sebastian-philipp commented Jan 27, 2022

Signed-off-by: Sebastian Wagner sewagner@redhat.com

#39931

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
  • jenkins retest this please
  • jenkins test classic perf
  • jenkins test crimson perf
  • jenkins test signed
  • jenkins test make check
  • jenkins test make check arm64
  • jenkins test submodules
  • jenkins test dashboard
  • jenkins test dashboard cephadm
  • jenkins test api
  • jenkins test docs
  • jenkins render docs
  • jenkins test ceph-volume all
  • jenkins test ceph-volume tox

@anthonyeleven
Copy link
Contributor

anthonyeleven commented Jan 27, 2022

Is count-per-host a new feature for Quincy? I don't know if we have a policy or even convention, but I personally try to note in docs which release functionality is first found, so as to not confuse people running older releases. Granted one can browse former doc releases, but I like to go the extra step.

Signed-off-by: Sebastian Wagner <sewagner@redhat.com>
Copy link
Contributor

@adk3798 adk3798 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Do we also want to mention here that this is how you do upgrade on single host clusters (or maybe link from single host defaults section to here)?

Co-location of daemons
----------------------

Cephadm supports the deployment of multiple daemons on the same host:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Cephadm supports the deployment of multiple daemons on the same host:
Cephadm supports the deployment of multiple daemons from the same service on the same host:

NIT

@anthonyeleven
Copy link
Contributor

LGTM, thanks for adding the note re Pacific.

@sebastian-philipp sebastian-philipp merged commit 39f972a into ceph:master Jan 28, 2022
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants