You are here: Home / News / RPM/Zenoss 4.2.3 - with managed service!

RPM/Zenoss 4.2.3 - with managed service!

by Alan Milligan last modified Jan 29, 2013 03:15 PM
Check out our managed-service Zenoss//Zentinel on BastionLinux/RHEL6

We've been beta-testing our Zenoss4/Chef deployment for some time now, and with 4.2.3, we're very happy to announce that we're now launching this offering.


  • Zenoss 4.2.3 runs on our bulletproof Zope stack, which we reguarly update, and has important security patches
  • All versions of Zenoss we ship (3.x, 4.x) run on the same underlying Zope stack, meaning a straightforward migration process
  • Our Zenoss 4.2.3 runs on Python 2.6, and we've worked really hard to use all the Red Hat/vendor-supplied packages possible so that your licensing support covers most of your critical Zenoss infrastructure
  • We use the Chameleon template rendering engine, giving you 20-50% faster Zentinel/portal performance
  • Our Zenoss 4.2.3 uses our standardised Monit for sophisticated startup/stop services dependency management, and auto restart/watchdogging.
  • Our Zenoss 4.2.3/Chef infrastructure is completely granular to support large clustered, scaled, redundant deployments 
  • Our Zenoss 4.2.3 runs with the latest Celery 3.x, giving better performance for jobber
  • Our Zenoss 4.2.3/ZEP runs on OpenJDK, with a smaller memory footprint than possible with Sun/Oracle/Hotspot.


Our Zenoss 4.2.3 is also available for other virtualisation platforms including VMWare, Qemu, and VirtualBox.  We will soon be releasing all of our Cloud infrastructure products on Amazon Web Services Marketplace - we'll let you know as soon as Zenoss  is available.


Managed Service Offering

You can now register your Zenoss installation(s) with our OpsCode/Chef infrastructure - explicitly focused around Enterprise Zope/Plone/Zenoss deployment.  We've built out a sophisticated suite of recipes for large-scale Zope/Web Services environments.  We've fully automated everything from Apache/SSL/rewrites through front-end cache servers, Zope products and extensions, standalone,ZEO, and RDBS backends, LDAP/SSO, ZenPacks, and much more.  This is all modular, and from the outset designed for clustering as well as all-in server deployments.

We have an automated migration from Zenoss 3.x/ZEO to Zenoss 4.x/RDBMS/RelStorage.

We ship the Chef client on all of our platforms.  All you need to do to participate is to contact us to receive the X509/Validation certificate for our Chef service.

We can make our entire Chef/Zenoss infrastructure available for you internally - just check out our Chef Channel (this is also RHEL6 compatible).


Petition Us

We've a range of other features we're working on and if you support us, we'll work to making these available on PyPi.  Features we're very interested in delivering include:

  • Backporting ZEO (smaller sites don't gain any advantage by requiring RDBMS for Zope)
  • PostgreSQL support (we really like the PostgreSQL 9.1 replication solution for redundancy)
  • Oracle Support (our Zope/RelStorage has been industrially tested with MySQL/PostgreSQL/Oracle)
  • OpenSuSE/SLES port.  This is quite probably dead given that  nobody was prepared to contribute to funding (see discussion)...
  • Running ZEP on tomcat/jboss/websphere/weblogic


Register your interest

We can immediately introduce you to our offerings (particularly Zenoss 2.x, 3.x) and discuss our structured migration approach to Zenoss 4 with our automated Chef infrastructure. 

There are a variety of ways to contact us: