Jeremy Stanley 497df9b4d1 Add backend source port to haproxy logs
When forwarding TCP sockets at OSI layer 4 with haproxy, it helps to
know the ephemeral port from which it sources each connection to the
backend. In this way, backend connections can be mapped to actual
client IP addresses by correlating backend service access logs with
haproxy logs.

Add "[%bi]:%bp" between the frontend name and backend name values
for the default log-format documented here:

    https://www.haproxy.com/blog/haproxy-log-customization/

Change-Id: Ic2623d483d98cd686a85d40bc4f2e8577fb9087f
2020-06-30 19:46:26 +00:00
2020-06-17 14:51:58 -07:00
2020-06-09 10:15:05 +10:00
2020-06-15 14:43:25 -05:00
2016-07-15 12:04:48 -07:00
2019-04-19 19:26:05 +00:00
2018-11-02 08:19:53 +11:00
2019-04-20 09:31:14 -07:00
2020-06-05 12:09:30 -05:00
2019-04-20 09:31:14 -07:00
2014-09-30 12:40:59 -07:00
2020-04-06 18:19:28 +00:00
2018-06-25 11:19:43 +10:00

Puppet Modules

These are a set of puppet manifests and modules that are currently being used to manage the OpenStack Project infrastructure.

The main entry point is in manifests/site.pp.

In general, most of the modules here are designed to be able to be run either in agent or apply mode.

These puppet modules require puppet 2.7 or greater. Additionally, the site.pp manifest assumes the existence of hiera.

See http://docs.openstack.org/infra/system-config for more information.

Documentation

The documentation presented at http://docs.openstack.org/infra/system-config comes from https://opendev.org/opendev/system-config repo's docs/source. To build the documentation use

tox -evenv python setup.py build_sphinx
Description
System configuration for the OpenDev Collaboratory
Readme 154 MiB
Languages
Jinja 37%
Python 36.7%
Shell 13.6%
Dockerfile 3.9%
JavaScript 3%
Other 5.8%