: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,
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.), there should be one
provider.
Having provider defined in multiple places does not make sense.
-San.
From: Vijay Venkatachalam
Yeah what I meant was the only solution I could come up with so that the
driver gets passed every call is to have the every entity have a
provider. I do believe this is a bit cumbersome for a user, and extra
validation would be needed to verify that two entities linked together
cannot have
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.), there should be one
provider.
You¹re right, but I think the point of Vijay¹s example was to highlight
the combo error problem
(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
11 matches
Mail list logo
