RSS Feed for This PostCurrent Article

Zenoss Core 2.1.71 (zenoss-2.2-sprint2) Available for Download

The latest packaged version of Zenoss Core, 2.1.71 (zenoss-2.2-sprint2) is available for download. This release continues the 2.2 development cycle.

This sprint release focuses on two main areas of Zenoss Core, ZenPacks and ZenHub consolidation.

With ZenPacks, we have moved to the python egg format which is the standard distribution mechanism for python packages. The move to eggs gives us dependency management of ZenPacks. For ZenPack authors, this is a good time to try porting your ZenPacks from their current zip form to the new egg form. Jason has written this document on how to perform the conversion process. It also details all of the 2.1.71 changes. Please give us feedback on any issues you discover while converting to the new format.

We have also migrated all collector daemons so that they talk though ZenHub. In the current release, some daemons talked directly to databases and others though the hub. The architecture will be easier to maintain now that everyone speaks though the hub.

When upgrading to 2.1.71, you can expect to get some hearbeat errors from zenmodeler, zensyslog and zentrap due to some programmatic changes. You can clear these heartbeats using the Clear heartbeats menu item in the event manager. You should only get these heartbeat errors once.

Zenoss Core 2.1.71 is available from the Zenoss Sprint page.


Here are all of the tickets fixed for this release (Also available in this report):All

  • 1549- Consistently report manager and agent in all events.
  • 1676- Sending events at shutdown causes traceback
  • 2630- Speed up the WMI rebuild process
  • 2640- A fresh install does not create the PerformanceConf Template

DataCollector

  • 2683- Fix getResults for PortscanClient, PythonClient and SshClient
  • 2095- Convert zendisc to a PBDaemon

User Interface

  • 2696- Update copyright on login page to 2008
  • 2618- Device list and event console grid component doesn’t calculate the offset of the next batch properly

ZenEvents

  • 2096- Convert zensyslog to a PBDaemon
  • 2097- Convert zentrap to a PBDaemon

ZenModel

  • 2562- Rest Bindings does not work on device classes
  • 2635- IpInterface.getRRDTemplates() is ill behaved at times
  • 2682- GraphReportElements ill behaved when a component is missing

ZenPack

  • 2664- New edit page for zenpacks
  • 2555- Investigate installation of zenpacks as egg files versus development mode.
  • 2693- ZenPack edit page formatted better
  • 2661- Change sitecustomize to add ZenPacks directory
  • 2670- New zenpack egg format needs to coexist with previous form zenpacks
  • 2672- Make sure auto-install of dependencies works

ZenRRD

  • 2570- upgrade rrdtool to latest stable (1.2.26)
  • 2596- Deleting RRD files fails when device has no perf monitor
  • 2636- GraphDefinition should catch KeyErrors in custom rrd commands

ZenStatus

  • 2093- Convert zenping to a PBDaemon

ZenUtils

  • 2574- add configuration option to allow more time for watchdog initialization
  • 2614- genconf option to commands produces wrong values for the config file

zenossinst

  • 2699- sitecustomize.py lacking a necessary semicolon

zenwin

  • 2650- wmic doesn’t support array types in the result set
  • 2690- Update WMI to wmi-0.1.8
  • 2615- Refactor zenwin as a PBDaemon
  • 2616- Refactor zeneventlog as a PBDaemon
  • 2631- watchdog only the deserving daemons

Enjoy!

–Zenoss Dev Team

Sphere: Related Content

Trackback URL

RSS Feed for This PostPost a Comment