Puppet users - Aug 2013 - Adding Foreman to an existing Puppet master

Greetings:

Sorry for cross-posting this question, but I haven''t gotten any love 
over on the Google Forum for Foreman
users<https://groups.google.com/forum/#!forum/foreman-users> (their
forum isn''t as active as this one). I only recently learned about The 
Foreman and I''d like to deploy it on a 64-bit Ubuntu 12.04 LTS
workstation
to provision/manage a bunch of VPSs. I have an existing master-agent Puppet 
deployment w/PuppetDB on it''s own VPS. In the Foreman 1.2 Installation 
Manual, the following is mentioned in a couple of places:

The Foreman installer uses Puppet to install Foreman. This guide assumes
> that you''ve already installed Puppet (without a master)...

Unless there''s a huge benefit to allowing the Foreman installer to 
overwrite my current puppetmaster configs, I''d like to keep my existing
Puppet master. In perusing through the manual, I then came across *3.2.2 
Installer Options*, which suggests that ''all with the world''
will be grand
and wonderful again, if I simply copy & edit the answers file found at 
/usr/share/foreman-installer/foreman_installer/answers.yaml.

I continued reading and then came across the following: "Other examples are
given in /usr/share/foreman-installer/README.md." Being the obedient-fellow
that I am, I went ahead and read the README file; because, at this point, 
my biggest question is this:

If I, in the *answers.yaml* file, set the *puppet* and *puppetmaster* variables
> to *false*, do I need to go back once the Foreman install is finished and 
> patch The Foreman to my existing puppetmaster that I am stubbornly hanging 
> on to?

In the README file, I came across the following:

Extras

------

If you just want to include the relavant bits to run on your puppet master
> you may
    include foreman::params, foreman::config::enc, foreman::config::reports


What exactly does "If you just want to include the relavant bits to run on 
your puppet master you may...." mean? Are those parameters what those with 
an existing Puppet master need to/should include? If so... where/when? 
Before running The Foreman Installer? In the *answers.yaml* file?

Thanks!

-Pablo

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

I just did a bunch of work in order to have puppet modules for the foreman 
that integrate with puppetlabs'' modules. You can find them in 
http://github.com/olindata/puppet-foreman. It''s a WIP, but it works for
me
for a CentOS 6 setup. Feel free to check it out.

cheers,

Walter

On Wednesday, August 7, 2013 8:44:56 PM UTC+2, Pablo Carranza
wrote:
>
> Greetings:
>
> Sorry for cross-posting this question, but I haven''t gotten any
love
> over on the Google Forum for Foreman
users<https://groups.google.com/forum/#!forum/foreman-users> (their
> forum isn''t as active as this one). I only recently learned about
The
> Foreman and I''d like to deploy it on a 64-bit Ubuntu 12.04 LTS
workstation
> to provision/manage a bunch of VPSs. I have an existing master-agent Puppet
> deployment w/PuppetDB on it''s own VPS. In the Foreman 1.2
Installation
> Manual, the following is mentioned in a couple of places:
>
> The Foreman installer uses Puppet to install Foreman. This guide assumes 
>> that you''ve already installed Puppet (without a master)...
>
>
> Unless there''s a huge benefit to allowing the Foreman installer to
> overwrite my current puppetmaster configs, I''d like to keep my
existing
> Puppet master. In perusing through the manual, I then came across *3.2.2 
> Installer Options*, which suggests that ''all with the
world'' will be
> grand and wonderful again, if I simply copy & edit the answers file
found
> at /usr/share/foreman-installer/foreman_installer/answers.yaml.
>
> I continued reading and then came across the following: "Other
examples
> are given in /usr/share/foreman-installer/README.md." Being the 
> obedient-fellow that I am, I went ahead and read the README file; because, 
> at this point, my biggest question is this:
>
> If I, in the *answers.yaml* file, set the *puppet* and *puppetmaster*
variables
>> to *false*, do I need to go back once the Foreman install is finished 
>> and patch The Foreman to my existing puppetmaster that I am stubbornly 
>> hanging on to?
>
>
> In the README file, I came across the following:
>
> Extras
>
> ------
>
> If you just want to include the relavant bits to run on your puppet master 
>> you may
>
>     include foreman::params, foreman::config::enc, foreman::config::reports
>
>
> What exactly does "If you just want to include the relavant bits to
run on
> your puppet master you may...." mean? Are those parameters what those
with
> an existing Puppet master need to/should include? If so... where/when? 
> Before running The Foreman Installer? In the *answers.yaml* file?
>
> Thanks!
>
> -Pablo
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.