Re: [ovs-discuss] clustered OVSDB in 2.9 or 2.10?
On Mon, Jan 15, 2018 at 2:30 AM, Numan Siddique wrote: > > > On Fri, Jan 12, 2018 at 1:28 AM, Ben Pfaff wrote: >> >> I posted the patches to add clustering support to OVSDB at the end of >> last year so that it was technically qualified to make it into OVS 2.9. >> At least in OVS 2.9, it will be marked "experimental", since it's a >> major change that might need work to be suitable for production (we >> simply don't know yet). Since it's a huge change, review is naturally >> taking a while. >> >> It occurred to me that it might make more sense to get this into master >> just after we branch for 2.9. Then it would be basically the first >> feature in 2.10. That would give us the whole 2.10 release cycle to get >> it from experimental to something production quality, and we could in >> theory release 2.10 with a solid clustered OVSDB. Instead of >> experimental in 2.9 and then production in 2.10, we'd just have >> production in 2.10. That might also give us some opportunity to make >> breaking changes within the 2.10 cycle that users who were experimenting >> with 2.9 might be reluctant to accept as part of an upgrade. >> >> Does anyone have thoughts on which is the preferred path? > > > Hi Ben, > > I see one advantage for OpenStack Tripleo + OVN integration in having this > feature > supported as expiremental in OVS 2.9. Once we have OVS 2.9 availalbe in RDO > packages > we could work on integrating this feature (as optional) during OVN > deployments. The scope of > this work would be to start OVN db services with clustering enabled and > configuring it. > The next OpenStack release is Queens and is under development, but we are > already late for new > features so it is fine. The release after Queens is Rocky and it will be > easier to integrate > clustered ovsdb feature with Rocky release if we have it in OVS 2.9. This is the main benefit of putting it in 2.9 to me -- it makes it easier to work on integration. If it's in 2.9, OpenStack (as one example) can do integration work and merge it as an optional feature. If it's deferred to 2.10, that work can begin, but the patches can't be merged until the feature is in a release. It's also a bit more difficult to test it in integrated CI until it's in a release. It's also understandable if 2.9 turns out to be too aggressive. -- Russell Bryant ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] OVS port name differ from interface name
Hi, Is it possible to have an OVS port ‘name’ differ from the interface name? Bridge ovs-ha-sw Port ovs-ha-sw Interface ovs-ha-sw type: internal Port "bond1" Interface "bond1" To have the effect of: Bridge ovs-ha-sw Port ovs-ha-sw Interface ovs-ha-sw type: internal Port “east-west" Interface "bond1" Thanks, Fred___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] OVS port name differ from interface name
On Mon, Jan 15, 2018 at 09:50:52AM -0800, Fred Licht wrote: >Is it possible to have an OVS port ‘name’ differ from the interface name? > > Bridge ovs-ha-sw > Port ovs-ha-sw > Interface ovs-ha-sw > type: internal > Port "bond1" > Interface "bond1" > > To have the effect of: > > Bridge ovs-ha-sw > Port ovs-ha-sw > Interface ovs-ha-sw > type: internal > Port “east-west" > Interface "bond1" You can do it, but since port names are immutable it has to happen at the time you add the port. For example: blp@sigabrt:~/nicira/ovs/tutorial(0)$ ovs-vsctl add-br br0 blp@sigabrt:~/nicira/ovs/tutorial(0)$ ovs-vsctl add-port br0 p0 -- set port p0 name=asdf blp@sigabrt:~/nicira/ovs/tutorial(0)$ ovs-vsctl show 8b75cccb-f1eb-4e75-ac67-57ebac4e8432 Bridge "br0" Port "br0" Interface "br0" type: internal Port asdf Interface "p0" blp@sigabrt:~/nicira/ovs/tutorial(0)$ ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] REDHAT: Route issue with dpdk-bond ports
On Tue, Dec 26, 2017 at 08:31:49AM +, Vishal Deep Ajmera wrote: > Hi, > > On Red-Hat, kernel IP Routes are getting deleted whenever a dpdk-bond port is > added to "netdev" type bridge. I understand that when a DPDK port is added to > ovs, the bridge port (LOCAL) is reconfigured with MAC address which requires > IOCTL calls to bring the device down and up. This causes kernel to remove the > routes. > > Can someone please have a look and let me know what am I missing here ? Hi Vishal, I think when the interface goes down to change the MAC address, the routes will go away. The only way to to make sure the routes will be restored is to change the initialization order. In your case, br0 is initialized first, then dpdkbond0 which will cause the issue. The order is alphabetical, so try renaming br0 to something like zbr0 to see if the bridge is reconfigured with the routes. fbl > Steps to reproduce the issue: > > # Create the bridge in OVS. > $ ifup br0 > > # Dump the routes > $ ip route > 11.2.0.0/24 dev br0 proto kernel scope link src 11.2.0.26 > 100.100.100.10 via 11.2.0.202 dev br0 > 100.100.100.20 via 11.2.0.201 dev br0 > 169.254.0.0/16 dev br0 scope link metric 1036 > > # Add DPDK Bond to bridge br0 > $ ifup dpdkbond0 > > # Dump the routes > $ ip route > 11.2.0.0/24 dev br0 proto kernel scope link src 11.2.0.26 > --> Other routes for br0 are missing. > > Here are the ifcfg files for the bridge BR0 and DPDKBOND0 port along with > static routes. > = > $ cat ifcfg-br0 > DEVICE=br0 > ONBOOT=yes > HOTPLUG=no > NM_CONTROLLED=no > PEERDNS=no > DEVICETYPE=ovs > TYPE=OVSUserBridge > BOOTPROTO=static > IPADDR=11.2.0.26 > NETMASK=255.255.255.0 > OVS_EXTRA="set bridge br0 fail_mode=standalone" > > $ cat ifcfg-dpdkbond0 > DEVICE=dpdkbond0 > ONBOOT=yes > HOTPLUG=no > NM_CONTROLLED=no > PEERDNS=no > DEVICETYPE=ovs > TYPE=OVSDPDKBond > OVS_BRIDGE=br0 > BOND_IFACES="dpdk0 dpdk1" > OVS_OPTIONS="bond_mode=balance-tcp other_config:lacp-time=fast lacp=passive" > > $ cat route-br0 > 100.100.100.10 via 11.2.0.201 dev br0 > 100.100.100.20 via 11.2.0.202 dev br0 > > = > > Warm Regards, > Vishal > > ___ > discuss mailing list > disc...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss -- Flavio ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] REDHAT: Route issue with dpdk-bond ports
Hi Flavio, Thanks for looking into this issue. I believe the order of initialization does not matter. Just an FYI: I tried with your suggestion of renaming the bridge name to zbr0 but it did not solve the issue. In my opinion the issue is with networking scripts which is not triggering route addition again for the bridge LOCAL port. Let me explain it a little more. As you see in the steps I followed, first we add the bridge br0 ($ifup br0). At this time the bridge LOCAL interface gets a random MAC address. Once the interface is configured, the networking service gets to see a new interface and invokes the route addition (due to presence of file route-br0) via ifup-eth/ifup-post script. Next when we add dpdk-bond ports ($ifup dpdkbond0), the bridge LOCAL interface is reconfigured with MAC address of one of the dpdk ports (since these are physical ports). At this time OVS only makes IOCTL calls for setting device flags to DOWN and UP. Once the device flag is set to UP again, I was assuming that ifup-eth/ifup-post script should get invoked again but it did not happen. Thus all the routes for br0 interface did not get added again. I hope this clarifies the issue. Warm Regards, Vishal Ajmera -Original Message- From: Flavio Leitner [mailto:f...@sysclose.org] Sent: Tuesday, January 16, 2018 9:17 AM To: Vishal Deep Ajmera Cc: ovs-discuss@openvswitch.org Subject: Re: [ovs-discuss] REDHAT: Route issue with dpdk-bond ports On Tue, Dec 26, 2017 at 08:31:49AM +, Vishal Deep Ajmera wrote: > Hi, > > On Red-Hat, kernel IP Routes are getting deleted whenever a dpdk-bond > port is added to "netdev" type bridge. I understand that when a DPDK > port is added to ovs, the bridge port (LOCAL) is reconfigured with MAC > address which requires IOCTL calls to bring the device down and up. > This causes kernel to remove the routes. > > Can someone please have a look and let me know what am I missing here ? Hi Vishal, I think when the interface goes down to change the MAC address, the routes will go away. The only way to to make sure the routes will be restored is to change the initialization order. In your case, br0 is initialized first, then dpdkbond0 which will cause the issue. The order is alphabetical, so try renaming br0 to something like zbr0 to see if the bridge is reconfigured with the routes. fbl > Steps to reproduce the issue: > > # Create the bridge in OVS. > $ ifup br0 > > # Dump the routes > $ ip route > 11.2.0.0/24 dev br0 proto kernel scope link src 11.2.0.26 > 100.100.100.10 via 11.2.0.202 dev br0 > 100.100.100.20 via 11.2.0.201 dev br0 > 169.254.0.0/16 dev br0 scope link metric 1036 > > # Add DPDK Bond to bridge br0 > $ ifup dpdkbond0 > > # Dump the routes > $ ip route > 11.2.0.0/24 dev br0 proto kernel scope link src 11.2.0.26 > --> Other routes for br0 are missing. > > Here are the ifcfg files for the bridge BR0 and DPDKBOND0 port along > with static routes. > = > $ cat ifcfg-br0 > DEVICE=br0 > ONBOOT=yes > HOTPLUG=no > NM_CONTROLLED=no > PEERDNS=no > DEVICETYPE=ovs > TYPE=OVSUserBridge > BOOTPROTO=static > IPADDR=11.2.0.26 > NETMASK=255.255.255.0 > OVS_EXTRA="set bridge br0 fail_mode=standalone" > > $ cat ifcfg-dpdkbond0 > DEVICE=dpdkbond0 > ONBOOT=yes > HOTPLUG=no > NM_CONTROLLED=no > PEERDNS=no > DEVICETYPE=ovs > TYPE=OVSDPDKBond > OVS_BRIDGE=br0 > BOND_IFACES="dpdk0 dpdk1" > OVS_OPTIONS="bond_mode=balance-tcp other_config:lacp-time=fast lacp=passive" > > $ cat route-br0 > 100.100.100.10 via 11.2.0.201 dev br0 > 100.100.100.20 via 11.2.0.202 dev br0 > > = > > Warm Regards, > Vishal > > ___ > discuss mailing list > disc...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss -- Flavio ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] unexpected behavior in ovs faucet tutorial
Hi, I'm following the ovs faucet tutorial to get familiar with openvswitch. Everything goes smoothly until section Triggering MAC Learning. I tried the ovs-appctl ofproto/trace ... ... -generate command, but no new logs showed in inst/faucet.log, and diff-flows also gives nothing. I'm using ovs 2.8.90, can anybody help me troubleshooting this? ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] unexpected behavior in ovs faucet tutorial
On Tue, Jan 16, 2018 at 3:04 PM, Hongwei Du wrote: > Hi, > > I'm following the ovs faucet tutorial to get familiar with > openvswitch. Everything goes smoothly until section Triggering MAC > Learning. > > I tried the ovs-appctl ofproto/trace ... ... -generate command, but no > new logs showed in inst/faucet.log, and diff-flows also gives nothing. > > I'm using ovs 2.8.90, can anybody help me troubleshooting this? > ___ > discuss mailing list > disc...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > Hi, Du This issue was just discussed in a recent talk[1]. Basically you should upgrade faucet to 1.6.15, and modify faucet.yaml with respect to the updated tutorial text[2]. [1] https://mail.openvswitch.org/pipermail/ovs-discuss/2018-January/045957.html [2] http://docs.openvswitch.org/en/latest/tutorials/faucet/ -robin ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] unexpected behavior in ovs faucet tutorial
Hi, Lee Thanks for your advice. I tried to use faucet 1.6.16 and modify faucet.yaml to be like this dps: switch-1: dp_id: 0x1 timeout: 3600 arp_neighbor_timeout: 3600 interfaces: 1: native_vlan: 100 2: native_vlan: 100 3: native_vlan: 100 4: native_vlan: 200 5: native_vlan: 200 vlans: 100: minimum_ip_size_check: False 200: minimum_ip_size_check: False After clean-up and re-entering ovs sandbox and restarting faucet, I still cannot get anything in diff-flows. On Tue, Jan 16, 2018 at 3:19 PM, Robin Lee wrote: > > > On Tue, Jan 16, 2018 at 3:04 PM, Hongwei Du wrote: >> >> Hi, >> >> I'm following the ovs faucet tutorial to get familiar with >> openvswitch. Everything goes smoothly until section Triggering MAC >> Learning. >> >> I tried the ovs-appctl ofproto/trace ... ... -generate command, but no >> new logs showed in inst/faucet.log, and diff-flows also gives nothing. >> >> I'm using ovs 2.8.90, can anybody help me troubleshooting this? >> ___ >> discuss mailing list >> disc...@openvswitch.org >> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > > Hi, Du > > This issue was just discussed in a recent talk[1]. > Basically you should upgrade faucet to 1.6.15, and modify faucet.yaml with > respect > to the updated tutorial text[2]. > > [1] > https://mail.openvswitch.org/pipermail/ovs-discuss/2018-January/045957.html > [2] http://docs.openvswitch.org/en/latest/tutorials/faucet/ > > -robin ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss