:58 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] Continuing on Calling driver
interface on every API request
Hi,
Validations such as timeout delay should be performed on the API level
before it reaches the driver
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] Continuing on Calling driver
interface on every API request
Well, that exactly what we've tried to solve with tags in the flavor.
Considering your example with whole configuration being
Hi:
Continuing from last week's LBaaS meeting...
Currently an entity cannot be sent to driver unless it is linked to
loadbalancer because loadbalancer is the root object and driver information is
only available with loadbalancer.
The request to the driver is delayed because of which error
[mailto:vijay.venkatacha...@citrix.com]
Sent: Monday, August 11, 2014 2:43 PM
To: OpenStack Development Mailing List (openstack-dev@lists.openstack.org)
Subject: [openstack-dev] [Neutron][LBaaS] Continuing on Calling driver
interface on every API request
Hi:
Continuing from last week's LBaaS meeting
not make sense.
-San.
From: Vijay Venkatachalam [mailto:vijay.venkatacha...@citrix.com]
Sent: Monday, August 11, 2014 2:43 PM
To: OpenStack Development Mailing List
(openstack-dev@lists.openstack.org)
Subject: [openstack-dev] [Neutron][LBaaS] Continuing on Calling
driver
not make sense.
-San.
From: Vijay Venkatachalam [mailto:vijay.venkatacha...@citrix.com]
Sent: Monday, August 11, 2014 2:43 PM
To: OpenStack Development Mailing List (openstack-dev@lists.openstack.org)
Subject: [openstack-dev] [Neutron][LBaaS] Continuing on Calling driver
interface on every API
(not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] Continuing on Calling driver
interface on every API request
Hi all,
Validations such as ³timeout delay² should be performed on the API
level before it reaches the driver.
For a configuration tree (lb, listeners, pools, etc
-
From: Doug Wiegley [mailto:do...@a10networks.com]
Sent: Monday, August 11, 2014 6:55 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] Continuing on Calling
driver interface on every API request
Hi all,
Validations such as ³timeout
: [openstack-dev] [Neutron][LBaaS] Continuing on Calling driver
interface on every API request
Hi Sam,
Very true. I think that Vijay’s objection is that we are currently imposing a
logical structure on the driver, when it should be a driver decision.
Certainly, it goes both ways.
And I also
Wiegley [mailto:do...@a10networks.com]
Sent: 11 August 2014 22:02
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] Continuing on Calling
driver interface on every API request
Hi Sam,
Very true. I think that Vijay’s objection
: Re: [openstack-dev] [Neutron][LBaaS] Continuing on
Calling
driver interface on every API request
Hi all,
Validations such as ³timeout delay² should be performed
on the API
level before it reaches the driver
Mailing List (not for usage
questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] Continuing on
Calling driver interface on every API request
Hi Sam,
Very true. I think that Vijay’s objection is that we are
currently imposing a logical
12 matches
Mail list logo
