Open Stack

On Wed, Mar 09, 2016 at 10:56:04PM +0000, Andrew Woodward wrote:
> Issue: moving to puppet-openstack on master has exposed fuel-library
> to breakage and there are many concerns about changes landing that can
> break it.
> 
> Alex S. Proposed that we continue the course, and finish setting up
> Check voting on the relevant puppet-openstack modules - The
> participants agreed with this

Since many people came up with different assumptions about how the CI
duty for Fuel CI for Puppet OpenStack is supposed to work, I've created
a wiki page with a proposed definition of the process:
https://wiki.openstack.org/wiki/Fuel/CI/Puppet_OpenStack_CI_duty

Please read, comment, and add more details as needed.

Please also review and comment on the spec from Igor Belikov:
https://review.openstack.org/286731

> Action: Sergii G & Aleksandra Fedorova will propose needed changes to
> project-config to add tests
> 
> Issue: closing the regressions gap until fuel-ci votes on
> puppet-openstack check
> 
> It was proposed that we invent a system that holds back the versions
> nightly, and after completion of automated testing; It can
> automatically move it forward.
> 
> Action: There was no consensus on this and should be discussed here
> further on this thread.

In the meanwhile, Alex has proposed a fuel-library change that would
record the commit ids of the Puppet OpenStack modules it was built with:
https://review.openstack.org/288768

Merging this would enable us to implement Aleksandra's proposal of using
the versions of Puppet OpenStack modules that have most recently passed
BVT to verify commits to fuel-library and other Fuel components covered
with deploy tests.

-- 
Dmitry Borodaenko