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
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
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
With the introduction of NeutronExtension for TaaS, the previous
TaaS CLI repository is not required anymore.
Therefore this patch removes the old TaaS CLI repo.
Also, with the introduction of the Neutron base TaaS CLI, the API
reference document is updated.
Change-Id: Iade483ab93583c5699ceee2259e3c309c3c5bb10