On Jul 19, 10:23 pm, James Turnbull wrote:
> The journey was long and arduous and many fell along the way but Puppet
> Labs is proud to announce the2.6.0release!
>
> The2.6.0release is a major feature release and includes a huge variety
> of new features, fixes, updates and enhancements. These in
On Apr 9, 9:04 am, Pete Emerson wrote:
> I see the instructions for creating custom facter recipes here:
>
> http://projects.reductivelabs.com/projects/puppet/wiki/Adding_Facts
>
> and in this thread, James Turnbull suggests that Facter might some day
> support other lang
I see the instructions for creating custom facter recipes here:
http://projects.reductivelabs.com/projects/puppet/wiki/Adding_Facts
and in this thread, James Turnbull suggests that Facter might some day
support other languages besides ruby:
http://groups.google.com/group/puppet-users/browse_thre
Interesting, I'll read that paper, thanks.
For our setup the version of software is exposed in the
puppet_node_classifier which connects to a database. Additionally, the
version of the configuration files and which puppet environment to use
are available as well. To do an upgrade, I change the ver
I'd also recommend (based on previous shooting myself in the foot)
that all of your servers talk to your own internal yum repo if
possible, and not directly to EPEL. Mirror EPEL if you want, but pull
in updates in some process that lets you review them before putting
them into your internal repo. T
If you don't care about the contents of the file, just whether it's
there or not:
unless => "/usr/bin/file MYFILE"
or
unless => "/usr/bin/stat MYFILE"
or
unless => "/bin/ls MYFILE"
should all be pretty lightweight
On Thu, Mar 4, 2010 at 12:06 PM, Patrick wrote:
>
> On Mar 4, 2010, at 7:29 A
I'm using puppet to deploy new versions of our application to our
server instances.
I do this by having a custom puppet node classifier that talks to a
database that defines what version of an application is supposed to be
on a particular node:
parameters:
application: "webapp",
webapp_versio
Okay, here's a proposed solution, what do you think?
In site.pp:
import "myapp/*/myapp.pp"
In myapp/123/myapp.pp:
if ($myapp_config == '123') {
// recipes go here
}
In this way, all different myapp.pp files get imported, but only the
rules inside the conditional for the desired version get
I take it back, I can't have the site.pp dynamically generated via
puppet, because potentially I need it to be different for each server.
--
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...@googlegrou
master to
generate the site.pp before running puppet on my node.
Pete
On Sun, Jan 10, 2010 at 5:22 PM, Pete Emerson wrote:
> Hmm, I'm not sure this accomplishes what I'm looking for. I already
> have control over what versions get installed on which servers (via a
> puppet_node_clas
Hmm, I'm not sure this accomplishes what I'm looking for. I already
have control over what versions get installed on which servers (via a
puppet_node_classifier tied to a database). Let me go into a bit more
detail. Maybe what you suggest applies, but I'm not seeing it quite
yet. Thanks for your h
A while ago I got some help from here about how to version my puppet
recipes. The solution was to generate an /etc/puppet.conf file via
puppet to create environments like this:
[v01]
manifest = /etc/puppet/manifests/v01/site.pp
Now, I want to move control of the puppet recipes to the applicat
Here's the solution I wound up using. I created a puppet.conf.erb
template file and had puppet create the puppet.conf file dynamically.
The critical pieces (I only wanted directories starting with v, like
v01, v02, et cetera):
<%
dirs = Dir.entries("/etc/puppet/manifests").sort
-%>
[main]
...
[
Scott,
Multiple environments is working for me under puppet 0.25.1.
I'm not sure what's wrong, but I wonder if having a manifest and
modulepath entry in the [main] part of your puppet.conf is overriding
any sections below. My puppet.conf does not have a manifest or
modulepath entry in [main].
P
You got close with quoting, but I think you're just missing the :
after the package, like this:
package { "lua5.1":
ensure => installed
}
On Fri, Oct 23, 2009 at 7:08 AM, Mathieu N wrote:
>
> Hi all,
> It might be a newby question but I cannot found any answer here or on
> the documentation
This originally started out as a question, but then I figured out the
answer (or should I say, "an answer"), so I'm sharing in the hopes
that this helps someone else out.
Suppose you have two packages that you want to ensure are installed,
and then use a require later on. I did it like this:
pac
aving WEBrick running, then cut over. So far, so good.
Next up is Puppet 0.25!
Pete
On Tue, Oct 6, 2009 at 3:03 PM, Paul Lathrop wrote:
>
> On Tue, Oct 6, 2009 at 2:10 PM, Pete Emerson wrote:
>>
>> I'm seeing this in my logs:
>>
>> kernel: possible SYN flooding on
I'm seeing this in my logs:
kernel: possible SYN flooding on port 8140. Sending cookies.
Could not call fileserver.describe: #
I'm running 0.24 with webrick, and have approximately 180 hosts under it.
I'm guessing that I'm simply hitting the limits of what webrick can do
(I'm working on moving
I'm working on migrating to 0.25 and Passenger, with multiple
master nodes for redundancy and scalability.
Pete
On Tue, Sep 22, 2009 at 12:41 PM, Clint Savage wrote:
>
> On Tue, Sep 22, 2009 at 1:38 PM, Pete Emerson wrote:
>>
>> I'm using 0.24 with Webrick (in the p
es, so it looks like what I can do is simply check the last
modified time of the last yaml file like this:
stat `ls -tr /var/lib/puppet/yaml/facts/*.yaml | tail -n1`
and then check to make sure that's within reasonable limits.
Pete
On Tue, Sep 22, 2009 at 12:55 PM, Pete Emerson wrote:
>
rint \$4}'` -ge 15 ]; then /etc/init.d/puppetmaster restart ;fi
>
> - Jeff
>
> On 09/22/2009 02:38 PM, Pete Emerson wrote:
>>
>> I'm using 0.24 with Webrick (in the process of migrating to 0.25 /
>> passenger).
>>
>> Occasionally, the puppetmasterd
I'm using 0.24 with Webrick (in the process of migrating to 0.25 / passenger).
Occasionally, the puppetmasterd becomes unavailable, and we see error
messages along the lines of:
Could not call puppetmaster.getconfig: #
I believe the puppetmasterd does not completely die, so it is still in
the p
Ah, in answer to my own question:
http://reductivelabs.com/trac/puppet/wiki/ConfigurationReference
--ignorecache should do the trick.
On Thu, Sep 17, 2009 at 7:14 AM, Pete Emerson wrote:
> With this solution would I need to clear a cache? If I do two puppet
> runs right after each
With this solution would I need to clear a cache? If I do two puppet
runs right after each other, doesn't puppet cache the recipes for a
period of time? If so, what do I need to do to wipe that local cache
out?
Pete
On Tue, Sep 15, 2009 at 2:42 PM, Pete Emerson wrote:
>
> Silviu, I
etdlock ]
> > do
> > sleep 1
> > done
>
> > #do your stuff
>
> > Silviu
>
> > On Tue, 15 Sep 2009 13:05:37 -0700, Pete Emerson
> > wrote:
> >> I'm using puppet (0.24, working on the 0.25 migration) to do rolling
> >> up
I'm using puppet (0.24, working on the 0.25 migration) to do rolling
upgrades across our datacenter.
I'm running puppet as a daemon.
In order to change an application version, I modify a database, which
in turn modifies the data that my puppet_node_classifier presents. I
then ssh to the nodes th
> On Sep 9, 2009, at 3:58 PM, Pete Emerson wrote:
>
>>
>> I'm seeing this as well, and have some info that may be useful. For me
>> the problem happens whether I use passenger-2.2.5, passenger-2.2.2, or
>> the puppetmasterd daemon directly.
>>
>> I
I'm seeing this as well, and have some info that may be useful. For me
the problem happens whether I use passenger-2.2.5, passenger-2.2.2, or
the puppetmasterd daemon directly.
I started with exactly the auth.conf from here:
http://github.com/reductivelabs/puppet/blob/c2e26b9bb28ebcb8e07822015f9
^
test.erb:5: syntax error
I'm missing something simple either in my test.erb or the way I run
ruby on it, or both.
Pete
On Thu, Aug 20, 2009 at 3:16 AM, Trevor Vaughan wrote:
>
> I usually just copy the erb, set the variables at the top and then run i
According to http://reductivelabs.com/trac/puppet/wiki/PuppetTemplating
I can do this for template syntax checking:
erb -x -T '-' mytemplate.erb | ruby -c
Is there a way to feed ruby values for the variables inside the
template and see what the file will look like on a target machine?
Pete
--
You can also use unless or onlyif. Here's an example where I manipulate
/foo/bar if package baz is not installed via rpm:
file { "/foo/bar":
source =>
unless => "rpm -q baz"
}
Same thing with 'onlyif'.
Pete
On Tue, Aug 4, 2009 at 11:37 PM, Eric Heydrick wrote:
>
> Facter plugin is
I have application and configuration versions stored so that my puppet node
classifier can spit them back out. I then change versions for the servers
that I want to upgrade and then force a puppet run. The remaining servers
won't change until I change their application / configuration versions.
Lat
I'm trying to figure out how "ensure => running" determines whether a
service is running or not (CentOS using init controlled services).
I have a custom service that has enable => running set on it:
service { "foo":
ensure => running,
enable => true
}
Every time puppet runs I see this:
Suppose I have 100 files distributed recursively:
file { "/var/sample":
source => "puppet:///files/sample",
ensure => directory,
recurse => true
}
What I'd like to do is have all files inside the directory be templated:
file { "/var/sample"
conf, I'll let you
know how it goes.
Thanks again for your pointer.
Pete
On Tue, Jul 7, 2009 at 8:45 AM, Pete Emerson wrote:
> Brilliant! I think that will save me tremendously. I'll play with it and
> let you know. Thanks very much.
>
> Pete
>
>
> On Tue, Jul 7, 2009
Brilliant! I think that will save me tremendously. I'll play with it and let
you know. Thanks very much.
Pete
On Tue, Jul 7, 2009 at 8:22 AM, Ohad Levy wrote:
>
> Maybe this can save you some time...
>
>
> http://github.com/ohadlevy/puppet-multipuppetmaster/blob/582f98840e2c7bbea9d9e820a3060b09
Levy wrote:
> why don't you use puppet environments?
>
> Ohad
>
>
> On Tue, Jul 7, 2009 at 7:46 AM, Pete Emerson wrote:
>
>> In order to facilitate puppet manifest upgrades, I need to manage puppet
>> recipes on a per-server basis.
>>
>> My puppet classi
In order to facilitate puppet manifest upgrades, I need to manage puppet
recipes on a per-server basis.
My puppet classifier spits out a variable called $puppet_iteration.
I tried putting this variable in my site.pp:
import
"/var/lib/puppet/files/static/applications/puppet/$puppet_iteration/syst
I also turn on reporting back to puppetmaster via --report and have
found that very useful for debugging and figuring out state centrally.
On 7/3/09, Sam Rowe wrote:
>
> FYI puppetd --test or puppetd -t is shorter than all of that
> --one-time --no-daemonize etc stuff and is basically the same.
If there is no default config file, you want to put a default config file in
place, but otherwise, leave it alone?
If so, one way to do it would be to use "unless" or "onlyif" in your recipe.
Something like this should work (untested by me), although there may be a
"better" way to do it:
I'm getting the same via Firefox on Mac. Doesn't look like it's browser
specific.
On Wed, Jul 1, 2009 at 10:35 AM, Sharada wrote:
> Any one able to join puppet chat from :
> http://reductivelabs.com/home/irc/
>
> I tried from IE and Firefox. It says ' Login Terminated'
>
> >
>
--~--~-~-
I have a bunch of CentOS machines. In the process of puppetizing one of them
I'm getting this warning (more complete debug info at the end):
warning: Found multiple default providers for service: init, base; using
init
info: /Service[gmond]: Provider init does not support features enableable;
not
Aha! Excellent. Reference:
http://reductivelabs.com/trac/puppet/wiki/ReportsAndReporting
I haven't played with this piece of puppet yet, but will do so now.
Thanks,
Pete
On Thu, Jun 11, 2009 at 3:55 PM, Luke Kanies wrote:
>
> On Jun 11, 2009, at 5:52 PM, Pete Emerson wrote:
>
Jun 11, 2009 at 8:55 AM, Luke Kanies wrote:
>
> On Jun 8, 2009, at 4:39 PM, Pete Emerson wrote:
>
> > I'm using puppet 0.24.7-4. I have a situation where I have some very
> > long running puppet runs in order to do upgrades (removing
> > applications from load bala
I'm using puppet 0.24.7-4. I have a situation where I have some very long
running puppet runs in order to do upgrades (removing applications from load
balancers gracefully, et cetera).
My puppet runs triggered via puppetrun are finishing successfully:
Jun 8 20:31:29 puppetd[10178]: Finished cata
Ah I see a new thread, "Assign variable with content of a file?" that lines
up with my needs, I'll check out the suggestions there.
Pete
On Sat, May 2, 2009 at 7:22 AM, Pete Emerson wrote:
> Oh, that makes sense. The require only sets the dependency of cron on exec,
> not
in/echo command
> itself. You can even see this in your logged output.
>
> On May 1, 1:56 pm, Pete Emerson wrote:
> > I'm trying to get a cron entry to exist based on the contents of a file.
> >
> > I tried this:
> >
> > exec { "check-cron&q
I'm trying to get a cron entry to exist based on the contents of a file.
I tried this:
exec { "check-cron":
command => "/bin/echo",
logoutput => true,
onlyif => "/bin/grep 'crontab' /etc/crontab.txt"
}
cron { exec-date:
require => Exec["check-cron"],
09 AM, Brice Figureau <
brice-pup...@daysofwonder.com> wrote:
>
> On 27/04/09 18:50, Pete Emerson wrote:
> > I think I'm running into situations where my variables are being used as
> > floats instead of strings.
> >
> > For example, if my puppet_node_clas
I think I'm running into situations where my variables are being used as
floats instead of strings.
For example, if my puppet_node_classifier prints this:
---
parameters:
version: 0.10
and my command is this:
command => "/bin/rpm -hiv http://server/package-$version.x86_64.rpm";
I think it wil
I overlooked the puppetmasterd syslog (*headslap*) which gave me the key
piece of information I needed: the classifier did not have permissions to
read my SQLite database.
It would have been useful to have this error message passed on to puppetd:
Apr 15 16:39:23 newinstance puppetmasterd[7949]: C
I'm stuck. All of my puppet clients in my dev environment are reporting this
when I do a manual run:
# /usr/sbin/puppetd --server=03.admin.demo.nym1 --test
err: Could not retrieve catalog: Could not find node '01.web.test'; cannot
compile
warning: Not using cache on failed catalog
Is there a good
I resolved this problem. I discovered that there was a key mismatch. I'm
loving puppet, but the error messages are completely frustrating.
Pete
>
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group
Apologies if this winds up in the group twice, I'm not positive I submitted
this the first time around.
I installed puppet on an existing client and am getting this when running
puppetd --test:
err: Could not create sshd: undefined method `controllable?' for
nil:NilClass
warning: Not using cache
I just connected a new host to my puppetmaster.
The error that I get when I run puppetd in test mode is:
err: Could not create sshd: undefined method `controllable?' for
nil:NilClass
warning: Not using cache on failed catalog
warning: Configuration could not be instantiated: undefined method
`co
55 matches
Mail list logo
