Hi Reedip, I believe TaaS API will go through a round of reviews when the spec is introduced. It will be good to discuss these points there.
Fawad Khaliq On Wed, Nov 25, 2015 at 12:45 PM, reedip banerjee <[email protected]> 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 > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
