On Tue, Jun 07, 2016 at 02:29:32AM +, Maurice Qureshi wrote:
> I wanted to find out QOS capabilities of OVS and found this link:
>
> https://github.com/openvswitch/ovs/blob/master/FAQ.md
>
> Wanted to make sure that the QOS section in this FAQ is up to date and
> that OVS derives its QOS func
Hi John,
I do not know any better approach, I think it is good to write all the
parameters in the creation of a port chain, this can avoid saving many
data in northbound db which are not used. We can do it in that way
currently, if the community has opposite ideas, we can change, what do you
t
I wanted to find out QOS capabilities of OVS and found this link:
https://github.com/openvswitch/ovs/blob/master/FAQ.md
Wanted to make sure that the QOS section in this FAQ is up to date and that OVS
derives its QOS functionality from Linux.
Thanks
Maurice
__
On Mon, Jun 6, 2016 at 8:33 AM, Christophe VILLA wrote:
> Hello,
>
> i use ovs 2.0.2 on Ubuntu 14.04 with kvm and run well.
>
> I have install on Ubuntu 16.04 with ovs 2.5.0 and i can not see virtual
> interface directly on ubuntu 16.04.
> The interfaces are present in ovs configuration but no app
If anyone else is interested in knowing how to fetch the payload info from
packetOut, create an object for ofputil_packet_out (eg:po). Use
ofputil_decode_packet_out to decode the packet and use the object with
attributes of structure ofputil_packet_out to get any packetOut related
information.
> On Jun 6, 2016, at 8:02 AM, Ben Pfaff wrote:
>
> On Mon, Jun 06, 2016 at 02:33:19PM +, Cristina Palomo Regidor wrote:
>> I read that nat is not currently supported by openvswitch.
>> Would this command somehow perform the behavior of nat?
>> ovs-ofctl add-flow br1 nw_dst=192.168.2.2,idle_t
I'm having a problem setting up the VMs like they are in the diagram. The
problem is that VM2 and VM1 aren't assigned IPs by the DHCP server unlike
the third VM(Open vSwitch VM) since it's connected to eth0. I want to ping
VMs 1 and 2 from the third VM.
_
Hello,
i use ovs 2.0.2 on Ubuntu 14.04 with kvm and run well.
I have install on Ubuntu 16.04 with ovs 2.5.0 and i can not see virtual
interface directly on ubuntu 16.04.
The interfaces are present in ovs configuration but no appear with ifconfig.
It's embarrasing when i want use virtual interface
sdavis writes:
>
> Greetings!
>
> I’ve installed OVS with some NSH patches using these instructions:
> https://github.com/yyang13/ovs_nsh_patches/blob/master/README.md. I ended
up building an rpm
> from the resulting package and installed from that. Here’s version output:
>
> [root prv-10-11-
On Sat, Jun 04, 2016 at 11:31:58AM +0800, 张晨 wrote:
> I'm wondering how gre tunnel is implemented in OVS, in the l2gre or
> the nvgre? And if it is implemented in l2gre, then what does the
> tunnel_id field mean for l2gre, where could i find the standard file?
OVS follows the RFCs for GRE, e.g. RF
Juno,
Let me check – my intention was that the networking-sfc OVNB driver would
configure all aspects of the port-chain and add the parameters to the
networking-sfc db. Once all the parameters were in the creation of a port-chain
would call networking-ovn (passing a deep copy of the port-chain
Juno,
I was going to take a pass at 3 today to see if I can get a working use case
before I submit the patches.
On 1 I will reach out to the networking-sfc team to get the design spec started.
I will start looking at how to get the patches submitted too.
So with your and Srilatha’s help I think
On Mon, Jun 06, 2016 at 02:33:19PM +, Cristina Palomo Regidor wrote:
> I read that nat is not currently supported by openvswitch.
> Would this command somehow perform the behavior of nat?
> ovs-ofctl add-flow br1 nw_dst=192.168.2.2,idle_timeout=0,
> mod_nw_dst:172.16.121.2,output:0
If that's
On Mon, Jun 06, 2016 at 10:33:54AM +0200, Vasileios Kotronis wrote:
> Hello,
>
> I would like to ask how one can bond two or more interfaces that already
> exist within an ovs bridge.
> The following command, that tries to bond together two physical system
> interfaces that belong to
> bridge sw
Hello,
I read that nat is not currently supported by openvswitch.
Would this command somehow perform the behavior of nat?
ovs-ofctl add-flow br1 nw_dst=192.168.2.2,idle_timeout=0,
mod_nw_dst:172.16.121.2,output:0
Thanks and BR/
Cristina
___
discuss mai
Hi John,
One question need confirm with you, I think the ovn flow classifier driver
and ovn port chain driver should call the APIs which you add to
networking-ovn to configure the northbound db sfc tables, right? I see
your networking-sfc ovn drivers, they does not call the APIs you add to
net
## - ##
## openvswitch 2.5.1 test suite. ##
## - ##
testsuite: command line was:
$ ./tests/testsuite -C tests AUTOTEST_PATH=utilities:vswitchd:ovsdb:vtep:tests::ovn/controller-vtep:ovn/northd:ovn/utilities:ovn/controller 953
## -
2.5.1~git20160606.ad4801b
/me figured today was a good date to do some test builds
== powerpc (big endian) ==
ofproto-dpif - flow translation resource limits
953: ofproto-dpif - in place modification (vlan) FAILED
(ofproto-dpif.at:7237)
== s390x ==
ofproto-dpif - flow translation resourc
Hi again!
I followed the instructions in INSTALL.SSL.md
1)created the PKI structure by
ovs-pki init
2)created the private key and certificates for ovsdb-client and server
% ovs-pki req+sign ctl controller
% ovs-pki req+sign sc switch
3)copied controllerca/cacert.pem , sc-privkey.pem and sc-
Hello,
I would like to ask how one can bond two or more interfaces that already exist
within an ovs bridge.
The following command, that tries to bond together two physical system
interfaces that belong to
bridge switch_c fails:
# ovs-vsctl add-bond switch_c bond0 peth6 peth7
ovs-vsctl: cannot c
20 matches
Mail list logo
