similar to: Help me understand class namespacing

I am running puppet 3.1.1 and have a site.pp which roughly looks like this site.pp: node basenode { include common } node ''server1'' inherits basenode { include role::appserver } node ''server2'' inherits basenode { include role::webserver } And my common module includes lots of different types of classes for creating base directories, adding in

Hi All, I asked on IRC but didn''t have everything organized and most people seemed busy. Hoping someone can see what I''m missing here. I''m trying to create a network module, used similar to the ''users'' configuration described in the Best Practices document. I have a users module which has that and it works with similar syntax to below. If I

hello guys, I am trying to incorporate run stages into my puppet setup. I''ve been working with this for a few days and I haven''t quite got the hang of it yet... When I attempt my puppet run this is the error I see: ------------------------------------------------ [root@chromews21 ~]# puppetd -t err: Could not retrieve catalog from remote server: Error 400 on SERVER:

Yesterday, I switched our node structure from using node basenode, node nodetype inherits basenode, to using node classes per the changes discussed recently on this list and as defined in the wiki:GlossaryOfTerms. In the manifest, we have a syslog module which sets up all the components of syslog-ng we''re using. The ''syslog'' class is used by default on clients and then

I am trying to configure puppet with LDAP repository . I have set puppet schema and I have also added node definition at LDAP. Here is my configuration details . ############################################################## Puppet.conf node_terminus = ldap ldapserver = 10.250.11.127 ldapbase = ou=Hosts,dc=xyz,dc=com ldapassword = secret

hello list.. I am sharing a yum configuration in a class (centos.pp) between two nodes. But the yum configuration doesn''t apply at all to one node even tho it does to another identically configured node. ## packages are failing to install via yum on one ec2 aws instance and another identical ec2 instance works fine [root@kromep2 ~]# cat /etc/redhat-release CentOS release 5.5 (Final)

Hi, I''m having a problem with templates and a remote node. I have a working puppetserver and and puppet client (on the same server) which successfully runs my manifest(s) and now I''m trying to add a new client on a separate server. It all seems to work except for when I try to use templates. For example : file { "/etc/apt/sources.list":

Hello, I am rather new to Puppet and am starting to test it out for use on a client''s servers. I am running into difficulty with node behavior. I want to specify a different firewall for every server. The default "basenode" works (applies the various files/functions/etc to all the servers just fine). However, when I specify the following (see nodes.pp, specifically),

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

I''ve been having a mess of a time using this module, which stinks because its behavior is EXACTLY what I am looking for... whenever I bootstrap new rabbitMQ nodes I want to add them to our HAProxy instance. Here''s my relevant site.pp entries: node /^rabbit.*/ inherits basenode { @@haproxy::balancermember { $fqdn: listening_service => ''messaging00'',

Hello List, i''m running into an issue with puppet where I don''t know how to solve correctly. We''re managing applications and our monitoring (nagios) using puppet using the following schema: class nagios { // ensure nrpe ist installed // export a host definition nagios::check { ''ping'': } nagios::check { ''load'': } ...

I am new to Puppet and very eager to apply it to a project. But I am somewhat stymied by the learning curve. So far I''ve found many very simple examples of how to modify a file or add a user and a very complex example http://reductivelabs.com/trac/puppet/wiki/CompleteConfiguration . I have not been able to find any other examples of a total configuration tree (ie /etc/puppet/*)

Is it possible to define variable at this level. I need to pass the monit config file name ( sometimes its monitrc sometimes in not ). Here is what I have. # /etc/puppet/manifests/nodes.pp node basenode { include postgresql include monit include wiki include apace } node ''freebeerontuesdays.com'' inherits basenode { } -- You received this message because you are

Hi i am creating a template.pp for different OS.. Following is my template.pp file node basenode { case $operatingsystem { fedora: { include fedora } default: { include debian } } include baseapps, sshd, admin, default } <=== line 7 node default inherits basenode {} I receive an error. err: Could not parse for environment production: Syntax error

Hello, Is it possible to group many nodes together? Suppose I have a large number of machines that I all want to have the same config - rather than specify them as individual nodes each inheriting the same config, I''d like to say that a group inherits a config, and define the group elsewhere. Does this sort of construction already exist? Could it be cobbled together from what we

I had installed puppet master and client on two different machines. machine A has puppet master and machine B has client. both are centos6 64 bit machines. Machine B (client) is successfully connected to master (machine A). My aim is to install New Relic agent (server monitorinig tool) on different clients. I had installed new relic agent on machine A and trying to build a module so that I

I just upgraded to 0.22.0 from 0.18.4 and I''m running into what I think are problems due to changes in scope rules. In my site.pp manifest, I have the following: import "classes/*" node nfsserver { include nfsserver } node webserver { include webserver } class cluster1_sites { website { "example.com": ...; "example2.com": ...; } } node

Hi, I am trying to allow certain nodes to override variables in inherited classes. Here''s an example: node ''my.server.com'' inherits webserver {} node ''other.server.com'' inherits webserver { $var = "newvalue" } node webserver { $var = "value" include snmp, dns, classx } In this example classx ends up using

I am trying to override variables in a class that is defined in the default node profile. I want parent class to be included in every single node, but override its variables in others. I have tried it several different ways now, and every single time the variables either become unset (undefined) or are set to the value of the first if statement. Here is my current iteration of failure.

OS: FreeBSD 6.2-RELEASE Puppet: 0.22.4 OS: CentOS 5.0 Puppet: 0.23.2 Is it currently not possible for puppetd to upgrade itself (0.22.4 -> 0.23.2)? I tried it, and when puppetd attempted to restart itself (using the init provider), it failed to start back up. Perhaps the init provider needs to close all file handles before executing the rc.d scripts? Additionally, I had puppetd update its