Announcing Puppet Dashboard 0.1.0 Release
4 views
Skip to first unread message
Rein Henrichs
Dec 14, 2009, 3:29:35 PM12/14/09
to puppe...@googlegroups.com, puppet...@googlegroups.com, Puppet Announce
Greetings Puppeteers,
It's the holidays once again and, in the spirit of the season, I bring you the immediate release of Puppet Dashboard 0.1.0, codenamed "Wira". Because the Wira is a car. From Malaysia. And cars have dashboards. Even cars from Malaysia.
This release includes run success and total run time graphs and a global status drop-down tab that provides at-a-glance system status updates. We are still deciding on which information to present where and how best to present it, so expect these to change in upcoming releases as we converge on the most useful set of data to display. Coincidentally, this would be a great time to tell us which information is most important to you on which pages. You could even reply to this message on the list if you want (hint).
It's the holidays once again and, in the spirit of the season, I bring you the immediate release of Puppet Dashboard 0.1.0, codenamed "Wira". Because the Wira is a car. From Malaysia. And cars have dashboards. Even cars from Malaysia.
This release includes run success and total run time graphs and a global status drop-down tab that provides at-a-glance system status updates. We are still deciding on which information to present where and how best to present it, so expect these to change in upcoming releases as we converge on the most useful set of data to display. Coincidentally, this would be a great time to tell us which information is most important to you on which pages. You could even reply to this message on the list if you want (hint).
Also, at the request of just about everyone, I've posted a tour of the latest Dashboard release on the Reductive Labs blog at http://reductivelabs.com/2009/12/14/a-tour-of-puppet-dashboard-0-1-0. Yes, it includes screenshots. Huzzah.
Get the code at http://github.com/reductivelabs/puppet-dashboard.
Submit feature requests and bug reports at http://projects.reductivelabs.com/projects/dashboard.
Get the code at http://github.com/reductivelabs/puppet-dashboard.
Submit feature requests and bug reports at http://projects.reductivelabs.com/projects/dashboard.
jw2d...@gmail.com
Dec 15, 2009, 4:09:33 PM12/15/09
to Puppet Users
Bummer. Requires rake >= 0.8.4, but RHEL5/EPEL is only 0.8.3.
http://download.fedora.redhat.com/pub/epel/5/x86_64/repoview/rubygem-rake.html
On Dec 14, 3:29 pm, Rein Henrichs <r...@reductivelabs.com> wrote:
> Greetings Puppeteers,
>
> It's the holidays once again and, in the spirit of the season, I bring you
> the immediate release of Puppet Dashboard 0.1.0, codenamed "Wira". Because
> the Wira is a car. From Malaysia. And cars have dashboards. Even cars from
> Malaysia.
>
> This release includes run success and total run time graphs and a global
> status drop-down tab that provides at-a-glance system status updates. We are
> still deciding on which information to present where and how best to present
> it, so expect these to change in upcoming releases as we converge on the
> most useful set of data to display. Coincidentally, this would be a great
> time to tell us which information is most important to you on which pages.
> You could even reply to this message on the list if you want (hint).
>
> Also, at the request of just about everyone, I've posted a tour of the
> latest Dashboard release on the Reductive Labs blog athttp://reductivelabs.com/2009/12/14/a-tour-of-puppet-dashboard-0-1-0. Yes,
> it includes screenshots. Huzzah.
>
> Get the code athttp://github.com/reductivelabs/puppet-dashboard.
> Submit feature requests and bug reports athttp://projects.reductivelabs.com/projects/dashboard.
http://download.fedora.redhat.com/pub/epel/5/x86_64/repoview/rubygem-rake.html
On Dec 14, 3:29 pm, Rein Henrichs <r...@reductivelabs.com> wrote:
> Greetings Puppeteers,
>
> It's the holidays once again and, in the spirit of the season, I bring you
> the immediate release of Puppet Dashboard 0.1.0, codenamed "Wira". Because
> the Wira is a car. From Malaysia. And cars have dashboards. Even cars from
> Malaysia.
>
> This release includes run success and total run time graphs and a global
> status drop-down tab that provides at-a-glance system status updates. We are
> still deciding on which information to present where and how best to present
> it, so expect these to change in upcoming releases as we converge on the
> most useful set of data to display. Coincidentally, this would be a great
> time to tell us which information is most important to you on which pages.
> You could even reply to this message on the list if you want (hint).
>
> Also, at the request of just about everyone, I've posted a tour of the
> it includes screenshots. Huzzah.
>
> Get the code athttp://github.com/reductivelabs/puppet-dashboard.
> Submit feature requests and bug reports athttp://projects.reductivelabs.com/projects/dashboard.
Rein Henrichs
Dec 15, 2009, 4:43:29 PM12/15/09
to puppet...@googlegroups.com
At the risk of sparking another flame war, the best way to manage Ruby library dependencies is via Rubygems rather than your platform's packaging system -- which tends to have out of date Ruby packages and can conflict with installed gems[1]. Fortunately, it is entirely possible and in fact quite easy to install and use Rubygems as a local user (rather than root)[2]. We've done our best to remove external dependencies but this one unfortunately remains.
The bottom line is that rake 0.8.4 is the first known-good version for the version of Rails that Dashboard uses and, as such, the first that we currently support. However, the rake install task (which is the only thing that requires rake aside from running the spec suite) may work or be made to work with older versions of rake. We would be happy to bump the dependency down to 0.8.3 to provide out-of-the-box support for RHEL5 and will gratefully accept patches that let us do that.
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
jw2d...@gmail.com
Dec 15, 2009, 6:00:55 PM12/15/09
to Puppet Users
I'm sure this RubyGems topic probably deserves it's own thread...
We go through a lot of political/legal paperwork at $WORK to deploy
open-source software on our Red Hat systems. Throwing logic aside, we
managed to get approval to use any RPM package from EPEL, but that's
not the case for RubyGems out on rubyforge.org. RPM packages are
simple to maintain and track for inventory purposes, but I agree with
your comments on packaging systems falling behind.. (We still have
lots of RHEL4 boxes, which can be very difficult with the ruby RPMs
offered with that distro).
Thanks for the gem docs. I'll pursue that route.
On Dec 15, 4:43 pm, Rein Henrichs <r...@reductivelabs.com> wrote:
> At the risk of sparking another flame war, the best way to manage Ruby
> library dependencies is via Rubygems rather than your platform's packaging
> system -- which tends to have out of date Ruby packages and can conflict
> with installed gems[1]. Fortunately, it is entirely possible and in fact
> quite easy to install and use Rubygems as a local user (rather than
> root)[2]. We've done our best to remove external dependencies but this one
> unfortunately remains.
>
> The bottom line is that rake 0.8.4 is the first known-good version for the
> version of Rails that Dashboard uses and, as such, the first that we
> currently support. However, the rake install task (which is the only thing
> that requires rake aside from running the spec suite) may work or be made to
> work with older versions of rake. We would be happy to bump the dependency
> down to 0.8.3 to provide out-of-the-box support for RHEL5 and will
> gratefully accept patches that let us do that.
>
> [1] Seehttps://help.ubuntu.com/community/RubyOnRails
> [2]http://docs.rubygems.org/read/chapter/3
> > puppet-users...@googlegroups.com<puppet-users%2Bunsu...@googlegroups.com>
> > .
We go through a lot of political/legal paperwork at $WORK to deploy
open-source software on our Red Hat systems. Throwing logic aside, we
managed to get approval to use any RPM package from EPEL, but that's
not the case for RubyGems out on rubyforge.org. RPM packages are
simple to maintain and track for inventory purposes, but I agree with
your comments on packaging systems falling behind.. (We still have
lots of RHEL4 boxes, which can be very difficult with the ruby RPMs
offered with that distro).
Thanks for the gem docs. I'll pursue that route.
On Dec 15, 4:43 pm, Rein Henrichs <r...@reductivelabs.com> wrote:
> At the risk of sparking another flame war, the best way to manage Ruby
> library dependencies is via Rubygems rather than your platform's packaging
> system -- which tends to have out of date Ruby packages and can conflict
> with installed gems[1]. Fortunately, it is entirely possible and in fact
> quite easy to install and use Rubygems as a local user (rather than
> root)[2]. We've done our best to remove external dependencies but this one
> unfortunately remains.
>
> The bottom line is that rake 0.8.4 is the first known-good version for the
> version of Rails that Dashboard uses and, as such, the first that we
> currently support. However, the rake install task (which is the only thing
> that requires rake aside from running the spec suite) may work or be made to
> work with older versions of rake. We would be happy to bump the dependency
> down to 0.8.3 to provide out-of-the-box support for RHEL5 and will
> gratefully accept patches that let us do that.
>
> [2]http://docs.rubygems.org/read/chapter/3
>
> On Tue, Dec 15, 2009 at 1:09 PM, jw2dot...@gmail.com <jw2dot...@gmail.com>wrote:
>
>
>
> > Bummer. Requires rake >= 0.8.4, but RHEL5/EPEL is only 0.8.3.
>
> >http://download.fedora.redhat.com/pub/epel/5/x86_64/repoview/rubygem-...
> On Tue, Dec 15, 2009 at 1:09 PM, jw2dot...@gmail.com <jw2dot...@gmail.com>wrote:
>
>
>
> > Bummer. Requires rake >= 0.8.4, but RHEL5/EPEL is only 0.8.3.
>
> > .
Rein Henrichs
Dec 15, 2009, 6:20:27 PM12/15/09
to puppet...@googlegroups.com
I understand and sympathize with the political/legal reasons. We obviously want to do our best to support default RHEL4 configurations (since we have so many RHEL4 nodes running Puppet) and it is unfortunate that the available rake RPM lags JUST behind our requirements.
Try running things with a rake >= 0.8.3 dependency in config/environment.rb and see if things break. There may be a simple way to fix it (by monkey-patching rake inside our application, for instance) or it just might work, which would be fantastic. I'll do some digging myself as well.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages