heat/heat_integrationtests/scenario
Rabi Mishra 3db5d3a8b7 Use network 'heat-net' for integration_tests
Neutron support for ipv6 is not complete yet (ex. LBaaS
only supports ipv4). We'had some gate issues after dual
stack was enabled in devstack. We had put some tactical
fixes to resolve those[1][2].

This fix adds usage of heat-net/heat-subnet(only ipv4)
for integration tests. This also rolls back the earlier
tactical changes.

https://review.openstack.org/#/c/178576
https://review.openstack.org/#/c/178933/

Change-Id: Ia863edb8932b8dea5c4fa110c97dcfdadca85bb9
2015-05-27 21:01:30 +05:30
..
templates Use network 'heat-net' for integration_tests 2015-05-27 21:01:30 +05:30
__init__.py Move test_server_cfn_init from tempest to heat 2014-10-07 12:50:32 +13:00
scenario_base.py Use network 'heat-net' for integration_tests 2015-05-27 21:01:30 +05:30
test_ceilometer_alarm.py Add basic Ceilometer alarm test 2015-05-13 14:24:04 +10:00
test_neutron_autoscaling.py Use network 'heat-net' for integration_tests 2015-05-27 21:01:30 +05:30
test_neutron_loadbalancer.py Use network 'heat-net' for integration_tests 2015-05-27 21:01:30 +05:30
test_server_cfn_init.py Use network 'heat-net' for integration_tests 2015-05-27 21:01:30 +05:30
test_server_software_config.py Remove redundant checks of stack status 2015-04-20 10:23:25 -04:00
test_volumes.py Remove redundant checks of stack status 2015-04-20 10:23:25 -04:00