Hello Mr. O'Reilly,
Thanks for your reply.
I managed to get around the issue by editing the .xml file of each virtual
machine adding the following code in the interface section of the vports:
It is necessary to delete the following line (vportx is whatever name you
gave
On Wed, Jan 24, 2018 at 01:54:32PM -0500, John Lester wrote:
> What would be the way to express in a flow: match all vlans except vlan
> 405. Would it be vlan_vid=0/405 or perhaps another way?
That approach won't work.
The simplest way is to use two flows: one with a high priority that
matches
Maybe. Sometimes it's too hard to keep track of changes just by looking
at the flow.
On Wed, Jan 24, 2018 at 08:18:12PM +0100, Alan Kayahan wrote:
> Thanks for bearing with me so far Ben. I will post my experience in
> creating a custom action and match step by step like some others have done
>
That video is using VirtualBox. The error mentions macvtap – I think the GUI
should allow you to add the tap as a virtio.
From: ovs-discuss-boun...@openvswitch.org
[mailto:ovs-discuss-boun...@openvswitch.org] On Behalf Of ?
Sent: 24 January 2018 09:26
To: ovs-discuss@openvswitch.org
Hello, thanks for your attention.
I would like to kindly request support/advice/feedback about an issue that
I am having with the Virtual Machine Manager and OpenVSwitch.
I am deploying 7 Virtual Machines (Virtual Machine Manager 1.4.1, CentOS 7)
and need to connect them to an OpenVSwitch
hi all:
I have a question about the use of ovn-loadblace,
how about using ovn-loadblance to work with haproxy in openstack-lbaas, and
ovn-loadblance acts as level4(ip+port), while haproxy acts as level7 ?
Will this method work well?
Thanks.___
Hi Kevin,
My primary concern is that someone upgrading to OVS2.9 may find that
configurations that were previously working fine no longer do because the
memory dimensioned for OVS may not be sufficient. It could be argued that since
the shared mempool method allocates a fixed number of buffers
