cookbook 'zookeeper-cluster', '= 1.1.0', :supermarket
zookeeper-cluster (8) Versions 1.1.0 Follow2
Application cookbook which installs and configures a Zookeeper cluster.
cookbook 'zookeeper-cluster', '= 1.1.0'
knife supermarket install zookeeper-cluster
knife supermarket download zookeeper-cluster
zookeeper-cluster-cookbook
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:
ruby
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.
json
{
"id": "zookeeper",
"development": {
"zk1.dev.inf.hostname.com",
"zk2.dev.inf.hostname.com",
"zk3.dev.inf.hostname.com"
},
"production": {
"zk1.prod.inf.hostname.com",
"zk2.prod.inf.hostname.com",
"zk3.prod.inf.hostname.com",
"zk4.prod.inf.hostname.com",
"zk5.prod.inf.hostname.com",
}
}
Dependent cookbooks
java >= 0.0.0 |
libartifact ~> 1.3 |
poise ~> 2.0 |
poise-service >= 0.0.0 |
selinux >= 0.0.0 |
Contingent cookbooks
There are no cookbooks that are contingent upon this one.
Foodcritic Metric
1.1.0 failed this metric
FC031: Cookbook without metadata file: /tmp/cook/6e413607b216050840293004/zookeeper-cluster/metadata.rb:1
FC045: Consider setting cookbook name in metadata: /tmp/cook/6e413607b216050840293004/zookeeper-cluster/metadata.rb:1
1.1.0 failed this metric
FC045: Consider setting cookbook name in metadata: /tmp/cook/6e413607b216050840293004/zookeeper-cluster/metadata.rb:1