I spent a few minutes playing with stages as well and they seem like a great
solution to certain problems. Will there be more documentation made available
about how to use stages after final release? All I'm familiar with is what's in
the changelog.
--Ryan
- Original Message -
> From:
Hello All, I'm hoping to figure out how to use stages to reduce how many
require statements are used in a particular module.
I'm using the brief examples in the documentation as a reference but I can't
grep how to implement the staging.
http://docs.puppetlabs.com/references/2.6.0/metaparameter
I have had success with creating a simple parameterised class (cosign) in
2.6.1.RC1
My class looks like this:
class cosign($version="3.0.2-2") {...} ## This sets a default, you can omit
past "=" to ")".
My node definition looks a little like this:
node "foo.edu" {
class { cosign: version =>
- Original Message -
> From: "Jason Koppe"
> To: puppet-users@googlegroups.com
> Sent: Friday, September 3, 2010 7:12:34 AM
> Subject: Re: [Puppet Users] Puppet 2.6.1rc2 does not honor agent's --tags
> option
> Are automatic tags working for others in 2.6?
No, but see: http://projects.
Also see this blog post:
http://www.puppetlabs.com/blog/puppets-google-summer-of-code/ which discusses
this possibly useful module: http://github.com/blkperl/puppet-network
- Original Message -
> From: "Andrew Pollock"
> To: augeas-de...@redhat.com, puppet-users@googlegroups.com
> Cc: "
- Original Message -
> From: "Felix Frank"
> To: puppet-users@googlegroups.com
> Sent: Thursday, October 7, 2010 3:40:01 AM
> Subject: Re: [Puppet Users] puppet push mode
> On 10/07/2010 04:48 AM, Patrick wrote:
> > I'm guessing that it will work if you run it with the -no-deamonize
> >
> > From the 2.6.1 man page:
> >
> > test: Enable the most common options used for testing.
> > These are +onetime+, +verbose+, +ignorecache,
> > +no-daemonize+, and +no-usecacheonfailure+.
> >
> >
> >>
> >> Because --test is what we are using constantly he
I wrote up a blog post the other day of what I'm using at Penn State. Once I'm
more comfortable with stages, my plan is to help enhance the existing stage
documentation. They're great!
Hope this helps.. --Ryan
http://www.personal.psu.edu/ryc108/blogs/puppetmaster/2010/10/automating-shibboleth-
- Original Message -
> From: "Douglas Garstang"
> To: puppet-users@googlegroups.com
> Sent: Friday, October 8, 2010 3:35:52 PM
> Subject: Re: [Puppet Users] Run Stages
>
> Thanks Ryan. I must be missing something pretty fundamental, because
> when I do:
>
>
> class { "yum::client": sta
> - Original Message -
> > From: "Douglas Garstang" < doug.garst...@gmail.com >
>
> > To: puppet-users@googlegroups.com
> > Sent: Friday, October 8, 2010 3:35:52 PM
> > Subject: Re: [Puppet Users] Run Stages
> >
> > Thanks Ryan. I must be missing something pretty fundamental, because
> >
Hello All,
I've been thinking recently about how one could use Puppet to aid in the
process of documenting infrastructure for other administrators, managers and so
forth.
Puppetdoc gets me somewhat close, since I can add content above my class
definitions and have that content associated wit
11 matches
Mail list logo