No-one doing anything similar?
Cheers
Gav
On Friday, 15 February 2013 12:08:37 UTC, Gavin Williams wrote:
Morning all,
Firstly, apologies for the length of this post, however I thought it
probably most useful to fully outline the challenge and the desired
result...
Ok, so we're in
The Puppet Ruby DSL in its current form is deprecated:
Issue: https://projects.puppetlabs.com/issues/18876
Discussion:
https://groups.google.com/forum/?fromgroups=#!topic/puppet-dev/UsDaDGAneEE
On Sunday, February 17, 2013 12:42:05 AM UTC+1, Ryan Bowlby wrote:
...Bueller
Anyone have an
I've found an apparent bug in the puppet parser.
If you are using 'import' to include the contents of a subdirectory, like this:
import 'foo/*.pp'
and then you create a new module 'foo', suddenly the import statement silently
stops working. This means that any node definitions in the
Hi There,
You can, however once a class is defined you must then apply it to the node
using 'include'
Example:
[ Keiran ~]$ cat /tmp/example.pp
class class1 {
exec { exec1 :
command = /bin/touch /tmp/${title},
}
}
class class2 {
exec { exec2 :
On Monday, February 18, 2013 12:21:11 AM UTC-6, John Warburton wrote:
Is this mcollective version 3.x or 2.3.x?
Deprecation warning occurs in 2.3. Complete removal will occur in the 3.x
production branch.
So you should be good to continue using it for a few months to come, but
- Original Message -
From: Drew Blessing drew.bless...@mac.com
To: puppet-users@googlegroups.com
Sent: Monday, February 18, 2013 11:47:53 AM
Subject: Re: [Puppet Users] Stomp connector deprecated ?
On Monday, February 18, 2013 12:21:11 AM UTC-6, John Warburton wrote:
Is
On 22.1.2013 23:04, jcbollinger wrote:
You are correct that that only the identity of the client node is
authenticated by Puppet, and even that only insomuch as the client can
be relied upon to protect its SSL certificate. The $hostname fact
cannot be relied upon to convey that information,
Dear John,
I tryed as you suggested, and didn't work.
I Found where is the problem that produces the failure in both cases. The
problem basically is that on all the nodes I'm using inherits definition
like:
node basenode {
include shorewall
include othermodules
}
node examplenode1
I have been thinking about a good way to include things in Hiera--that is,
to insert a directive to add another stream. The problem is one of
attachment: inserting things becomes complex when you think much about it.
Consider the following:
---
key1: value1
key2: value2
On Saturday, February 16, 2013 5:42:05 PM UTC-6, Ryan Bowlby wrote:
...Bueller
Anyone have an answer for this? This seems like a pretty pertinent feature
for anyone looking to take advantage of the ruby DSL. I for one would be
eternally grateful.
As Ingo Fischer observed, Puppet's
On Monday, February 18, 2013 3:47:40 AM UTC-6, Steve Shipway wrote:
I've found an apparent bug in the puppet parser.
If you are using 'import' to include the contents of a subdirectory, like
this:
import 'foo/*.pp'
and then you create a new module 'foo', suddenly the import statement
Hi Gary,
Any other thoughts on what could be going on here? I'm afraid I haven't
made any further progress on it, and am at a bit of a loss. Any suggestions
you or anyone else may have would be greatly appreciated!
Thanks,
Doug
On Mon, Jan 28, 2013 at 4:38 PM, Doug Mayer d...@ebackpack.com
Hi,
Is there a way to control access to the filebucket?
Specifically, I wish to allow agents to backup to the filebucket but never
restore.
Is this possible to do?
Thanks,
Brian
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe
Why don't you use nodes groups or environments to prevent the second set of
servers to be updated?
Once validated on the first node group, you can easily deploy on the second set.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe
Why don't you use nodes groups or environments to prevent the second set of
servers to be updated?
Once validated on the first node group, you can easily deploy on the second set.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe
Sorry wrong thread *getting more coffee*
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group,
I just built a new puppet master, and whenever I run puppet on it, it
throws an error while processing a service resource:
# puppet agent -t
Info: Retrieving plugin
Info: Caching catalog for i-45dc2b1d
Info: Applying configuration version 'g
9ea47ad19bc706a754c00f00a024309948d3ea03'
Error:
On 18 February 2013 23:19, R.I.Pienaar r...@devco.net wrote:
No eta for when the 2.2.x branch will move forward, no eta for when this
adapter
will be removed from production code, no need to panic. But if you're
starting
out now you should look to using one of the new connectors I posted
Hi Elad,
There is an audit mode which may help you.
There is an explanation of how it works here.
https://puppetlabs.com/blog/all-about-auditing-with-puppet/
On 18 February 2013 16:45, Elad Shmitanka elad.shmita...@gmail.com wrote:
While trying to build safety mechanisms for applying new
On 17 February 2013 01:34, Jason Edgecombe ja...@rampaginggeek.com wrote:
On 02/14/2013 07:25 PM, Peter Brown wrote:
On 15 February 2013 10:04, joe lava...@gmail.com wrote:
Puppet isn't particularly good at code deployment. Ideally, you'd package
your code, set a package resource to ensure
No, but it's not related to the manifest. The manifest this resource is
in actually hasn't changed in months. Also I can reboot the box and it
goes away. Other boxes that aren't doing it will sometimes start doing
it when they reboot. (at least that's the behaviour I've been observing,
but I have
21 matches
Mail list logo
