On Oct 16, num...@ovn.org wrote:
> From: Numan Siddique
>
> If a virtual port has 2 parents and if both of them are scheduled
> on the same chassis, then virtual port binding doesn't work.
>
> For virtual port binding we have the below logical flows:
> inport == p1 && !is_chassis_resident("vip-p
On Thu, Oct 17, 2019 at 3:09 PM Dumitru Ceara wrote:
> On Wed, Oct 16, 2019 at 7:01 PM wrote:
> >
> > From: Numan Siddique
> >
> > If a virtual port has 2 parents and if both of them are scheduled
> > on the same chassis, then virtual port binding doesn't work.
> >
> > For virtual port binding
On Wed, Oct 16, 2019 at 7:01 PM wrote:
>
> From: Numan Siddique
>
> If a virtual port has 2 parents and if both of them are scheduled
> on the same chassis, then virtual port binding doesn't work.
>
> For virtual port binding we have the below logical flows:
> inport == p1 && !is_chassis_resident
Bleep bloop. Greetings Numan Siddique, I am a robot and I have tried out your
patch.
Thanks for your contribution.
I encountered some error that I wasn't expecting. See the details below.
checkpatch:
WARNING: Line is 201 characters long (recommended limit is 79)
#36 FILE: northd/ovn-northd.8.
From: Numan Siddique
If a virtual port has 2 parents and if both of them are scheduled
on the same chassis, then virtual port binding doesn't work.
For virtual port binding we have the below logical flows:
inport == p1 && !is_chassis_resident("vip-port") && arp ..
actions=bind_vport(vip-port);
