I have solved it as below with a wrapper to the zabbix module:
class common::zabbix {
contain zabbix::agent
Class['common::repos'] -> Class['common::zabbix']
}
and then in selected yaml environments
## YAML
---
classes:
- common
- ntp
- common::zabbix
El viernes, 17 de abril de 2
Hrm, well, with your help, I got this to work in the order I was expecting.
I think I had a few problems here.
1. My original ordering was:
File['Config'] -> Exec['stop'] -> Package['foo'] -> Exec['start']
I changed this to:
File['Config'] ~> Exec['stop'] -> Package['foo'] ~> Exec['start']
On Friday, September 19, 2014 12:59:34 PM UTC-5, Jake Lundberg wrote:
>
> Puppet 3.6.2
>
> First, I understand that Execs try not to run multiple times if called
> many times by many resources and typically wait until they've all been
> "collected" from all resources
>
Not exactly. Execs run
On Monday, December 16, 2013 10:38:27 AM UTC-6, Joseph Swick wrote:
>
> On 12/16/2013 10:59 AM, jcbollinger wrote:
> >
> >
> > On Friday, December 13, 2013 3:56:50 PM UTC-6, Joseph Swick wrote:
> >
> > [...]
> >
> > What am I missing to get Puppet to evaluate the $resourceX_type
> >> vari
On 12/16/2013 10:59 AM, jcbollinger wrote:
>
>
> On Friday, December 13, 2013 3:56:50 PM UTC-6, Joseph Swick wrote:
>
> [...]
>
> What am I missing to get Puppet to evaluate the $resourceX_type
>> variables as a resource type [e.g: File, Service, etc.] to get this to
>> work?
>
>
>
> Puppe
On Friday, December 13, 2013 3:56:50 PM UTC-6, Joseph Swick wrote:
[...]
What am I missing to get Puppet to evaluate the $resourceX_type
> variables as a resource type [e.g: File, Service, etc.] to get this to
> work?
Puppet DSL does not provide such a feature. It is conceivable -- likely
After all that, it looks like the function was doing exactly what it was
designed to... Filtering out irrelevant data...
However feeding it incorrect filters meant that it was filtering
everything... Doh...
Cheers
Gavin
On Thursday, 31 January 2013 22:37:30 UTC, jcbollinger wrote:
>
>
>
> O
On Thursday, January 31, 2013 11:52:41 AM UTC-6, Gavin Williams wrote:
>
> Afternoon all
>
> I'm sure this is probably a nice n easy one, but I can't work it out for
> the life of me...
>
> Anyhow, I've got the following code:
> # Load db yaml data
> $db_details = loadyaml('/etc/puppet/data
For the most part, execs is it, but sometimes you might use it for a
file or for a custom type.
I suppose that it could be built into each type as necessary with just
as much effectiveness.
In this case though, we might want to set up logging for the exec only
on specific failure states.
I.e. 2
On Wed, Jul 22, 2009 at 5:03 AM, Trevor Vaughan wrote:
>
> I was thinking of this in a very fine grained way, such as a metaparameter.
>
> The situation that made me think of this is:
>
> class foo {
> file { 'super/important':
> ensure => 'file',
> content => 'something great\n'
> }
>
>
It's not semi-satisfied in cases where you might be waiting for
cross-system semaphores to complete and you don't want to fire
anything else off until they are.
Trevor
> On Wed, Jul 22, 2009 at 08:26, Peter Meier wrote:
>> Hi
>>
>>> [discussion about soft failing]
>>
>> hmm I don't see why you'd
Hi
> [discussion about soft failing]
hmm I don't see why you'd like to have your environment in a
semi-satisfied state. Either your environment is in the state is
broken or you have to fix it. Everything else is imho just scary...
cheers pete
--~--~-~--~~~---~--
I was thinking of this in a very fine grained way, such as a metaparameter.
The situation that made me think of this is:
class foo {
file { 'super/important':
ensure => 'file',
content => 'something great\n'
}
exec { 'nice to have happen':
command => 'check stuff and set a fil
Luke Kanies wrote:
> On Jul 21, 2009, at 5:31 PM, Trevor Vaughan wrote:
>> Is there any way to make some things fail softly so that they can be
>> less hard than class-wise fatal?
>
> Hmm, no one's ever asked before.
>
> It seems reasonable that we could mark some resources as non-fatal,
> but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luke Kanies wrote:
> Is there any way to make some things fail softly so that they can be
> less hard than class-wise fatal?
>
>> Hmm, no one's ever asked before.
>
>> It seems reasonable that we could mark some resources as non-fatal,
>> but what
On Jul 21, 2009, at 5:31 PM, Trevor Vaughan wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> This is going to be a great feature.
>
> Over time, I've been struggling with trying to keep things extremely
> modular (perhaps too much so) but still well ordered.
>
> When I can make ever
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is going to be a great feature.
Over time, I've been struggling with trying to keep things extremely
modular (perhaps too much so) but still well ordered.
When I can make every class that needs apache just 'require apache', I
will be quite happ
On Jul 17, 2009, at 6:08 AM, Burkholder, Peter wrote:
>
> I just finished listening to the Configuration Management panel from
> OSBridge (on blip.tv).
>
> Near the end of it, Adam Jacob states that Puppet's resource
> dependency
> ordering is non-deterministic,
> and that manifests that work f
Burkholder, Peter wrote:
> I just finished listening to the Configuration Management panel from
> OSBridge (on blip.tv).
>
> Near the end of it, Adam Jacob states that Puppet's resource dependency
> ordering is non-deterministic,
> and that manifests that work fine 19 times will fail the 20th tim
I'm not biased and I also agree with Paul and James.
While I have had trouble with getting my order right in some cases, it
was generally a failing of the item that I was trying to configure
*not* a problem with Puppet.
It comes down to ordering something in a file implicitly or explicitly
and I
Paul Lathrop wrote:
>> Is this true? I'm puzzled that what Luke considers one of Puppet's
>> strong suits is derided by
>> others as its Achille's heel.
>
> This is true w/o being the whole story. Puppet obeys declared
> dependencies, but if you choose not to declare your dependencies, you
> are
On Fri, Jul 17, 2009 at 6:08 AM, Burkholder, Peter wrote:
>
> I just finished listening to the Configuration Management panel from
> OSBridge (on blip.tv).
>
> Near the end of it, Adam Jacob states that Puppet's resource dependency
> ordering is non-deterministic,
> and that manifests that work fi
2009/7/17 Burkholder, Peter
>
> I just finished listening to the Configuration Management panel from
> OSBridge (on blip.tv).
>
> Near the end of it, Adam Jacob states that Puppet's resource dependency
> ordering is non-deterministic,
> and that manifests that work fine 19 times will fail the 20t
Burkholder, Peter wrote:
> I just finished listening to the Configuration Management panel from
> OSBridge (on blip.tv).
>
> Near the end of it, Adam Jacob states that Puppet's resource dependency
> ordering is non-deterministic,
> and that manifests that work fine 19 times will fail the 20th ti
Perhaps if you didn't declare the dependencies accurately, some
orderings would work and some orderings would fail. Seems no
different to a declarative build tool in that respect.
Julian.
2009/7/17 Burkholder, Peter :
>
> I just finished listening to the Configuration Management panel from
25 matches
Mail list logo
