[Puppet Users] Re: puppet administration guidance

[chiggsy]

You'll want  to remember the declarative nature of puppet, that is, the 
manifests  are not recipes, they are applied to the system but in the sense 
of commands. 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/TmRib0F0d3R5Q0FK.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: [Puppet-dev] Re: "Open Source Team" planning meeting summary

[James Turnbull]

Andrew Forgue wrote:
> #5517 - behavior change within 2.6 makes it impossible to override class
> parameters of "included" parametrized classes
> 
> This bug is almost singlehandedly preventing us from using parameterized
> classes. We honestly can't move to 2.7 (and the changes in scope)
> without this being fixed. Reason being, we cannot include a global class
> on all nodes that has settings for all nodes and then override the class
> with updated parameters to the class for a specific set of nodes.
> Parameterized classes, in theory are such a good idea, but the
> implementation and attention after the fact seems to be severely
> lacking. It seems to get pushed back every minor revision for some
> reason, but it would be great if it got fixed.
> 

I think Dan, Jeff et al and I would +1 #5517.

Regards

James


-- 
James Turnbull
Puppet Labs
1-503-734-8571

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: "Open Source Team" planning meeting summary

[Andrew Forgue]

Writing this is groups.google.com's interface, pardon the formatting.

Some bugs that have been causing us a bit of pain that I would really be 
happy if they actually got fixed:

#3910 - Server is not authoritative over client environment when specified 
in an ENC

This particular bug has been open for a year, and it's potentially dangerous 
bug (data disclosure, and indadvertantly deleting files). We'd like to see 
this one fixed since we can have about 20 environments going at a time and 
getting files from other environments is really quite annoying. At least 
it's gotten some attention in the past month or so.

#5517 - behavior change within 2.6 makes it impossible to override class 
parameters of "included" parametrized classes

This bug is almost singlehandedly preventing us from using parameterized 
classes. We honestly can't move to 2.7 (and the changes in scope) without 
this being fixed. Reason being, we cannot include a global class on all 
nodes that has settings for all nodes and then override the class with 
updated parameters to the class for a specific set of nodes. Parameterized 
classes, in theory are such a good idea, but the implementation and 
attention after the fact seems to be severely lacking. It seems to get 
pushed back every minor revision for some reason, but it would be great if 
it got fixed.


Would be happy to provide use-cases or clarification if necessary. 



-Andrew


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/M0JJYjRLS2dnY2NK.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Puppet should correctly support CA trust chains (#3143)

[Jacob Helwig]

On Tue, 31 May 2011 22:01:15 -0600, Alan Sparks wrote:
> 
> On 5/31/2011 9:07 PM, Jacob Helwig wrote:
> > On Tue, 31 May 2011 20:56:47 -0600, Alan Sparks wrote:
> >>
> >>> On Tue, May 31, 2011 at 5:08 PM, Jacob Helwig  >>> > wrote:
> >>>
> >>> Just a quick reminder that we're going to have our planning meeting
> >>> tomorrow.  If you'd like to influence what we end up prioritizing for
> >>> ourselves for the coming week, please speak up.
> >>>
> >>
> >> Apologize for not having a bug number for this, but I recall that
> >> web-of-trust (intermediate CAs) did not work with Puppet as is.  If
> >> that's true, that's a long-standing one I'd like to see fixed...
> >> -Alan
> >>
> > 
> > I think you're talking about #3143.
> > 
> > http://projects.puppetlabs.com/issues/3143
> > 
> 
> Looks right... we need that where I work, is a killer if that has to
> wait for a 2.7ish.mumble release...
> -Alan
> 

Mind elaborating?  I have no idea which version we'll end up targeting
for #3143 when we do end up working on it.

-- 
Jacob Helwig


signature.asc
Description: Digital signature

Re: [Puppet Users] Re: "Open Source Team" planning meeting summary

[Alan Sparks]

On 5/31/2011 9:07 PM, Jacob Helwig wrote:
> On Tue, 31 May 2011 20:56:47 -0600, Alan Sparks wrote:
>>
>>> On Tue, May 31, 2011 at 5:08 PM, Jacob Helwig >> > wrote:
>>>
>>> Just a quick reminder that we're going to have our planning meeting
>>> tomorrow.  If you'd like to influence what we end up prioritizing for
>>> ourselves for the coming week, please speak up.
>>>
>>
>> Apologize for not having a bug number for this, but I recall that
>> web-of-trust (intermediate CAs) did not work with Puppet as is.  If
>> that's true, that's a long-standing one I'd like to see fixed...
>> -Alan
>>
> 
> I think you're talking about #3143.
> 
> http://projects.puppetlabs.com/issues/3143
> 

Looks right... we need that where I work, is a killer if that has to
wait for a 2.7ish.mumble release...
-Alan


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Facts with puppet master --compile

[Yushu Yao]

*Thanks a lot Nan!

I'll give it a try! And let the list know if it works.

-Yushu

*+-+
| Yushu Yao
| Ph:1-510-486-4690
|
| Lawrence Berkeley National Lab
| 1 Cyclotron Road
| Berkeley CA 94720 - USA
+-+




On Tue, May 31, 2011 at 5:41 PM, Nan Liu  wrote:

> On Tue, May 31, 2011 at 4:31 PM, Yushu Yao  wrote:
> > Hi Experts,
> >
> > Sorry for re-posting but I wasn't able to get a definite answer.
> >
> > I noticed there was an issue opened about this (And some posts).
> > https://projects.puppetlabs.com/issues/3646
> >
> > Just wondering what is the best way today to pass facts to puppet master
> > --compile?
>
> Supply the client yaml facts in $vardir/yaml/ directory, matching the
> client certname.
>
> facter --yaml output isn't actually valid, this script should generate
> the right data from the agent:
>
> #!/usr/bin/env ruby
>
> require 'puppet'
> result = Puppet::Node::Facts.new(Puppet[:certname].to_s, Facter.to_hash)
> result.add_local_facts
> result.stringify
> result.downcase_if_necessary
> puts result.to_yaml
>
> Thanks,
>
> Nan
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: "Open Source Team" planning meeting summary

[Jacob Helwig]

On Tue, 31 May 2011 20:56:47 -0600, Alan Sparks wrote:
> 
> > On Tue, May 31, 2011 at 5:08 PM, Jacob Helwig  > > wrote:
> > 
> > Just a quick reminder that we're going to have our planning meeting
> > tomorrow.  If you'd like to influence what we end up prioritizing for
> > ourselves for the coming week, please speak up.
> > 
> 
> Apologize for not having a bug number for this, but I recall that
> web-of-trust (intermediate CAs) did not work with Puppet as is.  If
> that's true, that's a long-standing one I'd like to see fixed...
> -Alan
> 

I think you're talking about #3143.

http://projects.puppetlabs.com/issues/3143

-- 
Jacob Helwig


signature.asc
Description: Digital signature

Re: [Puppet Users] Re: "Open Source Team" planning meeting summary

[Alan Sparks]

On 5/31/2011 7:19 PM, Nigel Kersten wrote:
> 
> 
> On Tue, May 31, 2011 at 5:08 PM, Jacob Helwig  > wrote:
> 
> On Thu, 26 May 2011 09:38:28 -0700, Jacob Helwig wrote:
> >
> > As promised yesterday, here are the results of our first planning
> > meeting.
> >
> > Right now, we're loosely following a Scrum style of development. With
> > the current one-week iteration's backlog outlined below.
> >
> >  * #2128 - Allow arbitrary fact as node_name identifier
> >
> >  * #7224 - Bad english: hostname was not match with the server
> >certificate
> >
> >  * #4416 - Resources cannot be used on the run where they are synced
> >
> >  * Package type V2 (apt)
> >
> >  * Package type V2 (dpkg)
> >
> >  * Package type V2 (aptitude)
> >
> > We're trying to work on things that we know have annoyed people using
> > Puppet. We are very open to any suggestions on what to add to the
> > following iterations, so please vote on tickets in Redmine[1], and
> > comment on these updates.
> >
> > The "Package type V2" items don't currently have any tickets in
> Redmine,
> > but the goal will be to clean up the current package type in the hopes
> > of having a clean, "modern" and well tested type, and set of providers
> > that people can use as a reference when writing their own.  If the
> > experiment in refactoring the package type, and the apt, aptitude, and
> > dpkg providers goes well, we plan on continuing on to the rest of the
> > providers.
> >
> > In addition to the iteration backlog, #7670 and #7681 have become
> > priorities that we will be addressing as soon as we can.
> >
> >  * #7670 - operatingsystem fact incorrect after clear on Ubuntu
> >
> >  * #7681 - Regression, arrays and variables
> >
> > [1] http://projects.puppetlabs.com
> >
> 
> Just a quick reminder that we're going to have our planning meeting
> tomorrow.  If you'd like to influence what we end up prioritizing for
> ourselves for the coming week, please speak up.
> 
> 
> I could be wrong, but I imagine people would quite like to see this
> issue fixed:
> 
> http://projects.puppetlabs.com/issues/7127
> 
> where the prerun_command exiting non-zero doesn't block the run, and I
> believe the postrun_command doesn't change the report status to failed.
> 
> 
> 
>  
> 
> 
> #7670, and #7681 have both been fixed, and merged into the appropriate
> branches to be released.
> 
> I've had one suggestion of working on #650 (Puppet replaces conf
> directories when they are symlinks).
> 
> Right now, the back-log looks the same as it did last wednesday due to
> the two "blockers" popping up, and the long holiday weekend here in the
> States.
> 


Apologize for not having a bug number for this, but I recall that
web-of-trust (intermediate CAs) did not work with Puppet as is.  If
that's true, that's a long-standing one I'd like to see fixed...
-Alan

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: "Open Source Team" planning meeting summary

[Nigel Kersten]

On Tue, May 31, 2011 at 5:08 PM, Jacob Helwig  wrote:

> On Thu, 26 May 2011 09:38:28 -0700, Jacob Helwig wrote:
> >
> > As promised yesterday, here are the results of our first planning
> > meeting.
> >
> > Right now, we're loosely following a Scrum style of development. With
> > the current one-week iteration's backlog outlined below.
> >
> >  * #2128 - Allow arbitrary fact as node_name identifier
> >
> >  * #7224 - Bad english: hostname was not match with the server
> >certificate
> >
> >  * #4416 - Resources cannot be used on the run where they are synced
> >
> >  * Package type V2 (apt)
> >
> >  * Package type V2 (dpkg)
> >
> >  * Package type V2 (aptitude)
> >
> > We're trying to work on things that we know have annoyed people using
> > Puppet. We are very open to any suggestions on what to add to the
> > following iterations, so please vote on tickets in Redmine[1], and
> > comment on these updates.
> >
> > The "Package type V2" items don't currently have any tickets in Redmine,
> > but the goal will be to clean up the current package type in the hopes
> > of having a clean, "modern" and well tested type, and set of providers
> > that people can use as a reference when writing their own.  If the
> > experiment in refactoring the package type, and the apt, aptitude, and
> > dpkg providers goes well, we plan on continuing on to the rest of the
> > providers.
> >
> > In addition to the iteration backlog, #7670 and #7681 have become
> > priorities that we will be addressing as soon as we can.
> >
> >  * #7670 - operatingsystem fact incorrect after clear on Ubuntu
> >
> >  * #7681 - Regression, arrays and variables
> >
> > [1] http://projects.puppetlabs.com
> >
>
> Just a quick reminder that we're going to have our planning meeting
> tomorrow.  If you'd like to influence what we end up prioritizing for
> ourselves for the coming week, please speak up.
>

I could be wrong, but I imagine people would quite like to see this issue
fixed:

http://projects.puppetlabs.com/issues/7127

where the prerun_command exiting non-zero doesn't block the run, and I
believe the postrun_command doesn't change the report status to failed.





>
> #7670, and #7681 have both been fixed, and merged into the appropriate
> branches to be released.
>
> I've had one suggestion of working on #650 (Puppet replaces conf
> directories when they are symlinks).
>
> Right now, the back-log looks the same as it did last wednesday due to
> the two "blockers" popping up, and the long holiday weekend here in the
> States.
>
> --
> Jacob Helwig
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iQGcBAEBAgAGBQJN5YLwAAoJEHJabXWGiqEBTBoMAIgU7JXHtexP2CCfphlIdca+
> oqz5WHH9aJd97mCfHvVAsKiTReY98ugtX9b4Z+1SG3Q7wQTkD4m8uw6ZoITQJwRu
> WgyztfxqZlnvdPZne+bE2XLljAMyehZimxn2sd/gbDxbVHlW0CmP4/8Hz831OlZY
> lChS3UX1SEwSDNEbhjdVpMP5Scse+BGTkTcNevWiFknDpNSEpkGEVNY4J6UFYWhT
> n3MdNw5kToB9DTpDGlG6RbKzjTKJB5eOjDjPerdhxNj0HacFI36qzi6DcSeY7CpQ
> /egZLOTps6Q4ftGxM6YKOXdyeqHSQiLGbBaIYhzEy5PqR3s2fe5FN2f9Aqzrn1LU
> +8R8vo56EGole+Ty1QG75yIHcb2f0OF4ekMIMA4EwDGq/vJkYlppGuBp64k9BR/l
> EadeGbvSRxVKjiuyAUgi/78sKzJ5TN9fX1tULnGC2ud3OFK+cc4s/lgSJMMe7bqz
> s+3pEeUmhj0fVGnEFsaGivnn3swcCiPzSfycZwt7KA==
> =0EHz
> -END PGP SIGNATURE-
>
>


-- 
Nigel Kersten
Product, Puppet Labs
@nigelkersten

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Any good documentation NGINX + Passenger + Puppet?

[Luc Suryo]

Hello,

I been browsing around and can not find any good documentation how to setup
Puppet with Nginx and passenger

I have a working Nginx with passenger support working but then what ?
Kinda confuse and wondering if maybe Passenger is not the way to go ?
Mongrel ? or something different?
any pointer appreciated .



btw I have read :

http://projects.puppetlabs.com/projects/1/wiki/Using_Mongrel_Nginx
and
http://projects/puppetlabs.com/projects/1/wiki/Using_Passenger



and still I do not get it ...


Nginx 1.0.0, Passenger 3.0.7 and puppet 2.6.2


thanks

-- 
-ls

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Facts with puppet master --compile

[Nan Liu]

On Tue, May 31, 2011 at 4:31 PM, Yushu Yao  wrote:
> Hi Experts,
>
> Sorry for re-posting but I wasn't able to get a definite answer.
>
> I noticed there was an issue opened about this (And some posts).
> https://projects.puppetlabs.com/issues/3646
>
> Just wondering what is the best way today to pass facts to puppet master
> --compile?

Supply the client yaml facts in $vardir/yaml/ directory, matching the
client certname.

facter --yaml output isn't actually valid, this script should generate
the right data from the agent:

#!/usr/bin/env ruby

require 'puppet'
result = Puppet::Node::Facts.new(Puppet[:certname].to_s, Facter.to_hash)
result.add_local_facts
result.stringify
result.downcase_if_necessary
puts result.to_yaml

Thanks,

Nan

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Semantic differences between selector and if/then?

[Aaron Grewell]

Should the C-style selector and if/then statements have equivalent
true/false handling?  Maybe I'm setting this up wrong, but I expected these
two to be the same:

if $name[symlink]{ $symlink= $name[symlink]} else { $symlink
= undef}
$symlink= $name[symlink]? { true => $name[symlink],false =>
undef  }

Yet they don't return the same result.  The if/then statement sets the value
to false as expected, whereas the selector never matches at all and throws
an error.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Facts with puppet master --compile

[Patrick]

On May 31, 2011, at 4:31 PM, Yushu Yao wrote:

> Hi Experts,
> 
> Sorry for re-posting but I wasn't able to get a definite answer.
> 
> I noticed there was an issue opened about this (And some posts).  
> https://projects.puppetlabs.com/issues/3646
> 
> Just wondering what is the best way today to pass facts to puppet master 
> --compile?
> 
> As suggested in the ticket above, puppet master —compile ${client_fqdn} 
> —factsfile ${file_full_of_facts} will be great!

I know that the master will cache the facts for clients at 
"/var/lib/puppet/yaml/facts".  What if you pre-populate the facts cache on the 
master?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: "Open Source Team" planning meeting summary

[Jacob Helwig]

On Thu, 26 May 2011 09:38:28 -0700, Jacob Helwig wrote:
> 
> As promised yesterday, here are the results of our first planning
> meeting.
> 
> Right now, we're loosely following a Scrum style of development. With
> the current one-week iteration's backlog outlined below.
> 
>  * #2128 - Allow arbitrary fact as node_name identifier
> 
>  * #7224 - Bad english: hostname was not match with the server
>certificate
> 
>  * #4416 - Resources cannot be used on the run where they are synced
> 
>  * Package type V2 (apt)
> 
>  * Package type V2 (dpkg)
> 
>  * Package type V2 (aptitude)
> 
> We're trying to work on things that we know have annoyed people using
> Puppet. We are very open to any suggestions on what to add to the
> following iterations, so please vote on tickets in Redmine[1], and
> comment on these updates.
> 
> The "Package type V2" items don't currently have any tickets in Redmine,
> but the goal will be to clean up the current package type in the hopes
> of having a clean, "modern" and well tested type, and set of providers
> that people can use as a reference when writing their own.  If the
> experiment in refactoring the package type, and the apt, aptitude, and
> dpkg providers goes well, we plan on continuing on to the rest of the
> providers.
> 
> In addition to the iteration backlog, #7670 and #7681 have become
> priorities that we will be addressing as soon as we can.
> 
>  * #7670 - operatingsystem fact incorrect after clear on Ubuntu
> 
>  * #7681 - Regression, arrays and variables
> 
> [1] http://projects.puppetlabs.com
> 

Just a quick reminder that we're going to have our planning meeting
tomorrow.  If you'd like to influence what we end up prioritizing for
ourselves for the coming week, please speak up.

#7670, and #7681 have both been fixed, and merged into the appropriate
branches to be released.

I've had one suggestion of working on #650 (Puppet replaces conf
directories when they are symlinks).

Right now, the back-log looks the same as it did last wednesday due to
the two "blockers" popping up, and the long holiday weekend here in the
States.

-- 
Jacob Helwig


signature.asc
Description: Digital signature

[Puppet Users] Facts with puppet master --compile

[Yushu Yao]

Hi Experts,

Sorry for re-posting but I wasn't able to get a definite answer.

I noticed there was an issue opened about this (And some posts).
https://projects.puppetlabs.com/issues/3646

Just wondering what is the best way today to pass facts to puppet master
--compile?

As suggested in the ticket above, puppet master —compile ${client_fqdn}
—factsfile ${file_full_of_facts} will be great!

Thanks a lot!

-Yushu

+-+
| Yushu Yao
| Ph:1-510-486-4690
|
| Lawrence Berkeley National Lab
| 1 Cyclotron Road
| Berkeley CA 94720 - USA
+-+

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: ipaddress returned by facter

[Daniel Pittman]

On Tue, May 31, 2011 at 14:04, Tim Coote  wrote:
> Thanks, chaps. Pleased to hear that I'm not mad.  The relationship
> between IP addresses and hosts is non-trivial, especially when you
> wrap in the MAC address concept. It's also asymmetrical in the sense
> that the value seen from 'inside' a host may not relate to the value
> used 'outside'.

Yeah.  If you only ever dealt with the single-homed, single-address
case (or maybe trivial NAT) it is easy to assume that there is "an" IP
address for a host, but in the data center... not so much. :)

> I've been through a lot of pain with this domain
> model elsewhere (happy to provide references for those that are
> interested, but no code, I'm afraid).  There's also complexities if
> one assumes that DNS resolves hostnames to IP addresses: it just
> resolves names to IP addresses.

Yeah; for a non-trivial number of cases this is the least wrong "do
what I mean" answer, but it is absolutely not clear that the hostname
and "the" IP address of a host are the same.  I would only look to
that if either I knew local convention assured it, or as a "less
wrong" answer for this fact for compatibility. :)

> I think that I'm going to ignore this issue for the moment as
> something that just doesn't work yet.

Yah.  Better write your own fact, or resolution, to match local rules.

Daniel

>
> Tim
>
> On May 31, 6:28 pm, Daniel Pittman  wrote:
>> On Tue, May 31, 2011 at 07:40, jcbollinger  wrote:
>> > On May 30, 3:10 pm, Tim Coote  wrote:
>> >> Hullo
>> >> I'm running facter 1.5.8 (fedora 13). I'm not very clear about what
>> >> the variable ipaddress is supposed to represent.
>>
>> > I suggest you read the discussion at
>> >http://groups.google.com/group/puppet-users/browse_thread/thread/f278...,
>> > especially Daniel Pittman's response at the end.  As Daniel observes,
>> > *Facter* is not very clear about what that fact represents.
>>
>> >> I've read that it
>> >> returns the ip address that's bound to the lowest alphabetic name of a
>> >> network interface. That model seems a bit weird to me but that's
>> >> probably because I'm just used to tools that return the set of IP
>> >> addresses associated with the host, as seen from the host.
>>
>> > No, I think it's because you intuitively understand what Daniel wrote,
>> > that Facter's ipaddress fact is not well-defined, and it is not very
>> > meaningful in the general case.
>>
>> *nod*
>>
>> Nothing much has changed since way back when; we still have the same
>> vague definition of what ipaddress means, which is "right" in the
>> trivial case where you have only one IP address, and more or less
>> wrong in any complex case.  (We have a vague plan to try and be a bit
>> more DWIM-ish by, indeed, respecting either the DNS IP for the current
>> hostname, or the IP of the interface with the default route, when
>> there is only one least-specific-route match.  Patches welcome; it
>> isn't super-high priority.)
>>
>> […]
>>
>> >> Facter is returning the IP v4 address on virbr0, which is neither what
>> >> the documentation says, nor much use as I can see that it's likely to
>> >> be the same on all hosts that have libvirt installed. There are no
>> >> IPv6 addresses returned.
>>
>> I think the latest release has IPv6 support, which is distinct from
>> the IPv4 facts.
>>
>> >> Am I seeing the expected behaviour for facter?  Do I have to
>> >> standardise how I name network interfaces and associate IP addresses
>> >> to them to be able to deal with them all in a consistent, meaningful
>> >> way (eg to pick out the IP that's used for backup, or the different IP
>> >> addresses connected to the different edge switches)?
>>
>> I would strongly suggest you use something else.  I did literally
>> standardise on using the resolved IP from DNS, and made it a failure
>> to compile when that failed to resolve.  Your network might not
>> support that, but I would suggest pretending the ipaddress fact just
>> doesn't exist at all.
>>
>> Fixing the interface naming ... nah.  Don't contort your network to
>> support a stupid tool.  Fix the stupid tool.
>>
>> (Incidentally, you should be able to replace the existing ipaddress
>> fact with a better, higher priority version that does respect your
>> needs, by putting a custom fact in place to override the shipped
>> version. :)
>>
>> Daniel
>> --
>> ⎋ Puppet Labs Developer –http://puppetlabs.com
>> ✉ Daniel Pittman 
>> ✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775
>> ♲ Made with 100 percent post-consumer electrons
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
>
>



-- 
⎋ Puppet Labs Developer – http://puppetlabs.com
✉ Daniel Pittman 
✆ Contact me via gtalk, email, o

Re: [Puppet Users] finished, yet execution expired

[Larry Ludwig]

Actually upon further investigation it turned out to be an odd iptables 
firewall rule, unrelated to puppet.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: ipaddress returned by facter

[Tim Coote]

Thanks, chaps. Pleased to hear that I'm not mad.  The relationship
between IP addresses and hosts is non-trivial, especially when you
wrap in the MAC address concept. It's also asymmetrical in the sense
that the value seen from 'inside' a host may not relate to the value
used 'outside'.  I've been through a lot of pain with this domain
model elsewhere (happy to provide references for those that are
interested, but no code, I'm afraid).  There's also complexities if
one assumes that DNS resolves hostnames to IP addresses: it just
resolves names to IP addresses.

I think that I'm going to ignore this issue for the moment as
something that just doesn't work yet.

Tim

On May 31, 6:28 pm, Daniel Pittman  wrote:
> On Tue, May 31, 2011 at 07:40, jcbollinger  wrote:
> > On May 30, 3:10 pm, Tim Coote  wrote:
> >> Hullo
> >> I'm running facter 1.5.8 (fedora 13). I'm not very clear about what
> >> the variable ipaddress is supposed to represent.
>
> > I suggest you read the discussion at
> >http://groups.google.com/group/puppet-users/browse_thread/thread/f278...,
> > especially Daniel Pittman's response at the end.  As Daniel observes,
> > *Facter* is not very clear about what that fact represents.
>
> >> I've read that it
> >> returns the ip address that's bound to the lowest alphabetic name of a
> >> network interface. That model seems a bit weird to me but that's
> >> probably because I'm just used to tools that return the set of IP
> >> addresses associated with the host, as seen from the host.
>
> > No, I think it's because you intuitively understand what Daniel wrote,
> > that Facter's ipaddress fact is not well-defined, and it is not very
> > meaningful in the general case.
>
> *nod*
>
> Nothing much has changed since way back when; we still have the same
> vague definition of what ipaddress means, which is "right" in the
> trivial case where you have only one IP address, and more or less
> wrong in any complex case.  (We have a vague plan to try and be a bit
> more DWIM-ish by, indeed, respecting either the DNS IP for the current
> hostname, or the IP of the interface with the default route, when
> there is only one least-specific-route match.  Patches welcome; it
> isn't super-high priority.)
>
> […]
>
> >> Facter is returning the IP v4 address on virbr0, which is neither what
> >> the documentation says, nor much use as I can see that it's likely to
> >> be the same on all hosts that have libvirt installed. There are no
> >> IPv6 addresses returned.
>
> I think the latest release has IPv6 support, which is distinct from
> the IPv4 facts.
>
> >> Am I seeing the expected behaviour for facter?  Do I have to
> >> standardise how I name network interfaces and associate IP addresses
> >> to them to be able to deal with them all in a consistent, meaningful
> >> way (eg to pick out the IP that's used for backup, or the different IP
> >> addresses connected to the different edge switches)?
>
> I would strongly suggest you use something else.  I did literally
> standardise on using the resolved IP from DNS, and made it a failure
> to compile when that failed to resolve.  Your network might not
> support that, but I would suggest pretending the ipaddress fact just
> doesn't exist at all.
>
> Fixing the interface naming ... nah.  Don't contort your network to
> support a stupid tool.  Fix the stupid tool.
>
> (Incidentally, you should be able to replace the existing ipaddress
> fact with a better, higher priority version that does respect your
> needs, by putting a custom fact in place to override the shipped
> version. :)
>
> Daniel
> --
> ⎋ Puppet Labs Developer –http://puppetlabs.com
> ✉ Daniel Pittman 
> ✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775
> ♲ Made with 100 percent post-consumer electrons

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Extlookup++

[Nigel Kersten]

On Fri, May 27, 2011 at 1:08 PM, R.I.Pienaar  wrote:

> And for what its worth this afternoon just to see how hard it is
> and to again ask to myself 'wtf has no-one done this yet?' and also
> 'wtf are people at Puppet Labs reinventing this wheel?' I wrote
> a new extlookup that has pluggable backends.
>

The bit about reinventing the wheel probably doesn't make sense to most of
this list. RI is referring to something I hacked up as a slightly different
direction to extlookup   which I
didn't send to the list after some chat back and forth between RI and I
convinced me that it wasn't a productive enough direction to head in.


> It has a 100% backward compatible CSV backend and new a YAML backend
>

This is killer work. If you haven't looked at this yet, and are struggling
with data separation, you should definitely check it out.


>
> Backends are easy to add - I will make the interface a little bit better
> in future and I, again, wish Puppet Labs would fix bugs that make it
> easier to deploy Util classes into masters.
>

Apart from that bug RI, what else could we do in core to make this more of a
seamless integration?



> Rather than abuse global variables I added a simple YAML based config
> file.
>
> So, again, I hacked this up this afternoon, its early days and no doubt
> can be improved.  Feedback welcome
>
> https://github.com/ripienaar/puppet-extlookup
>
> - Original Message -
> > Thanks Ohad, this looks very interesting.
> >
> >
> > On Fri, May 27, 2011 at 11:07 AM, Ohad Levy < ohadl...@gmail.com >
> > wrote:
> >
> >
> >
> > fyi, https://github.com/ohadlevy/puppet-lookup exists for a long time
> > too, it also allows you to put your actual data files inside your
> > modules (or mulitple modules with a search / prio path).
> >
> >
> > Ohad
> >
> >
> >
> >
> >
> > On Fri, May 27, 2011 at 7:30 PM, Aaron Grewell <
> > aaron.grew...@gmail.com > wrote:
> >
> >
> >
> >
> >
> > FYI, if you haven't seen ymllookup it's unofficial but worth a test:
> > http://projects.puppetlabs.com/issues/4433
> >
> > For those of us that find extlookup useful ymllookup takes it to the
> > next level and allows lookups in YAML. Having the ability to lookup
> > arrays of hashes has made life so much easier for me.
> >
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com .
> > To unsubscribe from this group, send email to
> > puppet-users+unsubscr...@googlegroups.com .
> > For more options, visit this group at
> > http://groups.google.com/group/puppet-users?hl=en .
> >
> >
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com .
> > To unsubscribe from this group, send email to
> > puppet-users+unsubscr...@googlegroups.com .
> > For more options, visit this group at
> > http://groups.google.com/group/puppet-users?hl=en .
> >
> >
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com.
> > To unsubscribe from this group, send email to
> > puppet-users+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> > http://groups.google.com/group/puppet-users?hl=en.
> >
>
> --
> R.I.Pienaar
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>


-- 
Nigel Kersten
Product, Puppet Labs
@nigelkersten

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: User's Home Folder is not Being created but the user is there.

[vella1tj]

Thanks you're great, I set it up and it's working now I changed my
ensure to absent to delete then change it back to present and added
managehome an it's working great you're ausome thanks man.

On May 31, 1:56 pm, Nigel Kersten  wrote:
> On Tue, May 31, 2011 at 10:50 AM, vella1tj  wrote:
> > user {'trevor' :
> >   uid            => 500,
> >   groups      => 'root',
> >   comment  => 'this user was created by Mr. Puppet',
> >   ensure      => present,
> >   home        => '/home/trevor',
> >   shell         => 'bin/bash',
> > }
>
> > I created this to create a User using puppet this was an exercise
> > given by one of my co-workers to get me to learn puppet quicker, I
> > created this and once it's applied it works I can login as the user
> > but the home directory is not created, This is using CentOS in
> > VMware Fusion.
>
> You want to have a look at the managehome attribute:
>
> http://docs.puppetlabs.com/references/stable/type.html#managehome
>
>
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com.
> > To unsubscribe from this group, send email to
> > puppet-users+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/puppet-users?hl=en.
>
> --
> Nigel Kersten
> Product, Puppet Labs
> @nigelkersten

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: User's Home Folder is not Being created but the user is there.

[vella1tj]

Thanks you're great, I set it up and it's working now I changed my
ensure to absent to delete then change it back to present and added
managehome an it's working great you're ausome thanks man.
On May 31, 1:56 pm, Nick Lewis  wrote:
> On Tuesday, May 31, 2011 at 10:50 AM, vella1tj wrote:
> > user {'trevor' :
> >  uid => 500,
> >  groups => 'root',
> >  comment => 'this user was created by Mr. Puppet',
> >  ensure => present,
> >  home => '/home/trevor',
> >  shell => 'bin/bash',
> > }
>
> > I created this to create a User using puppet this was an exercise
> > given by one of my co-workers to get me to learn puppet quicker, I
> > created this and once it's applied it works I can login as the user
> > but the home directory is not created, This is using CentOS in
> > VMware Fusion.
>
> You'll need to set the 'managehome' parameter to tell Puppet to actually 
> create the home directory.
>
>
>
>
>
>
>
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com 
> > (mailto:puppet-users@googlegroups.com).
> > To unsubscribe from this group, send email to 
> > puppet-users+unsubscr...@googlegroups.com 
> > (mailto:puppet-users+unsubscr...@googlegroups.com).
> > For more options, visit this group 
> > athttp://groups.google.com/group/puppet-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] User's Home Folder is not Being created but the user is there.

[Trevor Vella]

You guys are awesome just added it I delete my trevor user and recreated
it and it's working flawlessly sorry for wasting your time on such a medial
task and thanks so much for getting back to me.

On Tue, May 31, 2011 at 1:56 PM, Nick Lewis  wrote:

> On Tuesday, May 31, 2011 at 10:50 AM, vella1tj wrote:
>
> user {'trevor' :
> uid => 500,
> groups => 'root',
> comment => 'this user was created by Mr. Puppet',
> ensure => present,
> home => '/home/trevor',
> shell => 'bin/bash',
> }
>
> I created this to create a User using puppet this was an exercise
> given by one of my co-workers to get me to learn puppet quicker, I
> created this and once it's applied it works I can login as the user
> but the home directory is not created, This is using CentOS in
> VMware Fusion.
>
> You'll need to set the 'managehome' parameter to tell Puppet to actually
> create the home directory.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
>   --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>



-- 
*Trevor J. Vella*
* *
Cell Phone: 517-677-2225
Email: vella...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] User's Home Folder is not Being created but the user is there.

[Nick Lewis]

On Tuesday, May 31, 2011 at 10:50 AM, vella1tj wrote:

> user {'trevor' :
>  uid => 500,
>  groups => 'root',
>  comment => 'this user was created by Mr. Puppet',
>  ensure => present,
>  home => '/home/trevor',
>  shell => 'bin/bash',
> }
> 
> I created this to create a User using puppet this was an exercise
> given by one of my co-workers to get me to learn puppet quicker, I
> created this and once it's applied it works I can login as the user
> but the home directory is not created, This is using CentOS in
> VMware Fusion.
> 
You'll need to set the 'managehome' parameter to tell Puppet to actually create 
the home directory.
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] User's Home Folder is not Being created but the user is there.

[Nigel Kersten]

On Tue, May 31, 2011 at 10:50 AM, vella1tj  wrote:

> user {'trevor' :
>   uid=> 500,
>   groups  => 'root',
>   comment  => 'this user was created by Mr. Puppet',
>   ensure  => present,
>   home=> '/home/trevor',
>   shell => 'bin/bash',
> }
>
> I created this to create a User using puppet this was an exercise
> given by one of my co-workers to get me to learn puppet quicker, I
> created this and once it's applied it works I can login as the user
> but the home directory is not created, This is using CentOS in
> VMware Fusion.
>

You want to have a look at the managehome attribute:

http://docs.puppetlabs.com/references/stable/type.html#managehome



>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>


-- 
Nigel Kersten
Product, Puppet Labs
@nigelkersten

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] know what the master is currently doing

[Daniel Pittman]

2011/5/31 Carles Amigó :

> Is there any way to see which catalog is currently compiling the puppet
> master?
>
> The puppetmaster log only shows the catalog when it's been already compiled,
> not when it starts compiling it.
>
> In our configuration, we have many puppet masters running after a nginx and
> it would be useful to know what is doing each master process.

Sadly, no.  There was some discussion a while back about the feature,
and Brice had some patches, but they were never merged.

I generally agree that we should be decorating the system with process
status, so that this can be extracted one way or another. :)

Daniel
-- 
⎋ Puppet Labs Developer – http://puppetlabs.com
✉ Daniel Pittman 
✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775
♲ Made with 100 percent post-consumer electrons

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] User's Home Folder is not Being created but the user is there.

[vella1tj]

user {'trevor' :
   uid=> 500,
   groups  => 'root',
   comment  => 'this user was created by Mr. Puppet',
   ensure  => present,
   home=> '/home/trevor',
   shell => 'bin/bash',
}

I created this to create a User using puppet this was an exercise
given by one of my co-workers to get me to learn puppet quicker, I
created this and once it's applied it works I can login as the user
but the home directory is not created, This is using CentOS in
VMware Fusion.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] High CPU usage puppet 2.6.6

[Daniel Pittman]

On Tue, May 31, 2011 at 10:03, Marek Dohojda  wrote:

> I recently upgrade my puppet from .25 to 2.6.6.  The actual upgrade process
> was trivial, but now I am seeing issues.  Puppetmaster is running at very
> high CPU usage.  Prior to the upgrade my load average was at around 2 ( this
> server is doing more stuff than just puppet ), but now I am hitting 12!!!
>
> Is there a known issue with this puppet version that I haven't seen?

No, performance should be fairly similar.  I think the worst cost we
saw was on the order of 15 percent or so extra compile time, which
shouldn't should such a dramatic jump in most cases.  Can you quantify
the performance differences further?

Daniel
-- 
⎋ Puppet Labs Developer – http://puppetlabs.com
✉ Daniel Pittman 
✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775
♲ Made with 100 percent post-consumer electrons

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] uploading files via REST?

[Daniel Pittman]

On Tue, May 31, 2011 at 07:21, RCosma  wrote:
> Hello,
> I am a bit confused by the REST syntax - how can I PUT an arbitrary file in
> the bucket? Downloading works fine (Perl+LWP), see below, but for PUT I only
> see this line in the docs (http://docs.puppetlabs.com/guides/rest_api.html):
> PUT /{environment}/file_bucket_file/md5/{checksum}
> Should I compute the MD5 of the file and port its contents at the url ?

Yeah, you would need to: the indirector, which this is an instance of,
requires that you uniquely identify where you are writing to.  So, in
the case of the filebucket the "key" is that MD5 checksum; you would
need to calculate it for the file and supply it.

There is no support in the indirector for uploading the data with the
server calculating the checksum.

(As a side note, I don't think we actually *check* you were honest
about that, other than when the target checksum already exists, so
please try not to lie about it. ;)

Daniel
-- 
⎋ Puppet Labs Developer – http://puppetlabs.com
✉ Daniel Pittman 
✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775
♲ Made with 100 percent post-consumer electrons

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Removing links

[Nick Lewis]

On Tuesday, May 31, 2011 at 2:58 AM, John Kennedy wrote:

> I have a group of web servers being load balanced. I have 4 types of servers 
> all build from the same image. 
> When I build the image I forgot to clear out one of the sym links from 
> sites-enabled to sites-available. This is causing problems with the web 
> servers. I have tried to have puppet remove the link but have had little 
> success. I have tried the following:
> file { "/opt/nginx/sites-enabled/ absent }
> This will remove a file if it is there but not this link.
> What am I missing? I have googled to get the above which I thought would 
> remove the link.
> Thanks,
> John
> 
Which Puppet version are you using? This looks similar to #6856 which was fixed 
in 2.6.8. It could also be #4932.

> -- 
> John Kennedy
> 
>  -- 
>  You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
>  To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
>  To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
>  For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: ipaddress returned by facter

[Daniel Pittman]

On Tue, May 31, 2011 at 07:40, jcbollinger  wrote:
> On May 30, 3:10 pm, Tim Coote  wrote:
>> Hullo
>> I'm running facter 1.5.8 (fedora 13). I'm not very clear about what
>> the variable ipaddress is supposed to represent.
>
> I suggest you read the discussion at
> http://groups.google.com/group/puppet-users/browse_thread/thread/f278468018b13a32,
> especially Daniel Pittman's response at the end.  As Daniel observes,
> *Facter* is not very clear about what that fact represents.
>
>> I've read that it
>> returns the ip address that's bound to the lowest alphabetic name of a
>> network interface. That model seems a bit weird to me but that's
>> probably because I'm just used to tools that return the set of IP
>> addresses associated with the host, as seen from the host.
>
> No, I think it's because you intuitively understand what Daniel wrote,
> that Facter's ipaddress fact is not well-defined, and it is not very
> meaningful in the general case.

*nod*

Nothing much has changed since way back when; we still have the same
vague definition of what ipaddress means, which is "right" in the
trivial case where you have only one IP address, and more or less
wrong in any complex case.  (We have a vague plan to try and be a bit
more DWIM-ish by, indeed, respecting either the DNS IP for the current
hostname, or the IP of the interface with the default route, when
there is only one least-specific-route match.  Patches welcome; it
isn't super-high priority.)


[…]
>> Facter is returning the IP v4 address on virbr0, which is neither what
>> the documentation says, nor much use as I can see that it's likely to
>> be the same on all hosts that have libvirt installed. There are no
>> IPv6 addresses returned.

I think the latest release has IPv6 support, which is distinct from
the IPv4 facts.

>> Am I seeing the expected behaviour for facter?  Do I have to
>> standardise how I name network interfaces and associate IP addresses
>> to them to be able to deal with them all in a consistent, meaningful
>> way (eg to pick out the IP that's used for backup, or the different IP
>> addresses connected to the different edge switches)?

I would strongly suggest you use something else.  I did literally
standardise on using the resolved IP from DNS, and made it a failure
to compile when that failed to resolve.  Your network might not
support that, but I would suggest pretending the ipaddress fact just
doesn't exist at all.

Fixing the interface naming ... nah.  Don't contort your network to
support a stupid tool.  Fix the stupid tool.

(Incidentally, you should be able to replace the existing ipaddress
fact with a better, higher priority version that does respect your
needs, by putting a custom fact in place to override the shipped
version. :)

Daniel
-- 
⎋ Puppet Labs Developer – http://puppetlabs.com
✉ Daniel Pittman 
✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775
♲ Made with 100 percent post-consumer electrons

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Fwd: uploading files via REST?

[Razvan Cosma]

 Hello,
I am a bit confused by the REST syntax - how can I PUT an arbitrary file in
the bucket? Downloading works fine (Perl+LWP), see below, but for PUT I only
see this line in the docs (http://docs.puppetlabs.com/guides/rest_api.html):
PUT /{environment}/file_bucket_file/md5/{checksum}
Should I compute the MD5 of the file and port its contents at the url ?

my code:

my $ua = LWP::UserAgent->new();
my $ay = HTTP::Headers->new; $ay->header('Accept' => 'YAML');
my $as = HTTP::Headers->new; $as->header('Accept' => 's');
sub get_string {
my $req = HTTP::Request->new('GET',
"https://$server/production/file_metadata/".$_[0],
$ay);
my $res = $ua->request($req);
die "Something went wrong: ".$res->status_line unless $res->is_success;
my @ini = YAML::Load($res->content."\n");
my $md5 = $ini[0]->{checksum}; $md5 =~ s/^{md5}//;
$req = HTTP::Request->new('GET',
"https://$server/production/file_bucket_file/md5/$md5";,
$as);
$res = $ua->request($req);
die "Something went wrong: ".$res->status_line unless $res->is_success;
return $res->content;
}
sub get_yaml {
my $req = HTTP::Request->new('GET',
"https://$server/production/file_metadata/".$_[0],
$ay);
my $res = $ua->request($req);
die "Something went wrong: ".$res->status_line unless $res->is_success;
my @ini = YAML::Load($res->content."\n");
my $md5 = $ini[0]->{checksum}; $md5 =~ s/^{md5}//;
$req = HTTP::Request->new('GET',
"https://$server/production/file_bucket_file/md5/$md5";,
$ay);
$res = $ua->request($req);
die "Something went wrong: ".$res->status_line unless $res->is_success;
@ini = YAML::Load($res->content."\n");
return $ini[0];
}

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] ANNOUNCE: Facter 1.5.9 Final!

[Mark Phillips]

On 20 May 2011, at 19:48, Jacob Helwig wrote:

> Facter 1.5.9 is a maintenance release containing fixes and updates.
> 
> This release contains several fixes, and updated facts, as well as
> adding some new facts.  These include enhancements with Facter & EC2,
> additional memory facts for OS X, and better Ruby 1.9 support.
> 
> As always, please let us know if you run into any problems with any of
> the release candidates.

There's a CSW test release for Solaris at 
http://buildfarm.opencsw.org/experimental.html#markp

Once I've had a chance to check it over I'll release it.


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: puppet administration guidance

[Zico]

On Tue, May 31, 2011 at 8:00 PM, jcbollinger wrote:

>
>
>
>
> When you say "build a Puppet repo", I guess you're talking about
> writing manifests.  That is probably the most significant aspect of
> using Puppet, so you're cutting out a lot when you exclude it.
>
>
> > What sort of day to day issues to you guys run into, and what are they
> > command line tools that I should learn?
>
>
> For Puppet itself, you need to know the varied modes of the "puppet"
> command for controlling the agent, the certificate authority, etc.
>
>
>
[ ... ]

Just a fantastic email! Very nice!! Inspiring too! :) Thanks a
lot jcbollinger

-- 
Best,
Zico

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] High CPU usage puppet 2.6.6

[Marek Dohojda]

Hi

I recently upgrade my puppet from .25 to 2.6.6.  The actual upgrade process
was trivial, but now I am seeing issues.  Puppetmaster is running at very
high CPU usage.  Prior to the upgrade my load average was at around 2 ( this
server is doing more stuff than just puppet ), but now I am hitting 12!!!

Is there a known issue with this puppet version that I haven't seen?

Thank you!
Marek

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] finished, yet execution expired

