...@mirantis.commailto:obonda...@mirantis.com]
Sent: Monday, February 17, 2014 9:17 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] L7 data types
Hi,
I would add another candidate for being a closed set:
L7VipPolicyAssociation.action
questions)
*Subject:* Re: [openstack-dev] [Neutron][LBaaS] L7 data types
Hi,
I would add another candidate for being a closed set:
L7VipPolicyAssociation.action (use_backend, block, etc.)
Thanks,
Oleg
On Sun, Feb 16, 2014 at 3:53 PM, Avishay Balderman avish...@radware.com
wrote
Oh! One thing I forgot to mention below:
On Sat, Feb 15, 2014 at 11:55 PM, Avishay Balderman avish...@radware.comwrote:
Entity: L7Rule
Field : compare_type
Description: The way we compare the value against a given value
Possible values: REG_EXP, EQ, GT, LT,EQ_IGNORE_CASE,(?)
*Note*:
, February 17, 2014 9:17 AM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [Neutron][LBaaS] L7 data types
Hi,
I would add another candidate for being a closed set:
L7VipPolicyAssociation.action (use_backend, block, etc.)
Thanks,
Oleg
Hi
There are 2 fields in the L7 model that are candidates for being a closed set
(Enum).
I would like to hear your opinion.
Entity: L7Rule
Field : type
Description: this field holds the part of the request where we should look for
a value
Possible values: URL,HEADER,BODY,(?)
Entity: L7Rule
(removing extra space from the subject - let email clients apply their filters)
From: Avishay Balderman
Sent: Sunday, February 16, 2014 9:56 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Neutron][LBaaS] L7 data types
Hi
There are 2 fields in the L7
)
*From:* Avishay Balderman
*Sent:* Sunday, February 16, 2014 9:56 AM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* [openstack-dev] [Neutron][LBaaS] L7 data types
Hi
There are 2 fields in the L7 model that are candidates for being a closed
set (Enum).
I
