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.
Reviewed: https:/ /review. openstack. org/285160 /git.openstack. org/cgit/ openstack/ octavia/ commit/ ?id=ad3423afca8 caf9334dfd35542 752ca4ac25056e
Committed: https:/
Submitter: Jenkins
Branch: master
commit ad3423afca8caf9 334dfd35542752c a4ac25056e
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: I28b8161e85b9e8 6d4c44be3d48cbf 94a3ce631f3
Closes-Bug: 1549100