On Tue, Apr 2, 2019 at 4:48 PM Thomas Goirand <z...@debian.org> wrote: > > Hi, > > Using ceph-volume is absolutely *NOT* mandatory, this is only a way to > setup your ceph cluster, but that's really not the only one. > > I've been using ceph-osd without it, and the ceph-osd@.service is really > enough, provided that you know how to set it up properly. > > Therefore, this bug is *NOT* of severity grave, because the definition is: > > "makes the package in question unusable by most or all users, > or causes data loss, or introduces a security hole allowing > access to the accounts of users who use the package." > > There's no security hole or data loss, it is just maybe a little harder > to use ceph-osd.
I would argue that an unusable ceph-volume would make Ceph unusable for most users. Running ceph-osd@.service is not enough, since one of the responsibilities of ceph-volume is to ensure that everything is in place for the OSD to start when the system boots, with all the complexity that may involve: encrypted, bluestore or filestore, block/block.db/block.wal, journals, etc... You may be able to run an OSD manually, but that doesn't mean it is the way we would recommend for a stable system. > > It would still be desirable to get this fixed ASAP though, and probably > deserving a fix before Buster is out. > > Cheers, > > Thomas Goirand (zigo) > _______________________________________________ > Ceph-maintainers mailing list > ceph-maintain...@lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-maintainers-ceph.com
