Configuring
Our Chef/OpenStack recipes
We sell and support Opscode/Chef and have an extensive range of recipes that deploy and configure our best-practice Enterprise Zenoss. Our recipes evolve over time as the platform changes and technologies change, but that is the point. Our considerable expertise is commoditised and made available to you at an amazing price point.
Our suite of recipes to deploy Zenoss include the following:
| Chef role | description |
|---|---|
| Apache | We configure an optiimised Apache to handle SSL and redirection to other web services |
| Squid | We utlise the latest Squid 3.x with Edge Side Includes (ESI) and optimised URL redirector to your Zenoss |
| Zope Application Server | Our standard Zope server configuration with the backend of your choice |
| Zope Backend |
|
| Monitoring |
We set up a combination of SNMP, ZenPacks.lbn.ZopeMonitor and other client-side services for our Zenoss to monitor your Zenoss assets and provide capacity management information over time. |
Our Chef isn't a one-size fits all. Once you've registered your server (or Node in Chef-parlance), we have fantastic granularity to override and customise configuration specifically for you. We already incorporate a wide range of roles and features to deploy clustered solutions, or all-in-one, and quite a bit in between. If you have governance or risk requirements that preclude you from our Cloud-service, we can sell you our Chef and our Zope and Plone recipes for internal use and management. We even have systems in place to ship you updates to our recipes as we extend and enhance them over time.
