[Puppet Users] Scheduled maintenance - projects.puppetlabs.com and forge.puppetlabs.com

[James Turnbull]

Hi all

The sites:

http://projects.puppetlabs.com (Redmine)
http://forge.puppetlabs.com

Will be down for maintenance for 30 minutes on Friday (today) the 28th
at 11.00 PM PDT.

Thanks

James Turnbull

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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 Package Management - how far do you go?

[Matt Juszczak]

Well, these servers are cloud servers, so nightly snapshots are taken. And it 
really is a one off box. 

If I need to duplicate it, I just spin up another image anyway. 

-Original Message-
From: "Carl.caum" 
Date: Fri, 28 May 2010 23:05:30 
To: puppet-users@googlegroups.com
Subject: Re: [Puppet Users] Puppet Package Management - how far do you go?

Personally I like to increase my chances of getting to the bar early.  
If you know you're going to want to build the box again, automate it.  
If you need to ensure the box looks a certain way, automate it. If it  
takes the same amount of time to automate it as it does to not  
automate it, automate it. If it takes a little extra time to automate  
it but maybe someday somewhere you might want to do it again, automate  
it. So really, only don't bother if automating means without a doubt  
it will cost you time, now or in the future, for one extra beer.

On May 28, 2010, at 10:19 PM, Matt Juszczak  wrote:

> I have a "basenode" class which installs most of the packages needed  
> on a specific server.  For the database servers, we ensure mysql is  
> installed, setup the directory structure, etc.
>
> But what about "one off" servers?  For instance, I have a tools  
> server, that sort of runs random one-off tools in production.   
> Today, I had to install a bunch of python libraries on it to make  
> something in my home directory work that I was trying to get working.
>
> Would you guys have installed those packages manually, knowing that  
> you won't ever really have to launch another server exactly like it,  
> or would you have added those packages to puppet so that they would  
> be installed should the box ever need to be re-configured from  
> scratch?  How far would you go to keep puppet and your system 100%  
> in sync?
>
> -- 
> You received this message because you are subscribed to the Google  
> Groups "Puppet Users" group.
> To post to this group, send email to puppet-us...@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-us...@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-us...@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 Package Management - how far do you go?

[Carl.caum]

Personally I like to increase my chances of getting to the bar early.  
If you know you're going to want to build the box again, automate it.  
If you need to ensure the box looks a certain way, automate it. If it  
takes the same amount of time to automate it as it does to not  
automate it, automate it. If it takes a little extra time to automate  
it but maybe someday somewhere you might want to do it again, automate  
it. So really, only don't bother if automating means without a doubt  
it will cost you time, now or in the future, for one extra beer.


On May 28, 2010, at 10:19 PM, Matt Juszczak  wrote:

I have a "basenode" class which installs most of the packages needed  
on a specific server.  For the database servers, we ensure mysql is  
installed, setup the directory structure, etc.


But what about "one off" servers?  For instance, I have a tools  
server, that sort of runs random one-off tools in production.   
Today, I had to install a bunch of python libraries on it to make  
something in my home directory work that I was trying to get working.


Would you guys have installed those packages manually, knowing that  
you won't ever really have to launch another server exactly like it,  
or would you have added those packages to puppet so that they would  
be installed should the box ever need to be re-configured from  
scratch?  How far would you go to keep puppet and your system 100%  
in sync?


--
You received this message because you are subscribed to the Google  
Groups "Puppet Users" group.

To post to this group, send email to puppet-us...@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-us...@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] accessing client certname in manifests?

[Nigel Kersten]

On Fri, May 28, 2010 at 8:53 PM, James Turnbull wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Nigel Kersten wrote:
> >
> >> Anyone see any problems with doing it like this?
> >
> >> require 'puppet'
> >
> >> Facter.add("certname") do
> >>   setcode do
> > Puppet[:config] = "/etc/puppet/puppet.conf"
> > Puppet.parse_config
> > Puppet[:certname]
> >>   end
> >> end
> >
>
> Nope...
>
> Ours is:
>
> Facter.add("certname") do
>  path = '/usr/bin/puppet'
>  setcode do
>%x{#{path} --configprint certname}.chomp if File.exists?(path)
>  end
> end
>
> Which is kind of ugly in parts and I've been meaning to rewrite it... :)
>

Heh. That's kind of what we were doing, but it hit me it was a little silly
given we're running inside Puppet already.


>
> James
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.7 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEVAwUBTACPtSFa/lDkFHAyAQKsqAf8DNBlnJU1F8YXXqPYqMhZ81mMAko4w1zs
> htu4ATkZYGoLmFlaLd16mX34gHkpfjzaKViexwgDuZMtPhuU4QeN5P+jJ+OfzZHD
> lYTDocv0B+DGgr9wchBfudYDKmdBeIbTb9TvdwArYNycPHLyVX2ow9SXVKh04WZL
> NNhNVza41W60w2ZKFv0NV3b0IhO+nnt652BvtDz1ztXi06b+jnY2kxCmwjrtuMGj
> 6Ao6d8j7bNj+B/RZQujbrjhObD/DxK0zqc8JloO02ym+ZqD1r+g4qHzr2sk5KcZD
> XlLE7bhzHVgxFrOWtXNMUJ+u7gOoFnZJ5Pp2Go7DGGDFWXdvRUt5bw==
> =08y1
> -END PGP SIGNATURE-
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@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

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] accessing client certname in manifests?

[James Turnbull]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Nigel Kersten wrote:
> 
>> Anyone see any problems with doing it like this?
> 
>> require 'puppet'
> 
>> Facter.add("certname") do
>>   setcode do
> Puppet[:config] = "/etc/puppet/puppet.conf"
> Puppet.parse_config
> Puppet[:certname]
>>   end
>> end
> 

Nope...

Ours is:

Facter.add("certname") do
  path = '/usr/bin/puppet'
  setcode do
%x{#{path} --configprint certname}.chomp if File.exists?(path)
  end
end

Which is kind of ugly in parts and I've been meaning to rewrite it... :)

James
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBTACPtSFa/lDkFHAyAQKsqAf8DNBlnJU1F8YXXqPYqMhZ81mMAko4w1zs
htu4ATkZYGoLmFlaLd16mX34gHkpfjzaKViexwgDuZMtPhuU4QeN5P+jJ+OfzZHD
lYTDocv0B+DGgr9wchBfudYDKmdBeIbTb9TvdwArYNycPHLyVX2ow9SXVKh04WZL
NNhNVza41W60w2ZKFv0NV3b0IhO+nnt652BvtDz1ztXi06b+jnY2kxCmwjrtuMGj
6Ao6d8j7bNj+B/RZQujbrjhObD/DxK0zqc8JloO02ym+ZqD1r+g4qHzr2sk5KcZD
XlLE7bhzHVgxFrOWtXNMUJ+u7gOoFnZJ5Pp2Go7DGGDFWXdvRUt5bw==
=08y1
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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 Package Management - how far do you go?

[Ohad Levy]

from my experience, if you have the time to automate it - go ahead, most
likely if you wont, it will come to bite you in the a*s later on :)

