[Puppet Users] Re: puppet dashboard

[George Bobeck]

On Jun 14, 1:56 pm, Craig White  wrote:
> I am using Ubuntu 10.04 and ruby-enterprise (not ubuntu ruby) and installed 
> puppet via gem.
>
> How can I install puppet-dashboard if I don't see a gem available and if I 
> use the ubuntu package, i get the whole slop of ruby packages sucked in 
> (which i am trying to avoid)?

I'm not sure if this would be helpful in this case, however here is
how to make dpkg ignore dep issues.

  dpkg -i --ignore-depends= package.deb

If more than one package needs to be ignored, seperate them with
commas:

  dpkg -i --ignore-depends=package1,package2 package3.deb

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

[Puppet Users] Re: Puppet Dashboard

[siva kumar]

Dear Niraj, 
Could you please share the steps to configure the puppet dashboard... 
pre/post configuration details. Did we need to setup new web/mysql servers?
 

On Wednesday, April 4, 2012 5:57:00 PM UTC+5:30, niraj wrote:
>
> Hi All, 
>   I have somehow managed to configure the puppet dashboard, but it 
> is not displaying the nodes and the classes in the dashboard. It is 
> completely empty. Any one has any idea of configuring puppet dashboard 
> so that it displays all the nodes, classes, and reports/ I am newbie 
> so please explain in a little brief. 
>
>
> Regards 
> Niraj K.

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: puppet dashboard

[llowder]

On Friday, November 16, 2012 6:10:33 AM UTC-6, vioilly wrote:
>
> Hi,
>
> Can I have multiple puppet masters speaking to 1 puppet dashboard?
>
>
I don't see why not, just need to configure each one to send the reports.

If you are using the inventory service or the ENC it might get a little 
complicated but from what I have seen it shouldn't be too bad.

Just as a disclaimer, I only run with one master, so I could be rather off 
base here.
 

> Cheers,
> Oli
>
 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/3u80bbRaYYQJ.
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.

[Puppet Users] Re: puppet dashboard

[John Dixon]

> If you are using the inventory service or the ENC it might get a little 
> complicated but from what I have seen it shouldn't be too bad.
>
> Just as a disclaimer, I only run with one master, so I could be rather off 
> base here.
>  
>
>> Cheers,
>> Oli
>>
>  
>
We use one dashboard and have 3 masters, one per location.  The masters are 
not even using the same ca.  Less than ideal, but it works and leaves us 
some room for improvement.  We do not use the inventory service or ENC with 
dashboard. 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/m0A-JA4AB5QJ.
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.

[Puppet Users] Re: Puppet Dashboard

[Ryan Anderson]

Look at puppetboard and panopuppet instead and see which one fits your 
needs better. I'm using puppetboard and find it quite useful.

On Friday, February 26, 2016 at 8:39:24 AM UTC-6, moons...@gmail.com wrote:
>
> Hi All,
>
> I am using puppet 4.3. I think dashboard is not there any more instead of 
> this we have web console. 
>
> Just want to know whether I am right or not.
>
> Thanks,
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/91ad9d1e-49f2-495b-81be-bd5586314c3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet Dashboard; node.rake

[Stefan Heijmans]

Finally found out how it worked, I've create a 2 new rake tasks (all or by 
match) to display a
fulllist of nodes with
Nodename : 
Params   : =,=
Groups   : ,,
Classes  : ,,

fulllist of groups with
Group   : 
Params  : =,=
Classes : ,,
Nodes   : ,,

Now I can easily search where what is used.
I've attached the rake file if people want to use it.

Stefan

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/0bl7zHa0ukgJ.
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.



fulllist.rake
Description: Binary data

Re: [Puppet Users] Re: puppet dashboard

[Oliver Leach]

This sounds like what I want. I have different production networks and I
was hoping I could have one master looking after each production network
and all masters using the 1 dashboard. Each of the masters could be their
own ca for their respective production networks which could work well. How
would you point all the masters to the one dashboard? Does the dashboard
display all the puppet nodes for all master?

Thanks for your help!

Oli
--

We use one dashboard and have 3 masters, one per location.  The masters are
> not even using the same ca.  Less than ideal, but it works and leaves us
> some room for improvement.  We do not use the inventory service or ENC with
> dashboard.
>
>
>

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

[Puppet Users] Re: puppet dashboard inventory

[vioilly]

Just trying to get help here.

My puppetdb server is called puppet-server3. My dashboard server is 
puppet-server2. I can run inventory commands against my puppetdb and get 
results.

For example - i have a puppet-client2.test.net machine running the puppet 
agent

[root@puppet-server3 ~]# curl -H "Accept: application/json" 
'http://localhost:8080/status/nodes/puppet-client2.test.net'
{
  "name" : "puppet-client2.test.net",
  "deactivated" : null,
  "catalog_timestamp" : "2012-12-13T17:55:28.704Z",
  "facts_timestamp" : "2012-12-13T17:55:28.534Z"

So that tells me the puppetdb is holding facts about my puppet agent

For the dashboard, what inventory server do I specify in settings.yml? It 
is the puppetdb server (puppet-server3.test.net)

# Hostname of the inventory server.
inventory_server: 'puppet-server3.test.net'

# Port for the inventory server.
inventory_port: 8081

Do I need to set up SSL certs between the dashboard server and the puppetdb 
server?

Any help would be appreciated

Cheers,
Oli

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/QAfTY4yJgb0J.
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.

[Puppet Users] Re: Puppet Dashboard Groups

[Stefan Heijmans]

>>I was looking for a way to group the servers dynamically
Don't know about this but how about making use of the provided rake tasks, 
like;
rake nodegroup:add # Add a new node group
rake nodegroup:add_all_nodes   # Automatically adds all 
nodes to a group
rake node:addgroup # Add group(s) to a node

Stefan

Op maandag 27 januari 2014 15:16:09 UTC+1 schreef kaustubh chaudhari:

> Hi,
>
> I was looking for a way to group the servers dynamically. Eg: create a 
> "Windows" Group and all the existing nodes and new nodes should be part of 
> "Windows" group.
> I edit a group and then add each server, but practically its not possible 
> with 2k servers in all!!
>
> Is there a way to do that?
>
> -Kaustubh
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/0656e682-855e-4a39-a3bc-bcd2ba772308%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet Dashboard Groups

[kaustubh chaudhari]

Thanks for the Reply Stefan!

I did looked into these options, but i dint find a way to add only windows 
systems to windows group and linux system to linux group.

-Kaustubh

On Tuesday, January 28, 2014 4:15:39 AM UTC-5, Stefan Heijmans wrote:
>
> >>I was looking for a way to group the servers dynamically
> Don't know about this but how about making use of the provided rake tasks, 
> like;
> rake nodegroup:add # Add a new node group
> rake nodegroup:add_all_nodes   # Automatically adds all 
> nodes to a group
> rake node:addgroup # Add group(s) to a node
>
> Stefan
>
> Op maandag 27 januari 2014 15:16:09 UTC+1 schreef kaustubh chaudhari:
>
>> Hi,
>>
>> I was looking for a way to group the servers dynamically. Eg: create a 
>> "Windows" Group and all the existing nodes and new nodes should be part of 
>> "Windows" group.
>> I edit a group and then add each server, but practically its not possible 
>> with 2k servers in all!!
>>
>> Is there a way to do that?
>>
>> -Kaustubh
>>
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/5f504a37-5283-456c-bb34-4f7a2e92813c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet Dashboard Groups

[Stefan Heijmans]

Do you have MCollective running? 
You could use this to generate a list based on specified facts (mco find 
--wf ) to use in those rake tasks.
Or create them by hand from the Inventory Search in the Dashboard, maybe 
even a custom rake task.
 
Stefan
 

Op dinsdag 28 januari 2014 11:24:08 UTC+1 schreef kaustubh chaudhari:

> Thanks for the Reply Stefan!
>
> I did looked into these options, but i dint find a way to add only windows 
> systems to windows group and linux system to linux group.
>
> -Kaustubh
>
> On Tuesday, January 28, 2014 4:15:39 AM UTC-5, Stefan Heijmans wrote: 
>>
>>  >>I was looking for a way to group the servers dynamically
>> Don't know about this but how about making use of the provided rake 
>> tasks, like;
>> rake nodegroup:add # Add a new node group
>> rake nodegroup:add_all_nodes   # Automatically adds all 
>> nodes to a group
>> rake node:addgroup # Add group(s) to a node
>>
>> Stefan
>>
>> Op maandag 27 januari 2014 15:16:09 UTC+1 schreef kaustubh chaudhari:
>>
>>> Hi,
>>>
>>> I was looking for a way to group the servers dynamically. Eg: create a 
>>> "Windows" Group and all the existing nodes and new nodes should be part of 
>>> "Windows" group.
>>> I edit a group and then add each server, but practically its not 
>>> possible with 2k servers in all!!
>>>
>>> Is there a way to do that?
>>>
>>> -Kaustubh
>>>
>>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/6d1b71cb-77c4-4884-ac7f-ff06ce70f069%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet Dashboard Groups

[Richard Berwald]

I recently faced the same challenge. I did not want to group by osfamily 
but by another fact.
I came up with this solution:
1) retrieve a list from PuppetDB in format 'nodename:factvalue' for all 
nodes using puppetdbquery on a puppetmaster (sudo puppet query facts 
--facts= "")
2) retrieve the group list from the console with 'rake nodegroup:list'
3) Compare the existing groups with the groups based upon the values from 
the fact and create missing groups with 'nodegroup:add[groupname]
4) For each (already) existing group, get all members of the group with 
'nodegroup:group_list[groupname]'
5) Compare the nodenames that are already in the group with the list of 
nodenames from PuppetDB, and add missing nodes of a group with 
node:group[nodename,:]

I came to this solution because rake calls felt relatively slow (about 7 
seconds per call) on our platform and I wanted it to be able to potentially 
scale to thousands of nodes.
This runs once a night from an old fashioned cron.

Richard


On Monday, January 27, 2014 3:16:09 PM UTC+1, kaustubh chaudhari wrote:
>
> Hi,
>
> I was looking for a way to group the servers dynamically. Eg: create a 
> "Windows" Group and all the existing nodes and new nodes should be part of 
> "Windows" group.
> I edit a group and then add each server, but practically its not possible 
> with 2k servers in all!!
>
> Is there a way to do that?
>
> -Kaustubh
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/264ebf83-877d-47f6-851e-44dac62a8d9a%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet Dashboard Groups

[kaustubh chaudhari]

Hi,

Thanks for the reply Richard,

I will try this and share the details!

-Kaustubh

On Wednesday, January 29, 2014 2:13:13 PM UTC-5, Richard Berwald wrote:
>
> I recently faced the same challenge. I did not want to group by osfamily 
> but by another fact.
> I came up with this solution:
> 1) retrieve a list from PuppetDB in format 'nodename:factvalue' for all 
> nodes using puppetdbquery on a puppetmaster (sudo puppet query facts 
> --facts= "")
> 2) retrieve the group list from the console with 'rake nodegroup:list'
> 3) Compare the existing groups with the groups based upon the values from 
> the fact and create missing groups with 'nodegroup:add[groupname]
> 4) For each (already) existing group, get all members of the group with 
> 'nodegroup:group_list[groupname]'
> 5) Compare the nodenames that are already in the group with the list of 
> nodenames from PuppetDB, and add missing nodes of a group with 
> node:group[nodename,:]
>
> I came to this solution because rake calls felt relatively slow (about 7 
> seconds per call) on our platform and I wanted it to be able to potentially 
> scale to thousands of nodes.
> This runs once a night from an old fashioned cron.
>
> Richard
>
>
> On Monday, January 27, 2014 3:16:09 PM UTC+1, kaustubh chaudhari wrote:
>>
>> Hi,
>>
>> I was looking for a way to group the servers dynamically. Eg: create a 
>> "Windows" Group and all the existing nodes and new nodes should be part of 
>> "Windows" group.
>> I edit a group and then add each server, but practically its not possible 
>> with 2k servers in all!!
>>
>> Is there a way to do that?
>>
>> -Kaustubh
>>
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/e584314b-c88c-4dea-a55a-9c2f9eedbde0%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet Dashboard port

[Don Dorman]

Thanks so much for the link, but I am testing the opensource version of 
Puppet. A lot of the directory structure is much different.


On Thursday, June 5, 2014 10:27:56 AM UTC-4, Don Dorman wrote:
>
> Good morning Everyone.
>
> I have been struggling to change the default port for Dashboard access 
> from port 3000 to use SSL port 443. My Dashboard version is 1.2.34 if I 
> am not mistaken.
>
> My OS is RHEL 6.4, Puppet Master 3.42-1
>
> Any directions would be great.
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/85a2e004-f502-4c73-a74e-8226d111d730%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet-dashboard issues

[Benjamin Cayzac]

Hi !

Problem fixed !

Syntax wasn't good, i found on old doc but i've search again and i've found 
another syntaxe to do the same thing : "bundle exec rake db:migrate 
RAILS_ENV=production"

And it works ! the database has been generated.

I just want to know how to use the dashboard db with puppet. And if it's 
possible to fill that db automaticaly when a puppet agent connects itself 
to the puppetmaster.
Fill the nodes table and reports table etc.

More information on my configuration :
Passenger : 4.0
Puppet-dashboard : 2.0 Beta
i've just changed puppetmaster : 3.6

thx

Le mardi 29 juillet 2014 16:20:23 UTC+2, Benjamin Cayzac a écrit :
>
> Hi ! 
>
> (sorry for my poor english) 
>
>
> My puppetmaster 3.4.3 run on Ubuntu 14.04 LTS 
>
> I've just manage to replace WEBrick, Puppet use Apache/Passenger to work 
> now. 
>
> I'm a newbie on this, so i've setup Puppet with different docs found on 
> internet. I've started with "apt-get" for the basic install. 
>
> For Passenger, I tried gems. Ruby version is 1.9.1, I saw that is the 
> source 
> of many problems but i'm a newbie on linux too... I don't know if a 
> downgrad 
> of ruby is a good idea or not, or if it is necessary. 
>
> Puppet works fine, but my problem concern dashboard. 
>
> So here is my problem : 
>
> I've configured with success the vhost for apache. 
> I've created the database on mysql. 
>
> but when i run "rake RAILS_ENV=production db:migrate" i've got an error : 
> Warning: Rails rake tasks currently unavailable because we can't find the 
> 'rails' gem 
> rake aborted! 
> Don't know how to build task 'db:migrate' 
>
> trace : 
>
> /var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/task_manager.rb:62:in `[]' 
> /var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:149:in 
> `invoke_task' 
> /var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:106:in `block 
> (2 levels) in top_level' 
> /var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:106:in `each' 
> /var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:106:in `block 
> in top_level' 
> /var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:115:in 
> `run_with_threads' 
> /var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:100:in 
> `top_level' 
> /var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:78:in `block 
> in 
> run' 
> /var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:176:in 
> `standard_exception_handling' 
> /var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:75:in `run' 
> /var/lib/gems/1.9.1/gems/rake-10.3.2/bin/rake:33:in `' 
> /usr/local/bin/rake:23:in `load' 
> /usr/local/bin/rake:23:in `' 
>
>
> Any idea ? 
>
> thx 
>
>
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/aa4bf090-0c26-438b-9e86-1b58176b21b1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet Dashboard/console

[Nick Howes]

On Thursday, 22 January 2015 17:23:40 UTC, skc wrote:
>
> Hi 
>
> I am very new to puppet and I have installed puppet master server and 
> configure 2 node ( agent ) and its working.
>
> I want to know how can I manage puppet, 
>
> Is there any management console/ Puppet dashboard  ?
>
> If yes answer of above question  Can I installed it on separate  VM/server 
>
> Please provide documentation to configure it.
>


There's a good roundup of the options here:

http://www.olindata.com/blog/2014/01/puppet-management-gui-comparison 

Puppet Enterprise Console is arguably the best, but that's not available if 
you're using the free open source option. If you want something similar you 
are probably best looking at Foreman or Puppet Dashboard. Both are in 
development, though Foreman may be seeing more attention as Red Hat have 
started using it in their Satellite product.

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/d3c04114-c912-4c79-8551-345691d586bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet Dashboard/console

[PierreR]

> There's a good roundup of the options here:
>
> http://www.olindata.com/blog/2014/01/puppet-management-gui-comparison 
>
> Puppet Enterprise Console is arguably the best, but that's not available 
> if you're using the free open source option. If you want something similar 
> you are probably best looking at Foreman or Puppet Dashboard. Both are in 
> development, though Foreman may be seeing more attention as Red Hat have 
> started using it in their Satellite product.
>

Is Puppet Dashboard really deprecated as mentioned in the link ? It seems 
more active than both Puppetboard and Puppet Explorer. This last one looks 
promising but completely inactive apparently.

I guess you are right about Foreman. Even if it does not use the PuppetDB, 
it looks like the sole contender.

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/e8853117-a5c9-4375-bd3d-a8ccc994d2a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet Dashboard/console

[jcbollinger]

On Tuesday, February 3, 2015 at 4:23:05 PM UTC-6, PierreR wrote:
>
>
> There's a good roundup of the options here:
>>
>> http://www.olindata.com/blog/2014/01/puppet-management-gui-comparison 
>>
>> Puppet Enterprise Console is arguably the best, but that's not available 
>> if you're using the free open source option. If you want something similar 
>> you are probably best looking at Foreman or Puppet Dashboard. Both are in 
>> development, though Foreman may be seeing more attention as Red Hat have 
>> started using it in their Satellite product.
>>
>
> Is Puppet Dashboard really deprecated as mentioned in the link ? It seems 
> more active than both Puppetboard and Puppet Explorer. This last one looks 
> promising but completely inactive apparently.
>


Dashboard was once a PuppetLabs project, but PL no longer maintains it.  It 
is open-source, though, and I think there is now another maintainer.  I'm 
uncertain how active the project now is, or whether it is or will be ready 
for Puppet 4.


John

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/047a8802-6e5d-4989-99b8-7736f24b1f4f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: puppet dashboard performance issue

[Vincent]

no other solution ?
Where this query is used in the code ?
Can we disable the query ?



On Apr 18, 12:49 am, Andrew Forgue  wrote:
> I also tried to look at this; since it was causing me issues as well.  I had
> 800,000 rows or so in the reports table but I accidentally corrupted it
> (kill -9) so I won't have that many for a few more days.
>
> I created the separate indexex for kind and status but MySQL didn't use
> them.  It uses indexes for everything except the report.status != failed and
> then it switches to a full table scan, even if the query is a simple select
> with only the where and no join.  The documentation for MySQL indexes says
> that if MySQL thinks not using an index will be better it will not use
> indexes.
>
> mysql> explain select * from reports WHERE reports.status = 'failed';
> *** 1. row ***
>            id: 1
>   select_type: SIMPLE
>         table: reports
>          type: ref
> possible_keys: index_reports_on_status
>           key: index_reports_on_status
>       key_len: 258
>           ref: const
>          rows: 274
>         Extra: Using where
> 1 row in set (0.00 sec)
>
> mysql> explain select * from reports WHERE reports.status != 'failed';
> *** 1. row ***
>            id: 1
>   select_type: SIMPLE
>         table: reports
>          type: ALL
> possible_keys: index_reports_on_status
>           key: NULL
>       key_len: NULL
>           ref: NULL
>          rows: 108828
>         Extra: Using where
> 1 row in set (0.00 sec)
>
> Presumably it's doing this because the number of rows that are != failed are
> the vast majority so a full table scan is actually faster.
>
> It looks like it's selecting all the reports, and then grouping so we get
> the latest one.  Doing a cartesian join and then grouping seems extremely
> slow.  I re-wrote the query to use a sub-select:
>
> select reports.*,nodes.* from nodes, (select node_id,max(time) from reports
> where reports.kind = 'apply' and reports.status != 'failed' GROUP by
> node_id) as reports WHERE reports.node_id = nodes.id;
> 1424 rows in set (0.12 sec).
>
> So you're only getting the latest report and then the nodes for each.
>
> How fast does that query run?
>
> -Andrew

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

[Puppet Users] Re: Puppet Dashboard without MySQL

[Douglas Garstang]

Actually, to be more specific, our nodes are stored in yaml files, and I'd
like to keep them that way, and continue to have the yaml files as the
source of truth, not a MySQL database. Puppet dashboard should read from
those yaml files.

Doug.

On Mon, Jun 27, 2011 at 10:24 AM, Douglas Garstang
wrote:

> All,
>
> Can puppet dashboard be used WITHOUT MySQL?
>
> Can't find it documented here:
>
>
> http://docs.puppetlabs.com/guides/installing_dashboard.html#external_node_classification
>
> Doug.
>
>


-- 
Regards,

Douglas Garstang
http://www.linkedin.com/in/garstang
Email: doug.garst...@gmail.com
Cell: +1-805-340-5627

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

Re: [Puppet Users] Re: Puppet Dashboard; node.rake

[Nigel Kersten]

Nice work Stefan!

(as an aside, we keep digging up positive contributors named "Stefan" in
the Puppet community. If this trend continues, I expect 90% of posts to be
from a "Stefan" in 12 months time ;-) )

I've cc'd Dan and Kelsey, who have both been working on a Dashboard Puppet
Face for command-line control. Although the rake tasks are totally useful,
we'd like to be able to have all this functionality under a "puppet
dashboard ..." set of commands.


On Sat, Dec 10, 2011 at 1:08 PM, Stefan Heijmans wrote:

> Finally found out how it worked, I've create a 2 new rake tasks (all or by
> match) to display a
> fulllist of nodes with
> Nodename : 
> Params   : =,=
> Groups   : ,,
> Classes  : ,,
>
> fulllist of groups with
> Group   : 
> Params  : =,=
> Classes : ,,
> Nodes   : ,,
>
> Now I can easily search where what is used.
> I've attached the rake file if people want to use it.
>
> Stefan
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/0bl7zHa0ukgJ.
>
> 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.
>



-- 
Nigel Kersten
Product Manager, Puppet Labs

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

Re: [Puppet Users] Re: Puppet Dashboard; node.rake

[Stefan Heijmans]

Op zondag 11 december 2011 19:01:14 UTC+1 schreef Nigel Kersten het 
volgende:
>
> I've cc'd Dan and Kelsey, who have both been working on a Dashboard Puppet 
> Face for command-line control. Although the rake tasks are totally useful, 
> we'd like to be able to have all this functionality under a "puppet 
> dashboard ..." set of commands.
> -- 
> Nigel Kersten
> Product Manager, Puppet Labs
>

Hi Nigel,

we use rake at the moment as;
- we still run 2.6.12 in production 
- I don't get the Dashboard Puppet Face working on our test system with 
RHEL5.7 which has ruby 1.8.5
  gem install activerecord results in 
  *** buffer overflow detected ***: /usr/bin/ruby terminated
  /lib64/libc.so.6(__chk_fail+0x2f)[0x326bae807f]
  and activerecord 2.3.14 does install but doesn't seem to work.

Stefan
 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/_gTltiX8x10J.
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.

[Puppet Users] Re: puppet dashboard performance issue

[Vincent]

Thanks

I have make the
rake RAILS_ENV=production db:raw:optimize
and  in the my.cnf
query_cache_size = 2000

Its really better

Vincent

On 11 avr, 14:26, Mohamed Lrhazi  wrote:
> There's some rake tasks, and other things,  suggested 
> here:https://github.com/puppetlabs/puppet-dashboard
>
>
>
>
>
>
>
> On Mon, Apr 11, 2011 at 5:29 AM, Vincent  wrote:
> > Hello,
>
> > since the last upgrade to V1.1.0
> > The dashboard is very slow
>
> > I notice this slow queries in the log :
>
> >  Node Load (14178.9ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
> > `reports` ON reports.node_id = nodes.id WHERE ((reports.kind = 'apply'
> > AND reports.status != 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
> > nodes.id
> >  Node Load (13149.9ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
> > `reports` ON reports.node_id = nodes.id WHERE ((reports.kind = 'apply'
> > AND reports.status = 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
> > nodes.id
>
> > How can i optimize the DB ?
>
> > Vincent
>
> > --
> > 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 
> > athttp://groups.google.com/group/puppet-users?hl=en.

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

[Puppet Users] Re: puppet dashboard performance issue

[Vincent]

I have increase the mysql like this but the queries takes still more
than 9sec for the first page.
any other suggestions for the mysql tuning ?

key_buffer=64M
sort_buffer=4M
query_cache_size = 20M
read_buffer_size=1M

  Node Load (9090.5ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
`reports` ON reports.node_id = nodes.id WHERE ((reports.kind = 'apply'
AND reports.status != 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
nodes.id
  Node Load (9082.9ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
`reports` ON reports.node_id = nodes.id WHERE ((reports.kind = 'apply'
AND reports.status = 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
nodes.id


On Apr 11, 4:19 pm, Vincent  wrote:
> Thanks
>
> I have make the
> rake RAILS_ENV=production db:raw:optimize
> and  in the my.cnf
> query_cache_size = 2000
>
> Its really better
>
> Vincent
>
> On 11 avr, 14:26, Mohamed Lrhazi  wrote:
>
>
>
>
>
>
>
> > There's some rake tasks, and other things,  suggested 
> > here:https://github.com/puppetlabs/puppet-dashboard
>
> > On Mon, Apr 11, 2011 at 5:29 AM, Vincent  wrote:
> > > Hello,
>
> > > since the last upgrade to V1.1.0
> > > The dashboard is very slow
>
> > > I notice this slow queries in the log :
>
> > >  Node Load (14178.9ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
> > > `reports` ON reports.node_id = nodes.id WHERE ((reports.kind = 'apply'
> > > AND reports.status != 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
> > > nodes.id
> > >  Node Load (13149.9ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
> > > `reports` ON reports.node_id = nodes.id WHERE ((reports.kind = 'apply'
> > > AND reports.status = 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
> > > nodes.id
>
> > > How can i optimize the DB ?
>
> > > Vincent
>
> > > --
> > > 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 
> > > athttp://groups.google.com/group/puppet-users?hl=en.

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

[Puppet Users] Re: puppet dashboard performance issue

[Vincent]

query on nodes or reports table are very quick, it s with this join
that the query is slow

Is an index missing ?



On Apr 12, 12:25 pm, Vincent  wrote:
> I have increase the mysql like this but the queries takes still more
> than 9sec for the first page.
> any other suggestions for the mysql tuning ?
>
> key_buffer=64M
> sort_buffer=4M
> query_cache_size = 20M
> read_buffer_size=1M
>
>   Node Load (9090.5ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
> `reports` ON reports.node_id = nodes.id WHERE ((reports.kind = 'apply'
> AND reports.status != 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
> nodes.id
>   Node Load (9082.9ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
> `reports` ON reports.node_id = nodes.id WHERE ((reports.kind = 'apply'
> AND reports.status = 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
> nodes.id
>
> On Apr 11, 4:19 pm, Vincent  wrote:
>
>
>
>
>
>
>
> > Thanks
>
> > I have make the
> > rake RAILS_ENV=production db:raw:optimize
> > and  in the my.cnf
> > query_cache_size = 2000
>
> > Its really better
>
> > Vincent
>
> > On 11 avr, 14:26, Mohamed Lrhazi  wrote:
>
> > > There's some rake tasks, and other things,  suggested 
> > > here:https://github.com/puppetlabs/puppet-dashboard
>
> > > On Mon, Apr 11, 2011 at 5:29 AM, Vincent  wrote:
> > > > Hello,
>
> > > > since the last upgrade to V1.1.0
> > > > The dashboard is very slow
>
> > > > I notice this slow queries in the log :
>
> > > >  Node Load (14178.9ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
> > > > `reports` ON reports.node_id = nodes.id WHERE ((reports.kind = 'apply'
> > > > AND reports.status != 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
> > > > nodes.id
> > > >  Node Load (13149.9ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
> > > > `reports` ON reports.node_id = nodes.id WHERE ((reports.kind = 'apply'
> > > > AND reports.status = 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
> > > > nodes.id
>
> > > > How can i optimize the DB ?
>
> > > > Vincent
>
> > > > --
> > > > 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 
> > > > athttp://groups.google.com/group/puppet-users?hl=en.

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

[Puppet Users] Re: puppet dashboard performance issue

[Vincent]

I have noticed thaht when I remove ((reports.kind = ‘apply’ AND
reports.status = ‘failed’) part from the query, the query is very
quick.

mysql> show index from reports from dashboard;
+-++--
+--+-+---+-+--
++--++-+
| Table   | Non_unique | Key_name
| Seq_in_index | Column_name | Collation | Cardinality | Sub_part |
Packed | Null | Index_type | Comment |
+-++--
+--+-+---+-+--
++--++-+
| reports |  0 | PRIMARY
|1 | id  | A |  112252 | NULL |
NULL   |  | BTREE  | |
| reports |  1 | index_reports_on_node_id
|1 | node_id | A | 652 | NULL |
NULL   | YES  | BTREE  | |
| reports |  1 | index_reports_on_time_and_node_id_and_status
|1 | time| A |  112252 | NULL |
NULL   | YES  | BTREE  | |
| reports |  1 | index_reports_on_time_and_node_id_and_status
|2 | node_id | A |  112252 | NULL |
NULL   | YES  | BTREE  | |
| reports |  1 | index_reports_on_time_and_node_id_and_status
|3 | status  | A |  112252 | NULL |
NULL   | YES  | BTREE  | |
+-++--
+--+-+---+-+--
++--++-+
5 rows in set (0.01 sec)



On Apr 12, 4:04 pm, Charles Johnson  wrote:
> What indexes do you have on the respective tables?
>
>
>
>
>
>
>
> On Tue, Apr 12, 2011 at 5:25 AM, Vincent  wrote:
> > I have increase the mysql like this but the queries takes still more
> > than 9sec for the first page.
> > any other suggestions for the mysql tuning ?
>
> > key_buffer=64M
> > sort_buffer=4M
> > query_cache_size = 20M
> > read_buffer_size=1M
>
> >  Node Load (9090.5ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
> > `reports` ON reports.node_id = nodes.id WHERE ((reports.kind = 'apply'
> > AND reports.status != 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
> > nodes.id
> >  Node Load (9082.9ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
> > `reports` ON reports.node_id = nodes.id WHERE ((reports.kind = 'apply'
> > AND reports.status = 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
> > nodes.id
>
> > On Apr 11, 4:19 pm, Vincent  wrote:
> > > Thanks
>
> > > I have make the
> > > rake RAILS_ENV=production db:raw:optimize
> > > and  in the my.cnf
> > > query_cache_size = 2000
>
> > > Its really better
>
> > > Vincent
>
> > > On 11 avr, 14:26, Mohamed Lrhazi  wrote:
>
> > > > There's some rake tasks, and other things,  suggested here:
> >https://github.com/puppetlabs/puppet-dashboard
>
> > > > On Mon, Apr 11, 2011 at 5:29 AM, Vincent  wrote:
> > > > > Hello,
>
> > > > > since the last upgrade to V1.1.0
> > > > > The dashboard is very slow
>
> > > > > I notice this slow queries in the log :
>
> > > > >  Node Load (14178.9ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
> > > > > `reports` ON reports.node_id = nodes.id WHERE ((reports.kind =
> > 'apply'
> > > > > AND reports.status != 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
> > > > > nodes.id
> > > > >  Node Load (13149.9ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
> > > > > `reports` ON reports.node_id = nodes.id WHERE ((reports.kind =
> > 'apply'
> > > > > AND reports.status = 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
> > > > > nodes.id
>
> > > > > How can i optimize the DB ?
>
> > > > > Vincent
>
> > > > > --
> > > > > 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 athttp://
> > groups.google.com/group/puppet-users?hl=en.
>
> > --
> > 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.

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

[Puppet Users] Re: Puppet dashboard ap_content_length_filter error

[Jake - USPS]

Arg, I didn't even realize I was already using an old version ... I'll
update to 1.1.0 and give it another shot.

Thanks for the reply.

On Apr 12, 10:48 am, Patrick  wrote:
> On Apr 12, 2011, at 8:41 AM, Jake - USPS wrote:
>
> > puppet-dashboard-1.0.4-1.sles10
>
> > Everything works fine.  From what I've read, '/reports' is old/
> > deprecated and 'reports/upload' is what should be used ... so I was
> > wondering if this has been seen before and/or if I'm doing something
> > wrong.
>
> As far as I can tell, the quick answer is:
> The replacement was only added in 1.1.0.  If your version is less than 1.1.0, 
> you need to use the old URL.

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

[Puppet Users] Re: Puppet dashboard ap_content_length_filter error

[Jake - USPS]

What release notes are you referring to?  The puppet-dashboard page
mentions 1 upgrade, as does the README.markdown in the source/
package.  There is a RELEASE_NOTES.md file, but that seems to be a
copy of CHANGELOG.  Please let me know if I missed something or if
there is a better place to look for this type of information so I know
where to look for these type of oddities.

Thanks,
Jake

On Apr 12, 12:13 pm, Patrick  wrote:
> On Apr 12, 2011, at 9:57 AM, Jake - USPS wrote:
>
> > Arg, I didn't even realize I was already using an old version ... I'll
> > update to 1.1.0 and give it another shot.
>
> > Thanks for the reply.
>
> As a quick reminder if you're skimming release notes, or not reading them at 
> all, you'll need to do two migrates for that upgrade.  The first (normal) one 
> took me about 10 minutes.  During that time, dashboard didn't work.  The 
> second one took me 4 hours, but you can run dashboard while it's running.  
> Until you finish the second migrate, you can't use any old reports.

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

[Puppet Users] Re: Puppet dashboard ap_content_length_filter error

[Jake - USPS]

I just finished getting my 1.1.0rc3 package created and as you thought
my issues disappeared ... /reports/upload works fine now.

Thanks,
Jake

On Apr 12, 12:33 pm, Jake - USPS  wrote:
> What release notes are you referring to?  The puppet-dashboard page
> mentions 1 upgrade, as does the README.markdown in the source/
> package.  There is a RELEASE_NOTES.md file, but that seems to be a
> copy of CHANGELOG.  Please let me know if I missed something or if
> there is a better place to look for this type of information so I know
> where to look for these type of oddities.
>
> Thanks,
> Jake
>
> On Apr 12, 12:13 pm, Patrick  wrote:
>
>
>
>
>
>
>
> > On Apr 12, 2011, at 9:57 AM, Jake - USPS wrote:
>
> > > Arg, I didn't even realize I was already using an old version ... I'll
> > > update to 1.1.0 and give it another shot.
>
> > > Thanks for the reply.
>
> > As a quick reminder if you're skimming release notes, or not reading them 
> > at all, you'll need to do two migrates for that upgrade.  The first 
> > (normal) one took me about 10 minutes.  During that time, dashboard didn't 
> > work.  The second one took me 4 hours, but you can run dashboard while it's 
> > running.  Until you finish the second migrate, you can't use any old 
> > reports.

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

[Puppet Users] Re: Puppet dashboard and environments

[Ben Tullis]

Hi Rein,

OK, thanks for letting me know.

I will press on with setting the environment with a suitable parameter
then.

Kind regards,
Ben

On Jul 30, 4:21 pm, Rein Henrichs  wrote:
> Excerpts from Ben Tullis's message of Fri Jul 30 04:29:46 -0700 2010:
>
> > Why doesn't the dashboard understand which environment applies to the
> > host, and return that in the yaml output?
>
> > Is this something that is better handled another way, or is it on the
> > roadmap for the puppet dashboard?
>
> Hi Ben,
>
> Dashboard doesn't currently handle environments but it is on the
> roadmap.
>
> Rein Henrichshttp://puppetlabs.com

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.

[Puppet Users] Re: Puppet dashboard and environments

[Ashay]

You can use a wrapper for the external nodes script,
that will intercept the YAMl from Dashboard and attach an environment
to the YAML.

You can put logic in there that says: "if hostname =~ xyz, then
environment = production"
(Or whatever criteria you want, instead of hostname)

Foreman can do this out of the box, if you would rather not bother
with a wrapper.

This is a bit of a hack, but can help you have two manifiest
directories on a single puppetmaster,
based on the environment.


On Jul 30, 8:36 am, Ben Tullis  wrote:
> Hi Rein,
>
> OK, thanks for letting me know.
>
> I will press on with setting the environment with a suitable parameter
> then.
>
> Kind regards,
> Ben
>
> On Jul 30, 4:21 pm, Rein Henrichs  wrote:
>
> > Excerpts from Ben Tullis's message of Fri Jul 30 04:29:46 -0700 2010:
>
> > > Why doesn't the dashboard understand which environment applies to the
> > > host, and return that in the yaml output?
>
> > > Is this something that is better handled another way, or is it on the
> > > roadmap for the puppet dashboard?
>
> > Hi Ben,
>
> > Dashboard doesn't currently handle environments but it is on the
> > roadmap.
>
> > Rein Henrichshttp://puppetlabs.com
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.

[Puppet Users] Re: puppet-dashboard Explorer 8

[ScubaDude]

Ticket filed (bug, refactor)

On Aug 13, 7:56 am, Matt Robinson  wrote:
> We weren't aware as none of us are using Internet Explorer.  We'll
> have to have someone get a copy to test with at some point.
>
> Can you file a ticket?
>
> http://projects.puppetlabs.com
>
> Thanks,
> Matt
>
> On Thu, Aug 12, 2010 at 6:40 AM, ScubaDude  wrote:
> > puppet-dashboard on internet exploder 8:
>
> > Layout borked and no graphs?
> > I was wondering if you were aware of this?
>
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Puppet Users" group.
> > To post to this group, send email to puppet-us...@googlegroups.com.
> > To unsubscribe from this group, send email to 
> > puppet-users+unsubscr...@googlegroups.com.
> > For more options, visit this group 
> > athttp://groups.google.com/group/puppet-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.

[Puppet Users] Re: Puppet-dashboard(open source)

[Mamta Garg]

It resolved.don't reply :)

On Tue, Feb 19, 2013 at 4:15 AM, Mamta Garg  wrote:

> Hi ,
>
> I am working with puppet open source.I have setup puppet dashboard.
> But its is not showing any agent node there.Anyone guide me for the same?
>
> --
> Thanks and Regards,
> Mamta Garg
>



-- 
Thanks and Regards,
Mamta Garg

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet-dashboard(open source)

[siva kumar]

Dear Garg, 

Could you pleas share steps to install and configure Puppet-dashboard(open 
source).  

Thanks & Regards, 

Shivs

On Tuesday, February 19, 2013 2:45:48 PM UTC+5:30, Mamta Garg wrote:
>
> Hi ,
>
> I am working with puppet open source.I have setup puppet dashboard.
> But its is not showing any agent node there.Anyone guide me for the same?
>
> -- 
> Thanks and Regards,
> Mamta Garg
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: puppet dashboard stopped updating

[Gregory Damiani]

Looks like I sussed it on my own.  This had nothing to do with 
environments.  In the process of updating my puppet.conf file, I fat 
fingered the master's reporturl ... simple as that.  Nothing to see here.  

Thanks
/Greg

On Friday, March 29, 2013 3:08:26 PM UTC-4, Gregory Damiani wrote:
>
> I was in the process of setting up puppet environments.  I pulled code 
> from my main modules and manifests directories into the prod environment 
> folder, deployed a newer branch of that code to a 'stg' environment folder, 
> updated puppet.conf on the master, and reconfigured puppet.conf on my 
> agents to use the new environments.  All looked fine until I checked puppet 
> dashboard a while later and noticed all my hosts were coming up as 
> Unresponsive.  I confirmed on the agents that they can still compile 
> catalogs and create changes.  But no new reports are coming into the puppet 
> master.
>
> I checked the logs and see the following error:
>
> Report processor failed: undefined method `+' for nil:NilClass
>
> I'm using a trial version of puppet enterprise 2.6
>
> Any help is appreciated.
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: puppet dashboard inventory

