We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Don't Mind the Gap: How to Deploy Chef in Offline or "Airgapped" Network

Formal Metadata

Title
Don't Mind the Gap: How to Deploy Chef in Offline or "Airgapped" Network
Title of Series
Number of Parts
50
Author
License
CC Attribution - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
In high security environments, we are often behind proxies, firewalls or obnoxious corporate policies that disallow access to Github or RubyGems. What gives?! In this session, I will show exactly what it takes to set up your Chef environment in the offline world. I'll demonstrate how to download Chef packages, how to stand up the various Chef servers (Delivery, Insights, Compliance, Chef, Supermarket) and, most importantly, how to bootstrap systems in a way that they won't talk to the Internet. Topics will include (but not limited to): Gem, Artifact and Yum repositories; Chef package management; Provisioning/bootstrapping new systems; and Test-Kitchen. While this could all be done manually, that takes a lot of effort and isn't repeatable. So I'll be using Chef and other open source tools to accomplish this. All code will be open-sourced.