Ohad

On Sat, May 29, 2010 at 11:19 AM, Matt Juszczak  wrote:

> I have a "basenode" class which installs most of the packages needed on a
> specific server.  For the database servers, we ensure mysql is installed,
> setup the directory structure, etc.
>
> But what about "one off" servers?  For instance, I have a tools server,
> that sort of runs random one-off tools in production.  Today, I had to
> install a bunch of python libraries on it to make something in my home
> directory work that I was trying to get working.
>
> Would you guys have installed those packages manually, knowing that you
> won't ever really have to launch another server exactly like it, or would
> you have added those packages to puppet so that they would be installed
> should the box ever need to be re-configured from scratch?  How far would
> you go to keep puppet and your system 100% in sync?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@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-us...@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 Package Management - how far do you go?

[Matt Juszczak]

I have a "basenode" class which installs most of the packages needed on a 
specific server.  For the database servers, we ensure mysql is installed, 
setup the directory structure, etc.


But what about "one off" servers?  For instance, I have a tools server, 
that sort of runs random one-off tools in production.  Today, I had to 
install a bunch of python libraries on it to make something in my home 
directory work that I was trying to get working.


Would you guys have installed those packages manually, knowing that you 
won't ever really have to launch another server exactly like it, or would 
you have added those packages to puppet so that they would be installed 
should the box ever need to be re-configured from scratch?  How far would 
you go to keep puppet and your system 100% in sync?


--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-us...@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] accessing client certname in manifests?

[Nigel Kersten]

On Fri, May 28, 2010 at 4:19 PM, James Turnbull wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Nigel Kersten wrote:
> > I mentioned we had a custom fact for the client certname in IRC the
> > other day and someone poked fun at me as it's apparently built in.
> >
> > For the life of me I can't work out what variable it is. Anyone know?
> >
> > (our certnames bear no relationship to any other attribute, fqdn etc)
>
> It is not built-in - someone has misled you young man.
>

Anyone see any problems with doing it like this?

require 'puppet'

Facter.add("certname") do
  setcode do
Puppet[:config] = "/etc/puppet/puppet.conf"
Puppet.parse_config
Puppet[:certname]
  end
end





