Doing some testing of a new "ovs" build functionality built-in to Orabuntu-LXC
which allows Orabuntu-LXC to be used purely as a tool for testing building and
upgrading OpenvSwitch from source on RedHat-family Linux flavors and distros.
This mode of Orabuntu-LXC bypasses all the container
Hi Ben, thanks!
Well that solves my problem anyway. Prior to this "ovs" mode option,
Orabuntu-LXC deployed a container landscape complete with OpenvSwitch RPM
deployment and configuration of switches, and that was it. Any upgrade to
OpenvSwitch was basically in the hands of the owner of the
Hi, good to hear from you. Thanks for maintaining OVS on Orabuntu-LXC.
I took a look at the OVS scripts. The ovs-version gets set in the
database at the step where ovs-ctl prints out "Configuring Open vSwitch
system IDs". This happens just after starting ovsdb-server. If the
upgrade process
Performance should not be impacted if you run OVS as described in
https://github.com/servicefractal/ovs . The document does not refer to
DPDK explicitly. But, if the same logic does not work for DPDK enabled
ports, please let me know.
thanks
/Shivaram
On Thu, Oct 24, 2019 at 11:35 PM Vishal
Hi,
Does anyone know of any performance impact of running OVS + DPDK in a docker
container environment v/s running it on bare-metal ?
Are there any known functional limitations when running inside a container ?
We primarily use "netdev" bridges with "vhostuserclient" ports to connect to
guest
