So, longer term, I'd really like to see a set of smaller pieces of gate'ness
that co-check each other.
one gate that periodically checks that kolla:trunk builds (nightly?) sans
modification. As the containers themselves depend on a lot of
packages/repositories outside of kolla's control and therefore can break at any
time. These would be ran against the kolla-ansible/kolla-kubernetes trunk gate
checks. showing bugs in the potentially changing containers against known good
deployment tests.
A similar periodic check should be done for kolla-ansible/kolla-kubetes gates
to ensure things like a new version of kubeadm getting released doesn't break
things, and cause the other gate checks to produce misleading failures.
The results of the periodic gates, should be cached somewhere and used as input
to the kolla-ansible and kolla-kubernetes gates used to check incoming reviews.
You can then rely more on breakages in kolla-ansible/kolla-kubernetes gate
checks being actually caused by the patches incoming, and not some outside
influence.
This should make it much quicker to iterate though issues.
Thanks,
Kevin
________________________________________
From: Steven Dake (stdake) [std...@cisco.com]
Sent: Tuesday, November 29, 2016 6:48 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [kolla] Kolla-ansible is available
It’s not really about easy or hard.
We don’t want to make the gating less optimal then it was pre-repo split. To
achieve that objective, cross-repo gating is necessary to validate the images
in the docker repo are correct wrt the orchestration system they were developed
against originally (which has moved off into the kolla-ansible repository).
Hope that clears it up.
Regards
-steve
-----Original Message-----
From: Joshua Harlow <harlo...@fastmail.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Date: Tuesday, November 29, 2016 at 11:28 AM
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [kolla] Kolla-ansible is available
I would expect nothing less, things that are worthwhile doing are
usually not just (always) easy :)
Jeffrey Zhang wrote:
> If we can implement loose coupling, there will be optimal. But
> it is hard to do this.
>
> On Tue, Nov 29, 2016 at 2:50 PM, Joshua Harlow <harlo...@fastmail.com
> <mailto:harlo...@fastmail.com>> wrote:
>
> Jeffrey Zhang wrote:
>
> Because the role and dockerfile are tight couplings.
>
> For example, the container/Dockerfile may need an environment
> variable
> passed by ansible role. without it, the service may not work.
>
>
> Why do they need to be tightly coupled?
>
>
>
>
__________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>
>
>
>
> --
> Regards,
> Jeffrey Zhang
> Blog: http://xcodest.me <http://xcodest.me/>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
