Bug #3119
closed
Documentation issue in 3.2.2 Installer Options
Added by Duncan Innes over 10 years ago.
Updated almost 6 years ago.
Description
The Foreman 1.3 manual:
http://theforeman.org/manuals/1.3/index.html#3.2.2InstallerOptions
doesn't match up with what I see on my box after installing foreman-installer.
The file /usr/share/foreman-installer/foreman_installer/answers.yaml doesn't exist, but I do have a /usr/share/foreman-installer/config/answers.yaml file. The contents of this don't match what appears in the documentation:
- Format:
- <classname>: false - don't include this class
- <classname>: true - include and use the defaults
- <classname>:
- <param>: <value> - include and override the default(s)
#
- See params.pp in each class for what options are available
---
foreman: true
foreman_proxy: true
puppet:
server: true
Not a big difference, but documentation suggests:
---
foreman: true
puppet: true
puppetmaster: true
foreman_proxy: true
and I'm not sure what to do with the Puppet side of things.
For information, I'm trying to install Foreman on a single server, Puppetmaster on another single server, and finally the PostgreSQL database for Foreman on another server.
- Project changed from Foreman to Website
- Category deleted (
21)
- Status changed from New to Assigned
- Assignee set to Dominic Cleal
- Target version set to 1.3.0
Thanks, I'm going to have a go at rewriting the installer sections over the next few days, it needs an update to the whole section with 1.3 as we replaced the wrapper with kafo.
Thanks. If there's the possibility of being able to install as I'm trying to do, I'd be grateful of some pointers in the Docs when they arrive.
I'll be having a go using RPM install for now. Trying to fully automate the install from Satellite kickstart.
Yes, it's very much possible without needing to install and configure everything from RPMs (a lot of work). Run foreman-installer and there are options to configure the database - you'll want to disable db_manage and set db_type/host/database/username etc to point to your other server.
For the puppetmaster, I'd first install that using foreman-installer and setting --foreman=false etc, only installing the puppetmaster, puppet agent and foreman-proxy. Run "puppet cert generate <fqdn of foreman server>" on your new puppetmaster, copy the generated private key, cert and ca.pem to your Foreman host and then run the foreman-installer with --puppet-server=false. This will be the sequence I hope to document.
So should I be using foreman-installer with loads of -- options, or is it better to deploy the foreman-installer-answers.yaml file that I want on each server and just run foreman-installer without options?
Entirely up to you! It'll persist the -- options into the answer file if you run it with those, so you can do it once and re-run it easily.
- Status changed from Assigned to Ready For Testing
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Also available in: Atom
PDF
Updated by 
Updated by