Repository files navigation

You can install a PostgreSQL node with the PE installer starting in PE 2016.2. As far as I see it there are not many reasons to install an OSS PostgreSQL server any longer when PE will take care of it for you.

Here's a link to the docs on how to do that:https://docs.puppet.com/pe/latest/install_separate_pe_postgres.html

This puppet module will configure an external PostgreSQL node for your Puppet Enterprise infrastructure.

It will do the following things:

• Install postgresql 9.6
• Install postgresql-contrib package
• Create databases and users that are required by PE
• Install the citext module on the rbac databse which is required by PE
  • https://docs.puppetlabs.com/pe/latest/install_upgrading_notes.html#a-note-about-rbac-node-classifier-and-external-postgresql
• Install the pgcrypto extension on the pe-puppetdb database and the pe-rbac

In order to effectively use this module you will need to do the following in the context of installing PE.

1. Install the PE agent on the node you want to make your external postgresql node

• If you are installing a split installation you can install the puppet master node before installing this agent
• If you are installing an all-in-one master you will need to install this agent and continue when it says it can't connect to the master

2. Save something like the following to a file (maybe/tmp/postgresql_setup.pp) on your agent node but specify your own passwords

class { 'pe_external_postgresql' :  postgres_root_password   => 'pass1',  puppetdb_db_password     => 'pass2',  classifier_db_password   => 'pass3',  rbac_db_password         => 'pass4',  activity_db_password     => 'pass5',  orchestrator_db_password => 'pass6',}

3. puppet module install npwalker-pe_external_postgresql
4. Runpuppet apply /tmp/postgresql_setup.pp on the agent node to install postgresql and setup the databases.

Sets the password for the postgres user.

Sets the password for the puppetdb user to connect to the puppetdb database

Sets the password for the console user to connect to the console database

Sets the password for the pe-classifier user to connect to the pe-classifier database

Sets the password for the pe-rbac user to connect to the pe-rbac database

Sets the password for the pe-activity user to connect to the pe-activity database

Sets the password for the pe-orchestrator user to connect to the pe-orchestrator database

The version of postgresql to install. Defaults to 9.4.

If set totrue, PostgreSQL will be installed using the Puppet Enterprisepackages and paths. Note that for this option to work, you must have thepe-postgresql and pe-postgresql-contrib packages available in the configuredmachine's package repositories. Typically agent machines will have access tothese packages through thepe_repo class. Defaults tofalse.

Whether or not to manage the PE console databases. If set tofalse, thepe-activity,pe-classifier, andpe-rbac databases willnot be managed. This is useful when installing the Console and PuppetDBdatabases on separate servers. Defaults totrue.

Whether or not to manage the PE PuppetDB database. If set tofalse, thepe-puppetdb database will not be managed. This is useful when installing theConsole and PuppetDB databases on separate servers. Defaults totrue.

Whether or not to manage the PE Orchestrator database. If set tofalse, thepe-orchestrator database will not be managed. I would expect users to placethis database with the console database but want to leave the option to put itsomewhere else. Defaults totrue.

If you are using PE3.x please use version 1.1.1 of the module which is compatiblewith older versions of PE.