[Nigel Kersten]

On Fri, May 27, 2011 at 8:39 PM, Larry Ludwig  wrote:

> In my case is also happening with 2.6.8.
>
> making
>
> async_storeconfigs=false
>
> Seemed to resolve the issue.
>

hrm. that's rather strange. Daniel, if you're still watching this thread, do
you have any comment on whether your fix for:

http://projects.puppetlabs.com/issues/5318

could possibly have resolved this issue?

For those of you who can somewhat reliably reproduce this, would it be
possible to test a master running against 2.6.x HEAD to see if it resolved
it?



>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>



-- 
Nigel Kersten
Product, Puppet Labs
@nigelkersten

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet Enterprise scalability

[Nigel Kersten]

On Mon, May 30, 2011 at 4:58 AM, Kenneth Holter wrote:

> Hi,
>
>
> we're interested in the Puppet Enterprise software bundle, but have
> some concerns about the scalability of this type of bundled setup. Are
> there any puppet enterprise customers on the mailinglist that may
> comment on their experience with the puppet enterprise with regards to
> scalability - does the bundled package scale well to a few hundred
> nodes out of the box, or would we need some tweaking to get this
> working?
>

You'll definitely scale to a couple of hundred nodes out of the box,
assuming you're running on an average server.

Note we also have a dedicated list for PE user questions that you should
have been sent when you first got started.

http://groups.google.com/a/puppetlabs.com/group/pe-users



>
>
> Best regards,
> Kenneth Holter
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>


-- 
Nigel Kersten
Product, Puppet Labs
@nigelkersten

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] know what the master is currently doing

[Carles Amigó]

Hi

Is there any way to see which catalog is currently compiling the puppet 
master?


The puppetmaster log only shows the catalog when it's been already 
compiled, not when it starts compiling it.


In our configuration, we have many puppet masters running after a nginx 
and it would be useful to know what is doing each master process.


Cheers

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] ralsh - unable to pass alias array for host resource

[Dan Bode]

On Tue, May 31, 2011 at 8:34 AM, PBWebGuy  wrote:

> I'm trying create an entry in the /etc/hosts file but when trying to
> use the 'alias' parameter I'm getting a munge error because it can't
> parse the array passed from the command-line.  I've tried all sorts of
> ways to define the array but nothing seems to work.  Does anyone know
> how to define the array on the command-line?
>
> Here is the command that I run and the output:
>
> #  ralsh host puppet.domain.local ip=10.11.12.13 ensure=present
> alias=puppet
>

alias was changed to host_aliases a while back b/c alias is a meta parameter

Could not run: Parameter alias failed: Munging failed for value
> "puppet" in class alias: Cannot add aliases without a catalog
>
> TIA,
>
> John
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] ralsh - unable to pass alias array for host resource

[PBWebGuy]

I'm trying create an entry in the /etc/hosts file but when trying to
use the 'alias' parameter I'm getting a munge error because it can't
parse the array passed from the command-line.  I've tried all sorts of
ways to define the array but nothing seems to work.  Does anyone know
how to define the array on the command-line?

Here is the command that I run and the output:

#  ralsh host puppet.domain.local ip=10.11.12.13 ensure=present
alias=puppet
Could not run: Parameter alias failed: Munging failed for value
"puppet" in class alias: Cannot add aliases without a catalog

TIA,

John

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] New Puppet report processors...

[James Turnbull]

Hi all

On my TODO list for about a year now has been a tutorial on how easy it
is to write Puppet report processors and how much more you can do with
them than just email/log/store Puppet report data.  Rather than write a
whole tutorial I decided to create a whole series of examples of report
processors that should:

a) Provide some immediate solutions that you can deploy right now, and

b) Provide good examples of things you can do with report processing
that you can take, fork and modify.

All of them are released under the Apache 2.0 license.

In that spirit I've created ten new report processors:

1. Reports failed runs to an IRC channel -
https://github.com/jamtur01/puppet-irc

2. Reports failed runs and logs to PagerDuty -
https://github.com/jamtur01/puppet-pagerduty

3. Reports failed runs to Jabber/XMPP -
https://github.com/jamtur01/puppet-xmpp

4. Reports failed runs to Twitter -
https://github.com/jamtur01/puppet-twitter

5. Reports failed runs and logs to Campfire -
https://github.com/jamtur01/puppet-campfire

6. Reports failed runs to Twilio -
https://github.com/jamtur01/puppet-twilio

7. Reports failed runs to Boxcar -
https://github.com/jamtur01/puppet-boxcar

8. Reports failed runs to HipChat -
https://github.com/jamtur01/puppet-hipchat

9. Sends metrics to a Ganglia server via gmetric -
https://github.com/jamtur01/puppet-ganglia

10. Reports failed runs to Growl - https://github.com/jamtur01/puppet-growl

Comments, feedback, testing and ideas for other integrations all welcomed.

Regards

James

-- 
James Turnbull
Puppet Labs
1-503-734-8571

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] puppet dashboard 404s

[Randall Hansen]

On Sat, May 28, 2011 at 5:36 AM, Tim Dunphy  wrote:

>  I noticed that it complained that it couldn't find this file
>  /usr/share/puppet-dashboard/public/stylesheets/all.css

This is actually one of the more straightforward aspects of Ruby on
Rails.  Everything in the "public" directory is served directly by the
webserver.  This error likely means that the server running Dashboard
can't find that directory.

>  I looked on the system and couldn't find it (tho I am not sure that
> is causing the problem)
>  this is one of the errors I see (I am looking for others).. a lot of
> info was output to the screen when I tried to load that page
>  here is more output that I saw to the screen.

This looks like log output from importing reports.  I haven't read
every line, but nothing jumps out as wrong.

> what logs should I be looking at for clues?

It depends on how you're running Dashboard.  Apache?  Passenger?
Using `script/server` locally?  How did you install Dashboard?  From
source, or a package?

With a little more information this should be an easy problem.

r

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: ipaddress returned by facter

[jcbollinger]

On May 30, 3:10 pm, Tim Coote  wrote:
> Hullo
> I'm running facter 1.5.8 (fedora 13). I'm not very clear about what
> the variable ipaddress is supposed to represent.


I suggest you read the discussion at
http://groups.google.com/group/puppet-users/browse_thread/thread/f278468018b13a32,
especially Daniel Pittman's response at the end.  As Daniel observes,
*Facter* is not very clear about what that fact represents.


> I've read that it
> returns the ip address that's bound to the lowest alphabetic name of a
> network interface. That model seems a bit weird to me but that's
> probably because I'm just used to tools that return the set of IP
> addresses associated with the host, as seen from the host.


No, I think it's because you intuitively understand what Daniel wrote,
that Facter's ipaddress fact is not well-defined, and it is not very
meaningful in the general case.  It's not very useful if you have to
worry about machines that have more than one non-loopback network
interface.  It might be even less useful than that.


> On one of my machines, ifconfig returns 5 device names which can have
> IP addresses associated with them (eth0, lo, virbr0, vmbridge, and
> vnet0), of these, eth0 is bridged to vmbridge (and has no IPv4 address
> of its own), lo I don't care about, virbr0 is the internal (ie not
> visible off the host) bridge created by some libvirt (I think) and I
> don't know where vnet0 comes from.
>
> Facter is returning the IP v4 address on virbr0, which is neither what
> the documentation says, nor much use as I can see that it's likely to
> be the same on all hosts that have libvirt installed. There are no
> IPv6 addresses returned.
>
> Am I seeing the expected behaviour for facter?  Do I have to
> standardise how I name network interfaces and associate IP addresses
> to them to be able to deal with them all in a consistent, meaningful
> way (eg to pick out the IP that's used for backup, or the different IP
> addresses connected to the different edge switches)?


