[openstack-dev] [3rd party testing] How to setup CI? Take #2

Luke Gorrie luke at snabb.co
Tue Mar 4 15:31:52 UTC 2014

Hi Jay,

(Switching Subject to third party testing)

On 4 March 2014 15:13, Jay Pipes <jaypipes at gmail.com> wrote:

> Let me know how we can help you!

Thanks for the invitation! I will take you up on it :-).

My goal is to make sure the Tail-f NCS mechanism driver is fully supported
in Icehouse.

Question: How should I setup CI?

Option 1: Should I debug the CI implementation we developed and tested back
in December, which was not based on Tempest but rather on our private
integration test method that we used in the Havana cycle? The debugging
that is needed is more defensive programming in our automated attempt to
setup OpenStack for test -- so that if the installation fails for some
unexpected reason we don't vote based on that.

Option 2: Should I start over with a standard Tempest test insead? If so,
what's the best method to set it up (yours? Arista's? another?), and how do
I know when that method is sufficiently debugged that it's time to start?

I was on the 3rd party testing meeting last night (as 'lukego') and your
recommendation for me was to hold off for a week or so and then try your
method after your next update. That sounds totally fine to me in principle.
However, this will mean that I don't have a mature test procedure in place
by March 14th, and I'm concerned that there may be bad consequences on
this. This date was mentioned as a deadline in the Neutron meeting last
night, but I don't actually understand what the consequence of
non-compliance is for established drivers such as this one.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140304/df28869c/attachment.html>

More information about the OpenStack-dev mailing list