Displaying 20 results from an estimated 10000 matches similar to: "[summary] virtio network device failover writeup"
2019 Mar 19
2
[summary] virtio network device failover writeup
Hi Michael,
Great blog-post which summarise everything very well!
Some comments I have:
1) I think that when we are using the term ?1-netdev model? on community discussion, we tend to refer to what you have defined in blog-post as "3-device model with hidden slaves?.
Therefore, I would suggest to just remove the ?1-netdev model? section and rename the "3-device model with hidden
2019 Mar 20
2
[summary] virtio network device failover writeup
> On 20 Mar 2019, at 16:09, Michael S. Tsirkin <mst at redhat.com> wrote:
>
> On Wed, Mar 20, 2019 at 02:23:36PM +0200, Liran Alon wrote:
>>
>>
>>> On 20 Mar 2019, at 12:25, Michael S. Tsirkin <mst at redhat.com> wrote:
>>>
>>> On Wed, Mar 20, 2019 at 01:25:58AM +0200, Liran Alon wrote:
>>>>
>>>>
2019 Mar 20
2
[summary] virtio network device failover writeup
> On 20 Mar 2019, at 16:09, Michael S. Tsirkin <mst at redhat.com> wrote:
>
> On Wed, Mar 20, 2019 at 02:23:36PM +0200, Liran Alon wrote:
>>
>>
>>> On 20 Mar 2019, at 12:25, Michael S. Tsirkin <mst at redhat.com> wrote:
>>>
>>> On Wed, Mar 20, 2019 at 01:25:58AM +0200, Liran Alon wrote:
>>>>
>>>>
2019 Mar 20
2
[summary] virtio network device failover writeup
> On 20 Mar 2019, at 12:25, Michael S. Tsirkin <mst at redhat.com> wrote:
>
> On Wed, Mar 20, 2019 at 01:25:58AM +0200, Liran Alon wrote:
>>
>>
>>> On 19 Mar 2019, at 23:19, Michael S. Tsirkin <mst at redhat.com> wrote:
>>>
>>> On Tue, Mar 19, 2019 at 08:46:47AM -0700, Stephen Hemminger wrote:
>>>> On Tue, 19 Mar 2019
2019 Mar 20
2
[summary] virtio network device failover writeup
> On 20 Mar 2019, at 12:25, Michael S. Tsirkin <mst at redhat.com> wrote:
>
> On Wed, Mar 20, 2019 at 01:25:58AM +0200, Liran Alon wrote:
>>
>>
>>> On 19 Mar 2019, at 23:19, Michael S. Tsirkin <mst at redhat.com> wrote:
>>>
>>> On Tue, Mar 19, 2019 at 08:46:47AM -0700, Stephen Hemminger wrote:
>>>> On Tue, 19 Mar 2019
2019 Mar 20
2
[summary] virtio network device failover writeup
> On 21 Mar 2019, at 0:10, Michael S. Tsirkin <mst at redhat.com> wrote:
>
> On Wed, Mar 20, 2019 at 11:43:41PM +0200, Liran Alon wrote:
>>
>>
>>> On 20 Mar 2019, at 16:09, Michael S. Tsirkin <mst at redhat.com> wrote:
>>>
>>> On Wed, Mar 20, 2019 at 02:23:36PM +0200, Liran Alon wrote:
>>>>
>>>>
2019 Mar 20
2
[summary] virtio network device failover writeup
> On 21 Mar 2019, at 0:10, Michael S. Tsirkin <mst at redhat.com> wrote:
>
> On Wed, Mar 20, 2019 at 11:43:41PM +0200, Liran Alon wrote:
>>
>>
>>> On 20 Mar 2019, at 16:09, Michael S. Tsirkin <mst at redhat.com> wrote:
>>>
>>> On Wed, Mar 20, 2019 at 02:23:36PM +0200, Liran Alon wrote:
>>>>
>>>>
2019 Mar 21
3
[summary] virtio network device failover writeup
> On 21 Mar 2019, at 14:37, Michael S. Tsirkin <mst at redhat.com> wrote:
>
> On Thu, Mar 21, 2019 at 12:07:57PM +0200, Liran Alon wrote:
>>>>>> 2) It brings non-intuitive customer experience. For example, a customer may attempt to analyse connectivity issue by checking the connectivity
>>>>>> on a net-failover slave (e.g. the VF) but will see no
2019 Mar 21
3
[summary] virtio network device failover writeup
> On 21 Mar 2019, at 14:37, Michael S. Tsirkin <mst at redhat.com> wrote:
>
> On Thu, Mar 21, 2019 at 12:07:57PM +0200, Liran Alon wrote:
>>>>>> 2) It brings non-intuitive customer experience. For example, a customer may attempt to analyse connectivity issue by checking the connectivity
>>>>>> on a net-failover slave (e.g. the VF) but will see no
2019 Mar 21
4
[summary] virtio network device failover writeup
> On 21 Mar 2019, at 14:57, Michael S. Tsirkin <mst at redhat.com> wrote:
>
> On Thu, Mar 21, 2019 at 02:47:50PM +0200, Liran Alon wrote:
>>
>>
>>> On 21 Mar 2019, at 14:37, Michael S. Tsirkin <mst at redhat.com> wrote:
>>>
>>> On Thu, Mar 21, 2019 at 12:07:57PM +0200, Liran Alon wrote:
>>>>>>>> 2) It brings
2019 Mar 21
4
[summary] virtio network device failover writeup
> On 21 Mar 2019, at 14:57, Michael S. Tsirkin <mst at redhat.com> wrote:
>
> On Thu, Mar 21, 2019 at 02:47:50PM +0200, Liran Alon wrote:
>>
>>
>>> On 21 Mar 2019, at 14:37, Michael S. Tsirkin <mst at redhat.com> wrote:
>>>
>>> On Thu, Mar 21, 2019 at 12:07:57PM +0200, Liran Alon wrote:
>>>>>>>> 2) It brings
2019 Mar 21
2
[summary] virtio network device failover writeup
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 at 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
2019 Mar 21
2
[summary] virtio network device failover writeup
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 at 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
2019 Mar 21
2
[summary] virtio network device failover writeup
> On 21 Mar 2019, at 15:12, Michael S. Tsirkin <mst at redhat.com> wrote:
>
> On Thu, Mar 21, 2019 at 03:04:37PM +0200, Liran Alon wrote:
>>
>>
>>> On 21 Mar 2019, at 14:57, Michael S. Tsirkin <mst at redhat.com> wrote:
>>>
>>> On Thu, Mar 21, 2019 at 02:47:50PM +0200, Liran Alon wrote:
>>>>
>>>>
2019 Mar 21
2
[summary] virtio network device failover writeup
> On 21 Mar 2019, at 15:12, Michael S. Tsirkin <mst at redhat.com> wrote:
>
> On Thu, Mar 21, 2019 at 03:04:37PM +0200, Liran Alon wrote:
>>
>>
>>> On 21 Mar 2019, at 14:57, Michael S. Tsirkin <mst at redhat.com> wrote:
>>>
>>> On Thu, Mar 21, 2019 at 02:47:50PM +0200, Liran Alon wrote:
>>>>
>>>>
2019 Mar 21
2
[summary] virtio network device failover writeup
> On 21 Mar 2019, at 10:58, Michael S. Tsirkin <mst at redhat.com> wrote:
>
> On Thu, Mar 21, 2019 at 12:19:22AM +0200, Liran Alon wrote:
>>
>>
>>> On 21 Mar 2019, at 0:10, Michael S. Tsirkin <mst at redhat.com> wrote:
>>>
>>> On Wed, Mar 20, 2019 at 11:43:41PM +0200, Liran Alon wrote:
>>>>
>>>>
2019 Mar 21
2
[summary] virtio network device failover writeup
> On 21 Mar 2019, at 10:58, Michael S. Tsirkin <mst at redhat.com> wrote:
>
> On Thu, Mar 21, 2019 at 12:19:22AM +0200, Liran Alon wrote:
>>
>>
>>> On 21 Mar 2019, at 0:10, Michael S. Tsirkin <mst at redhat.com> wrote:
>>>
>>> On Wed, Mar 20, 2019 at 11:43:41PM +0200, Liran Alon wrote:
>>>>
>>>>
2019 Mar 19
2
[summary] virtio network device failover writeup
On Tue, Mar 19, 2019 at 08:46:47AM -0700, Stephen Hemminger wrote:
> On Tue, 19 Mar 2019 14:38:06 +0200
> Liran Alon <liran.alon at oracle.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
2019 Mar 19
2
[summary] virtio network device failover writeup
On Tue, Mar 19, 2019 at 08:46:47AM -0700, Stephen Hemminger wrote:
> On Tue, 19 Mar 2019 14:38:06 +0200
> Liran Alon <liran.alon at oracle.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
2019 Mar 21
1
[summary] virtio network device failover writeup
> On 21 Mar 2019, at 17:50, Michael S. Tsirkin <mst at 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 at oracle.com> wrote:
>>
>>>>
>>>> OK. Now what happens if master is moved to another namespace? Do we need
>>>>