This time we familiarize you with the backings of chef kitchen. Chef kitchen provides you facility of trial and verification of your cookbooks over different environment so that you can confidently use them on your targeted infrastructure. This may be getting boring some times but here is always some seeds in oranges.
This blog requires an initial information about Git and Vagrant. This blog uses centos7 as platform. It needs basic understanding of chef, it’s cookbooks and chef kitchen. To know about chef cookbooks and work with chef kitchen follow our previous blogs of this series Chef Start here with ease...
To setup kitchen chase same procedure as we cater in our previous blog Chef-Kitchen Do it simply .
Backings of Kitchen
Chef kitchen is the diagnosis center of chef. Here you can test the authenticity of your cookbooks on different platforms and confidently use them on your infra. Kitchen achive this by using its configuration file where you define all the things which are necessary to run the complete cycle of kitchen.
This file contains all the required stuff to run chef kitchen. This file is divided into four major sections.
Driver: This is the name of a driver that will be used to create platform instances used during cookbook testing. This is the default driver used for all platforms and suites unless a platform or suite specifies a driver to override the default driver for that platform or suite; a driver specified for a suite will override a driver set for a platform.
Provisioner: This specifies how the chef-client will be simulated during testing. chef_zero andchef_solo are the most common provisioners used for testing cookbooks
Platforms: This is a the name of a platform on which Kitchen will perform cookbook testing, for example,ubuntu-12.04 or centos-6.4; depending on the platform.
Suites: This is a collection of test suites, with each suite_name grouping defining an aspect of a cookbook to be tested.
This directory holds logs for every kitchen run for each platform entry in .kitchen.yml file. This folder also holds keypair for the ssh into your virtual environment.
Analysis of Kitchen
Kitchen performs its own complete cycle of testing via different phases. Kitchen has its five phases i.e., create, converge, login, verify and destroy. Each phase has its own significance and some specific task is gonna performed in every phase.
In this step chef’s kitchen tool creates a virtual instance. This virtual instance could use cloud or any other virtualization technology. Chef supports cookbook testing across many cloud providers and virtualization technologies.
This phase is responsible for application of your cookbook on virtual instance. Here your all cookbooks deployed into the virtual instance, though in next steps you can verify the complete functioning of your cookbooks.
This step creates a ssh session into your machine and provide you a login into it. So that you can run your test to verify the proper functioning of your cookbook.
In this step you manually perform all checks so that you can certify the authenticity of your cookbook over all platforms.
This is the final step of your kitchen testing cycle. Here you destroy your virtual environment after entire testing phases.
Here is also a combine command for all these phases i.e., kitchen test. This command club all the commands in below listed manner.
Hass finally this over!! I know you too get frustrated with the theories. We now aware with the backings of Chef Kitchen.
“Be Warned: I Am Bored. This Could Get Dangerous.”