Hi!
a few email exchanges on this ML coupled with John's remark that he'd
be open for an architectural advice made realize that a discussion focused
on a particular use case I'm trying to address might be much more fruitful
than random questions here and there. It is a long email, but I hope it wi
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 o
On 17 February 2013 01:34, Jason Edgecombe wrote:
> On 02/14/2013 07:25 PM, Peter Brown wrote:
>
>> On 15 February 2013 10:04, joe wrote:
>>
>> Puppet isn't particularly good at code deployment. Ideally, you'd package
>>> your code, set a package resource to ensure => latest, then update your
>
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 wrote:
> While trying to build "safety mechanisms" for applying new configuration,
> the aim
On 18 February 2013 23:19, R.I.Pienaar 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 links
> to.
On 18 February 2013 22:47, Drew Blessing wrote:
> You are absolutely fine to continue with your roll out. However, you
> should work the specific ActiveMQ or RabbitMQ connector into that rollout
> if you want to be fully forward-compatible. Ellison posted the link to the
> docs previously.
>
T
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'
> Er
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, se
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 f
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 f
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 unsubscrib
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 wrote:
>
> Hi Gary,
John
Cheers again for the response...
Commented in-line below...
Cheers
Gav
On 18 February 2013 15:08, jcbollinger wrote:
>
>
> On Monday, February 18, 2013 2:13:26 AM UTC-6, Gavin Williams wrote:
>>
>> No-one doing anything similar?
>>
>>
> Puppet is all about managing nodes to a known-in-ad
On Monday, February 18, 2013 2:13:26 AM UTC-6, Gavin Williams wrote:
>
> No-one doing anything similar?
>
>
Puppet is all about managing nodes to a known-in-advance state. You can
encapsulate stateful logic inside 'providers' for custom or built-in
resource types. You also might be able to m
I have a module for windows nodes that is defined like:
class ast_win {
Class['ast_win::env'] ~> Class['ast_win::restart'] -> Class['ast_win']
ast_win::env contains a bunch of scripts that modify the environment on the
host machine. Mostly the PATH variable, but also other variables (e.g.
ht
On Monday, February 18, 2013 1:07:39 AM UTC-6, yarlagadda ramya wrote:
>
> Hi all,
>
> Can we write many classes in a single manifest and apply that manifest??
>
Yes and no. You can write many classes in the same manifest file, but you
cannot leverage their colocation in the same file to assi
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 st
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, Puppe
On Friday, February 15, 2013 5:41:55 PM UTC-6, blalor wrote:
>
> On Feb 15, 2013, at 1:45 PM, jcbollinger >
> wrote:
>
> Curiouser and curiouser. The "1:" is an epoch number, as you probably
> recognize. I was a bit surprised that Puppet would require you to include
> it, but very surprised
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
key3
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 inh
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
- Original Message -
> From: "Drew Blessing"
> 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 this
Bumping - no one knows if its possible or isnt it possible at all?
--
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
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
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
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 manifests
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
On 02/15/2013 01:11 AM, Brian Lalor wrote:
>> Puppet isn't particularly good at code deployment. Ideally, you'd
>> package your code, set a package resource to ensure => latest, then
>> update your package repo with the new code. Then, all the resources
>> that subscribe to that package (services,
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'
30 matches
Mail list logo
