Description

Chef zookeeper_bridge cookbook, used to help integrating the Chef Run with ZooKeeper.

It can help in the following:

• Installing and running Chef ZooKeeper Handler.
• Reading or writing Chef Node attributes to and from ZooKeeper.
• Running ZooKeeper Client commands.
• Interacting with ZooKeeper read/write locks during the Chef Run.
• Interacting with ZooKeeper semaphores during the Chef Run.
• Wait until a ZooKeeper znode has the desired state or a certain event happens.

Some of the resources included in this cookbook have not been widely tested, so you should consider this cookbook as something experimental.

This cookbook is mainly used by calling the resources it provides. See their documentation below. The zookeeper_bridge::default recipe needs to be included before their use.

Requirements

Supported Platforms

This cookbook has been tested on the following platforms:

• Amazon
• CentOS
• Debian
• Fedora
• RedHat
• Ubuntu

Please, let us know if you use it successfully on any other platform.

Required Cookbooks

• build-essential ~> 2.0
• chef_handler

Required Applications

• Ruby 1.9.3 or higher.
• zk ruby gem.

Attributes

<table>
<tr>
<th>Attribute</th>
<th>Description</th>
<th>Default</th>
</tr>
<tr>
<td><code>node['zookeeper_bridge']['server']</code></td>
<td>ZooKeeper server address.</td>
<td><code>"127.0.0.1:2181"</code></td>
</tr>
<tr>
<td><code>node['zookeeper_bridge']['chef_handler']['version']</code></td>
<td><code>chef-handler-zookeeper</code> gem version to install.</td>
<td><code>nil</code> <em>(latest)</em></td>
</tr>
<tr>
<td><code>node['zookeeper_bridge']['chef_handler']['znode']</code></td>
<td><code>chef-handler-zookeeper</code> znode path. The path must be absolute.</td>
<td><code>"/chef/#{node.name}/status"</code></td>
</tr>
</table>

Recipes

zookeeper_bridge::default

Recipe required before using the resources.

zookeeper_bridge::chef_handler

Installs and enables chef-handler-zookeeper gem.

zookeeper_bridge::chef_handler Example

The node['zookeeper_bridge']['chef_handler']['znode'] path must exist before calling this recipe:

$ ./zkCli.sh
[zk: localhost:2181(CONNECTED) 0] create /chef {}
[zk: localhost:2181(CONNECTED) 1] create /chef/server1.example.com {}
[zk: localhost:2181(CONNECTED) 2] create /chef/server1.example.com/status {}

Or using the recipe itself:

# We set the ZooKeeper server address
node.default['zookeeper_bridge']['server'] = 'zk.example.com'

# zookeeper_bridge_cli resource should ignore cli errors if they already exist
zookeeper_bridge_cli 'create /chef {}'
zookeeper_bridge_cli "create /chef/#{node.name} {}"
zookeeper_bridge_cli "create /chef/#{node.name}/status {}"

This is because the chef-handler-zookeeper requires that the znode exists.

Now we can install and enable the handler:

node.default['zookeeper_bridge']['chef_handler']['znode'] = "/chef/#{node.name}/status"
include_recipe 'zookeeper_bridge::chef_handler'

zookeeper_bridge::depends

Install some dependencies required by this cookbook. Used by the other recipes.

Resources

zookeeper_bridge_rdlock[path]

Runs a Read or Shared Lock inside ZooKeeper. This resource is intended to be used together with the zookeeper_bridge_wrlock resource.

zookeeper_bridge_rdlock Actions

• run

zookeeper_bridge_rdlock Parameters

