Do we have corresponding changes in --xml output? If we are removing any
existing elements, the management systems will break.
Thanks,
Kanagaraj
On 11/26/2014 06:49 PM, Mohammed Rafi K C wrote:
Hi All,
We are planning to change the volume status command to show RDMA port for
tcp,rdma volumes
Hello Rafi,
For clarity and ease of fast visual identification, I would prefer #3. It would
be even better to put a dash or something in the RDMA port column when RDMA is
not used so that each line can be parsed easily with a relatively regular
number of fields:
Status of volume: xcube
Gluste
Hello all,
On 27/11/14 07:15, Jiffin Tony Thottan wrote:
>> Status of volume: xcube
>> Gluster process Port Online Pid
>>
>> Brick 192.168.44.108:/home/brick49157Y
Not adding an extra column is least likely to break any scripts that
currently parse the status output by splitting on spaces.
On Wed, 2014-11-26 at 20:27 +0530, Atin Mukherjee wrote:
> I would vote for 2nd one.
>
> ~Atin
>
> On 11/26/2014 06:49 PM, Mohammed Rafi K C wrote:
> >
> >
> > Hi Al
I vote 3
在 2014年11月27日，上午9:23，Franco Broi 写道：
>
> Not adding an extra column is least likely to break any scripts that
> currently parse the status output by splitting on spaces.
>
> On Wed, 2014-11-26 at 20:27 +0530, Atin Mukherjee wrote:
>> I would vote for 2nd one.
>>
>> ~Atin
>>
>> On 11
IMO, this would definitely have a corresponding change in --xml output.
We need to take that into account as well.
~Atin
On 11/27/2014 10:00 AM, Kanagaraj wrote:
> Do we have corresponding changes in --xml output? If we are removing any
> existing elements, the management systems will break.
>
>