>
> Regards
>
> James Turnbull
>
> - --
> Author of:
> * Pro Linux Systems Administration
> (http://www.amazon.com/gp/product/1430219122/)
> * Pulling Strings with Puppet
> (http://www.amazon.com/gp/product/1590599780/)
> * Pro Nagios 2.0
> (http://www.amazon.com/gp/product/1590596099/)
> * Hardening Linux
> (http://www.amazon.com/gp/product/159059/)
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.7 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEVAwUBTABPZiFa/lDkFHAyAQLkywgAl1tn3QraNmZLn3Tsdt1Ymt7gOuVoISzX
> bz1BxW+QDWGVZZFw0hYZ8ob1kgiCgdkrZkLtjIzQbzJNR2yNY0PURqUvpGNpfoVi
> wB2O2JmtNu3v1mFovvHrSTtcruQ53VBpOaL2wdKcoPX+IF/sZbeQic1RTLS2S0YZ
> fa/iRRABidN7g5BSIiK5xPmRBbTuG25BngWs242p/vFeIbHOn57ix3dBVKZpZHnO
> DT0mt8uCYz2pEEVHVVDXwf4GL43jbATGRCgWuXKt0WATvwg06a8/njDmXTV45OEC
> 6FL2/yETt6sUk9snXyKyTWtTzKN++gXNadtPs+/LaJPwVHh0AHyzhQ==
> =M0AA
> -END PGP SIGNATURE-
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@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

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.

Logging bugs (was Re: [Puppet Users] Toplevel domain and facter)

[James Turnbull]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Klaus Ethgen wrote:
> 
> Behind the line it was more problematic to get to the informations about
> the bug tracker and the knowledge to apply to this mailing list with a
> non-google address than it is needed and more than it is common with
> other software projects. And that was, beside the bug, the main subject
> of that thread. And If I look back, I can find that I am not the only
> one who is a bit upset about the login need to fill a bug.

I don't believe this is the case personally - a lot of projects use
Google Groups - they aren't perfect but they are pretty effective.
Instructions for joining without an account are available, for example
the link I provided to you.

http://onlygizmos.com/how-to-join-google-groups-without-a-google-id/2009/05/

We've looked at a number of other solutions without finding one that met
all our requirements - Google Groups is the best fit thus far.

> If you want the contribution of other people, just hold the hurdle low.
> For the projects I am involved in I am very happy to get bug reports by
> mail and if I want to track them in a bug tracker, well, I have no
> problem to fill it in myself.

I'd love it if this was easy - but it isn't.  The volume of our bug
reports - and for most other projects - is way too high to manually
track incoming bug reports, patches, updates to tickets. It's simply not
operationally or practically feasible to do this.

Additionally, when we ran Trac we were BURIED in spam until we turned on
authentication for most things.  Redmine is not as bad but we're
starting to get more and more spam.  It can take hours to clean-up after
a major spam attack - some may remember the Trac spam attack that took
me two days to fix - almost every file had been changed.

I think our bar to entry is quite low - you can also use OpenID for
example on Redmine - but any bug tracking system that is unauthenticated
is an open invitation to spammers to mess up your environment.

Regards

James Turnbull

- -- 
Author of:
* Pro Linux Systems Administration
(http://www.amazon.com/gp/product/1430219122/)
* Pulling Strings with Puppet
(http://www.amazon.com/gp/product/1590599780/)
* Pro Nagios 2.0
(http://www.amazon.com/gp/product/1590596099/)
* Hardening Linux
(http://www.amazon.com/gp/product/159059/)

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBTABR2CFa/lDkFHAyAQJokAgAqgu5vY89kQD13RXbCjUlztaSKMwDBZdU
VY2xhFj3hmNDpdE1XMHoFGmmj73dE9gjWoEelpOC2ujdUqmPPjQ1ubqz6QHb0ZwD
YylM3D2lgKAiJlKC8kXxMnC+l8fS/hLZi1G0ah429YhFmwku/h8wpPNR4fRDe+xc
JB/K/7InoA/mj3yeKCX1qIH4imjmgmbedHJg43VE4ikB8MnrK73HkRCoX4U7SaAE
V5y1jDBZEHThNjCP+UCiPtVLKGmkpksO7ODrQrMD+pWh1iEp8TYsLbVLeEDLgICf
nwJr7B1GM+rAhSi/Ln3xJ9bBnOnpuL2kKRTVOHhozOp6Su32vpzfzw==
=8mG1
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] accessing client certname in manifests?

[James Turnbull]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Nigel Kersten wrote:
> I mentioned we had a custom fact for the client certname in IRC the
> other day and someone poked fun at me as it's apparently built in.
> 
> For the life of me I can't work out what variable it is. Anyone know?
> 
> (our certnames bear no relationship to any other attribute, fqdn etc)

It is not built-in - someone has misled you young man.

Regards

James Turnbull

- -- 
Author of:
* Pro Linux Systems Administration
(http://www.amazon.com/gp/product/1430219122/)
* Pulling Strings with Puppet
(http://www.amazon.com/gp/product/1590599780/)
* Pro Nagios 2.0
(http://www.amazon.com/gp/product/1590596099/)
* Hardening Linux
(http://www.amazon.com/gp/product/159059/)

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBTABPZiFa/lDkFHAyAQLkywgAl1tn3QraNmZLn3Tsdt1Ymt7gOuVoISzX
bz1BxW+QDWGVZZFw0hYZ8ob1kgiCgdkrZkLtjIzQbzJNR2yNY0PURqUvpGNpfoVi
wB2O2JmtNu3v1mFovvHrSTtcruQ53VBpOaL2wdKcoPX+IF/sZbeQic1RTLS2S0YZ
fa/iRRABidN7g5BSIiK5xPmRBbTuG25BngWs242p/vFeIbHOn57ix3dBVKZpZHnO
DT0mt8uCYz2pEEVHVVDXwf4GL43jbATGRCgWuXKt0WATvwg06a8/njDmXTV45OEC
6FL2/yETt6sUk9snXyKyTWtTzKN++gXNadtPs+/LaJPwVHh0AHyzhQ==
=M0AA
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Question about templates from variables

[Darren Chamberlain]

* James Cammarata  [2010/05/28 10:09]:
> My primary motivation for this is something like sudoers, where
> certain system roles require sudoers commands for different groups
> to use.

But sudoers has native support for exactly this use case, in that
you can assign permissions based on host as well as user.  So you
could do something like:

  Host_Alias DB_SERVERS = orasrv1, orasrv2, orasrv3
  User_Alias DBA = jsmith, tjones, brogers
  Runas_Alias ORACLE_USER = orauser
  Cmnd_Alias ORACLE_COMMANDS = ...

  DBA DB_SERVERS = (ORACLE_USER) ORACLE_COMMANDS

You could distribute this sudoers to every host and sudo will do the
right thing.

Of course, this doesn't invalidate what you're doing, I'm just
pointing out an alternate implementation.

-- 
The Net views censorship as a network failure, and routes around it.
-- John Gilmore

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Toplevel domain and facter

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

Am Fr den 28. Mai 2010 um 17:04 schrieb Joe McDonagh:
> Regardless of your intentions, etc, this is somewhat insulting IMO to an  
> open-source/foss project.

That is not my intention and I think I made that clear.

> It's almost like saying "Well I appreciate the  thousands of lines of
> code you've given me for free, and the man-hours  it took to write
> that code, and the man-hours you've saved me, but I'm  not willing to
> give you five minutes to create a log in to your bug  tracker."

Well, I do not think that way. It is not the time that is needed to fill
such a login. Its the fact _that_ there is a independent login for one
another software project.

If you just use one tool and are not interested in the rest of the
world, that might be ok. But I am willing to contribute to several
projects if I find errors or, better, if I have something to contribute
the code. So if every project ask to create a login this is a pain in
the a... Not to mention the information which is needed to fill such a
login application, which is not you want to spray all over the world. (I
know, public viewing and public exhibition is common in the facebook and
twitter generation but I think that is the wrong way.)

> Just sayin'. If you really can't be bothered feel free to hop  on IRC,
> I will file the bug for you.

Oh, I wonder if IRC is that much more non-anonymous than e-mail!? (That
does not mean that we can not talk about the bug on IRC if needed. Just
tell me the server and the channel.)

However:

Am Do den 27. Mai 2010 um 13:24 schrieb Paul Nasrat:
> Note this is probably a dupe of
> 
> http://projects.puppetlabs.com/issues/3356

the problem is still known so there is no need to fill another bug.

Behind the line it was more problematic to get to the informations about
the bug tracker and the knowledge to apply to this mailing list with a
non-google address than it is needed and more than it is common with
other software projects. And that was, beside the bug, the main subject
of that thread. And If I look back, I can find that I am not the only
one who is a bit upset about the login need to fill a bug.

If you want the contribution of other people, just hold the hurdle low.
For the projects I am involved in I am very happy to get bug reports by
mail and if I want to track them in a bug tracker, well, I have no
problem to fill it in myself.

Regards
   Klaus
- -- 
Klaus Ethgenhttp://www.ethgen.de/
pub  2048R/D1A4EDE5 2000-02-26 Klaus Ethgen 
Fingerprint: D7 67 71 C4 99 A6 D4 FE  EA 40 30 57 3C 88 26 2B
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQEVAwUBTAAmw5+OKpjRpO3lAQr8Sgf+IenjXS5fMPT4PATaqWGn6F/nxqdVvCuA
OnV4Zr0CWaoa967xnE2rn9qF46qQTwX88iWhGdSUKHF7jwmzboCxQsv2aaPyA4Yg
avaSe+F5n4uLiCBNFQwNtk/ZbhzBw1N2c4dRNSihS35q8PFkkO3m7dCtvxpFch+s
vIAJGhUU0dSutAlrKeA+tOGa1NtzOp3wpZo617ZqATWwkJsq5CKbgombXnC81Yc8
l/o6djwM59KJVVIFC/dzVaskWYKBH85v3i78qLapdWvhyTPTk+5WBDCbJizoKPqg
iB94Az3WbMmCddifkXFMMTd0GC1A1Mcov/xXUKwRp1G8h3y/oqi6Mw==
=86bS
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] storing facter facts in Dashboard.....

[CraftyTech]

Hello All,

 Is there a way that I can store the facter facts in Dashboard ? I
noticed that there are some yaml files in /var/lib/puppet/yaml/facts/;
are these it?  Can I get these to display on Dashboard?  I looked
around the docs and didn't find any information on the topic.

Thanks,

Henry

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] accessing client certname in manifests?

[Carl Caum]

I can't find it.  I just use $fqdn mostly with the exception of a few DHCP 
boxes.

On May 28, 2010, at 2:02 PM, Nigel Kersten wrote:

> 
> 
> On Fri, May 28, 2010 at 12:00 PM, Dan Bode  wrote:
> 
> 
> On Fri, May 28, 2010 at 11:52 AM, Nigel Kersten  wrote:
> I mentioned we had a custom fact for the client certname in IRC the other day 
> and someone poked fun at me as it's apparently built in.
> 
> if that's the case, then the following ticket needs to be closed.
> 
> http://projects.puppetlabs.com/issues/3021
> 
> Yeah, I don't think it is built in, and people just access fqdn or some other 
> equivalent that happens to have the same value as the certname.
> 
> I'd love it if someone proves me wrong though.
>  
> 
>  
> For the life of me I can't work out what variable it is. Anyone know?
> 
> (our certnames bear no relationship to any other attribute, fqdn etc)
> 
> 
> 
> -- 
> nigel
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@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-us...@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
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@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-us...@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] accessing client certname in manifests?

[Nigel Kersten]

On Fri, May 28, 2010 at 12:00 PM, Dan Bode  wrote:

>
>
> On Fri, May 28, 2010 at 11:52 AM, Nigel Kersten  wrote:
>
>> I mentioned we had a custom fact for the client certname in IRC the other
>> day and someone poked fun at me as it's apparently built in.
>
>
> if that's the case, then the following ticket needs to be closed.
>
> http://projects.puppetlabs.com/issues/3021
>

Yeah, I don't think it is built in, and people just access fqdn or some
other equivalent that happens to have the same value as the certname.

I'd love it if someone proves me wrong though.


>
>
>
>> For the life of me I can't work out what variable it is. Anyone know?
>>
>> (our certnames bear no relationship to any other attribute, fqdn etc)
>>
>>
>>
>> --
>> nigel
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To post to this group, send email to puppet-us...@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-us...@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

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] accessing client certname in manifests?

[Dan Bode]

On Fri, May 28, 2010 at 11:52 AM, Nigel Kersten  wrote:

> I mentioned we had a custom fact for the client certname in IRC the other
> day and someone poked fun at me as it's apparently built in.


if that's the case, then the following ticket needs to be closed.

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


> For the life of me I can't work out what variable it is. Anyone know?
>
> (our certnames bear no relationship to any other attribute, fqdn etc)
>
>
>
> --
> nigel
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@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-us...@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] accessing client certname in manifests?

[Nigel Kersten]

I mentioned we had a custom fact for the client certname in IRC the other
day and someone poked fun at me as it's apparently built in.

For the life of me I can't work out what variable it is. Anyone know?

(our certnames bear no relationship to any other attribute, fqdn etc)



-- 
nigel

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Question about templates from variables

[James Cammarata]

On Sat, 29 May 2010 02:30:03 +1000, Daniel Pittman 
wrote:
> James Cammarata  writes:
> 
>>> This seems like it's a bug with plusassignment to me, can you open a
>>> ticket on this?
>>
>> I had a moment of inspiration this morning and figured out what I needed
>> to
>> do to get this working the way I wanted:
> 
> [...]
> 
>> My primary motivation for this is something like sudoers, where certain
>> system roles require sudoers commands for different groups to use.
> 
> FWIW, my short term solution to that problem is to use a concatenated
file
> module, which allows me to incorporate arbitrary ordered fragments into
the
> output file.
> 
> Those can be nicely generated from a puppet define, wrapping up the
process
> in a way that is reasonably error-checked and in which the nasty
> implementation details are hidden from the "end users" in my sysadmin
team.

That sounds like just what I need, any documentation on the web for that,
or anything you can share?

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] combining arrays in site.pp

[Kenton Brede]

On Fri, May 28, 2010 at 11:15 AM, Michael DeHaan  wrote:
> On Fri, May 28, 2010 at 11:57 AM, Kenton Brede  wrote:
>> I'm running 0.25.4.  What I'd like to do is place an array of users
>> under the default node.  These users rarely change.  Then within each
>> subsequent node, have another array of users added to the original
>> array.  These users change more frequently.  These users are then be
>> snarfed into a template.  The setup I've been using is adding all the
>> users to one array in each node definition.
>>
>> I've read that using "+=" will add arrays to one another, but I keep
>> getting a "Could not parse for environment testing: Syntax error at
>> '='; expected '}' at /etc/puppet/manifests/testing/site.pp:54" error.
>> Is "+=" just not allowed in site.pp?
>>
>> This is an example of what I have.
>>
>> site.pp
>> -
>> node basenode {
>>    $users_group = ['user0', 'user1']
>> }
>>
>> node server1 inherits basenode {
>>    $users_group += ['user2', 'user3', 'user4']
>> }
>
> Puppet uses "+>" for appending to arrays.
>
> Here's the feature where it was added:
> http://projects.puppetlabs.com/issues/1584

Doh!  Looks like me just being an idiot.  I won't even tell you.
:)  Anyway "+=" is working just fine in my site.pp now.
Thanks,
Kent

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Question about templates from variables

[Michael DeHaan]

On Fri, May 28, 2010 at 12:40 PM, Michael DeHaan  wrote:
>> $template_list = ["template1","template2","template3"]
>> content => template($template_list),
>
> Puppet has a split() function that splits a string into an array, that
> should do what you want there.
>
> template(split($template_list))
>
> --Michael
>

Sorry, I posted too quickly, you can also specify the delimiter:

http://docs.puppetlabs.com/references/latest/function.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Question about templates from variables

[Michael DeHaan]

> $template_list = ["template1","template2","template3"]
> content => template($template_list),

Puppet has a split() function that splits a string into an array, that
should do what you want there.

template(split($template_list))

--Michael

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Question about templates from variables

[Daniel Pittman]

James Cammarata  writes:

>> This seems like it's a bug with plusassignment to me, can you open a
>> ticket on this?
>
> I had a moment of inspiration this morning and figured out what I needed to
> do to get this working the way I wanted:

[...]

> My primary motivation for this is something like sudoers, where certain
> system roles require sudoers commands for different groups to use.

FWIW, my short term solution to that problem is to use a concatenated file
module, which allows me to incorporate arbitrary ordered fragments into the
output file.

Those can be nicely generated from a puppet define, wrapping up the process
in a way that is reasonably error-checked and in which the nasty
implementation details are hidden from the "end users" in my sysadmin team.

Daniel

-- 
✣ Daniel Pittman✉ dan...@rimspace.net☎ +61 401 155 707
   ♽ 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-us...@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 error.

[David Schmitt]

Everything you can pass on the commandline, you can also put into the 
puppet.conf, probably constrained to the [puppetmaster(d?)] section.


Best Regards, David

On 27.05.2010 13:47, Marley Bacelar wrote:

Gabriel,

I my CentOS, enabled in /etc/sysconfig in /etc/sysconfig/puppetmaster:

PUPPETMASTER_EXTRA_OPTS="--reports puppet_dashboard --reports store"

--
Marley Bacelar
Project Fedora Ambassador
VCP, VSP. VTSP., ITILF, IBM 000-076, IBM 000-330, IBM 000-331
marleybace...@gmail.com 

2010/5/27 Gabriel - IP Guys mailto:gabr...@impactteachers.com>>

Where did you enable this reports switch? I’m having similar problems J

*From:* puppet-users@googlegroups.com

[mailto:puppet-users@googlegroups.com
] *On Behalf Of *Marley Bacelar
*Sent:* 25 May 2010 01:26
*To:* puppet-users@googlegroups.com

*Subject:* Re: [Puppet Users] Puppet Dashboard error.

Yeahh!

Dan,

Thank you very much, after set in puppetmaster reports=store,
everything worked!


2010/5/24 Dan Bode mailto:d...@puppetlabs.com>>

On Sat, May 22, 2010 at 9:50 PM, Marley Bacelar
mailto:marleybace...@gmail.com>> wrote:

Hi i have the running i both sides, client and server sides the
puppet 0.25.4

Get this error on server side:

puppetmasterd[5363]: Report puppet_dashboard failed: wrong
Content-Length format


this sounds like http://projects.puppetlabs.com/issues/3428 , feel
free to log you experience in the ticket.

And receive this error on my client side:

warning: Value of 'preferred_serialization_format' (pson) is
invalid for report, user default (b64_zlib_yaml)


this usually indicates that the reports are being sent correctly.
this has been moved to debug in later versions.


I am getting any reports on my /var/lib/puppet/reports.


you would only get reports in reports/ if you have the store reports
handler enabled on the server

reports=store

the puppet dashboard handler does not create store reports.


--
Marley Bacelar
Project Fedora Ambassador
VCP, VSP. VTSP., ITILF, IBM 000-076, IBM 000-330, IBM 000-331
marleybace...@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.

--
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.






--
You received this message because you are subscribed to the Google
Groups "Puppet Users" group.
To post to this group, send email to puppet-us...@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-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, 

Re: [Puppet Users] Build nginx conf dynamically (depending on the upstream machines)

[David Schmitt]

On 27.05.2010 05:10, Daniel Pittman wrote:

Gonçalo Queirós  writes:


That module helped me implement one of the proposed solutions. I though
there might be something "prettier" to handle this kind of situations,
but seems not.


Nope.  That is the "best practice" mechanism for doing this.  Sorry.


Not quite. Best practice would be to implement a native type which 
parses out the config file, but that involves ruby.



Best Regards, David

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-us...@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] External Nodes Require a Forklift?

[Joe McDonagh]

What's the state of storedconfigs these days?

Doug.

   
In what sense? I am using it right now for other pieces of 
infrastructure, works pretty nicely but I am not exactly large scale. 
What did you want to accomplish with it?


--
--
Joe McDonagh
Operations Engineer
AIM: YoosingYoonickz
IRC: joe-mac on freenode
"When the going gets weird, the weird turn pro."

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-us...@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] combining arrays in site.pp

[Michael DeHaan]

On Fri, May 28, 2010 at 11:57 AM, Kenton Brede  wrote:
> I'm running 0.25.4.  What I'd like to do is place an array of users
> under the default node.  These users rarely change.  Then within each
> subsequent node, have another array of users added to the original
> array.  These users change more frequently.  These users are then be
> snarfed into a template.  The setup I've been using is adding all the
> users to one array in each node definition.
>
> I've read that using "+=" will add arrays to one another, but I keep
> getting a "Could not parse for environment testing: Syntax error at
> '='; expected '}' at /etc/puppet/manifests/testing/site.pp:54" error.
> Is "+=" just not allowed in site.pp?
>
> This is an example of what I have.
>
> site.pp
> -
> node basenode {
>    $users_group = ['user0', 'user1']
> }
>
> node server1 inherits basenode {
>    $users_group += ['user2', 'user3', 'user4']
> }

Puppet uses "+>" for appending to arrays.

Here's the feature where it was added:
http://projects.puppetlabs.com/issues/1584

--Michael

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Toplevel domain and facter

[Joe McDonagh]

Rather than continue with this sort of semi-argument, I've gone and 
created an issue in redmine, #3909.


--
--
Joe McDonagh
Operations Engineer
AIM: YoosingYoonickz
IRC: joe-mac on freenode
"When the going gets weird, the weird turn pro."

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-us...@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] Nagios checks

[Joe McDonagh]

On 05/27/2010 02:37 PM, Peter Berghold wrote:


Has anybody out there written a custom check for Nagios to determine 
if puppetd and/or puppetmasterd is running? I am considering writing 
one if not.


--
You received this message because you are subscribed to the Google 
Groups "Puppet Users" group.

To post to this group, send email to puppet-us...@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.
I use the one that came with the source download, however it requires a 
rubygem that IMO it probably shouldn't use.


--
--
Joe McDonagh
Operations Engineer
AIM: YoosingYoonickz
IRC: joe-mac on freenode
"When the going gets weird, the weird turn pro."

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-us...@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] Toplevel domain and facter

