sts.opnfv.org>
Sent: Wednesday, September 7, 2016 11:22:18 AM
Subject: Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][hackfest]
Release Milestone Review presentation
This is absolutely one of the value-adds that OPNFV brings to the table – very
much in line w
le...@lists.opnfv.org>;
TECH-DISCUSS OPNFV
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][hackfest]
Release Milestone Review presentation
It feels like perhaps we need a more nuanced
Hi Heather,
Please see inline.
Tim Rozet
Red Hat SDN Team
- Original Message -
From: "Heather Kirksey"
To: "Tim Rozet"
Cc: "David McBride" ,
opnfv-project-le...@lists.opnfv.org, "Christopher Price"
It feels like perhaps we need a more nuanced understanding of what we mean
by our "use" of upstream components. If I am understanding some of the
conversations correctly, Be might be more generally overall stable, but
doesn't enable key capabilities (or has higher instability) around VPN and
SFC
I don't see any issue here. Colorado 1.0 is set to use Beryllium, which is
already released. Even the scenarios that require Boron (FDS/SFC) do not
require ODL HA, and we already have Boron RC builds that work. ODL HA is known
to be buggy, so at least in Apex we don't enable it.
Tim Rozet