Configuring
Managed configuration
We have made great effort to provide large-scale clustered support for Enterprise Chef with our Chef deployment. 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 Chef include the following:
| Chef reciple | description |
|---|---|
| lbnchef | Configures chef-server |
| lbnchef::expander | Configures chef-expander |
| lbnchef::rabbitmq | Configures RabbitMQ |
| lbnchef::solr | Configures Apache/Solr |
| lbnchef::couch | Configures a CouchDB server for Chef |
| lbnchef::webui |
Configures the webui server, with Apache/SSL |
| lbnchef::client | Configures client daemon on a Node |
| lbnchef::allinone | Configures a complete Chef server installation on a single machine |
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.
