puppet-dashboard - connection to existing puppet environment
tomholl
puppet server and the interface looks great. However none of my
existing puppet environment activity is showing up in the puppet-
dashboard.
I have successfully setup puppetshow and storeconfigs in a prior
installation of puppet and I thought that maybe the configuration
might be similar but after looking at the configs and comparing the
two databases/tables I'm not sure that I know how to configure it
properly for puppet-dashboard. I'm still pretty new to puppet.
How do I get my existing puppet environment pointed to the puppet-
dashboard database? Did I miss a step in the puppet-dashboard
installation?
Joe McDonagh
>
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To post to this group, send email to puppet...@googlegroups.com.
> To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
>
>
>
I was also under the impression it would use the stored config and
existing reports, however Ohad Levy informed me that it uses a custom
report and sends it to the dashboard at :3000, assumed on localhost by
default. So you need to make sure you install the custom reporter, I
think it's called 'puppet-dashboard' on your nodes, as well as enabling
this type of report in the 'reports' config directive.
--
Joe McDonagh
Silent Penguin Services
Operations Engineer
AIM: YoosingYoonickz
IRC: joe-mac on freenode
Blog: www.colonfail.com
Rein Henrichs
Joe McDonagh
>
>
> You do not have to configure individual puppet clients.
>
That's awesome... I thought I would have to have the report processor on
each node.
--
Joe McDonagh
Operations Engineer
Silent Penguin Services
AIM: YoosingYoonickz
IRC: joe-mac on freenode
tomholl
README.markdown instructions.
I was able to get it working by copying the puppet_dashboard.rb into /
usr/lib/ruby/site_ruby/1.8/puppet/reports
Setting the $libdir in puppet.conf seemed to work but I still kept
getting "No report named 'puppet_dashboard' " errors after each
successful catalog compile.
The reason I think the $libdir was getting set is that the output of
'puppetd --configprint libdir' and 'puppetmasterd --configprint
libdir' is /opt/puppetdashboard/lib/puppet (where I put my test
install)
Since I kept getting errors about not finding the report I ran
'puppetmasterd --configprint reports' and got an output of store.
Once I found where the store file was and copied the
puppet_dashboard.rb file into that location (/usr/lib/ruby/site_ruby/
1.8/puppet/reports) everything worked.
So what am I missing? Why did I have to copy the report file over to /
usr/lib/ruby/site_ruby/1.8/puppet/reports if my $libdir was set
properly?
I'm running puppet 0.24.8
On Dec 16, 11:29 am, Rein Henrichs <r...@reductivelabs.com> wrote:
> Hi folks,
>
> Dashboard doesn't (currently) use stored configs or existing reports. The
> README.markdown file in your Dashboard directory has instructions on using
> the included puppet_dashboard report processor with your puppetmasterd to
> send reports to the Dashboard. Please let me know if you run into any
> problems following them.
>
> Your puppetmasterd must be able to speak to the Dashboard via HTTP and
> assumes that the Dashboard is available at "localhost" on port 3000 by
> default.
>
> You do not have to configure individual puppet clients.
>
> On Wed, Dec 16, 2009 at 8:47 AM, Joe McDonagh
> <joseph.e.mcdon...@gmail.com>wrote:
>