Open Stack

Dear Members of Neutron-TaaS community,

One of the points discussed in the last meeting , was whether we need to
modify the  API endpoints from
/v2_0/taas/ to /v2_0
Most of the Extensions in Neutron are listed under v2_0, and do not need
any separate Parent ID.

I would like to know if there is any specific reason to keep the End Points
under the parenthood of ´taas´?
If not, then like other extensions, we should move the endpoints to v2_0.

Thanks and Regards,
Reedip Banerjee


On Wed, Nov 25, 2015 at 4:45 PM, reedip banerjee <reedip14 at gmail.com> wrote:

> Dear Members of Neutron-TaaS community,
> I have a few queries related to the TaaS API, and would like to know a bit
> more details about them.
>
> a) Currently Tap Service and Tap flow Endpoints are listed under
> /v2_0/taas/
>
> For example:
> http://111.000.222.115:9696/v2.0/taas/tap-services.json
> http://111.000.222.115:9696/v2.0/taas/tap-flows.json
>
> Is it necessary to list the endpoints under /taas/?
> Can we keep them under v2_0 like most of the other Neutron Extensions?
> i.e.
>
> http://111.000.222.115:9696/v2.0/taas/tap-services.json  -->
> http://111.000.222.115:9696/v2.0/tap-services.json
>
> b) Currently TaaS has 2 different ports:
> - Tap Service uses port_id to specify ports
> - Tap Flow uses source_port to specify ports.
> As both of these attributes are under different end points, can we use
> ´port´ instead of port_id and source_port?
> From my understanding, port makes bit of a sense, and it is also an known
> attribute in Neutron.
>
>
>
> --
> Thanks and Regards,
> Reedip Banerjee
> irc:reedip
>
>


-- 
Thanks and Regards,
Reedip Banerjee


The Only One Thing Constant In Life Is CHANGE
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151208/a2f5fa7a/attachment.html>