README refers to ceph charm, not ceph-mon, is silent on ceph-osd colocation

Bug #1681746 reported by Florian Haas
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ceph Monitor Charm
In Progress
Medium
Chris MacNaughton

Bug Description

The README (apparently copied over from the ceph charm) states that the ceph-mon charm should be deployed like this:

juju deploy -n 3 --config ceph.yaml ceph

This quite obviously needs to be changed to "juju deploy -n 3 --config ceph.yaml ceph-mon", but even then it isn't immediately clear how users should proceed. Can this charm safely be colocated with ceph-osd? Are you supposed to run ceph-mon in a LXD container, and ceph-osd on the same node but outside the container?

James Page (james-page)
Changed in charm-ceph-mon:
status: New → Triaged
importance: Undecided → Medium
Changed in charm-ceph-mon:
assignee: nobody → Chris Holcombe (xfactor973)
status: Triaged → In Progress
Revision history for this message
Chris Holcombe (xfactor973) wrote :

Thanks for catching this Florian. I've put a PR in to update the readme here: https://review.openstack.org/#/c/455846/. If you'd like to jump onto the review I'd appreciate the feedback.

Revision history for this message
Chris MacNaughton (chris.macnaughton) wrote :

I'm not sure why but Gerrit isn't updating this with my new review: https://review.opendev.org/c/openstack/charm-ceph-mon/+/815119

Changed in charm-ceph-mon:
assignee: Chris Holcombe (xfactor973) → Chris MacNaughton (chris.macnaughton)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on charm-ceph-mon (master)

Change abandoned by "James Page <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/charm-ceph-mon/+/815119
Reason: This review is > 12 weeks without comment, and failed testing the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.