Hey Greg,
Thank you for the detailed update.
I will work on a work-around.
Thank you for the support!
-
Keerthana
On Thu, Apr 11, 2019 at 10:54 PM Gregory Rose wrote:
>
>
> On 3/27/2019 10:33 PM, Ammu wrote:
>
> Hi Greg,
>
> *ens256:*
>
>- Source interface which is intended to receive al
Hi, all
I want to run pktgen with ovs, and I follow some tutorials in the network
but I ran into some problems related to socket ID:
Copyright (c) <2010-2019>, Intel Corporation. All rights reserved. Powered
by DPDK
EAL: Detected 6 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /v
On Mon, Apr 01, 2019 at 06:39:46PM +, Ian Hu wrote:
> I saw threads from 2015/2016 about doing MSS clamping using OVS, but
> the general answer at the time was it was not doable. We are currently
> using iptables to do MSS clamping, but I am wondering if anything has
> changed since then and wh
On 4/3/2019 5:15 PM, Tobias Hofmann -T (tohofman - AAP3 INC at Cisco) wrote:
Sorry I just accidentally sent out the last mail too early...
Hi Ian,
To answer your questions, I just reproduced the issue on my system:
What commands have you used to configure the hugepage memory on your
On Mon, Apr 01, 2019 at 04:12:48PM +0200, Premysl Kouril wrote:
> We have upgraded to new version of OpenStack and with new OVS (2.11) we see
> that for some reason - the OVS installs drop rule which drops traffic from
> our DHCP server towards virtual machine. I've checked all open-flow rules
> in
Hello
When sysconfig OVS_USER_ID is changed to a different user, it requires
a manual ownership change of the OVS conf.db database if existing or
otherwise ovsdb-server will fail to (re)start. I was wondering if I am
missing any particular reason why this is change of ownership is not
automaticall
On Tue, Apr 16, 2019 at 11:32:21PM +0200, Jaime Caamaño Ruiz wrote:
> When sysconfig OVS_USER_ID is changed to a different user, it requires
> a manual ownership change of the OVS conf.db database if existing or
> otherwise ovsdb-server will fail to (re)start. I was wondering if I am
> missing any
We have a lot of tracing tools, at multiple levels. I wonder whether
they are documented adequately. I tried to document them by example in
the OVN OpenStack tutorial
(e.g. http://docs.openvswitch.org/en/latest/tutorials/ovn-openstack/),
but it is not exactly a how-to guide. Maybe someone could
> On any given system, I would expect ovsdb-server to run as the same
> user
> every time. Is there a reason to sometimes use a different user?
Well, changing from root which was the only supported option in the
past and current default to a different user (like the suggested
openvswitch), this o
OK, that seems reasonable, I'll look forward to the patch.
On Wed, Apr 17, 2019 at 12:35:48AM +0200, Jaime Caamaño Ruiz wrote:
> > On any given system, I would expect ovsdb-server to run as the same
> > user
> > every time. Is there a reason to sometimes use a different user?
>
> Well, changing
On Tue, 16 Apr 2019 at 15:36, Jaime Caamaño Ruiz wrote:
>
> > On any given system, I would expect ovsdb-server to run as the same
> > user
> > every time. Is there a reason to sometimes use a different user?
>
> Well, changing from root which was the only supported option in the
> past and curren
On Tue, 16 Apr 2019 at 16:11, Ansis Atteka wrote:
>
> On Tue, 16 Apr 2019 at 15:36, Jaime Caamaño Ruiz wrote:
> >
> > > On any given system, I would expect ovsdb-server to run as the same
> > > user
> > > every time. Is there a reason to sometimes use a different user?
> >
> > Well, changing fro
On Tue, Apr 16, 2019 at 04:11:44PM -0700, Ansis Atteka wrote:
> On Tue, 16 Apr 2019 at 15:36, Jaime Caamaño Ruiz wrote:
> >
> > > On any given system, I would expect ovsdb-server to run as the same
> > > user
> > > every time. Is there a reason to sometimes use a different user?
> >
> > Well, cha
My intention was doing it at systemd unit (prestart) for file conf.db
(and .conf.db.~lock~ that stays around) only.
I was not thinking on absolutely fool proof mechanism, among other
things because the admin might have customized the location for the
database. Also, updating and restarting the ser
On Tue, 16 Apr 2019 at 17:20, Jaime Caamaño Ruiz wrote:
>
> My intention was doing it at systemd unit (prestart) for file conf.db
> (and .conf.db.~lock~ that stays around) only.
You also need to chown /var/log/openvswitch.*.log files.
>
> I was not thinking on absolutely fool proof mechanism, amo
15 matches
Mail list logo
