Merge ~verterok/charm-graylog:beats-lb into charm-graylog:master
Status: | Merged |
---|---|
Approved by: | James Troup |
Approved revision: | 651d326ae5496d39d60614d9bf2210d0588ba85a |
Merged at revision: | ab29d166b1eb89596a7c74e4b7499f8f746c3fc6 |
Proposed branch: | ~verterok/charm-graylog:beats-lb |
Merge into: | charm-graylog:master |
Diff against target: |
191 lines (+66/-14) 10 files modified
src/metadata.yaml (+2/-0) src/reactive/graylog.py (+13/-0) src/tests/functional/tests/bundles/bionic-graylog2-ha.yaml (+2/-2) src/tests/functional/tests/bundles/bionic-graylog2.yaml (+2/-2) src/tests/functional/tests/bundles/bionic-graylog3-ha.yaml (+2/-2) src/tests/functional/tests/bundles/bionic-graylog3.yaml (+2/-2) src/tests/functional/tests/bundles/bionic-ha.yaml (+2/-2) src/tests/functional/tests/bundles/focal-graylog2.yaml (+2/-2) src/tests/functional/tests/bundles/focal-graylog3.yaml (+2/-2) src/tests/unit/test_graylog.py (+37/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
🤖 prod-jenkaas-bootstack (community) | continuous-integration | Needs Fixing | |
James Troup (community) | Needs Fixing | ||
BootStack Reviewers | Pending | ||
Review via email: mp+411035@code.launchpad.net |
Commit message
Add support to loadbalance beats protocol using a haproxy in front of a cluster via beats-lb relation
Description of the change
This adds a beats-lb relation, which allows to use haproxy as a reverseproxy for the beats protocol
No tests added, as I was not sure which kind of test a new relation is required for this change: unit or functional? Also, I couldn't find any testing related to haproxy relations, please point me out if I missed something.
e.g:
# deploy a graylog cluster
juju deploy haproxy
juju add-relation haproxy:
juju config haproxy services=$(cat <<-END
- service_name: beats
service_host: "0.0.0.0"
service_port: 5044
service_options:
- mode tcp
- balance leastconn
- timeout server 30000
- timeout client 30000
server_options: check inter 2000 rise 2 fall 5 maxconn 200
END
)
This merge proposal is being monitored by mergebot. Change the status to Approved to merge.