On Sat, 20 Oct 2018 at 01:37, Gregory Rose wrote:
>
> On 10/18/2018 10:28 PM, Yousong Zhou wrote:
> > On Fri, 19 Oct 2018 at 01:13, Gregory Rose wrote:
> >> On 10/17/2018 6:01 AM, Yousong Zhou wrote:
> >>
> >> I tried to use ip-over-gre with openvswitch 2.8.4, but no "ip proto
> >> 47" traffic
On Fri, Oct 19, 2018 at 07:26:14PM +, Srinivas via discuss wrote:
> Hello all,We are starting with ovs and want to use it as
> a) a L2 switch with vlan tagging on the guest vm ports.b) no openflow rules
> will be configured.c) We will have 4 -5 bridges created on the system with
> each
Hello all,We are starting with ovs and want to use it as
a) a L2 switch with vlan tagging on the guest vm ports.b) no openflow rules
will be configured.c) We will have 4 -5 bridges created on the system with each
bridge having a corresponding bond interface along with the guest vtap's.
Given
Hi,
On Mon, Oct 08, 2018 at 11:52:24AM +0200, Andrzej Ostruszka wrote:
> First of all thank you Flavio for your reply and sorry for late reply
> but I had to switch to something else. Now I resume my ovs ramp up and
> have some additional problems.
>
> My goal is actually to measure performance
On Fri, Oct 19, 2018 at 02:53:53PM -0300, Flavio Leitner wrote:
> On Fri, Oct 19, 2018 at 08:23:37AM -0700, Ben Pfaff wrote:
> > On Fri, Oct 19, 2018 at 11:48:07AM +, Stokes, Ian wrote:
> > > > On 10/18/2018 10:46 PM, Ben Pfaff wrote:
> > > > > I've had a number of queries from folks lately
On Fri, Oct 19, 2018 at 08:23:37AM -0700, Ben Pfaff wrote:
> On Fri, Oct 19, 2018 at 11:48:07AM +, Stokes, Ian wrote:
> > > On 10/18/2018 10:46 PM, Ben Pfaff wrote:
> > > > I've had a number of queries from folks lately about our roadmap for
> > > > LTS releases. It has, indeed, been a long
On 10/18/2018 10:28 PM, Yousong Zhou wrote:
On Fri, 19 Oct 2018 at 01:13, Gregory Rose wrote:
On 10/17/2018 6:01 AM, Yousong Zhou wrote:
I tried to use ip-over-gre with openvswitch 2.8.4, but no "ip proto
47" traffic can be seen with tcpdump. Later I added a WARN_ON_ONCE(1)
line just before
Hello,
I migrated all instanced from “high cpu usage ovs” node to another node to
avoid unexpected packet drop.
When migration was finished, ovs-vswitchd was crashed suddenly.
console logs when ovs-vswitchd was crashed
/usr/local/bin/start-ovs: line 2:16 Segmentation fault
Hello,
I want to report an issue that ovs-vswitchd high CPU usage after attaching new
port.
Please see following informations.
The most important parts of your bug report are the following:
* What you did that make the problem appear.
* Neutron openvswitch agent added 4 ports on
On Fri, Oct 19, 2018 at 11:48:07AM +, Stokes, Ian wrote:
> > On 10/18/2018 10:46 PM, Ben Pfaff wrote:
> > > I've had a number of queries from folks lately about our roadmap for
> > > LTS releases. It has, indeed, been a long time since we've had a
> > > long-term support release (the current
> On 10/18/2018 10:46 PM, Ben Pfaff wrote:
> > I've had a number of queries from folks lately about our roadmap for
> > LTS releases. It has, indeed, been a long time since we've had a
> > long-term support release (the current LTS is 2.5). Usually, we've
> > done LTS releases before some kind
On 10/18/2018 10:46 PM, Ben Pfaff wrote:
> I've had a number of queries from folks lately about our roadmap for LTS
> releases. It has, indeed, been a long time since we've had a long-term
> support release (the current LTS is 2.5). Usually, we've done LTS
> releases before some kind of big
12 matches
Mail list logo
