On Sun, Jun 19, 2016 at 04:11:03PM +, Hui Kang wrote:
> Thanks for your explanation. Does it mean in real deployment (i.e., no fake
> chassis), I should use "ovs-vsctl add-port br-int" on the hypervisor to bind
> lport?
Yes, and also populate the external-ids described in
IntegrationGuide.md.
- Original message -From: Russell Bryant To: Hui Kang/Watson/IBM@IBMUSCc: "discuss@openvswitch.org" Subject: Re: [ovs-discuss] [OVN] different ways to bind lportsDate: Sun, Jun 19, 2016 9:13 AM On Saturday, June 18, 2016, Hui Kang wrote:
Hi,
I saw there are two comma
On Saturday, June 18, 2016, Hui Kang wrote:
> Hi,
> I saw there are two commands binding logical ports to hypervisor in OVN
> tutorial scripts
>
> ovs-vsctl add-port br-int lport1 -- set Interface lport1
> external_ids:iface-id=sw0-port1[1]
>
> ovn-sbctl lport-bind sw0-port3 fakechassis [2]
Hi,
I saw there are two commands binding logical ports to hypervisor in OVN tutorial scripts
ovs-vsctl add-port br-int lport1 -- set Interface lport1 external_ids:iface-id=sw0-port1 [1]
ovn-sbctl lport-bind sw0-port3 fakechassis [2]
Is there any difference between them? Thanks.
- Hui