From: Stefano Brivio <sbrivio@redhat.com>
To: Paul Holzinger <pholzing@redhat.com>
Cc: passt-dev@passt.top, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH v2] conf: Accept duplicate and conflicting options, the last one wins
Date: Thu, 20 Jun 2024 12:09:27 +0200 [thread overview]
Message-ID: <20240620120927.6f3b670d@elisabeth> (raw)
In-Reply-To: <5ce4381a-4a8b-4ad4-b0e8-04ae85734d12@redhat.com>
On Thu, 20 Jun 2024 11:06:48 +0200
Paul Holzinger <pholzing@redhat.com> wrote:
> On 19/06/2024 17:40, Stefano Brivio wrote:
> > In multiple occasions, especially when passt(1) and pasta(1) are used
> > in integrations such as the one with Podman, the ability to override
> > earlier options on the command line with later one would have been
> > convenient.
> >
> > Recently, to debug a number of issues happening with Podman, I would
> > have liked to ask users to share a debug log by passing --debug as
> > additional option, but pasta refuses --quiet (always passed by Podman)
> > and --debug at the same time.
> >
> > On top of this, Podman lets users specify other pasta options in its
> > containers.conf(5) file, as well as on the command line.
> >
> > The options from the configuration files are appended together with
> > the ones from the command line, which makes it impossible for users to
> > override options from the configuration file, if duplicated options
> > are refused, unless Podman takes care of sorting them, which is
> > clearly not sustainable.
> >
> > For --debug and --trace, somebody took care of this on Podman side at:
> > https://github.com/containers/common/pull/2052
> >
> > but this doesn't fix the issue with other options, and we'll have
> > anyway older versions of Podman around, too.
> >
> > I think there's some value in telling users about duplicated or
> > conflicting options, because that might reveal issues in integrations
> > or accidental misconfigurations, but by now I'm fairly convinced that
> > the downsides outweigh this.
> >
> > Drop checks about duplicate options and mutually exclusive ones. In
> > some cases, we need to also undo a couple of initialisations caused
> > by earlier options, but this looks like a simplification, overall.
> >
> > Notable exception: --stderr still conflicts with --log-file, because
> > users might have the expectation that they don't actually conflict.
> > But they do conflict in the existing implementation, so it's safer
> > to make sure that the users notice that.
> >
> > Suggested-by: Paul Holzinger <pholzing@redhat.com>
> > Suggested-by: David Gibson <david@gibson.dropbear.id.au>
> > Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
> > ---
> > v2:
> > - report --log-file and --stderr as conflicting, but accept
> > multiple options if they don't conflict
> > - for --log-file and --pcap, make it clear in the man page that
> > the general principle still applies: only the last one (of each)
> > takes effect
> > - add some more context about Podman and how the list of pasta
> > options is built there, in the commit message
> >
> > conf.c | 134 ++++++++++++++++----------------------------------------
> > passt.1 | 17 +++++++
> > 2 files changed, 55 insertions(+), 96 deletions(-)
>
> I have done some tests and while you changed --gateway to only take the
> last one --address was not changed:
>
> ./pasta --config-net -a 10.0.0.1 -a 10.0.0.2 ip a
>
> Invalid address: 10.0.0.2
>
> The error is clearly nonsensical as the address is valid. So either it
> should match the gateway behavior or the error must clearly state that
> multiple addresses are not accepted if this is what you want.
Gosh, thanks, nice catch, v3 coming (in a while).
--
Stefano
prev parent reply other threads:[~2024-06-20 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 15:40 [PATCH v2] conf: Accept duplicate and conflicting options, the last one wins Stefano Brivio
2024-06-20 0:22 ` David Gibson
2024-06-20 9:06 ` Paul Holzinger
2024-06-20 10:09 ` Stefano Brivio [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=20240620120927.6f3b670d@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=pholzing@redhat.com \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).