Hi neutron folks and everyone interested in LBaaS,

Let's meet as usual on #openstack-meeting at 14-00 UTC.

The meeting agenda will be mostly around schema change.
Please look over ML discussion and this link:
https://wiki.openstack.org/wiki/Neutron/LBaaS/LoadbalancerInstance/Discussion

Currently we are evaluating the approach #3.
I'd urge everyone to focus on the discussion of the basic object
relationships
(vips/pools/listeners/healthmons/members).
I think the best outcome of the meeting should be:
1) define attribute sets for pool, vip, listener
2) agree on compatibility mode in which we will introduce the new model
3) discuss and agree on API limitation in favor of code simplicity.
The limitation is that we will require user to manually envelope complex
configurations that involve
multiple vips and pools into a single instance.
That limitation can be omitted later when we figure out how is it better to
deal with multiple backends serving the configuration.

I think (3) is pretty important: there is already a line of patches
depending on the model change.
More complex change will put more pressure on both developers, reviewers
and all those who depend on the change, so more simple approach at the cost
of API "limitation" is something we may consider.

Thanks,
Eugene.
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to