I do that in this way:
On puppet.conf on the puppetmaster:
---
[puppetmasterd]
reports = store,rrdgraph,tagmail,log
autosign = true
environments = alpha,beta,gamma
manifest = /no/file
[beta]
modulepath = /etc/puppet/data/beta/
manifest = /e
Thanks for the info, Andrew.
I'm waiting for passport reneval procedures and relative timings
before confirming my partecipation at the Puppet Camp.
I take the occasion for a general broadcast.
For the people planning to come to San Francisco some days before the
event (to cope with jet-lags or ju
I'm in :)
On Tue, Sep 8, 2009 at 5:45 PM, Macno wrote:
>
> Thanks for the info, Andrew.
> I'm waiting for passport reneval procedures and relative timings
> before confirming my partecipation at the Puppet Camp.
> I take the occasion for a general broadcast.
> For the people planning to come to
Hi,
Not sure this is the right place to report this.
On an OpenVZ HardwareNode, the 'virtual' parameter given by facter
says 'openvz'.
This is because the /proc/user_beancounters file also exists on the
hardware node.
This has some bad side-effects as a hardware node should, for example,
have a
Thank you, the request has been created:
http://projects.reductivelabs.com/issues/2611
On Sep 8, 7:56 am, Luke Kanies wrote:
> On Aug 20, 2009, at 1:25 AM, Jan wrote:
>
>
>
> > Hi,
>
> > I came across a use case where I would like to access a value of an
> > attribute of a particular resource.
On Monday 07 September 2009 17:44:48 sven.tho...@bt.com wrote:
> Hi Gary,
>
> thanks for the solaris package! Some questions: At which point will 0.25 be
> available in the current/unstable tree? Also, is anyone creating packages
> for Sol8 and 10? We are still at 0.24.7 here (in /current)...which
Has anyone done an upgrade script to upgrade from 0.24 to 0.25?
I usually just run ruby install.rb to install from the tar ball, but
notice that quite a bit has changed with the 0.25 release and know
that much of the 0.24 stuff will still be hanging around.
Thanks,
Matt
--~--~-~--~
On Sep 8, 2009, at 9:13 AM, Matt wrote:
>
> Has anyone done an upgrade script to upgrade from 0.24 to 0.25?
>
> I usually just run ruby install.rb to install from the tar ball, but
> notice that quite a bit has changed with the 0.25 release and know
> that much of the 0.24 stuff will still be ha
On Sep 8, 2009, at 6:34 AM, Julien Cornuwel wrote:
>
> Hi,
>
> Not sure this is the right place to report this.
> On an OpenVZ HardwareNode, the 'virtual' parameter given by facter
> says 'openvz'.
> This is because the /proc/user_beancounters file also exists on the
> hardware node.
>
> This ha
is the classes section from Puppet::Node accessible at parse time?
example:
from yaml/node/supercoolmanchine.super.cool.place.yaml
classes:
- workstation
- httpd
- dev
can I access this list from within puppet manifests?
thanks,
Dan
--~--~-~--~~~---~--~~
You r
2009/9/8 Matt :
>
> Has anyone done an upgrade script to upgrade from 0.24 to 0.25?
>
> I usually just run ruby install.rb to install from the tar ball, but
> notice that quite a bit has changed with the 0.25 release and know
> that much of the 0.24 stuff will still be hanging around.
>
Matt
If
RRDtool gem wont install in Ubuntu, neither will work trying to
recompile the library since there are some rassignments of struts that
break the whole thing.
On Sep 7, 2009, at 2:29 PM, Eric Lannaud wrote:
> Hi,
>
> i'm on Linux ubuntu 9.04, with puppet version 0.24.5 ; I try to use
> the r
2009/9/8 Julien Cornuwel :
>
> Hi,
>
> Not sure this is the right place to report this.
> On an OpenVZ HardwareNode, the 'virtual' parameter given by facter
> says 'openvz'.
> This is because the /proc/user_beancounters file also exists on the
> hardware node.
Check the current Facter tickets - I
On Sep 8, 2009, at 1:53 AM, Matt Delves wrote:
>
> Hey Folks,
> I'm looking for some documentation on migrating clients from one
> puppet server to another. Any links would be greatly appreciated.
>
> Thanks,
> Matt Delves
>
Hi Matt,
It's moving:
- the puppet code
- SSL certs
- node definiti
I'm currently upgrading our puppetmaster to 0.25, at first just using
the standard webrick install to get the modules working.
Both my new 0.25 clients and existing 0.24 clients had no problem connecting.
I've now changed the puppetmaster over to run under passenger, my 0.24
clients are still con
Hi Macno
My intention was to use a similar setup like you explained ...
The big issue is now ...
the customer beta can get the configuration from alpha!
All what customer beta has to do is to run something like that in the
console
puppetd -t --environment=alpha
or to change the environm
On Sun, Sep 6, 2009 at 2:21 PM, Joe McDonagh wrote:
>
> Nigel Kersten wrote:
> > https://sites.google.com/a/explanatorygap.net/puppet/
> >
> >
> https://sites.google.com/a/explanatorygap.net/puppet/Home/puppet-0.25.0.pkg.tar.bz2
> >
> >
> > Please note the issue with Facter and OS X 10.6.0 still r
On Mon, Sep 7, 2009 at 9:34 AM, Asif Iqbal wrote:
>
> On Sat, Sep 5, 2009 at 4:11 PM, Asif Iqbal wrote:
> > # /etc/init.d/apache2 restart
> > * Restarting web server apache2
> > Syntax error on line 21 of /etc/apache2/conf.d/puppetmasterd:?
> > Invalid command 'RackAutoDetect', perhaps misspelle
Those aren't errors as far as I understand it Asif.
They're a summary of the status of each thread for debugging purposes. In
our use cases with Puppet it's almost always going to show the same status
for each thread as below.
On Mon, Sep 7, 2009 at 4:58 PM, Asif Iqbal wrote:
>
> I am getting a
This would be awesomely useful.
I'm thinking of cases where you may have complicated conditionals
determining the attribute for a resource, and then want to reuse that same
attribute value in a different resource without repeating the conditional
work.
On Mon, Sep 7, 2009 at 10:56 PM, Luke Kanie
> All what customer beta has to do is to run something like that in the
> console
>
> puppetd -t --environment=alpha
>
> or to change the environment entry to alpha in /etc/puppet/puppet.conf
> on the client side !
>
> So there is no security in place ;-(.
Well, not exactly.
In order to do this
Philipp,
a side note to avoid confusion: Macno = Al @ Lab42
There was some bug lurking in Google groups that used in this group a
nick I defined for another one...
Alessandro
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Noticed I was running passenger 2.2.3 (which did work for 0.24) so I
upgraded to 2.2.5.
After restarting one of my 0.25 nodes started working, but the other
one still gets:
warning: peer certificate won't be verified in this SSL session
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:55:in
On Tue, Sep 8, 2009 at 11:02 AM, Nigel Kersten wrote:
>
>
> On Mon, Sep 7, 2009 at 9:34 AM, Asif Iqbal wrote:
>>
>> On Sat, Sep 5, 2009 at 4:11 PM, Asif Iqbal wrote:
>> > # /etc/init.d/apache2 restart
>> > * Restarting web server apache2
>> > Syntax error on line 21 of /etc/apache2/conf.d/puppet
On Tue, Sep 8, 2009 at 11:04 AM, Nigel Kersten wrote:
> Those aren't errors as far as I understand it Asif.
Thanks
>
> They're a summary of the status of each thread for debugging purposes. In
> our use cases with Puppet it's almost always going to show the same status
> for each thread as below
On Tue, Sep 8, 2009 at 8:44 AM, Gary Larizza wrote:
>
>
> As long as it includes a trip to the Mission District for Burritos,
> I'm in for 9/30.
>
We have great burritos down in the South Bay too.
This is the best breakfast burrito/hangover cure I've found down here:
http://www.yelp.com/biz/ro
Is is possible to have a puppetmaster that is a client of a different
puppetmaster? We manage our customers' server via puppet, but one customer
has a puppetmaster server which looks after their internal systems. We've
tried the following in /etc/puppet/puppet.conf ("customer" and "us"
replacing t
On Sep 8, 12:34 pm, Julien Cornuwel wrote:
> Not sure this is the right place to report this.
> On an OpenVZ HardwareNode, the 'virtual' parameter given by facter
> says 'openvz'.
> This is because the /proc/user_beancounters file also exists on the
> hardware node.
This has been fixed already:
I'm going to start a fresh with the puppetmaster install :-)
2009/9/8 Matt :
> Noticed I was running passenger 2.2.3 (which did work for 0.24) so I
> upgraded to 2.2.5.
>
> After restarting one of my 0.25 nodes started working, but the other
> one still gets:
>
> warning: peer certificate won't b
Any idea how quickly we'll see this in EPEL?
Thanks,
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-users@googlegroups.com
To unsubscribe
On 8/09/09 11:45, Macno wrote:
> Thanks for the info, Andrew.
> I'm waiting for passport reneval procedures and relative timings
> before confirming my partecipation at the Puppet Camp.
> I take the occasion for a general broadcast.
> For the people planning to come to San Francisco some days befo
AFAIK this is the result of a known bug in Passenger 2.2.3 and newer.
ext/rack/README states:
> *** Important note about Passenger versions:
>2.2.2 is known to work.
>2.2.3-2.2.4 are known to *NOT* work.
>2.2.5 (when it is released) is expected to work properly again.
You should prob
As long as it includes a trip to the Mission District for Burritos,
I'm in for 9/30.
--~--~-~--~~~---~--~~
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@googlegro
Hi John,
Thank you very much for the answer, it's seem like a good one.
its going to help me a lot!!
I will be out of office until next week, so i can check that in a while, but
im sure that this mail will fixed my problem.
Thanks again,
Dotan
On Tue, Sep 8, 2009 at 3:43 AM, John Warburton wro
I've been running puppet for nearly two years. As the number of clients have
expanded so performance has eroded. I've done stop gaps solutions such as
creating two puppet masters and feeding a fileserver off one of them and
reducing the frequency that clients check in, but I knew they were stop gap
hmm passenger 2.2.5 is released? hmm I'll have to test it out.
-L
--
Larry Ludwig
Reductive Labs
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-u
Any recommendations on lodging?
-Ben
--~--~-~--~~~---~--~~
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 emai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brice Figureau wrote:
>> Who is interested for a can reply here or mail me.
>
> I'll be in SF from Sept 28th, and certainly available each evening (and
> certainly also the week-end post Puppet Camp).
>
> Feel free to ping me by e-mail/irc,
Ditto.
http://tmz.fedorapeople.org/repo/puppet/
-L
--
Larry Ludwig
Reductive Labs
--~--~-~--~~~---~--~~
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
T
I know that the pkgdmg provider doesn't support upgradeable or
anything like that... so how do the mac
admins out there upgrade for example puppet to the latest version on
macs using puppet itself? Is there
a good way to do this? I know it will reinstall (and "upgrade" of
course) if I remove the /
$facter_package = "facter-1.5.4.dmg"
$puppet_package = "puppet-0.24.8-p20090805.dmg"
package { "$facter_package":
ensure => installed,
source => "$pkgbase/puppet/$facter_package",
}
package { "$puppet_package":
ensure => installed,
source => "$pkgbase/puppet/$pup
Marziani, Michael wrote:
> Any idea how quickly we'll see this in EPEL?
In addition to the link Larry posted for unofficial Fedora/EPEL
packages¹, I'd say we probably shouldn't rush this into the EPEL
repos. It's a large change and it's probably wise to let it see a bit
more testing before we pus
2009/9/9 Todd Zullinger :
> Marziani, Michael wrote:
>> Any idea how quickly we'll see this in EPEL?
>
> In addition to the link Larry posted for unofficial Fedora/EPEL
> packages¹, I'd say we probably shouldn't rush this into the EPEL
> repos. It's a large change and it's probably wise to let it
Yes, its possible :)
but that would mean a CA chain, and eventually that each client can query
all puppetmasters (which I'm not sure this is what you are looking for in).
maybe setup a different puppet.conf for your puppet master clients (With a
different ssl directory etc?)
Ohad
On Wed, Sep 9
Cool, I agree epel-testing is probably better, and maybe once we're sure most
of the easy bugs are cooked out in 0.25.1 we can get that into EPEL.
best regards,
michael
-Original Message-
From: puppet-users@googlegroups.com [mailto:puppet-us...@googlegroups.com] On
Behalf Of James Turn
Hey Folks,
I've just migrated from 0.24.8 to 0.25.0 and I'm finding that the
logfiles aren't being updated promptly. If I restart the puppet-server
service it dumps the logs then though only intermittently.
Is this a known problem? The only other change I've made is that I've
added storeconfigs a
Hi Andrew,
Its hard to get through if you are not in the right timezone, any email?
Thanks,
Ohad
On Wed, Sep 9, 2009 at 11:06 AM, Andrew Shafer wrote:
>
> We're staying at the Serrano and there is a block of rooms there.
>
> You should be able to get them for $149 a night.
>
> Call them here 41
We're staying at the Serrano and there is a block of rooms there.
You should be able to get them for $149 a night.
Call them here 415-351-7660
On Tue, Sep 8, 2009 at 2:24 PM, Ben Beuchler wrote:
>
> Any recommendations on lodging?
>
> -Ben
>
> >
>
--~--~-~--~~~---
48 matches
Mail list logo
