[Gluster-devel] [Gluster-users] Gluster CLI Feedback

Marcin Dulak marcin.dulak at gmail.com
Wed Oct 11 14:06:53 UTC 2017


Hi,

I have only a feedback to point 4/5.
Despite using
http://docs.ansible.com/ansible/latest/gluster_volume_module.html for
gluster management
I see the operation of replacing a server with a new hardware while keeping
the same IP number poorly documented.
Maybe I was just unlucky in my search for the documentation, but the best
source I found is
https://support.rackspace.com/how-to/recover-from-a-failed-server-in-a-glusterfs-array/

Basically I need to: shut down the old server, perform a clean OS
installation on the new server,
and make the new server to appear disguised as the old peer, while limiting
the bandwidth used by the volume sync.

Cheers,

Marcin


On Wed, Oct 11, 2017 at 11:08 AM, Nithya Balachandran <nbalacha at redhat.com>
wrote:

> Hi,
>
> As part of our initiative to improve Gluster usability, we would like
> feedback on the current Gluster CLI. Gluster 4.0 upstream development is
> currently in progress and it is an ideal time to consider CLI changes.
> Answers to the following would be appreciated:
>
>    1. How often do you use the Gluster CLI? Is it a preferred method to
>    manage Gluster?
>    2. What operations do you commonly perform using the CLI?
>    3. How intuitive/easy to use do you find the CLI ?
>    4. Is the help/information displayed sufficient?
>    5. Are there operations that are difficult to perform?
>
> Regards,
> Nithya
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20171011/3f64eb23/attachment.html>


More information about the Gluster-devel mailing list