test-kitchen / kitchen-rackspace

A Rackspace Cloud driver for Test Kitchen

Test Kitchen

Website	https://kitchen.ci/
Source Code	https://kitchen.ci/docs/getting-started/introduction/
Slack	#test-kitchen channel on Chef Community Slack

Test Kitchen is an integration tool for developing and testing infrastructure code and software on isolated target platforms.

Getting Started Guide

To learn how to install and setup Test Kitchen for developing infrastructure code, check out the Getting Started Guide.

If you want to get going super fast, then try the Quick Start next...

Quick Start

Test Kitchen is a RubyGem and can be installed with:

gem install test-kitchen

If you use Bundler, you can add gem "test-kitchen" to your Gemfile and make sure to run bundle install.

Next add support to your library, Chef cookbook, or empty project with kitchen init:

kitchen init

A kitchen.yml file will be created in your project base directory. This file describes your testing configuration; what you want to test and on which target platforms. Each of these suite and platform combinations are called instances. By default your instances will be converged with Chef Solo and run in Vagrant virtual machines.

Get a listing of your instances with:

kitchen list

Run Chef Infra Client on an instance, in this case default-ubuntu-2004, with:

kitchen converge default-ubuntu-2004

Destroy all instances with:

kitchen destroy

You can clone a Chef Infra cookbook project that contains Test Kitchen support and run through all the instances in serial by running:

kitchen test

Usage

There is help included with the kitchen help subcommand which will list all subcommands and their usage:

kitchen help test

More verbose logging for test-kitchen can be specified when running test-kitchen from the command line using:

kitchen test -l debug

For the provisioner (e.g. chef-solo or chef-infra) add a log_level item to the provisioner section of the .kitchen.yml For more information on setting log_level see the configuration documentation.

Documentation

Documentation is being added on the Test Kitchen website. Please read and contribute to improve them!

Versioning

Test Kitchen aims to adhere to Semantic Versioning 2.0.0.

Community and Ecosystem

If you would like to see a few of the plugins or ecosystem helpers, please look at ECOSYSTEM.md.

Development

• Source hosted at GitHub
• Report issues/questions/feature requests on GitHub Issues

Pull requests are very welcome! Make sure your patches are well tested. Ideally create a topic branch for every separate change you make. For example:

1. Fork the repo
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Added some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create a new Pull Request

Authors

Created by Fletcher Nichol ([email protected]).

Maintained by Chef Software and a growing community of contributors.

License

Apache License, Version 2.0 (see LICENSE)

kitchen-rackspace's Issues

config[:name] is now used by Test Kitchen...

Need to change the config var for server names. Right now, generate_name never gets called because the "name" is already "rackspace".

rebuild servers that build in error state

Use Project Name in Server Hostname

Too hard to tell at a glance which server is which.

Support for disabling the root password lockout implemented by fog

Per fog/fog#3715, fog's bootstrap method for Rackspace Compute v2 actually locks the root user out. It has an optional flag to disable the functionality. We should add that as a pass-through option for kitchen-rackspace.

Support waiting for service level automation before continuing

Similar to chef-boneyard/knife-rackspace#42, we should add support for waiting on service level automation before bootstrapping further.

Support friendly flavor names

kitchen-rackspace does not support winrm as a transport

While trying to test cookbooks in rackspace we found that kitchen-rackspace can only use the ssh transport.

Support friendly image names

Start building in TravisCI

Dynamically Support Friendlier Images and/or Flavors

#17 added a hash of friendly image names:Rackspace image IDs. The next step beyond that would be to grab the available images and flavors from Fog and parse those so this project doesn't need updates each time there's a new image released.

RSpec Tests(?)

Fog Gem Issue

As part of the auto-releasing work I'm doing, I'm updating the workflows to actually run tests in GitHub Actions.

bundle exec rake test currently returns:

An error occurred while loading ./spec/kitchen/driver/rackspace_spec.rb.
Failure/Error: require "fog/rackspace"

NameError:
  wrong constant name CDN v2

I've opened an issue over here: fog/fog-rackspace#45, to see if we can get a version bump.

If we don't get anyone to come forward to help maintain fog, or a similar Rackspace gem I'm going to suggest we archive this repository, rather than fight the tide.

Allow data center / region selection

Allow the selection of a specific data center / region via driver_config.

Remove occurrences of "require_chef_omnibus: latest" in docs

See this

Better output during bootstrap

bootstrap waits with no output until the server is up, making it look like things are frozen for up to a few minutes.

Implement same 64-character hostname limit as in kitchen-openstack

Seen here.

64 characters can create a mismatch between hostname and the contents of /etc/hosts, resulting in:

# sudo echo hi
sudo: unable to resolve host default-ubuntu-1310-jhartman-jonathans-imac.rackspace.corp-cuyo

Fix Failing Style Checks

Methods exceeded maximum allowed ABC complexity (1):

  lib/kitchen/driver/rackspace.rb  Kitchen::Driver::Rackspace#create  17

Total Violations: 1

Yo, dawg, I heard you like Test Kitchen...

If we did a very simple run during builds, it would catch issues like #13.

Support boot from volume in kitchen-rackspace

Similar to this issue in knife-rackspace: chef-boneyard/knife-rackspace#91. We should also probably support boot from volume cloud server flavors. Putting in this issue so we don't forget :)