Open Stack

Quick updates:

- All FFEs patches have been merged except:
https://review.openstack.org/#/c/330050/ - so we're green on this
side.
- Upgrade team is still working on automation to upgrade from newton to ocata.
- ovb-updates (CI job with IPv6) doesn't pass -
https://bugs.launchpad.net/tripleo/+bug/1663187 - See
https://review.openstack.org/#/c/432761/ for a potential fix.
- our CI is testing OpenStack from trunk, we have regular promotions.

At this stage, I believe we can release TripleO Ocata RC1 by Thursday
17th, considering Congress will be landed, 1663187 fixed, no new
blocker in CI.

I think upgrade folks will still have some patches after Thursday, but
I don't think it's a big deal, we'll just backport them to
stable/ocata.

Please let us know asap if you see more blockers for Ocata RC1.

On Mon, Feb 6, 2017 at 9:19 AM, Emilien Macchi <emilien at redhat.com> wrote:
> I found useful to share the reasons why we didn't release TripleO RC1
> last week and what are the remaining blockers.
>
> - Nova from trunk doesn't work for TripleO. We have to pin Nova to
> ocata-3 if we want to continue the promotions in our CI.
>
> Some work is in progress to solve this problem, you can follow it here:
> https://review.openstack.org/#/q/status:open+topic:bug/1661360
>
> TL;DR: we're disabling Nova API in WSGI with Apache when deploying
> TripleO & Puppet OpenStack CI.
>
> - Fix updating images in promotion pipeline:
> https://review.openstack.org/#/c/429713
>
> - Upgrades from Newton to Ocata. The list of bugs / work in progress
> is still consequent, it doesn't make sense to release before we have
> them fixed. Composable upgrades are our essential blueprint for Ocata.
>
>
> I proposed https://review.openstack.org/#/c/428416/ to prepare TripleO
> RC1 but I won't update it before our blockers are solved.
>
> Any help, feedback or question is very welcome.
> Thanks,
> --
> Emilien Macchi



-- 
Emilien Macchi