From: "Michael S. Tsirkin" <mst@redhat.com>
To: Liran Alon <liran.alon@oracle.com>
Cc: vuhuong@mellanox.com, Jiri Pirko <jiri@resnulli.us>,
Jakub Kicinski <kubakici@wp.pl>,
Sridhar Samudrala <sridhar.samudrala@intel.com>,
Alexander Duyck <alexander.duyck@gmail.com>,
virtualization@lists.linux-foundation.org,
Netdev <netdev@vger.kernel.org>,
Si-Wei Liu <si-wei.liu@oracle.com>,
boris.ostrovsky@oracle.com, David Miller <davem@davemloft.net>,
ogerlitz@mellanox.com
Subject: Re: [summary] virtio network device failover writeup
Date: Thu, 21 Mar 2019 13:12:23 -0400 [thread overview]
Message-ID: <20190321131006-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <BC327EF2-22C7-402B-9078-93891A4774D6@oracle.com>
On Thu, Mar 21, 2019 at 06:31:35PM +0200, Liran Alon wrote:
>
>
> > On 21 Mar 2019, at 17:50, Michael S. Tsirkin <mst@redhat.com> wrote:
> >
> > On Thu, Mar 21, 2019 at 08:45:17AM -0700, Stephen Hemminger wrote:
> >> On Thu, 21 Mar 2019 15:04:37 +0200
> >> Liran Alon <liran.alon@oracle.com> wrote:
> >>
> >>>>
> >>>> OK. Now what happens if master is moved to another namespace? Do we need
> >>>> to move the slaves too?
> >>>
> >>> No. Why would we move the slaves? The whole point is to make most customer ignore the net-failover slaves and remain them “hidden” in their dedicated netns.
> >>> We won’t prevent customer from explicitly moving the net-failover slaves out of this netns, but we will not move them out of there automatically.
> >>
> >>
> >> The 2-device netvsc already handles case where master changes namespace.
> >
> > Is it by moving slave with it?
>
> See c0a41b887ce6 ("hv_netvsc: move VF to same namespace as netvsc device”).
> It seems that when NetVSC master netdev changes netns, the VF is moved to the same netns by the NetVSC driver.
> Kinda the opposite than what we are suggesting here to make sure that the net-failover master netdev is on a separate
> netns than it’s slaves...
>
> -Liran
>
> >
> > --
> > MST
Not exactly opposite I'd say.
If failover is in host ns, slaves in /primary and /standby, then moving
failover to /container should move slaves to /container/primary and
/container/standby.
--
MST
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2019-03-21 17:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190317095052-mutt-send-email-mst@kernel.org>
2019-03-19 12:38 ` [summary] virtio network device failover writeup Liran Alon
[not found] ` <54E7C3AF-C3C5-4AF2-86C9-AA50389F855F@oracle.com>
2019-03-19 15:46 ` Stephen Hemminger
2019-03-19 21:06 ` Michael S. Tsirkin
[not found] ` <20190319084647.727f8dcf@shemminger-XPS-13-9360>
2019-03-19 21:19 ` Michael S. Tsirkin
[not found] ` <20190319171638-mutt-send-email-mst@kernel.org>
2019-03-19 23:25 ` Liran Alon
[not found] ` <79F5D7C0-BBAA-4F78-9039-27A444970002@oracle.com>
2019-03-20 10:25 ` Michael S. Tsirkin
[not found] ` <20190320061632-mutt-send-email-mst@kernel.org>
2019-03-20 12:23 ` Liran Alon
[not found] ` <E0606AE7-7DE2-47C7-B64A-8161FD814277@oracle.com>
2019-03-20 14:09 ` Michael S. Tsirkin
[not found] ` <20190320100747-mutt-send-email-mst@kernel.org>
2019-03-20 21:43 ` Liran Alon
[not found] ` <36772E22-7A8F-4C42-A731-398E3204B418@oracle.com>
2019-03-20 22:10 ` Michael S. Tsirkin
[not found] ` <20190320180641-mutt-send-email-mst@kernel.org>
2019-03-20 22:19 ` Liran Alon
[not found] ` <B3FB267A-2DC0-4A4C-8193-7F420BC9791B@oracle.com>
2019-03-21 8:58 ` Michael S. Tsirkin
[not found] ` <20190321044920-mutt-send-email-mst@kernel.org>
2019-03-21 10:07 ` Liran Alon
[not found] ` <CD40EA09-242D-41E1-8BD2-4FF4BB4D1986@oracle.com>
2019-03-21 12:37 ` Michael S. Tsirkin
[not found] ` <20190321082532-mutt-send-email-mst@kernel.org>
2019-03-21 12:47 ` Liran Alon
[not found] ` <BB2B938F-D2F0-47F8-B651-70EC8A19BC6B@oracle.com>
2019-03-21 12:57 ` Michael S. Tsirkin
[not found] ` <20190321085159-mutt-send-email-mst@kernel.org>
2019-03-21 13:04 ` Liran Alon
2019-03-21 15:44 ` Stephen Hemminger
[not found] ` <2939FB15-720A-4C9E-92B7-2DBA139DDE0F@oracle.com>
2019-03-21 13:12 ` Michael S. Tsirkin
[not found] ` <20190321090619-mutt-send-email-mst@kernel.org>
2019-03-21 13:24 ` Liran Alon
[not found] ` <1B52153B-B968-4E5B-8959-E7E83CE7FEAF@oracle.com>
2019-03-21 13:51 ` Michael S. Tsirkin
[not found] ` <20190321094217-mutt-send-email-mst@kernel.org>
2019-03-21 14:16 ` Liran Alon
[not found] ` <FF25F82E-F6FF-424E-88BA-A3D74EE505DE@oracle.com>
2019-03-21 15:15 ` Michael S. Tsirkin
2019-03-21 15:45 ` Stephen Hemminger
[not found] ` <20190321084517.773a65fa@shemminger-XPS-13-9360>
2019-03-21 15:50 ` Michael S. Tsirkin
[not found] ` <20190321114557-mutt-send-email-mst@kernel.org>
2019-03-21 16:31 ` Liran Alon
[not found] ` <BC327EF2-22C7-402B-9078-93891A4774D6@oracle.com>
2019-03-21 17:12 ` Michael S. Tsirkin [this message]
2019-03-21 17:15 ` Liran Alon
[not found] ` <20190319170445-mutt-send-email-mst@kernel.org>
2019-03-19 23:05 ` Liran Alon
2019-03-17 13:55 Michael S. Tsirkin
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=20190321131006-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=boris.ostrovsky@oracle.com \
--cc=davem@davemloft.net \
--cc=jiri@resnulli.us \
--cc=kubakici@wp.pl \
--cc=liran.alon@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=si-wei.liu@oracle.com \
--cc=sridhar.samudrala@intel.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=vuhuong@mellanox.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.
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).