[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJieiUhRp5JWWH+Du+TSUW9Ve-jqcfHH6Zciz-EM1pmOj5Ctdw@mail.gmail.com>
Date: Wed, 22 Jun 2016 10:41:52 -0700
From: Roopa Prabhu <roopa@...ulusnetworks.com>
To: Jiri Pirko <jiri@...nulli.us>
Cc: "stephen@...workplumber.org" <stephen@...workplumber.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Anuradha Karuppiah <anuradhak@...ulusnetworks.com>,
Nikolay Aleksandrov <nikolay@...ulusnetworks.com>,
Julien Fortin <julien@...ulusnetworks.com>
Subject: Re: [PATCH iproute2 net-next v4 0/5] bridge: json support for fdb and
vlan show
On Wed, Jun 22, 2016 at 7:53 AM, Jiri Pirko <jiri@...nulli.us> wrote:
> Wed, Jun 22, 2016 at 03:45:50PM CEST, roopa@...ulusnetworks.com wrote:
>>From: Roopa Prabhu <roopa@...ulusnetworks.com>
>>
>>This patch series adds json support for a few bridge show commands.
>>We plan to follow up with json support for additional commands soon.
>
> I'm just curious, what is you use case for this? Apps can use rtnetlink
> socket directly.
most important use case is for automation/orchestration tools.
They use existing linux tools to query and configure. Iproute2 output
is not machine
readable today ...and json is industry standard.
Powered by blists - more mailing lists