From: Joe Damato <jdamato@fastly.com>
To: David Ahern <dsahern@kernel.org>
Cc: Paolo Abeni <pabeni@redhat.com>,
Stephen Hemminger <stephen@networkplumber.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: yaml gen NL families support in iproute2?
Date: Mon, 21 Oct 2024 13:58:29 -0700 [thread overview]
Message-ID: <ZxbAdVsf5UxbZ6Jp@LQ3V64L9R2> (raw)
In-Reply-To: <61184cdf-6afc-4b9b-a3d2-b5f8478e3cbb@kernel.org>
On Thu, Oct 17, 2024 at 12:36:47PM -0600, David Ahern wrote:
> On 10/17/24 11:41 AM, Paolo Abeni wrote:
> > Hi all,
> >
> > please allow me to [re?]start this conversation.
> >
> > I think it would be very useful to bring yaml gennl families support in
> > iproute2, so that end-users/admins could consolidated
> > administration/setup in a single tool - as opposed to current status
> > where something is only doable with iproute2 and something with the
> > yml-cli tool bundled in the kernel sources.
> >
> > Code wise it could be implemented extending a bit the auto-generated
> > code generation to provide even text/argument to NL parsing, so that the
> > iproute-specific glue (and maintenance effort) could be minimal.
> >
> > WDYT?
> >
>
> I would like to see the yaml files integrated into iproute2, but I have
> not had time to look into doing it.
I agree with David, but likewise have not had time to look into it.
It would be nice to use one tool instead of a combination of
multiple tools, if that were at all possible.
next prev parent reply other threads:[~2024-10-21 20:58 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 [this message]
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
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=ZxbAdVsf5UxbZ6Jp@LQ3V64L9R2 \
--to=jdamato@fastly.com \
--cc=dsahern@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.