opuppet/module-icinga2
5
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

adding specific pgsql instructions for centos5

Browse source 
Signed-off-by: Nick Chappell <nick@intronic.org>

Merged from: https://github.com/Icinga/puppet-icinga2/pull/41

refs#7674: https://dev.icinga.org/issues/7674
This commit is contained in:
Devon Mizelle 2014-11-12 15:02:22 -05:00 committed by Nick Chappell
parent bf5440fb3e
commit b139f775a6
1 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
README.md
View file

@ -61,6 +61,22 @@ The example below shows the [Puppet Labs Postgres module](https://github.com/pup
For production use, you'll probably want to get the database password via a [Hiera lookup](http://docs.puppetlabs.com/hiera/1/puppet.html) so the password isn't sitting in your site manifests in plain text.
####Note For CentOS 5
If you are attempting to install Icinga2 server on CentOS 5 (discouraged) and would like to use PostgreSQL, you must provide a non-EOL'd version of it. If you are installing PostgreSQL for the first time, you can tell the module to manage the pgsql YUM repository like so:
<pre>
class { 'postgresql::globals':
manage_package_repo => true,
version => '9.3',
}->
class { 'postgresql::server': }
</pre>
CentOS 5 provides PostgreSQL 9.1 by default, which was end-of-life'd in 2010. Without having the module manage the repo, it will gladly install this crippled version for you which isn't what you want.
**You will still need to declare a database for Icinga2 to access.**
[Usage](id:usage)
-----