ChefConf is the largest community gatheing and educational event for teams on the journey to becoming fast, efficient, and innovative software-driven organizations. In other words, you and your team!
ChefConf 2018 will take place May 22-25 in Chicago, Illinois and we want you to present! The ChefConf call for presentations (CFP) is now open.
A number of tracks have been announced for the conference and we will be describing those tracks in a bit more detail with posts similar to this one. Use these posts for inspiration as you develop a presentation to submit to the CFP or as a preview of what you can expect as an attendee of the conference in May.
Infrastructure automation is the process by which we automate the provisioning, installation, configuration, and ongoing maintenance of computers within our environment. The ideas, processes, and tools used to manage infrastructure as code are great topics for ChefConf.
One of the first steps to automating an environment is getting a handle on the current state of that environment. Simply running the chef-client on a machine that reports data to Chef Automate is a great first step in that process. Ohai, the system profiler, gathers thousands of system attributes, the chef-client sends this data off to Chef Automate. This data is organized and exposed so that queries can be executed to help answer questions about the environment. Questions like “what versions of which operating systems are running?”, “how many CPUs do a group of servers have?”, etc.
Managing infrastructure as code allows us to model the desired state of our infrastructure. Chef accomplishes this through things like resources, recipes, cookbooks, roles, and policyfiles. The extensibility of Chef allows for the creation of custom resources to help make the model more clear and easier to reason about. Cookbooks and other policy artifacts can be jointly developed by a team of engineers and can also be shared both within a company and across the entire community.
Building in and migrating to the cloud is fundamentally different than deploying to a data center. Chef and other tools allow you to automate this process. Being in the cloud changes the economics and approaches to things like disaster recovery, scaling up and down, and geolocation of running services.
The Chef ecosystem is full of tools that make it easy to take a test-driven approach to developing infrastructure code. Development begins on the developer’s workstation or laptop. Developers can validate their code locally using tools including cookstyle, Foodcritic, ChefSpec, Test Kitchen, InSpec, and more. Getting everyone on the team using a similar set-up and development process is important.
Everyone was new to Infrastructure Automation at one point. You do not need to be an expert to help others get started. A lot of experiences from the early days of automation are worth sharing, even if as cautionary tales. ChefConf is a great place to help fellow community members get started on the right foot.
The ChefConf CFP is open for the following tracks:
Your story and experiences are worth sharing with the community. Help others learn and further your own knowledge through sharing. The ChefConf CFP is open now. Use some of the questions posed here to help form a talk proposal for the infrastructure automation track.
Submit your talk proposal now! The deadline is Wednesday, January 10, 2018 at 11:59 PM Pacific time.