Chef, Puppet, and other tools that implement “infrastructure as code” are great for configuration management and automated deployments, but it is difficult to test these infrastructure scripts before putting them into production. Since infrastructure as code is a relatively new technology, methodologies for its testing are not yet standardized. Glen Buckholz shares a way to solve the two major problems with testing Chef scripts—[1] capturing a start state similar to your target environment, and [2] rolling back to the starting state when your script fails. Development techniques are typically ad-hoc with most developers creating a personal method of testing in their own environment or circumstance. Glen shows how to use established continuous integration (CI) techniques to allow an automated platform to more quickly generate test results and automatically stage the code to the Chef server. By linking together established CI and testing techniques, we can hold Chef code development to the same mature standard as application programming.
Continuous Integration Testing Techniques to Improve Chef Cookbook Quality
1. W11
DevOps
&
Testing
5/4/16
13:45
Continuous
Integration
Testing
Techniques
to
Improve
Chef
Cookbook
Quality
Presented
by:
Glenn
Buckholz
Coveros,
Inc.
Brought
to
you
by:
350
Corporate
Way,
Suite
400,
Orange
Park,
FL
32073
888-268-8770 904-278-0524 info@techwell.com http://www.stareast.techwell.com/
2. Glenn
Buckholz
Coveros,
Inc.
With
fifteen
years
of
industry
experience,
Glenn
Buckholz
leads
continuous
integration
and
deployment
automation
efforts
at
Coveros.
His
career
began
as
a
consultant
implementing
automated
test
frameworks
and
introducing
the
concept
of
change
management
to
many,
many
projects.
Glenn
then
decided
to
become
a
part
of
honest
society
and
settled
down
at
the
Public
Company
Accounting
Oversight
Board
as
their
full8 time
enterprise
change
manager.
Several
years
later,
he
joined
Coveros,
where
he
specializes
in
implementing
agile
practices
and
CI,
and
engineering
configuration
management
instead
of
simply
documenting
it.