Puppet users - Apr 2013 - Using puppet to install puppet modules

Hi people,

I use puppet forge to install various modules on my puppetmaster. I''m 
thinking about the build process if I build a new puppetmaster. Manually 
reinstalling the modules is prone to error if I forget which modules I 
used to have.

I looked at this module[1] as a way of making puppet automatically 
install its own modules. But then I realised - if I am building a 
puppetmaster from scratch then it won''t have the ability to use this 
module to install itself... chicken and egg.

How have other people handled this?

Cheers,
Jonathan


[1] https://forge.puppetlabs.com/rcoleman/puppet_module

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

I usually package the modules that I want in the native package manager of
the system.

Much easier to track and the ''package'' statement works just
fine.

Trevor


On Fri, Apr 26, 2013 at 6:19 AM, Jonathan Gazeley <
Jonathan.Gazeley@bristol.ac.uk> wrote:
>  Hi people,
>
> I use puppet forge to install various modules on my puppetmaster.
I''m
> thinking about the build process if I build a new puppetmaster. Manually
> reinstalling the modules is prone to error if I forget which modules I used
> to have.
>
> I looked at this module[1] as a way of making puppet automatically install
> its own modules. But then I realised - if I am building a puppetmaster from
> scratch then it won''t have the ability to use this module to
install
> itself... chicken and egg.
>
> How have other people handled this?
>
> Cheers,
> Jonathan
>
>
> [1] https://forge.puppetlabs.com/rcoleman/puppet_module
>
> --
> 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?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>


-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvaughan@onyxpoint.com

-- This account not approved for unencrypted proprietary information --

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

On Fri, Apr 26, 2013 at 3:19 AM, Jonathan Gazeley <
Jonathan.Gazeley@bristol.ac.uk> wrote:
> How have other people handled this?
>
In addition to Puppet''s built-in `puppet module` tool, there''s
a project
called librarian-puppet that lets you express your Forge modules in a
bundler like way. http://librarian-puppet.com/


-- 
Ryan Coleman | Modules & Forge | @ryanycoleman | ryancoleman in #puppet

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

I can second that. Not sure why puppetlabs decided to invent yet another
package system with it''s own problems and metadata definition and
updates specifics

-- 
Nikola

On Fri, Apr 26, 2013 at 09:02:53AM -0400, Trevor Vaughan
wrote:
> I usually package the modules that I want in the native package manager of
> the system.
> 
> Much easier to track and the ''package'' statement works
just fine.
> 
> Trevor
> 
> 
> On Fri, Apr 26, 2013 at 6:19 AM, Jonathan Gazeley <
> Jonathan.Gazeley@bristol.ac.uk> wrote:
> 
> >  Hi people,
> >
> > I use puppet forge to install various modules on my puppetmaster.
I''m
> > thinking about the build process if I build a new puppetmaster.
Manually
> > reinstalling the modules is prone to error if I forget which modules I
used
> > to have.
> >
> > I looked at this module[1] as a way of making puppet automatically
install
> > its own modules. But then I realised - if I am building a puppetmaster
from
> > scratch then it won''t have the ability to use this module to
install
> > itself... chicken and egg.
> >
> > How have other people handled this?
> >
> > Cheers,
> > Jonathan
> >
> >
> > [1] https://forge.puppetlabs.com/rcoleman/puppet_module
> >
> > --
> > 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?hl=en.
> > For more options, visit https://groups.google.com/groups/opt_out.
> >
> >
> >
> 
> 
> 
> -- 
> Trevor Vaughan
> Vice President, Onyx Point, Inc
> (410) 541-6699
> tvaughan@onyxpoint.com
> 
> -- This account not approved for unencrypted proprietary information --
> 
> -- 
> 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?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
> 
> 
-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

On Wed, May 15, 2013 at 10:48 AM, Nikola Petrov <nikolavp@gmail.com>
wrote:
> I can second that. Not sure why puppetlabs decided to invent yet another
> package system with it''s own problems and metadata definition and
> updates specifics
>
While I''m not disagreeing that this is a pain, I think part of the
difficulty with using system packages is they tend to assume you have one
set of files going into one place.   How do you easily package up a module
when you want it to go into:

/etc/puppet/environments/production/x
/etc/puppet/environments/dev/x

Keeping in mind everyone has a different number of environments they want
modules in.  I think that definitely makes things complex for OS level
packaging.  Having said that, package{} really should grow a puppetmodule
provider to make some of this easier. :)

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

On 26.04.2013 12:19, Jonathan Gazeley wrote:
> I use puppet forge to install various modules on my puppetmaster.
I''m
> thinking about the build process if I build a new puppetmaster. Manually
> reinstalling the modules is prone to error if I forget which modules I
> used to have.
>
> I looked at this module[1] as a way of making puppet automatically
> install its own modules. But then I realised - if I am building a
> puppetmaster from scratch then it won''t have the ability to use
this
> module to install itself... chicken and egg.
>
> How have other people handled this?

I''ve put all puppet modules I''m deploying into a central git
repo. This
is my source of truth. It has branches for each environment (currently 
not used here). There is a script on the puppetmaster polling the repo 
(or reacting to triggers, depending on the client''s setup) which
updates
all environments from the branches.

Setting up a new puppetmaster in an already running system is easy: 
there''s a puppetmaster class that clones the required repos and deploys
the scripts and keys.

Bootstrapping a new puppetmaster from scratch requires installing enough 
software and repos to run puppet apply on a puppetmaster.pp script.

The public working code can be found on github:
> https://github.com/DavidS/dasz-configuration
The puppetmaster vagrant box is bootstrapped each time the box is 
rebuilt using the configuration in
>
https://github.com/DavidS/dasz-configuration/blob/master/manifests/puppetmaster.pp
The production puppetmaster is configured very similarly using this node 
definition:
>
https://github.com/DavidS/dasz-configuration/blob/master/manifests/nodes/puppetmaster.dasz.at.pp
Note the additional "secrets" repo. I''ve not yet added the
pull scripts
to this version.



Regards, David

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.