Ibm Demo Haproxy

Learn about configurations >

• default_log | string

  Default: global

  Default log

• default_mode | string

  Default: http

  Default mode

• default_options | string

  Default: httplog, dontlognull

  Default options

• default_retries | int

  Default: 3

  Set the number of retries to perform on a server after a connection failure. It is important to understand that this value applies to the number of connection attempts, not full requests. When a connection has effectively been established to a server, there will be no more retry. In order to avoid immediate reconnections to a server which is restarting, a turn-around timer of 1 second is applied before a retry occurs.

• default_timeouts | string

  Default: queue 20000, client 50000, connect 5000, server 50000

  Default timeouts

• enable_monitoring | boolean

  Enable monitoring

• global_debug | boolean

  Debug or not

• global_group | string

  Default: haproxy

  Group

• global_log | string

  Default: 127.0.0.1 local0, 127.0.0.1 local1 notice

  Global log line ( multiples ... comma separated list )

• global_maxconn | int

  Default: 4096

  Sets the maximum per-process number of concurrent connections to <number>.

• global_quiet | boolean

  Quiet

• global_spread_checks | int

  Sometimes it is desirable to avoid sending health checks to servers at exact intervals, for instance when many logical servers are located on the same physical server. With the help of this parameter, it becomes possible to add some randomness in the check interval between 0 and +/- 50%. A value between 2 and 5 seems to show good results.

• global_stats_socket | boolean

  Whether to enable the stats UNIX socket.

• global_user | string

  Default: haproxy

  User

• metrics_prefix | string

  Default: dev.$UNIT.haproxy

  Prefix for metrics. Special value $UNIT can be used to include the name of the unit in the prefix.

• metrics_sample_interval | int

  Default: 5

  Period for metrics cron job to run in minutes

• metrics_target | string

  Destination for statsd-format metrics, format "host:port". If not present and valid, metrics disabled. Requires "enable_monitoring" to be set to true to work.

• monitoring_allowed_cidr | string

  Default: 127.0.0.1/32

  CIDR allowed ( multiple CIDRs separated by space ) access to the monitoring interface.

• monitoring_password | string

  Default: changeme

  Password to the monitoring interface ( if "changeme", a new password will be generated and displayed in juju-log )

• monitoring_port | int

  Default: 10000

  Default monitoring port

• monitoring_stats_refresh | int

  Default: 3

  Monitoring interface refresh interval (in seconds)

• monitoring_username | string

  Default: haproxy

  Monitoring username

• nagios_context | string

  Default: juju

  Used by the nrpe-external-master subordinate charm. A string that will be prepended to instance name to set the host name in nagios. So for instance the hostname would be something like: juju-postgresql-0 If you're running multiple environments with the same services in them this allows you to differentiate between them.

• package_status | string

  Default: install

  The status of service-affecting packages will be set to this value in the dpkg database. Useful valid values are "install" and "hold".

• services | string

  Default: - service_name: haproxy_service service_host: "0.0.0.0" service_port: 80 service_options: [balance leastconn, cookie SRVNAME insert] server_options: maxconn 100 cookie S{i} check

  Services definition(s). Although the variable type is a string, this is interpreted in the charm as yaml. To use multiple services within the same haproxy instance, specify all of the variables (service_name, service_host, service_port, service_options, server_options) with a "-" before the first variable, service_name, as above. Service options is a comma separated list, server options will be appended as a string to the individual server lines for a given listen stanza. If your web application serves dynamic content based on users' login sessions, a visitor will experience unexpected behaviour if each request is proxied to a different backend web server. Session stickiness ensures that a visitor 'sticks' to the backend web server which served their first request. This is made possible by tagging each backend server with a cookie. Session are sticky by default. To turn off sticky sessions, remove the 'cookie SRVNAME insert' and 'cookie S{i}' stanzas from `service_options` and `server_options`.

• sysctl | string

  YAML-formatted list of sysctl values, e.g.: '{ net.ipv4.tcp_max_syn_backlog : 65536 }'