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 adding a monitor to a deployed cluster #3547
Conversation
19f8f3e
to
1be7ba8
Compare
d084d23
to
a73091e
Compare
|
3a438de
to
3a604d2
Compare
|
cfe2186
to
bdf1bd3
Compare
296e7f8
to
5533f77
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about the containerized equivalent?
@@ -1,4 +1,12 @@ | |||
--- | |||
- name: check if monitor initial keyring already exists | |||
command: ceph auth get-key mon. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
command: ceph auth get-key mon. | |
command: ceph --cluster {{ cluster }} auth get-key mon. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@leseb is ceph-ansible still supporting custom cluster names? (why?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it is, for OSP and for existing clusters too.
Once I get this done for non-containers, I'll focus on containerized equivalent as well. |
cf5c187
to
560f42c
Compare
|
@guits @dsavineau |
jenkins test dev-centos-container-add_mons |
jenkins test dev-centos-non_container-add_mons |
a45a2b3
to
8f2f9fb
Compare
jenkins test dev-centos-non_container-add_mons |
jenkins test dev-centos-container-add_mons |
jenkins test dev-centos-container-all_daemons |
jenkins test dev-centos-non_container-all_daemons |
- initial_mon_key.skipped is defined | ||
- ceph_current_status.fsid is undefined | ||
|
||
- name: debugtask |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
leftover ?
|
||
# add code to read the key or/and try to find it on other nodes | ||
- name: debugtask |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ditto
|
||
# add code to read the key or/and try to find it on other nodes | ||
- name: debugtask | ||
debug: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ditto
When adding a new monitor, we must reuse the existing initial monitor keyring. Otherwise, the new monitor will issue its 'mkfs' with a new monitor keyring and it will result with a mismatch between them. The new monitor will be unable to join the quorum in the end. Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com> Co-authored-by: Rishabh Dave <ridave@redhat.com>
Signed-off-by: Rishabh Dave <ridave@redhat.com>
Add a playbook that deploys a new monitor on a new node, adds that node to the Ceph cluster and the monitor to the quorum and updates the ceph configuration file on OSD nodes. Signed-off-by: Rishabh Dave <ridave@redhat.com>
jenkins test dev-centos-non_container-all_daemons |
jenkins test dev-centos-container-all_daemons |
jenkins test dev-centos-non_container-add_mons |
jenkins test dev-centos-container-add_mons |
This (early) PR aims to add a playbook,
add-mon.yml
, toinfrastructure-playbooks
for adding a monitor to already deployed Ceph cluster.