Open Stack

On Thu, Feb 2, 2017 at 7:00 AM, Dan Radez <dradez at redhat.com> wrote:
> I'd like to request a feature freeze exception to add Congress to
> Triple-o. This work is mostly already done. The puppet-tripleo work is
> already merged and the puppet-congress work is complete.

It would be great to have to test Congress in Puppet OpenStack scenarios:
https://github.com/openstack/puppet-openstack-integration

Like we already do for most other services.

It seems like Congress has some Tempest tests:
https://github.com/openstack/congress/tree/master/congress_tempest_tests

So we would be able to deploy Congress on scenario004 maybe (or
scenario001 like you did in TripleO Scenarios) and run Tempest to make
sure the Puppet module is working well.

> https://blueprints.launchpad.net/tripleo/+spec/congress-service-integration
>
> We hit a packaging snag when adding dependencies to Fedora. The fedora
> review is currently waiting for a Fedora Packaging Exception.
> https://bugzilla.redhat.com/show_bug.cgi?id=1407000
>
> RDO plans to package this dependency before we get a response from the
> FPE so that work is not stalled. This work is on deck to be completed.
>
> Once the Dep is packaged the openstack-congress packaging can be completed:
> https://review.rdoproject.org/r/4487
>
> Once the packaging is completed the final patches can land to complete
> the work.
> https://review.openstack.org/#/c/330050/
> and a tripleo-puppet-elements change to add the package.
>
>
> I believe that this work could be completed within a week as long as RDO
> is able to complete the Dep packaging work. All the pieces are mostly
> sitting waiting to be completed.

Yeah, just keep in mind RDO is also very busy on other Ocata blockers
during the release time, that's why we block new features, because we
have many bugs coming during this time.
I'm adding apevec so he can maybe weight on it.

> Thanks,

Waiting for Alan to give -1/+1 on the RDO side, but it's a +1 for me
on the TripleO side.
-- 
Emilien Macchi