← Back to team overview

openstack team mailing list archive

Re: Steps that can help stabilize Nova's trunk


Andy has listed a few things on the wiki. I'll summarize the known efforts here:

* Anso has created some Vagrant scripts that test multi-node
functionality of the EC2 API, libvirt + KVM, and nova-objectstore
* Vishy/Devin  have been refactored Nova's existing smoketests/ and
updated to include netadmin tests. Still only testing EC2 API
* Trey has been "volunteered" to write an OpenStack API smoketest for
XenServer functionality (https://bugs.launchpad.net/nova/+bug/720941)
* Jordan Rinke has been working on a 10-machine test cluster for
testing deployments and running smoketests on
* Other rackers (Pvo, Ant?) have been working on getting a much larger
production-level test cluster for running longer, more complex tests

Stuff we need to do:

* Create a staging/testing branch, have Openstack Hudson LP user own it
* Get the test cluster machines entered into Hudson
* On each merge proposal into trunk, have Tarmac pull the branch, run
unit tests automatically, fire off smoketests/ against the test
machines automatically, and notify the merge proposal that tests pass
or don't pass.
* For merge proposals that pass the merge into staging and all tests
that also have 2 Approves from core devs, have Tarmac merge into trunk
* Create long-running functional tests that are essentially re-playing
large Apache/nginx log files of existing Nebula and Cloud Servers API
nodes against Nova staging branch with various configurations


On Thu, Feb 24, 2011 at 3:49 PM, Sandy Walsh <sandy.walsh@xxxxxxxxxxxxx> wrote:
> Jay,
> Nice to see this issue being addressed ... it's a big deal.
> From reading this (long) thread, my biggest source of confusion was so
> many "we're doing something on this front too ..." messages.
> Would it be possible to get a summary of the various integration testing
> efforts underway so we can find out where the
> commonality/biggest-bang-for-the-buck/overlap is? Perhaps a wiki page
> already exists for this?
> Thx,
> -S
> ________________________________
> From: << a cast of thousands ... delete >>
> Confidentiality Notice: This e-mail message (including any attached or
> embedded documents) is intended for the exclusive and confidential use of
> the
> individual or entity to which this message is addressed, and unless
> otherwise
> expressly indicated, is confidential and privileged information of
> Rackspace.
> Any dissemination, distribution or copying of the enclosed material is
> prohibited.
> If you receive this transmission in error, please notify us immediately by
> e-mail
> at abuse@xxxxxxxxxxxxx, and delete the original message.
> Your cooperation is appreciated.
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

Follow ups