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.
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.
Berkshelf is the tool which makes ‘the management’ & 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.
Berkshelf is included in the Chef Development Kit.
Running “chef generate cookbook” will, by default, create a Berksfile in the root of the cookbook, alongside the cookbook’s metadata.rb. As usual, add your cookbook’s dependencies to the metadata:
depends ‘apt’, ‘~> 5.0′[/code]
The default Berksfile will contain the following:
Now, when you run “berks install“, the apt cookbook will be downloaded from Supermarket into the cache…
[code]$ berks install
Resolving cookbook dependencies…
Fetching ‘my_first_cookbook’ from source at .
Fetching cookbook index from https://supermarket.chef.io…
Installing apt (5.0.0)
Using my_first_cookbook (0.1.0) from source at .
Installing compat_resource (12.16.2)[/code]
Example of Berksfile
cookbook ‘zabbix-agent’, path: ‘cookbooks/zabbix-agent’
cookbook ‘hostnames’, path: ‘cookbooks/hostnames’
cookbook ‘chef-client’, path: ‘cookbooks/chef-client’
cookbook ‘rethinkdb’, path: ‘cookbooks/rethinkdb’
cookbook ‘zookeeper’, path: ‘cookbooks/zookeeper’
cookbook ‘logstash’, path: ‘cookbooks/logstash’
cookbook ‘kafka’, path: ‘cookbooks/kafka’
cookbook ‘elasticsearch’, path: ‘cookbooks/elasticsearch’
cookbook ‘testbook’, path: ‘cookbooks/testbook’
cookbook ‘base-ubuntu’, path: ‘cookbooks/base-ubuntu'[/code]
For 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.
- Example of S3 Bucket Policy to allow from IP address and Domain name - August 28, 2020
- kubernetes ingress complete reference - August 7, 2020
- Kubernetes POD observability and Deep Dive - August 7, 2020