On Fri, May 6, 2011 at 4:47 PM, Christopher Lee <chr...@spiralweb.com>wrote:
> Hello, > > I am playing with Puppet Dashboard and I have a few questions. > > First, as we start using puppet we are planning on running puppet agent > from cron or via mcollective runs in --noop mode every few hours as an > audit function. If anything is changed we would like to have it show up in > Puppet Dashboard so we can alarm on it and then manually find out why it was > changed before reverting back. I noticed dashboard only reports "green" > good run, no errors or "yellow" changes where made. If I run in noop it > returns green because no changes where made but I would like to see it tell > me changes needed to be made but where not. Does this make since? Is there > away to get this functionality? > Chris, we're actually working on this exact issue in the next few days, showing "Pending" changes in a much more obvious manner with noop/simulation runs. We'll have this ready within the next two Dashboard point releases. > > Second, we have two data centers and two puppet masters. I would like to > run one dashboard. I can see from reporting this not to be a big deal but > if I start using dashboard as an external node provider will I have issues. > Looking at the settings.yml file for dashboard the setting seem to be very > specific to one master. Am I going to start running into issue trying to > use one dashboard with two puppetmaster (more more in the future). > As far as an external node classifier goes, you really shouldn't have problems with multiple masters, both configured to use Dashboard as their ENC. -- Nigel Kersten Product, Puppet Labs @nigelkersten -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
