From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Ulf Kreutzberg <ulf.kreutzberg@hosteurope.de>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 2/2] xl: allow specifying a default netdev in xl.conf
Date: Tue, 5 Feb 2013 12:00:17 +0100 [thread overview]
Message-ID: <5110E641.9090902@citrix.com> (raw)
In-Reply-To: <1360060895.17017.27.camel@zakaz.uk.xensource.com>
On 05/02/13 11:41, Ian Campbell wrote:
> On Mon, 2013-01-28 at 11:00 +0000, George Dunlap wrote:
>> On Fri, Jan 25, 2013 at 3:26 PM, Roger Pau Monne
>> <roger.pau@citrix.com> wrote:
>> This adds a new global option in the xl configuration file
>> called
>> "defaultnetdev", that is used to specify the default netdev to
>> use
>> when none is passed in the vif specification.
>>
>>
>> I'm not a fan of the name, though; it doesn't seem very scalable. It
>> looks like we already have "defaultbridge', so I can see this is just
>> following precedent, but I wonder if it might be worth putting some
>> more thought into it before proceeding?
>>
>>
>> It seems like if we're going to have a default sub-option, it should
>> at least have the name of the option in which it resides.
>> "vif_netdev_default" or "default_vif_netdev" seem like better option.
>> Or maybe "vif.netdev.default"? "defaults.vif.netdev"?
>
> netdev is also a bit non-descriptive, even if it is what the vif-route
> script uses perhaps we present something more meaningful to the user?
>
> "gatewaydev" or something along those lines perhaps?
Will this also imply that xl should use gatewaydev instead of netdev in
the vif config line? Right now we don't support netdev, but I guess we
should add it for backwards compatibility.
> I'd be inclined to use whatever name we decide here in the libxl
> API/internals as well and just go netdev at the hotplug script
> interface.
>
> Ian.
>
>
next prev parent reply other threads:[~2013-02-05 11:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 15:26 [PATCH 0/2] add vif-route support to libxl/xl Roger Pau Monne
2013-01-25 15:26 ` [PATCH 1/2] xl/libxl: add netdev to vif specification Roger Pau Monne
2013-02-05 10:40 ` Ian Campbell
2013-02-05 10:56 ` Roger Pau Monné
2013-02-05 11:10 ` Ian Campbell
2013-02-05 11:39 ` Roger Pau Monné
2013-02-05 11:41 ` Ian Campbell
2013-01-25 15:26 ` [PATCH 2/2] xl: allow specifying a default netdev in xl.conf Roger Pau Monne
2013-01-28 11:00 ` George Dunlap
2013-01-28 17:11 ` George Dunlap
2013-01-29 11:01 ` Roger Pau Monné
2013-02-05 10:41 ` Ian Campbell
2013-02-05 11:00 ` Roger Pau Monné [this message]
2013-02-05 11:09 ` Ian Campbell
2013-01-25 16:16 ` [PATCH 0/2] add vif-route support to libxl/xl Roger Pau Monné
2013-02-05 11:48 ` Ian Campbell
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=5110E641.9090902@citrix.com \
--to=roger.pau@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=ulf.kreutzberg@hosteurope.de \
--cc=xen-devel@lists.xen.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.