similar to: Duplicate class declaration because of counterintuitive class scoping

I have these three modules with the following structure: |-- modules | |-- create_resources | | |-- LICENSE | | |-- Modulefile | | |-- README | | |-- lib | | | `-- puppet | | | `-- parser | | | `-- functions | | | `-- create_resources.rb | | |-- spec | | | |-- spec.opts | | | |-- spec_helper.rb | | | `-- unit

Hi everyone, Here are the manifest I am using: In file ''*modules/test/manifest/init.pp*'': class test ( $test = undef, ) { notice("Here is the message: ${test}") } Now in ''*modules/saas/manifests/client/sudo.pp*'': class saas::client::sudo { class { ''test'': } } Now in ''*manifests/sites.pp*'': import

I want to have a parametrized class with lookup from params.pp but I keep getting into problems. init.pp: class foo ( $bar = $foo::params::bar, $foofoo = $foo::params::foofoo ) inherits foo::params { file {''/tmp/foobar'': content => template("foo/foobar.erb"), } } params: class foo::params { $bar = true if $foo::bar { $foobar =

Hi, My dilemma is how should I write my module to be "next-gen" ? Not from a code point of view but from a design/layout point of view. We wrote our modules for 2.6.x like every beginner would have done: write everything in init.pp. But now, the fashion is to use parameterized classes and Hiera which we will use with puppet 2.7.x. I mainly followed/watched what Example42 was doing.

Well, I''m suddenly confused. I''m getting this error... Dec 3 15:55:37 gumby puppetd[15606]: Configuration could not be instantiated: Could not find dependency Class[java::jdk] for Package[tf-tomcat-starterkit-tfel0] at /etc/puppet/modules/tomcat/manifests/init.pp:19 I can''t see why.The aforementioned line 19 in tomcat/manifests/init.pp is the line containing

I am using puppet 2.6.11 and want to pass parameter for implementing sudo for mulitple users. So here is my simple code, which I would like to pass to hiera to specify user name lookup. Appreciate any help, thanks in advance. class sudo( $name) { #Class:: sudo # # package { "sudo": ensure => present, } file { "/etc/sudoers": owner => root, group => root,

Hi All, I have been searching around for a few hours now, but don''t seem to be using the correct search terms for the answer I need. So please forgive me if this is a question that has been answered 100 times :( I have seen many questions regarding enviroment variables, but non seem to be related. Again, I may be misunderstanding the vocabulary) I am setting up

I can''t work this out and I''m getting frustrated. :( Puppet is complaining: err: Failed to apply catalog: Could not find dependency Lvm::Volume_group[bcvg] for Lvm::Application_volume[cache] at /truth/sauce/env/prod/modules/object_store/manifests/server.pp:47 Yet, if I comment out that line so that puppet runs ok, and then look at the state.yml file on the client, I see:

Hi List, Puppet Version: v2.7.13 Question - If I correctly setup multiple manifestdir''s in the puppet.conf file how can I import a node pp file located in a different directory tree to site.pp? My configuration information is below. In my puppet.conf file I have setup an environment called "stable", within this environment I have setup the manifestdir, modulepath and

Hi there, I''m running into an problem which I can resolve. It is bugging me for couple of days now. Goal: CentOS 6.4 freshly installed incl puppet 3.2.3 and I want to install puppet master, puppetdb, mod_passenger & apache with "puppet apply". So when this is complete, I should have an puppet master server running so I can create new hosts etc. So this is the command

So I''m trying to get multiple environments to work with puppet 0.25.1 on ubuntu 8.04 and no matter what I do, puppet just completely ignores any environment setting. There''s really next to no information in terms of configuration on the multiple environments documentation page (http://reductivelabs.com/trac/puppet/wiki/UsingMultipleEnvironments) other than saying that the

Hi, I am new to puppet and have started evaluating various features in last few days. I am not a developer and am mostly going to use the modules available on github or puppet forge. Currently I have tried all easier modules and they seem to work perfectly without any issues, but now the problem is arising when I am trying to use modules like mysql, tomcat etc... For mysql I am using the module

I''ve gotten an install of solr working, but it''s pretty much a hack job at the moment. If y''all could give me your thoughts on how to improve my setup, I''d appreciate it. apache-tomcat is an rpm of Tomcat 7 that references the oracle jdk instead of openjdk. Thanks. class solr { service { ''iptables'' : ensure =>

Dear puppet wizards, http://docs.puppetlabs.com/puppet/3/reference/lang_defined_types.html does not suggest to me that nested parametrized defines would be forbidden, hence I expected the following code to work: add_to_ssh_authorized_keys.pp: -------- define a::ssh_keys::add_to_ssh_authorized_keys($homebasedir="/home", $targetuser="root", $keyowner, $keyownername,

Hello, I''m configuring my linux server with puppet open and is ok. My question is the next; I''ve a declared in mi nodes.pp the next: [.............] node ''basenode'' { include ''baseos'' include ''motd'' import ''useradd.pp'' } #All nodes for my domain node /.*\.example\.com/ inherits

In general, the loading/import/namespacing mechanism is really something that I cannot wrap my head around, even after reading the relevant sections in the documentation. Specifically, I''m trying to put together a module. I believe I have the correct module structure: $ find . ./test.pp ./graphite ./graphite/manifests ./graphite/manifests/init.pp ./graphite/files

Hi, We''ve been using puppet for a couple of months now (started with a new deployment for a customer, and it''s slowly taking over their whole environment). We''re gradually getting our heads around it, but there are some things that we''re hoping other people have encountered and solved before us. First one is to do with scoping... We have defined some

Hi guys I have a small question, I have 3 environments in puppet.conf file: [development] modulepath=/etc/puppet/development/modules manifests=/etc/puppet/development/manifests/site.pp I have defined the site.pp path, my question is do I need to make a nodes.pp for every environment?????? Thanks -- You received this message because you are subscribed to the Google Groups "Puppet

I''m trying to try out puppet and can''t seem to get to square one. I''ve been using cfengine for years and have just upgraded about 80 Debian machines to etch and wanted to try puppet. So, I have two Debian ''etch'' machines one a server and the other a client. I''m running puppet 0.23.2 installed from the unstable packages. As a first step

I know this comes up periodically, and I''ve read through the wiki (including the Best Practices page) & list archives, but still can''t quite get my head around it. I see lots of references to /modules and $MODULE_PATH, but am not sure what these refer to. Here''s a basic setup I have. Let me know if this looks correct: /etc/puppet/ |-- autosign.conf |--