Hi,
I'm using Gentoo and puppet-2.6.12. The puppet master and client are
wrapped up in the same package, app-admin/puppet. Can someone suggest
a simple way of installing only the puppet client (I'm new to Gentoo)?
Thanks,
P.
--
You received this message because you are subscribed to the Goo
Hello list,
I am looking for advice/best-practices on how to handle inter-module
dependencies.
We have a fairly large/complex code base (100+ modules) with a lot of
history (we started at 0.24) and lately we have taken into looking how we
can improve the quality of the codebase.
Parametrized cl
On Thu, Jan 26, 2012 at 7:55 AM, Alexander Swen wrote:
> hi,
>
> in the logs of our 2.7.10 puppet master we find messages like these:
> Dynamic lookup of $functie at /etc/puppet/manifests/server_classes.pp:52
> is deprecated. Support will be removed in Puppet 2.8. Use a fully-qualified
> variable
Since Felix seems not to have gotten around to doing this in the past
couple of days, or else was unable to do so,
On Jan 24, 3:28 am, Felix Frank
wrote:
>
> there was a discussion in the "can we deprecate defined() in Telly"
> thread about how we can even begin to design Forge modules without it
On 26/01/12 16:02, Matt Zagrabelny wrote:
On Thu, Jan 26, 2012 at 9:35 AM, Jonathan Gazeley
wrote:
On 26/01/12 15:22, Matt Zagrabelny wrote:
I don't know about "easy", but here is what I am doing:
Thanks Matt, that's helpful.
This addresses how to distribute keys to node from the fileser
I don't have a suggestion but I can confirm I see the same behavior with a
2.7.10 server and 2.7.10
client running the very latest puppetlabs-firewall code. It constantly
claims things have changed to
the exact identical stuff:
notice: /Firewall[000 INPUT allow related and established]/state: sta
On Thu, Jan 26, 2012 at 9:35 AM, Jonathan Gazeley
wrote:
> On 26/01/12 15:22, Matt Zagrabelny wrote:
>>
>> I don't know about "easy", but here is what I am doing:
>
>
> Thanks Matt, that's helpful.
>
> This addresses how to distribute keys to node from the fileserver, but I
> wonder if there is a
Hi,
After upgrading a server and client from 2.6.13 to 2.7.10 my configuration with
array attributes
are behaving differently. 3 examples:
(1)
k5login {'/root/.k5login-test':
principals => ['m...@cern.ch', 't...@cern.ch'],
}
while .k5login file is created perfectly but every puppet
hi,
in the logs of our 2.7.10 puppet master we find messages like these:
Dynamic lookup of $functie at /etc/puppet/manifests/server_classes.pp:52 is
deprecated. Support will be removed in Puppet 2.8. Use a fully-qualified
variable name (e.g., $classname::variable) or parameterized classes.
Howe
Has anyone had any experience with using RVM with Puppet?
I know with puppet 2.6 it directly invokes /usr/bin/ruby on RHEL based
OSes but in 2.7 I see that its using env to invoke ruby.
Is there a noticable performance increase with ruby 1.9 over 1.8?
--
You received this message because you ar
On 26/01/12 15:22, Matt Zagrabelny wrote:
I don't know about "easy", but here is what I am doing:
Thanks Matt, that's helpful.
This addresses how to distribute keys to node from the fileserver, but I
wonder if there is a mechanism where if the key doesn't exist on the
fileserver, the key tha
On 01/26/2012 04:28 PM, jcbollinger wrote:
> The 'defined' function can maybe
> ensure that the manifests compile, but it cannot ensure that the
> resulting configuration is correct. That makes it worse than useless
> for the purpose, as far as I'm concerned.
Exceptionally good point.
--
You re
On Jan 20, 4:34 pm, Cody wrote:
> On Jan 20, 6:39 am, jcbollinger wrote:
>
>
>
> > On Jan 20, 3:00 am, Dan Bode wrote:
>
> > > * the big reason I keep on leaning on it is for package dependencies.
> > > Often
> > > something needs an additional package installed (and it is possible that
> > >
Hi Jonathan,
On Thu, Jan 26, 2012 at 5:40 AM, Jonathan Gazeley
wrote:
> Hi all,
>
> I already use Puppet to collect and distribute SSH host public keys between
> machines I manage. I now want to collect private host keys from each node
> and store them on the puppetmaster, so when I rebuild a nod
Here is my config.ru by the way... checking to make sure it is correct...
# This file is mostly based on puppetmasterd, which is part of
# the standard puppet distribution.
require 'rack'
require 'puppet'
require 'puppet/network/http_server/rack'
# startup code stolen from bin/puppetmasterd
Pupp
Based on what Nigel said I checked my auth.conf file lo and behold it was
MIA. Don't know why but I created a new one at any rate and tried again.
Still getting errors, but they are at least different errors.
Looking in the apache2 log I find an intriguing error:
from config.ru:1
[ pid=7
On Jan 23, 9:12 am, Kenneth Lo wrote:
> The way my environment setup is that we have puppet dashboard handles ALL
> node registration as well as class assignment. We simply declare different
> groups, assign them with classes, and assign nodes into those groups for
> different roles.
>
> So w
- Original Message -
> I'm having the same thing, I use puppetd -tv all the time and now
> it's
> trying to delete a .pid at the end:
>
>
> err: Could not remove PID file /var/run/puppet/agent.pid
>
>
> It's super annoying but not fatal I suppose. I stopped the daemon
> from running a
On Jan 24, 3:51 am, Alexandre wrote:
> > Think about it. You want puppet to send a notification to a resource.
> > Puppet must decide whether this notification gets sent. So it must
> > process the notifying resource. After that, *if* a notification was in
> > fact generated, it can process the
I'm having the same thing, I use puppetd -tv all the time and now it's
trying to delete a .pid at the end:
err: Could not remove PID file /var/run/puppet/agent.pid
It's super annoying but not fatal I suppose. I stopped the daemon from
running and tried running puppetd again but it still gave the
Thanks for replying. I will try it on my 2.6.12 and report back to the list
“Sometimes I think the surest sign that intelligent life exists elsewhere in
the universe is that none of it has tried to contact us.”
Bill Waterson (Calvin & Hobbes)
- Felix Frank wrote:
> On 01/26/2012 02:20 PM,
On Jan 25, 10:53 am, Jo Rhett wrote:
> On Jan 25, 2012, at 8:30 AM, Nick wrote:
>
> > But then I have to anticipate every possible value of $shell and define
> > resources for them. Anything which is not defined like this is not usable
> > within the scheme, because there will be no file resour
On 01/26/2012 02:20 PM, Dick Davies wrote:
> That kind of thing should work (been using similar tricks since 0.25.x);
I think Dan was addressing this:
> scope.lookupvar('resolver::params::resolvers')
I'm not sure when this was new, I believe it works with 2.6.x
--
You received this message bec
That kind of thing should work (been using similar tricks since 0.25.x);
one odd thing about Puppet is you have
more flexibility in templates than in the DSL itself (since erb opens up
the full Ruby syntax).
On 24 January 2012 14:30, Dan White wrote:
> What is the minimum version of puppet (and o
- Original Message -
> Is the puppet agent daemon running when you run the agent by hand?
Ah! thats it, I'll take a look
--
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.c
Is the puppet agent daemon running when you run the agent by hand?
On Thu, 26 Jan 2012 13:07:16 + (GMT)
"R.I.Pienaar" wrote:
> On a fresh 2.7.10 install with official RPMs on CentOS 6.2 I can't reproduce
> this:
>
> [root@dev1]# puppet agent --onetime --verbose --no-daemonize
> info: Cach
On a fresh 2.7.10 install with official RPMs on CentOS 6.2 I can't reproduce
this:
[root@dev1]# puppet agent --onetime --verbose --no-daemonize
info: Caching catalog for dev1.devco.net
info: Applying configuration version '1327583153'
notice: Finished catalog run in 0.28 seconds
[root@dev1]#
and
Looks like the code paths in Puppet::Agent changed a lot and the patch
that was applied and worked for 2.6.x would need to be different for 2.7.x
Will set up a 2.7 master and see if i can reproduce/fix
- Original Message -
> Yeah everything does work, I just really don't like seeing pink
Yeah everything does work, I just really don't like seeing pink :)
Cheers,
Steph
On Thu, 26 Jan 2012 12:26:14 +
Jonathan Gazeley wrote:
> I am seeing the same message printed on each run, on CentOS 6.2. Puppet
> still works, so it's not critical. Just waiting for a fix :)
>
> Jonathan
>
I am seeing the same message printed on each run, on CentOS 6.2. Puppet
still works, so it's not critical. Just waiting for a fix :)
Jonathan
On 26/01/12 12:00, Steph Gosling wrote:
Hi all,
Upgraded a master and a couple of clients to 2.7.10 and now see the
following when running an agent if
Hi all,
Upgraded a master and a couple of clients to 2.7.10 and now see the
following when running an agent if the daemon is also running:
[steph@somehost ~]$ sudo puppet agent --onetime --verbose --no-daemonize
info: Caching catalog for somehost.example.com
info: Applying configuration version '
Hi all,
I already use Puppet to collect and distribute SSH host public keys
between machines I manage. I now want to collect private host keys from
each node and store them on the puppetmaster, so when I rebuild a node
it receives the same key.
Is there an easy way of doing this?
Thanks,
Jo
On 01/26/2012 12:15 PM, Felix Frank wrote:
> On 01/24/2012 08:21 PM, Aaron Grewell wrote:
>> If you didn't specifically configure Puppet to use Passenger then
>> you're using Mongrel by default. Scalability => false.
>
> Isn't that webrick?
>
> AFAIK mongrel would be fine, webrick is indeed a
On 01/26/2012 11:21 AM, Nick wrote:
> For example, suppose in one place I need a file to exist, and in another I
> also
> need it to be executable. Oh dear, I can't do that.
That, and you'd need to merge require/before etc. Such things aren't
trivial. Nan put it this way:
On 01/25/2012 03:59 PM
On 26/01/12 01:25, Ashley Penney wrote:
> All I know is that telling users "If you download 5 modules from puppet forge
> make sure you go through them all, extract any duplicating resources into
> random modules that exist purely to allow you to realize packages" instead
> leads
> to a really bad
On 26/01/12 00:55, Trevor Vaughan wrote:
> I mentioned in a previous thread that I don't see an issue with having
> multiple identical resources compiled across the code base and I'd like to add
> that to this thread since it's related.
>
> class a {
> package { 'foo': ensure => 'present' }
> }
Hi,
On 01/26/2012 02:25 AM, Ashley Penney wrote:
> This is a fantastic reply and I appreciate the work you put into it. I
> have just one
> question. As it stands functions can only apply to partial catalogs and
> not to the
> full catalog. Is this a fundamental design decision that cannot be
>
101 - 137 of 137 matches
Mail list logo
