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

librbd: use actual monitor addresses when creating a peer bootstrap token #47835

Merged
merged 1 commit into from
Aug 31, 2022

Conversation

idryomov
Copy link
Contributor

Contribution Guidelines

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
  • jenkins test windows

…oken

Relying on mon_host config option is fragile, as the user may confuse
v1 and v2 addresses, group them incorrectly, etc.  Get mon_host value
only as a fallback.

Fixes: https://tracker.ceph.com/issues/57317
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
Copy link
Contributor

@chrisphoffman chrisphoffman left a comment

Choose a reason for hiding this comment

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

If I understand this patch correctly, if there's no mon addresses already known, use ceph.conf config value. What are the cases where it will fallback?

If one wants to specify specific addresses via ceph.conf is it useful to allow for override to this? Do you anticipate any problems with clusters already relying on mon_host option set explicitly? For example, firewalls, specific eth interfaces for mon etc.

@idryomov
Copy link
Contributor Author

idryomov commented Aug 29, 2022

If I understand this patch correctly, if there's no mon addresses already known, use ceph.conf config value. What are the cases where it will fallback?

Unknown to me... I actually had an assert for mon_addrs != nullptr && !mon_addrs->empty() there but then decided to keep the conf branch as a fallback just in case.

If one wants to specify specific addresses via ceph.conf is it useful to allow for override to this? Do you anticipate any problems with clusters already relying on mon_host option set explicitly? For example, firewalls, specific eth interfaces for mon etc.

They would need to add mirror peers manually with ... peer add on each cluster. ... peer bootstrap create/... peer bootstrap import is intended to be a hands-off solution.

Copy link
Contributor

@trociny trociny left a comment

Choose a reason for hiding this comment

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

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants