Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 851047 Details for
Bug 1036518
[Docs] [HA] OpenStack mysql/qpid driver and haproxy timers need to be carefully documented
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
haproxy configuration which works ok for my testing
haproxy.cfg (text/plain), 3.29 KB, created by
Ihar Hrachyshka
on 2014-01-16 13:09:50 UTC
(
hide
)
Description:
haproxy configuration which works ok for my testing
Filename:
MIME Type:
Creator:
Ihar Hrachyshka
Created:
2014-01-16 13:09:50 UTC
Size:
3.29 KB
patch
obsolete
>#--------------------------------------------------------------------- ># Example configuration for a possible web application. See the ># full configuration options online. ># ># http://haproxy.1wt.eu/download/1.4/doc/configuration.txt ># >#--------------------------------------------------------------------- > >#--------------------------------------------------------------------- ># Global settings >#--------------------------------------------------------------------- >global > # to have these messages end up in /var/log/haproxy.log you will > # need to: > # > # 1) configure syslog to accept network log events. This is done > # by adding the '-r' option to the SYSLOGD_OPTIONS in > # /etc/sysconfig/syslog > # > # 2) configure local2 events to go to the /var/log/haproxy.log > # file. A line like the following can be added to > # /etc/sysconfig/syslog > # > # local2.* /var/log/haproxy.log > # > log 127.0.0.1 local2 > > chroot /var/lib/haproxy > pidfile /var/run/haproxy.pid > maxconn 4000 > user haproxy > group haproxy > daemon > > # turn on stats unix socket > stats socket /var/lib/haproxy/stats > >#--------------------------------------------------------------------- ># common defaults that all the 'listen' and 'backend' sections will ># use if not designated in their block >#--------------------------------------------------------------------- >defaults > mode tcp > log global > option httplog > option dontlognull > option http-server-close > option forwardfor except 127.0.0.0/8 > option redispatch > retries 3 > timeout http-request 30s > timeout queue 1m > timeout connect 30s > timeout client 30s > timeout server 30s > timeout http-keep-alive 30s > timeout check 1s > maxconn 3000 > >#--------------------------------------------------------------------- ># main frontend which proxys to the backends >#--------------------------------------------------------------------- >#frontend main *:5000 ># acl url_static path_beg -i /static /images /javascript /stylesheets ># acl url_static path_end -i .jpg .gif .png .css .js > ># use_backend static if url_static ># default_backend app > >#--------------------------------------------------------------------- ># static backend for serving up images, stylesheets and such >#--------------------------------------------------------------------- >#backend static ># balance roundrobin ># server static 127.0.0.1:4331 check > >#--------------------------------------------------------------------- ># round robin balancing between the various backends >#--------------------------------------------------------------------- >#backend app ># balance roundrobin ># server app1 127.0.0.1:5001 check ># server app2 127.0.0.1:5002 check ># server app3 127.0.0.1:5003 check ># server app4 127.0.0.1:5004 check > >frontend qpid-admin-vip > bind 10.34.61.60:5672 > default_backend qpid > >backend qpid > balance roundrobin > server allinone 10.34.60.119:5672 check inter 2s > server qpidd 10.34.61.102:5672 check inter 2s >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 1036518
: 851047