Chef - Available Testing Frameworks - InSpec and ChefSpec

1. We need to download the correct version of ChefDK, which is 2.4.17. In a command line, run:

   wget https://packages.chef.io/files/stable/chefdk/2.4.17/el/7/chefdk-2.4.17-1.el7.x86_64.rpm
   

2. Now install it:

   sudo rpm -ivh chefdk-2.4.17-1.el7.x86_64.rpm
   

3. Once it's installed, we need to make sure Chef uses the correct system locations for things:

   echo 'eval "$(chef shell-init bash)"' >> ~/.bash_profile
   

   source ~/.bash_profile
   

4. Now check to see if it worked with which ruby and we should see /opt/chefdk/embedded/bin/ruby get returned.

1. We need Docker on our workstation so we will need to run the following commands:

   sudo yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo 
   

   sudo yum-config-manager --setopt="docker-ce-stable.baseurl=https://download.docker.com/linux/centos/7/x86_64/stable" --save 
   

   sudo yum-config-manager --add-repo=http://mirror.centos.org/centos/7/extras/x86_64/ 
   

   sudo rpm --import https://www.centos.org/keys/RPM-GPG-KEY-CentOS-7 
   

   sudo yum install -y container-selinux docker-ce
   

2. Now, let's start Docker and enable it to start on system boot:

   sudo systemctl start docker
   

   sudo systemctl enable docker
   

3. We should also set your user to be able to use Docker without using the sudo command. Once we've done this, we have to log out and back in again:

   sudo usermod -aG docker $USER
   

   exit
   

4. Use SSH to get back in again and check to make sure Docker is running:

   docker ps
   

   If we can do that without prefacing it with sudo, we're ready to continue.

When we use Kitchen later in the lab, we need Git to be installed and set up with some basic information. These commands will make that happen.

1. Install it:

   sudo yum -y install git
   

2. Configure some Git basics like the username, email address, and a default text editor:

   git config --global user.name "USERNAME"
   

   git config --global user.email "[email protected]"
   

   git config --global core.editor vim
   

   Note: We can use fake email information since we don't actually use it for this lab. It just needs to be set or we will get errors later.

1. Docker requires a gem for this all to work. Install it with this:

   gem install kitchen-docker
   

1. To perform the tasks properly, you should change SELinux so that it is permissive:

   sudo setenforce permissive
   

2. We should also edit /etc/selinux/config and change things to permissive there too:

   sudo vim /etc/selinux/config
   

   Change the SELINUX line from SELINUX=enforcing to SELINUX=permissive.

1. Create the cookbook with this command:

   chef generate cookbook la_testing
   

2. Now, change to the newly created directory:

   cd la_testing
   

1. Edit kitchen.yml:

   vim .kitchen.yml
   

2. In the top section, replace vagrant with docker and add some things. When we're done, that top section should look like this:

   ---
   driver:
     name: docker
     privileged: true
     use_sudo: false
   

   Remember that this is YAML, so we need to make sure we have the right number of spaces in spots. Those lines under driver are all indented two spaces.

3. Down in the provisioner section, we need to add a name and version. It should look like this when we're done:

   provisioner:
     name: chef_zero
     # You may wish to disable always updating cookbooks in CI or other testing environments.
     # For example:
     #   always_update_cookbooks: <%= !ENV['CI'] %>
     always_update_cookbooks: true
     product_name: "chef"
     product_version: "13.8.5"
   

4. We're on a CentOS machine so we need to get rid of ubuntu from the file. Just delete (or comment out) the line in the platforms section that reads:

     - name: ubuntu-16.04
   

That's it for kitchen.yml edits. Write and quit so that we can get back to the command prompt.

1. Edit the default recipe:

   vim recipes/default.rb
   

2. Add this to the end of the file:

   ['net-tools','httpd'].each do |pkg|
     package pkg do
      action :install
     end
   end
   

1. Edit the InSpec test:

   vim test/smoke/default/default_test.rb
   

2. At the end of this file, we need to add:

   ['net-tools','httpd'].each do |pkg|
     describe package(pkg) do
      it { should be_installed }
     end
   end
   

1. We've finished the InSpec portion of our tests. Now, let's edit the ChefSpec test so that it does what we need it to:

   vim spec/unit/recipes/default_spec.rb
   

2. Here, we want to remove any reference to Ubuntu tests. Let's erase lines 10-22 (the whole first context section):

     context 'When all attributes are default, on Ubuntu 16.04' do
       let(:chef_run) do
         # for a complete list of available platforms and versions see:
         # https://github.com/customink/fauxhai/blob/master/PLATFORMS.md
         runner = ChefSpec::ServerRunner.new(platform: 'ubuntu', version: '16.04')
         runner.converge(described_recipe)
       end
   
       it 'converges successfully' do
         expect { chef_run }.to_not raise_error
       end
     end
   

3. We should just have a CentOS section now. Let's add our test to this (for net-tools and httpd). The whole section should look like this:

   describe 'la_testing::default' do
     context 'When all attributes are default, on CentOS 7.4.1708' do
       let(:chef_run) do
         # for a complete list of available platforms and versions see:
         # https://github.com/customink/fauxhai/blob/master/PLATFORMS.md
         runner = ChefSpec::ServerRunner.new(platform: 'centos', version: '7.4.1708')
         runner.converge(described_recipe)
       end
   
       it 'converges successfully' do
         expect { chef_run }.to_not raise_error
       end
   
       it 'installs httpd' do
         expect(chef_run).to install_package('httpd')
       end
       it 'installs net-tools' do
         expect(chef_run).to install_package('net-tools')
       end
     end
   end
   

4. Save this file and let's run some tests!

1. We're going to run the ChefSpec test that we just altered with this command:

   chef exec rspec --color -fd
   

   If everything passes, we can move on.

1. To test if this cookbook works, we'll run:

   kitchen verify
   

2. You may also notice, in the end of the output, that our InSpec test gets run. If that all looks good, we're done. Clean up the mess with this:

   kitchen destroy