On Fri, 2014-02-21 at 22:58 +0400, Eugene Nikanorov wrote: > Hi Jay, > > Just a quick response: > > The 'implementation detail in API' that we all are arguing about is > some hint from the user about how logical configuration is mapped on > the backend(s), not much detail IMO. > > Your proposed model has that, because you create the balancer at once > and the driver can easily map submitted configuration to *some* > backend or even decide how to split it. > Things get more complicated when you need fine-grained control.
Could you provide some examples -- even in the pseudo-CLI commands like I did below. It's really difficult to understand where the limits are without specific examples. > Looking at your proposal it reminds me Heat template for > loadbalancer. > It's fine, but we need to be able to operate on particular objects. I'm not ruling out being able to add or remove nodes from a balancer, if that's what you're getting at? Best, -jay _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