[Joe McDonagh]

On 05/27/2010 02:51 PM, Klaus Ethgen wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am Do den 27. Mai 2010 um 17:57 schrieb Nigel Kersten:
   

You'll need to be logged in.
 

Ah. Bad. I have no account there and I dislike the idea to create a
account anywhere to just report a bug. I have that many accounts sprayed
around the net that I do not want to manage one more, sorry.
   

That's kind of a crappy approach don't you think?
 

Do you really think so?

   

Have you ever dealt with a bug reporter that accepts anonymous bug reports?
 

Do you know debian? Do you know /usr/bin/reportbug? Do you know RT?
There are many bug tracker out there where reporting by e-mail is the
usual way.

   

It's almost impossible to treat such reports seriously as you're often not
quite sure whether you've fixed the issue or not because you can't get in
contact with the original reporter.
 

With bug reports by e-mail this is normally not anonymous. Also usual
you can get in contact with the reporter.

More over, you do not need to go to any web page, you even need no web
browser. You can write comfortable with your preferred mail reader and
editor.

There are many bugs out there. Sometimes they can be reported by the
distribution bug tracker but if you install software directly or know
that the bug is upstream it is of no use to have a maintainer between.
And if you need to register with your shoe size (attention, I do
exaggerate) often at least I let the bug be and might fix it locally so
the software will not get better. This registration stuff for all is
such a broken concept at all! Also mailing lists is not the best form of
communication but it is ok that far as I can configure it in my mail
reader to sort it in a nice way. (Ever use nntp? This concept is much
better than Foren and mailing lists!)

