"russell.fulton" writes:
> I have a class in a file monitor/manifest/masters/dmzo:
[...]
> and I get the error:
> "Could not find value for 'rule_categories' at /etc/puppet/modules/
> monitor/manifests/init.pp:62"
>
> I have tried qualifying the name by prefixing it with dmzo:: and dmzo. then
I have a class in a file monitor/manifest/masters/dmzo:
class dmzo {
$rule_categories = [
scan,finger,ftp,telnet,rpc,rservices,ddos,dns,tftp,web-
coldfusion,misc,web-php,
]
}
and probably other variables eventually...
In my monitor/manifest/init.pp:
module monitor {
impor
I have worked my way around this one:
empirical evidence suggest that one can use variable in include but
not import. This makes some sort of sense.
So I now
import "master/*.pp"
include $master
This leads to another problem but I'll post it to a thread of its
own...
Russell
--
You received
I'm a newbie in Puppet.
I had googled for a while,
I just wonder if those work ? (syntax below)
packe
{
provider => "yum"
allowcdrom => true
"python*":
ensure => installed;
"mysql*":
ensure => installed;
}
please help!
thanks!
--
You received this messa
On Sat, Nov 20, 2010 at 11:01 PM, Jay Adkisson wrote:
> FWIW, it's probably better performance-wise to do the string manipulations
> in Ruby rather than shelling out to bash.
>
> Facter.add "lokatie" do
> setcode do
> case Facter.value(:ipaddress).split('.')[1]
> when '84': 'AAA'
>
On Nov 21, 7:55 am, Nick wrote:
> A problem I've run into during my first attempts at writing manifests, is
> knowing what possible facts are available, and for a given fact, what values
> my
> manifest might encounter.
I use 'default' matches liberally. For required values I throw an
error or w
On Tue, Nov 16, 2010 at 01:49:41AM +0100, Stefan Schulte wrote:
> You should file a bug about the sshkey type not raising an Error if you
> define a resourcename with "," in it.
>
> -Stefan
Just for the record: The issue has already been reported:
http://projects.puppetlabs.com/issues/2495
pgpE
Still on my sensor management project ;)
I have a parameterised define (sensor) within a class monitor:
class monitor {
import "masters/*.pp" # class for each sensor master
define sensor( $master, .)
# and I want to include a class whose name is give by $master.
include $ma
On Sun, Nov 21, 2010 at 6:15 PM, Markus Falb wrote:
> On 18.11.10 21:17, CraftyTech wrote:
> > Hello All,
> >
> > Is there a way of suppressing DEPRECATION WARNINGS? Ever since I
> > upgraded rails, I keep on getting deprecation warnings that I run
> > puppetd. Is there any way of turning
On 18.11.10 21:17, CraftyTech wrote:
> Hello All,
>
> Is there a way of suppressing DEPRECATION WARNINGS? Ever since I
> upgraded rails, I keep on getting deprecation warnings that I run
> puppetd. Is there any way of turning these off? i.e,
>
> ruby --version
> ruby 1.8.6 (2007-09-24 pat
Hi,
A problem I've run into during my first attempts at writing manifests, is
knowing what possible facts are available, and for a given fact, what values my
manifest might encounter.
A classic one is the possible values of $operatingsystem, but it applies to all
sorts of facts.
Of course, I kno
11 matches
Mail list logo
