Re: [ceph-users] EXT: ceph-lvm - a tool to deploy OSDs from LVM volumes

2017-06-19 Thread Willem Jan Withagen
Op 19-6-2017 om 19:57 schreef Alfredo Deza: On Mon, Jun 19, 2017 at 11:37 AM, Willem Jan Withagen wrote: On 19-6-2017 16:13, Alfredo Deza wrote: On Mon, Jun 19, 2017 at 9:27 AM, John Spray wrote: On Fri, Jun 16, 2017 at 7:23 PM, Alfredo Deza

Re: [ceph-users] EXT: ceph-lvm - a tool to deploy OSDs from LVM volumes

2017-06-19 Thread Andrew Schoen
>> >> I think having one part of Ceph on a different release cycle to the >> rest of Ceph is an even more dramatic thing than having it in a >> separate git repository. >> >> It seems like there is some dissatisfaction with how the Ceph project >> as whole is doing things that is driving you to

Re: [ceph-users] EXT: ceph-lvm - a tool to deploy OSDs from LVM volumes

2017-06-19 Thread Alfredo Deza
On Mon, Jun 19, 2017 at 11:37 AM, Willem Jan Withagen wrote: > On 19-6-2017 16:13, Alfredo Deza wrote: >> On Mon, Jun 19, 2017 at 9:27 AM, John Spray wrote: >>> On Fri, Jun 16, 2017 at 7:23 PM, Alfredo Deza wrote: On Fri, Jun 16, 2017

Re: [ceph-users] EXT: ceph-lvm - a tool to deploy OSDs from LVM volumes

2017-06-19 Thread Alfredo Deza
On Mon, Jun 19, 2017 at 12:55 PM, John Spray wrote: > On Mon, Jun 19, 2017 at 3:13 PM, Alfredo Deza wrote: >> On Mon, Jun 19, 2017 at 9:27 AM, John Spray wrote: >>> On Fri, Jun 16, 2017 at 7:23 PM, Alfredo Deza wrote:

Re: [ceph-users] EXT: ceph-lvm - a tool to deploy OSDs from LVM volumes

2017-06-19 Thread John Spray
On Mon, Jun 19, 2017 at 3:13 PM, Alfredo Deza wrote: > On Mon, Jun 19, 2017 at 9:27 AM, John Spray wrote: >> On Fri, Jun 16, 2017 at 7:23 PM, Alfredo Deza wrote: >>> On Fri, Jun 16, 2017 at 2:11 PM, Warren Wang - ISD >>>

Re: [ceph-users] EXT: ceph-lvm - a tool to deploy OSDs from LVM volumes

2017-06-19 Thread Willem Jan Withagen
On 19-6-2017 16:13, Alfredo Deza wrote: > On Mon, Jun 19, 2017 at 9:27 AM, John Spray wrote: >> On Fri, Jun 16, 2017 at 7:23 PM, Alfredo Deza wrote: >>> On Fri, Jun 16, 2017 at 2:11 PM, Warren Wang - ISD >>> wrote: I would

Re: [ceph-users] EXT: ceph-lvm - a tool to deploy OSDs from LVM volumes

2017-06-19 Thread Alfredo Deza
On Mon, Jun 19, 2017 at 9:27 AM, John Spray wrote: > On Fri, Jun 16, 2017 at 7:23 PM, Alfredo Deza wrote: >> On Fri, Jun 16, 2017 at 2:11 PM, Warren Wang - ISD >> wrote: >>> I would prefer that this is something more generic, to

Re: [ceph-users] EXT: ceph-lvm - a tool to deploy OSDs from LVM volumes

2017-06-19 Thread John Spray
On Fri, Jun 16, 2017 at 7:23 PM, Alfredo Deza wrote: > On Fri, Jun 16, 2017 at 2:11 PM, Warren Wang - ISD > wrote: >> I would prefer that this is something more generic, to possibly support >> other backends one day, like ceph-volume. Creating one tool

Re: [ceph-users] EXT: ceph-lvm - a tool to deploy OSDs from LVM volumes

2017-06-16 Thread Willem Jan Withagen
On 16-6-2017 20:23, Alfredo Deza wrote: > On Fri, Jun 16, 2017 at 2:11 PM, Warren Wang - ISD > wrote: >> I would prefer that this is something more generic, to possibly support >> other backends one day, like ceph-volume. Creating one tool per backend >> seems silly. >>

Re: [ceph-users] EXT: ceph-lvm - a tool to deploy OSDs from LVM volumes

2017-06-16 Thread Sage Weil
On Fri, 16 Jun 2017, Alfredo Deza wrote: > On Fri, Jun 16, 2017 at 2:11 PM, Warren Wang - ISD > wrote: > > I would prefer that this is something more generic, to possibly support > > other backends one day, like ceph-volume. Creating one tool per backend > > seems

Re: [ceph-users] EXT: ceph-lvm - a tool to deploy OSDs from LVM volumes

2017-06-16 Thread Alfredo Deza
On Fri, Jun 16, 2017 at 2:11 PM, Warren Wang - ISD wrote: > I would prefer that this is something more generic, to possibly support other > backends one day, like ceph-volume. Creating one tool per backend seems silly. > > Also, ceph-lvm seems to imply that ceph itself

Re: [ceph-users] EXT: ceph-lvm - a tool to deploy OSDs from LVM volumes

2017-06-16 Thread Warren Wang - ISD
I would prefer that this is something more generic, to possibly support other backends one day, like ceph-volume. Creating one tool per backend seems silly. Also, ceph-lvm seems to imply that ceph itself has something to do with lvm, which it really doesn’t. This is simply to deal with the