Now that ExtensionDescriptor is in neutron-lib[0], use it
to for neutron_lib migration in TaaS.
[0] https://review.openstack.org/389825
Partially-implements: blueprint neutron-lib
Change-Id: I8db2bdc72e43eeb4befd48d9d3b1895bc7d899bc
Depends-On: I5a111e0033e518e39b3042f047ee9eebba77a0d5
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
Currently tap-*-update is not possible, though the
API documentation states that Update of Name/Description
is possible. This patch adds the functionality.
Change-Id: Ia32136ce80a4e8f4234d00491730dc725d7c7b7b
Closes-Bug: #1540754
This patch fixes the validation of direction.
* change API validator from type:string to type:values
* remove None from direction_enum because of NOT NULL constraint
Change-Id: Iae4f13451002db7567425ae33d1c36bd2013ae75
Closes-Bug: #1585445
Currently it's unused. Thus no good reason to force users to
specify it.
It can be re-introduced when/if we decide automatic port creation
is desirable. For db models, a boolean to say if the port has been
automatically created might be more appropriate, though.
Change-Id: Ia183635c183fd4ad731fd1ee48c58f6b10f06c5b
Due to the difference of API Endpoint and Resource Body,
NeutronClient could not succesfully create the tap-services
( and consecutively, tapflow).
The following code change modifies the API end point, and fixes
the problem with NeutronClient.
Change-Id: I9fa21bb273ef8a5c6fabece0a29673839cf8e945
Closes-Bug: #1539130