lp:~ce-hyperscale/charms/precise/haproxy/arm64-trusty

Created by dann frazier and last modified
Get this branch:
bzr branch lp:~ce-hyperscale/charms/precise/haproxy/arm64-trusty
Members of CE Hyperscale can upload to this branch. Log in for directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
CE Hyperscale
Status:
Development

Recent revisions

77. By Marco Ceppi

"Add revision file"

76. By Matt Bruzek

Added amulet tests for haproxy charm.

R=
CC=
https://codereview.appspot.com/56140043

75. By Marco Ceppi

[davidpbritton] Add test case and fix for backend "server" entries not getting unioned, when multiple units join the relation

74. By Jorge Castro

README updates as part of charm audit.

73. By Jorge Castro

Fix typo in config.yaml to pass proof.

72. By Marco Ceppi

[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

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

70. By Marco Ceppi

[sidnei] Fix tests

69. By Marco Ceppi

[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

[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:
lp:charms/haproxy
This branch contains Public information 
Everyone can see this information.

Subscribers