[Peter Bukowinski]

On Dec 13, 2012, at 4:09 PM, vioilly wrote:

> Just trying to get help here.
> 
> My puppetdb server is called puppet-server3. My dashboard server is 
> puppet-server2. I can run inventory commands against my puppetdb and get 
> results.
> 
> For example - i have a puppet-client2.test.net machine running the puppet 
> agent
> 
> [root@puppet-server3 ~]# curl -H "Accept: application/json" 
> 'http://localhost:8080/status/nodes/puppet-client2.test.net'
> {
>   "name" : "puppet-client2.test.net",
>   "deactivated" : null,
>   "catalog_timestamp" : "2012-12-13T17:55:28.704Z",
>   "facts_timestamp" : "2012-12-13T17:55:28.534Z"
> 
> So that tells me the puppetdb is holding facts about my puppet agent
> 
> For the dashboard, what inventory server do I specify in settings.yml? It is 
> the puppetdb server (puppet-server3.test.net)
> 
> # Hostname of the inventory server.
> inventory_server: 'puppet-server3.test.net'
> 
> # Port for the inventory server.
> inventory_port: 8081
> 
> Do I need to set up SSL certs between the dashboard server and the puppetdb 
> server?
> 
> Any help would be appreciated
> 
> Cheers,
> Oli

You do not need to make any changes to your dashboard server. Instead, you need 
to modify two files and add one file to your puppet master. See step 2 on this 
page for the details: 
http://docs.puppetlabs.com/puppetdb/1/connect_puppet_master.html#step-2-edit-config-files

--
Peter

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

Re: [Puppet Users] Re: puppet dashboard inventory

[vioilly]

Correction to the above post


Also puppetdb.conf

[master]
  storeconfigs = true
  storeconfigs_backend = puppetdb


should be 

[main]

server = puppet-server3.test.net
port = 8081



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/AzA2bKtVECQJ.
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.

Re: [Puppet Users] Re: puppet dashboard inventory

[vioilly]

Hi,

I believe I have done that.

So on my puppet master (puppet-server1) I have modified the puppet.conf 
file and added the following:

[master]

storeconfigs = true
storeconfigs_backend = puppetdb

Also puppetdb.conf

[master]
  storeconfigs = true
  storeconfigs_backend = puppetdb


and added the route.yaml file

I did also edit the auth.conf file - do I need to do on the puppetmaster ?

On the dashboard server I have turned on the inventory service and added 
the puppetdb server as the invenory_server - wher else would it know how to 
connect to the puppetdb ?

I have also made sure all the certs have been signed by the puppet CA 
server and are valid

Thanks,
Oli

On Thursday, December 13, 2012 9:26:28 PM UTC, pmbuko wrote:
>
> On Dec 13, 2012, at 4:09 PM, vioilly wrote:
>
> Just trying to get help here.
>
> My puppetdb server is called puppet-server3. My dashboard server is 
> puppet-server2. I can run inventory commands against my puppetdb and get 
> results.
>
> For example - i have a puppet-client2.test.net machine running the puppet 
> agent
>
> [root@puppet-server3 ~]# curl -H "Accept: application/json" '
> http://localhost:8080/status/nodes/puppet-client2.test.net'
> {
>   "name" : "puppet-client2.test.net",
>   "deactivated" : null,
>   "catalog_timestamp" : "2012-12-13T17:55:28.704Z",
>   "facts_timestamp" : "2012-12-13T17:55:28.534Z"
>
> So that tells me the puppetdb is holding facts about my puppet agent
>
> For the dashboard, what inventory server do I specify in settings.yml? It 
> is the puppetdb server (puppet-server3.test.net)
>
> # Hostname of the inventory server.
> inventory_server: 'puppet-server3.test.net'
>
> # Port for the inventory server.
> inventory_port: 8081
>
> Do I need to set up SSL certs between the dashboard server and the 
> puppetdb server?
>
> Any help would be appreciated
>
> Cheers,
> Oli 
>
>
> You do not need to make any changes to your dashboard server. Instead, you 
> need to modify two files and add one file to your puppet master. See step 2 
> on this page for the details: 
> http://docs.puppetlabs.com/puppetdb/1/connect_puppet_master.html#step-2-edit-config-files
>
> --
> Peter
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/I4jqT0AyqGYJ.
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.

Re: [Puppet Users] Re: Puppet Dashboard Groups

[kaustubh chaudhari]

Hi Stefan,

I am in process of setting up MCollective!

In the mean while i can do the search using inventory search in Dashboard,
i do get the list, but when i try ti export the details in the cvs format,
it wont export only filtered, it will export all the node list ie: all
linux windows etc.

where i an searching with the facts as osfamily = windows  and/or Linux.

-Kaustubh

With Warm Regards
Kaustubh.A.Chaudhari
(M)-09373102619


On Tue, Jan 28, 2014 at 6:35 AM, Stefan Heijmans wrote:

> Do you have MCollective running?
> You could use this to generate a list based on specified facts (mco find
> --wf ) to use in those rake tasks.
> Or create them by hand from the Inventory Search in the Dashboard, maybe
> even a custom rake task.
>
> Stefan
>
>
> Op dinsdag 28 januari 2014 11:24:08 UTC+1 schreef kaustubh chaudhari:
>
>> Thanks for the Reply Stefan!
>>
>> I did looked into these options, but i dint find a way to add only
>> windows systems to windows group and linux system to linux group.
>>
>> -Kaustubh
>>
>> On Tuesday, January 28, 2014 4:15:39 AM UTC-5, Stefan Heijmans wrote:
>>>
>>>  >>I was looking for a way to group the servers dynamically
>>> Don't know about this but how about making use of the provided rake
>>> tasks, like;
>>> rake nodegroup:add # Add a new node group
>>> rake nodegroup:add_all_nodes   # Automatically adds all
>>> nodes to a group
>>> rake node:addgroup # Add group(s) to a node
>>>
>>> Stefan
>>>
>>> Op maandag 27 januari 2014 15:16:09 UTC+1 schreef kaustubh chaudhari:
>>>
 Hi,

 I was looking for a way to group the servers dynamically. Eg: create a
 "Windows" Group and all the existing nodes and new nodes should be part of
 "Windows" group.
 I edit a group and then add each server, but practically its not
 possible with 2k servers in all!!

 Is there a way to do that?

 -Kaustubh

>>>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "Puppet Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/puppet-users/bzFuC0l3TPk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/6d1b71cb-77c4-4884-ac7f-ff06ce70f069%40googlegroups.com
> .
>
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGceKKqi%2BSM87fFdYS2NgyGSV%2BOcMhzgnDrJX49dWpSSqzKt4g%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Puppet Dashboard Groups

[Stefan Heijmans]

>>it will export all the node list 
That's not nice :(
So that will really be by hand; copy/paste & strip hostnames.
 
Stefan

Op dinsdag 28 januari 2014 13:36:11 UTC+1 schreef kaustubh chaudhari:

>   Hi Stefan,
>
> I am in process of setting up MCollective!
>
> In the mean while i can do the search using inventory search in Dashboard, 
> i do get the list, but when i try ti export the details in the cvs format, 
> it wont export only filtered, it will export all the node list ie: all 
> linux windows etc.
>
> where i an searching with the facts as osfamily = windows  and/or Linux.
>
> -Kaustubh
>
> With Warm Regards
> Kaustubh.A.Chaudhari
> (M)-09373102619
>
>
> On Tue, Jan 28, 2014 at 6:35 AM, Stefan Heijmans 
> 
> > wrote:
>
>>  Do you have MCollective running? 
>> You could use this to generate a list based on specified facts (mco find 
>> --wf ) to use in those rake tasks.
>> Or create them by hand from the Inventory Search in the Dashboard, maybe 
>> even a custom rake task.
>>  
>> Stefan
>>  
>>
>> Op dinsdag 28 januari 2014 11:24:08 UTC+1 schreef kaustubh chaudhari:
>>  
>>> Thanks for the Reply Stefan!
>>>
>>> I did looked into these options, but i dint find a way to add only 
>>> windows systems to windows group and linux system to linux group.
>>>
>>> -Kaustubh
>>>
>>> On Tuesday, January 28, 2014 4:15:39 AM UTC-5, Stefan Heijmans wrote: 

  >>I was looking for a way to group the servers dynamically
 Don't know about this but how about making use of the provided rake 
 tasks, like;
 rake nodegroup:add # Add a new node group
 rake nodegroup:add_all_nodes   # Automatically adds 
 all nodes to a group
 rake node:addgroup # Add group(s) to a node

 Stefan

 Op maandag 27 januari 2014 15:16:09 UTC+1 schreef kaustubh chaudhari:

> Hi,
>
> I was looking for a way to group the servers dynamically. Eg: create a 
> "Windows" Group and all the existing nodes and new nodes should be part 
> of 
> "Windows" group.
> I edit a group and then add each server, but practically its not 
> possible with 2k servers in all!!
>
> Is there a way to do that?
>
> -Kaustubh
>
  -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Puppet Users" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/puppet-users/bzFuC0l3TPk/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> puppet-users...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/6d1b71cb-77c4-4884-ac7f-ff06ce70f069%40googlegroups.com.
>>  
>>
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/0e9146e4-cf79-4f2e-8440-f91adb4c0a58%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Puppet Dashboard Groups

[Jose Luis Ledesma]

What about storing the facts in yaml format in the puppetmaster and just doing 
a grep there?

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/5a54a80e-0cdc-4006-b1b1-f4066a4a743f%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Puppet Dashboard port

[Kwame Bahena]

Ah,

Can you please then share your config and the steps you are following?


Cheers!


On Thu, Jun 5, 2014 at 10:15 AM, Don Dorman  wrote:

> Thanks so much for the link, but I am testing the opensource version of
> Puppet. A lot of the directory structure is much different.
>
>
>
> On Thursday, June 5, 2014 10:27:56 AM UTC-4, Don Dorman wrote:
>>
>> Good morning Everyone.
>>
>> I have been struggling to change the default port for Dashboard access
>> from port 3000 to use SSL port 443. My Dashboard version is 1.2.34 if I
>> am not mistaken.
>>
>> My OS is RHEL 6.4, Puppet Master 3.42-1
>>
>> Any directions would be great.
>>
>  --
> 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 puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/85a2e004-f502-4c73-a74e-8226d111d730%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANtpaPpb2A6OQ8EgCsuX-h6pkM-EoHPp0xkWV9yxCr4E_zE4og%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Puppet Dashboard port

[Don Dorman]

I almost have it figured out, and of course I will share the information

On Thursday, June 5, 2014 11:55:35 AM UTC-4, Kwame Bahena wrote:
>
> Ah,
>
> Can you please then share your config and the steps you are following?
>
>
> Cheers!
>
>
> On Thu, Jun 5, 2014 at 10:15 AM, Don Dorman  > wrote:
>
>> Thanks so much for the link, but I am testing the opensource version of 
>> Puppet. A lot of the directory structure is much different.
>>
>>
>>
>> On Thursday, June 5, 2014 10:27:56 AM UTC-4, Don Dorman wrote:
>>>
>>> Good morning Everyone.
>>>
>>> I have been struggling to change the default port for Dashboard access 
>>> from port 3000 to use SSL port 443. My Dashboard version is 1.2.34 if I 
>>> am not mistaken.
>>>
>>> My OS is RHEL 6.4, Puppet Master 3.42-1
>>>
>>> Any directions would be great.
>>>
>>  -- 
>> 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 puppet-users...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/85a2e004-f502-4c73-a74e-8226d111d730%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/ceedf7c7-e0d9-4b93-afe8-3e32fe826d99%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Puppet Dashboard port

[Don Dorman]

You will find this works great.

http://devsops.blogspot.ca/2013/04/installing-puppet-dashboard.html

On Thursday, June 5, 2014 2:15:48 PM UTC-4, Don Dorman wrote:
>
> I almost have it figured out, and of course I will share the information
>
> On Thursday, June 5, 2014 11:55:35 AM UTC-4, Kwame Bahena wrote:
>>
>> Ah,
>>
>> Can you please then share your config and the steps you are following?
>>
>>
>> Cheers!
>>
>>
>> On Thu, Jun 5, 2014 at 10:15 AM, Don Dorman  wrote:
>>
>>> Thanks so much for the link, but I am testing the opensource version of 
>>> Puppet. A lot of the directory structure is much different.
>>>
>>>
>>>
>>> On Thursday, June 5, 2014 10:27:56 AM UTC-4, Don Dorman wrote:

 Good morning Everyone.

 I have been struggling to change the default port for Dashboard access 
 from port 3000 to use SSL port 443. My Dashboard version is 1.2.34 if 
 I 
 am not mistaken.

 My OS is RHEL 6.4, Puppet Master 3.42-1

 Any directions would be great.

>>>  -- 
>>> 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 puppet-users...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/puppet-users/85a2e004-f502-4c73-a74e-8226d111d730%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/19cafabe-0cd5-4d2f-b853-7b9ad852aad4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Puppet Dashboard without MySQL

[Nan Liu]

On Mon, Jun 27, 2011 at 10:35 AM, Douglas Garstang
 wrote:
> Actually, to be more specific, our nodes are stored in yaml files, and I'd
> like to keep them that way, and continue to have the yaml files as the
> source of truth, not a MySQL database. Puppet dashboard should read from
> those yaml files.
> Doug.

You can use Dashboard in any of the following combination:

ENC
Reporting
ENC + Reporting.

If you have an existing ENC that reads those YAML files you can keep
that process intact and only use dashboard for reporting.

Nan

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

Re: [Puppet Users] Re: Puppet Dashboard without MySQL

[Douglas Garstang]

On Mon, Jun 27, 2011 at 10:49 AM, Nan Liu  wrote:

> On Mon, Jun 27, 2011 at 10:35 AM, Douglas Garstang
>  wrote:
> > Actually, to be more specific, our nodes are stored in yaml files, and
> I'd
> > like to keep them that way, and continue to have the yaml files as the
> > source of truth, not a MySQL database. Puppet dashboard should read from
> > those yaml files.
> > Doug.
>
> You can use Dashboard in any of the following combination:
>
> ENC
> Reporting
> ENC + Reporting.
>
>
Kinda wanted to use it for more than reporting. Shame, really. It would be
nice if there was a tool that could translate any external node format.

Doug.

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

Re: [Puppet Users] Re: Puppet Dashboard without MySQL

[Ohad Levy]

On Mon, Jun 27, 2011 at 9:40 PM, Douglas Garstang
 wrote:
> On Mon, Jun 27, 2011 at 10:49 AM, Nan Liu  wrote:
>>
>> On Mon, Jun 27, 2011 at 10:35 AM, Douglas Garstang
>>  wrote:
>> > Actually, to be more specific, our nodes are stored in yaml files, and
>> > I'd
>> > like to keep them that way, and continue to have the yaml files as the
>> > source of truth, not a MySQL database. Puppet dashboard should read from
>> > those yaml files.
>> > Doug.
>>
>> You can use Dashboard in any of the following combination:
>>
>> ENC
>> Reporting
>> ENC + Reporting.
>>
>
> Kinda wanted to use it for more than reporting. Shame, really. It would be
> nice if there was a tool that could translate any external node format.

not sure what do you mean by translate, but Foreman can import
information from other ENC's

Ohad
>
> Doug.
>
> --
> 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.
>

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

Re: [Puppet Users] Re: Puppet Dashboard without MySQL

[Douglas Garstang]

On Mon, Jun 27, 2011 at 12:30 PM, Ohad Levy  wrote:

> On Mon, Jun 27, 2011 at 9:40 PM, Douglas Garstang
>  wrote:
> > On Mon, Jun 27, 2011 at 10:49 AM, Nan Liu  wrote:
> >>
> >> On Mon, Jun 27, 2011 at 10:35 AM, Douglas Garstang
> >>  wrote:
> >> > Actually, to be more specific, our nodes are stored in yaml files, and
> >> > I'd
> >> > like to keep them that way, and continue to have the yaml files as the
> >> > source of truth, not a MySQL database. Puppet dashboard should read
> from
> >> > those yaml files.
> >> > Doug.
> >>
> >> You can use Dashboard in any of the following combination:
> >>
> >> ENC
> >> Reporting
> >> ENC + Reporting.
> >>
> >
> > Kinda wanted to use it for more than reporting. Shame, really. It would
> be
> > nice if there was a tool that could translate any external node format.
>
> not sure what do you mean by translate, but Foreman can import
> information from other ENC's
>
>
I don't want to import the nodes, I want to leave the node information in
YAML files and have Foreman read from that. When edits are made to the
nodes, I want the edits to be made to the YAML files. Putting the node
config into anything else removes the ability to do revision control, and
importing the data info Foreman (I assume) obfuscates it to the point that I
can't easily view/edit the files any more.

Doug.

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

[Puppet Users] Re: puppet dashboard and complex data

[Matt]

Nan, thanks for the quick response. I think that might work for me,
but what would give me a bit more power in the future would being able
to add define resources and the parameters. Not sure if that had been
a requested feature or not.



On Oct 17, 7:14 pm, Nan Liu  wrote:
> On Mon, Oct 17, 2011 at 3:57 PM, Matt  wrote:
> > So I am messing around with puppet dashboard and for the most part for
> > what I am working on it fits the bill for an ENC. The only question I
> > have is I need to pass information about a customer to set up
> > resources and the system can have multiple customers on it. What is
> > the best way to handle complex data? Would I be able to pass json data
> > for example?
>
> This is stolen from some doc I wrote for how to support complex data
> in dashboard until is has hash/array support. Missing pictures, but
> should have everything you need on how to use json data in dashboard.
>
> In puppetlabs-stdlib we added several functions including parseyaml,
> and parsejson for this purpose. Unfortunately there’s one more hurdle
> since the data passed back from dashboard is pading single \ to triple
> \\\ as well as striping leading ---, so this requires us to convert
> “[\\\“0.pool.ntp.org\\\”]” to “[\”0.pool.ntp.org\”]”. To get around
> this we do a quick data cleanup with the following function:
>
> module Puppet::Parser::Functions
>   newfunction(:convjson, :type => :rvalue) do |args|
>     if args[0].to_s.empty? then
>       fail "Must provide non empty value."
>     else
>       return args[0].gsub(/\\/,'')
>     end
>   end
> end
>
> At this point you can convert the json string back to an array/hash in puppet:
> class ntp(
>   $ntp_server=parsejson(convjson($::ntp_server))
>   ) {
>     file {'/etc/ntp.conf':
>       ...
>       # template use $ntp_server
>       content => template('ntp/ntp.conf.erb'),
>     }
>     service {'ntpd':
>       ...
>     }
>
> }
>
> Thanks,
>
> Nan

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

[Puppet Users] Re: puppet dashboard group and class

[Christian]

Hi Nicolas,

i had exactly the same problem when i start using puppet dashboard
some months ago. There is no documentation about it on the page and i
would say that the names 'Classes' and 'Groups' are used unlucky. It
turns out that classes acutally are the puppet modules (why the hell
they dont use the same expression in puppet dashboard like in the rest
puppet) and groups can be used to model a kind of inheritance. If you
use classes and groups you have to use puppet dashboard as an external
node classifier means you are not using node.pp anymore. The modeling
which module belongs to which node will be done then in puppet
dashboard. Your class name have of course be exactly the same name as
the module name you have in your folder structure in the puppet module
folder.

Hope that helps a bit

Christian



On 15 Dez., 02:17, Nicolas Aizier 
wrote:
> Hi everyone,
>
> I'm actually kind of new in puppet but I'm doing good in progressing.
> I have read lot of docs and how to to understand the whole behaviour
> of puppet.
> Installed a puppet master server, deployed 15 clients to test it on
> some of our testing servers.
> Written modules to get exactly what we want, and then installed puppet
> dashboard which work really fine.
>
> My question might sound a bit noobish but I'm stuck on that point and
> I really don't like to don't understand every part of a tool.
> What is the use of adding "groups" and "class" in the dashboard ?
> It seems that the dashboard don't see your class from the modules (saw
> that it will be corrected soon), but what is the point to creating
> class in the GUI ? Can you do anything with that ? and if yes will
> that not spread the config through dashboard + puppet config files,
> it'll be messy to maintain 
> Same question with the groups, I understand that you can assign class
> to groups so it's easyer to add a server in a global behavior but it
> only uses class from dashboard . And is there a way to create such
> group in puppet config files (if yes I didn't manage to find it ...) ?
>
> Thx a lot for your time and to all the puppet users !

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.

[Puppet Users] Re: puppet dashboard group and class

[Nicolas Aizier]

Hi Christian,

Thanks a lot buddy, that helped me a lot. I was able today to change
all my puppet configuration with the external_node feature using
dashboard.
This is really a good thing but definitely need to be documented so
people can use it. I'm considering writing such a doc for the wiki to
help the project.
The more people use puppet the more puppet will be loved, this project
really deserve it 

Thx again !

On Dec 15, 5:42 pm, Christian 
wrote:
> Hi Nicolas,
>
> i had exactly the same problem when i start using puppet dashboard
> some months ago. There is no documentation about it on the page and i
> would say that the names 'Classes' and 'Groups' are used unlucky. It
> turns out that classes acutally are the puppet modules (why the hell
> they dont use the same expression in puppet dashboard like in the rest
> puppet) and groups can be used to model a kind of inheritance. If you
> use classes and groups you have to use puppet dashboard as an external
> node classifier means you are not using node.pp anymore. The modeling
> which module belongs to which node will be done then in puppet
> dashboard. Your class name have of course be exactly the same name as
> the module name you have in your folder structure in the puppet module
> folder.
>
> Hope that helps a bit
>
> Christian
>
> On 15 Dez., 02:17, Nicolas Aizier 
> wrote:
>
>
>
>
>
>
>
> > Hi everyone,
>
> > I'm actually kind of new in puppet but I'm doing good in progressing.
> > I have read lot of docs and how to to understand the whole behaviour
> > of puppet.
> > Installed a puppet master server, deployed 15 clients to test it on
> > some of our testing servers.
> > Written modules to get exactly what we want, and then installed puppet
> > dashboard which work really fine.
>
> > My question might sound a bit noobish but I'm stuck on that point and
> > I really don't like to don't understand every part of a tool.
> > What is the use of adding "groups" and "class" in the dashboard ?
> > It seems that the dashboard don't see your class from the modules (saw
> > that it will be corrected soon), but what is the point to creating
> > class in the GUI ? Can you do anything with that ? and if yes will
> > that not spread the config through dashboard + puppet config files,
> > it'll be messy to maintain 
> > Same question with the groups, I understand that you can assign class
> > to groups so it's easyer to add a server in a global behavior but it
> > only uses class from dashboard . And is there a way to create such
> > group in puppet config files (if yes I didn't manage to find it ...) ?
>
> > Thx a lot for your time and to all the puppet users !

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.

Re: [Puppet Users] Re: puppet-dashboard Explorer 8

[John Warburton]

On 13 August 2010 18:59, ScubaDude  wrote:

> Ticket filed (bug, refactor)
>
> On Aug 13, 7:56 am, Matt Robinson  wrote:
> > We weren't aware as none of us are using Internet Explorer.  We'll
> > have to have someone get a copy to test with at some point.
> >
> > Can you file a ticket?
> >
> > http://projects.puppetlabs.com
> >
> > Thanks,
> > Matt
> >
> > On Thu, Aug 12, 2010 at 6:40 AM, ScubaDude 
> wrote:
> > > puppet-dashboard on internet exploder 8:
> >
> > > Layout borked and no graphs?
> > > I was wondering if you were aware of this?
>

Am I the only other person interested in this?
https://projects.puppetlabs.com/issues/4530

Its driving our managers nuts to copy & paste URLs from email to Firefox (if
they have it) rather than just clicking on the dashboard URL and having it
work with the corporate SOE

Please "watch" this ticket if you are interested

Thanks

John

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

Re: [Puppet Users] Re: puppet dashboard performance issue

[Charles Johnson]

What indexes do you have on the respective tables?

On Tue, Apr 12, 2011 at 5:25 AM, Vincent  wrote:

> I have increase the mysql like this but the queries takes still more
> than 9sec for the first page.
> any other suggestions for the mysql tuning ?
>
> key_buffer=64M
> sort_buffer=4M
> query_cache_size = 20M
> read_buffer_size=1M
>
>  Node Load (9090.5ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
> `reports` ON reports.node_id = nodes.id WHERE ((reports.kind = 'apply'
> AND reports.status != 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
> nodes.id
>  Node Load (9082.9ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
> `reports` ON reports.node_id = nodes.id WHERE ((reports.kind = 'apply'
> AND reports.status = 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
> nodes.id
>
>
> On Apr 11, 4:19 pm, Vincent  wrote:
> > Thanks
> >
> > I have make the
> > rake RAILS_ENV=production db:raw:optimize
> > and  in the my.cnf
> > query_cache_size = 2000
> >
> > Its really better
> >
> > Vincent
> >
> > On 11 avr, 14:26, Mohamed Lrhazi  wrote:
> >
> >
> >
> >
> >
> >
> >
> > > There's some rake tasks, and other things,  suggested here:
> https://github.com/puppetlabs/puppet-dashboard
> >
> > > On Mon, Apr 11, 2011 at 5:29 AM, Vincent  wrote:
> > > > Hello,
> >
> > > > since the last upgrade to V1.1.0
> > > > The dashboard is very slow
> >
> > > > I notice this slow queries in the log :
> >
> > > >  Node Load (14178.9ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
> > > > `reports` ON reports.node_id = nodes.id WHERE ((reports.kind =
> 'apply'
> > > > AND reports.status != 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
> > > > nodes.id
> > > >  Node Load (13149.9ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
> > > > `reports` ON reports.node_id = nodes.id WHERE ((reports.kind =
> 'apply'
> > > > AND reports.status = 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
> > > > nodes.id
> >
> > > > How can i optimize the DB ?
> >
> > > > Vincent
> >
> > > > --
> > > > 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 athttp://
> groups.google.com/group/puppet-users?hl=en.
>
> --
> 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.
>
>

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

Re: [Puppet Users] Re: puppet dashboard performance issue

[Charles Johnson]

You have a partial (i.e., three-part) index 'time', 'node_id', 'status' from
which you appear to be selecting against only two parts. On the mysql
command line run the query by hand preceded by the keywprd "explain"

explain select nodes blah blah blah

You should get back a listing that will let you see how the indexes are
being used (or abused!). You may discover that in addition to the composite
index you have that two additional indexes will help.

~Charles~

On Tue, Apr 12, 2011 at 9:15 AM, Vincent  wrote:

> I have noticed thaht when I remove ((reports.kind = ‘apply’ AND
> reports.status = ‘failed’) part from the query, the query is very
> quick.
>
> mysql> show index from reports from dashboard;
> +-++--
> +--+-+---+-+--
> ++--++-+
> | Table   | Non_unique | Key_name
> | Seq_in_index | Column_name | Collation | Cardinality | Sub_part |
> Packed | Null | Index_type | Comment |
> +-++--
> +--+-+---+-+--
> ++--++-+
> | reports |  0 | PRIMARY
> |1 | id  | A |  112252 | NULL |
> NULL   |  | BTREE  | |
> | reports |  1 | index_reports_on_node_id
> |1 | node_id | A | 652 | NULL |
> NULL   | YES  | BTREE  | |
> | reports |  1 | index_reports_on_time_and_node_id_and_status
> |1 | time| A |  112252 | NULL |
> NULL   | YES  | BTREE  | |
> | reports |  1 | index_reports_on_time_and_node_id_and_status
> |2 | node_id | A |  112252 | NULL |
> NULL   | YES  | BTREE  | |
> | reports |  1 | index_reports_on_time_and_node_id_and_status
> |3 | status  | A |  112252 | NULL |
> NULL   | YES  | BTREE  | |
> +-++--
> +--+-+---+-+--
> ++--++-+
> 5 rows in set (0.01 sec)
>
>
>
> On Apr 12, 4:04 pm, Charles Johnson  wrote:
> > What indexes do you have on the respective tables?
> >
> >
> >
> >
> >
> >
> >
> > On Tue, Apr 12, 2011 at 5:25 AM, Vincent  wrote:
> > > I have increase the mysql like this but the queries takes still more
> > > than 9sec for the first page.
> > > any other suggestions for the mysql tuning ?
> >
> > > key_buffer=64M
> > > sort_buffer=4M
> > > query_cache_size = 20M
> > > read_buffer_size=1M
> >
> > >  Node Load (9090.5ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
> > > `reports` ON reports.node_id = nodes.id WHERE ((reports.kind = 'apply'
> > > AND reports.status != 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
> > > nodes.id
> > >  Node Load (9082.9ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
> > > `reports` ON reports.node_id = nodes.id WHERE ((reports.kind = 'apply'
> > > AND reports.status = 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
> > > nodes.id
> >
> > > On Apr 11, 4:19 pm, Vincent  wrote:
> > > > Thanks
> >
> > > > I have make the
> > > > rake RAILS_ENV=production db:raw:optimize
> > > > and  in the my.cnf
> > > > query_cache_size = 2000
> >
> > > > Its really better
> >
> > > > Vincent
> >
> > > > On 11 avr, 14:26, Mohamed Lrhazi  wrote:
> >
> > > > > There's some rake tasks, and other things,  suggested here:
> > >https://github.com/puppetlabs/puppet-dashboard
> >
> > > > > On Mon, Apr 11, 2011 at 5:29 AM, Vincent 
> wrote:
> > > > > > Hello,
> >
> > > > > > since the last upgrade to V1.1.0
> > > > > > The dashboard is very slow
> >
> > > > > > I notice this slow queries in the log :
> >
> > > > > >  Node Load (14178.9ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
> > > > > > `reports` ON reports.node_id = nodes.id WHERE ((reports.kind =
> > > 'apply'
> > > > > > AND reports.status != 'failed') AND (`nodes`.`hidden` = 0)) GROUP
> BY
> > > > > > nodes.id
> > > > > >  Node Load (13149.9ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
> > > > > > `reports` ON reports.node_id = nodes.id WHERE ((reports.kind =
> > > 'apply'
> > > > > > AND reports.status = 'failed') AND (`nodes`.`hidden` = 0)) GROUP
> BY
> > > > > > nodes.id
> >
> > > > > > How can i optimize the DB ?
> >
> > > > > > Vincent
> >
> > > > > > --
> > > > > > 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 athttp://
> > > groups.google.com/group/puppet-users?hl=en.
> >
> > > --
> > > You received this message because you are subscr

Re: [Puppet Users] Re: puppet dashboard performance issue

[vincent]

here is the result , I don't know what to do :(

mysql> explain SELECT `nodes`.* FROM `nodes` INNER JOIN `reports` ON
reports.node_id = nodes.id WHERE ((reports.kind = 'apply' AND reports.status
!= 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY nodes.id;
++-+-+---+--+--+-++--+-+
| id | select_type | table   | type  | possible_keys| key
   | key_len | ref| rows | Extra   |
++-+-+---+--+--+-++--+-+
|  1 | SIMPLE  | nodes   | index | PRIMARY  | PRIMARY
   | 4   | NULL   |  573 | Using where |
|  1 | SIMPLE  | reports | ref   | index_reports_on_node_id |
index_reports_on_node_id | 5   | dashboard.nodes.id |  167 | Using where
|
++-+-+---+--+--+-++--+-+
2 rows in set (0.00 sec)



2011/4/12 Charles Johnson 

> You have a partial (i.e., three-part) index 'time', 'node_id', 'status'
> from which you appear to be selecting against only two parts. On the mysql
> command line run the query by hand preceded by the keywprd "explain"
>
> explain select nodes blah blah blah
>
> You should get back a listing that will let you see how the indexes are
> being used (or abused!). You may discover that in addition to the composite
> index you have that two additional indexes will help.
>
> ~Charles~
>
>
> On Tue, Apr 12, 2011 at 9:15 AM, Vincent  wrote:
>
>> I have noticed thaht when I remove ((reports.kind = ‘apply’ AND
>> reports.status = ‘failed’) part from the query, the query is very
>> quick.
>>
>> mysql> show index from reports from dashboard;
>> +-++--
>> +--+-+---+-+--
>> ++--++-+
>> | Table   | Non_unique | Key_name
>> | Seq_in_index | Column_name | Collation | Cardinality | Sub_part |
>> Packed | Null | Index_type | Comment |
>> +-++--
>> +--+-+---+-+--
>> ++--++-+
>> | reports |  0 | PRIMARY
>> |1 | id  | A |  112252 | NULL |
>> NULL   |  | BTREE  | |
>> | reports |  1 | index_reports_on_node_id
>> |1 | node_id | A | 652 | NULL |
>> NULL   | YES  | BTREE  | |
>> | reports |  1 | index_reports_on_time_and_node_id_and_status
>> |1 | time| A |  112252 | NULL |
>> NULL   | YES  | BTREE  | |
>> | reports |  1 | index_reports_on_time_and_node_id_and_status
>> |2 | node_id | A |  112252 | NULL |
>> NULL   | YES  | BTREE  | |
>> | reports |  1 | index_reports_on_time_and_node_id_and_status
>> |3 | status  | A |  112252 | NULL |
>> NULL   | YES  | BTREE  | |
>> +-++--
>> +--+-+---+-+--
>> ++--++-+
>> 5 rows in set (0.01 sec)
>>
>>
>>
>> On Apr 12, 4:04 pm, Charles Johnson  wrote:
>> > What indexes do you have on the respective tables?
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > On Tue, Apr 12, 2011 at 5:25 AM, Vincent  wrote:
>> > > I have increase the mysql like this but the queries takes still more
>> > > than 9sec for the first page.
>> > > any other suggestions for the mysql tuning ?
>> >
>> > > key_buffer=64M
>> > > sort_buffer=4M
>> > > query_cache_size = 20M
>> > > read_buffer_size=1M
>> >
>> > >  Node Load (9090.5ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
>> > > `reports` ON reports.node_id = nodes.id WHERE ((reports.kind =
>> 'apply'
>> > > AND reports.status != 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
>> > > nodes.id
>> > >  Node Load (9082.9ms)   SELECT `nodes`.* FROM `nodes` INNER JOIN
>> > > `reports` ON reports.node_id = nodes.id WHERE ((reports.kind =
>> 'apply'
>> > > AND reports.status = 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
>> > > nodes.id
>> >
>> > > On Apr 11, 4:19 pm, Vincent  wrote:
>> > > > Thanks
>> >
>> > > > I have make the
>> > > > rake RAILS_ENV=production db:raw:optimize
>> > > > and  in the my.cnf
>> > > > query_cache_size = 2000
>> >
>> > > > Its really better
>> >
>> > > > Vincent
>> >
>> > > > On 11 avr, 14:26, Mohamed Lrhazi  wrote:
>> >
>> > > > > There's some rake tasks, and other things,  suggested here:
>> > >https://github.com/puppetlabs/puppet-dashboard
>> >
>> > > > > On Mon, Apr 11, 2011 

Re: [Puppet Users] Re: Puppet dashboard ap_content_length_filter error

[Patrick]

On Apr 12, 2011, at 9:57 AM, Jake - USPS wrote:

> Arg, I didn't even realize I was already using an old version ... I'll
> update to 1.1.0 and give it another shot.
> 
> Thanks for the reply.

As a quick reminder if you're skimming release notes, or not reading them at 
all, you'll need to do two migrates for that upgrade.  The first (normal) one 
took me about 10 minutes.  During that time, dashboard didn't work.  The second 
one took me 4 hours, but you can run dashboard while it's running.  Until you 
finish the second migrate, you can't use any old reports.

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

Re: [Puppet Users] Re: puppet dashboard performance issue

[Charles Johnson]

A couple of things to notice. First, only the nodes.id index and
index_reports_on_node_id
index are used, and since index_reports_on_node_id is used as a ref type you
will have 573 x 167 rows to examine (95,651 more or less) to produce the
rows your sql finally fetches. You might --important: might-- be able to do
better. There is an index: index_reports_on_time_and_node_id_and_status,
which includes node_id and status, but is not used. Without hurting
anything, and without changing the query you could create an index on
reports.kind and reports.status. This might help if there are lots of
different values for kind and status. For example, you generally do not want
to create an index for a column where the only values are 'true' and
'false', say. That effectively divides the table in half, and if you have a
million rows, reducing a full scan to 500,000 may not help much.

But anyway, if you know how to create indexes, this is what I would try
first.

Others probably have much better ideas. You might ping a mysql list as well.

On Tue, Apr 12, 2011 at 11:26 AM, vincent  wrote:

> here is the result , I don't know what to do :(
>
> mysql> explain SELECT `nodes`.* FROM `nodes` INNER JOIN `reports` ON
> reports.node_id = nodes.id WHERE ((reports.kind = 'apply' AND
> reports.status != 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY nodes.id;
>
> ++-+-+---+--+--+-++--+-+
> | id | select_type | table   | type  | possible_keys| key
>| key_len | ref| rows | Extra   |
>
> ++-+-+---+--+--+-++--+-+
> |  1 | SIMPLE  | nodes   | index | PRIMARY  | PRIMARY
>| 4   | NULL   |  573 | Using where |
> |  1 | SIMPLE  | reports | ref   | index_reports_on_node_id |
> index_reports_on_node_id | 5   | dashboard.nodes.id |  167 | Using
> where |
>
> ++-+-+---+--+--+-++--+-+
> 2 rows in set (0.00 sec)
>
>  
>
> 2011/4/12 Charles Johnson 
>
>> You have a partial (i.e., three-part) index 'time', 'node_id', 'status'
>> from which you appear to be selecting against only two parts. On the mysql
>> command line run the query by hand preceded by the keywprd "explain"
>>
>> explain select nodes blah blah blah
>>
>> You should get back a listing that will let you see how the indexes are
>> being used (or abused!). You may discover that in addition to the composite
>> index you have that two additional indexes will help.
>>
>> ~Charles~
>>
>>
>> On Tue, Apr 12, 2011 at 9:15 AM, Vincent  wrote:
>>
>>> I have noticed thaht when I remove ((reports.kind = ‘apply’ AND
>>> reports.status = ‘failed’) part from the query, the query is very
>>> quick.
>>>
>>> mysql> show index from reports from dashboard;
>>> +-++--
>>> +--+-+---+-+--
>>> ++--++-+
>>> | Table   | Non_unique | Key_name
>>> | Seq_in_index | Column_name | Collation | Cardinality | Sub_part |
>>> Packed | Null | Index_type | Comment |
>>> +-++--
>>> +--+-+---+-+--
>>> ++--++-+
>>> | reports |  0 | PRIMARY
>>> |1 | id  | A |  112252 | NULL |
>>> NULL   |  | BTREE  | |
>>> | reports |  1 | index_reports_on_node_id
>>> |1 | node_id | A | 652 | NULL |
>>> NULL   | YES  | BTREE  | |
>>> | reports |  1 | index_reports_on_time_and_node_id_and_status
>>> |1 | time| A |  112252 | NULL |
>>> NULL   | YES  | BTREE  | |
>>> | reports |  1 | index_reports_on_time_and_node_id_and_status
>>> |2 | node_id | A |  112252 | NULL |
>>> NULL   | YES  | BTREE  | |
>>> | reports |  1 | index_reports_on_time_and_node_id_and_status
>>> |3 | status  | A |  112252 | NULL |
>>> NULL   | YES  | BTREE  | |
>>> +-++--
>>> +--+-+---+-+--
>>> ++--++-+
>>> 5 rows in set (0.01 sec)
>>>
>>>
>>>
>>> On Apr 12, 4:04 pm, Charles Johnson  wrote:
>>> > What indexes do you have on the respective tables?
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Tue, Apr 12, 2011 at 5:25 AM, Vincent  wrote:
>>> > > I have increase the mysql like this but th

Re: [Puppet Users] Re: puppet dashboard performance issue

[vincent]

I have add an index
ALTER TABLE `reports` ADD INDEX `index_reports_on_kind_and_status` ( `kind`
, `status` )

it s better but maybe not perfect as the query is performed on each pages in
the dashboard

Thanks

Vincent

mysql> explain SELECT `nodes`.* FROM `nodes` INNER JOIN `reports` ON
 reports.node_id = nodes.id WHERE ((reports.kind = 'apply' AND
reports.status  != 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY nodes.id;
++-+-++---+--+-+---+---+--+
| id | select_type | table   | type   | possible_keys
  | key  | key_len | ref
  | rows  | Extra|
++-+-++---+--+-+---+---+--+
|  1 | SIMPLE  | reports | ref|
index_reports_on_node_id,index_reports_on_kind_and_status |
index_reports_on_kind_and_status | 768 | const |
19483 | Using where; Using temporary; Using filesort |
|  1 | SIMPLE  | nodes   | eq_ref | PRIMARY
  | PRIMARY  | 4   |
dashboard.reports.node_id | 1 | Using where
 |
++-+-++---+--+-+---+---+--+
2 rows in set (0.00 sec)

2011/4/12 Charles Johnson 

> A couple of things to notice. First, only the nodes.id index and 
> index_reports_on_node_id
> index are used, and since index_reports_on_node_id is used as a ref type
> you will have 573 x 167 rows to examine (95,651 more or less) to produce the
> rows your sql finally fetches. You might --important: might-- be able to do
> better. There is an index: index_reports_on_time_and_node_id_and_status,
> which includes node_id and status, but is not used. Without hurting
> anything, and without changing the query you could create an index on
> reports.kind and reports.status. This might help if there are lots of
> different values for kind and status. For example, you generally do not want
> to create an index for a column where the only values are 'true' and
> 'false', say. That effectively divides the table in half, and if you have a
> million rows, reducing a full scan to 500,000 may not help much.
>
> But anyway, if you know how to create indexes, this is what I would try
> first.
>
> Others probably have much better ideas. You might ping a mysql list as
> well.
>
> On Tue, Apr 12, 2011 at 11:26 AM, vincent  wrote:
>
>> here is the result , I don't know what to do :(
>>
>> mysql> explain SELECT `nodes`.* FROM `nodes` INNER JOIN `reports` ON
>> reports.node_id = nodes.id WHERE ((reports.kind = 'apply' AND
>> reports.status != 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY nodes.id
>> ;
>>
>> ++-+-+---+--+--+-++--+-+
>> | id | select_type | table   | type  | possible_keys| key
>>  | key_len | ref| rows | Extra   |
>>
>> ++-+-+---+--+--+-++--+-+
>> |  1 | SIMPLE  | nodes   | index | PRIMARY  | PRIMARY
>>  | 4   | NULL   |  573 | Using where |
>> |  1 | SIMPLE  | reports | ref   | index_reports_on_node_id |
>> index_reports_on_node_id | 5   | dashboard.nodes.id |  167 | Using
>> where |
>>
>> ++-+-+---+--+--+-++--+-+
>> 2 rows in set (0.00 sec)
>>
>>  
>>
>> 2011/4/12 Charles Johnson 
>>
>>> You have a partial (i.e., three-part) index 'time', 'node_id', 'status'
>>> from which you appear to be selecting against only two parts. On the mysql
>>> command line run the query by hand preceded by the keywprd "explain"
>>>
>>> explain select nodes blah blah blah
>>>
>>> You should get back a listing that will let you see how the indexes are
>>> being used (or abused!). You may discover that in addition to the composite
>>> index you have that two additional indexes will help.
>>>
>>> ~Charles~
>>>
>>>
>>> On Tue, Apr 12, 2011 at 9:15 AM, Vincent  wrote:
>>>
 I have noticed thaht when I remove ((reports.kind = ‘apply’ AND
 reports.status = ‘failed’) part from the query, the query is very
 quick.

 mysql> show index from reports from dashboard;
 +-++--

Re: [Puppet Users] Re: puppet dashboard performance issue

[Charles Johnson]

Good try! But I was not clear. Try an index just for kind, and another
separate index just for status. You are down to 4 x 768 (3072) from 95691.
That is much better. Again, drop the create separate indexes for kind and
status and  index_reports_on_kind_and_status .

On Tue, Apr 12, 2011 at 2:11 PM, vincent  wrote:

> I have add an index
> ALTER TABLE `reports` ADD INDEX `index_reports_on_kind_and_status` (
> `kind` , `status` )
>
> it s better but maybe not perfect as the query is performed on each pages
> in the dashboard
>
> Thanks
>
> Vincent
>
> mysql> explain SELECT `nodes`.* FROM `nodes` INNER JOIN `reports` ON
>  reports.node_id = nodes.id WHERE ((reports.kind = 'apply' AND
> reports.status  != 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY nodes.id
> ;
>
> ++-+-++---+--+-+---+---+--+
> | id | select_type | table   | type   | possible_keys
>   | key  | key_len | ref
>   | rows  | Extra|
>
> ++-+-++---+--+-+---+---+--+
> |  1 | SIMPLE  | reports | ref|
> index_reports_on_node_id,index_reports_on_kind_and_status |
> index_reports_on_kind_and_status | 768 | const |
> 19483 | Using where; Using temporary; Using filesort |
> |  1 | SIMPLE  | nodes   | eq_ref | PRIMARY
>   | PRIMARY  | 4   |
> dashboard.reports.node_id | 1 | Using where
>  |
>
>
> ++-+-++---+--+-+---+---+--+
> 2 rows in set (0.00 sec)
>
> 2011/4/12 Charles Johnson 
>
>> A couple of things to notice. First, only the nodes.id index and 
>> index_reports_on_node_id
>> index are used, and since index_reports_on_node_id is used as a ref type
>> you will have 573 x 167 rows to examine (95,651 more or less) to produce the
>> rows your sql finally fetches. You might --important: might-- be able to do
>> better. There is an index: index_reports_on_time_and_node_id_and_status,
>> which includes node_id and status, but is not used. Without hurting
>> anything, and without changing the query you could create an index on
>> reports.kind and reports.status. This might help if there are lots of
>> different values for kind and status. For example, you generally do not want
>> to create an index for a column where the only values are 'true' and
>> 'false', say. That effectively divides the table in half, and if you have a
>> million rows, reducing a full scan to 500,000 may not help much.
>>
>> But anyway, if you know how to create indexes, this is what I would try
>> first.
>>
>> Others probably have much better ideas. You might ping a mysql list as
>> well.
>>
>> On Tue, Apr 12, 2011 at 11:26 AM, vincent  wrote:
>>
>>> here is the result , I don't know what to do :(
>>>
>>> mysql> explain SELECT `nodes`.* FROM `nodes` INNER JOIN `reports` ON
>>> reports.node_id = nodes.id WHERE ((reports.kind = 'apply' AND
>>> reports.status != 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
>>> nodes.id;
>>>
>>> ++-+-+---+--+--+-++--+-+
>>> | id | select_type | table   | type  | possible_keys| key
>>>  | key_len | ref| rows | Extra   |
>>>
>>> ++-+-+---+--+--+-++--+-+
>>> |  1 | SIMPLE  | nodes   | index | PRIMARY  | PRIMARY
>>>  | 4   | NULL   |  573 | Using where |
>>> |  1 | SIMPLE  | reports | ref   | index_reports_on_node_id |
>>> index_reports_on_node_id | 5   | dashboard.nodes.id |  167 | Using
>>> where |
>>>
>>> ++-+-+---+--+--+-++--+-+
>>> 2 rows in set (0.00 sec)
>>>
>>>  
>>>
>>> 2011/4/12 Charles Johnson 
>>>
 You have a partial (i.e., three-part) index 'time', 'node_id', 'status'
 from which you appear to be selecting against only two parts. On the mysql
 command line run the query by hand preceded by the keywprd "explain"

 explain select nodes blah blah blah

 You should get back a listing that will let you see how the indexes are
 being used (or abused!). You may

Re: [Puppet Users] Re: puppet dashboard performance issue

[vincent]

the rows are respectively 19450  and 1
So I have down from 95691 to 19450

with one index on kind and one on status , it s worst

it use only index_reports_on_kind and 1 X 58631 rows ..

mysql> explain SELECT `nodes`.* FROM `nodes` INNER JOIN `reports` ON
 reports.node_id = nodes.id WHERE ((reports.kind = 'apply' AND
reports.status  != 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY nodes.id;
++-+-+++---+-+---+---+--+
| id | select_type | table   | type   | possible_keys
   | key   | key_len | ref
| rows  | Extra|
++-+-+++---+-+---+---+--+
|  1 | SIMPLE  | reports | ref|
index_reports_on_node_id,index_reports_on_kind,index_reports_on_status |
index_reports_on_kind | 768 | const | 58631 | Using
where; Using temporary; Using filesort |
|  1 | SIMPLE  | nodes   | eq_ref | PRIMARY
   | PRIMARY   | 4   |
dashboard.reports.node_id | 1 | Using where
 |
++-+-+++---+-+---+---+--+
2 rows in set (0.00 sec)



2011/4/12 Charles Johnson 

> Good try! But I was not clear. Try an index just for kind, and another
> separate index just for status. You are down to 4 x 768 (3072) from 95691.
> That is much better. Again, drop the create separate indexes for kind and
> status and  index_reports_on_kind_and_status .
>
> On Tue, Apr 12, 2011 at 2:11 PM, vincent  wrote:
>
>> I have add an index
>> ALTER TABLE `reports` ADD INDEX `index_reports_on_kind_and_status` (
>> `kind` , `status` )
>>
>> it s better but maybe not perfect as the query is performed on each pages
>> in the dashboard
>>
>> Thanks
>>
>> Vincent
>>
>> mysql> explain SELECT `nodes`.* FROM `nodes` INNER JOIN `reports` ON
>>  reports.node_id = nodes.id WHERE ((reports.kind = 'apply' AND
>> reports.status  != 'failed') AND (`nodes`.`hidden` = 0)) GROUP BY
>> nodes.id;
>>
>> ++-+-++---+--+-+---+---+--+
>> | id | select_type | table   | type   | possible_keys
>> | key  | key_len | ref
>> | rows  | Extra|
>>
>> ++-+-++---+--+-+---+---+--+
>> |  1 | SIMPLE  | reports | ref|
>> index_reports_on_node_id,index_reports_on_kind_and_status |
>> index_reports_on_kind_and_status | 768 | const |
>> 19483 | Using where; Using temporary; Using filesort |
>> |  1 | SIMPLE  | nodes   | eq_ref | PRIMARY
>> | PRIMARY  | 4   |
>> dashboard.reports.node_id | 1 | Using where
>>  |
>>
>>
>> ++-+-++---+--+-+---+---+--+
>> 2 rows in set (0.00 sec)
>>
>> 2011/4/12 Charles Johnson 
>>
>>>  A couple of things to notice. First, only the nodes.id index and 
>>> index_reports_on_node_id
>>> index are used, and since index_reports_on_node_id is used as a ref type
>>> you will have 573 x 167 rows to examine (95,651 more or less) to produce the
>>> rows your sql finally fetches. You might --important: might-- be able to do
>>> better. There is an index: index_reports_on_time_and_node_id_and_status,
>>> which includes node_id and status, but is not used. Without hurting
>>> anything, and without changing the query you could create an index on
>>> reports.kind and reports.status. This might help if there are lots of
>>> different values for kind and status. For example, you generally do not want
>>> to create an index for a column where the only values are 'true' and
>>> 'false', say. That effectively divides the table in half, and if you have a
>>> million rows, reducing a full scan to 500,000 may not help much.
>>>
>>> But anyway, if you know how to create indexes, this is what I would try
>>> first.
>>>
>>> Oth

Re: [Puppet Users] Re: puppet dashboard performance issue

[Charles Johnson]

What seems the best set of indexes to you?

Next, you need to read your mysql docs to "optimize table" and to reindex a
table, especially if there have been lots of writes and/or lots of deletes.

~Charles~

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

Re: [Puppet Users] Re: Puppet dashboard ap_content_length_filter error

[Patrick]

On Apr 12, 2011, at 10:33 AM, Jake - USPS wrote:

> What release notes are you referring to?  The puppet-dashboard page
> mentions 1 upgrade, as does the README.markdown in the source/
> package.  There is a RELEASE_NOTES.md file, but that seems to be a
> copy of CHANGELOG.  Please let me know if I missed something or if
> there is a better place to look for this type of information so I know
> where to look for these type of oddities.


I'd guess it's on the website too, but I saw it in this email:
http://groups.google.com/group/puppet-users/msg/a58575de08b7b16d

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

Re: [Puppet Users] Re: puppet dashboard performance issue

[Andrew Forgue]

I also tried to look at this; since it was causing me issues as well.  I had 
800,000 rows or so in the reports table but I accidentally corrupted it 
(kill -9) so I won't have that many for a few more days.

I created the separate indexex for kind and status but MySQL didn't use 
them.  It uses indexes for everything except the report.status != failed and 
then it switches to a full table scan, even if the query is a simple select 
with only the where and no join.  The documentation for MySQL indexes says 
that if MySQL thinks not using an index will be better it will not use 
indexes.

mysql> explain select * from reports WHERE reports.status = 'failed';
*** 1. row ***
   id: 1
  select_type: SIMPLE
table: reports
 type: ref
possible_keys: index_reports_on_status
  key: index_reports_on_status
  key_len: 258
  ref: const
 rows: 274
Extra: Using where
1 row in set (0.00 sec)

mysql> explain select * from reports WHERE reports.status != 'failed';
*** 1. row ***
   id: 1
  select_type: SIMPLE
table: reports
 type: ALL
possible_keys: index_reports_on_status
  key: NULL
  key_len: NULL
  ref: NULL
 rows: 108828
Extra: Using where
1 row in set (0.00 sec)

Presumably it's doing this because the number of rows that are != failed are 
the vast majority so a full table scan is actually faster.

It looks like it's selecting all the reports, and then grouping so we get 
the latest one.  Doing a cartesian join and then grouping seems extremely 
slow.  I re-wrote the query to use a sub-select:

select reports.*,nodes.* from nodes, (select node_id,max(time) from reports 
where reports.kind = 'apply' and reports.status != 'failed' GROUP by 
node_id) as reports WHERE reports.node_id = nodes.id;
1424 rows in set (0.12 sec).

So you're only getting the latest report and then the nodes for each.

How fast does that query run?

-Andrew

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

[Puppet Users] Re: Puppet Dashboard packages now available!

[Michael DeHaan]

On Tue, Apr 6, 2010 at 3:48 AM, James Turnbull  wrote:
> Hi all
>
> I've created RPM and DEB packages for the Puppet Dashboard 1.0.0rc1.
> These are available via APT and Yum repositories hosted by Puppet
> Labs.

Cool.

A puppetlabs-release RPM might be nice for this.

--Michael

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.

[Puppet Users] Re: puppet dashboard rake install aborted

[Asif Iqbal]

On Wed, Apr 7, 2010 at 1:41 PM, Asif Iqbal  wrote:
> ** Invoke db:seed (first_time)
> ** Invoke environment
> ** Execute db:seed
> rake aborted!
> no such file to load -- puppet
> /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `gem_original_require'
> /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
> /home/iqbala/puppet-dashboard/vendor/rails/activesupport/lib/active_support/dependencies.rb:156:in
> `require'

These are the gems installed

 gem list

*** LOCAL GEMS ***

abstract (1.0.0)
capistrano (2.5.9)
chef (0.7.4)
cisco (0.0.2)
erubis (2.6.5)
extlib (0.9.12)
fastthread (1.0.7)
highline (1.5.1)
json (1.1.7)
mixlib-cli (1.0.4)
mixlib-config (1.0.9)
mixlib-log (1.0.3)
net-scp (1.0.2)
net-sftp (2.0.2)
net-ssh (2.0.20, 2.0.15)
net-ssh-gateway (1.0.1)
ohai (0.3.2)
passenger (2.2.2)
rack (0.4.0)
rake (0.8.7)
ruby-openid (2.1.7)
stomp (1.1)
systemu (1.2.0)


-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.

[Puppet Users] Re: Puppet Dashboard - Directory Index Forbidden

[fsalum]

Try to add the 2 lines below inside your virtualhost


SetEnv RAILS_ENV production
RackBaseURI /
...


Don't forget to restart apache.

[]s
Felipe

On Mar 9, 6:33 am, theirpuppet  wrote:
> Hello all
>
> Puppet, puppetmaster, ruby, etc installed from standard Ubuntu 11.10 x86_64
> APT repos
> Dashboard 1.26 from .deb pulled 
> fromhttp://apt.puppetlabs.com/pool/oneiric/main/p/puppet-dashboard/
> Apache config pulled
> from /usr/share/puppet-dashboard/ext/passenger/dashboard-vhost.conf
>
> My simple test with webbrick worked a treat. So I installed Apache and
> passenger mod (from Ubuntu APT repos) and that's where I had a problem. The
> error from Apache2 error log:
>
> > [Fri Mar 09 13:09:35 2012] [error] [client 1.2.3.4] Directory index
> > forbidden by Options directive: /usr/share/puppet-dashboard/public/,
> > referer:http://[IPADDRESS]:3000/nodes/unchanged
>
> Adding Options +Indexes is not the resolution as it just displays the
> static files in that directory.
>
> Here's my /etc/apache2/sites-enabled/010-dashboard.conf:
>
> > #PassengerRoot /var/lib/gems/1.8/gems/passenger-2.2.11
> > PassengerRoot /usr/lib/phusion_passenger
> > PassengerRuby /usr/bin/ruby
> > # you may want to tune these settings
> > PassengerHighPerformance on
> > PassengerMaxPoolSize 12
> > PassengerPoolIdleTime 1500
> > # PassengerMaxRequests 1000
> > PassengerStatThrottleRate 120
> > RailsAutoDetect On
> > 
> >         ServerName FQDN
>
>         ServerAlias X.X.X.X
>
>         DocumentRoot /usr/share/puppet-dashboard/public/
>
> >         
> >                 Options None
> >                 Order allow,deny
> >                 allow from all
> >         
> >   #ErrorLog /var/log/apache2/dashboard.example.com_error.log
> >   LogLevel warn
> >   #CustomLog /var/log/apache2/dashboard.example.com_access.log combined
> >   ServerSignature On
> > 
>
> The only thing I can think of is that I had connected via IP Address, not
> FQDN. So I've updated DNS but unfortunately I don't have control over my
> employer's resolvers. Thus I have to wait until the cached failure expires
> - or bother the team responsible...
>
> Any and all ideas are welcome. I think it's either the DNS issue or
> something wrong with Passenger?
>
> Thanks
> David

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

[Puppet Users] Re: Puppet Dashboard - Directory Index Forbidden

[theirpuppet]

Thanks, however this still doesn't work.

>From error log:
[Mon Mar 19 12:29:00 2012] [error] [client X.X.X.X] Directory index 
forbidden by Options directive: /usr/share/puppet-dashboard/public/

And the current apache configuration:

root:~# cat /etc/apache2/sites-enabled/010-dashboard.conf 
# UPDATE THESE PATHS TO SUIT YOUR ENVIRONMENT
LoadModule passenger_module 
/var/lib/gems/1.8/gems/passenger-2.2.11/ext/apache2/mod_passenger.so
#PassengerRoot /var/lib/gems/1.8/gems/passenger-2.2.11
PassengerRoot /usr/lib/phusion_passenger
PassengerRuby /usr/bin/ruby

# you may want to tune these settings
PassengerHighPerformance on
PassengerMaxPoolSize 12
PassengerPoolIdleTime 1500
# PassengerMaxRequests 1000
PassengerStatThrottleRate 120
RailsAutoDetect On


ServerName X.X.X
ServerAlias X.X.X.X
DocumentRoot /usr/share/puppet-dashboard/public/
RailsBaseURI /
SetEnv Rails_ENV production
PassengerEnabled on

Options -MultiViews -Indexes FollowSymLinks
Order allow,deny
allow from all

  #ErrorLog /var/log/apache2/dashboard.example.com_error.log
  LogLevel warn
  #CustomLog /var/log/apache2/dashboard.example.com_access.log combined
  ServerSignature On



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/fgfDMT0_1xMJ.
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.

[Puppet Users] Re: Puppet dashboard not enabling inventory

[Luke]

I should point out that I restarted the dashboard service after making 
changes.

On Wednesday, January 9, 2013 10:11:11 AM UTC-4, Luke wrote:
>
> Hello,
>
> My puppet dashboard is not enabling the inventory tab / node info even 
> though I have:
>
> *enable_inventory_service set to true*
> *
> *
> *Pointing to correct port for puppetdb and server in settings.yml.*
> *
> *
> Everything is wide open in auth.conf and puppetdb is working fine. 
>
> I mean regardless of what settings are set shouldn't I at least be able to 
> see the inventory tab if *enable_inventory_service is set to true?*
> *
> *
> *Using dashboard 1.2.17.*
> *
> *
> *Thanks for all the help!*
> *
> *
> *Luke*
> *
> *
> *
> *
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/0N_ihAK2XL4J.
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.

[Puppet Users] Re: Puppet dashboard not enabling inventory

[Luke]

Has anyone else successfully got the puppet dashboard working with 
dashboard version *1.2.17 with puppet 3?*

On Wednesday, January 9, 2013 10:11:11 AM UTC-4, Luke wrote:
>
> Hello,
>
> My puppet dashboard is not enabling the inventory tab / node info even 
> though I have:
>
> *enable_inventory_service set to true*
> *
> *
> *Pointing to correct port for puppetdb and server in settings.yml.*
> *
> *
> Everything is wide open in auth.conf and puppetdb is working fine. 
>
> I mean regardless of what settings are set shouldn't I at least be able to 
> see the inventory tab if *enable_inventory_service is set to true?*
> *
> *
> *Using dashboard 1.2.17.*
> *
> *
> *Thanks for all the help!*
> *
> *
> *Luke*
> *
> *
> *
> *
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/RF_qPkwdTE0J.
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.

[Puppet Users] Re: Puppet dashboard not enabling inventory

[Stefan Heijmans]

>>I mean regardless of what settings are set shouldn't I at least be able 
to see the inventory tab if enable_inventory_service is set to true?
Yes if you mean the one on top of the screen
If you click on a node when it's not configured correctly it shows;
Inventory
Could not retrieve facts from inventory service: getaddrinfo: Name or 
service not known

>>Pointing to correct port for puppetdb and server in settings.yml
my inventory_server & inventory_port parameters points to  

>>Has anyone else successfully got the puppet dashboard working with 
dashboard version 1.2.17 with puppet 3?
Yes on rhel63 with
puppet 3.0.2
puppet dashboard 1.2.18
puppetdb 1.0.5

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/QPUP0oc6Gy0J.
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.

[Puppet Users] Re: Puppet dashboard not enabling inventory

[Luke]

Thank you for your reply.

I am confused as to why it is not working then. I have this set exactly 
like this in my settings:

enable_inventory_service: true


It is like it isn't recognizing this setting. I have updated my dashboard 
to the same version as you with no change.

On Thursday, January 10, 2013 5:16:30 PM UTC-4, Stefan Heijmans wrote:
>
> >>I mean regardless of what settings are set shouldn't I at least be able 
> to see the inventory tab if enable_inventory_service is set to true?
> Yes if you mean the one on top of the screen
> If you click on a node when it's not configured correctly it shows;
> Inventory
> Could not retrieve facts from inventory service: getaddrinfo: Name or 
> service not known
>
> >>Pointing to correct port for puppetdb and server in settings.yml
> my inventory_server & inventory_port parameters points to  server> 
>
> >>Has anyone else successfully got the puppet dashboard working with 
> dashboard version 1.2.17 with puppet 3?
> Yes on rhel63 with
> puppet 3.0.2
> puppet dashboard 1.2.18
> puppetdb 1.0.5
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/CVP1VZP7M6EJ.
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.

[Puppet Users] Re: puppet dashboard run time problems

[Matt John]

+1

On Thursday, December 20, 2012 10:23:25 AM UTC, Jacob wrote:
>
> Hello all,
>
> I just noticed that in my dashboard the "Run Time" graph shows really 
> weird output.  It seems like it is different for different nodes. For some 
> nodes, it doesn't seem to be updating, and for others it graphs values that 
> are wrong.  The "recent report" table seems to be correct however.
>
> Has anyone seen this or have any pointers?
>
> Thanks
>
> //Jacob.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/9b-k6twxjVgJ.
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.

[Puppet Users] Re: Puppet dashboard stuck pending jobs

[Jagga Soorma]

Thanks for pointing me to the log location.  Looks like this might be the 
cause of the problem:

--
..snip
2013-02-10T10:40:35-0800: [Worker(delayed_job.3 host:ssfpcond01 pid:25048)] 
Report.create_from_yaml_file failed with ActiveRecord::StatementInvalid: 
*Mysql::Error: 
Data too long for column 'details' at row 1: INSERT INTO 
`delayed_job_failures` *(`summary`, `read`, `updated_at`, `backtrace`, 
`details`, `created_at`) VALUES('Importing report report-18121-1179.
yaml', 0, '2013-02-10 18:40:35', '--- \n- 
/usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/connection_adapters/a
..snip..
--

I am managing my passwd & group file via puppet which at times have huge 
amount of changes especially in the group file.  This could possibly be 
causing this error.  Is there a way to increase the size of the details 
column to enable it to accept larger data?

Has anyone seen this issue before?

Thanks again for your help with this.

On Friday, February 8, 2013 1:53:02 PM UTC-8, Jagga Soorma wrote:
>
> Hi Guys,
>
> I am a new puppet user and wanted some type of monitoring for puppet so 
> deployed puppet-dashboard.  It has been working very well for a few days 
> not, but all of a sudden I start getting pending tasks and they never 
> finish even after restarting all processes.  They keep accumulating and 
> never seem to finish even though the clients are running fine.  I have the 
> puppet-dashboard running on a different server than my puppetmaster.  Is 
> there any way to troubleshoot what seems to be stuck and how to I get it 
> going without having to destroy the dashboard mysql db and recreating it 
> again?  That is the only way I have got it working again but that is not 
> the correct way of doing this :)  Any help would be appreciated.
>
> Thanks!
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet dashboard stuck pending jobs

[Jagga Soorma]

Looks like that was actually the problem.  Searched google and came across 
the fix.  Had to change the type of the messages column to mediumtext and 
the pending jobs started finishing.  Did this by:

alter table report_logs change column message message VARCHAR(65536);

Just in case someone runs into this issue.  Thanks.

On Sunday, February 10, 2013 10:56:14 AM UTC-8, Jagga Soorma wrote:
>
> Thanks for pointing me to the log location.  Looks like this might be the 
> cause of the problem:
>
> --
> ..snip
> 2013-02-10T10:40:35-0800: [Worker(delayed_job.3 host:ssfpcond01 
> pid:25048)] Report.create_from_yaml_file failed with 
> ActiveRecord::StatementInvalid: *Mysql::Error: Data too long for column 
> 'details' at row 1: INSERT INTO `delayed_job_failures` *(`summary`, 
> `read`, `updated_at`, `backtrace`, `details`, `created_at`) 
> VALUES('Importing report report-18121-1179.
> yaml', 0, '2013-02-10 18:40:35', '--- \n- 
> /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/connection_adapters/a
> ..snip..
> --
>
> I am managing my passwd & group file via puppet which at times have huge 
> amount of changes especially in the group file.  This could possibly be 
> causing this error.  Is there a way to increase the size of the details 
> column to enable it to accept larger data?
>
> Has anyone seen this issue before?
>
> Thanks again for your help with this.
>
> On Friday, February 8, 2013 1:53:02 PM UTC-8, Jagga Soorma wrote:
>>
>> Hi Guys,
>>
>> I am a new puppet user and wanted some type of monitoring for puppet so 
>> deployed puppet-dashboard.  It has been working very well for a few days 
>> not, but all of a sudden I start getting pending tasks and they never 
>> finish even after restarting all processes.  They keep accumulating and 
>> never seem to finish even though the clients are running fine.  I have the 
>> puppet-dashboard running on a different server than my puppetmaster.  Is 
>> there any way to troubleshoot what seems to be stuck and how to I get it 
>> going without having to destroy the dashboard mysql db and recreating it 
>> again?  That is the only way I have got it working again but that is not 
>> the correct way of doing this :)  Any help would be appreciated.
>>
>> Thanks!
>>
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: puppet dashboard enc default group

[vioilly]

Does anyone know if this works? I have tested it and it is not working for 
me but I see this:

http://projects.puppetlabs.com/issues/4412


Cheers,
Oli

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: puppet dashboard enc default group

[vioilly]

I found another way of doing this. A workaround but I found that I could 
add all the nodes to a default group via a rake task as follows:

*sudo -u puppet-dashboard RAILS_ENV=production rake -f  
/usr/share/puppet-dashboard/Rakefile nodegroup:add_all_nodes group=default
*
I am running that rake task via jenkins on a scheduled basis*.*

Unless anyone else has a better way, that will do for now.* *If you do know 
if that feature request got implemented, then please reply*
*

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet dashboard suddenly stopped working

[Corey Hammerton]

Is the puppet-dashboard-workers service running?

On Friday, August 10, 2012 4:26:20 PM UTC-4, Anatoliy Lisovskiy (Wavebourn) 
wrote:
>
> Today I found that puppet dashboard does not work since Aug,1
>
> It shows all 23 hosts as being non-responsive, and 8,000+ pending tasks. 
> Both server and agents work well, but the dashboard does not reflect that.
>
> What could go wrong? I restarted puppet-db and puppet-dashboard, did not 
> help.
>
> Anatoliy
>
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/ALOzlEUt7I8J.
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.

[Puppet Users] Re: Puppet Dashboard/DB Inventory (Detach?)

[tsuave]

Also, if I try to stop the service from said putty session (the one that 
the output is being sent to, I get this error:

 * Stopping Puppet Dashboard   
 [2012-08-20 09:42:21] ERROR 
SignalException: SIGTERM
/usr/lib/ruby/1.8/webrick/server.rb:91:in `select'

I did find, however, that if I start the service with:
puppet resource service puppet-dashboard ensure=running enable=true
The dashboard will start and inventory will work even when puty is closed 
as the output is no longer sent to the terminal (since puppet started it 
and not my root instance)
The problem is solved, but I am still curious how to detach when using the 
init.d scripts.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/4OmJqngaBxMJ.
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.

[Puppet Users] Re: Puppet Dashboard/DB Inventory (Detach?)

[jonauman]

Hi,

FIrst, sorry for not sending a patch file. I did not save the original init.d 
scripts before I hacked it.
I also had the same issues on debian. Here's what I did to resolve it:

1) add "-s INT" to the stop and stop portion of the restart functions. The 
default is to send a term signal, but you need to send kill or int signal to 
get it to go away.

stop)
log_daemon_msg "Stopping Puppet Dashboard"
if start-stop-daemon --stop -s INT --quiet --oknodo --pidfile 
${PIDFILE} --user ${DASHBOARD_USER} --retry 10; then

2) Remove the & in the start script and replace with -d. This will prevent all 
the messages going to console.

start_puppet_dashboard() {
start-stop-daemon --start --quiet --oknodo --make-pidfile --pidfile 
${PIDFILE} --user ${DASHBOARD_USER} --chuid ${DASHBOARD_USER} --exec 
${DASHBOARD_RUBY} -- ${DASHBOARD_HOME}/script/server -e 
${DASHBOARD_ENVIRONMENT} -p ${DASHBOARD_PORT} -b ${DASHBOARD_IFACE} -d

3) I commented out  check_puppet_dashboard_status in start_puppet_dashboard() 
function since it was giving bogus failure messages.

I also had issues with the init script killing the puppetmaster as well but 
leaving its pid file, but that seemed to go away once I daemonized the 
dashboard.  Not sure why the two were tied together.

Hope that helps.

-Jon

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/BSd1OY4QxjcJ.
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.

[Puppet Users] Re: Puppet Dashboard for Rails 3

[Aaron Stone]

I've added Devise and OmniAuth, starting with configs for Google OAuth2
(compatible with and can be restricted to apps-for-your-domain) on this
branch:

https://github.com/sodabrew/puppet-dashboard/tree/rails3-aaa

Next week I will tie logins to who-changed-what-and-when accounting,
followed by viewer/editor/admin access levels.

Cheers,
Aaron



On Fri, Nov 9, 2012 at 4:30 PM, Aaron Stone  wrote:

> Hi all,
>
> Over the past few weeks, I ported the Puppet Dashboard to run on Rails 3
> with Ruby 1.8.7. I'm down to only three unit test failures, so I think it's
> a good time to share the work and see if anybody else is interested in
> continuing Dashboard with me.
>
> http://github.com/sodabrew/puppet-dashboard
>
> https://travis-ci.org/sodabrew/puppet-dashboard/jobs/3095051
>
> What's new here?
>  - Rails 3.2.8!
>  - Model protection against mass-assignment attacks.
>  - Prototype JS is removed.
>  - URLs for Groups and Classes by name, not only ID number.
>  - Bundler 1.x, Gemfile, runs under Thin.
>
> My next plans:
>  - Use PaperTrail to provide change histories for everything (way more
> than fact reports, I need "who changed this parameter?").
>  - Use Devise for AAA, integration with company Auth and view/edit
> permissions (e.g. Devs can view, Ops can edit).
>  - Make it prettier? Bootstrap perhaps?
>  - Unit tests passing ;)
>
> Cheers,
> Aaron
>

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

[Puppet Users] Re: Puppet Dashboard for Rails 3

[Joshua Bussdieker]

Awesome! I had that thought myself :)

On Tuesday, November 20, 2012 11:10:38 AM UTC-8, Aaron Stone wrote:
>
> I've added Devise and OmniAuth, starting with configs for Google OAuth2 
> (compatible with and can be restricted to apps-for-your-domain) on this 
> branch:
>
> https://github.com/sodabrew/puppet-dashboard/tree/rails3-aaa
>
> Next week I will tie logins to who-changed-what-and-when accounting, 
> followed by viewer/editor/admin access levels.
>
> Cheers,
> Aaron
>
>
>
> On Fri, Nov 9, 2012 at 4:30 PM, Aaron Stone 
> > wrote:
>
>> Hi all,
>>
>> Over the past few weeks, I ported the Puppet Dashboard to run on Rails 3 
>> with Ruby 1.8.7. I'm down to only three unit test failures, so I think it's 
>> a good time to share the work and see if anybody else is interested in 
>> continuing Dashboard with me.
>>
>> http://github.com/sodabrew/puppet-dashboard
>>
>> https://travis-ci.org/sodabrew/puppet-dashboard/jobs/3095051
>>
>> What's new here?
>>  - Rails 3.2.8!
>>  - Model protection against mass-assignment attacks.
>>  - Prototype JS is removed.
>>  - URLs for Groups and Classes by name, not only ID number.
>>  - Bundler 1.x, Gemfile, runs under Thin.
>>
>> My next plans:
>>  - Use PaperTrail to provide change histories for everything (way more 
>> than fact reports, I need "who changed this parameter?").
>>  - Use Devise for AAA, integration with company Auth and view/edit 
>> permissions (e.g. Devs can view, Ops can edit).
>>  - Make it prettier? Bootstrap perhaps?
>>  - Unit tests passing ;)
>>
>> Cheers,
>> Aaron
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/O4fdHxPiJFIJ.
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.

[Puppet Users] Re: Puppet Dashboard for Rails 3

[Aaron Stone]

Update: thanks to help from GitHub users @igreg and @astratto, Puppet
Dashboard Rails 3 is now fully compatible with Ruby 1.9! The rails3 and
rails3-aaa branches are up to date as of Dashboard version 1.2.15 plus the
work on those branches.

I'm down to just 3 test failures, and actively working on getting to fully
clean test runs. Help appreciated! Please take a look at the test results
from these Travis builds:
https://travis-ci.org/sodabrew/puppet-dashboard/builds/3588533

Still working on the audit trail, but no new updates on that yet.

Cheers,
Aaron



On Fri, Nov 9, 2012 at 4:30 PM, Aaron Stone  wrote:

> Hi all,
>
> Over the past few weeks, I ported the Puppet Dashboard to run on Rails 3
> with Ruby 1.8.7. I'm down to only three unit test failures, so I think it's
> a good time to share the work and see if anybody else is interested in
> continuing Dashboard with me.
>
> http://github.com/sodabrew/puppet-dashboard
>
> https://travis-ci.org/sodabrew/puppet-dashboard/jobs/3095051
>
> What's new here?
>  - Rails 3.2.8!
>  - Model protection against mass-assignment attacks.
>  - Prototype JS is removed.
>  - URLs for Groups and Classes by name, not only ID number.
>  - Bundler 1.x, Gemfile, runs under Thin.
>
> My next plans:
>  - Use PaperTrail to provide change histories for everything (way more
> than fact reports, I need "who changed this parameter?").
>  - Use Devise for AAA, integration with company Auth and view/edit
> permissions (e.g. Devs can view, Ops can edit).
>  - Make it prettier? Bootstrap perhaps?
>  - Unit tests passing ;)
>
> Cheers,
> Aaron
>

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

[Puppet Users] Re: puppet dashboard certificate request fails

[Bernhard Efler]

Hi!

I got the same problem. Has someone a solution for this?

thanks

Am Freitag, 2. August 2013 22:37:36 UTC+2 schrieb espe:
>
> Hi,
> if I send the certificate request from puppet dashboard to the puppet 
> master, I get the error
>
> SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: 
> certificate verify failed
>
> The master log gives me this message:
>
> [2013-08-02 22:28:22] ERROR OpenSSL::SSL::SSLError: SSL_accept returned=1 
> errno=0 state=SSLv3 read client certificate A: tlsv1 alert unknown ca
> 
> /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/network/http/webrick.rb:34:in 
> `accept'
> 
> /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/network/http/webrick.rb:34:in 
> `block (3 levels) in listen'
> /usr/lib64/ruby/1.9.1/webrick/server.rb:191:in `call'
> /usr/lib64/ruby/1.9.1/webrick/server.rb:191:in `block in 
> start_thread'
>
> The puppet setup at all works fine. A have a lot of nodes connecting 
> without problems to the master. The puppet dashboard runs on the same host 
> like the puppet master. The dashboards collects reports successfully, too.
>
> It's openSuSE 12.2 with puppet 3.2.2, puppet-dashboard 1.2.23, ruby 
> 1.9.3p392 and rake 0.9.2.2.
>
> Can anybody help?
>
> Thanks!
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet dashboard data internally inconsistent

[Sam Tresler]

I should add, nothing in logs of puppet master or dashboard. 

On Tuesday, November 26, 2013 11:39:34 AM UTC-5, Sam Tresler wrote:
>
>
> https://www.dropbox.com/s/0vao04js5v7edga/Screenshot%20-%2011262013%20-%2011%3A31%3A35%20AM.png
>
> In the attached screenshot you can see that the last report was 10:07. The 
> graph definitely shows an 11:36 run, and the dashboard activity shows that 
> the nod was updated at 11:05. 
>
> Puppet dashboard is getting reports from over 300 nodes. CPU is maxed, but 
> pending tasks are consistently 1-2, and the machine isn't overloaded. Came 
> in this morning to 80ish Unreported Nodes. Most nodes are still reporting 
> and not exhibiting this behavior. The nodes in showing as unreported all 
> have similar traits as the screenshot - data is getting to the dashboard 
> somehow, but dashboard is not registering it as a report. 
>
> Any ideas what is going on here? 
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/7741e1d1-a171-458f-a22c-b4422990dabc%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet Dashboard: how to connect?

[Stuart Cracraft]

yum install puppet-dashboard gives a requirement for dependency resolution:

  Error: Package: puppet-dashboard-1.2.23-1.el6.noarch (puppetlabs)
 Requires: rubygem(rake)

My question is, how to install rubygem so that puppet-dashboard installs?

Stuart

On Friday, December 13, 2013 9:25:55 AM UTC-8, Stuart Cracraft wrote:

> Hi - I run puppet 3.3.2 currently of Open Source Puppet.
>
> I am looking for anyone who has run Puppet Dashboard.
>
> How do I connect to the dashboard?
>
> Stuart
>
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/b501fed0-1922-4445-b577-1d212c70970d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet Dashboard: how to connect?

[Stuart Cracraft]

Okay, now puppet-dashboard is installed on my Puppet Master and I am ready 
and ripe.

How do I access the dashboard?


-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/0f180467-733b-4c4d-8dca-c919823cba27%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: puppet dashboard group and class

[Suresh P]

Hi Nicolas,

I too have the same issue.  Do you have doc to enable external_node feature.

Thanks,
Suresh


On Wednesday, 15 December 2010 06:47:24 UTC+5:30, Nicolas Aizier wrote:
>
> Hi everyone, 
>
> I'm actually kind of new in puppet but I'm doing good in progressing. 
> I have read lot of docs and how to to understand the whole behaviour 
> of puppet. 
> Installed a puppet master server, deployed 15 clients to test it on 
> some of our testing servers. 
> Written modules to get exactly what we want, and then installed puppet 
> dashboard which work really fine. 
>
> My question might sound a bit noobish but I'm stuck on that point and 
> I really don't like to don't understand every part of a tool. 
> What is the use of adding "groups" and "class" in the dashboard ? 
> It seems that the dashboard don't see your class from the modules (saw 
> that it will be corrected soon), but what is the point to creating 
> class in the GUI ? Can you do anything with that ? and if yes will 
> that not spread the config through dashboard + puppet config files, 
> it'll be messy to maintain  
> Same question with the groups, I understand that you can assign class 
> to groups so it's easyer to add a server in a global behavior but it 
> only uses class from dashboard . And is there a way to create such 
> group in puppet config files (if yes I didn't manage to find it ...) ? 
>
> Thx a lot for your time and to all the puppet users !

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/6648be15-2a83-46af-b3e1-692c139a8a3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: puppet dashboard group and class

[Stefan Heijmans]

this one?
http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#using-dashboard-for-node-classification
 

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/309dec2c-7ec9-4713-abe5-d89c58326d45%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet Dashboard - Directory Index Forbidden

[Kiran Sysadm]

Hello all,

I also have similar issue with launching the Puppet Dashboard UI, Below is 
my config file. Please can anyone help me on this issue.

Error I am getting : [Thu Aug 20 05:25:09 2015] [error] [client 
192.168.XXX.XXX] Directory index forbidden by Options directive: 
/usr/share/puppet-dashboard/public/
Below is my VirtualHost file.

# UPDATE THESE PATHS TO SUIT YOUR ENVIRONMENT
#LoadModule passenger_module 
/var/lib/gems/1.8/gems/passenger-2.2.11/ext/apache2/mod_passenger.so
PassengerRoot /usr/lib/ruby/gems/1.8/gems/passenger-5.0.15
PassengerRuby /usr/
#PassengerRuby /usr/bin/ruby

# you may want to tune these settings
PassengerHighPerformance on
PassengerMaxPoolSize 12
PassengerPoolIdleTime 1500
# PassengerMaxRequests 1000
PassengerStatThrottleRate 120
#RailsAutoDetect On
Listen 3000


ServerName puppetma.domain.net
ServerAlias puppetma
DocumentRoot /usr/share/puppet-dashboard/public/

Options None
Order allow,deny
allow from all

  ErrorLog /var/log/httpd/puppet-dashboard_error.log
  LogLevel warn
  CustomLog /var/log/httpd/puppet-dashboard_access.log combined
  ServerSignature On

I could see my DNS is absolutely working fine,  I have also ensured 
stopping my host level firewall and selinux.

Thanks,
Kiran

On Friday, March 9, 2012 at 5:33:23 AM UTC-8, theirpuppet wrote:
>
> Hello all
>  
> Puppet, puppetmaster, ruby, etc installed from standard Ubuntu 11.10 
> x86_64 APT repos 
> Dashboard 1.26 from .deb pulled from 
> http://apt.puppetlabs.com/pool/oneiric/main/p/puppet-dashboard/
> Apache config pulled 
> from /usr/share/puppet-dashboard/ext/passenger/dashboard-vhost.conf
>
> My simple test with webbrick worked a treat. So I installed Apache and 
> passenger mod (from Ubuntu APT repos) and that's where I had a problem. The 
> error from Apache2 error log: 
>
>> [Fri Mar 09 13:09:35 2012] [error] [client 1.2.3.4] Directory index 
>> forbidden by Options directive: /usr/share/puppet-dashboard/public/, 
>> referer: http://[IP ADDRESS]:3000/nodes/unchanged
>
>
> Adding Options +Indexes is not the resolution as it just displays the 
> static files in that directory.
>  
> Here's my /etc/apache2/sites-enabled/010-dashboard.conf:
>
>> #PassengerRoot /var/lib/gems/1.8/gems/passenger-2.2.11
>> PassengerRoot /usr/lib/phusion_passenger
>> PassengerRuby /usr/bin/ruby
>> # you may want to tune these settings
>> PassengerHighPerformance on
>> PassengerMaxPoolSize 12
>> PassengerPoolIdleTime 1500
>> # PassengerMaxRequests 1000
>> PassengerStatThrottleRate 120
>> RailsAutoDetect On
>> 
>> ServerName FQDN
>>
> ServerAlias X.X.X.X 
>
> DocumentRoot /usr/share/puppet-dashboard/public/
>> 
>> Options None
>> Order allow,deny
>> allow from all
>> 
>>   #ErrorLog /var/log/apache2/dashboard.example.com_error.log
>>   LogLevel warn
>>   #CustomLog /var/log/apache2/dashboard.example.com_access.log combined
>>   ServerSignature On
>> 
>
>
> The only thing I can think of is that I had connected via IP Address, not 
> FQDN. So I've updated DNS but unfortunately I don't have control over my 
> employer's resolvers. Thus I have to wait until the cached failure expires 
> - or bother the team responsible... 
>
> Any and all ideas are welcome. I think it's either the DNS issue or 
> something wrong with Passenger?
>
> Thanks
> David
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/40040503-7f10-438b-9e36-9e0f5cb6d2f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet Dashboard or Forman on SLES?

[Benjamin]

Hi,
thx this package could be installed on SLES.

I tried to use this guide
http://docs.puppetlabs.com/guides/installing_dashboard.html

Setup a MySQL database server, create a user and database for use with
the Dashboard by either:

   1.

  Using a rake task to create just the database from settings in
the
config/database.yml file. You must cd into the directory with the
Puppet
Dashboard software containing this README.markdown file before running
these commands:

But after this point i get this error message:

rake RAILS_ENV=production db:create --trace
rake aborted!
no such file to load -- spec/rake/spectask
/usr/lib64/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:29:in
`gem_original_require'
/usr/lib64/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:29:in
`require'
/usr/share/puppet-dashboard/vendor/gems/haml-3.1.2/vendor/sass/vendor/
fssm/Rakefile:20
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2.2/lib/rake/rake_module.rb:
25:in
`load'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2.2/lib/rake/rake_module.rb:
25:in
`load_rakefile'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2.2/lib/rake/application.rb:
501:in `raw_load_rakefile'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2.2/lib/rake/application.rb:
82:in
`load_rakefile'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2.2/lib/rake/application.rb:
133:in `standard_exception_handling'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2.2/lib/rake/application.rb:
81:in
`load_rakefile'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2.2/lib/rake/application.rb:
65:in
`run'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2.2/lib/rake/application.rb:
133:in `standard_exception_handling'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2.2/lib/rake/application.rb:
63:in
`run'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2.2/bin/rake:33
/usr/bin/rake:19:in `load'
/usr/bin/rake:19

I searched in Google but the solution "you need to install the rspec
gem" don't resolve my problem.

Best regards

Benjamin

On 11 Dez., 14:30, Darin Perusich  wrote:
> Mike,
>
> I'd recommend pulling down the SRPM from the Open(SuSE) Build Service if
> you're thinking about at building packages for SuSE. Ben has put a lot of
> work and effort into packaging for Puppet and the dashboard on SuSE
> systems. We've SuSE'fied the init scripts, added them for the dashboard
> worker processes, etc. Also using the magic of the build service it's
> trivial to build the packages for other distributions.
>
> http://download.opensuse.org/repositories/home:/eclipseagent:/puppet/...https://build.opensuse.org/package/show?package=puppet-dashboard&proj...
>
> --
> Later,
> Darin
>
> On Fri, Dec 9, 2011 at 10:18 PM, Michael Stahnke 
> wrote:
>
> > Thanks.  I'll tackle this next week.
>
> > Mike
>
> > On Fri, Dec 9, 2011 at 2:42 PM, Jeffrey Watts 
> > wrote:
> > > Here you go:
>
> > > $ diff puppet-dashboard.spec puppet-dashboard.spec-sles
> > > 2c2
> > > < %global initrddir /etc/rc.d/init.d
> > > ---
> > >> %global initrddir /etc/init.d
> > > 9c9
> > > < Release:        1%{?dist}
> > > ---
> > >> Release:        2%{?dist}
> > > 17,18c17,18
> > > < Requires:       ruby(abi) = 1.8, rubygems, ruby-mysql
> > > < Requires:       ruby > 1.8.7, rubygem(rake)
> > > ---
> > >> Requires:       rubygems, ruby-mysql
> > >> Requires:       ruby > 1.8.7, rubygem-rake
> > > 22,25d21
> > > < Requires(post):   chkconfig
> > > < Requires(preun):  chkconfig
> > > < Requires(preun):  initscripts
> > > < Requires(postun): initscripts
> > > 137a134,136
> > >> * Wed Dec 07 2011 Jeffrey Watts  - 1.2.3-2
> > >> - Modified it to work on SLES
>
> > > Jeffrey.
>
> > > On Fri, Dec 9, 2011 at 3:35 PM, Michael Stahnke <
> > stah...@fedoraproject.org>
> > > wrote:
>
> > >> If somebody has a spec file that is working pretty well for SLES and/or
> > >> OpenSUSE we'd be glad to look at it and potentially host packages for
> > it.
> > >> It's on the list of things to do, it just hasn't made it to the top yet.
>
> > >> Mike
>
> > > --
> > > 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.
>
> > --
> > 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.

-- 
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/grou

[Puppet Users] Re: puppet dashboard and 64-bit mysql

[Tim]

Thanks for the suggestion. I tried, oh maybe a hundred or so
variations of installing that gem, trying an earlier version and even
downloading the source and trying it that way. No dice. It simply
won't compile against the 64-bit mysql libraries. I'm not even sure it
was understanding the ARCHFLAGS variable. It could be that there's
specific syntax for use on Solaris that I wasn't using. I tried using
env ARCHFLAGS and export ARCHFLAGS, even just setting the variable
normally via the standard declaration/export.

I was able to build it against the 32-bit libraries, but then the
dashboard install fails.

Seems strange to me though. Puppet seems to be designed to manage
servers at an enterprise level, so all of my machines are 64-bit and
most of the apps they run are 64-bit, so why would I have to install a
32-bit MySQL database just to run the puppet dashboard?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.

[Puppet Users] Re: puppet dashboard and 64-bit mysql

[deet]

> env ARCHFLAGS and export ARCHFLAGS, even just setting the variable
> normally via the standard declaration/export.

  Tim.
 From your original post I'm assuming your using "cc" from sun
studio.  If that's the case I use the following when I need to compile
something against my 64 bit mysql package ( say php for example).

CC=cc CFLAGS="-xtarget=generic -m64 -xO4" CXX="CC" CXXFLAGS="-
xtarget=generic -m64 -xO4" LDFLAGS="-m64"

 Are you setting the "-m64" flags like in the above example?
Installing puppet dashboard on Solaris is on my list of things to do
but not in the immediate future.So if you do get through it and
generate some special incantations i'd love to see them:)
 HTH.  Derek.

>
> I was able to build it against the 32-bit libraries, but then the
> dashboard install fails.
>
> Seems strange to me though. Puppet seems to be designed to manage
> servers at an enterprise level, so all of my machines are 64-bit and
> most of the apps they run are 64-bit, so why would I have to install a
> 32-bit MySQL database just to run the puppet dashboard?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.

[Puppet Users] Re: Puppet-dashboard ActiveRecord::Base (nil object)

[Forrie]

This appears to be a problem with data that got stored in the database
during the migration as I was able to duplicate the error on a fresh
installation of 1.0.4.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.

[Puppet Users] Re: Puppet dashboard don't show current day

[ssiefkas]

I am also having issues with today not showing in the daily run status
graph.  The reports are coming in normally and are up to date.  I am
on dashboard 1.0.4.

On Jan 18, 11:14 pm, Nicolas Aizier 
wrote:
> Now that I've been running dashboard for more than 30 days puppet
> dashboard daily run status show me the last 30 days fully. Which said
> like this is good.
> But it only show me the "day-30" to "day-1", and no more the current
> one.
>
> I'm sure everything is fine since just under that in the "Recently-
> reported nodes" I see all the reports passing. I can also see them in
> the "reports" tabs.
>
> Is anyone having the same issue ? It's not big but it's annoying to
> not be able to see the current day status.
>
> Cheers.

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

[Puppet Users] Re: Puppet dashboard don't show current day

[Nicolas Aizier]

I made some more research on this problem and found another one. I
think it's linked.

The 30th day of puppet (the one the more on the left side in puppet-
dashboard) is slowly decrasing in term of successfull reports. So the
chart for this day is slowly decreasing as long as the day go on.
I guess, but I'm absolutely not sure, that the extract for the 30 days
is straight. I mean it takes 30 times 24H so as you day goes on the
30th day go by.
I think that's a bug since it can lead you to think that you had a
problem for this day.

So to be completely clear the graph :
- takes day -31 to -1 but not the current one
- is managing the -31 day as running and only show the reports
depending on current time.

I'll have a look in bug to see if I got to log something.

On Jan 22, 4:16 am, ssiefkas  wrote:
> I am also having issues with today not showing in the daily run status
> graph.  The reports are coming in normally and are up to date.  I am
> on dashboard 1.0.4.
>
> On Jan 18, 11:14 pm, Nicolas Aizier 
> wrote:
>
>
>
>
>
>
>
> > Now that I've been running dashboard for more than 30 days puppet
> > dashboard daily run status show me the last 30 days fully. Which said
> > like this is good.
> > But it only show me the "day-30" to "day-1", and no more the current
> > one.
>
> > I'm sure everything is fine since just under that in the "Recently-
> > reported nodes" I see all the reports passing. I can also see them in
> > the "reports" tabs.
>
> > Is anyone having the same issue ? It's not big but it's annoying to
> > not be able to see the current day status.
>
> > Cheers.

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

[Puppet Users] Re: Puppet dashboard don't show current day

[Nicolas Aizier]

Raised bug #5983 about those points.

On Jan 24, 11:43 am, Nicolas Aizier 
wrote:
> I made some more research on this problem and found another one. I
> think it's linked.
>
> The 30th day of puppet (the one the more on the left side in puppet-
> dashboard) is slowly decrasing in term of successfull reports. So the
> chart for this day is slowly decreasing as long as the day go on.
> I guess, but I'm absolutely not sure, that the extract for the 30 days
> is straight. I mean it takes 30 times 24H so as you day goes on the
> 30th day go by.
> I think that's a bug since it can lead you to think that you had a
> problem for this day.
>
> So to be completely clear the graph :
> - takes day -31 to -1 but not the current one
> - is managing the -31 day as running and only show the reports
> depending on current time.
>
> I'll have a look in bug to see if I got to log something.
>
> On Jan 22, 4:16 am, ssiefkas  wrote:
>
>
>
>
>
>
>
> > I am also having issues with today not showing in the daily run status
> > graph.  The reports are coming in normally and are up to date.  I am
> > on dashboard 1.0.4.
>
> > On Jan 18, 11:14 pm, Nicolas Aizier 
> > wrote:
>
> > > Now that I've been running dashboard for more than 30 days puppet
> > > dashboard daily run status show me the last 30 days fully. Which said
> > > like this is good.
> > > But it only show me the "day-30" to "day-1", and no more the current
> > > one.
>
> > > I'm sure everything is fine since just under that in the "Recently-
> > > reported nodes" I see all the reports passing. I can also see them in
> > > the "reports" tabs.
>
> > > Is anyone having the same issue ? It's not big but it's annoying to
> > > not be able to see the current day status.
>
> > > Cheers.

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

Re: [Puppet Users] Re: Puppet Dashboard packages now available!

[James Turnbull]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 7/04/10 10:38 AM, Michael DeHaan wrote:
> On Tue, Apr 6, 2010 at 3:48 AM, James Turnbull  
> wrote:
>> Hi all
>>
>> I've created RPM and DEB packages for the Puppet Dashboard 1.0.0rc1.
>> These are available via APT and Yum repositories hosted by Puppet
>> Labs.
> 
> Cool.
> 
> A puppetlabs-release RPM might be nice for this.

On the list.

Regards

James Turnbull

- -- 
Author of:
* Pro Linux System Administration (http://tinyurl.com/linuxadmin)
* Pulling Strings with Puppet (http://tinyurl.com/pupbook)
* Pro Nagios 2.0 (http://tinyurl.com/pronagios)
* Hardening Linux (http://tinyurl.com/hardeninglinux)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBS7vUniFa/lDkFHAyAQK45QgA5R4nCKx71vhKIye/2U6OigRUje0+pFAD
Ea/uuxfBCX4ZuuAv7lzGD4C7SdYZj1eHyK7+CYtJ4gkyV8WKrzpGJMYCl3S0IIot
DPxa5rJCzaJL5AcrgOn4Tyl3wrlY+BldiRk1lRTPwf6ZPOPZl5/Zosw6tisVMPq/
YtNK1vDZu/cTB96q2GeniQlZ1LZ8fYvNNuuxqAxqzqpaDKi5HJkR+AoCMZXzKTNx
VJ1bjkrYYdW9wdBWLBh7YEdHUCrobavEoSJLC1I13QLcaN/iSzIJB0x2mhb/PJO2
y+Gh9/4tbKzWeEtzsBvuEYyNls4BucEYr89MFUr2mhYeI+nix5qMgQ==
=zQIi
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.

Re: [Puppet Users] Re: Puppet Dashboard packages now available!

[James Turnbull]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 7/04/10 10:38 AM, Michael DeHaan wrote:
> On Tue, Apr 6, 2010 at 3:48 AM, James Turnbull  
> wrote:
>> Hi all
>>
>> I've created RPM and DEB packages for the Puppet Dashboard 1.0.0rc1.
>> These are available via APT and Yum repositories hosted by Puppet
>> Labs.
> 
> Cool.
> 
> A puppetlabs-release RPM might be nice for this.

I've created and update a puppetlabs-repo RPM at:

http://yum.puppetlabs.com/base/puppetlabs-repo-1.0-1.noarch.rpm

That adds the Puppet Labs GPG key and a puppetlabs.repo file.

Regards

James Turnbull

- -- 
Author of:
* Pro Linux System Administration (http://tinyurl.com/linuxadmin)
* Pulling Strings with Puppet (http://tinyurl.com/pupbook)
* Pro Nagios 2.0 (http://tinyurl.com/pronagios)
* Hardening Linux (http://tinyurl.com/hardeninglinux)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBS7vYdiFa/lDkFHAyAQIBNQf+PrpQWXeVM3Zx5VbsmT3YKkDS3Zqrl3zk
/VioFeJoBoR6/RERvFOh6h0Y5Iu/Rgnjcr2eODiCAcGI0k9g6Vy4MytxtlLo8RPW
lo4+YVB+KxbZpT1g6JSVRm5ZYxq+NCURCVYFdc01uiIs4RYgCtqw8PMwc0G94ewW
PzrWBFqnUVKbfRUdgJlcwBSxrhfetkR/RJsBYFYgWGlbJTnyzZdO1j7rPkSytKbH
7ntiBIOkCyAhsxHqW4vw46npkm/i7iaMOBw1WKjhdVog7IaTod2rZIzdQxuO8vIG
YdqLhUGi4WLyaL8xovREseQFaQ9bQ0RIIPC35xZkoSTL8vL2oZTZgQ==
=QC8W
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.

Re: [Puppet Users] Re: Puppet Dashboard - Directory Index Forbidden

[Antidot SAS]

HI,

I had exactly the same issue last week when I wanted to create a vhost for
the puppet dashboard, I finally wasn't able to resolve the issue. And if
you change the directive in '+Indexes', the ruby code is not correctly
executed.


Any help is alos appareached.

Regards,
JM

On Mon, Mar 19, 2012 at 1:34 PM, theirpuppet  wrote:

> Thanks, however this still doesn't work.
>
> From error log:
> [Mon Mar 19 12:29:00 2012] [error] [client X.X.X.X] Directory index
> forbidden by Options directive: /usr/share/puppet-dashboard/public/
>
> And the current apache configuration:
>
> root:~# cat /etc/apache2/sites-enabled/010-dashboard.conf
> # UPDATE THESE PATHS TO SUIT YOUR ENVIRONMENT
> LoadModule passenger_module
> /var/lib/gems/1.8/gems/passenger-2.2.11/ext/apache2/mod_passenger.so
> #PassengerRoot /var/lib/gems/1.8/gems/passenger-2.2.11
> PassengerRoot /usr/lib/phusion_passenger
> PassengerRuby /usr/bin/ruby
>
> # you may want to tune these settings
> PassengerHighPerformance on
> PassengerMaxPoolSize 12
> PassengerPoolIdleTime 1500
> # PassengerMaxRequests 1000
> PassengerStatThrottleRate 120
> RailsAutoDetect On
>
> 
> ServerName X.X.X
> ServerAlias X.X.X.X
> DocumentRoot /usr/share/puppet-dashboard/public/
> RailsBaseURI /
> SetEnv Rails_ENV production
> PassengerEnabled on
> 
> Options -MultiViews -Indexes FollowSymLinks
> Order allow,deny
> allow from all
> 
>   #ErrorLog /var/log/apache2/dashboard.example.com_error.log
>   LogLevel warn
>   #CustomLog /var/log/apache2/dashboard.example.com_access.log combined
>   ServerSignature On
> 
>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/fgfDMT0_1xMJ.
>
> 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.
>

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

Re: [Puppet Users] Re: Puppet Dashboard - Directory Index Forbidden

[Felipe Salum]

I had the same issue too, so I had to make a few changes on my virtualhost
to work. Try changing your Options to None and confirm that your
PassengerRoot and module path are correct.

I'm attaching my working virtualhost for you to compare:


LoadModule passenger_module /usr/lib/apache2/modules/mod_passenger.so
PassengerRoot /usr
PassengerRuby /usr/bin/ruby


SetEnv RAILS_ENV production
RackBaseURI /

ServerName X.X.X.X
DocumentRoot /usr/share/puppet-dashboard/public/

Options None
Order allow,deny
allow from all




Felipe

On Mon, Mar 19, 2012 at 7:52 AM, Antidot SAS  wrote:

> HI,
>
> I had exactly the same issue last week when I wanted to create a vhost for
> the puppet dashboard, I finally wasn't able to resolve the issue. And if
> you change the directive in '+Indexes', the ruby code is not correctly
> executed.
>
>
> Any help is alos appareached.
>
> Regards,
> JM
>
>
> On Mon, Mar 19, 2012 at 1:34 PM, theirpuppet wrote:
>
>> Thanks, however this still doesn't work.
>>
>> From error log:
>> [Mon Mar 19 12:29:00 2012] [error] [client X.X.X.X] Directory index
>> forbidden by Options directive: /usr/share/puppet-dashboard/public/
>>
>> And the current apache configuration:
>>
>> root:~# cat /etc/apache2/sites-enabled/010-dashboard.conf
>> # UPDATE THESE PATHS TO SUIT YOUR ENVIRONMENT
>> LoadModule passenger_module
>> /var/lib/gems/1.8/gems/passenger-2.2.11/ext/apache2/mod_passenger.so
>> #PassengerRoot /var/lib/gems/1.8/gems/passenger-2.2.11
>> PassengerRoot /usr/lib/phusion_passenger
>> PassengerRuby /usr/bin/ruby
>>
>> # you may want to tune these settings
>> PassengerHighPerformance on
>> PassengerMaxPoolSize 12
>> PassengerPoolIdleTime 1500
>> # PassengerMaxRequests 1000
>> PassengerStatThrottleRate 120
>> RailsAutoDetect On
>>
>> 
>> ServerName X.X.X
>> ServerAlias X.X.X.X
>> DocumentRoot /usr/share/puppet-dashboard/public/
>> RailsBaseURI /
>> SetEnv Rails_ENV production
>> PassengerEnabled on
>> 
>> Options -MultiViews -Indexes FollowSymLinks
>> Order allow,deny
>> allow from all
>> 
>>   #ErrorLog /var/log/apache2/dashboard.example.com_error.log
>>   LogLevel warn
>>   #CustomLog /var/log/apache2/dashboard.example.com_access.log combined
>>   ServerSignature On
>> 
>>
>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/puppet-users/-/fgfDMT0_1xMJ.
>>
>> 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.
>>
>
>  --
> 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.
>

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