Open Stack

A couple quick suggestions (additions):

         Entity: L7Rule

o   Attribute: type

§  Possible values:


   - HTTP_METHOD

o   Attribute: compare_type

§  Possible values:


   - GT (greater than)
   - LT (less than)
   - GE (greater than or equal to)
   - LE (less than or equal to)

Will we be doing syntax checking based on the L7Rule type being presented?
 (eg. if w'ere going to check that HEADER X has a value that is greater
than Y, are we going to make sure that "Y" is an integer? Or if we're going
to check that the PATH STARTS_WITH Z, are we going to make sure that Z is a
non-zero-length string? )

Thanks,
Stephen

On Tue, Feb 18, 2014 at 3:58 AM, Avishay Balderman <AvishayB at radware.com>wrote:

>  Here are the suggested values for the attributes below:
>
> ·         Entity: L7Rule
>
> o   Attribute: type
>
> §  Possible values:
>
> ·         HOST_NAME
>
> ·         PATH
>
> ·         FILE_NAME
>
> ·         FILE_TYPE
>
> ·         HEADER
>
> ·         COOKIE
>
> o   Attribute: compare_type
>
> §  Possible values:
>
> ·         EQUAL
>
> ·         CONTAINS
>
> ·         REGEX
>
> ·         STARTS_WITH
>
> ·         ENDS_WITH
>
> ·         Entity:L7VipPolicyAssociation
>
> o   Attribute:action
>
> §  Possible values:
>
> ·         POOL (must have pool id)
>
> ·         REDIRECT(must have a url to be used as redirect destination)
>
> ·         REJECT
>
>
>
>
>
> *From:* Oleg Bondarev [mailto:obondarev at 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 (use_backend, block, etc.)
>
>
>
> Thanks,
>
> Oleg
>
>
>
> On Sun, Feb 16, 2014 at 3:53 PM, Avishay Balderman <AvishayB at radware.com>
> wrote:
>
> (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 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
>
> 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*: With REG_EXP we can cover the rest of the values.
>
>
>
> In general In the L7rule one can express the following (Example):
>
> “check if in the value of header named ‘Jack’  starts with X” – if this is
> true – this rule “returns” true
>
>
>
>
>
> Thanks
>
>
>
> Avishay
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140218/ac6849e7/attachment.html>