However, I will not create a user account on this site too. Take the bug
report I gave here or let it be. If you are not interested in the
report, well, that's yours. If you are interested, I stay here or by PM
to answer questions or doing debugging. (And you might notice that I am
not anonymous, I even sign my mails.)

Regards
Klaus
- -- 
Klaus Ethgenhttp://www.ethgen.de/

pub  2048R/D1A4EDE5 2000-02-26 Klaus Ethgen
Fingerprint: D7 67 71 C4 99 A6 D4 FE  EA 40 30 57 3C 88 26 2B
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQEVAwUBS/6/Pp+OKpjRpO3lAQr/vwf/Q7cJW+djFrQQJCCEFzGCNhJ7+CBXDlsM
cDNthtphyWZKfk3EL8q4P+QDSw1MOuylkcTvGFzmcDPQz1yqVZ2KhDP3CTMWLOG7
8Zg3Ip93K5ZPLnTF28xgPsLGLjMEODTB9bDh6fymGCHYIVt8YW2lG+uN7EkJMy6e
f8iAdmRZWCEdT57uHpDwBmNMoSYDZd2RY5Qhor75YI9G5ikGqyvjbYlAlKmSYfFd
8eJkXbwoJb+2AuzplrUn6nl4Kb0tKxmWeNM3GMnpRRe4iJCuqXbMI+azakngIt0s
DTKoEvSK8bpSmEHBixfz9NLzKnGoaJodlJOe6FE+k4Uee2Qw5EeXBA==
=cz9H
-END PGP SIGNATURE-

   
Regardless of your intentions, etc, this is somewhat insulting IMO to an 
open-source/foss project. It's almost like saying "Well I appreciate the 
thousands of lines of code you've given me for free, and the man-hours 
it took to write that code, and the man-hours you've saved me, but I'm 
not willing to give you five minutes to create a log in to your bug 
tracker." Just sayin'. If you really can't be bothered feel free to hop 
on IRC, I will file the bug for you.

