dea75ed695
* install_modules.sh: Add puppetlabs-haproxy forge module. * modules/cgit/manifests/init.pp: Add haproxy config to load balance https, https and git protocol git access. Each git server will host git http on port 8080, https on port 4443 and git protocol on 29418. These endpoints will then be load balanced by a single haproxy instance listening on ports 80, 443 and 9418. The use of haproxy and having services listen on offset ports to accomodate haproxy is toggleable using the $balance_git and $behind_proxy boolean flags. Additionally, configure rsyslog for haproxy. * modules/cgit/files/rsyslog.haproxy.conf: Enable syslog over UDP on port 514. This is needed by haproxy to perform logging. Send local0 messages to /var/log/haproxy.log. * modules/cgit/templates/ssl.conf.erb: Make Apache https listen port configurable. Remove default virtualhost. * modules/cgit/templates/httpd.conf.erb: Make Apache http listen port configurable. * modules/cgit/templates/git.vhost..erb: Make Apache http(s) listen ports configuruable. Allow http without redirecting to https as a fallback option to accomodate CentOS clients. * modules/openstack_project/manifests/git.pp: Pass load balancer variables through to the cgit manifest. * manifests/site.pp: Configure git.o.o to run the load balancer haproxy and balance across the new gitXX.o.o nodes. Change-Id: Icefc5923cff9a7c6ce62c1923ec2ea87ebc6474a
69 lines
2.5 KiB
Plaintext
69 lines
2.5 KiB
Plaintext
#
|
|
# This is the Apache server configuration file providing SSL support.
|
|
# It contains the configuration directives to instruct the server how to
|
|
# serve pages over an https connection. For detailing information about these
|
|
# directives see <URL:http://httpd.apache.org/docs/2.2/mod/mod_ssl.html>
|
|
#
|
|
# Do NOT simply read the instructions in here without understanding
|
|
# what they do. They're here only as hints or reminders. If you are unsure
|
|
# consult the online docs. You have been warned.
|
|
#
|
|
|
|
LoadModule ssl_module modules/mod_ssl.so
|
|
|
|
#
|
|
# When we also provide SSL we have to listen to the
|
|
# the HTTPS port in addition.
|
|
#
|
|
Listen <%= scope.lookupvar("cgit::https_port") %>
|
|
|
|
##
|
|
## SSL Global Context
|
|
##
|
|
## All SSL configuration in this context applies both to
|
|
## the main server and all SSL-enabled virtual hosts.
|
|
##
|
|
|
|
# Pass Phrase Dialog:
|
|
# Configure the pass phrase gathering process.
|
|
# The filtering dialog program (`builtin' is a internal
|
|
# terminal dialog) has to provide the pass phrase on stdout.
|
|
SSLPassPhraseDialog builtin
|
|
|
|
# Inter-Process Session Cache:
|
|
# Configure the SSL Session Cache: First the mechanism
|
|
# to use and second the expiring timeout (in seconds).
|
|
SSLSessionCache shmcb:/var/cache/mod_ssl/scache(512000)
|
|
SSLSessionCacheTimeout 300
|
|
|
|
# Semaphore:
|
|
# Configure the path to the mutual exclusion semaphore the
|
|
# SSL engine uses internally for inter-process synchronization.
|
|
SSLMutex default
|
|
|
|
# Pseudo Random Number Generator (PRNG):
|
|
# Configure one or more sources to seed the PRNG of the
|
|
# SSL library. The seed data should be of good random quality.
|
|
# WARNING! On some platforms /dev/random blocks if not enough entropy
|
|
# is available. This means you then cannot use the /dev/random device
|
|
# because it would lead to very long connection times (as long as
|
|
# it requires to make more entropy available). But usually those
|
|
# platforms additionally provide a /dev/urandom device which doesn't
|
|
# block. So, if available, use this one instead. Read the mod_ssl User
|
|
# Manual for more details.
|
|
SSLRandomSeed startup file:/dev/urandom 256
|
|
SSLRandomSeed connect builtin
|
|
#SSLRandomSeed startup file:/dev/random 512
|
|
#SSLRandomSeed connect file:/dev/random 512
|
|
#SSLRandomSeed connect file:/dev/urandom 512
|
|
|
|
#
|
|
# Use "SSLCryptoDevice" to enable any supported hardware
|
|
# accelerators. Use "openssl engine -v" to list supported
|
|
# engine names. NOTE: If you enable an accelerator and the
|
|
# server does not start, consult the error logs and ensure
|
|
# your accelerator is functioning properly.
|
|
#
|
|
SSLCryptoDevice builtin
|
|
#SSLCryptoDevice ubsec
|