On Fri, Apr 03, 2015 at 08:06:12PM -0700, Sabyasachi Sengupta wrote:
> By "certification" I meant any pre-release testing that you must be doing
> before releasing a new version of ovs, nothing beyond that.. Its fair to
> assume that this would be the starting point for many who are using this
> so
Ben,
By "certification" I meant any pre-release testing that you must be doing
before releasing a new version of ovs, nothing beyond that.. Its fair to
assume that this would be the starting point for many who are using
this software. That is, go ahead and grab the latest released version. It
I recommend building a kernel module from master.
New features, such as support for new kernels, are always added on
master first. Periodically we branch to a release branch, and then
release that branch after allowing some time to report and fix bugs.
We do not certify any version of OVS for an
Well, the last released version of ovs-2.3.1 was in Dec/03/2014 (per NEWS)
and there is no formal plan discussed about ovs-2.4 in any of the mailing
lists. I see there is ovs-2.3.2 documented in NEWS with xxx suggesting there
will be a release sometime in future. Unless there is a certified an
On Fri, Apr 03, 2015 at 12:46:45PM -0700, Joe Stringer wrote:
> OVS userspace can work with the OVS kernel module distributed with the
> kernel. This provides a straightforward workaround.
>
> I don't understand the comment about updating the FAQ/NEWS version
> matrix. It already states that 2.3 s
OVS userspace can work with the OVS kernel module distributed with the
kernel. This provides a straightforward workaround.
I don't understand the comment about updating the FAQ/NEWS version
matrix. It already states that 2.3 supports Linux 2.6.32 to 3.14, and
explicitly mentions that modified kern
Thanks. A patch off branch-2.3 will certainly help as 2.3.1 the latest
released OVS version and it would be nice to see it compatible with latest
Centos official distro. Can you also update the FAQ/NEWs version matrix?
On Thu, 2 Apr 2015, Joe Stringer wrote:
I pushed a fix to master for wha
I pushed a fix to master for what looks like the corresponding RHEL7
kernel last week (I didn't backport this to 2.3, was I meant to?):
https://github.com/openvswitch/ovs/commit/13dd4a9738e99684a56b10ce2f1a5ee2d2ec2f9f
On 1 April 2015 at 16:57, Ben Pfaff wrote:
> Seems likely.
>
> For new kernel
Seems likely.
For new kernels, make sure you're building master.
On Wed, Apr 01, 2015 at 04:46:54PM -0700, Sabyasachi Sengupta wrote:
>
> ovs from master branch off github does not build in C7.1. There are
> quite a few errors in datapath directory, was hoping if a patch was
> already available.
ovs from master branch off github does not build in C7.1. There are quite a
few errors in datapath directory, was hoping if a patch was already
available. Probably no one tried it yet?
---
Nuage Networks Business Unit, Alcatel-Lucent,
755 Ravendale Drive, Mountain View, CA, 94043
Mailstop: 11
Does it build? Then I imagine it's supported.
On Wed, Apr 01, 2015 at 01:44:41PM -0700, Sabyasachi Sengupta wrote:
>
> Can anyone respond to this question? I can provide a patch for enabling the
> 3.10.229 kernel (backported from native Linux) if one is not already
> available..
>
> On Mon, 30
Can anyone respond to this question? I can provide a patch for enabling the
3.10.229 kernel (backported from native Linux) if one is not already
available..
On Mon, 30 Mar 2015, Sabyasachi Sengupta wrote:
Hi,
Can anyone please let me know if Centos 7.1 (3.10.0-229) kernel supported in
mas
Hi,
Can anyone please let me know if Centos 7.1 (3.10.0-229) kernel supported in
master branch? I'm currently based off branch-2.3. If this is already
available, what would be the commit hash(es) to be picked up?
Thanks,
Sabya
___
dev mailing list
13 matches
Mail list logo