--

Joe McDonagh
Operations Engineer
AIM: YoosingYoonickz
IRC: joe-mac on freenode
"When the going gets weird, the weird turn pro."

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-us...@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] combining arrays in site.pp

[Kenton Brede]

I'm running 0.25.4.  What I'd like to do is place an array of users
under the default node.  These users rarely change.  Then within each
subsequent node, have another array of users added to the original
array.  These users change more frequently.  These users are then be
snarfed into a template.  The setup I've been using is adding all the
users to one array in each node definition.

I've read that using "+=" will add arrays to one another, but I keep
getting a "Could not parse for environment testing: Syntax error at
'='; expected '}' at /etc/puppet/manifests/testing/site.pp:54" error.
Is "+=" just not allowed in site.pp?

This is an example of what I have.

site.pp
-
node basenode {
$users_group = ['user0', 'user1']
}

node server1 inherits basenode {
$users_group += ['user2', 'user3', 'user4']
}
-

What I'm expecting from the above is $users_group = ['user0', 'user1',
'user2', 'user3', 'user4']

Thanks for any help.
Kent

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] Question about templates from variables

[James Cammarata]

> This seems like it's a bug with plusassignment to me, can you open a
> ticket on this?
> 

I had a moment of inspiration this morning and figured out what I needed to
do to get this working the way I wanted:

class foo {
  $file_content = template('foo/foo-base','foo/foo-bar')
  file { "/etc/foo":
content => $file_content,
  }
}

class foo::bab inherits foo {
  $foo::file_content += template('foo/foo-bab')
  File["/etc/foo"]{
content => $foo::file_content,
  }
}

I believe this is the way the plussignment operator should work, so you can
avoid the hackish use of variables like I'm doing above.

My primary motivation for this is something like sudoers, where certain
system roles require sudoers commands for different groups to use.  A
perfect example from our environment is any system that has an
Oracle-related role requires sudoers commands for the DBAs, on top of the
base roles we as Linux admins require on every system.  Essentially I want
to avoid having to list every template combination for every possible
permutation of roles.

An alternative to this would be to allow the template() function to take a
list as a variable, something like this:

$template_list = ["template1","template2","template3"]
content => template($template_list),

When I try that currently, I get the following error (which is a weird
error in and of itself):

err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Syntax error at '['; expected ']' at ...



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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: package question

[ed-rfmd]

That took care of it . I changed the names to libXp.i386 and
openmotif.i386. I was not using the package name properly, I was using
it as a generic identified instead of the actual package name.

Thanks again,
Ed

On May 28, 9:25 am, Thomas Bellman  wrote:
> On 2010-05-28 15:19, ed-rfmd wrote:
>
>
>
> >              package { "libXp-32bit":
> >                  provider =>  rpm,
> >                  source   =>  "$kickstart/ICAClient/RHEL5/
> > libXp-1.0.0-8.1.el5.i386.rpm",
> >                  ensure   =>  installed,
> >              }
>
> >              package { "openmotif-32bit":
> >                  provider =>  rpm,
> >                  source   =>  "$kickstart/ICAClient/RHEL5/
> > openmotif-2.3.1-2.el5_4.1.i386.rpm",
> >                  ensure   =>  installed,
> >                  require  =>  Package["libXp-32bit"],
> >              }
> > Why is it attempting to install libXp again? Shouldn't the ensure =>
> > installed prevent that from happening? Or does it have something to do
> > with the fact it is a duplicate package name but with a different
> > architecture?
>
> Because the package type uses the name you have specified to see
> if the package is already installed.  The packages are not really
> named "libXp-32bit" and "openmotif-32bit", are they?  They are
> more likely named "libXp.i386" and "openmotif.i386"; use that as
> package names, and it should work better.
>
>         /Bellman

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] package question

[Thomas Bellman]

On 2010-05-28 15:19, ed-rfmd wrote:


 package { "libXp-32bit":
 provider =>  rpm,
 source   =>  "$kickstart/ICAClient/RHEL5/
libXp-1.0.0-8.1.el5.i386.rpm",
 ensure   =>  installed,
 }

 package { "openmotif-32bit":
 provider =>  rpm,
 source   =>  "$kickstart/ICAClient/RHEL5/
openmotif-2.3.1-2.el5_4.1.i386.rpm",
 ensure   =>  installed,
 require  =>  Package["libXp-32bit"],
 }



Why is it attempting to install libXp again? Shouldn't the ensure =>
installed prevent that from happening? Or does it have something to do
with the fact it is a duplicate package name but with a different
architecture?


