Hi, I must be missing an essential piece here.
All three of your puppet stack nodes must be present in each instance, no? The production master manages all three masters, normally. To change monitoring of either of them, you update the production manifests. Of course, if you implement some new monitoring feature on the dev master, you must have that node run puppet against its local dev master to export resources, then the nagios server also against the dev master to import them. But that is just the usual dev workflow, I assume. So I suspect things aren't so simple for you. I just don't see in what manner. Thanks in advance for any clarification, Felix On 12/03/2013 02:39 AM, Jason Antman wrote: > Hello, > > I have 3 puppet stacks (master, puppetdb, enc) - dev, test/qa and prod. > Dev is used for initial development and testing of code (including > puppet), which is then promoted to test and then prod. > > I'd like to start using the nagios types to configure monitoring, via > exported resources (yes I'm aware of the issues with the builtins, but > they'll have to do for now). I only have one Nagios server, and I'd like > to reliably monitor at least some stuff on the dev and test puppet > nodes. So... setting up all 3 puppet stacks to export resources that are > realized somehow on the Nagios server isn't a possibility, as bad > manifests/modules could affect the monitoring of one of the dev or test > hosts. > > What's the safe way to "freeze" exported resources, or prevent them from > being changed? The best that I can come up with so far is to have the > nagios server connected to the production puppetmaster, and when I want > to update the (exported resource) monitoring configuration for one of > the dev or test nodes, have to do a one-time run on each node in > question against the prod puppet master. > > Any other thoughts or theories? > > Thanks, > Jason Antman -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/529F2CA4.2040203%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/groups/opt_out.
