similar to: Why no hostgroups parameter for nagios_host types?

I''ve tried to achieve my overall goals with several different features of Puppet, but I''ve hit a bit of a wall here. I think it''s time for me to explain what I''m trying to accomplish: I want the enabling of a service in my manifests to configure the monitoring of that service by a nagios server, without needless repetition. Let me explain how my

I am trying to create a hostgroup using the Foreman API (foreman-0.4-0.1rc1.noarch): Using perl v.5.14.2, REST::Client et. al., ending up with sending: POST /hostgroups {"name":"api-created-

I''m trying to generate (and manage) nagios configuration based on what classes have been included by nodes. I''ve seen the example at http://docs.puppetlabs.com/guides/exported_resources.html, and I''m doing that now. However, it has some problems: - puppet runs are very slow on the nagios node - when I want to change the service configuration in nagios, I have to wait

Running puppet 2.6.11 opensource on Red Hat 5.6 client. I cannot explain this logically but I have a directory structure like so: /etc/puppet/manifests/hiera/hostgroups/ with directories for each of my application areas like so: *clickz core devel dns icross iswap itch puppet test ubuntu* *What is weird is that if I put anything under the directory named "core", the ext

I am trying to supplement and ultimately provide a patch for ''foreman'' which is an adjunct to puppet. Essentially, there is a Hosts class which belongs_to Hostgroup and Hostgroup class has a column called ''ancestry'' which is actually a Hostgroup (probably what is referred to as STI but I am not sure) and thus within Foreman, nesting Hostgroups is not uncommon.

Hi everyone, I am reconsidering how I am using the Puppet nagios functionality, at the moment I am creating one service for each check on each host. A lot of them are identical, and would be better tied to hostgroups to simplify my config. Namely, I have about 5,000 checks in there now which will go up to about 20K over the next month, and it''s taking about 5-10 minutes for a Puppet

Hi, I''m having a problem with extlookup not respecting the ''certname'' parameter[1].  When executing a puppet run with either the --certname or --fqdn parameters, it ends up using the specified SSL certificate and gets the correct node definition applied from the puppetmaster.  However, it still retrieves extlookup data using the node''s actual FQDN, not the one

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,

I''ve been using foreman as an ENC and assigning node parameters for some time and it was clearly working but it apparently broke somewhere along the way and I can''t tell why. Here''s part of the modules/sudoers/manifests/sudoers_hostgroup.pp class sudoers::hostgroup { case hostgroup { default: { file{"/etc/sudoers.d/admins_web": ensure

Hi all . i am running puppet version 2.6.16 and foreman Version 0.4.2 . my question is as follows . i would like to know if there is a way to tag server with a group tagging . for example . let say i am running apache with a unique configuration and network architecture and want to tag in with "tag1" and a i have few more apache installation with the a new unique configuration and

On Oct 25, 2011, at 3:17 PM, Pawel Wodnicki wrote: > Chris, > >> FYI, I completely agree that we shouldn't remove the sparc target. However, it is currently unmaintained, and has some pretty glaring bugs. Is anyone interested in stepping up to maintain the target? >> >> -Chris > > We can not let it die and I volunteer to keep the Sparc alive! > > My

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I''me using nagios builtin types and I''m very surprised that the parameter *name* is not available for type nagios_host ?!? This parameter is required to use inheritance (http://nagios.sourceforge.net/docs/3_0/objectinheritance.html) and I don''t understand why it is not included in all nagios types ? Maybe someone has

Hello! What does this error means? err: Could not retrieve catalog from remote server: Could not intern from pson: Could not convert from pson: Could not find relationship target "Nagios_hostgroup[]" I cannot find it anywhere in my config... I have only 2 nagios_hostgroups, exported to server, then collected in nagios module. Any ideas? Cheers --- Grzegorz Marszałek

Hi folks, For the first time since I started playing with puppet I started down the road of using exported resources This was inspired by my reading all of the nagios related recipes that went something along the lines of class nagios { package {nagios: ensure=> latest } service {nagios : ensure => running , enable => true} Nagios_host <<! !>>

I am using stored configs to manage my nagios host and services checks and I have run into a problem that I have been unable to solve. When the stored configs are purged from puppet the nagios server correctly removes them from the services and hosts file but does not notify the nagios service and instead throws an error. So the entries are still there and nagios still reports on them until

Hi, Since the below is a little long, I put my question at the top: how do I troubleshoot awful exported resources performance in puppet and is there anything I can tweak to get it to run under 10 minutes in larger environments? I have a fairly modest environment (118 nodes, but prod will be at least twice as large). I''m trying to move my distributed nagios setup to one based on

Chris, > FYI, I completely agree that we shouldn't remove the sparc target. However, it is currently unmaintained, and has some pretty glaring bugs. Is anyone interested in stepping up to maintain the target? > > -Chris We can not let it die and I volunteer to keep the Sparc alive! My SPARCstation pizzaboxes can be ready for action in a day or two. Pawel Wodnicki > On Oct

We were using Naginator resources like nagios_host, etc. along with stored configurations and exported resources. Worked pretty well. However we have to separate the Puppet master and the Icinga (Nagios) server. They will be on different machines from now on. Are there any best practices for such a scenario? I already thought about some kind of ''rsync'' of the configuration from

Hi folks, I noticed an interesting problem with the nagios_* providers especially in Debian. Besides writing to the wrong file (I fixed that issue) I''ve noticed there is a umask issue where the config files end up being owned by root with perms 0640. This causes nagios to spit milk out of its nose because it cannot read the configuration files. I came up with a kludgey solution to the

On 30/01/2020 12:53, Michael Str?der wrote: > On 1/30/20 1:27 PM, Brian Candler wrote: >> I am trying to work out the best way to issue SSH certificates in such >> way that they only allow access to specific usernames*and* only to >> specific groups of host. > I also thought about this for a while. The only idea I came up with is > to have separate CAs used as trust