heat/heat_integrationtests
Sergey Kraynev bf20657824 Unify workers options for API services
This patch change behaviour of launching API services for different
numbers of workers:
- workers < 0 -> is not allowed
- workers == 0 -> as much worker *processes* as CPU cores
- workers == 1 -> no child *processes*, single *green thread*
- workers > 1 -> specified number of worker *processes*

Note: According with old behaviour following services have corresponding
defaul values:
 - heat-api  -> '0', instead of function for calculation number of cores.
 - heat-api-cfn -> '1', instead of '0' (i.e. one *green thread*)
 - heat-api-cw -> '1', instead of '0' (i.e. one *green thread*)

Also updated number of workers for functional tests.
It's necessary, because priveous value was '1', which now mean one
single thread. (Previously it was one worker).

Change-Id: Idebd19c62adea02d9181236f6cbfed090acb32b9
Closes-Bug: #1523390
2016-01-18 13:16:48 +00:00
..
2015-07-17 11:01:31 +00:00

Heat integration tests

These tests can be run against any heat-enabled OpenStack cloud, however defaults match running against a recent DevStack.

To run the tests against DevStack, do the following:

# source DevStack credentials

source /opt/stack/devstack/openrc

# run the heat integration tests with those credentials

cd /opt/stack/heat

tox -eintegration

If custom configuration is required, copy the following file:

heat_integrationtests/heat_integrationtests.conf.sample

to:

heat_integrationtests/heat_integrationtests.conf

and make any required configuration changes before running:

tox -eintegration