Re: [ceph-users] ceph-disk is getting removed from master
On Wed, May 30, 2018 at 8:13 AM, Konstantin Shalygin wrote: > On 05/30/2018 07:08 PM, Alfredo Deza wrote: >> >> ceph-volume accepts a bare block device as input, but it will create >> an LV behind the scenes > > > I think this is regression. What if I don't need LV? ceph-volume has always used LVM behind the scenes, this is the default, and there is no other support for creating new OSDs that is not LVM-based. If you don't want LVM, you can continue to use ceph-disk. There is room for developing non-LVM support, but we haven't seen any issues with LVM so far, so there is no incentive to try a different route at this point. > > > > > k ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
Re: [ceph-users] ceph-disk is getting removed from master
On 05/30/2018 07:08 PM, Alfredo Deza wrote: ceph-volume accepts a bare block device as input, but it will create an LV behind the scenes I think this is regression. What if I don't need LV? k ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
Re: [ceph-users] ceph-disk is getting removed from master
On Fri, May 25, 2018 at 3:22 AM, Konstantin Shalygin wrote: > ceph-disk should be considered as "frozen" and deprecated for Mimic, > in favor of ceph-volume. > > > ceph-volume will continue to support bare block device, i.e. without lvm'ish > stuff? Not sure I follow, ceph-volume has two ways of provisioning OSDs, one is by taking over currently deployed OSDs (ceph-disk or manual) and the other one is with LVM. ceph-volume accepts a bare block device as input, but it will create an LV behind the scenes > > > > > > k > > ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
Re: [ceph-users] ceph-disk is getting removed from master
ceph-disk should be considered as "frozen" and deprecated for Mimic, in favor of ceph-volume. ceph-volume will continue to support bare block device, i.e. without lvm'ish stuff? k ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
Re: [ceph-users] ceph-disk is getting removed from master
On Wed, May 23, 2018 at 10:03 AM, Alfredo Dezawrote: > On Wed, May 23, 2018 at 12:12 PM, Vasu Kulkarni wrote: >> Alfredo, >> >> Do we have the migration docs link from ceph-disk deployment to >> ceph-volume? the current docs as i see lacks scenario migration, maybe >> there is another link ? >> http://docs.ceph.com/docs/master/ceph-volume/simple/#ceph-volume-simple >> >> If it doesn't exist can we document, how a) ceph-disk with filestore >> (with/without) journal can migrate to ceph-volume and b) >> ceph-disk/bluestore with wal/db on same/different partitions. > > There is no "scenario" because ceph-volume scans the existing OSD and > whatever that gives us we work with it: > > * filestore with collocated/separate journals > * bluestore in any kind of deployment (with wal, with db, with db and > wal, with main only) > > multiply that with *both* ceph-disk's way of encrypting. > > In short: we support them all. No special command or flag needed. Cool that sounds great. Thanks > > >> >> Regards >> Vasu >> >> >> On Wed, May 23, 2018 at 8:12 AM, Alfredo Deza wrote: >>> Now that Mimic is fully branched out from master, ceph-disk is going >>> to be removed from master so that it is no longer available for the N >>> release (pull request to follow) >>> >>> ceph-disk should be considered as "frozen" and deprecated for Mimic, >>> in favor of ceph-volume. >>> >>> This means that if you are relying on ceph-disk *at all*, you should >>> plan on migrating to ceph-volume for Mimic, and should expect breakage >>> if using/testing it in master. >>> >>> Please refer to the guide to migrate away from ceph-disk [0] >>> >>> Willem, we don't have a way of directly supporting FreeBSD, I've >>> suggested that a plugin would be a good way to consume ceph-volume >>> with whatever FreeBSD needs, alternatively forking ceph-disk could be >>> another option? >>> >>> >>> Thanks >>> >>> >>> [0] http://docs.ceph.com/docs/master/ceph-volume/#migrating >>> ___ >>> ceph-users mailing list >>> ceph-users@lists.ceph.com >>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
Re: [ceph-users] ceph-disk is getting removed from master
On Wed, May 23, 2018 at 11:47 AM, Willem Jan Withagenwrote: > On 23-5-2018 17:12, Alfredo Deza wrote: >> Now that Mimic is fully branched out from master, ceph-disk is going >> to be removed from master so that it is no longer available for the N >> release (pull request to follow) > >> Willem, we don't have a way of directly supporting FreeBSD, I've >> suggested that a plugin would be a good way to consume ceph-volume >> with whatever FreeBSD needs, alternatively forking ceph-disk could be >> another option? > > Yup, I'm aware of my "trouble"/commitment. > > Now that you have riped out most/all of the partitioning stuff there > should not much that one would need to do in ceph-volume other than > accept the filestore directories to format the MON/OSD stuff in. I worry about the way we poke at devices for setups (blkid, lsblk, /proc/mounts, etc...) The creation of the OSD (aside from devices) is straightforward > > IFF I could find the time to dive into ceph-volume. :( > ATM I'm having a hard time keeping up with the changes as it is. > > I'd appreciate if you could delay yanking ceph-disk until we are close > to the nautilus release. At which point feel free to use the axe. We can't delay this for ~8 months because it will obfuscate what breakage we will find on our end by ripping it up (teuthology suites, etc...) I've already started working on it, and we should be looking at 2 to 3 weeks from today. > > --WjW > ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
Re: [ceph-users] ceph-disk is getting removed from master
On Wed, May 23, 2018 at 12:12 PM, Vasu Kulkarniwrote: > Alfredo, > > Do we have the migration docs link from ceph-disk deployment to > ceph-volume? the current docs as i see lacks scenario migration, maybe > there is another link ? > http://docs.ceph.com/docs/master/ceph-volume/simple/#ceph-volume-simple > > If it doesn't exist can we document, how a) ceph-disk with filestore > (with/without) journal can migrate to ceph-volume and b) > ceph-disk/bluestore with wal/db on same/different partitions. There is no "scenario" because ceph-volume scans the existing OSD and whatever that gives us we work with it: * filestore with collocated/separate journals * bluestore in any kind of deployment (with wal, with db, with db and wal, with main only) multiply that with *both* ceph-disk's way of encrypting. In short: we support them all. No special command or flag needed. > > Regards > Vasu > > > On Wed, May 23, 2018 at 8:12 AM, Alfredo Deza wrote: >> Now that Mimic is fully branched out from master, ceph-disk is going >> to be removed from master so that it is no longer available for the N >> release (pull request to follow) >> >> ceph-disk should be considered as "frozen" and deprecated for Mimic, >> in favor of ceph-volume. >> >> This means that if you are relying on ceph-disk *at all*, you should >> plan on migrating to ceph-volume for Mimic, and should expect breakage >> if using/testing it in master. >> >> Please refer to the guide to migrate away from ceph-disk [0] >> >> Willem, we don't have a way of directly supporting FreeBSD, I've >> suggested that a plugin would be a good way to consume ceph-volume >> with whatever FreeBSD needs, alternatively forking ceph-disk could be >> another option? >> >> >> Thanks >> >> >> [0] http://docs.ceph.com/docs/master/ceph-volume/#migrating >> ___ >> ceph-users mailing list >> ceph-users@lists.ceph.com >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
Re: [ceph-users] ceph-disk is getting removed from master
Alfredo, Do we have the migration docs link from ceph-disk deployment to ceph-volume? the current docs as i see lacks scenario migration, maybe there is another link ? http://docs.ceph.com/docs/master/ceph-volume/simple/#ceph-volume-simple If it doesn't exist can we document, how a) ceph-disk with filestore (with/without) journal can migrate to ceph-volume and b) ceph-disk/bluestore with wal/db on same/different partitions. Regards Vasu On Wed, May 23, 2018 at 8:12 AM, Alfredo Dezawrote: > Now that Mimic is fully branched out from master, ceph-disk is going > to be removed from master so that it is no longer available for the N > release (pull request to follow) > > ceph-disk should be considered as "frozen" and deprecated for Mimic, > in favor of ceph-volume. > > This means that if you are relying on ceph-disk *at all*, you should > plan on migrating to ceph-volume for Mimic, and should expect breakage > if using/testing it in master. > > Please refer to the guide to migrate away from ceph-disk [0] > > Willem, we don't have a way of directly supporting FreeBSD, I've > suggested that a plugin would be a good way to consume ceph-volume > with whatever FreeBSD needs, alternatively forking ceph-disk could be > another option? > > > Thanks > > > [0] http://docs.ceph.com/docs/master/ceph-volume/#migrating > ___ > ceph-users mailing list > ceph-users@lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
Re: [ceph-users] ceph-disk is getting removed from master
On 23-5-2018 17:12, Alfredo Deza wrote: > Now that Mimic is fully branched out from master, ceph-disk is going > to be removed from master so that it is no longer available for the N > release (pull request to follow) > Willem, we don't have a way of directly supporting FreeBSD, I've > suggested that a plugin would be a good way to consume ceph-volume > with whatever FreeBSD needs, alternatively forking ceph-disk could be > another option? Yup, I'm aware of my "trouble"/commitment. Now that you have riped out most/all of the partitioning stuff there should not much that one would need to do in ceph-volume other than accept the filestore directories to format the MON/OSD stuff in. IFF I could find the time to dive into ceph-volume. :( ATM I'm having a hard time keeping up with the changes as it is. I'd appreciate if you could delay yanking ceph-disk until we are close to the nautilus release. At which point feel free to use the axe. --WjW ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
[ceph-users] ceph-disk is getting removed from master
Now that Mimic is fully branched out from master, ceph-disk is going to be removed from master so that it is no longer available for the N release (pull request to follow) ceph-disk should be considered as "frozen" and deprecated for Mimic, in favor of ceph-volume. This means that if you are relying on ceph-disk *at all*, you should plan on migrating to ceph-volume for Mimic, and should expect breakage if using/testing it in master. Please refer to the guide to migrate away from ceph-disk [0] Willem, we don't have a way of directly supporting FreeBSD, I've suggested that a plugin would be a good way to consume ceph-volume with whatever FreeBSD needs, alternatively forking ceph-disk could be another option? Thanks [0] http://docs.ceph.com/docs/master/ceph-volume/#migrating ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com