[ovs-discuss] Tx/Rx count not increasing OVS-DPDK
Hi Team I'm having 2 VMs running with ovs-dpdk as a networking agent on openstack compute node. When I'm checking the external connectivity of the VMs by pinging to the external world,the Tx/Rx count of the VMs is not increasing. However I'm able to ping the local-Ip of the respective Vms. Let me know the possible solution for this. Regards Abhishek Jain ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] 回复:Re: [ovs-dev] How to set QoS for VM egress traffic on tunnel mode
you can use linux tc filter u32 matching on packet data payload on physical output in this case. At 2017-11-29 02:40:07, "Ben Pfaff" wrote: >On Wed, Nov 22, 2017 at 09:50:54AM +, 王志克 wrote: >> Hi All, >> >> I want to set QoS with guide from below link “egress traffic shaping”, but >> do not know how for tunnel mode. >> http://docs.openvswitch.org/en/latest/faq/qos/ >> >> My scenario: >> >> I have several VM ports, and several VxLan ports in br0, and there is one >> seprate eth0 port (not in br0), which is the underlay port of Vxlan port. >> Currently I add rule to match VM traffic to certain Vxlan port, and all >> these vxlan ports would go out through eth0. >> >> Now I want to enable egress traffic shaping, eg: >> VM1 goes out with min_rate=10M, max_rate=100M. >> VM2 goes out with min_rate=50M, max_rate=200M. >> >> In the given example in http://docs.openvswitch.org/en/latest/faq/qos/ >> chapter “egress traffic shaping”, it directly uses the physical port. But in >> tunnel case, I can NOT specify the physical port directly. >> So how to configrue egress traffic shaping in tunnel case? Appreciate some >> example configruation. Thanks. > >You would want to configure shaping on the physical output port in this >case. >___ >discuss mailing list >disc...@openvswitch.org >https://mail.openvswitch.org/mailman/listinfo/ovs-discuss ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] [ovs-dev] How to set QoS for VM egress traffic on tunnel mode
On Wed, Nov 22, 2017 at 09:50:54AM +, 王志克 wrote: > Hi All, > > I want to set QoS with guide from below link “egress traffic shaping”, but do > not know how for tunnel mode. > http://docs.openvswitch.org/en/latest/faq/qos/ > > My scenario: > > I have several VM ports, and several VxLan ports in br0, and there is one > seprate eth0 port (not in br0), which is the underlay port of Vxlan port. > Currently I add rule to match VM traffic to certain Vxlan port, and all these > vxlan ports would go out through eth0. > > Now I want to enable egress traffic shaping, eg: > VM1 goes out with min_rate=10M, max_rate=100M. > VM2 goes out with min_rate=50M, max_rate=200M. > > In the given example in http://docs.openvswitch.org/en/latest/faq/qos/ > chapter “egress traffic shaping”, it directly uses the physical port. But in > tunnel case, I can NOT specify the physical port directly. > So how to configrue egress traffic shaping in tunnel case? Appreciate some > example configruation. Thanks. You would want to configure shaping on the physical output port in this case. ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Idea of an ovn native "rally"
On Thu, Nov 23, 2017 at 12:01:33PM +0100, Miguel Angel Ajo Pelayo wrote: > Today during coffee I was discussing with Jakub the idea of having > some sort of "rally" [1] [2] like project to measure the native reponse > of OVN at scale, measuring things like: > > * NB object creation to SB update > * Tap creation to SB port binding, and to connectivity. > * dnat NAT association to dnat connectivity > > * any other ideas? > > > This project has been specially helpful (in OpenStack) to detect race > conditions and bottlenecks. But I'm afraid that the OpenStack overhead > hide the real OVN numbers. I support adding some OVN testing, especially scale testing. There is a dormant ovn scale testing project that might be a place to start (I've never looked at it personally): https://github.com/openvswitch/ovn-scale-test ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] ovndb_servers can't be promoted
On Tue, Nov 28, 2017 at 2:29 PM, Hui Xiang wrote: > Hi Numan, > > > Finally figure it out what's wrong when running ovndb-servers ocf in my > environment. > > 1. There is no default ovnnb and ovnsb running in my environment, I > thought it should be started by pacemaker as the usual way other typical > resource agent do it. > when I create the ovndb_servers resource, nothing happened, no operation > is executed except monitor, which is really hard to debug for a while. > In the ovsdb_server_monitor() function, first it will check the status, > here, it will be return NOT_RUNNING, then in the ovsdb_server_master_update() > function, "CRM_MASTER -D" is being executed, which appears stopped every > following action, I am not very clear what work it did. > > So, do the ovn_nb and ovn_sb needs to be running previouly before > pacemaker ovndb_servers resource create? Is there any such documentation > referred? > > 2. Without your patch every nodes executing ovsdb_server_monitor and > return OCF_SUCCESS > However, the first node of the three nodes cluster is executed > ovsdb_server_stop action, the reason showed below: > <27>Nov 28 15:35:11 node-1 pengine[1897010]:error: clone_color: > ovndb_servers:0 is running on node-1.domain.tld which isn't allowed > Did I miss anything? I don't understand why it isn't allowed. > > 3. Regard your patch[1] > It first reports "/usr/lib/ocf/resource.d/ovn/ovndb-servers: line 26: > ocf_attribute_target: command not found ]" in my environment(pacemaker > 1.1.12) > Thanks. I will come back to you on your other points. The function "ocf_attribute_target" action must be added in 1.1.16-12. I think it makes sense to either remove "ocf_attribute_target" or find a way so that even older versions work. I will spin a v2. Thanks Numan The log showed same as item2, but I have seen very shortly different state > from "pcs status" as below shown: > Master/Slave Set: ovndb_servers-master [ovndb_servers] > Slaves: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld ] > There is no promote action being executed. > > > Thanks for looking and help. > > [1] - https://patchwork.ozlabs.org/patch/839022/ > > > > > > On Fri, Nov 24, 2017 at 10:54 PM, Numan Siddique > wrote: > >> Hi Hui Xiang, >> >> Can you please try with this patch [1] and see if it works for you ? >> Please let me know how it goes. But I am not sure, if the patch would fix >> the issue. >> >> To brief, the OVN OCF script doesn't add monitor action for "Master" >> role. So pacemaker Resource agent would not check for the status of ovn db >> servers periodically. In case ovn db servers are killed, pacemaker wont >> know about it. >> >> >> >> >> You can also take a look at this [1] to know how it is used in openstack >> with tripleo installation. >> >> [1] - https://patchwork.ozlabs.org/patch/839022/ >> [2] - https://github.com/openstack/puppet-tripleo/blob/master/ >> manifests/profile/pacemaker/ovn_northd.pp >> >> >> Thanks >> Numan >> >> On Fri, Nov 24, 2017 at 3:00 PM, Hui Xiang wrote: >> >>> Hi folks, >>> >>> I am following what suggested on doc[1] to configure the ovndb_servers >>> HA, however, it's so unluck with upgrading pacemaker packages from 1.12 to >>> 1.16, do almost every kind of changes, there still not a ovndb_servers >>> master promoted, is there any special recipe for it to run? so frustrated >>> on it, sigh. >>> >>> It always showed: >>> Master/Slave Set: ovndb_servers-master [ovndb_servers] >>> Stopped: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld ] >>> >>> Even if I tried below steps: >>> 1. pcs resource debug-stop ovndb_server on every nodes. ovn-ctl >>> status_ovnxb: running/backup >>> 2. pcs resource debug-start ovndb_server on every nodes. ovn-ctl >>> status_ovnxb: running/backup >>> 3. pcs resource debug-promote ovndb_server on one nodes. ovn-ctl >>> status_ovnxb: running/active >>> >>> With above status, the pcs status still showed as: >>> Master/Slave Set: ovndb_servers-master [ovndb_servers] >>> Stopped: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld ] >>> >>> >>> [1]. https://github.com/openvswitch/ovs/blob/master/Document >>> ation/topics/integration.rst >>> >>> Appreciated any hint. >>> >>> >>> >>> ___ >>> discuss mailing list >>> disc...@openvswitch.org >>> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss >>> >>> >> > ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] How to create a new bridge by API， not command line
Hi all, I want to create a new bridge by ovs. But I don't want to use command line in my program. So, is there some C language API to create it ? And is there a example or demo? I have read the website carefully, but not found it. THX.___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] ovndb_servers can't be promoted
Hi Numan, Finally figure it out what's wrong when running ovndb-servers ocf in my environment. 1. There is no default ovnnb and ovnsb running in my environment, I thought it should be started by pacemaker as the usual way other typical resource agent do it. when I create the ovndb_servers resource, nothing happened, no operation is executed except monitor, which is really hard to debug for a while. In the ovsdb_server_monitor() function, first it will check the status, here, it will be return NOT_RUNNING, then in the ovsdb_server_master_update() function, "CRM_MASTER -D" is being executed, which appears stopped every following action, I am not very clear what work it did. So, do the ovn_nb and ovn_sb needs to be running previouly before pacemaker ovndb_servers resource create? Is there any such documentation referred? 2. Without your patch every nodes executing ovsdb_server_monitor and return OCF_SUCCESS However, the first node of the three nodes cluster is executed ovsdb_server_stop action, the reason showed below: <27>Nov 28 15:35:11 node-1 pengine[1897010]:error: clone_color: ovndb_servers:0 is running on node-1.domain.tld which isn't allowed Did I miss anything? I don't understand why it isn't allowed. 3. Regard your patch[1] It first reports "/usr/lib/ocf/resource.d/ovn/ovndb-servers: line 26: ocf_attribute_target: command not found ]" in my environment(pacemaker 1.1.12) The log showed same as item2, but I have seen very shortly different state from "pcs status" as below shown: Master/Slave Set: ovndb_servers-master [ovndb_servers] Slaves: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld ] There is no promote action being executed. Thanks for looking and help. [1] - https://patchwork.ozlabs.org/patch/839022/ On Fri, Nov 24, 2017 at 10:54 PM, Numan Siddique wrote: > Hi Hui Xiang, > > Can you please try with this patch [1] and see if it works for you ? > Please let me know how it goes. But I am not sure, if the patch would fix > the issue. > > To brief, the OVN OCF script doesn't add monitor action for "Master" role. > So pacemaker Resource agent would not check for the status of ovn db > servers periodically. In case ovn db servers are killed, pacemaker wont > know about it. > > > > > You can also take a look at this [1] to know how it is used in openstack > with tripleo installation. > > [1] - https://patchwork.ozlabs.org/patch/839022/ > [2] - https://github.com/openstack/puppet-tripleo/blob/ > master/manifests/profile/pacemaker/ovn_northd.pp > > > Thanks > Numan > > On Fri, Nov 24, 2017 at 3:00 PM, Hui Xiang wrote: > >> Hi folks, >> >> I am following what suggested on doc[1] to configure the ovndb_servers >> HA, however, it's so unluck with upgrading pacemaker packages from 1.12 to >> 1.16, do almost every kind of changes, there still not a ovndb_servers >> master promoted, is there any special recipe for it to run? so frustrated >> on it, sigh. >> >> It always showed: >> Master/Slave Set: ovndb_servers-master [ovndb_servers] >> Stopped: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld ] >> >> Even if I tried below steps: >> 1. pcs resource debug-stop ovndb_server on every nodes. ovn-ctl >> status_ovnxb: running/backup >> 2. pcs resource debug-start ovndb_server on every nodes. ovn-ctl >> status_ovnxb: running/backup >> 3. pcs resource debug-promote ovndb_server on one nodes. ovn-ctl >> status_ovnxb: running/active >> >> With above status, the pcs status still showed as: >> Master/Slave Set: ovndb_servers-master [ovndb_servers] >> Stopped: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld ] >> >> >> [1]. https://github.com/openvswitch/ovs/blob/master/Document >> ation/topics/integration.rst >> >> Appreciated any hint. >> >> >> >> ___ >> discuss mailing list >> disc...@openvswitch.org >> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss >> >> > ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
