cookbook 'zookeeper-cluster', '= 1.3.0'
zookeeper-cluster (8) Versions 1.3.0 Follow2
Application cookbook which installs and configures a Zookeeper cluster.
cookbook 'zookeeper-cluster', '= 1.3.0', :supermarket
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.example.com",
"zk2.dev.inf.example.com",
"zk3.dev.inf.example.com"
},
"production": {
"zk1.prod.inf.example.com",
"zk2.prod.inf.example.com",
"zk3.prod.inf.example.com",
"zk4.prod.inf.example.com",
"zk5.prod.inf.example.com",
}
}
Dependent cookbooks
java >= 0.0.0 |
libartifact ~> 1.3 |
poise ~> 2.2 |
poise-service ~> 1.0 |
selinux >= 0.0.0 |
rc ~> 1.5 |
Contingent cookbooks
There are no cookbooks that are contingent upon this one.
Change Log
All notable changes to this project will be documented in this file.
This project adheres to Semantic Versioning.
[Unreleased]
1.3.0
- PR#16 Fixes service resource not restarting when upgraded.
- PR#17 Adds support for log4j configuration.
1.2.0
- Fixes several issues with usage of the Poise Service cookbook.
- Fixes a few bits for testing and linting harness.
1.0.0
- Custom resources for managing Apache Zookeeper configuration and service lifecycle.
- Default recipe which installs Apache Zookeeper and starts service from attributes.
Foodcritic Metric
1.3.0 passed this metric
1.3.0 passed this metric