lp:~aglenyoung/charms/precise/haproxy/haproxy-stats-socket

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:charms/haproxy at revision 83

Tim Van Steenburgh (community): Approve on 2014-09-08

Marco Ceppi: Pending requested 2014-01-16

Diff: 60 lines (+12/-0)

3 files modified

config.yaml (+5/-0)
hooks/hooks.py (+3/-0)
hooks/tests/test_helpers.py (+4/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

76. By Andrew Glen-Young on 2014-01-16

Allow haproxy stats socket to be configured.

75. By Andrew Glen-Young on 2014-01-16

Fix test linting errors and update README with additional required packages to run the test suite.

74. By Jorge Castro on 2014-01-07

README updates as part of charm audit.

73. By Jorge Castro on 2014-01-07

Fix typo in config.yaml to pass proof.

72. By Marco Ceppi on 2014-01-03

[jseutter] adds support for the backend service to specify errorfiles in the service configuration. If errorfiles are supplied, the haproxy charm will write them to /var/lib/haproxy/<service_name>/<http status>.html and configure haproxy to use them.

71. By Marco Ceppi on 2013-12-11

[marcoceppi] Don't proceed if there are no services available

70. By Marco Ceppi on 2013-11-04

[sidnei] Fix tests

69. By Marco Ceppi on 2013-11-04

[sidnei] This restores some functionality that got removed by accident during my refactoring and was even documented in README.md, namely, that a service can specify a piece of yaml via relation set services=<> to be used when generating the haproxy stanzas.

68. By Marco Ceppi on 2013-10-17

[sidnei] The 'all_services' config now supports a static list of servers to be used *in addition* to the ones provided via relation.
[sidnei] When more than one haproxy units exist, the configured service is upgraded in-place to a mode where traffic is routed to a single haproxy unit (the first one in unit-name order) and the remaining ones are configured as 'backup'. This is done to allow the enforcement of a 'maxconn' session in the configured services, which would not be possible to enforce otherwise.
[sidnei] Changes to the configured services are properly propagated to the upstream relation.

67. By Mark Mims on 2013-06-03

merging lp:~davidpbritton/charms/precise/haproxy/trunk