[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190319084647.727f8dcf@shemminger-XPS-13-9360>
Date: Tue, 19 Mar 2019 08:46:47 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Liran Alon <liran.alon@...cle.com>
Cc: "Michael S. Tsirkin" <mst@...hat.com>,
Si-Wei Liu <si-wei.liu@...cle.com>,
Sridhar Samudrala <sridhar.samudrala@...el.com>,
Alexander Duyck <alexander.duyck@...il.com>,
Jakub Kicinski <kubakici@...pl>, Jiri Pirko <jiri@...nulli.us>,
David Miller <davem@...emloft.net>,
Netdev <netdev@...r.kernel.org>,
virtualization@...ts.linux-foundation.org,
boris.ostrovsky@...cle.com, vijay.balakrishna@...cle.com,
jfreimann@...hat.com, ogerlitz@...lanox.com, vuhuong@...lanox.com
Subject: Re: [summary] virtio network device failover writeup
On Tue, 19 Mar 2019 14:38:06 +0200
Liran Alon <liran.alon@...cle.com> wrote:
> b.3) cloud-init: If configured to perform network-configuration, it attempts to configure all available netdevs. It should avoid however doing so on net-failover slaves.
> (Microsoft has handled this by adding a mechanism in cloud-init to blacklist a netdev from being configured in case it is owned by a specific PCI driver. Specifically, they blacklist Mellanox VF driver. However, this technique doesn’t work for the net-failover mechanism because both the net-failover netdev and the virtio-net netdev are owned by the virtio-net PCI driver).
Cloud-init should really just ignore all devices that have a master device.
That would have been more general, and safer for other use cases.
Powered by blists - more mailing lists