L7 - HAproxy fails with more than 53 L7 rules

[Michael Johnson]

HAProxy will fail with more than 53 L7 rules in a policy. We should limit the user to 50 L7 rules per policy.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/285160

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/285160
Committed: https://git.openstack.org/cgit/openstack/octavia/commit/?id=ad3423afca8caf9334dfd35542752ca4ac25056e
Submitter: Jenkins
Branch: master

commit ad3423afca8caf9334dfd35542752ca4ac25056e
Author: Stephen Balukoff <email address hidden>
Date: Fri Feb 26 00:37:25 2016 -0800

    Add maximum number of l7rules per l7policy

    For reasons of pure practicality, it is not a good idea to allow tenants
    to create arbitrarily long lists of l7rules on their l7policies. After a
    brief discussion we decided that 50 rules is good limit, especially
    given that we expect most practical uses of L7 functionality to entail 1
    to 4 rules per policy at most.

    This commit also fixes a minor bug I noticed in the L7 rule API tests,
    and cleans up the L7Rule API rule response specification.

    Change-Id: I28b8161e85b9e86d4c44be3d48cbf94a3ce631f3
    Closes-Bug: 1549100