Re: [openstack-dev] [Octavia] Responsibilities for controller drivers

2014-09-15 Thread Stephen Balukoff
Hi Brandon! My responses in-line: On Fri, Sep 12, 2014 at 11:27 AM, Brandon Logan brandon.lo...@rackspace.com wrote: IN IRC the topic came up about supporting many-to-many load balancers to amphorae. I believe a consensus was made that allowing only one-to-many load balancers to amphorae

Re: [openstack-dev] [Octavia] Responsibilities for controller drivers

2014-09-15 Thread Adam Harwell
) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Date: Monday, September 15, 2014 1:33 PM To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Octavia

Re: [openstack-dev] [Octavia] Responsibilities for controller drivers

2014-09-15 Thread Brandon Logan
Hi Stephen, Same drill On Mon, 2014-09-15 at 13:33 -0700, Stephen Balukoff wrote: Hi Brandon! My responses in-line: On Fri, Sep 12, 2014 at 11:27 AM, Brandon Logan brandon.lo...@rackspace.com wrote: IN IRC the topic came up about supporting many-to-many load balancers

[openstack-dev] [Octavia] Responsibilities for controller drivers

2014-09-12 Thread Brandon Logan
IN IRC the topic came up about supporting many-to-many load balancers to amphorae. I believe a consensus was made that allowing only one-to-many load balancers to amphorae would be the first step forward, and re-evaluate later, since colocation and apolocation will need to work (which brings up