similar to: Node behavior

Hi, I have several Debian servers with puppet 0.23.2. Part of my manifest looks like this: class virt_all_users { @group { "andy": ensure => "present", gid => "1000" } @user { "andy": ensure => "present", uid => "1000",

Hi all, I''d got the impression that puppet didn''t care about ordering - ie. the ordering of imports and includes related to calling them in the manifest. Lately I''ve had big trouble getting puppet to accept that I require some resource that I _have_ defined elsewhere in the manifest. To explain it, here is a simplified example: site.pp: -------- import

I asked on IRC but no one responded. Suppose the following: class basenode { include users include security class webserver { include apache, php } } node web1a { include basenode::webserver } Does node web1a imply including users and security specified under class basenode as well? Similarly, does this mean the same thing? class basenode { include users include security }

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

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 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:

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

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

Hi, Just a quick query about some things that crop up when I run ''puppetd --test''. Every time I run this command I always see the following output, which I think is strange as the ''man'' package has been installed previously and the firewall service is definitely running. Has anybody got any suggestions as to why puppet thinks it needs to install the man

Still very new to puppet, so go easy :-) Bit of a braindump I''m afraid, but I''d really appreciate any "Yep", "interesting", "No!!!" comments. I''ll start with an example - adding NTP support. This primarily consists of two configs: a) NTP clients - this is quite easy, it''s a templated file requiring the names of the NTP

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

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''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'',

I managed to build a reduced test case: ================== foo.m ================== #include <Foundation/Foundation.h> @interface BaseNode : NSObject <NSCoding, NSCopying> { } @end @implementation BaseNode @end int main(int argc, char **argv) { return 0; } ========================================== # clang -o foo -arch i386 -framework Foundation foo.m foo.m:8:1: warning:

Hi, I am getting the following error on my CentOS clients; err: Could not run Puppet configuration client: Invalid parameter stage at /etc/puppet/manifests/nodes.pp:32 The server is CentOS 5.4 with packages from the epel-puppet repos; # rpm -qa | grep puppet puppet-dashboard-1.0.3-3 puppet-2.6.1-0.3.rc3.el5 puppet-server-2.6.1-0.3.rc3.el5 The clients are; # rpm -qa | grep puppet

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

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 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 all, I''m a new puppet user and I''m running into some weirdness around creating users on solaris. (puppet version 0.23.2) The virt_all_users way of managing users seems pretty reasonable, but I don''t see how to deal with user specific groups with that. I have: class virt_all_users { @user { "seph": ensure => "present",

Trying to setup a sandbox environment, and I''m running into some issues. When I run the system in --noop mode, everything works as it should (long list of options truncated to ...): [root@kvm001 ~]# puppetd ... --noop info: Caching catalog at /var/lib/puppet/localconfig.yaml notice: Starting catalog run notice: //dev_server/basenode/role_general/ntpd/File[/etc/localtime]/ensure: is