Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

Select Status


zookeeper-cluster (8) Versions 1.1.2

Application cookbook which installs and configures a Zookeeper cluster.

cookbook 'zookeeper-cluster', '= 1.1.2', :supermarket
cookbook 'zookeeper-cluster', '= 1.1.2'
knife supermarket install zookeeper-cluster
knife supermarket download zookeeper-cluster
Quality 0%


Application cookbook which installs and configures
Apache Zookeeper.

Apache Zookeeper is a highly-available, centralized service which is
commonly used for maintaining configuration information, distributed
service discovery and providing coordination services. This cookbook
takes a simplified approach towards configuring Apache Zookeeper.

Basic Usage

This cookbook was designed from the ground up to make it dead simple
to install and configure a Zookeeper cluster using Chef. It also highlights
several of our best practices for developing reusable Chef cookbooks
at Bloomberg.

This cookbook provides [node attributes](attributes/default.rb) which
can be used to fine tune the default recipe which installs and
configures Zookeeper. The values from the node attributes are passed
directly into the configuration and service resources.

Out of the box the following platforms are certified to work and
are tested using our Test Kitchen configuration. Additional platforms
may work, but your mileage may vary.
- CentOS (RHEL) 6.6, 7.1
- Ubuntu 12.04, 14.04

The correct way to use this cookbook is to create a
wrapper cookbook which configures all of the members of the
Zookeeper ensemble (cluster). We do this by using a data bag for each
Chef environment. The default recipe in your wrapper cookbook may
look something like the following block:
bag = data_bag_item('config', 'zookeeper')[node.chef_environment]
node.default['zookeeper-cluster']['config']['instance_name'] = node['ipaddress']
node.default['zookeeper-cluster']['config']['ensemble'] = bag['ensemble']
include_recipe 'zookeeper-cluster::default'

The data bag for the above block should have an array of
fully-qualified hostnames, the exact ones that appear in
node['fqdn'], which represent the members of the Zookeeper
ensemble. These hostnames are used when configuring the Zookeeper
service on each node.
"id": "zookeeper",
"development": {
"production": {

Dependent cookbooks

java >= 0.0.0
libartifact ~> 1.3
poise ~> 2.2
poise-service ~> 1.0
selinux >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Foodcritic Metric

1.1.2 failed this metric

FC031: Cookbook without metadata file: /tmp/cook/6c54e1039111216c80533a7c/zookeeper-cluster/metadata.rb:1
FC045: Consider setting cookbook name in metadata: /tmp/cook/6c54e1039111216c80533a7c/zookeeper-cluster/metadata.rb:1