Because the package type uses the name you have specified to see
if the package is already installed.  The packages are not really
named "libXp-32bit" and "openmotif-32bit", are they?  They are
more likely named "libXp.i386" and "openmotif.i386"; use that as
package names, and it should work better.


/Bellman

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-us...@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] package question

[ed-rfmd]

The ICAClient package requires the 32 bit versions of libXp and
openmotif. I have this class defined:

class icaclient{

case $architecture {

i386: {

package { "ICAClient":
provider => rpm,
source   => "$kickstart/ICAClient/RHEL5/
ICAClient-11.100-1.i386.rpm",
ensure   => installed,
}
}

x86_64: {

package { "libXp-32bit":
provider => rpm,
source   => "$kickstart/ICAClient/RHEL5/
libXp-1.0.0-8.1.el5.i386.rpm",
ensure   => installed,
}

package { "openmotif-32bit":
provider => rpm,
source   => "$kickstart/ICAClient/RHEL5/
openmotif-2.3.1-2.el5_4.1.i386.rpm",
ensure   => installed,
require  => Package["libXp-32bit"],
}

package { "ICAClient":
provider => rpm,
source   => "$kickstart/ICAClient/RHEL5/
ICAClient-11.100-1.i386.rpm",
ensure   => installed,
require  => Package["openmotif-32bit", "libXp-32bit"],
}

}
}
}

On the initial run of puppetd on a 64 bit system I see these lines:
notice: //icaclient/Package[libXp-32bit]/ensure: created
notice: //icaclient/Package[openmotif-32bit]/ensure: created
notice: //icaclient/Package[ICAClient]/ensure: created

Everything installed correctly and the ICAClient works.

On subsequent puppetd executions I get these:
err: //icaclient/Package[libXp-32bit]/ensure: change from absent to
present failed: Execution of '/bin/rpm -i --oldpackage /net/rfns1/vol/
flexsrc/kickstart/config/ICAClient/RHEL5/libXp-1.0.0-8.1.el5.i386.rpm'
returned 1: warning: /net/rfns1/vol/flexsrc/kickstart/config/ICAClient/
RHEL5/libXp-1.0.0-8.1.el5.i386.rpm: Header V3 DSA signature: NOKEY,
key ID 37017186
package libXp-1.0.0-8.1.el5.i386 is already installed

Why is it attempting to install libXp again? Shouldn't the ensure =>
installed prevent that from happening? Or does it have something to do
with the fact it is a duplicate package name but with a different
architecture?

Lastly, does anyone have a suggestion on what to do to prevent this
error?

Thanks,
Ed

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] facter values in upper case

[Adam Winberg]

way to make it work:

$my_type = "$type"
$my_type = inline_template("<%= my_type.upcase %>")
notify { "type is set to $my_type":; }

thanks for your help!

//Adam



On 28 May 2010 13:47, Daniel Pittman  wrote:

