Coming soon! Chef is headed to Austin for #HugOps and #DevOps. Music by local artists, Otis and the Destroyer. Catch them live at ChefConf 2016.
At SAP NS2, our business is focused on delivering a full suite of applications, analytics, database, cybersecurity, and cloud software solutions. with specialized levels of security and support for our U.S. national security and critical infrastructure customers. We have the same needs for development velocity as many other organizations but we must operate under stringent compliance and security protocols that present barriers to collaboration and fast, small batch releases. Our presentation will examine how you can balance velocity and compliance in regulated environments, and will take what we’ve learned from working with the government and show you how to apply those lessons to a range of industries with their own security and compliance considerations. A few topics we will cover: -How do you apply DevOps to enterprise software? -Compliance and security at speed and scale -Continuous monitoring is continuous delivery -How do I ensure auditability of my infrastructure -Chef Delivery and its vital role with compliance -Chef provisioning and our ability to adapt to customer needs quickly and reliably. -Auto scaling powered by slapchop Attendees will learn how we: -Leveraged Chef to enforce compliance -Leveraged Delivery for Change Control -Enabled auditing powered by Chef data.
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.
Habitat is an open-source framework that gives modern application teams an application-centric automation platform. Build, deploy, and manage modern and legacy applications with Habitat.
In this talk we will explore:
Introduction to Habitat
The problems Habitat solves
Getting started with Habitat Plans
Using Habitat in your Chef workflow
John Kerry and Michael Hedgpeth worked within their large organization to use Chef to eliminate change-related outages for one of their most strategically important teams. Learn how they approached cultural differences within the organization, what PCI-related challenges they faced, and how they balanced their short-term and long-term objectives within the organization.
The journey of how Standard Bank implemented continuous delivery in a highly regulated industry using Chef, Chef Delivery and a host of other tools.
Cædman has been working closely with Chef to introduce continuous delivery into an enterprise ecosystem. The company is using Chef Delivery within an existing Chef infrastructure, and has many of the normal issues that people run into : workflow changes, high-security requirements, and resistance to change. This talk will cover the journey from a bare, mostly sort-of CI, shop running a single Jenkins master to a company that has services running on Chef Delivery, and being continuously delivered. We will cover "Barriers to Adoption", "Solving the Soft Problems", "Delivery Truck? Oh Fudge", "The Road to Deployment Is Paved with Good Intentions" and other topics. At the end of this talk, you will be able to navigate the minefield of moving an organization from a traditional set of models to a more complete continuous delivery model. not just from a theoretical standpoint, but by seeing examples of what went well and what went badly.
Habitat is an open-source framework that gives modern application teams an application-centric automation platform. Build, deploy, and manage modern and legacy applications with Habitat. Habitat plays well with many container technologies such as Docker, rkt, Mesosphere, and Kubernetes. This talk will explore some of the ways Habitat fits into the broader ecosystem.
Part of the "Welcome to Chef" track, this talk is intended for beginning Chef users. A year ago, I was new to Chef, so I came to ChefConf to learn. Now I'm sharing my current strategies, best practices, sketchy hacks and a blooper reel. I'll also lay out my current challenges and answer questions. There will be code, oh yes, there will be code. Topics discussed will include: - Embracing the suck: Why modern tech means always learning new stuff - How being wrong on github made me smarter - Chef-driven monitoring with iCinga, Nagios, and NRPE - How spider-web code can burn you, and how to stop it - Cookbook version control - Data, the "other" D-bag - Reduce, reuse and recycle your infra code - Literally, breaking literally every single server, recently. How I got there, how I fixed it - Useful tools or some hammers are better than others, but ya still gotta watch your fingers - The next steps.
The National Geospatial-Intelligence Agency has adopted open source software development and cloud computing as technology initiatives that are very important to furthering its strategic objectives. This represents a huge cultural shift from the way its software development is currently done. Part of this effort involves an adoption of DevOps and automated provisioning of infrastructure. MITRE participated in a pathfinder effort to migrate legacy applications to a cloud architecture provisioned by Chef. I'll discuss the challenges of regularly merging that open source code back into various closed, disconnected networks.
Writing cookbooks that can be easily consumed by varying users is a daunting task. How can you write robust cookbooks that cover all configuration scenarios without a level of complexity that would make users want to run and hide? Could it be that easy to consume and robust cookbooks are actually those that lack recipes and attributes altogether? This talk will compare and contrast monolithic cookbook design with that of composable cookbooks. The talk will show the pitfalls of a recipe / attribute driven monolithic cookbook through the lens of Chef?s own Tomcat cookbook. We?ll walk through the redesign and rewrite of the Tomcat cookbook to show how composable design and Chef 12.5+ Custom Resources can create robust and reusable cookbooks.
Have you integrated Chef with all the tools in your IT environment? Or putting it a different way… have you integrated your device managers, automated your firmware upgrades, and simplified the provisioning of your bare metal servers and storage with Chef? At Hewlett Packard Enterprise we have a wide array of different products; each with their own unique configurations. We were able to simplify and automate the use of our products by integrating them with Chef in the form of resources and drivers. In this session, we will be looking at how we were able to achieve this and how you too can integrate your tools with Chef!
SAP IT story into DevOps using Chef as our main automation tool in order to achieve large scale configuration management and policy enforcement on servers and user desktops, collaboration with development teams, providing automated CI processes.
Generating excitement and interest around a DevOps transformation can be difficult in any organization. When you are trying to do it across ten, the complexities are at an all-new level. One method to bring people together is to rally them behind a central cause and tool. We chose automation and Chef as that starting point. Like any complex and highly effective tool, Chef can only prove its value through training, proper use, collaboration and support. With these things, Chef is a powerful weapon for configuration management and consistency. Our approach focuses not only on how to wield the weapon, but how to do so with finesse. Pauly will speak to the cultural movement within Hearst, and how Chef is bringing teams together and removing reliance on the “caped hero”. Sharing a common goal, language and approach not only brings the team's closer, it makes accomplishing goals smoother. He will showcase the challenges and show how we overcame them so that the position of the team is now one of cultural and automation enablement rather than another step/bottleneck on the continuum. Aaron will share our journey from classic data center to the AWS cloud with multiple business units, including Fitch. He will discuss techniques used to mentor rather than just train people in the Chef approach. He’ll show how to overcome the challenges and roadblocks associated with migrating a complex application to the cloud using a tool like Chef, along with CloudFormation templates, and Chef deployment mechanisms.
There’s a lot going on in the cloud, much of it driven by open source, the community, and born in the cloud companies. Fueled by desire to be fast to market and to realize the economics of Cloud adoption, DevOps practices are becoming more and more commonplace across companies of all sizes to accommodate modern cloud application (microservices) needs. As these organizations invest in their people and processes to enable modern DevOps and look at the cloud to deliver business value, a thorough and innovative open source strategy has become a key factor in evaluating the platforms out there. Microsoft is building an open cloud in Azure, where more than 1 in 4 virtual machines run Linux. A wide array of partners like Chef are bringing DevOps practices to life in the cloud where we work with partners like Docker and Mesosphere to build solutions that help customers deliver real value in exploring industry trends, such as Azure Container Service. In this session, we’ll share why we are betting on open source in the cloud, how we enable, integrate, release and contribute to it and why it’s important for your DevOps practices, wherever you are in your journey.
A year ago I finished building a large distributed system to support an online game. We used a the most advanced tooling and patterns known at that time but we still didn't exactly get what we needed. [new paragraph] Habitat needed a similar large, distributed system of it's own: Builder. Builder is the first production application built with Habitat in mind.
I will explore the development process of Builder, lessons learned along the way, and show you how Habitat helped us build and deploy a scalable, distributed hosted service.
With infrastructure and application automation we have gained the tools to change systems in the blink of an eye. However, with increasing size, complexity, and time, these components will inevitably challenge your expectations. This uncertainty will ultimately slow you down. This talk will introduce the workflow to gain back trust. We will cover the foundation of effective infrastructure tests and failure domains for isolation. Moreover, we will look into the management of divergent environments, from legacy systems to modern clouds. This talk will combine Delivery, InSpec, and Test-Kitchen in intensely mixed deployments.
Chef is an amazing tool but to really unlock its potential you need to look at how it integrates with the rest of your technology. This presentation is the story of how the NFL used Chef to transform its siloed infrastructure and practices into something more agile, automated, and reliable. This presentation will talk about the last 2 years of Chef at the NFL, including how we integrated it with our virtualization infrastructure, load balancers, storage, and application performance monitoring. We'll talk about some things that Chef taught us about infrastructure as code that we were able to apply to other areas, and things we learned to make our cookbooks easier to manage across groups.
Want to get a handle on dependency support and safe promotion, what does that mean anyhow and how can they help? You've come to the right place. This talk will dive into the philosophy of dependencies, how to use 'em and a bit about how the sausage is made.
Chef Automate Demo presented by Seth Falcon and Oliver Ferrigni.
Rachel Trombetta, Director Service Operations, GE Digital
Veresh Sita, CIO, Alaska Airlines
Dawie Olivier, CIO, WestPac NZC and Justin Arbuckle, VP of Transformation, Chef
Learn about the Workflow feature of Chef Automate.
Deliver a continuous deployment pipeline for infrastructure and applications. Its full-stack approach, where infrastructure changes are delivered in tandem with application changes, means safe deployment at high velocity.
Learn about the visibility feature of Chef Automate.
Gain insight into operational, compliance, and workflow events. There is a query language available through the user interface and customizable dashboards. Insight into your network and development processes has never been easier.
Are you from a large and old IT organization? Do you support legacy applications that were lovingly built by hand in the distant past? Do you want to automate all of the things but feel it’s just not possible because you’re faced with a mountain of technical debt? Or do you think automation is too hard because you simply can’t rebuild your servers because you either don’t know how or because no one will give you new servers? Do you want to have nice things? It’s hard to know where to start a brownfield automation project and how to keep it going once it’s started. Adobe IT Web Platform Services had this problem and still has this problem. We used to build and deploy everything by hand. We had excessive configuration drift. We didn’t exactly know how to rebuild our servers. We would fat finger deployments and cause service outages. We had 19 different environments, all different, and all updates were pushed out by hand. We have a lot of technical debt. We’re better because we’ve tried to automate. We’re not yet completely automated. We don’t do CI or CD. We don’t even do automated tests. But we’re using Chef and our lives are better because of it. We’ve eliminated configuration drift. We’ve made rollout and rollback easier. And yes, we have nice things.
Whether you're a pointy-haired boss or just a technical individual looking to explain Chef and the DevOps movement to the people who hold the purse strings, this session is for you. We'll discuss DevOps, configuration management, and Chef in high-level business terms, and how such low-level topics directly correlate to business value. I want to arm you with the basics of selling your boss on something, not only as it relates to Chef, but to be used as a skill in general.
This session is a call to action for organizations to embrace Infrastructure as Code to achieve compliance and vulnerability remediation without slowing down the DevOps process. As an industry, we are now capturing most commercial and government compliance frameworks as standardized Chef cookbooks. This not only enables an organization to quickly roll out server compliance to meet various regulations (CIS, PCI, NIST) but also enables the rapid testing of server configurations. In this session I will demonstrate how Booz Allen has used Chef Compliance and Chef Delivery to enable quick response to remediating vulnerabilities, testing the compliance checks, and delivering those changes quickly. I will also present a call to action for our DevOps practitioners to embrace govready.org, open sourced compliance cookbooks and to participate in the compliance community to enable organizations of all sizes to take advantage of Infrastructure as Code and improve the compliance posture of the IT industry.
At Capital One, we want our cloud-enabled infrastructure to be an incubator for innovation and an accelerator for bringing more capabilities to our customers. We embraced the principles of Automation, Agile, DevOps, DevOpsSecurity, and Open Source with a robust automation framework to reach our goals. Chef combines innovation, speed, collaboration, and safety all into one DevOps platform. We introduced Chef to our DevOps engineers and quickly built a strong user community through sharing code and discussion forums like office hours and an internal Stack Exchange. Our Chefs didn't need to keep a personal knife because our Jenkins did all the work. We built a flexible Jenkins pipeline to deliver cookbook-enabled integration with automated application builds and provisioning. Implementing Chef Analytics provided more insight into the actions of the nodes and fed all of this data into Splunk for better visualization. A highly available Chef server and a private Supermarket provided our DevOps engineers with everything needed to manage their infrastructure and share their automation. This enabled fast and flexible IT as well as continuous delivery of applications and infrastructure. In this talk, we will share some details about our journey from sous chefs to master chefs. We hope you can leverage our experience on your own master chef journey.
Hosted Chef is one of the biggest Chef installations there is, with tens of thousands of organizations managing hundreds of thousands of Chef clients. By 2015, Hosted Chef had been growing exponentially for several years, and it was quickly outgrowing its home. It was time for a change, and so last October we migrated Hosted Chef from its original data center into AWS. As if the migration of a large production service wasn't enough, we were using an aging code base with practices and procedures that were years old, with references to CouchDB and workarounds from Chef 0.9! It was time to modernize all of our cookbooks, start using modern features, and generally rewrite everything at the same time. This talk is the story of that migration, the decisions we made, the challenges we faced, and the spectacular results. I'll cover what worked and what didn't go so well, and along the way I'll share some critical insights that will be useful to anyone running a large Chef installation in a cloud environment such as AWS.
Previously I've spoken extensively at ChefConf about the technical aspect of devops. How to implement the technologies, controls, tools, code, etc. But over the past few years people have asked more and more about the social aspect. How did we get countless teams across a large company to do this? How do you get buy-in? How do you sell it? How do you handle the teams who you don't think can cut it? What about the teams that are stuck in the past? How do you build or transform your team/teams/department/company? Getting one team to do it is easy - but it doesn't get you where you want to go. You have to get everyone in. That's what this talk will focus on: the soft-skills side of devops. AUDIENCE:From executive to developer to sysadmin... this is everyone's jobs and this aims to speaks to the broader audience.
In "Adding Windows to Your Kitchen", Trevor "The Chef Prince" Hess from 10th Magnitude and Levi Geinert from the Target DevOps Dojo will discuss common practices and challenges in the process of converging Windows. You’ll learn how you can use your existing Chef knowledge to build out integrations so your Windows machines can have the same level of testing/coverage as your Linux machines! Attendees will learn how 10th Magnitude and Target approached: -Kitchen Setup, Image Requirements, and Reboots -WinRM challenges (it's getting better!) -WSUS limits & Workarounds (Chef solo schedules task) -Using Rake tasks to manage multiple converges -Leverage DSC to make your life easier -Pester for testing -Tying into existing source control & CI tools -Utilizing add-ons like Jenkins, TeamCity, TFS, Git, NANO, containers, and more! In addition to the spoken presentation, "Adding Windows to Your Kitchen" will include a 5 minute episode of the "popular", (and completely made-up) renovation series: 127.0.0.1 Improvement (read as: Localhost Improvement) The video will introduce the higher-level concepts of the presentation in a similar way to last year’s "Chef Prince of Azure" music video. Think equal parts "Tool Time" from Home Improvement and This Old House.
This session provides a look into Chef Delivery and how the pipeline is used and adapted across development teams. The shape of your delivery pipeline is critical as it controls your DevOps workflow. In this session we will demonstrate how Booz Allen leverages Chef Delivery and our lessons learned in capturing, developing, and deploying software for a federal government agency that drove us to adopt Chef Delivery. We will also discuss various Microservices design and deployment strategies that can be applied using Chef Delivery which will provide the pros and cons serving as a reference point for your current and future efforts. This enables organizations to have multiple feature teams working on different aspects of applications while ensuring confidence that changes deployed are controlled, tested, compliant, and expected.
Windows management is all about taking advantage of the rich API surface that features and products have to offer. This API surface includes cmdlets, WMI, etc. PowerShell is the platform of choice on Windows that binds together these various API surfaces and brings out the best management experience. Therefore it is a natural and obvious choice to expose declarative configuration in Windows using PowerShell Desired State Configuration. DSC is a platform that allows any management solution to consume its artifacts and Chef on Windows provides an awesome integration. Chef can consume any DSC resource and the resources get executed in the context of the DSC agent process providing the best possible use of the API surface as well as desired performance characteristics. In this session, you will learn about writing DSC resources and how to consume them using Chef for Windows
The cloud players get it (often with custom automation by a huge development team), and the people that do everything on AWS don't care. But what about the rest of us who manage real networks everyday? What does DevOps mean to us? Is it just the latest fad? Where do I start? Come see why there's never been a better time to start taking advantage of DevOps practices and tooling to make it easier to run your network.
So you have Chef Delivery, now what? This talk is a practical introduction to build cookbooks and how to figure out what should run in each stage. Have you ever found yourself wondering: "What is a build cookbook?" "Where should I put performance tests?" "How does this work with Docker?" If you have, this talk is for you. Come join us as we plan out a few projects in Delivery. We will start by using the Service Delivery Canvas, a tool for thinking about where things go in the pipeline, to layout our project. From there, we will take what we learned from the canvas and walk through building out a few applications, including examples from Chef's own infrastructure. We will also demonstrate multiple language runtimes and methodologies. Come be part of delivering all the things!
Corey Sanders, Director of Program Management, Microsoft Azure, and Ken Cheney, VP Business Development, Chef
Mark Kirby, SVP & CTO of Information Technology, Liberty Mutual Insurance Group, with Nathen Harvey, VP Community Development, Chef
Nicholas Weaver, Director, SDI, Intel and Ken Cheney, VP of Business Development, Chef
Brandon Jung, Head of Americas, Cloud Partner Business, Google and Ken Cheney, VP of Business Development, Chef
Mark Kirby, SVP & CTO of Information Technology, Liberty Mutual Insurance Group
Looking for some ways to spice up your Chef usage on AWS? In this session we'll show you how to leverage services like AWS Lambda, AWS Key Management Service (KMS), Amazon CloudWatch Events, and Amazon EC2 Run Command with Chef. We'll introduce the AWS services and demo how they can be used to better manage your Chef nodes. Gannett, a leading media company and publisher of USA Today, will also join us to talk about how they build, test, and deliver over 400 cookbooks on AWS. They'll talk tools and process for building AMI's and managing 1,000 Jenkins jobs to continuously deliver their Chef environment.
Learn how customers are using chef and chef delivery to run, deploy, and manage workloads across Google Cloud on PaaS, IaaS and container environments.