David Ames e1ac46f342 Update HAProxy default timeout values ... The default HAProxy timeout values are fairly strict. On a busy cloud it is common to exceed one or more of these timeouts. The only indication that HAProxy has exceeded a timeout and dropped the connection is errors such as "BadStatusLine" or "EOF." These can be very difficult to diagnose when intermittent. This charm-helpers sync pulls in the change to update the default timeout values to more real world settings. These values have been extensively tested in ServerStack. Configured values will not be overridden. Partial Bug: #1736171 Change-Id: I973962a5c1538b0d9afbebea8cebf50d938ecfb5		2017-12-11 11:37:02 -08:00
..
cli	Resync charmhelpers for licensing change	2016-07-06 16:35:04 +01:00
contrib	Update HAProxy default timeout values	2017-12-11 11:37:02 -08:00
core	Update HAProxy default timeout values	2017-12-11 11:37:02 -08:00
fetch	Enable xenial-pike amulet test	2017-11-15 16:19:26 -08:00
payload	Pre-release charm-helpers sync 16.10	2016-09-30 09:04:39 -07:00
__init__.py	Dual Stack VIPs	2017-08-10 18:41:53 -07:00
osplatform.py	Do not run client relation until clustered if HA	2017-02-16 10:47:38 +00:00