> Ohad Levy  writes:
>
> > you are right, it seems that type is a reserved word in ruby :(
>
> Just don't try using the variable 'fork' in your templates. ;)
>
> > using another variable name should work.
>
> Theoretically you might be able to use a lookup function to get the value,
> but
> practically it is (sadly) simpler to deal with Ruby being a bit kooky, and
> just use a different fact or variable name.
>
>Daniel
>
> > On Fri, May 28, 2010 at 4:13 PM, Adam Winberg 
> wrote:
> >
> >> ok, interesting!
> >>
> >> however i cant make it work:
> >>
> >> $my_type = inline_template("<%= type.upcase %>") notify { "type is set
> to
> >> $my_type":; }
> >>
> >> and log output on client:
> >>
> >> puppetd[13739]: type is set to Notebook
> >>
> >> i was expecting to see "NOTEBOOK" there, but no luck. I'm new to puppet
> and
> >> my ruby is rubbish, am i doing something wrong?
> >>
> >> //Adam
> >>
> >> On 28 May 2010 08:53, Ohad Levy  wrote:
> >>
> >>> you can use inline_template to sanitize your values.. e.g.:
> >>>
> >>> $my_type = inline_template("<%= type.upcase %>
> >>>
> >>> Ohad
> >>>
> >>> On Fri, May 28, 2010 at 2:44 PM, Adam Winberg 
> >>> wrote:
> >>>
>  Hi,
> 
>  facter variables typically have values in lower case. We are looking
> into
>  moving to puppet for our config administration and are currently using
> a
>  system where we do file name matching dependent on specific suffixes -
> for
>  example a file named "*--LAPTOP" will only be deployed on machines
> tagged
>  as laptops.
> 
>  I would like to keep this naming convention and observed that facter
> has a
>  "type" variable that on laptops will contain the value "laptop" - but
> of
>  course i want it in upper case for, in my opinion, better clarity. Is
>  there some smart way of doing this?
> 
>  I guess i could do something like if $type == "laptop" {  $type =
> "LAPTOP"
>  }
> 
>  but im looking to see if there is any other smarter ways of doing
> this.
> 
>  Thanks,
> 
>  //Adam Winberg
> 
>  -- You received this message because you are subscribed to the Google
>  Groups "Puppet Users" group.  To post to this group, send email to
>  puppet-us...@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-us...@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-us...@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.
> >>
>
> --
> ✣ Daniel Pittman✉ dan...@rimspace.net☎ +61 401 155
> 707
>   ♽ 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-us...@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-us...@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] facter values in upper case

[Daniel Pittman]

Ohad Levy  writes:

> you are right, it seems that type is a reserved word in ruby :(

Just don't try using the variable 'fork' in your templates. ;)

> using another variable name should work.

Theoretically you might be able to use a lookup function to get the value, but
practically it is (sadly) simpler to deal with Ruby being a bit kooky, and
just use a different fact or variable name.

Daniel

> On Fri, May 28, 2010 at 4:13 PM, Adam Winberg  wrote:
>
>> ok, interesting!
>> 
>> however i cant make it work:
>> 
>> $my_type = inline_template("<%= type.upcase %>") notify { "type is set to
>> $my_type":; }
>> 
>> and log output on client:
>> 
>> puppetd[13739]: type is set to Notebook
>> 
>> i was expecting to see "NOTEBOOK" there, but no luck. I'm new to puppet and
>> my ruby is rubbish, am i doing something wrong?
>> 
>> //Adam
>> 
>> On 28 May 2010 08:53, Ohad Levy  wrote:
>> 
>>> you can use inline_template to sanitize your values.. e.g.:
>>> 
>>> $my_type = inline_template("<%= type.upcase %>
>>> 
>>> Ohad
>>> 
>>> On Fri, May 28, 2010 at 2:44 PM, Adam Winberg 
>>> wrote:
>>> 
 Hi,
 
 facter variables typically have values in lower case. We are looking into
 moving to puppet for our config administration and are currently using a
 system where we do file name matching dependent on specific suffixes - for
 example a file named "*--LAPTOP" will only be deployed on machines tagged
 as laptops.
 
 I would like to keep this naming convention and observed that facter has a
 "type" variable that on laptops will contain the value "laptop" - but of
 course i want it in upper case for, in my opinion, better clarity. Is
 there some smart way of doing this?
 
 I guess i could do something like if $type == "laptop" {  $type = "LAPTOP"
 }
 
 but im looking to see if there is any other smarter ways of doing this.
 
 Thanks,
 
 //Adam Winberg
 
 -- You received this message because you are subscribed to the Google
 Groups "Puppet Users" group.  To post to this group, send email to
 puppet-us...@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-us...@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-us...@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.
>> 

-- 
✣ Daniel Pittman✉ dan...@rimspace.net☎ +61 401 155 707
   ♽ 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-us...@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 Labs Announces Puppet Forge, a Central Repository for Puppet Modules

[James Turnbull]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Paul Lathrop wrote:
> Haha!
> 
> So much for my purchase of puppetstrings.net! I guess I can scrap the
> crappy code I had put together, too. :-P

Well if you have features you had done or had in mind - we'd welcome the
input.

Cheers

James

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBS/+suiFa/lDkFHAyAQJTtgf9EesVA4GoaZ8yH2Vw5ofZUwHgkfz/SDBf
RyTpqDj39DRKPMv86gNG6J0ystWaByRlsQEDvcFl370zLbTkU+RMVFpjt+mb4cOj
gc3XawiAn6ozIakAmKa7HNjtpwJmEtXBfURXGd28j4AhZw9N/Kdzq4Kh+HJleZgN
nD7QPvmmMupH3RwNO/M6Lt47o+BcPBobUnVBEtotYHQuINdi1se3z8OE9zBB4ycK
m9YE52NgReZB/3NawG0QgKqVJ8jSYZRVBESyRBD/Z3J2mfQ+Rdv3m+2BTHrLJCCy
zaDVesxi2Fer1FK8hoivf+VcykU4eUdveoVkHd/RsdVQzZ3fkkTeUQ==
=40ea
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] facter values in upper case

[Ohad Levy]

you are right, it seems that type is a reserved word in ruby :(
using another variable name should work.

I'll play and see if I can come up with something


On Fri, May 28, 2010 at 4:13 PM, Adam Winberg wrote:

> ok, interesting!
>
> however i cant make it work:
>
> $my_type = inline_template("<%= type.upcase %>")
> notify { "type is set to $my_type":; }
>
> and log output on client:
>
> puppetd[13739]: type is set to Notebook
>
> i was expecting to see "NOTEBOOK" there, but no luck. I'm new to puppet and
> my ruby is rubbish, am i doing something wrong?
>
> //Adam
>
>
>
> On 28 May 2010 08:53, Ohad Levy  wrote:
>
>> you can use inline_template to sanitize your values.. e.g.:
>>
>> $my_type = inline_template("<%= type.upcase %>
>>
>> Ohad
>>
>> On Fri, May 28, 2010 at 2:44 PM, Adam Winberg wrote:
>>
>>> Hi,
>>>
>>> facter variables typically have values in lower case. We are looking
>>> into moving to puppet for our config administration and are currently
>>> using a system where we do file name matching dependent on specific
>>> suffixes - for example a file named "*--LAPTOP" will only be deployed
>>> on machines tagged as laptops.
>>>
>>> I would like to keep this naming convention and observed that facter
>>> has a "type" variable that on laptops will contain the value "laptop"
>>> - but of course i want it in upper case for, in my opinion, better
>>> clarity. Is there some smart way of doing this?
>>>
>>> I guess i could do something like
>>> if $type == "laptop" {
>>>  $type = "LAPTOP"
>>> }
>>>
>>> but im looking to see if there is any other smarter ways of doing
>>> this.
>>>
>>> Thanks,
>>>
>>> //Adam Winberg
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Puppet Users" group.
>>> To post to this group, send email to puppet-us...@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-us...@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-us...@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-us...@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] facter values in upper case

[Adam Winberg]

ok, interesting!

however i cant make it work:

$my_type = inline_template("<%= type.upcase %>")
notify { "type is set to $my_type":; }

and log output on client:

puppetd[13739]: type is set to Notebook

i was expecting to see "NOTEBOOK" there, but no luck. I'm new to puppet and
my ruby is rubbish, am i doing something wrong?

//Adam



On 28 May 2010 08:53, Ohad Levy  wrote:

> you can use inline_template to sanitize your values.. e.g.:
>
> $my_type = inline_template("<%= type.upcase %>
>
> Ohad
>
> On Fri, May 28, 2010 at 2:44 PM, Adam Winberg wrote:
>
>> Hi,
>>
>> facter variables typically have values in lower case. We are looking
>> into moving to puppet for our config administration and are currently
>> using a system where we do file name matching dependent on specific
>> suffixes - for example a file named "*--LAPTOP" will only be deployed
>> on machines tagged as laptops.
>>
>> I would like to keep this naming convention and observed that facter
>> has a "type" variable that on laptops will contain the value "laptop"
>> - but of course i want it in upper case for, in my opinion, better
>> clarity. Is there some smart way of doing this?
>>
>> I guess i could do something like
>> if $type == "laptop" {
>>  $type = "LAPTOP"
>> }
>>
>> but im looking to see if there is any other smarter ways of doing
>> this.
>>
>> Thanks,
>>
>> //Adam Winberg
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To post to this group, send email to puppet-us...@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-us...@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-us...@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: SuSE and zypper

[Alpár Török]

2010/5/28 jb :
> looks like a typo/omission.  Add:
>
>    commands :zypper => "/usr/bin/zypper"
>
> to zypper.rb
>
> or change :rub to :zypper would probably be the right thing to do?
>

Yes, that was actually fixed. Check out
http://projects.puppetlabs.com/issues/3802.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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 Labs Announces Puppet Forge, a Central Repository for Puppet Modules

[Gabriel - IP Guys]

Haha!

So much for my purchase of puppetstrings.net! I guess I can scrap the
crappy code I had put together, too. :-P

--Paul

[Mr Gabriel Says ...] 

Then maybe grab a few guys from this list, and get them to help you
transfer everything to puppetforge :) Content, content content, any
takers?

Latest Article  :- The Puppet Module Tool
The Puppet Apprentice   :- http://puppetnewbie.blogspot.com
Follow me on twitter:- http://twitter.com/mritguru
Puppet #tags on twitter :- #puppet #puppetforge
IRC :- itguru ON irc.freenode.org (feel free to say
hi!)

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.