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
>>
>> 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
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
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:
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
>>>
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
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
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
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.
>>
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
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
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
12 matches
Mail list logo