layout | title | canonical |
---|---|---|
default |
Split Puppet Enterprise Install, PuppetDB Answer File Reference |
/pe/latest/install_split_puppetdb_answers.html |
The following example answers can be used as baseline to perform an automated split installation of PE on the node assigned to the PuppetDB component.
A .txt file version can be found in the answers
directory of the PE installer tarball.
See Installing with an answer file for more details. In addition, the Complete Answer File Reference contains all answers that you can use to install PE.
Warning: If you're performing a split installation of PE using an answer file, install the components in the following order:
- Puppet master
- Puppet DB and database support (which includes the console database)
- The PE console
These answers are always needed.
Y or N --- Whether to install. Answer files must set this to "Y".
Y or N --- Whether the installer has permission to install additional packages from the OS’s repositories. If this is set to "N", the installation will fail if the installer detects missing dependencies.
These answers are optional.
Y or N --- Only used on AIX. Whether to run updtvpkg
command to add info about native libraries to the RPM database. The answer should usually be "Y", unelss you have special needs around the RPM.
These answers are always needed.
Y or N --- Whether to install the Puppet master component.
Y or N --- Whether to install the database support (the console Postgres server and PuppetDB) component.
These answers are optional.
Y or N --- Whether to install the Puppet agent component.
These answers are always needed.
String --- An identifying string for this agent node. This per-node ID must be unique across your entire site. Fully qualified domain names are often used as agent certnames.
String --- The hostname of the Puppet master server. For the agent to trust the master’s certificate, this must be one of the valid DNS names you chose when installing the Puppet master.
Y or N --- Whether to quit the install if the Puppet master cannot be reached.
Y or N --- This is a silent install option, default is "N". When set to "Y", the installer will skip master verification which allows the user to deploy agents when they know the master won’t be available.
These answers are generally needed if you are installing the Puppet master role.
String --- An identifying string for the puppet master. This ID must be unique across your entire site. The server’s fully qualified domain name is often used as the Puppet master’s certname.
These answers are optional.
String --- The location from which PE agent tarballs will be downloaded before installation. Note that agent tarballs are only available for certain operating systems. For details, see the PE agent installation instructions.
These answers are only needed if you are installing the database support role.
Y or N --- Whether or not to install the PostgreSQL server that supports the console.
String --- The database PuppetDB will use.
String --- The password for PuppetDB’s root user.
String --- PuppetDB’s root user name.
String --- The database the RBAC service will use.
String --- The password for the RBAC service root user.
String --- The RBAC service root user name.
String --- The database the activity service will use.
String --- The password for the activity service root user.
String --- The activity service root user name.
String --- The database the orchestrator service will use.
String --- The password for the orchestrator service root user.
String --- The orchestrator service root user name.
String --- The database the node classifier will use.
String --- The password for the node classifer root user.
String --- The node classifier root user name.
String --- The password for the console's PostgreSQL user.
String --- The console's PostgreSQL root user name.
Integer --- The port on which PuppetDB accepts plain-text HTTP connections (default port is 8080).