Puppet users - Aug 2011 - Announce: Dashboard 1.2.0 is available now

It''s here.  Puppet Labs Announces Puppet Dashboard version 1.2.0.

This is a significant upgrade over the 1.1.x series, with new
features, prettier views and some all-in-all awesomeness.   Thanks to
those who filed bugs, submitted patches and helped with the RC
process.


Major Highlights:
------
*  Dashboard now processes workloads asynchronously with a delayed_job
worker.  The worker is controlled either through Rake in the RAILSROOT
or through init scripts (puppet-dashboard-workers) on rpm and deb
based systems.
* License change to Apache Software License version 2.0
* Upgraded version of Rails stack components
* Export most views to CSV
* Dashboard now requires Ruby 1.8.7 to operate
* Puppet agents should be at 2.6.4 or higher


This release is available for download at:
http://downloads.puppetlabs.com/dashboard/

We have included Debian and RPM packages as well as a tarball.

See the Verifying Puppet Download section at:
http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet

Please report feedback via the Puppet Labs Redmine site, using an
affected version of 1.2.0
http://projects.puppetlabs.com/projects/dashboard

Documentation is available at:
http://docs.puppetlabs.com/dashboard/index.html


CHANGELOG since 1.1.1

v1.2.0
==9c32431 (#8228) Reports fail to upload with spool directory
0bfa755 (#9101) Dashboard workers should not be enabled by default
3abc596 (#9103) Remove invalid files from git repo
f52b0ee (#9182) Fix ability to add classes and groups on creation
e924586 (#9195) Use a shorter date format for the report status graph
2e85b8d Apply security patch for XSS Vulnerability in the escaping
function in Ruby on Rails
d3bfcf5 Apply security patch for XSS Vulnerability in strip_tags helper
107f101 Apply security patch for SQL Injection Vulnerability in quote_table_name
0a73593 (#7934) Improve wording to filebucket error
fa8d27c (#7934) Give a better error message when filebucket contents
don''t exist
7b742e9 (#7934) Don''t link md5s for new content
735925f (#9032) Update Debian package to ensure VERSION is packaged
620de4e (#8251 and #8042) Don''t use our own logger
a2a97ab (#8796) Re-write misleading 500 error message
6b525b1 (#5845) Changed host to node in UI.
90f5ce0 (#8488) Move tfoot before tbody in reports table
ee1f182 (#8488) Make columns consistent between report views
e54ecb8 (#8790) Fix reports page column display and alignment
947dcee (#8748) Put sensible umask on pids and logs that delayed_job creates
4ef96b6 (#8785) Close a directory that we open
0bfbbf6 (#8785) - Revert "(#8748) Upgrade vendored daemons gem to fix
umask on pids"
3f88c7f (#8748) Fix my forgetting to add a vendored gem
2f636a9 Allow setting of RUBY for the workers on redhat systems
651511c (#8748) Upgrade vendored daemons gem to fix umask on pids
3a65fd0 (#8694) Add backtrace info to DelayedJobFailure
bf22939 Add document outlining preferred contribution methods
49cca0b Add document outlining preferred contribution methods
803be4f (#8745) Update gitignore to not exlucde tmp during tarball creation
e45338a (#8691) Fix the order of changed and unchanged resources on
the report summary
7653800 Provide clearer error message when report host, kind and time
are not unique
e86526f (#8686) Handle concurrent DelayedJob workers importing for same node
88771ec (#8589) Report events are now ordered by name.
8bd0ffb (#8544) Make empty inspected resources "red".
d036276 (#8505) Update the default date stringification.
bb99ed9 Properly Quote RAILS_ROOT in get_app_version method
08717e1 (#8508) Add delayed job worker script for debian/ubuntu package
2eef4f4 (#8529) Remove unneeded a print statement from sass.rb
af8b6e9 (#8500) Replace README with a smaller one
dff2256 (#8499) Update the usage of mktemp in Rakefile to work on mac
3f0afca (#8484) "Nodes for this group" heading now appears correctly
d389d8b (#7568) Relicense to Apache-2.0 License
82eeea7 (#7567) Refactor dashboard packaging to allow for nightly builds
a58f3e0 (#6840) Remove need for VERSION file in puppet-dashboard
d9a384f (#8316) Ruby sorting for ResourceEvents.
57d0122 (#8276) Remove MaRuKu dependency
a44d9ff (#8262) Show node groups even when node classification is disabled
3996b29 (#8262) Create callbacks for each section of node_classification partial
8f7da94 Remove unused node_groups/_node_groups partial
5dac13a (#8199) Move ''failed'' resources to the top when
viewing report events
2a3a73c (#7967) Improved user-facing design for delayed job warnings
c78b85a (#8266) Back-end logic for splitting read and unread DJ failures.
15bba31 (#8121) Properly generate CSS from SASS in production.
68c0236 Maint: Added $RAILSROOT/spool directory
365a432 Maint: Removing reference to CentOS 5.5.
518bbca Maint: Added rake task to generate srpm
223822e Maint: Updated rpm spec file.
a9abf41 (#8101) Updated to new version of Tipsy plugin
9cb5e55 (Maint) More generalized tabbed interface
07ae6f7 Updating to rename pupet-dashboard-workers
491cf33 Updating spec.
a428d15 Updating to version 1.1.9 for a 1.2. beta
fbe11aa (#8196) Adjust content width based on body classes.
e756c25 (#8196) Add a body class describing sidebar state.
23cbef1 (#8196) Clean up body class manipulation.
c55c326 (Maint) popup_md5 is a little more functional
3670e2b (#8146) Change default DASHBOARD_URL in external_node to localhost
ed8e765 Maint: Tell git to ignore plugin resources with underscores
81ec3c0 (#8090) Update .gitignore to ignore plugin files
6f117fc (#8022) Don''t fail when installing plugin without `public`
directory
07a9407 (#8022) Create a hook for plugins to add items to <head> in layout
66e8d81 (#8022) Provide a rake task to symlink public assets from
plugins into `public`.
05524f0 Maint: small refactor of tab styles for portability
64be352 (#7967) Add default value for read column of delayed_job_failures
240c548 (#7967) Infrastructure for displaying background failures.
240c548 (#7967) Infrastructure for displaying background failures.
612623a Aligning node category names in sidebar.
8038cce (#7389) Don''t auto-start DelayedJob workers.
933ae04 (#7389) Cheaper unique filenames for spooled reports.
b4384eb (#7398) Support externally managed DelayedJob workers.
184e65b (#7689) Rake task to support parallel report POSTing.
2333c08 (#5947) Rename Destroy button to Delete
2fb0ac1 (#7976) Fixed static debug data in view
393970d (#7976) Node filter links in sidebar work in all cases
4ba3d23 (#7398) Configurable DelayedJob worker count.
e839884 (#7938) Delayed import from file, not YAML string.
d24c323 (#7973) Refactor colors for changed/unchanged
58c2b52 (#7398) Use DelayedJob for background processing.
6aefc60 (#7938) Add daemons gem to support DelayedJob
7395369 (#7398) Vendor DelayedJob for background tasks.
05040d9 (#7958) Allow plugins to add top level navigation
eda53a9 Align node list headers when associated with a class or group
8fb1c50 (#7597) Many small design changes for final integration
c4d2f26 (#7597) Better integration of node summaries
4ad9cbc (#7913) Upgrade rspec and rspec-rails vendored gems
c09b650 (#7913) Fix tap deprecation warning
d88da0e (#7913) Update README to say we only support Ruby 1.8.7
acdc31f (#7913) upgrade will_paginate gem to avoid deprecation warnings
e935b8d (#7913) vendor newer version of RDoc
ce9be98 (#7913) Fix deprecation warning for config.load_paths
dd8f277 (#7913) Upgrade vendored haml gem and vendor sass
dd88d74 (#7913) vendor json_pure since it was an undocumented dependency
789c1b7 (#7913) Upgrading from Rails 2.3.4 to 2.3.12
060799f (#7597) Reformat node view CSV link
3726771 (#7280) Edit outdated information about the inventory service
a02113a (#7597) Change empty tab display, report tab ordering, link expansion
b62bf4c (#7597) Add count to pagination link, fix duplicate tags
9f06f58 (#7597) Display only relevant columns in node tables
96bb99c (#7597) Add "help" link to node summary.
95f870e (#6992) Add totals row for resource status counts to node view
598f42a Ignoring RVM''s local config.
44a145c (#7544) Group report resources by status
c2e2c63 (#7840) Increase consistency of status definitions and remove old code
dd5e610 (#7674) Add pending to the run status stacked bar graph
a58d06d (#6992) Show a summary of nodes x resources on home page.
9d71cd2 (#7630) Denormalize ResourceStatus status and count calculations
6e03872 (#6528) Cleanup implementation of `::words`.
2b53c29 (#6528) Remove hideous Array monkeypatch.
0312ea2 (#7007) Stream node CSV download
87b3e91 (#7007) Add a link to the home page to download nodes in CSV
1af5e86 (#7007) Add support for CSV to nodes index
2829a8b (#7007) Add custom CSV output for nodes with resources
11aa643 (#7007) Use a custom property list for ResourceStatus.to_csv
fc0fe85 (#7007) Add support for CSV output
d2184e4 (#7537) Use #titleize for report tab names.
12b035d (#7537) Add reasonable defaults for report tab names.
b230077 (#7560) Clean up the Dashboard index for 0 nodes.
e0eb377 Updating package files for the v1.1.1 release.
6fe8513 (#6991) Add the Node Status summary graph.
8e70035 (#6991) Massage Node named scopes.
57d6b6b (#6991) Cleanup of excessively long lines.
db61b1b (#6537) Add a pending scope to nodes
552c760 (#5126) Support HTTP basic auth in bin/external_node
a85c681 (#6537) Add a pending scope to nodes
cf1410a (#6988) rpm should include logrotate file
0ff2373 (#7209) Require naming convention for plugin migration files
8ff11be (#7161) Add a route to create node group memberships
ec9e879 (#7161) Remove forgery protection
6c700c1 (#4816) Add a Node#find_by_id_or_name helper
d540cc6 (#6989) Improve messages for empty tabs.
b36bfb6 (#6989) Squash bugs in IE{7,8}.
16d6fad (#6989) Fix font rendering in Firefox.
0f2723b (#6989) Add basic styling for tabs.
31984aa (#6989) Remove a call to Registry.each_callback.
4d2f9c7 (#6989) Remove ugly <Proc instance>#name hack.
b8f5a04 (#6989) Refactor user-facing names.
04153bc (#6989) Refactor Javascript into application.js
cc43e61 (#6989) Add "tabs" for report sections.

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Fri, 26 Aug 2011, Michael Stahnke wrote:
> * Dashboard now requires Ruby 1.8.7 to operate
I''ve always found it odd that sysadmins would opt for such an unstable
language.  One where minor revisions are often backwards incompatible
changes to the language.  The ruby design seems to this particular
sysadmin, to be contraindicative of something that can be well
sysadminned.  So it seems odd that it''s the backbone of such an
important
sysadmin tool.

All distributions have a reasonable method of including a good selection
of perl modules.  And perl is pretty stable over time.  But this choice of
not debugging the problems with ruby 1.8.5 leads to it being impossible to
host dashboard on redhat 5 entirely.

I don''t have the freedom of not chosing rhel at work.  If I provisioned
a
new rhel6 server for the new puppet infrastructure, then I''d just be
pushing back the problem until next year when dashboard decided to come
out with ruby dependencies of > 1.8.7.

Is there a great need for choosing bleeding edge features of an unstable
language for a sysadmin tool that''s meant to be around for a long time
because of the amount of investment required in setting it up?

</rant, part question>

-- 
Tim Connors

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Hi Tim,

Correct me if i''m getting this wrong, but you can grab the source of
ruby and compile it as you need on all kind of linux disto! So there
is no need for you to move your server on RHEL6 just to get ruby
1.8.7.

Xavier
SysAdmin



Le 2011-08-27 à 07:37, Tim Connors <tim.w.connors@gmail.com> a écrit :
> On Fri, 26 Aug 2011, Michael Stahnke wrote:
>
>> * Dashboard now requires Ruby 1.8.7 to operate
>
> I''ve always found it odd that sysadmins would opt for such an
unstable
> language.  One where minor revisions are often backwards incompatible
> changes to the language.  The ruby design seems to this particular
> sysadmin, to be contraindicative of something that can be well
> sysadminned.  So it seems odd that it''s the backbone of such an
important
> sysadmin tool.
>
> All distributions have a reasonable method of including a good selection
> of perl modules.  And perl is pretty stable over time.  But this choice of
> not debugging the problems with ruby 1.8.5 leads to it being impossible to
> host dashboard on redhat 5 entirely.
>
> I don''t have the freedom of not chosing rhel at work.  If I
provisioned a
> new rhel6 server for the new puppet infrastructure, then I''d just
be
> pushing back the problem until next year when dashboard decided to come
> out with ruby dependencies of > 1.8.7.
>
> Is there a great need for choosing bleeding edge features of an unstable
> language for a sysadmin tool that''s meant to be around for a long
time
> because of the amount of investment required in setting it up?
>
> </rant, part question>
>
> --
> Tim Connors
>
> --
> 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+unsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

ruby 1.8.5, released Apr 2006
ruby 1.8.7, released May 2008
ruby 1.9.2, released Oct 2010

Not exactly bleeding edge though I suppose anything released in the
last four years could be considered that when compared to RHEL 5. :-)

FWIW, if you think of the releases as Ruby 1.0.x, 1.5.x, and 2.0.x
respectively the differences in capabilities will make more sense.

Ramin

On Aug 27, 4:36 am, Tim Connors <tim.w.conn...@gmail.com>
wrote:
> On Fri, 26 Aug 2011, Michael Stahnke wrote:
> > * Dashboard now requires Ruby 1.8.7 to operate
>
> I''ve always found it odd that sysadmins would opt for such an
unstable
> language.  One where minor revisions are often backwards incompatible
> changes to the language.  The ruby design seems to this particular
> sysadmin, to be contraindicative of something that can be well
> sysadminned.  So it seems odd that it''s the backbone of such an
important
> sysadmin tool.
>
> All distributions have a reasonable method of including a good selection
> of perl modules.  And perl is pretty stable over time.  But this choice of
> not debugging the problems with ruby 1.8.5 leads to it being impossible to
> host dashboard on redhat 5 entirely.
>
> I don''t have the freedom of not chosing rhel at work.  If I
provisioned a
> new rhel6 server for the new puppet infrastructure, then I''d just
be
> pushing back the problem until next year when dashboard decided to come
> out with ruby dependencies of > 1.8.7.
>
> Is there a great need for choosing bleeding edge features of an unstable
> language for a sysadmin tool that''s meant to be around for a long
time
> because of the amount of investment required in setting it up?
>
> </rant, part question>
>
> --
> Tim Connors
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Sat, Aug 27, 2011 at 2:36 PM, Tim Connors <tim.w.connors@gmail.com>
wrote:
> On Fri, 26 Aug 2011, Michael Stahnke wrote:
>
>> * Dashboard now requires Ruby 1.8.7 to operate
>
> I''ve always found it odd that sysadmins would opt for such an
unstable
> language.  One where minor revisions are often backwards incompatible
> changes to the language.  The ruby design seems to this particular
> sysadmin, to be contraindicative of something that can be well
> sysadminned.  So it seems odd that it''s the backbone of such an
important
> sysadmin tool.
>
> All distributions have a reasonable method of including a good selection
> of perl modules.  And perl is pretty stable over time.  But this choice of
> not debugging the problems with ruby 1.8.5 leads to it being impossible to
> host dashboard on redhat 5 entirely.
>
> I don''t have the freedom of not chosing rhel at work.  If I
provisioned a
> new rhel6 server for the new puppet infrastructure, then I''d just
be
> pushing back the problem until next year when dashboard decided to come
> out with ruby dependencies of > 1.8.7.
>
> Is there a great need for choosing bleeding edge features of an unstable
> language for a sysadmin tool that''s meant to be around for a long
time
> because of the amount of investment required in setting it up?
>
> </rant, part question>
>
> --
AFAIR, all major distributions (that has a stable long running life
cycle) already include ruby 1.87.
imho - if you are building new infrastructure today, there is little
sense to install it on an obsolete distribution.

saying that, you can always use an older version to match your distribution ;)
Ohad
> Tim Connors
>
> --
> 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+unsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

wat

On Sat, Aug 27, 2011 at 4:36 AM, Tim Connors
<tim.w.connors@gmail.com>wrote:
> On Fri, 26 Aug 2011, Michael Stahnke wrote:
>
> > * Dashboard now requires Ruby 1.8.7 to operate
>
> I''ve always found it odd that sysadmins would opt for such an
unstable
> language.  One where minor revisions are often backwards incompatible
> changes to the language.  The ruby design seems to this particular
> sysadmin, to be contraindicative of something that can be well
> sysadminned.  So it seems odd that it''s the backbone of such an
important
> sysadmin tool.
>
> All distributions have a reasonable method of including a good selection
> of perl modules.  And perl is pretty stable over time.  But this choice of
> not debugging the problems with ruby 1.8.5 leads to it being impossible to
> host dashboard on redhat 5 entirely.
>
> I don''t have the freedom of not chosing rhel at work.  If I
provisioned a
> new rhel6 server for the new puppet infrastructure, then I''d just
be
> pushing back the problem until next year when dashboard decided to come
> out with ruby dependencies of > 1.8.7.
>
> Is there a great need for choosing bleeding edge features of an unstable
> language for a sysadmin tool that''s meant to be around for a long
time
> because of the amount of investment required in setting it up?
>
> </rant, part question>
>
> --
> Tim Connors
>
> --
> 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+unsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Hi Tim,

Correct me if i''m getting this wrong, but you can grab the source of
ruby and compile it as you need on all kind of linux disto! So there
is no need for you to move your server on RHEL6 just to get ruby
1.8.7.

Xavier

On 26 août, 16:38, Michael Stahnke <stah...@puppetlabs.com>
wrote:
> It''s here.  Puppet Labs Announces Puppet Dashboard version 1.2.0.
>
> This is a significant upgrade over the 1.1.x series, with new
> features, prettier views and some all-in-all awesomeness.   Thanks to
> those who filed bugs, submitted patches and helped with the RC
> process.
>
> Major Highlights:
> ------
> *  Dashboard now processes workloads asynchronously with a delayed_job
> worker.  The worker is controlled either through Rake in the RAILSROOT
> or through init scripts (puppet-dashboard-workers) on rpm and deb
> based systems.
> * License change to Apache Software License version 2.0
> * Upgraded version of Rails stack components
> * Export most views to CSV
> * Dashboard now requires Ruby 1.8.7 to operate
> * Puppet agents should be at 2.6.4 or higher
>
> This release is available for download
at:http://downloads.puppetlabs.com/dashboard/
>
> We have included Debian and RPM packages as well as a tarball.
>
> See the Verifying Puppet Download section
at:http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet
>
> Please report feedback via the Puppet Labs Redmine site, using an
> affected version of 1.2.0http://projects.puppetlabs.com/projects/dashboard
>
> Documentation is available
at:http://docs.puppetlabs.com/dashboard/index.html
>
> CHANGELOG since 1.1.1
>
> v1.2.0
> ==> 9c32431 (#8228) Reports fail to upload with spool directory
> 0bfa755 (#9101) Dashboard workers should not be enabled by default
> 3abc596 (#9103) Remove invalid files from git repo
> f52b0ee (#9182) Fix ability to add classes and groups on creation
> e924586 (#9195) Use a shorter date format for the report status graph
> 2e85b8d Apply security patch for XSS Vulnerability in the escaping
> function in Ruby on Rails
> d3bfcf5 Apply security patch for XSS Vulnerability in strip_tags helper
> 107f101 Apply security patch for SQL Injection Vulnerability in
quote_table_name
> 0a73593 (#7934) Improve wording to filebucket error
> fa8d27c (#7934) Give a better error message when filebucket contents
don''t exist
> 7b742e9 (#7934) Don''t link md5s for new content
> 735925f (#9032) Update Debian package to ensure VERSION is packaged
> 620de4e (#8251 and #8042) Don''t use our own logger
> a2a97ab (#8796) Re-write misleading 500 error message
> 6b525b1 (#5845) Changed host to node in UI.
> 90f5ce0 (#8488) Move tfoot before tbody in reports table
> ee1f182 (#8488) Make columns consistent between report views
> e54ecb8 (#8790) Fix reports page column display and alignment
> 947dcee (#8748) Put sensible umask on pids and logs that delayed_job
creates
> 4ef96b6 (#8785) Close a directory that we open
> 0bfbbf6 (#8785) - Revert "(#8748) Upgrade vendored daemons gem to fix
> umask on pids"
> 3f88c7f (#8748) Fix my forgetting to add a vendored gem
> 2f636a9 Allow setting of RUBY for the workers on redhat systems
> 651511c (#8748) Upgrade vendored daemons gem to fix umask on pids
> 3a65fd0 (#8694) Add backtrace info to DelayedJobFailure
> bf22939 Add document outlining preferred contribution methods
> 49cca0b Add document outlining preferred contribution methods
> 803be4f (#8745) Update gitignore to not exlucde tmp during tarball creation
> e45338a (#8691) Fix the order of changed and unchanged resources on
> the report summary
> 7653800 Provide clearer error message when report host, kind and time
> are not unique
> e86526f (#8686) Handle concurrent DelayedJob workers importing for same
node
> 88771ec (#8589) Report events are now ordered by name.
> 8bd0ffb (#8544) Make empty inspected resources "red".
> d036276 (#8505) Update the default date stringification.
> bb99ed9 Properly Quote RAILS_ROOT in get_app_version method
> 08717e1 (#8508) Add delayed job worker script for debian/ubuntu package
> 2eef4f4 (#8529) Remove unneeded a print statement from sass.rb
> af8b6e9 (#8500) Replace README with a smaller one
> dff2256 (#8499) Update the usage of mktemp in Rakefile to work on mac
> 3f0afca (#8484) "Nodes for this group" heading now appears
correctly
> d389d8b (#7568) Relicense to Apache-2.0 License
> 82eeea7 (#7567) Refactor dashboard packaging to allow for nightly builds
> a58f3e0 (#6840) Remove need for VERSION file in puppet-dashboard
> d9a384f (#8316) Ruby sorting for ResourceEvents.
> 57d0122 (#8276) Remove MaRuKu dependency
> a44d9ff (#8262) Show node groups even when node classification is disabled
> 3996b29 (#8262) Create callbacks for each section of node_classification
partial
> 8f7da94 Remove unused node_groups/_node_groups partial
> 5dac13a (#8199) Move ''failed'' resources to the top when
viewing report events
> 2a3a73c (#7967) Improved user-facing design for delayed job warnings
> c78b85a (#8266) Back-end logic for splitting read and unread DJ failures.
> 15bba31 (#8121) Properly generate CSS from SASS in production.
> 68c0236 Maint: Added $RAILSROOT/spool directory
> 365a432 Maint: Removing reference to CentOS 5.5.
> 518bbca Maint: Added rake task to generate srpm
> 223822e Maint: Updated rpm spec file.
> a9abf41 (#8101) Updated to new version of Tipsy plugin
> 9cb5e55 (Maint) More generalized tabbed interface
> 07ae6f7 Updating to rename pupet-dashboard-workers
> 491cf33 Updating spec.
> a428d15 Updating to version 1.1.9 for a 1.2. beta
> fbe11aa (#8196) Adjust content width based on body classes.
> e756c25 (#8196) Add a body class describing sidebar state.
> 23cbef1 (#8196) Clean up body class manipulation.
> c55c326 (Maint) popup_md5 is a little more functional
> 3670e2b (#8146) Change default DASHBOARD_URL in external_node to localhost
> ed8e765 Maint: Tell git to ignore plugin resources with underscores
> 81ec3c0 (#8090) Update .gitignore to ignore plugin files
> 6f117fc (#8022) Don''t fail when installing plugin without `public`
directory
> 07a9407 (#8022) Create a hook for plugins to add items to <head> in
layout
> 66e8d81 (#8022) Provide a rake task to symlink public assets from
> plugins into `public`.
> 05524f0 Maint: small refactor of tab styles for portability
> 64be352 (#7967) Add default value for read column of delayed_job_failures
> 240c548 (#7967) Infrastructure for displaying background failures.
> 240c548 (#7967) Infrastructure for displaying background failures.
> 612623a Aligning node category names in sidebar.
> 8038cce (#7389) Don''t auto-start DelayedJob workers.
> 933ae04 (#7389) Cheaper unique filenames for spooled reports.
> b4384eb (#7398) Support externally managed DelayedJob workers.
> 184e65b (#7689) Rake task to support parallel report POSTing.
> 2333c08 (#5947) Rename Destroy button to Delete
> 2fb0ac1 (#7976) Fixed static debug data in view
> 393970d (#7976) Node filter links in sidebar work in all cases
> 4ba3d23 (#7398) Configurable DelayedJob worker count.
> e839884 (#7938) Delayed import from file, not YAML string.
> d24c323 (#7973) Refactor colors for changed/unchanged
> 58c2b52 (#7398) Use DelayedJob for background processing.
> 6aefc60 (#7938) Add daemons gem to support DelayedJob
> 7395369 (#7398) Vendor DelayedJob for background tasks.
> 05040d9 (#7958) Allow plugins to add top level navigation
> eda53a9 Align node list headers when associated with a class or group
> 8fb1c50 (#7597) Many small design changes for final integration
> c4d2f26 (#7597) Better integration of node summaries
> 4ad9cbc (#7913) Upgrade rspec and rspec-rails vendored gems
> c09b650 (#7913) Fix tap deprecation warning
> d88da0e (#7913) Update README to say we only support Ruby 1.8.7
> acdc31f (#7913) upgrade will_paginate gem to avoid deprecation warnings
> e935b8d (#7913) vendor newer version of RDoc
> ce9be98 (#7913) Fix deprecation warning for config.load_paths
> dd8f277 (#7913) Upgrade vendored haml gem and vendor sass
> dd88d74 (#7913) vendor json_pure since it was an undocumented dependency
> 789c1b7 (#7913) Upgrading from Rails 2.3.4 to 2.3.12
> 060799f (#7597) Reformat node view CSV link
> 3726771 (#7280) Edit outdated information about the inventory service
> a02113a (#7597) Change empty tab display, report tab ordering, link
expansion
> b62bf4c (#7597) Add count to pagination link, fix duplicate tags
> 9f06f58 (#7597) Display only relevant columns in node tables
> 96bb99c (#7597) Add "help" link to node summary.
> 95f870e (#6992) Add totals row for resource status counts to node view
> 598f42a Ignoring RVM''s local config.
> 44a145c (#7544) Group report resources by status
> c2e2c63 (#7840) Increase consistency of status definitions and remove old
code
> dd5e610 (#7674) Add pending to the run status stacked bar graph
> a58d06d (#6992) Show a summary of nodes x resources on home page.
> 9d71cd2 (#7630) Denormalize ResourceStatus status and count calculations
> 6e03872 (#6528) Cleanup implementation of `::words`.
> 2b53c29 (#6528) Remove hideous Array monkeypatch.
> 0312ea2 (#7007) Stream node CSV download
> 87b3e91 (#7007) Add a link to the home page to download nodes in CSV
> 1af5e86 (#7007) Add support for CSV to nodes index
> 2829a8b (#7007) Add custom CSV output for nodes with resources
> 11aa643 (#7007) Use a custom property list for ResourceStatus.to_csv
> fc0fe85 (#7007) Add support for CSV output
> d2184e4 (#7537) Use #titleize for report tab names.
> 12b035d (#7537) Add reasonable defaults for report tab names.
> b230077 (#7560) Clean up the Dashboard index for 0 nodes.
> e0eb377 Updating package files for the v1.1.1 release.
> 6fe8513 (#6991) Add the Node Status summary graph.
> 8e70035 (#6991) Massage Node named scopes.
> 57d6b6b (#6991) Cleanup of excessively long lines.
> db61b1b (#6537) Add a pending scope to nodes
> 552c760 (#5126) Support HTTP basic auth in bin/external_node
> a85c681 (#6537) Add a pending scope to nodes
> cf1410a (#6988) rpm should include logrotate file
> 0ff2373 (#7209) Require naming convention for plugin migration files
> 8ff11be (#7161) Add a route to create node group memberships
> ec9e879 (#7161) Remove forgery protection
> 6c700c1 (#4816) Add a Node#find_by_id_or_name helper
> d540cc6 (#6989) Improve messages for empty tabs.
> b36bfb6 (#6989) Squash bugs in IE{7,8}.
> 16d6fad (#6989) Fix font rendering in Firefox.
> 0f2723b (#6989) Add basic styling for tabs.
> 31984aa (#6989) Remove a call to Registry.each_callback.
> 4d2f9c7 (#6989) Remove ugly <Proc instance>#name hack.
> b8f5a04 (#6989) Refactor user-facing names.
> 04153bc (#6989) Refactor Javascript into application.js
> cc43e61 (#6989) Add "tabs" for ...
>
> plus de détails »
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

While I agree that it''s annoying that the puppet dashboard
doesn''t run
with the ruby included in RHEL, i suggest you have a look at the Ruby
Version Manager (RVM) http://beginrescueend.com/
Makes running the latest 1.8.x and 1.9.x versions of Ruby a breeze on
any OS you might use.

I''m running puppet on hundreds of CentOS 5 hosts using rvm.

--
Toni Birrer

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Aug 28, 7:07 am, Toni Birrer <t...@memonic.ch>
wrote:
> While I agree that it''s annoying that the puppet dashboard
doesn''t run
> with the ruby included in RHEL, i suggest you have a look at the Ruby
> Version Manager (RVM)http://beginrescueend.com/
> Makes running the latest 1.8.x and 1.9.x versions of Ruby a breeze on
> any OS you might use.
>
> I''m running puppet on hundreds of CentOS 5 hosts using rvm.
Personally, I wouldn''t touch RVM with a ten-foot pole.  For one thing,
I insist on installing software only from native packages.  For
another, RVM requires manually switching among various Ruby versions
-- useful for developers, I''m sure, but not so much for running system
software.

But one could, indeed, package a more recent Ruby oneself.  In this
particular case, it is likely that the RHEL or CentOS 6 source RPM for
Ruby 1.8.7 will build with little or no change on CentOS 5.


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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

----- Original Message -----
> 
> On Aug 28, 7:07 am, Toni Birrer <t...@memonic.ch> wrote:
> > While I agree that it''s annoying that the puppet dashboard
doesn''t
> > run
> > with the ruby included in RHEL, i suggest you have a look at the
> > Ruby
> > Version Manager (RVM)http://beginrescueend.com/
> > Makes running the latest 1.8.x and 1.9.x versions of Ruby a breeze
> > on
> > any OS you might use.
> >
> > I''m running puppet on hundreds of CentOS 5 hosts using rvm.
> 
> Personally, I wouldn''t touch RVM with a ten-foot pole.  For one
> thing,
> I insist on installing software only from native packages.  For
> another, RVM requires manually switching among various Ruby versions
> -- useful for developers, I''m sure, but not so much for running
> system
> software.
> 
> But one could, indeed, package a more recent Ruby oneself.  In this
> particular case, it is likely that the RHEL or CentOS 6 source RPM
> for Ruby 1.8.7 will build with little or no change on CentOS 5.
As has already been done by the CentOS maintainer:

http://centos.karan.org/el5/ruby187/

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Ruby 1.8.7 is unfortunately required to support modernish Rails, etc.
To include security fixes, we had to be 1.8.7.

1.  There are ways to get 1.8.7 onto enterprise platforms these days.
Also, EL6 has been out a while now which ships with 1.8.7.
2.  If you purchase puppet enterprise, ruby 1.8.7 is included


There was a minor bug in an init script on EL based platforms for
puppet-dashboard-workers.  That is fixed in -2 of the package.

http://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.0-2.el6.noarch.rpm

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Aug 27, 2011, at 4:36 AM, Tim Connors wrote:
> On Fri, 26 Aug 2011, Michael Stahnke wrote:
> 
>> * Dashboard now requires Ruby 1.8.7 to operate
> 
> I''ve always found it odd that sysadmins would opt for such an
unstable
> language.  One where minor revisions are often backwards incompatible
> changes to the language.  The ruby design seems to this particular
> sysadmin, to be contraindicative of something that can be well
> sysadminned.  So it seems odd that it''s the backbone of such an
important
> sysadmin tool.
> 
> All distributions have a reasonable method of including a good selection
> of perl modules.  And perl is pretty stable over time.  But this choice of
> not debugging the problems with ruby 1.8.5 leads to it being impossible to
> host dashboard on redhat 5 entirely.
> 
> I don''t have the freedom of not chosing rhel at work.  If I
provisioned a
> new rhel6 server for the new puppet infrastructure, then I''d just
be
> pushing back the problem until next year when dashboard decided to come
> out with ruby dependencies of > 1.8.7.
> 
> Is there a great need for choosing bleeding edge features of an unstable
> language for a sysadmin tool that''s meant to be around for a long
time
> because of the amount of investment required in setting it up?
----
basically anyone attempting to do anything reasonable with ruby on RHEL 5.x (or
any of the free repackaged distributions of RHEL 5.x) knows that 1.8.5 version
is just short of useless and has implemented other fixes.

For example, if you use passenger, the same people put out enterprise ruby which
will not over write any existing ruby installation and it works really well:

http://www.rubyenterpriseedition.com/

or of course you can build from source or even use the package that Karanbir
Singh of CentOS packages that will replace the 1.8.5 packages from RHEL

The choice of course is yours.

It''s not really just a dashboard thing as you suggest because puppet
also runs under ruby and I think you will be pushed to get a properly
functioning puppetmaster running on 1.8.5 too. Then again, there''s the
issue of making it run efficiently and effectively (ie - passenger)

Your rant should be directed those who think it is reasonable to be running an
OS that is long in the tooth and thinking that they can easily implement
innovative technologies that require something a little more modern. Ruby is the
backbone of puppet - deal with it.

Craig

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

> basically anyone attempting to do anything reasonable with ruby on RHEL 5.x
(or any of the free repackaged distributions of RHEL 5.x) knows that 1.8.5
version is just short of useless and has implemented other fixes.
Some comments on this thread, and current software development trends
in general.

Craig, the version of ruby that ships with RHEL 5 was good enough for
many things, including dashboard <= 1.1.  So, while it may have
problems and limitations,  I think you overstate things to say it is
"just short of useless."

Also, "long in the tooth" is subjective; RHEL 5 (and the derivative
works) are currently supported distributions with significant
installed user bases.  Many environments, for many different reasons,
have decided that EL is the best choice for them.  It''s important to
respect those decisions.  As a system administrator, I see people
ignore compatibility with the EL distros regularly, and it''s
unfortunate that many people wave their hands with phrases like ''long
in the tooth,'' ''next to useless,'' or ''any
modern linux
distribution'' (from another project I was asked to install recently),
which don''t mesh well with the realities of significant parts of the
installed linux base.

In this case, as was pointed out, there are fairly simple ways to get
ruby >1.8.5 onto an EL 5 system.  But when someone writes an app
against the lastest and greatest libgtk and friends, and uses the most
recent versions of everything because that''s what''s available
on their
latest ubuntu release, it simply cuts them off from many potential
users, for perhaps very little developer gain.  Developers should
consider carefully the run-time requirements vs. the target audience
as part of the development process.

I agree with Ramin that a different numbering scheme for ruby versions
would have made more sense.  A tiny version change (e.g. 1.8.5 to
1.8.7) would be understood in many release contexts to contain bug-
fixes only and introduce no higher-level incompatibilities (a very
broad simplification, but still true).  Version numbers mean something
very different to the ruby development team than they do to many other
knowledgeable people.

All that being said, if the dashboard development folks have decided
that 1.8.7 is needed, then 1.8.7 it is.  Perhaps pointers to suitable
ruby builds could be included in the release notes (or on the download
page, etc., etc.) as an aid to those who will need to upgrade.

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

+1 for all of it.


On Tue, 2011-08-30 at 08:15 -0700, David Thompson wrote:
> > basically anyone attempting to do anything reasonable with ruby on
RHEL 5.x (or any of the free repackaged distributions of RHEL 5.x) knows that
1.8.5 version is just short of useless and has implemented other fixes.
> 
> Some comments on this thread, and current software development trends
> in general.
> 
> Craig, the version of ruby that ships with RHEL 5 was good enough for
> many things, including dashboard <= 1.1.  So, while it may have
> problems and limitations,  I think you overstate things to say it is
> "just short of useless."
> 
> Also, "long in the tooth" is subjective; RHEL 5 (and the
derivative
> works) are currently supported distributions with significant
> installed user bases.  Many environments, for many different reasons,
> have decided that EL is the best choice for them.  It''s important
to
> respect those decisions.  As a system administrator, I see people
> ignore compatibility with the EL distros regularly, and it''s
> unfortunate that many people wave their hands with phrases like
''long
> in the tooth,'' ''next to useless,'' or
''any modern linux
> distribution'' (from another project I was asked to install
recently),
> which don''t mesh well with the realities of significant parts of
the
> installed linux base.
> 
> In this case, as was pointed out, there are fairly simple ways to get
> ruby >1.8.5 onto an EL 5 system.  But when someone writes an app
> against the lastest and greatest libgtk and friends, and uses the most
> recent versions of everything because that''s what''s
available on their
> latest ubuntu release, it simply cuts them off from many potential
> users, for perhaps very little developer gain.  Developers should
> consider carefully the run-time requirements vs. the target audience
> as part of the development process.
> 
> I agree with Ramin that a different numbering scheme for ruby versions
> would have made more sense.  A tiny version change (e.g. 1.8.5 to
> 1.8.7) would be understood in many release contexts to contain bug-
> fixes only and introduce no higher-level incompatibilities (a very
> broad simplification, but still true).  Version numbers mean something
> very different to the ruby development team than they do to many other
> knowledgeable people.
> 
> All that being said, if the dashboard development folks have decided
> that 1.8.7 is needed, then 1.8.7 it is.  Perhaps pointers to suitable
> ruby builds could be included in the release notes (or on the download
> page, etc., etc.) as an aid to those who will need to upgrade.
> 

-- 
Christopher McCrory
To the optimist, the glass is half full.
To the pessimist, the glass is half empty.
To the engineer, the glass is twice as big as it needs to be.

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Tue, Aug 30, 2011 at 8:15 AM, David Thompson
<dthompson@waisman.wisc.edu> wrote:
>
>> basically anyone attempting to do anything reasonable with ruby on RHEL
5.x (or any of the free repackaged distributions of RHEL 5.x) knows that 1.8.5
version is just short of useless and has implemented other fixes.
>
> Some comments on this thread, and current software development trends
> in general.
>
> Craig, the version of ruby that ships with RHEL 5 was good enough for
> many things, including dashboard <= 1.1.  So, while it may have
> problems and limitations,  I think you overstate things to say it is
> "just short of useless."
>
> Also, "long in the tooth" is subjective; RHEL 5 (and the
derivative
> works) are currently supported distributions with significant
> installed user bases.  Many environments, for many different reasons,
> have decided that EL is the best choice for them.  It''s important
to
> respect those decisions.  As a system administrator, I see people
> ignore compatibility with the EL distros regularly, and it''s
> unfortunate that many people wave their hands with phrases like
''long
> in the tooth,'' ''next to useless,'' or
''any modern linux
> distribution'' (from another project I was asked to install
recently),
> which don''t mesh well with the realities of significant parts of
the
> installed linux base.
>
> In this case, as was pointed out, there are fairly simple ways to get
> ruby >1.8.5 onto an EL 5 system.  But when someone writes an app
> against the lastest and greatest libgtk and friends, and uses the most
> recent versions of everything because that''s what''s
available on their
> latest ubuntu release, it simply cuts them off from many potential
> users, for perhaps very little developer gain.  Developers should
> consider carefully the run-time requirements vs. the target audience
> as part of the development process.
>
> I agree with Ramin that a different numbering scheme for ruby versions
> would have made more sense.  A tiny version change (e.g. 1.8.5 to
> 1.8.7) would be understood in many release contexts to contain bug-
> fixes only and introduce no higher-level incompatibilities (a very
> broad simplification, but still true).  Version numbers mean something
> very different to the ruby development team than they do to many other
> knowledgeable people.
>
> All that being said, if the dashboard development folks have decided
> that 1.8.7 is needed, then 1.8.7 it is.  Perhaps pointers to suitable
> ruby builds could be included in the release notes (or on the download
> page, etc., etc.) as an aid to those who will need to upgrade.
It''s not just Dashboard that decided not to support older versions of
Ruby, Rails (the framework Dashboard uses) doesn''t support older
version of Ruby.

    http://rubyonrails.org/download
    We recommend Ruby 1.8.7 or Ruby 1.9.2 for use with Rails. Ruby
1.8.6 and earlier are not supported, neither is version 1.9.1.

While it''s true this statement applies explicitly to Rails 3.x rather
than Rails 2.3.x (which Dashboard is still based on), there is nowhere
we could find that explicitly says that Rails 2.3.x *supports* Ruby
1.8.5, so there''s no guarantee that security fixes (of which there
were a few applied recently) will support Ruby 1.8.5.

It''s probably a good idea to briefly mention a few ways (numerous were
mentioned in this thread) to get newer Rubies in the Dashboard manual
(http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#installing-dependencies).
 I''ve included our excellent documentation writer on this thread.

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On 08/27/2011 08:07 PM, Ramin K wrote:
> ruby 1.8.5, released Apr 2006
> ruby 1.8.7, released May 2008
> ruby 1.9.2, released Oct 2010
>
> Not exactly bleeding edge though I suppose anything released in the
> last four years could be considered that when compared to RHEL 5.:-)
>
> FWIW, if you think of the releases as Ruby 1.0.x, 1.5.x, and 2.0.x
> respectively the differences in capabilities will make more sense.
For my environment, having puppet agents >= 2.6.4 is the only blocking 
issue, because I''d like to stay with Debian/Ubuntu packages and so far 
the most I can get from stable versions are 2.6.2 (the only exception 
being FreeBSD 8.2 shipping 2.6.7)

Argh... I just can''t wait to see the new Dashboard! :D

-- 
Alexander Fortin
http://about.me/alexanderfortin/

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.