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

[Mahdi Adnan]

Hi,


  1.  How often do you use the Gluster CLI? Is it a preferred method to manage 
Gluster? It's the only way we manage our volumes.
  2.  What operations do you commonly perform using the CLI? Create, replace, 
set, and healing info.
  3.  How intuitive/easy to use do you find the CLI ? it's easy enough and not 
confusing.
  4.  Is the help/information displayed sufficient? Yes, the help is suffecint 
enough.
  5.  Are there operations that are difficult to perform? no.



--

Respectfully
Mahdi A. Mahdi


From: gluster-users-boun...@gluster.org  on 
behalf of Nithya Balachandran 
Sent: Monday, October 16, 2017 12:57 PM
To: gluster-users
Cc: Gluster Devel
Subject: Re: [Gluster-users] Gluster CLI Feedback

Gentle reminder.

Thanks to those who have already responded.
Nithya

On 11 October 2017 at 14:38, Nithya Balachandran 
mailto:nbala...@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-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-users] Don't allow data loss via add-brick (was Re: Add single server)

[Mahdi Adnan]

I first encountered this bug about a year ago, and lost more than 100 VM.

Sharding is essential to VM datastores and i think Gluster is't that useful 
without this feature for VMs.

I appreciate all the hard work that the developers putting on this bug, but i 
think a warning in CLI or something would be really helpful for Gluster users 
until the fix is ready.


--

Respectfully
Mahdi A. Mahdi


From: gluster-users-boun...@gluster.org  on 
behalf of Joe Julian 
Sent: Monday, May 1, 2017 6:37:00 PM
To: gluster-us...@gluster.org; Gluster Devel
Subject: [Gluster-users] Don't allow data loss via add-brick (was Re: Add 
single server)


On 04/30/2017 01:13 AM, lemonni...@ulrar.net wrote:
>> So I was a little but luck. If I has all the hardware part, probably i
>> would be firesd after causing data loss by using a software marked as stable
> Yes, we lost our data last year to this bug, and it wasn't a test cluster.
> We still hear from it from our clients to this day.
>
>> Is known that this feature is causing data loss and there is no evidence or
>> no warning in official docs.
>>
> I was (I believe) the first one to run into the bug, it happens and I knew it
> was a risk when installing gluster.
> But since then I didn't see any warnings anywhere except here, I agree
> with you that it should be mentionned in big bold letters on the site.
>
> Might even be worth adding a warning directly on the cli when trying to
> add bricks if sharding is enabled, to make sure no-one will destroy a
> whole cluster for a known bug.

I absolutely agree - or, just disable the ability to add-brick with
sharding enabled. Losing data should never be allowed.
___
Gluster-users mailing list
gluster-us...@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel