I'm testing against a bare metal installation of Openstack and since a few days ago, an instance of Devstack as well. My team and I are mostly running Tempest from OSX or Ubuntu. Some of the clutter in the Tempest project is due to a merge of many projects to one. There are still some legacy portions of code remaining which will be phased out in the next few months so that the final project is much cleaner and easier to understand.
I have some revised documentation that I'm preparing to push, but in the interim I'll explain a bit more about how the project should be configured. The tempest.conf.sample file is a template to be used for your actual configuration. Your actual config file should be named tempest.conf. The host, port, apiVer, and path variables should build the path to your Keystone deployment, and the user, api_key, and tenant_name fields should match some existing user in your deployment. The environment section is mostly for reference data. image_ref and image_ref_alt should be id or ref for two distinct images in your deployment. Flavor_ref and flavor_ref_alt should be set based on valid flavors in your deployment as well. Create_image_enabled and resize_available are feature flags to toggle tests for that functionality. Once you have a valid config file, the tests are runnable like any other test via nose. That one file is all that needs to be changed. I'm glad to see the surge of interest in Tempest, and every bit of feedback is helpful. I'll be pushing code (some of which is already merged) and documentation changes this week to address issues and concerns. I'm also lurking in openstack-dev as dwalleck, and I'd be more than glad to discuss Tempest and help work through any issues anyone is having. Daryl On Feb 27, 2012, at 11:03 AM, Ionuț Arțăriși wrote: > On 02/27/2012 05:13 PM, Daryl Walleck wrote: >> I'm actively looking into any issues. I have all these tests passing locally >> in my environment, so the issues seem to be focused around people using >> devstack. I've made some merge prop's that will take care of a few of the >> issues. One issue that will certainly come up is that if you have rate >> limiting enabled, most of the tests will certainly fail. I've also included >> the link to the Tempest documentation, which also should help make using a >> bit more clear. I'm working on updating this document as I'm using Devstack >> so that I can either smooth over or enumerate issues that may come up when >> running the tests. If you run into anything though, please make a report to >> the Tempest project and I'll have a look. >> >> http://qa.openstack.org/integration.html >> >> https://launchpad.net/tempest >> >> Daryl >> > > Can you give more details about your environment? What operating system are > you running the tests on? Are all the tested openstack components the latest > versions from master? What specific configurations have you done? > > The documentation that you linked to does not explain how to actually set up > the tests. > > There are currently three README files in the repository which say to rename > the tempest.conf.sample and config.ini.sample files and then "edit the > variables to fit your test environment", but none of them explain what that > actually means. Which values should be reset? Where would I get the > information to be able to set them? > > I'm trying hard to understand how all of this works, but without a canonical > working configuration I don't know which errors are mine and which are > tempest bugs. > > -Ionuț _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
