Re: Phasing out replace-brick for data migration in favor of remove-brick.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Amar Tumballi <amarts@xxxxxxxxx>
Subject: Re: Phasing out replace-brick for data migration in favor of remove-brick.
From: Anand Avati <avati@xxxxxxxxxxx>
Date: Mon, 30 Sep 2013 15:13:18 -0700
Cc: gluster-users <Gluster-users@xxxxxxxxxxx>, Gluster Devel <gluster-devel@xxxxxxxxxx>
In-reply-to: <CA+OzEQvX+9eUVPguFN8xuNT_r04qeni7BV_E2OqrRDEB3tBw5A@mail.gmail.com>

On Fri, Sep 27, 2013 at 10:15 AM, Amar Tumballi <amarts@xxxxxxxxx> wrote:

I plan to send out patches to remove all traces of replace-brick data migration code by 3.5 branch time.

Thanks for the initiative, let me know if you need help.

I could use help here, if you have free cycles to pick up this task?

Avati

Follow-Ups:
- Re: Phasing out replace-brick for data migration in favor of remove-brick.
  - From: Amar Tumballi

References:
- Phasing out replace-brick for data migration in favor of remove-brick.
  - From: Anand Avati
- Re: Phasing out replace-brick for data migration in favor of remove-brick.
  - From: Amar Tumballi

Prev by Date: Re: RFC/Review: libgfapi object handle based extensions
Next by Date: Re: RFC/Review: libgfapi object handle based extensions
Previous by thread: Re: [Gluster-users] Phasing out replace-brick for data migration in favor of remove-brick.
Next by thread: Re: Phasing out replace-brick for data migration in favor of remove-brick.
Index(es):
- Date
- Thread

[Index of Archives] [Gluster Users] [Ceph Users] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux