|
[[TOC]]
+ +HA Proxy is a very powerful and popular open source load
-balanacer to balance incoming requests between multiple instances of web-,
+balancer to balance incoming requests between multiple instances of web-,
application- or database servers etc.
cd_haproxy automates installation and configuration of
HA proxy including self-healing, monitoring and firewall etc.
**__!!! Attention: Never use this puppet module on systems which have
been previously configured manually. It is impossible to predict how and
-what would have been configured, hence previuos configurations outside the
+what would have been configured, hence previous configurations outside the
scope of this module may be overwritten! Automated configurations require a
test environment to verify that the module suits the purpose intended by
the user, as well as tune the parameters, before deploying into live
production!!! __**
INSTALLATION
install rpm binaries
CONFIGURATION
+manage haproxy user
+manage directories (file system permissions, selinux context)
+manage files (file system permissions, content, selinux context)
+manage proxy instances through a define
+frontend options
+backend options
+ACL options
+INSTALLATION * install rpm binaries
+SERVICE
+manage haproxy service
+restart service after changes in the configuration
+CONFIGURATION * manage haproxy user * manage directories (file system -permissions, selinux context) * manage files (file system permissions, -content, selinux context) * manage proxy instances through a define * -frontend options * backend options * ACL options
+SERVICE * manage haproxy service * restart service after changes in the -configuration
- -Repostructure has moved to REPOSTRUCTURE.md in repo.
- -See the full Puppet documentation in docs/index.html
- -All dependencies must be included in the catalogue.
cd_resources +href="https://gitlab.confdroid.com/12WW1160/cd_resources">cd_resources for managing yum base repos
via site.pp or nodes.pp
@@ -160,41 +138,30 @@ managing file fragments include cd_haproxy } -In order to apply parameters through Foreman, -cd_haproxy::params must be added to the host or hostgroup -in question.
+Add params.pp to the host or hostgroup.
See more -details about class deployment on Confdroid.com.
+href="https://confdroid.com/2017/05/deploying-our-puppet-modules/">details. -The following parameters are editable via params.pp or through ENC -(recommended). Values changed will take immediate effect -at next puppet run. Services will be restarted where neccessary.
+The full -list of Parameters is available here and in -the docs folder in the software repo.
+The parameters are defined and described in params.pp. The
+documentation is provided via puppet strings in HTML format,
+please see doc/index.html via web browser.
hy_host_fqdn: Specify the FQDN of the host(s) where HA proxy
-should be running. The module will install it only on the host in question.
The proxy instances are configured in /etc/haproxy/haproxy.cfg, which is -concatenated from various templates through a define in this puppet module. -In order to create proxy instances, you will need an external class, which -addresses the define, like so:
+The proxy instances are configured in
+/etc/haproxy/haproxy.cfg, which is concatenated from various
+templates through a define in this puppet module. In order to create proxy
+instances, you will need an external class, which addresses the define,
+like so:
cd_haproxy::server::proxy { 'testing':
haproxy_fqdn => 'node.example.net',
@@ -205,65 +172,59 @@ addresses the define, like so:
backend_name => 'test01-backend',
}This allows the puppet module to create the sections in the configuration
-file as required. The haproxy service will be restarted after the changes
-in the configuration file are made. haproxy_fqdn
-must contain the fqdn of the haproxy
-server where this should be configured, otherwise the
-templates are not being populated. Multiple ACLs need to be added as array,
-and will create one line each.
This class should be placed in an internal configuration repo specific to +your environment.
-All files and directories are configured with correct selinux context. If selinux is disabled, these contexts are ignored.
-OS: CentOS 7
Puppet 5.x
Puppet Lint
excluded tests:
--no-class_inherits_from_params_class-check:relavant only to
+
--no-class_inherits_from_params_class-check:relevant only to
non-supported outdated puppet versions
--no-variable_scope-check: not applicable as we are inheriting
-parameters from params class. the lint check does not distinguish between
-facts and inherited parameters.
--no-80chars-check: it is not always possible to stay within
-80 characters, although typically only occurring on the parameter vault
+
--no-80chars-check: it is not always possible to stay within
+80 characters, although typically only occurring on the parameter vault
params.pp.
--no-arrow_alignment-check: this check leads to actually not
-having am easily readable arrow alignment, as this checks per
-block, not per class.
per
+block, not per class.
Puppet Parser
ERB Template Parser
Test for unwanted UTF8 files in the Puppet code as this causes problems -with PuppetDB (see tests/UTF_Files)
- -Test for unwanted UTF8 files
ConfDroid as entity is entirely independent from Puppet. We provide custom +
+ +ConfDroid as entity is independent from Puppet. We provide custom configuration modules, written for specific purposes and specific environments. The modules are tested and supported only as documented, and require testing in designated environments (i.e. lab or development diff --git a/doc/index.html b/doc/index.html index dc57f2c..7c8cf3e 100644 --- a/doc/index.html +++ b/doc/index.html @@ -61,98 +61,76 @@
|
[[TOC]]
+ +HA Proxy is a very powerful and popular open source load
-balanacer to balance incoming requests between multiple instances of web-,
+balancer to balance incoming requests between multiple instances of web-,
application- or database servers etc.
cd_haproxy automates installation and configuration of
HA proxy including self-healing, monitoring and firewall etc.
**__!!! Attention: Never use this puppet module on systems which have
been previously configured manually. It is impossible to predict how and
-what would have been configured, hence previuos configurations outside the
+what would have been configured, hence previous configurations outside the
scope of this module may be overwritten! Automated configurations require a
test environment to verify that the module suits the purpose intended by
the user, as well as tune the parameters, before deploying into live
production!!! __**
INSTALLATION
install rpm binaries
CONFIGURATION
+manage haproxy user
+manage directories (file system permissions, selinux context)
+manage files (file system permissions, content, selinux context)
+manage proxy instances through a define
+frontend options
+backend options
+ACL options
+INSTALLATION * install rpm binaries
+SERVICE
+manage haproxy service
+restart service after changes in the configuration
+CONFIGURATION * manage haproxy user * manage directories (file system -permissions, selinux context) * manage files (file system permissions, -content, selinux context) * manage proxy instances through a define * -frontend options * backend options * ACL options
+SERVICE * manage haproxy service * restart service after changes in the -configuration
- -Repostructure has moved to REPOSTRUCTURE.md in repo.
- -See the full Puppet documentation in docs/index.html
- -All dependencies must be included in the catalogue.
cd_resources +href="https://gitlab.confdroid.com/12WW1160/cd_resources">cd_resources for managing yum base repos
via site.pp or nodes.pp
@@ -160,41 +138,30 @@ managing file fragments include cd_haproxy } -In order to apply parameters through Foreman, -cd_haproxy::params must be added to the host or hostgroup -in question.
+Add params.pp to the host or hostgroup.
See more -details about class deployment on Confdroid.com.
+href="https://confdroid.com/2017/05/deploying-our-puppet-modules/">details. -The following parameters are editable via params.pp or through ENC -(recommended). Values changed will take immediate effect -at next puppet run. Services will be restarted where neccessary.
+The full -list of Parameters is available here and in -the docs folder in the software repo.
+The parameters are defined and described in params.pp. The
+documentation is provided via puppet strings in HTML format,
+please see doc/index.html via web browser.
hy_host_fqdn: Specify the FQDN of the host(s) where HA proxy
-should be running. The module will install it only on the host in question.
The proxy instances are configured in /etc/haproxy/haproxy.cfg, which is -concatenated from various templates through a define in this puppet module. -In order to create proxy instances, you will need an external class, which -addresses the define, like so:
+The proxy instances are configured in
+/etc/haproxy/haproxy.cfg, which is concatenated from various
+templates through a define in this puppet module. In order to create proxy
+instances, you will need an external class, which addresses the define,
+like so:
cd_haproxy::server::proxy { 'testing':
haproxy_fqdn => 'node.example.net',
@@ -205,65 +172,59 @@ addresses the define, like so:
backend_name => 'test01-backend',
}This allows the puppet module to create the sections in the configuration
-file as required. The haproxy service will be restarted after the changes
-in the configuration file are made. haproxy_fqdn
-must contain the fqdn of the haproxy
-server where this should be configured, otherwise the
-templates are not being populated. Multiple ACLs need to be added as array,
-and will create one line each.
This class should be placed in an internal configuration repo specific to +your environment.
-All files and directories are configured with correct selinux context. If selinux is disabled, these contexts are ignored.
-OS: CentOS 7
Puppet 5.x
Puppet Lint
excluded tests:
--no-class_inherits_from_params_class-check:relavant only to
+
--no-class_inherits_from_params_class-check:relevant only to
non-supported outdated puppet versions
--no-variable_scope-check: not applicable as we are inheriting
-parameters from params class. the lint check does not distinguish between
-facts and inherited parameters.
--no-80chars-check: it is not always possible to stay within
-80 characters, although typically only occurring on the parameter vault
+
--no-80chars-check: it is not always possible to stay within
+80 characters, although typically only occurring on the parameter vault
params.pp.
--no-arrow_alignment-check: this check leads to actually not
-having am easily readable arrow alignment, as this checks per
-block, not per class.
per
+block, not per class.
Puppet Parser
ERB Template Parser
Test for unwanted UTF8 files in the Puppet code as this causes problems -with PuppetDB (see tests/UTF_Files)
- -Test for unwanted UTF8 files
ConfDroid as entity is entirely independent from Puppet. We provide custom +
+ +ConfDroid as entity is independent from Puppet. We provide custom configuration modules, written for specific purposes and specific environments. The modules are tested and supported only as documented, and require testing in designated environments (i.e. lab or development