Your current filters are…
How to build a continues delivery pipeline including complete test of configuration management code. I will describe how we use Jenkins to compile, create artifacts, test and verify for all our code including configuration management code. The pipeline build consist of 10 different steps that includes compilation, lint tools, Chef cookbooks test, integration test of cookbooks and application, full deployment on existing infrastructure and full the final step that is a full deployment from scratch. The pipeline is built on Jenkins, AWS, Chef, Test kitchen, lxc, Foodcritic, maven and rake. I will also show how we use feature toggling and avoid branching in application and configuration management code to be able to always have builds that are ready for deployment
by Zac Stevens
"Don't use SSH in a `for` loop!" We know we should be better than that, yet many Chef shops still rely on SSH to orchestrate their environments.
Are you using "knife ssh", but aren't happy with the security profile?
Are you using chef-solo, but wish you could use "knife ssh"?
Are you trying to invoke Chef from your other applications, and integrating with SSH feels wrong?
Solve these problems and more with MCollective, a CM-agnostic orchestration framework built on Ruby and message queues. This session shows how to deploy MCollective with Chef, integrate the two systems in various ways, use it as an ad-hoc tool, build multi-node orchestration workflows, and invoke Chef from other applications.
This session will introduce some new work. While it will include some demonstrations, this session is not a tutorial - it examines the capabilities and limitations of this approach to building orchestration, and hopes to provoke further discussion and development.
by Michael Ducy
Sometimes you need action to happen right away, and you just need to be a bit more pushy about it. This talk till cover the features of Chef's Pushy server and how it can be used to run ad-hoc commands or orchestrate action between multiple machines. We will also cover the architecture of Pushy and give an overview of how it works internally.
When we talk about configuration management and automation, we're often talking about automating Linux or UNIX platforms. Less frequently mentioned is how to automate Windows, an operating system that is widely used, but can often be a challenge to automate.
In this talk, I'll review some approaches to doing configuration management on Windows using out-of-the-box declarative Chef resources. I'll also discuss how Chef on Windows compares/relates to Microsoft System Center Configuration Manager (SCCM), Powershell, and some of the exciting new features in Windows 2012R2 a/k/a Desired State Configuration (DSC).
In this talk I will show a live demo covering the status of Foreman and Chef integration and try to answer the question "where do we want to go?" Also I will sum up what's needed to add similar support for config management tools of your choice.
The demo will include inventory management (ohai attributes upload), reporting (chef-client result upload) and whatever else we have time for.
A great thing about the Chef community is the wide assortment of various cookbooks to configure and manage servers. Often there is more than one cookbook available to manage the same software. How do you know whether a cookbook is any good? If youre automating something for the first time, how do you write a 'good' cookbook?
In this talk, I'll give my thoughts on cookbook style, focusing less on details ("should I use symbols or strings?") and more on general practices for what a good cookbook looks like. We'll take a quick tour through varied topics such as recipe size and structure, levels of abstraction and when they're appropriate, namespacing, unit testing (when and where), and more.
Foodcritic is a lint tool for your Chef cookbooks that you can use to find common problems.
In this talk I will show how you can extend Foodcritic with custom rules that you write yourself. We'll look at how Foodcritic actually works, the api available to write rules with and how you can test that your rules work properly.
You are already using Chef, but you want to implement Continuous Delivery and you're not sure where to start? Well then this talk is for you! We'll cover general workflow considerations when starting to tackle the problem of implementing Continuous Delivery. We'll use a Git and Jenkins specific development workflow as a use case for understanding how to turn that high-level view of considerations into a working pipeline. We'll look at Chef specific constructs that are especially helpful and give you a couple of helpful tools when building your own pipelines using Chef.
3rd–4th February 2014