Keynotes and Panels
Barry Crist, CEO, Chef
Mindy Bomonti, Sr. Customer Marketing Manager, Chef
Corey Johnston, Manager of Cloud Engineering and IT, Edgenuity
In almost no period has there been so much forced innovation so quickly. People and businesses have had to adapt overnight to changes in everyday things we may take for granted. For many, this has been an impossible challenge, creating major business and customer impact. For others, they’ve been able to shift and adapt much more quickly to better serve their employees and customers. In this Keynote session, Chef CEO Barry Crist will look at how Chef and our customers are reacting to this unprecedented change, highlighting ways that industry leaders have evolved into Coded Enterprises, including a discussion of the technology and processes they provide their teams to be nimble, secure, and lean in an ever-changing business landscape.
Corey Scobie, Chef, CTO
Luis Madrigal, Engineering Manager, Client Platform Engineering + IOT, Uber
John Snow, Sr. Software Development Engineer, Chef
Since ChefConf 2019 we have been busy building, driving, and evolving massive innovation across our product portfolio. Our entire team has been working to make our products easier to use identifying how we can simplify the workstreams between DevOps and Security teams to improve compliance and overall security posture, and defining how IT managers can better manage fleets of desktops, laptops, and kiosks. This session with Chef CTO Corey Scobie will show off new products and features that will make your life easier every day and help you enable your business to become a Coded Enterprise.
benny Vasquez, Community Manager, Chef
Mandi Walls, Developer Advocate, Chef
Jason Field, DevOps Team Lead, Calastone
Marc Chamberland, Consultant, Mandate at National Banque of Canada
John Roesler, Lead Engineer, Target
Lance Albertson, Director, OSU Open Source Lab
The Chef Community has overcome some amazing obstacles in the last year, and is stronger for it. In this panel, we’ll hear from benny about Chef’s focus on community in the next year, talk to representatives from Chef’s community, and award this year’s Awesome Chef award.
Alayshia Knighten, Senior Professional Services Engineer, Chef
benny Vasquez, Community Manager, Chef
Jody Wolfborn, Developer Advocate, Chef
Brittany Woods, Automation Engineer, CARFAX
Krystianne Avedian, Chief Relationship Officer and GTM Lead, Capgemini
Stephanie Aurich, Senior Technical Program Manager, Amazon, Alexa Home
WomXn in the tech industry face a diverse set of challenges and rise up to meet them each day with strength and determination. Join us to engage with six womxn tech champions who conquered obstacles and adversity in their professional lives. These panelists will share empowering stories of strength, creativity, and rising to overcome challenges faced by many womxn in the workplace today, with Q&A opportunities offered for our attendees. Immediately following the panel, we invite our guests to switch on their webcams and stay for a mocktail hour to continue the conversation, just like we would in person!
Galen Emery, Lead Security & Compliance Architect, Chef
Annagreth Flierl, Customer Success Manager - EMEA, Chef
Keka Ichinose, Product Manager, Chef
Anthony Rees, Solutions Architect - APAC, Chef
Rachel Rice, Software Development Engineer, Chef
John Snow, Sr. Software Development Engineer, Chef
John Wyss, VP of Product, Chef
Compliance and security for organizations remains a complex and unsolved puzzle. Customers have told us that Chef’s automation stack has enabled them to take their first steps forward by scanning their fleet for issues and authoring remediation cookbooks for the most critical assets. The criticality of security and compliance work for IT leaders has been underscored by an endless parade of high profile breaches across every industry, which continue to rise in frequency and severity each year. Can we collect all the learnings from the Chef community and raise the bar on automation tools?
Customers have encouraged us to continue to innovate in this area by removing much of the delay and cost associated with content production, and enable them to take an enterprise-wide approach across even cloud and hybrid assets. What’s needed is a policy-driven framework for benchmarks with controls which are easily customized to company compliance posture, including the ability to manage waivers as needed, including full visibility of approvals.
With the new Chef Compliance product, Chef includes a spectrum of certified, Chef-tested and fully supported audit and remediation content which represents best practices for securing each type of end point.
In this marquee session, the Chef team will introduce Chef Compliance, moving forward automation-at-scale for the DevSecOps community. See for yourself a demo on how Chef Compliance Audit helps security and operations teams maintain complete visibility over compliance status. See also how Chef Compliance Remediation helps close the loop between audit and remediation to allow for continuous compliance in the enterprise. And you’ll hear some real world customer outcomes!
Virginia Nguyen, Product Operations Sr. Director, Chef
John McCrae, Software Development Engineer, Chef
Alan Baptista, Product Marketing Director, Chef
Nick Rycar, Senior Technical Product Marketing Manager, Chef
Stephen Wise, Customer Success Sr. Manager, Chef
Jeff Vogt, Sr. Field Solutions Architect, NA Sales, Chef
For over a decade, the Chef community has proven that “Infrastructure as Code” is the only scalable way to manage a large digital fleet without hiring armies of “click next” administrators. We at Chef are thrilled to innovate alongside you, extending the power of Chef beyond the data center to the perimeter of the enterprise. Turns out, desktops, kiosks and laptops can benefit from the same approach! We’ve also been managing literally everything inside Chef that way for years! Now, it’s time to turn that into a real product you can run with as well!
Introducing Chef Desktop, a new product organizations can use to eliminate the time-consuming, manual steps needed to configure, maintain, and trace any change events in their IT resource (Laptop/Desktop) fleet. This also gives organizations a dynamic way to enforce enterprise security and compliance, as well as zero touch process for enrollment and provisioning of new Mac and Windows devices.
In this Marquee session, the Chef team will walk you through how Chef Desktop allows IT resource managers the ability to automate the deployment, management, and secure maintenance of a single laptop or the entire fleet, all from a centralized location on a range of operating systems.
Robin Beck, Senior Developer Advocate, Chef
Mike Krasnow, Senior Product Manager, Chef
Scott Lappin, Director DevOps, Panera Bread
Matt Wrock, Principal Software Development Engineer, Chef
Whether you’re dealing with in-house developed applications or third-party applications – building, deploying and maintaining these applications tends to be a very complex orchestration. From application dependency encapsulation to integrations with pipelines to runtime management - not to forget inter-team dynamics and ‘throw-it-over-the-fence’ issues, there are myriad challenges you face. Throw in bare-metal, containers, VMs and multi-cloud strategies and you’ll soon start thinking that travel to Mars might be easier!
What if - through the power of automation - all of these complexities could be simplified by defining everything an application needs to be built, run and managed in development alongside the application. What if a single artifact could be packaged that could be delivered to any environment and validated in real-time? And what if all of this could integrate seamlessly with your existing pipeline and infrastructure?
That’s exactly what Chef’s application delivery offering does for you. Join us to learn how Chef is re-defining application delivery and hear from a customer managing distribution of applications to thousands of retail stores without dropping your order!
Sudhir Reddy, VP of Engineering, Chef
Josh O'Brien, Product Manager, Chef
Jody Wolfborn, Senior Developer Advocate, Chef
Tim Smith, Senior Software Development Engineer, Chef
Tyler Ball, Senior Software Development Engineer, Chef
Jeff Brimager, Engineering Consultant, Professional Services, Chef
Long time user of Chef and a pro at writing cookbooks? Does the sound of upgrading to the latest Chef Infra Client from previous versions make you wanna cry? Well - let’s turn those into tears of joy!
In this session, you will learn about how Chef engineers have been busy working on a new tool to help you modernize your fleet painlessly. Introducing Chef Workstation - Upgrade Lab, which helps Chef customers migrate to the latest version by providing a recommended upgrade path and a set of tools to scan, analyze, and upgrade via Workstation.
You will hear about how we went about building this for our customer Chefs, and some actual success stories within a complex customer environment. We’ll also touch on some of the enhancements in Chef 16 such as YAML support and converting to Ruby with Knife.
This is the tool you’ve been looking for to upgrade to the latest Chef toolset. Come join us to hear all about it!
Justin Rivait, Infrastructure Engineer, CUNA Mutual GroupWatch Session » Session Description »
The hardest part of integrating Chef Infra into an organization isn’t learning the technical aspect - it’s helping others to understand “The Why”, and to build a solid community of practitioners. Culinary students often learn the concept of “Mise en Place”, or “Everything in its Place”. From champions, to technical challenges - come learn from my organizations’ lessons that enabled us to scale Chef out, and the epics and features that would have helped us grow faster and become more successful earlier in our journey.
As organizations look to bring new tools in to increase the quality of their infrastructure and speed software delivery, it’s often engineers that identify what may be able to improve these processes. Generally what follows is a business case presented to leadership in order to secure funding, an initial purchase order, and then a discovery period for those engineers and their product or service owners on how to make the tool work well in their unique ecosystems. For many, it’s tempting to start automating and delivering right away - to just get something out there to show value. Often there is low hanging fruit that can be pointed to as a success story - but it’s the more complicated patterns that can slow adoption down. In order for real success to happen there must be a strong community and willingness to change the ways in which we work, as well as support from the bottom of the organization all the way to the business leaders that partner with IT. We can increase velocity and adoption of new tools and ideas by following the concept of “Mise en place”, or “Everything in its Place” by laying a solid foundation for Chef, or any other new tool or concept in our organizations to remove friction and make new ideas become successful realities.
Come learn how we developed a community of practitioners, built support for Chef, and laid the groundwork for Chef to not only survive, but to excel in our organization. In this talk we’ll share how to build a strong business case for Chef to garner support and build new champions. We’ll also cover some epics and features that we think are critical to the success of Chef in an organization. Finally, we’ll talk about some thoughts around removing friction from the development lifecycle for Chef Infra to make it easier to learn and use.
Dan-Joe Lopez, DevOps CoE Global Lead, SAPWatch Session » Session Description »
Having trouble picking a talk? Not sure where to start? Are you new to Chef, configuration management, or automation in general? Are you looking for a quick intro to get you started? This talk is for you!
The SAP DevOps Center of Excellence is a global enablement team, helping our developer teams to adopt the DevOps culture and practices. We act as a knowledgebase on topics, technologies and best practices surrounding automation, continuous integration, continuous delivery, micro architecture, etc.
We often work with the development teams to create custom solutions and pipelines, most of which include some chef management. As we work with new development teams, or add members to our own team, we have to quickly ramp up their knowledge of Chef Infra.
In this talk, we’ll share with you how we ramp up knowledge in SAP to get our colleagues working with Chef fast and efficiently. You can expect to learn:
- The basic concepts of declarative configuration management and how it differs from scripted automation.
- Important terms you’ll hear at ChefConf.
- The anatomy of a Chef cookbook.
- The process of a Chef client execution.
- How the Chef Infra Client and Server work together.
- Where to find resources to expand your knowledge and get your questions answered.
Steven O’Neill, JM Family, Cloud Engineer
Terry Arroyo, JM Family, Technical Architect
Are you part of an enterprise that has recently started your automation journey or one that is a few years in? Starting 5 years ago, JM Family started with Chef and it has been a key tool to bootstrap our automation capabilities. Join us as we talk about our journey so far, the thrill of automation and the agony of emergent problems, and what we think we want to build on in the future.
In this session, Terry Arroyo and Steven O’Neill will present the evolution of JM Family’s automation workflows for Chef, including: cookbook development, provisioning Chef Infra, and application deployment. We will then highlight what we think are our opportunities to improve as we move forward.
Matt Ray, Regional Manager, Customer Architect APJ, ChefWatch Session » Session Description »
HashiCorp’s Terraform is a popular open-source Infrastructure as Code tool that allows us to quickly provision and manage infrastructure across the cloud. There are a wide variety of complementary integrations between Chef Infra, Habitat, and InSpec with Terraform that enhance the ease of managing infrastructure, applications, and compliance. This talk will dive into what’s available and provide live demos of the Terraform integrations working together as we discuss how these complementary technologies achieve the goals of Infrastructure as Code.
Mark Gibbons, Senior Engineer II, NordstromWatch Session » Session Description »
Sometimes the knife command just isn’t what you want when interacting with the Chef server. Chef Manage is going away or gone. The Chef Infra Server API offers convenient access to the functions behind the knife commands. Web apps using the API can allow access to sensitive interfaces in a controlled manner.
Graham DavisonWatch Session » Session Description »
This talk will follow a five-year journey with Chef Infra. We will start with its introduction to an existing on-premise infrastructure and scaling as the environment grew. As we scaled, we extended some of the Chef command-line tools to ease deployment.
Next, we will explore the successful and less successful approaches to moving into a hybrid cloud infrastructure in AWS. We built AMIs using Packer and Chef Infra, but ended up with forked cookbook implementations for on-premise and cloud environments.
Finally, we will explore a cloud-centric deployment integrating AWS features with Chef Infra and Chef InSpec, and adopting Policyfiles.
Arthur Maltson, Distinguished Engineer, Capital OneWatch Session » Session Description »
Test Driven Development is a popular concept in Software Development, leading to higher quality code that’s easier to maintain. Automated testing is normally a foreign concept in the Operations/DevOps world, but as you ssh into your servers to make that quick fix or run your updated script (fingers crossed), you might be wondering if there’s a better way. A way that gives you the confidence in your script and lets you test those scripts in isolation. There is a better way! Test Driven Infrastructure (TDI) is now possible. I know, it sounds crazy.
At this session you’ll learn the how, and more importantly the why, of TDI. You’ll see how Chef can be tested with Test Kitchen and Chef InSpec. You’ll also learn how to improve your feedback cycle with Docker, and using the Docker approach on a CI server. There’s even a live demo!
Finally, the Ops world collides with the Dev world in true DevOps testing bliss.
Kyle Harper, Lead Engineering Manager, CernerWatch Session » Session Description »
Are you challenged to demonstrate security compliance with strict security controls? Are your systems unexpectedly failing security audits due to your inability to routinely assess your posture? By auditing compliance through agile software delivery, one can reduce the toil of demonstrating an aggressive security posture at scale. InSpec, a compliance as code tool, enables organizations to quickly and frequently produce compliance artifacts while providing a framework for iterative continuous improvement.
In this talk, we will share our journey and challenges encountered leveraging compliance as code to validate system compliance in a federal space. We will share first-hand experience and lessons learned with successfully meeting these challenges. Whether you are a software developer, security professional, or in operations, all can benefit from these concepts.
- Interpret Security Technical Implementation Guides (STIGs) into well-defined InSpec.
- Collaborate on InSpec controls to unite and articulate your organization’s desired security posture.
- Learn methods to inject more contextual information into your InSpec results.
- Prepare auditors for this new philosophical approach.
- Create orchestration pipelines to execute InSpec at mass scale.
- Learn techniques for converting InSpec results into auditor required specific formats.
Learn from the shared experiences of an engineering manager responsible for the creation of InSpec profiles leveraged to audit systems with stringent federal security requirements.
Lance Albertson, Director, OSU Open Source LabWatch Session » Session Description »
Multi-node testing with Kitchen has long been a requested feature, however it’s outside of the scope of Kitchen. Multi-node testing is useful for testing complex services such as replicated database servers, Ceph clusters and OpenStack to name a few.
Some examples of how this is useful:
- Test to ensure your replicated database servers can fail over properly
- Test an upgrade between versions of Ceph or Openstack where doing this in an “All-in-One” might have differences with multiple nodes interacting
- Ensure all components can communicate properly with firewalls
At the OSUOSL, we developed a method for doing this using a combination of Kitchen, Terraform, InSpec and OpenStack (however any public cloud supported by Terraform will also work).
This session will cover the following topics:
- Why this is important and the problem we’re trying to solve
- Discuss what tools we used
- How you can replicate this for your environment
- Recorded demo using a real-world example
Annie Hedgpeth, Senior Cloud Automation Engineer, 10th MagnitudeWatch Session » Session Description »
For those that have longed for a simpler test-driven approach to Terraform development, come and see how I’ve made my team’s lives easier by using Test Kitchen for Terraform and how I can validate my deployments with InSpec. This will be a beginner’s guide, but all skillsets are welcome to contribute to the conversation!
We’ll discuss the different use cases for Terraform testing, such as:
- Test Driven Development (TDD)
- Integration Testing and CI/CD
- Compliance, shifting security left
- Production provisioning validation
As we know, good testing doesn’t just solve CI/CD problems; it solves culture problems. I will seek to convince you of why you need to invest in a good Terraform testing strategy early and how you might have bought into a myth that makes you think you have velocity when you don’t (are you running in wet cement).
And if you’re late to the game and have existing infrastructure with no tests, that’s okay, too. Let’s talk about how you can reduce stress by adding in some testing now. It’s not too late.
It takes an IT village to do DevOps, so let’s talk about moving security and sanity left with InSpec and Terraform. So many use cases, and so little time. You’ll leave this talk ready to implement at least one of them.
Scott Lappin, Panera Bread
Michal Rysanek, Panera Bread
Greg Schofield, Indellient
Matt Wrock, Principal Software Development Engineer, Chef
Eric Calabretta, Lead Solutions Architect, Chef
Come see how we overcame unreliable networks, low bandwidth (T1), and near 24x7 operations to improve our speed and efficiency to thousands of cafes with tens of thousands of devices. Our cafés, while critical to our business, have numerous constraints you don’t find in a standard data center or the cloud.
Graham Weldon, Technical Coordinator and Vision Lead, Rakuten, IncWatch Session » Session Description »
Learning Habitat is easy. Learning how to take it to production can be tricky! Experience how to bridge that gap during Graham’s presentation about production Habitat services.
Learn about the difference between “getting started” Habitat demonstrations, and the efforts required to go to production during a deep dive into Habitat package architecture, deployment and orchestration with one of the primary Habitat core-plans developers!
David McMaster, Automation Engineer, NetDocumentsWatch Session » Session Description »
Chef Habitat can be intimidating to adopt as it is considerably different than its predecessor, Chef Infra. This talk will go over a few different partial implementations of Chef Habitat from binary management to full blown habitat environments.
In the first example I will go over is a very basic implementation habitat where you can use existing cookbooks without much modification. This will use zookeeper, Chef Infra, and Chef Habitat to illustrate my point. The binaries will be handled by habitat while service management is handled by the Linux OS and configuration management is handled by chef infrastructure.
Next I will go over a more mixed example based on the same concept. In this iteration the binaries and service management will be handled by Chef Habitat while the release versioning is done by Chef Infra.
Finally I will go over other features, like service discovery and health checks, that could be implemented in a mixed deployment. This should help show a stepwise implementation of Chef Habitat that could transition to a more idealized Chef Habitat deployment.
The intent will be to cover ways an organization can use Chef Habitat to solve application level issues. Hopefully to both get more comfortable with Chef Habitat and solve problems within some limitations for a given organization.
Yonathan Koren, DevOps Specialist, Indellient / ShuttleOpsWatch Session » Session Description »
This talk begins with an overview of Chef Effortless’ debut in 2019 and the historical challenges stemming from Chef Infra which Effortless attempts to solve. This talk will recount a first-hand experience of an organization’s movement away from Chef Server to Chef Effortless inside their own datacenter, and how the gradual retirement of the datacenter’s Chef Server was met with challenges in regards to Secrets Management and Configuration Management. We will delve into why these challenges were encountered - because the organization was reliant on Encrypted Data Bag Items and environment-based Cookbook workflows, both features which disappear when moving to the Habitat-driven Chef Effortless model - and how these challenges were overcome.
Sean Carolan, Senior Technology Specialist, HashiCorpWatch Session » Session Description »
One of the questions Chef users often ask is “How can I orchestrate Chef runs across multiple nodes, where node A depends on something that happens on node B?” The standard solution has been to store the data temporarily on the Chef server where the dependent nodes can reach it.
Instead of a kludgy workaround that passes state data between machines, what if you had an always on, always up-to-date service catalog showing the IP address, port and health of every service on your network. You can even store arbitrary data in Consul for Chef to consume during runs.
Take the hassle out of multi-node configuration management with Consul and Chef.
Chad Larkin, DevOps Solution Architect, Early WarningWatch Session » Session Description »
Early Warning is a fintech that partners with many of the country’s largest banks. Given the evolving customer needs across the financial services industry, there has been an increased expectation for Early Warning to rapidly launch new product lines. However, legacy processes meant that requests for new Development Environments typically took 1 to 2 months to complete, often impeding progress in achieving ambitious goals. Using the tools provided by Chef, Early Warning developed a solution. In just a week using Chef Infra, Habitat, some domain-specific scripting, and the company’s CI/CD pipeline, Early Warning was able to prefabricate a path for new development projects that reduced time to start, build, and deploy from the month-plus timeframe down to an hour, a 98% improvement.
Nell Shamrell-Harrington, MozillaWatch Session » Session Description »
We used to operate in a world of complicated technical systems - systems which, even if they were difficult to understand, were knowable. Over the past decade, however, we have transitioned from complicated systems to complex systems. A complex system and the way it integrates and interacts with other complex systems is not fully knowable by any one person, one company, or even one industry. The only way to operate within a world of complex systems is through cultivating a community of varying experiences, knowledge, and observations. Come to this talk to hear stories from technical communities - including the Rust Community, The Covid-19 Cyber Threat Intelligence League, and the U.S. Marine Corps Cyber Auxiliary - and how they work together to fulfill their missions not in spite of complex systems but through those systems. Learn how you can take lessons from these communities and apply them to your own.
Damith Karunaratne, CEO, ShuttleOpsWatch Session » Session Description »
The move towards digital transformation and faster software delivery has many DevOps teams contemplating the role of code, low-code and no-code solutions. The success of building and scaling application automation practices remains a challenge for most companies, due to complexity and a lack of access to skilled DevOps engineers. Growing economic pressures have many technology leaders evaluating how to incorporate innovative solutions that enable teams with limited experience, to orchestrate the end-to-end DevOps toolchain, while retaining the depth of functionality required to be successful. Join us as we demonstrate when and how to combine these strategies, so you can:
- Integrate the Coded Enterprise with a no-code platform
- Leverage existing Chef investments
- Scale and easily move applications to the cloud
Bakh Inamov, Security & Compliance Specialist, Google
Konrad Schieban, Infrastructure Cloud Consultant, Google
In this talk we’ll discuss the challenges and approaches for achieving a Secure by Default posture on a cloud provider. We’ll walk you through some of the work we’ve built to make this journey easier, including PCI blueprints for deployment of secure workloads and Chef InSpec profiles for verification and generation of a compliance score. Finally, we’ll show you how to wrap all the pieces together in a CI/CD build pipeline.
Brittany Woods, Automation Engineer, CARFAXWatch Session » Session Description »
As we have automated our processes, it has become more important than ever to maintain visibility into our systems. As part of that, harnessing the power of our data is on the forefront of all of our minds. Chef is a treasure trove of data. In contrast, ServiceNow acts as a pane of glass for incidents and events among your ecosystem. ServiceNow, in many cases, also houses change data and asset data about your ecosystem.
How can you marry the two? By integrating Chef with ServiceNow in different ways you can improve your visibility into your systems, improve ecosystem health, improve the accuracy of your asset data, and improve incident tracking and response. Join me as we discuss the many different ways you can integrate these two systems effectively to get the most out of your data, the benefit that will provide you, and why you would want to do this in the first place.
Chris Todd, Vice President of Engineering, TapHere!
Keith Walters, Director of Partner Solutions, TapHere!
Congratulations! You just landed a new opportunity, and architects have tasked you with building the next greatest platform on Kubernetes - and everything will be automated and deployed in containers. Now what? You need a team! Where are you going to find the experience to build this solution? Oh, and by the way - your team starts tomorrow.
Building and recruiting teams and training them for the often novel patterns inherent to DevSecOps has been a difficult perennial challenge, especially for larger enterprises with established or rigid staffing processes. DevOps has been well conversed and spread over the past decade, and a lot of core tenets and ideas are finally becoming mature. On the other hand, the technology that drives DevOps and delivering business outcomes continues to evolve at a fast pace. This doesn’t lend to the availability of large pools of seasoned experts readily available for these newer essential technologies and methodologies - hiring experts in things like Kubernetes and container orchestration is really challenging. This makes it hard to assemble a productive team on day 1.
As a developer lead or project manager, staffing for opportunities comes from three likely sources: The unicorn expert, existing developers and system administrators with varying degrees of experience in the required technologies, or entry level hires with the expectation of on-the-job training. Recruiting is hard, so when it comes to building new teams it’s important to invest in the right skills and talent. Each of these has their advantages and challenges:
- Unicorns are great at executing these complex systems, but they are extremely hard to find and often not ready to move/jump/leap when you need them.
- Experienced developers and system administrators bring valuable and crucial experience necessary completing your new projects. However, years of engagement and experience can sometimes make seasoned engineers reticent to make leaps of faith into new methodologies - and a focus on solving hard problems can give limited time for perspective-changing training, resulting in a longer and more expensive training ramp-up.
- Entry level engineers come to us fresh and moldable, but it’s up to us seasoned folk to give them the right tools, attitude and patterns - and to expose them to diverse and expandable perspectives.
In addition to recruiting and training experienced engineers in the field, fostering the skills of more junior engineers through the universal applicability of the concepts in Chef Effortless results in a shorter training tail and engineers with more portable and adaptable skills. We expose them to established patterns that reinforce from the start that infrastructure and apps are -all- code, and deployment is as much a part of the development lifecycle as feature implementation and testing.
In this talk we’ll share our experiences in how we use Chef’s Effortless Infrastructure as a reference implementation to teach and expose newer engineers the core patterns of DevOps to be able recognize when to apply those patterns and strengthen their ability to adapt when faced with problems they haven’t seen before.
Damith Karunaratne, CEO, ShuttleOpsWatch Session » Session Description »
ShuttleOps CEO Damith Karunaratne explains the top challenges of implementing automated application delivery, and how organizations can benefit from pairing Chef technologies with a no-code CI/CD platform like ShuttleOps for fast, simple and secure application delivery.
Waldo, TechEvangelist, DatadogWatch Session » Session Description »
Have you ever gotten into an argument because the statement that you made wasn’t understood as you meant it? Have you ever seen a simple disagreement go rapidly off the rails and turn into a shouting match?
Rather than quipping at one-another (like UDP), there is a technique for resolving disputes or conflicts that is more akin to TCP. It is called “Active Listening.” In this lightning talk, I’ll show you how this technique reduces the likelihood of a shouting match by drastically slowing the escalation and forcing each side to listen and comprehend what the other person is trying to say.
Pradeep Nair, DevOps Consulting Head, Relevance Lab
Pradeep Joshi, Director/Architect, DevOps, Relevance Lab
Relevance Lab talks about its DevOps Consulting services with and Chef work that we have executed over the years. We talk about our solution with ServiceNow and Chef integrated for automating a spectrum of ITSM/ITIL tasks and use cases:
- Resolving a typical ITSM incident like password reset
- Provisioning of infrastructure stacks on any cloud
- Feeding critical build and deployment information from Chef to the ServiceNow DevOps module to accelerate change management decisions.
Ran Ribenzaft, Co-founder and CTO, EpsagonWatch Session » Session Description »
The move from host-based monolithic applications to complex distributed ones comprised of microservices raises new challenges for Engineering, Devs, and Ops teams. Monitoring, troubleshooting, and eventually development, require a modern OOTB approach for observability. Being able to understand exactly what’s going on under the hood and avoiding alert fatigue are both crucial for daily work.
In this talk, we explain how gaining end-to-end observability within microservice-based environments with Epsagon’s automated solution helps you overcome these challenges, whether you’re running on containers, VMs, serverless, or else.
Tal Klein, CMO, RezilionWatch Session » Session Description »
What if we took a fresh approach to security that treated developers as intelligent human beings capable of making good decisions? The reality is that the lines between immutability and security and becoming more blurry every day. This quick talk explores an approach for using code, recipes and cookbooks to define security policies and ensure that what goes into production as well as what’s running in production achieves the developers’ desired state. We call it: Desired State Enforcement with Chef and Rezilion.