I think the API should provide an richly featured interface, and individual drivers should indicate if they support the provided configuration. For example there is a spec for a Linux LVS LBaaS driver, this driver would not support TLS termination or any layer 7 features, but would still be valuable for some deployments. The user experience of such a solution could be improved if the driver to propagate up a message specifically identifying the unsupported feature.
-Dustin On Tue, Jun 24, 2014 at 4:28 AM, Avishay Balderman <avish...@radware.com> wrote: > Hi > > One of L7 Rule attributes is ‘compare_type’. > > This field is the match operator that the rule should activate against the > value found in the request. > > Below is list of the possible values: > > - Regexp > > - StartsWith > > - EndsWith > > - Contains > > - EqualTo (*) > > - GreaterThan (*) > > - LessThan (*) > > > > The last 3 operators (*) in the list are used in numerical matches. > > Radware load balancing backend does not support those operators “out of > the box” and a significant development effort should be done in order to > support it. > > We are afraid to miss the Junu timeframe if we will have to focus in > supporting the numerical operators. > > Therefore we ask to support the non-numerical operators for Junu and add > the numerical operators support post Junu. > > > > See https://review.openstack.org/#/c/99709/4/specs/juno/lbaas-l7-rules.rst > > > > 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
