Support seamless reloading with HAProxy
Bug #1892676 reported by
Haw Loeung
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Content Cache Charm |
Fix Released
|
Critical
|
Haw Loeung | ||
Bug Description
Hi,
Please add support for seamless reloading with HAProxy. That's using load-server-
http://
Related branches
~hloeung/content-cache-charm:cleanup
- Benjamin Allot: Approve
- Canonical IS Reviewers: Pending requested
-
Diff: 39 lines (+8/-4)3 files modifiedlib/haproxy.py (+5/-1)
tests/unit/files/content_cache_rendered_haproxy_test_output_srv_template.txt (+2/-2)
tests/unit/files/haproxy_config_rendered_backends_stanzas_test_output2.txt (+1/-1)
~hloeung/content-cache-charm:haproxy-config
- Benjamin Allot: Approve
- Barry Price: Approve
-
Diff: 375 lines (+89/-7)14 files modifiedlib/haproxy.py (+26/-0)
reactive/content_cache.py (+1/-0)
templates/haproxy_cfg.tmpl (+3/-1)
tests/unit/files/content_cache_rendered_haproxy_test_output.txt (+2/-0)
tests/unit/files/content_cache_rendered_haproxy_test_output2.txt (+2/-0)
tests/unit/files/content_cache_rendered_haproxy_test_output3.txt (+2/-0)
tests/unit/files/content_cache_rendered_haproxy_test_output_auto_maxconns.txt (+2/-0)
tests/unit/files/content_cache_rendered_haproxy_test_output_load_balancing_algorithm.txt (+2/-0)
tests/unit/files/content_cache_rendered_haproxy_test_output_processes_and_threads.txt (+2/-0)
tests/unit/files/haproxy_config_rendered_test_output.txt (+2/-0)
tests/unit/files/haproxy_config_rendered_test_output2.txt (+2/-0)
tests/unit/files/haproxy_show_servers_state.txt (+8/-0)
tests/unit/test_content_cache.py (+14/-6)
tests/unit/test_haproxy.py (+21/-0)
| Changed in content-cache-charm: | |
| assignee: | nobody → Haw Loeung (hloeung) |
| importance: | Undecided → Critical |
| status: | New → In Progress |
| Changed in content-cache-charm: | |
| status: | In Progress → Fix Committed |
| Changed in content-cache-charm: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
