Some haproxy config examples

Here are some config snippets from the haproxy setup I mentioned in the last post.  Note that if this looks weird, it probably is - our environment is a bit of a mess, but due to constrained test resources, no cleanup is possible.

Some organizational helpers I used:


  • IP addresses 'make sense' - for example WEB02-IP2 is 192.168.1.62, -IP3 is .63, etc
  • Keep the naming convention for backends consistent
  • Keep things simple
  • Comments only for the first frontend, first backend, unless actual specific notes required
  • Keep spacing consistent, tabs, etc

Frontend Example

frontend domain1_com-http
bind 192.168.0.50:80

# Subdomains: I put relevant subdomains here (just to keep track)
acl is_GKWEB-http hdr(host) -i -f /etc/haproxy/GKWEB-http-urls
# Subdomains: subdomain1 subdomain2
acl is_ITF01-http hdr(host) -i -f /etc/haproxy/ITF01-http-urls
# Subdomains: subdomain1 subdomain2
acl is_WEB34-IP2-http hdr(host) -i -f /etc/haproxy/WEB34-IP2-http-urls
# Subdomains: subdomain1 subdomain2
acl is_WEB02-IP2-http hdr(host) -i -f /etc/haproxy/WEB02-IP2-http-urls

use_backend GKWEB-http if is_GKWEB-http
use_backend ITF01-http if is_ITF01-http
use_backend WEB34-IP2-http if is_WEB34-IP2-http
use_backend WEB02-IP2-http if is_WEB02-IP2-http

default_backend maintenance

SFTP Backend

backend LG01-sftp
balance roundrobin
mode tcp
stick-table type ip size 200k expire 30m
stick on src
server lg01 192.168.1.51:22 check

Backend with IP Session Persistence

backend WEB02-IP2-http
balance roundrobin
# No persistence
server web02-ip2 192.168.1.92:80 check

backend WEB02-IP2-https
balance roundrobin
stick-table type ip size 200k expire 30m
stick on src
server web02-ip2 192.168.1.92:443 check ssl verify none

Backend with Cookie Session Persistence

backend WEB34-IP4-http
balance roundrobin
stick-table type ip size 200k expire 30m
stick on src
cookie SRV_ID prefix
server web03-ip4 192.168.1.64:80 check cookie
server web04-ip4 192.168.1.74:80 check cookie

 backend WEB34-IP4-https
balance roundrobin
stick-table type ip size 200k expire 30m
stick on src
cookie SRV_ID prefix
server web03-ip4 192.168.1.64:443 check cookie ssl verify none
server web04-ip4 192.168.1.74:443 check cookie ssl verify none


Comments

Post a Comment

Popular posts from this blog

Learning through failure - a keyboard creation journey

Image
tl;dr Built a custom keyboard cuz I have weirdo nerve pain issues.   Learned a lot cuz I failed a lot.   Maybe 'do it right the first time' is a bad frame of mind.   The keyboard ended up being kinda nifty.   It has lights, and a trackball, and QMK, and it helps my issues.   \o/ ( tl;dr is internet lingo that means, too long; didn't read ) Pain as a key ingredient An old proverb says, 'necessity is the mother of invention', and that is how this story begins. Over the last few years, age or stress or something has caught up with me and I developed the need to change my human-to-computer interface.  Mousing changed to trackballing.  The traditional keyboard was swapped out for an ergonomic, and then split keyboard.  Complicated multi-finger-and-hand key combinations were replaced by single keypress macros.  And yet more was still needed. It's often said that change only happens with pain - indeed, the organizations many...
Read more

Learning Opportunities - Watching/listening list

Over the last year I've spent a lot of time learning (thank you, long commute & lunch hours).  Many topics ranging from Chef to DevOps to architecture concepts to management concepts and everything in between.  Why have I done this? DevOps Demystified with Ben Rockwood: https://www.youtube.com/watch?v=h5E--QSBVBY DevOps at ancestry.com: https://www.youtube.com/watch?v=pF5ya0q53kk Those two presentations were key in sending me down this road.  First, and most important, was Mr. Rockwood's explanation as to the real 'why', and the point behind DevOps from an operational perspective.  Second, and no less important but for a different reason, the continuous delivery system at ancestry.com really made it real to me because they are a 'Windows shop'.  So much of what I'd been reading about Chef/config mgmt. relied on amazing tools (see the error there?) only available to the Linux world.  Suddenly here's this guy telling me that it's possible...
Read more

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder: You are trying to set up replication for a DFS folder (no existing replication) Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2) You have no issues getting replication configured You see the DFSR folders get created on the other end, but nothing stages Finally you get EventID 4312: The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.    Additional Information:  Folder: F:\Users$\user.name\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D...
Read more