Created by Andrew Glen-Young on 2014-01-15 and last modified on 2014-01-16
Get this branch:
bzr branch lp:~aglenyoung/charms/precise/haproxy/haproxy-stats-socket
Only Andrew Glen-Young can upload to this branch. If you are Andrew Glen-Young please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Andrew Glen-Young

Recent revisions

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.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
This branch contains Public information 
Everyone can see this information.