Why does ceph-mon charm have cluster bindings?

Bug #1668901 reported by Sandor Zeestraten on 2017-03-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack ceph-mon charm
Low
Unassigned

Bug Description

According to the Network Space support section in the Readme and the metadata.yaml file, the ceph-mon has support for cluster bindings. But according to the Ceph Network reference[1], Ceph monitors only use the public network space. Is this some leftover stuff from the original ceph charm or am I missing something?

[1] http://docs.ceph.com/docs/master/rados/configuration/network-config-ref/

Dmitrii Shcherbakov (dmitriis) wrote :

This question has occurred to me independently as well. I've looked at the ceph's source code and found no reference for this extra binding to be present, see a description for this PR:

https://review.openstack.org/#/c/477433

James Page (james-page) wrote :

Technically it does not require them; marking 'Triaged' and 'Low' as this has minimal impact.

Changed in charm-ceph-mon:
status: New → Triaged
importance: Undecided → Low
James Page (james-page) wrote :

(this is a hangover from the ceph -> ceph-mon rewrite from a few cycles back).

Change abandoned by Dmitrii Shcherbakov (<email address hidden>) on branch: master
Review: https://review.openstack.org/477433

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers