Hi Salvatore,
On 03/04/2014 14:56, Salvatore Orlando wrote:
Hi Simon,
snip
I hope stricter criteria will be enforced for Juno; I personally think
every CI should run at least the smoketest suite for L2/L3 services (eg:
load balancer scenario will stay optional).
I had a little thinking
Hi Simon,
You are absolutely right in your train of thoughts: unless the
third-party CI monitors and vets all the potential changes it cares
about there's always a chance something might break. This is why I
think it's important that each Neutron third party CI should not only
test Neutron
Hi,
I'm looking at [1] but I see no requirement of which Tempest tests
should be executed.
In particular, I'm a bit puzzled that it is not mandatory to boot an
instance and check that it gets connected to the network. To me, this is
the very minimum for asserting that your plugin or driver is
Hi Simon,
I agree with your concern.
Let me point out however that VMware mine sweeper runs almost all the smoke
suite.
It's been down a few days for an internal software upgrade, so perhaps you
have not seen any recent report from it.
I've seen some CI systems testing as little as
I agree 100% on this in fact. One of the other concerns I have with
the existing 3rd party
CI systems is that, other than the audit review Salvatore mentions,
who is ensuring
they continue to run ok? Once they've been given voting rights, is
anyone auditing these
to ensure they continue to
Thanks Salvatore and Kyle for your feedback.
Kyle, you're right, my question has been kicked off by the ML2 ODL bug.
I didn't want to point fingers but rather understand the mid/long-term
plan for 3rd party testing. I'm happy to see that this is taken into
account and hopefully the Juno cycle
