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: > (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@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