<table>
<tr>
<th>Parameter</th>
<th>Description</th>
<th>Default</th>
</tr>
<tr>
<td>path</td>
<td>Znode path. The path can be relative to <code>"/_zklocking"</code>.</td>
<td><em>name</em></td>
</tr>
<tr>
<td>server</td>
<td>ZooKeeper server address.</td>
<td><code>node['zookeeper_bridge']['server']</code></td>
</tr>
<tr>
<td>wait</td>
<td>This can be an integer to wait a maximum of seconds and raise a timeout exception if this time is exceeded. By default is set to <code>true</code>, which will wait infinitely.</td>
<td><code>true</code></td>
</tr>
<tr>
<td>block</td>
<td>The <em>recipe code</em> that will be run within the lock.</td>
<td><code>nil</code></td>
</tr>
</table>

zookeeper_bridge_rdlock Examples

zookeeper_bridge_rdlock 'lock1' do
  server 'zk.example.com'
  block do
    # recipe code can be used here
    execute '...'
  end
end

Then we can use an exclusive lock from another node:

zookeeper_bridge_wrlock 'lock1' do
  server 'zk.example.com'
  block do
    # recipe code can be used here
    execute '...'
  end
end

zookeeper_bridge_wrlock[path]

Runs a Write or Exclusive Lock inside ZooKeeper. This resource is intended to be used together with the zookeeper_bridge_rdlock resource.

zookeeper_bridge_wrlock Actions

• run

zookeeper_bridge_wrlock Parameters

<table>
<tr>
<th>Parameter</th>
<th>Description</th>
<th>Default</th>
</tr>
<tr>
<td>path</td>
<td>Znode path. The path can be relative to <code>"/_zklocking"</code>.</td>
<td><em>name</em></td>
</tr>
<tr>
<td>server</td>
<td>ZooKeeper server address.</td>
<td><code>node['zookeeper_bridge']['server']</code></td>
</tr>
<tr>
<td>wait</td>
<td>This can be an integer to wait a maximum of seconds and raise a timeout exception if this time is exceeded. By default is set to <code>true</code>, which will wait infinitely.</td>
<td><code>true</code></td>
</tr>
<tr>
<td>block</td>
<td>The <em>recipe code</em> that will be run within the lock.</td>
<td><code>nil</code></td>
</tr>
</table>

zookeeper_bridge_wrlock Examples

The following block will only be running by a maximum of one node at a particular instant:

zookeeper_bridge_wrlock 'lock1' do
  server 'zk.example.com'
  block do
    # recipe code can be used here
    execute '...'
  end
end

zookeeper_bridge_sem[path]

Runs a Semaphore inside ZooKeeper.

zookeeper_bridge_sem Actions

• run

zookeeper_bridge_sem Parameters

<table>
<tr>
<th>Parameter</th>
<th>Description</th>
<th>Default</th>
</tr>
<tr>
<td>path</td>
<td>Znode path. The path can be relative to <code>"/_zksemaphore"</code>.</td>
<td><em>name</em></td>
</tr>
<tr>
<td>server</td>
<td>ZooKeeper server address.</td>
<td><code>node['zookeeper_bridge']['server']</code></td>
</tr>
<tr>
<td>size</td>
<td>Semaphore size: the maximum number of nodes that will be able to run the block at the same time.</td>
<td><code>nil</code></td>
</tr>
<tr>
<td>block</td>
<td>The <em>recipe code</em> that will be run within the semaphore.</td>
<td><code>nil</code></td>
</tr>
<tr>
<td>wait</td>
<td>This can be an integer to wait a maximum of seconds and raise a timeout exception if this time is exceeded. By default is set to <code>true</code>, which will wait infinitely.</td>
<td><code>true</code></td>
</tr>
</table>

zookeeper_bridge_sem Examples

You can call this from multiple nodes. The code within the following block will be running by a maximum of three nodes at the same time:

zookeeper_bridge_sem 'sem1' do
  server 'zk.example.com'
  size 3
  block do
    # recipe code can be used here
    execute '...'
  end
end

zookeeper_bridge_attrs[path]

Used to read or write Chef Node attributes from or to ZooKeeper znode paths. The attributes are saved into the znode using JSON format.

zookeeper_bridge_attrs Actions

• read: Read Node attributes from a znode.
• write: Write Node attributes to a znode.

zookeeper_bridge_attrs Parameters

<table>
<tr>
<th>Parameter</th>
<th>Description</th>
<th>Default</th>
</tr>
<tr>
<td>path</td>
<td>Znode path. The path must be absolute.</td>
<td><em>name</em></td>
</tr>
<tr>
<td>server</td>
<td>ZooKeeper server address.</td>
<td><code>node['zookeeper_bridge']['server']</code></td>
</tr>
<tr>
<td>attribute</td>
<td>Node attribute object or a Ruby Hash. This should be something like <code>node['foo']</code> for <strong>reading</strong> and <code>node.normal['foo']</code> for <strong>writing</strong>.</code></td>
<td><code>nil</code></td>
</tr>
<tr>
<td>key</td>
<td>JSON sub-key to use for storing the attributes. This key is merged with the other JSON keys that currently exists in the znode. By default no key is used: attributes are at a root level JSON object.</td>
<td><code>nil</code></td>
</tr>
<tr>
<td>force_encoding</td>
<td>Force character encoding. For example: <code>"UTF-8"</code>.</td>
<td><code>nil</code></td>
</tr>
</table>

zookeeper_bridge_attrs Examples

Reading All Node Attributes

The znode to read attributes from must exist before reading it. For writting, at least the parent znode must exist:

$ ./zkCli.sh
[zk: localhost:2181(CONNECTED) 0] create /chef {}
[zk: localhost:2181(CONNECTED) 1] create /chef/server1.example.com {}
[zk: localhost:2181(CONNECTED) 2] create /chef/server1.example.com/read_attributes {"attr1":"value1"}

We can also create them from a recipe using zookeeper_bridge_cli:

# We set the ZooKeeper server address
node.default['zookeeper_bridge']['server'] = 'zk.example.com'

# zookeeper_bridge_cli resource should ignore cli errors if they already exist
zookeeper_bridge_cli('create /chef {}').run_action(:run)
zookeeper_bridge_cli("create /chef/#{node.name} {}").run_action(:run)
# zkCli.sh does not support spaces in the data:
zookeeper_bridge_cli("create /chef/#{node.name}/read_attributes {\"attr1\":\"value1\"}")
  .run_action(:run)

Now we can read and write all node attributes from and to ZooKeeper:

zookeeper_bridge_attrs "/chef/#{node.name}/read_attributes" do
  attribute node.normal
  action :nothing
end.run_action(:read)

# [...]

zookeeper_bridge_attrs "/chef/#{node.name}/write_attributes" do
  attribute node.attributes
  action :write
end

Note: You need to understand how compile and converge phases work on Chef Run to know when to use #run_action.

Reading and Writing Apache Cookbook Attributes

As in the previous example, we create the necessary znodes:

$ ./zkCli.sh
[zk: localhost:2181(CONNECTED) 0] create /chef {}
[zk: localhost:2181(CONNECTED) 1] create /chef/server1.example.com {}
[zk: localhost:2181(CONNECTED) 2] create /chef/server1.example.com/apache_attributes {}

We can also create them from a recipe using zookeeper_bridge_cli:

# We set the ZooKeeper server address
node.default['zookeeper_bridge']['server'] = 'zk.example.com'

# zookeeper_bridge_cli resource should ignore cli errors if they already exist
zookeeper_bridge_cli 'create /chef {}'
zookeeper_bridge_cli "create /chef/#{node.name} {}"
zookeeper_bridge_cli "create /chef/#{node.name}/apache_attributes {}"

Now we can read and write apache attributes:

# We use override in this case to overwrite default and normal values, why not?
zookeeper_bridge_attrs "/chef/#{node.name}/apache_attributes" do
  attribute node.override['apache']
  action :nothing
end

# [...]

