On Sun, Apr 1, 2018 at 5:32 PM, Willem Jan Withagen <wjw@xxxxxxxxxxx> wrote: > On 01/04/2018 14:06, Alfredo Deza wrote: > >> I closed them because ceph-volume cannot work without systemd. > > > Alfredo, > > I have not yet started looking into ceph-volume due to the full load at > $work. > > But if this dependency on systemd is the 100% the case, than I don't even > have to. FreeBSD does not have it, and with 99,9% certainty will never have. There is currently a dependency on systemd for `ceph-volume lvm activate`, but ceph-volume wasn't created in a way that would mean this is the only way. A lot (most?) of the common parts for preparing, and activating an OSD are placed in places where it can be reused. For other non-systemd units, I would suggest starting to look into creating a plugin that can borrow all the bits and pieces that are "public" in ceph-volume, for example: https://github.com/ceph/ceph/blob/master/src/ceph-volume/ceph_volume/util/prepare.py It shouldn't be hard to wire up a plugin to a different initd system. The way we do it currently is just a single call to `ceph-volume-systemd` which forwards the information needed (OSD ID and FSID) to `ceph-volume systemd`. You can see that the systemd unit is fairly simple: https://github.com/ceph/ceph/blob/master/systemd/ceph-volume%40.service > > So what do you suggest I do from here on, for creating Ceph {mon,osd,...} ?? > > --WjW > > > -- > 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 -- 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
