8:26 a.m.
Everyone involved: are we shipping OVS 2.6.x for >= Ocata only or is
this meant to be distributed across all maintained stable releases ?
I felt like the understanding was that it was only meant for >= Ocata
but I could be wrong.
Need an answer ASAP.
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Tue, Feb 7, 2017 at 5:40 PM, Flavio Leitner <fbl(a)redhat.com> wrote:
On Mon, Jan 30, 2017 at 06:20:43AM -0500, Assaf Muller wrote:
> On Sun, Jan 29, 2017 at 2:13 PM, Alan Pevec <apevec(a)redhat.com> wrote:
> >
> > On Jan 29, 2017 2:18 PM, "Assaf Muller" <assaf(a)redhat.com>
wrote:
> >
> > Indeed Terry reproduced the issue, we got in contact with Flavio, he
> > knows what's going on and we're waiting on a fix and a new 2.6 build.
>
> Ack.
2.6 build with the fix available.
https://bugzilla.redhat.com/show_bug.cgi?id=1419632#c1
Thanks,
--
Flavio
9:40 a.m.
New subject: [rdo-list] Shipping OVS 2.6?
On Wed, Feb 22, 2017 at 9:26 AM, David Moreau Simard <dms(a)redhat.com> wrote:
Everyone involved: are we shipping OVS 2.6.x for >= Ocata only or
is
this meant to be distributed across all maintained stable releases ?
I felt like the understanding was that it was only meant for >= Ocata
but I could be wrong.
Need an answer ASAP.
From my perspective, OVS 2.6 for >= Ocata only, not older releases.
I'd also like to see us get on a cadence where we are updating OVS every
cycle. So, we should also expect:
Pike with OVS 2.7
Q with OVS 2.8
etc.
--
Russell Bryant
2838
days inactive
2838
days old
1 comments
2 participants
participants (2)
-
David Moreau Simard -
Russell Bryant