zookeeper_bridge_attrs "/chef/#{node.name}/apache_attributes" do
  attribute node['apache']
  action :write
end

zookeeper_bridge_wait[path]

Waits until a given ZooKeeper znode path exists, does not exist or changes its state.

zookeeper_bridge_wait Actions

• run

zookeeper_bridge_wait Parameters

<table>
<tr>
<th>Parameter</th>
<th>Description</th>
<th>Default</th>
</tr>
<tr>
<td>path</td>
<td>Znode path. The path must be absolute.</td>
<td><em>name</em></td>
</tr>
<tr>
<td>server</td>
<td>ZooKeeper server address.</td>
<td><code>node['zookeeper_bridge']['server']</code></td>
</tr>
<tr>
<td>status</td>
<td>Wait until znode has this status. Possible values: <code>:any</code>, <code>:created</code> or <code>:deleted.</code>. <code>:any</code> means to ignore the status, normally used when the <code>event</code> parameter below is set.</td>
<td><code>:any</code></td>
</tr>
<tr>
<td>event</td>
<td>Wait until specific znode event occurs. Possible values: <code>:none</code>, <code>:created</code>, <code>:deleted.</code>, <code>:changed</code>, <code>:child</code> or an array of multiple values. <code>:none</code> means to ignore the events, normally used when the <code>status</code> parameter is set. <code>:child</code> is for znode child events.</td>
<td><code>:none</code></td>
</tr>
</table>

zookeeper_bridge_wait Examples

Wait until host znode is created (at compile time, to avoid compilling the next resources):

zookeeper_bridge_wait "/chef/#{node.name}" do
  status :created
  event :none
  action :nothing
end.run_action(:run)

Wait until the attributes exists before reading them:

zookeeper_bridge_wait "/chef/#{node.name}/attributes" do
  status :created
  event :none
  action :nothing
end.run_action(:run)

zookeeper_bridge_attrs "/chef/#{node.name}/attributes" do
  attribute node.normal
  action :nothing
end.run_action(:read)

Continue the Chef Run convergence only when the stop znode does not exist:

zookeeper_bridge_wait "/chef/#{node.name}/chef_stop" do
  status :deleted
  event :none
end

Continue the Chef Run convergence only when the continue znode is updated:

zookeeper_bridge_wait "/chef/#{node.name}/chef_continue" do
  status :any
  event :changed
end

zookeeper_bridge_cli[path]

Runs a ZooKeeper command using the zkCli.sh script. This resouce should be run from the ZooKeeper server node, because zkCli.sh connects to localhost (connecting to remote server is not supported yet).

Remember that this script has some limitations, so use it with caution.

zookeeper_bridge_cli Actions

• run: Runs a command.

zookeeper_bridge_cli Parameters

<table>
<tr>
<th>Parameter</th>
<th>Description</th>
<th>Default</th>
</tr>
<tr>
<td>command</td>
<td>ZooKeeper <code>zkCli.sh</code> command.</td>
<td><em>name</em></td>
</tr>
<tr>
<td>base_path</td>
<td>ZooKeeper installation path.</td>
<td><code>"#{node['zookeeper']['install_dir']}/zookeeper-#{node['zookeeper']['version']}"</code></td>
</tr>
<tr>
<td>sleep</td>
<td>Time to sleep in seconds before the command is run (type <code>Float</code>).</td>
<td><code>nil</code></td>
</tr>
<tr>
<td>background</td>
<td>Whether to run the command in background.</td>
<td><code>false</code></td>
</tr>
</table>

zookeeper_bridge_cli Examples

zookeeper_bridge_cli 'create /test some_random_data'

This resource is currently used in the integration tests. See the zookeeper_bridge_test cookbook recipes for more usage examples.

Testing

See TESTING.md.

Contributing

Please do not hesitate to open an issue with any questions or problems.

See CONTRIBUTING.md.

TODO

See TODO.md.

License and Author

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.