On Tuesday, March 4, 2014 9:56:33 AM UTC-6, Jose Luis Ledesma wrote:
On Tue, Mar 4, 2014 at 3:36 PM, jcbollinger
john.bo...@stjude.orgjavascript:
wrote:
On Tuesday, March 4, 2014 1:30:44 AM UTC-6, Jose Luis Ledesma wrote:
Although it is not incorrect, you should not bypass class
Well, it is not an unbreakable rule, but from my point referencing
individual resources from another class is a source of possible future
problems.
In a simple module like the OP seems to expose, that is:
Params
Config
Install
Service
If you reference individual resources from another class
On Tuesday, March 4, 2014 1:30:44 AM UTC-6, Jose Luis Ledesma wrote:
Although it is not incorrect, you should not bypass class boundaries, so
it's better:
require=Class['munin::install']
Well, that's one school of thought. Personally, I don't have any problem
with cross-class
Hey guys,
I've actually found the problem. It turns out that I thought I had defined
the munin-node package definition in my install.pp (munin::install)
manifest. Turns out I only had defined the munin package which takes care
of all the dependencies for it.
Here's my main class in init.pp:
On Tue, Mar 4, 2014 at 3:36 PM, jcbollinger john.bollin...@stjude.orgwrote:
On Tuesday, March 4, 2014 1:30:44 AM UTC-6, Jose Luis Ledesma wrote:
Although it is not incorrect, you should not bypass class boundaries, so
it's better:
require=Class['munin::install']
Well, that's one school
Hey all,
I notice with the munin module I wrote, the munin-node service won't start
on the first puppet run. Run it a second time, and the service starts no
problem.
The problem here I believe is that puppet is attempting to start the
service before the package is installed.
So I tried to
On Mon, 2014-03-03 at 21:07 -0500, Tim Dunphy wrote:
Error: Failed to apply catalog: Could not find dependency
Package[munin-node] for Service[munin-node]
at /etc/puppet/environments/production/modules/munin/manifests/service.pp:8
Looks to me like puppet isn't finding the declaration for
Although it is not incorrect, you should not bypass class boundaries, so
it's better:
require=Class['munin::install']
And usually you may include the diferent classes for a module in init.pp
chaining them there.
Regards,
El 04/03/2014 03:07, Tim Dunphy bluethu...@gmail.com escribió:
Hey all,
