From: Jakub Kicinski <kuba@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Joe Damato <jdamato@fastly.com>, David Ahern <dsahern@kernel.org>,
Stephen Hemminger <stephen@networkplumber.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: yaml gen NL families support in iproute2?
Date: Tue, 29 Oct 2024 06:39:39 -0700 [thread overview]
Message-ID: <20241029063939.244e2c67@kernel.org> (raw)
In-Reply-To: <46b77837-2f87-44aa-a6f2-e61919591659@redhat.com>
On Tue, 29 Oct 2024 10:29:15 +0100 Paolo Abeni wrote:
> > That's assuming that by
> >
> > so that end-users/admins could consolidated administration/setup
> > in a single tool
> >
> > you mean that you are aiming to create a single tool capable of
> > handling arbitrary specs. > If you want to make the output
> > and input more "pretty" than just attrs in / attrs out -- then
> > indeed building on top of libynl.a makes sense.
>
> My understanding is that a similar/consistent command line and man page
> based documentation will preferable for the end-user - say to configure
> ip addresses and configure tx shaping on a given device.
I see. You got me slightly confused with "single tool" as iproute2
itself contains multiple tools. Sounds like you just want to write
a tool / add to ip the ability to talk net shaper nl.
prev parent reply other threads:[~2024-10-29 13:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 17:41 yaml gen NL families support in iproute2? Paolo Abeni
2024-10-17 18:36 ` David Ahern
2024-10-21 20:58 ` Joe Damato
2024-10-22 7:55 ` Paolo Abeni
2024-10-28 20:58 ` Jakub Kicinski
2024-10-28 21:29 ` David Ahern
2024-10-28 22:15 ` Jakub Kicinski
2024-10-28 23:40 ` Stephen Hemminger
2024-10-29 0:06 ` Jakub Kicinski
2024-10-29 0:43 ` Stephen Hemminger
2024-10-29 9:29 ` Paolo Abeni
2024-10-29 13:39 ` Jakub Kicinski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241029063939.244e2c67@kernel.org \
--to=kuba@kernel.org \
--cc=dsahern@kernel.org \
--cc=jdamato@fastly.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).