Open Stack

Hi,

To run a multi-region scenario you need to have both regions deployed
before a tempest run is started, so you would need a extra configuration
items.  But I'm not convinced that would be in scope for tempest - there's
no single way to deploy multiple regions.

To run the same scenario tests against multiple regions (or clouds) you
could have multiple tempest folders (use "tempest init" to create them) or
you could have a single folder and point tempest to a different
configuration file, depending on whether you wish to keep your testr db
separated per region or not. In any case you'll need multiple config files.

You can use a template config and change only the bits that you need using
tools like crudini or jinja2 templates (if you use ansible).

Andrea

On Fri, 25 Mar 2016 5:18 pm Danny Choi (dannchoi), <dannchoi at cisco.com>
wrote:

> Hi,
>
> There are variables defined in the tempest.conf.  How does tempest read
> them and use them in the tests?
>
> I’m trying to write scenario tests in multiple regions.
>
> Under tempest.conf:
>
> [identity]
>
> Region = RegionOne
>
>
> [compute]
>
> image_ref = b6f85abb-c582-40e4-ad18-5a01431a6bfd
>
> image_ref_alt = b6f85abb-c582-40e4-ad18-5a01431a6bfd
>
> [network]
>
> public_network_id = 51efe3a5-390f-4a40-a480-8aa41d704c69
>
>
> I’m thinking to change these variables within the test on the fly to run
> test within that particular region
>
> (region name, image id, public network id).
>
>
> My question is what tempest variables uses these conf variables?
>
>
> Is this the right approach or there is a better way to do it?
>
>
> Thanks,
>
> Danny
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160326/5f795399/attachment.html>