zhiyuan_cai 9897c65a26 Local FIP not created after central FIP creation ... 1. What is the problem After booting a VM, we associate a FIP to it via central Neutron. However, local FIP is not created as expected. Also, there is no related asynchronous job registered. The reason may be that we don't trigger asynchronous job in "create_floatingip" method, and since VM is already there, there's no chance to trigger the job. 2. What is the solution for the problem If "port_id" is specified in the body, trigger asynchronous job. 3. What features need to be implemented to the Tricircle to realize the solution Support creating FIP with "port_id" specified. Change-Id: Iceb15f68acc23f8dcb8767ac0371947334a1e9db Closes-Bug: #1691918		2017-06-12 09:54:28 +08:00
..
gate_hook.sh	Basic smoke test script	2017-04-27 19:11:07 +08:00
post_test_hook.sh	Basic smoke test script	2017-04-27 19:11:07 +08:00
pre_test_hook.sh	Remove API-GW related code from the Tricricle	2016-10-10 23:12:09 -04:00
smoke_test.sh	Local FIP not created after central FIP creation	2017-06-12 09:54:28 +08:00
smoke_test_validation.py	Local FIP not created after central FIP creation	2017-06-12 09:54:28 +08:00
tempest_network.sh	Add tempest test cases which are needed for integration test in Tricircle	2016-06-28 13:17:42 +08:00
tempest_scenario.sh	Add tempest test cases which are needed for integration test in Tricircle	2016-06-28 13:17:42 +08:00