[openstack-dev] [QA] Tempest blueprints status update and rationale, input demanded

Sean Dague sean at dague.net
Wed Dec 11 20:19:34 UTC 2013

First, thanks for this! Much appreciated.

On 12/11/2013 07:44 AM, Giulio Fidente wrote:
> hi,
> I'm attempting to rationalize on the status of tempest blueprints. I
> need your help so I organized questions in a few open points.
> * (1) I'm looking for input here on the actual status of the following
> blueprints, which are already approved or in a good progress state:
> https://blueprints.launchpad.net/tempest/+spec/add-basic-heat-tests
> seems done, shall we close it? (steve baker)
> https://blueprints.launchpad.net/tempest/+spec/fail-gate-on-log-errors
> seems done, shall we close it? (david kranz)

I'm happy closing this one, but I think we need a follow up about
actually closing out the logging errors. We should have a pretty
discreet count of what's in the white list. And how big the white list
is every week is something I think we should bring to the meeting.

> https://blueprints.launchpad.net/tempest/+spec/config-cleanup
> https://blueprints.launchpad.net/tempest/+spec/config-verification
> seems done, close? (mtreinish)
> https://blueprints.launchpad.net/tempest/+spec/fix-gate-tempest-devstack-vm-quantum-full
> old but still valid for icehouse, what is the real status here? (mlavalle)
> https://blueprints.launchpad.net/tempest/+spec/client-lib-stability
> is slow progress appropriate here? (david kranz)
> https://blueprints.launchpad.net/tempest/+spec/quantum-basic-api
> this was approved but it looks to me quite hard to implement tests for
> the different network topologies, is it even possible given our infra?
> (mlavalle)
> https://blueprints.launchpad.net/tempest/+spec/crash-scenario-generator
> needs approval, is there any agreement upon this being implemented or
> shall we drop this? (all core and contributors)

I've yet to see a champion on this or bring this up at weekly meetings,
irc, or on the mailing list (any of which would be valid discussion
areas). So my suggestion is to close it out as invalid at this point.

> https://blueprints.launchpad.net/tempest/+spec/missing-compute-api-extensions
> identifying missing tests isn't a blueprint per se I think so I'd close
> this unless someone volunteer the work to at least identify the wanted
> tests


> * (2) The following are instead blueprints open for discussion which I
> think should either be approved or closed, again input is more  than
> welcomed as well as assignees if you care about it:
> https://blueprints.launchpad.net/tempest/+spec/refactor-rest-client
> https://blueprints.launchpad.net/tempest/+spec/tempest-multiple-images
> https://blueprints.launchpad.net/tempest/+spec/general-swift-client
> https://blueprints.launchpad.net/tempest/+spec/input-scenarios-for-scenario
> https://blueprints.launchpad.net/tempest/+spec/neutron-advanced-scenarios
> https://blueprints.launchpad.net/tempest/+spec/stress-api-tracking
> https://blueprints.launchpad.net/tempest/+spec/test-developer-documentation

This needs more specificity around it, which I don't think we have at
this point.

> * (3) Finally, as a general rule of thumb for the many remaining
> blueprints which only demand for new tests, I think we should keep and
> approve blueprints asking for basic tests around new components but
> *not* (as in close) blueprints demanding for additional tests around
> existing components. Does it look reasonable?

Yes, I think so.

Sean Dague

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 482 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131211/42e1c404/attachment.pgp>

More information about the OpenStack-dev mailing list