[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gluster-devel] [Gluster-users] FeedBack Requested : Changes to CLI
From: |
Kaushal M |
Subject: |
Re: [Gluster-devel] [Gluster-users] FeedBack Requested : Changes to CLI output of 'peer status' |
Date: |
Tue, 28 Aug 2012 20:01:33 +0530 |
Bryan,
FYI XML output for 'peer status' isn't yet present in 3.3.0. It was
just pushed into master. So if you want to test it, you'll have to
build from master
- Kaushal
On Tue, Aug 28, 2012 at 7:27 PM, Pranith Kumar Karampuri
<address@hidden> wrote:
> No. Output formats in that way generally start out nice but as you start
> adding more fields, formatting them becomes difficult IMO.
>
> Pranith
> ----- Original Message -----
> From: "Stephan von Krawczynski" <address@hidden>
> To: "Pranith Kumar Karampuri" <address@hidden>
> Cc: "gluster-users" <address@hidden>, "Gluster Devel" <address@hidden>
> Sent: Tuesday, August 28, 2012 7:01:57 PM
> Subject: Re: [Gluster-devel] [Gluster-users] FeedBack Requested : Changes to
> CLI output of 'peer status'
>
> Top posting and kidding is a bit exaggerated for one posting ...
>
> You are not seriously talking about 80 char terminals for an output that is
> commonly used by scripts and stuff like nagios, are you?
>
>
> On Tue, 28 Aug 2012 08:46:22 -0400 (EDT)
> Pranith Kumar Karampuri <address@hidden> wrote:
>
>> hi Amar,
>> This is the format we considered initially but we did not go with this
>> because it may exceed 80 chars and wrap over for small terminals if we want
>> to add more fields in future.
>>
>> Pranith.
>> ----- Original Message -----
>> From: "Amar Tumballi" <address@hidden>
>> To: "Gluster Devel" <address@hidden>, "gluster-users" <address@hidden>
>> Sent: Tuesday, August 28, 2012 4:36:07 PM
>> Subject: [Gluster-users] FeedBack Requested : Changes to CLI output of 'peer
>> status'
>>
>> Hi,
>>
>> Wanted to check if any one is using gluster CLI output of 'peer status'
>> in their scripts/programs? If yes, let me know. If not, we are trying to
>> make it more script friendly.
>>
>> For example the current output would look something like:
>>
>> -----
>> Hostname: 10.70.36.7
>> Uuid: c7283ee7-0e8d-4cb8-8552-a63ab05deaa7
>> State: Peer in Cluster (Connected)
>>
>> Hostname: 10.70.36.6
>> Uuid: 5a2fdeb3-e63e-4e56-aebe-8b68a5abfcef
>> State: Peer in Cluster (Connected)
>>
>> -----
>>
>> New changes would make it look like :
>>
>> -------
>> UUID Hostname Status
>> c7283ee7-0e8d-4cb8-8552-a63ab05deaa7 10.70.36.7 Connected
>> 5a2fdeb3-e63e-4e56-aebe-8b68a5abfcef 10.70.36.6 Connected
>>
>> -------
>>
>> If anyone has better format, or want more information, let us know now.
>> I would keep timeout for this mail as 3 more working days, and without
>> any response, we will go ahead with the change.
>>
>> Regards,
>> Amar
>> _______________________________________________
>> Gluster-users mailing list
>> address@hidden
>> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
>>
>> _______________________________________________
>> Gluster-devel mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/gluster-devel
>>
>
>
> --
> Regards,
> Stephan
>
> _______________________________________________
> Gluster-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/gluster-devel
> _______________________________________________
> Gluster-users mailing list
> address@hidden
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-devel] [Gluster-users] FeedBack Requested : Changes to CLI output of 'peer status', Anand Avati, 2012/08/29