tap-as-a-service-tempest-pl.../neutron_taas/tests/unit
Kazuhiro Suzuki 752fb029fa Add status field in the TaaS API
In the current implementation, when the TaaS API (tap-service,
tap-flow) call completes, the status of result is returned. [1]
In order to adopt an asynchronous model, the 'status' field is
needed in the API.
The following code adds the status field in the API.
In the first step, the status is set to 'ACTIVE' by default.

[1]: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html

Depends-On: Ie6b3811e41a94721679c9178cdd5119bdad8208d
Change-Id: Ib8e4ad15e5b4272ac7f8800f72d7f2c003db798e
2016-09-23 19:03:31 +09:00
..
db Bring models in sync with migrations, add test 2016-08-17 13:31:29 -07:00
services Add status field in the TaaS API 2016-09-23 19:03:31 +09:00
taas_client UT: Fix "RuntimeError: stop called on unstarted patcher" 2016-08-01 08:07:33 +09:00
__init__.py Start writing tests 2015-10-02 02:57:37 +09:00