I'm not sure whether you're seeing the expected behavior.  If ifconfig
lists an IP address for eth0, then probably not.  Otherwise, probably
so, though it must be understood that "expected" is not necessarilly
the same as "most desirable".

I recommend that you reserve twiddling interface names for a last
resort.  It really shouldn't come to that.  I also recommend, however,
that you stop using the 'ipaddress' fact.  In the words of Inigo
Montoya, "I don't think it means what you think it means."

Pittman offered an alternative in the discussion I linked above.  You
might also be able to use one of the per-interface ipaddress facts
(e.g. ipaddress_eth0) if that's sensible and if facter is picking it
up (check by running facter from the command line on the system in
question).  If neither of those fits the bill, then a custom fact is
pretty easy to write and distribute; that's the Swiss army knife of
Facter.


John

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] uploading files via REST?

[RCosma]

Hello,
I am a bit confused by the REST syntax - how can I PUT an arbitrary file in 
the bucket? Downloading works fine (Perl+LWP), see below, but for PUT I only 
see this line in the docs (http://docs.puppetlabs.com/guides/rest_api.html):
PUT /{environment}/file_bucket_file/md5/{checksum}
Should I compute the MD5 of the file and port its contents at the url ?

my code: 

my $ua = LWP::UserAgent->new();
my $ay = HTTP::Headers->new; $ay->header('Accept' => 'YAML');
my $as = HTTP::Headers->new; $as->header('Accept' => 's');
sub get_string {
my $req = HTTP::Request->new('GET', 
"https://$server/production/file_metadata/".$_[0], $ay);
my $res = $ua->request($req);
die "Something went wrong: ".$res->status_line unless $res->is_success;
my @ini = YAML::Load($res->content."\n");
my $md5 = $ini[0]->{checksum}; $md5 =~ s/^{md5}//;
$req = HTTP::Request->new('GET', 
"https://$server/production/file_bucket_file/md5/$md5";, $as);
$res = $ua->request($req);
die "Something went wrong: ".$res->status_line unless $res->is_success;
return $res->content;
}
sub get_yaml {
my $req = HTTP::Request->new('GET', 
"https://$server/production/file_metadata/".$_[0], $ay);
my $res = $ua->request($req);
die "Something went wrong: ".$res->status_line unless $res->is_success;
my @ini = YAML::Load($res->content."\n");
my $md5 = $ini[0]->{checksum}; $md5 =~ s/^{md5}//;
$req = HTTP::Request->new('GET', 
"https://$server/production/file_bucket_file/md5/$md5";, $ay);
$res = $ua->request($req);
die "Something went wrong: ".$res->status_line unless $res->is_success;
@ini = YAML::Load($res->content."\n");
return $ini[0];
}

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: puppet administration guidance

[jcbollinger]

On May 30, 3:36 pm, S Ahmed  wrote:
> Other than learning on to build a puppet repo, what other
> skills/tutorials/docs can you point me to do learn how to admin a puppet
> setup.


When you say "build a Puppet repo", I guess you're talking about
writing manifests.  That is probably the most significant aspect of
using Puppet, so you're cutting out a lot when you exclude it.


> What sort of day to day issues to you guys run into, and what are they
> command line tools that I should learn?


For Puppet itself, you need to know the varied modes of the "puppet"
command for controlling the agent, the certificate authority, etc.


> /var/log/syslog seems to be the place to look for any issues for things like
> agent's not being able to connect or problems with the catalog.
>
> I know this is a open ended question, but I want to be prepared :)


Puppet automates a variety of system administration tasks, but it does
not replace a system administrator -- rather it empowers one.  You
will not administer Puppet well if you are not a capable system
administrator apart from Puppet.

To really be effective, it helps to understand how to adminster your
systems without relying on GUI admin tools.  From your question, I
guess you recognize that.  The real sysadmin's toolset includes at
least these programs (in no particular order):

Basic filesystem commands:
mkdir, rmdir, ln (-s), rm

Advanced filesystem commands:
mount, umount, chown, chmod

Package management:
yum / apt / etc. as appropriate

Service management:
(varies, but for example:) chkconfig, service

Scheduling:
cron

Scripting:
sh / bash

User and Group management:
(varies, but for example:) useradd, usermod, userdel, groupadd,
groupmod, groupdel, chsh

Basic security management:
passwd

There others, too, some fundamental, but all less relevant to Puppet.
But even being expert with all of those doesn't make you much of a
sysadmin.  Other than system privilege, what makes a sysadmin is not
so much his tools, but rather his understanding of how the system
works.  What do various services do?  Which files configure system
operations and policy, and how?  If the network is down, how do you
bring it up?  Where are the user home directories? Where are the
system logs?  Where are the various shell startup scripts?  And so on.

I'm not sure where you're coming from skill-wise, but don't be
discouraged if all that sounds like a lot.   Nobody is born knowing
that stuff, and few sysadmins are across-the-board experts in all of
the above.  Everyone improves with experience.  If you're not
confident in your general sysadmin abilities, however, then do be wary
of taking a position where you don't have a superior or peers who can
help you in that area.  For help with Puppet, though, you have
us :-) .


John

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Removing links

[jcbollinger]

On May 31, 4:58 am, John Kennedy  wrote:
> I have a group of web servers being load balanced. I have 4 types of servers
> all build from the same image.
> When I build the image I forgot to clear out one of the sym links from
> sites-enabled to sites-available. This is causing problems with the web
> servers. I have tried to have puppet remove the link but have had little
> success. I have tried the following:
> file { "/opt/nginx/sites-enabled/ absent }
> This will remove a file if it is there but not this link.
> What am I missing? I have googled to get the above which I thought would
> remove the link.


ensure => absent is what I would expect to work, too.  Does that
parameter actually end up in the catalog for the node(s) you are
testing?  If so, then what message, if any, does the Puppet agent log
about it?

Crazy idea: does the link target exist?  If not, then what happens if
you create it first?  It would be a bug if Puppet won't remove broken
links, but I can imagine a couple of ways that such a bug could creep
in.


John

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Not able to execute shell script

[Felix Frank]

If that is the whole content of you "shell script" it's missing the
shebang line.

"""
#!/bin/sh

chmod 777 /root/testfile
"""

You're still missing a PATH variable, so this script is still a mess.

You should write a proper test script.

HTH,
Felix

On 05/20/2011 10:36 AM, Sumith Sudhakaran wrote:
> Thanks for your reply
> 
> No, I just create a shell for testing  with following content.
> 
> chmod 777 /root/testfile
> 
> Nothing else.
> 
> 
> On Fri, May 20, 2011 at 1:00 PM, Denmat  > wrote:
> 
> Hi,
> 
> What is the exit code of the script when you run manually? Does it
> exit with 1?
> 
> Cheers,
> Den
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Removing links

[John Kennedy]

I have a group of web servers being load balanced. I have 4 types of servers
all build from the same image.
When I build the image I forgot to clear out one of the sym links from
sites-enabled to sites-available. This is causing problems with the web
servers. I have tried to have puppet remove the link but have had little
success. I have tried the following:
file { "/opt/nginx/sites-enabled/ absent }
This will remove a file if it is there but not this link.
What am I missing? I have googled to get the above which I thought would
remove the link.
Thanks,
John

-- 
 John Kennedy

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.