On 7/24/2015 6:50 PM, Cathy Zhang wrote:
Hi Everyone, In our last networking-sfc project IRC meeting, an issue was brought up that the API proposed in https://review.openstack.org/#/c/186663/ has a lot of duplication to the SFC API https://review.openstack.org/#/c/192933/ that is being currently implemented. In the IRC meeting, the project team reached consensus that we only need one API and the service chain API can cover the functionality needed by https://review.openstack.org/#/c/186663/. Please refer to the meeting log http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-07-23-17.02.log.html for more discussion info. Please let us know if you have different opinion. Thanks,
I would, however, like input on the idea of CLI and API shortcuts. I don't think the API proposed in 186663 should be a completely separate implementation of creating flow table entries, but I can see the appeal of CLI options and perhaps API operations that allow the end user a quick and easy way of invoking the degenerate case without going through the multi-step, multi-api call execution of the full API.
Is there a precedent for CLI options and/or single API calls that invoke a predefined multi-step path through a more comprehensive API? Perhaps the "Get me a network" work for example?
It isn't very user friendly to force people to learn and navigate a complicated and comprehensive API if all they want to do is one simple and very common use case out of a myriad of possible and possibly esoteric applications of the full API.
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
