Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HAProxy Stats Page as easy to configure option #7

Closed
fititnt opened this issue Nov 4, 2019 · 1 comment
Closed

HAProxy Stats Page as easy to configure option #7

fititnt opened this issue Nov 4, 2019 · 1 comment
Labels
network-load-balancer user-interface User interface (Super admins are also users in this case!)

Comments

@fititnt
Copy link
Owner

fititnt commented Nov 4, 2019

Allow (as option, not by default) HAProxy Stats Page https://www.haproxy.com/blog/exploring-the-haproxy-stats-page/.

This maybe also will be the start of have some types of apps that are mean to be for internal use, and not the alb_apps array

@fititnt
Copy link
Owner Author

fititnt commented Nov 9, 2019

ALB v0.5.0-alpha already have a MVP for implement HAProxy Status page.

Here some example of configuration

- name: "ap-application-load-balancer playbook example (complex)"
  hosts: my_complex_hosts
  remote_user: root
  vars:
    alb_name: "MyALBName/2.0"
    alb_forcedebug: yes

    alb_haproxy_stats_enabled: yes

    alb_superuser_auth:
     - username: Admin1
       password: "plain-password"
     - username: Admin2
       password: "plain-password2"
    alb_superuser_ip: 123.123.123.123
    # alb_superuser_autodiscoveripnull: yes Not implemented yet

The passwords can be saved encrypted on yaml playbooks using Ansible Vault (see https://docs.ansible.com/ansible/latest/user_guide/playbooks_vault.html) but the underline application still need plain passwords to work with less configurations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
network-load-balancer user-interface User interface (Super admins are also users in this case!)
Projects
None yet
Development

No branches or pull requests

1 participant