Configuration Management using chef is being implemented with the help of desire files, which is often called a “cookbooks” in chef. Usuallay separate cookbooks is written in practice for each module so its easy to maintain. Also, there are good numbers of cookbooks which is being used from community portal which is from supermarket.chef.io.<\/p>\n
In order to meet the desire state in servers, once the multile cookbooks is used, Very often these cookbooks become large and highly interdependent, it becomes necessary to manage these cookbooks itself.<\/p>\n
Berkshelf is the tool which makes \u2018the management\u2019 & dependency management between cookbooks easy. Berkshelf is a dependency manager for Chef cookbooks. With it, you can easily depend on community cookbooks and have them safely included in your workflow. Using Berkshelf, you need to package, bundle dependent cookbooks rather using it will download from “source” which is defined in Berksfile.<\/p>\n
Berkshelf is included in the Chef Development Kit.<\/p>\n
Quick Start<\/strong> [code]name ‘my_first_cookbook’ The default Berksfile will contain the following:<\/p>\n [code]source ‘https:\/\/supermarket.chef.io’ Now, when you run “berks install<\/strong>“, the apt cookbook will be downloaded from Supermarket into the cache…<\/p>\n [code]$ berks install Example of Berksfile<\/strong><\/p>\n [code]source “https:\/\/supermarket.chef.io”<\/p>\n metadata Important Notes<\/strong>
\nRunning “chef generate cookbook<\/strong>” will, by default, create a Berksfile in the root of the cookbook, alongside the cookbook\u2019s metadata.rb. As usual, add your cookbook\u2019s dependencies to the metadata:<\/p>\n
\nversion ‘0.1.0’
\ndepends ‘apt’, ‘~> 5.0′[\/code]<\/p>\n
\nmetadata[\/code]<\/p>\n
\nResolving cookbook dependencies…
\nFetching ‘my_first_cookbook’ from source at .
\nFetching cookbook index from https:\/\/supermarket.chef.io…
\nInstalling apt (5.0.0)
\nUsing my_first_cookbook (0.1.0) from source at .
\nInstalling compat_resource (12.16.2)[\/code]<\/p>\n
\ncookbook ‘zabbix-agent’, path: ‘cookbooks\/zabbix-agent’
\ncookbook ‘hostnames’, path: ‘cookbooks\/hostnames’
\ncookbook ‘chef-client’, path: ‘cookbooks\/chef-client’
\ncookbook ‘rethinkdb’, path: ‘cookbooks\/rethinkdb’
\ncookbook ‘zookeeper’, path: ‘cookbooks\/zookeeper’
\ncookbook ‘logstash’, path: ‘cookbooks\/logstash’
\ncookbook ‘kafka’, path: ‘cookbooks\/kafka’
\ncookbook ‘elasticsearch’, path: ‘cookbooks\/elasticsearch’
\ncookbook ‘testbook’, path: ‘cookbooks\/testbook’
\ncookbook ‘base-ubuntu’, path: ‘cookbooks\/base-ubuntu'[\/code]<\/p>\n
\nFor new users, we strongly recommend using Policyfiles rather than Berkshelf. Policyfiles provide more predictability, since dependencies are only resolved once, and a much improved way of promoting cookbooks from dev to testing, and then to production. Note that Policyfile is not supported as part of a Chef Automate workflow.<\/p>\n\n