No check that healthmonitor delay should >= timeout

[dongjuan]

issue is in kilo branch

healthmonitor delay is 10, timeout is 12

it does not make sense

[root@opencos2 ~(keystone_admin)]# neutron lbaas-healthmonitor-show 6d29f448-1965-40b9-86e2-cf18d86ae6f8
+----------------+------------------------------------------------+
| Field | Value |
+----------------+------------------------------------------------+
| admin_state_up | True |
| delay | 10 |
| expected_codes | 305,205 |
| http_method | GET |
| id | 6d29f448-1965-40b9-86e2-cf18d86ae6f8 |
| max_retries | 10 |
| pools | {"id": "591be59b-eb81-4f1d-8ab7-b023df6cccfa"} |
| tenant_id | be58eaec789d44f296a65f96b944a9f5 |
| timeout | 12 |
| type | PING |
| url_path | /api/ |
+----------------+------------------------------------------------+

[Dustin Lundquist (dlundquist)]

A health check sent every 10 seconds with a 12 second delay is possible, although not all drivers may support overlapping health checks like this. I do agree there should be an administratively configureable lower bound on health check intervals (delay) to prevent user using the LBaaS to preform a DoS. This becomes more important with https://bugs.launchpad.net/neutron/+bug/1600326, since delay values are interpreted in milliseconds.

[Gregory Thiemonge (gthiemonge)]

Abandoned after re-enabling the Octavia launchpad.