Thanks John, the "if has_variable" was the key and allowed me to
remove the default variable definition.
If anyone is interested I posted an explanation and link to the source
here, http://itscblog.tamu.edu/managing-zabbix-agents-with-puppet/.
Thanks
- Trey
On Jun 6, 8:38 am, jcbollinger wrote
Hi,
On 06/08/2011 10:40 PM, Toby wrote:
> Hello all, sort of a puppet newbie here,
>
> I have some constructs that are like so:
>
> class hosts {
>file {"/etc/hosts":
> owner => root,
> group => root,
> mode => 644,
> source => ["puppet://puppet/files/etc/hosts.$h
On Wed, Jun 08, 2011 at 05:50:58PM -0700, Josh Cooper wrote:
> It'd be great to hear about your experience with the pre/post run
> commands and what use cases you are trying to solve.
We use the feature to generate additional information about how the
puppet run has changed the system:
http://w
Thank you all for the quick responses I really do appreciate it, you
guys are awesome!!!
On Jun 8, 5:38 pm, Nigel Kersten wrote:
> On Wed, Jun 8, 2011 at 2:38 PM, Nigel Kersten wrote:
>
> > On Wed, Jun 8, 2011 at 2:11 PM, Denmat wrote:
>
> >> Hi,
>
> >> If your password hash has any $ in it the
On Thu, Jun 9, 2011 at 3:15 AM, Dean Wilson wrote:
> On Wed, Jun 08, 2011 at 05:50:58PM -0700, Josh Cooper wrote:
>
> > It'd be great to hear about your experience with the pre/post run
> > commands and what use cases you are trying to solve.
>
> We use the feature to generate additional informat
Hi Josh,
This might be out of scope of your bug fix, but why not make the
behaviour configurable? If prerun/postrun fails, give people the
option of continuing or dying.
prerun_command = /bin/meow
prerun_failure_fatal = true
> It'd be great to hear about your experience with the pre/post run
> c
On Jun 9, 1:33 am, Sirtaj Singh Kang wrote:
> On 08-Jun-11, at 9:31 PM, Brian Gallew wrote:
> [snip]
>
>
>
> > See, there's the crux of the issue: arrays are *not* a method of
> > looping. Puppet's DSL is declarative, not procedural (imperative).
>
> This isn't precisely true - every pure fun
On Thu, Jun 9, 2011 at 7:04 AM, Luke Bigum wrote:
> Hi Josh,
>
> This might be out of scope of your bug fix, but why not make the
> behaviour configurable? If prerun/postrun fails, give people the
> option of continuing or dying.
>
> prerun_command = /bin/meow
> prerun_failure_fatal = true
>
You
Hi all,
I haven't used exported resources before, and I'm finding it a little
confusing.
Basically I want Puppet to know which of the servers have the DNS
servers class applied to them, so it can use these servers' IP addresses
when it generates the DHCP config.
This way, if we add or remo
On Thu, Jun 9, 2011 at 5:40 PM, Jonathan Gazeley <
jonathan.gaze...@bristol.ac.uk> wrote:
> Hi all,
>
> I haven't used exported resources before, and I'm finding it a little
> confusing.
>
> Basically I want Puppet to know which of the servers have the DNS servers
> class applied to them, so it ca
Hello.
I'd like to enhance the classical package/configuration/service pattern
with an additional stage: configuration syntax checking. The goal is to
ensure a service won't be restarted with an invalid configuration first,
but also to ensure this configuration error will get explicitly
notified,
Part of the challenge is that I haven't seen a generally accepted language
that succinctly describes what arrays do. If I had it to say again I would
have said arrays are Puppet's only available declarative multiplier.
On Thu, Jun 9, 2011 at 7:21 AM, jcbollinger wrote:
>
>
> On Jun 9, 1:33 am, S
(apologies for the derail)
On 09-Jun-11, at 7:51 PM, jcbollinger wrote:
[snip]
On Jun 9, 1:33 am, Sirtaj Singh Kang wrote:
On 08-Jun-11, at 9:31 PM, Brian Gallew wrote:
[snip]
See, there's the crux of the issue: arrays are *not* a method of
looping. Puppet's DSL is declarative, not procedur
On Thu, Jun 9, 2011 at 07:40, Jonathan Gazeley
wrote:
> I haven't used exported resources before, and I'm finding it a little
> confusing.
>
> Basically I want Puppet to know which of the servers have the DNS servers
> class applied to them, so it can use these servers' IP addresses when it
> gen
> One use of pre commands that isn't solved with stages is to check "Should I
> even do a Puppet run right now?" or anything else that is out of band in a
> similar sense.
This makes complete sense and is how the feature was intended to work,
but unfortunately, it never has worked that way (for th
On Thu, Jun 9, 2011 at 1:22 PM, Josh Cooper wrote:
> > One use of pre commands that isn't solved with stages is to check "Should
> I
> > even do a Puppet run right now?" or anything else that is out of band in
> a
> > similar sense.
>
> This makes complete sense and is how the feature was intende
On Wed, May 4, 2011 at 2:20 PM, treydock wrote:
> In my puppet-dashboard when a change is made to files and it shows the
> MD5 sums I am never presented a link to view the file or any diffs of
> those files. I assume that the text between '[' and ']' is supposed
> to be the link but it's just pl
On Thu, Jun 9, 2011 at 3:28 PM, Nigel Kersten wrote:
>
>
> On Wed, May 4, 2011 at 2:20 PM, treydock wrote:
>
>> In my puppet-dashboard when a change is made to files and it shows the
>> MD5 sums I am never presented a link to view the file or any diffs of
>> those files. I assume that the text
https://projects.puppetlabs.com/issues/7697
One problem people producing modules that make use of stages are hitting is
that it's difficult to create something reusable that integrates seamlessly
into existing setups.
This feature request is to add several more implicit stages to Puppet so we
hav
On Thu, 09 Jun 2011 18:42:54 -0700, Nigel Kersten wrote:
>
> https://projects.puppetlabs.com/issues/7697
>
> One problem people producing modules that make use of stages are hitting is
> that it's difficult to create something reusable that integrates seamlessly
> into existing setups.
>
> This
A while back I wrote down all the puppet patterns
I could think of, and this was one of them.
I named it Cradle To Grave, but probably that's not
appropriate. However, I was only focusing on
puppet runs at the time, so that name popped into my head.
It is an instance of the more general pattern
I prefer having a small number of predefined stages in puppet.
This makes it easier to share modules which use stages.
My suggestion:
- a small number of stages is easier to remeber
- a samll numer of possibilities makes people think in advance in which
stage they need to put their module
Additio
On 10 June 2011 02:50, Jacob Helwig wrote:
> On Thu, 09 Jun 2011 18:42:54 -0700, Nigel Kersten wrote:
> >
> > https://projects.puppetlabs.com/issues/7697
> >
> > One problem people producing modules that make use of stages are hitting
> is
> > that it's difficult to create something reusable that
23 matches
Mail list logo
