On Mon, Jul 30, 2018 at 8:01 AM, Alfredo Deza <adeza@xxxxxxxxxx> wrote: > On Mon, Jul 30, 2018 at 4:55 AM, Dan van der Ster <dan@xxxxxxxxxxxxxx> wrote: >> Hi Alfredo, >> >> Why don't we enable the ceph-osd@<id> service during ceph-volume lvm activation? >> >> ceph_volume/devices/lvm/activate.py: >> >> if no_systemd is False: >> # enable the ceph-volume unit for this OSD >> systemctl.enable_volume(osd_id, osd_fsid, 'lvm') >> >> # start the OSD >> systemctl.start_osd(osd_id) >> >> Because of this, the ceph-osd.target doesn't really work on lvm >> activated machines: >> >> # systemctl list-dependencies ceph-osd.target >> ceph-osd.target >> # > > This is not because of the snippet you pasted. We do enable it always > unless the --no-systemd flag is set. > > I think that what you are describing is captured here > http://tracker.ceph.com/issues/24152 which seems like it will need > some sort > of systemd configuration for the unit. Unsure how to make that happen > though, happy to see some ideas >> >> and once we stop osds with `systemctl stop ceph-osd.target`, they can >> no longer be started, i.e. `systemctl start ceph-osd.target` does >> nothing. Sorry about that, I misunderstood the `enable` being for the ceph-volume systemd unit which is always done. You are right, we don't enable the ceph-osd unit, this is a bug >> >> Cheers, Dan -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
