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" gr
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: [
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, autom
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/pup
-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
>
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.
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
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 m
-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 so
-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 certnam
* 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
-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
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
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 th
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 followi
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/iss
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
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 w
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
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))
> $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 subscribe
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
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:
PUPPETMAST
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
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:
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
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 t
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" gro
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 bu
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.
> 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
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:
>
>
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"
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-
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
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)
-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
-BEGI
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("<%=
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
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 messa
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?
Lat
41 matches
Mail list logo
