On Wed, Jun 22, 2016 at 1:00 PM, Jiri Pirko <j...@resnulli.us> wrote: > Wed, Jun 22, 2016 at 08:10:47PM CEST, step...@networkplumber.org wrote: >>On Wed, 22 Jun 2016 16:53:44 +0200 >>Jiri Pirko <j...@resnulli.us> wrote: >> >>> Wed, Jun 22, 2016 at 03:45:50PM CEST, ro...@cumulusnetworks.com wrote: >>> >From: Roopa Prabhu <ro...@cumulusnetworks.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. >> >>Try using netlink in perl or python, it is quite difficult. > > pyroute2? Quite easy...
none of the implementations out there are complete nor can compete with iproute2. iproute2 is maintained by netdev community and always is up-todate with the latest networking api. Nothing against pyroute2 but we wrote our own for other reasons and we carry additional burden of maintaining it and keeping it up-todate for every networking api.. that gets added to iproute2 (and the implementation of netlink is often very easy in C). Also, for external automation and orchestration tools (to whom this patch-set is addressed), there is no reason for them to write and maintain their own tools using netlink when they can use iproute2 directly to create a link or query its properties.
