We’ll talk about the fundamentals of automation, what we’ve learned over multiple generations of tooling and research, and discuss the path forward.
So you want to start a DevOps revolution. Great...where do you start? Going from manual deployments to a fully automated delivery pipeline has brought many changes; both technical and cultural. In this talk, we will cover "the five phases of DevOps" we found on our journey at Gogo. Finally, we will wrap up the talk with how you too can start your own DevOps revolution! We will talk about our successes and challenges implementing various tools and driving large cultural changes.
Serverless is the next step after containers. DevOps will not go away, but it will certainly change. Getting ahead of the curve is important for a DevOps practitioner so that they can make sure the transition goes smoothly when their organization changes.
I’ll cover where my company ran into trouble when going serverless and how we solved all the new problems that come with managing a bunch of small functions instead of larger programs. I’ll also cover specifics of how our company manages an almost completely serverless environment, including the open source tools that we use and publish.
Many of us feel nervous or fearful about fully engaging with our teams, lest we be "found out" as an imposter who doesn't belong there. Imposter Syndrome is not silly, trivial, or something you’ll “just grow out of”. Many people have been experiencing Imposter Syndrome since childhood. But when does this anxiety become unhealthy? Is Imposter syndrome something we really even NEED to cure? As a fellow imposter, I’d like to share some of my own adventures in embracing my fears, learning to trust myself, and getting comfortable with asking for help.
DevOps has a well-established relationship with animals, particularly cattle and pets. Many attempts to "cattlle-ize" existing systems stall halfway, leading to somewhat different outcomes and leaving operations teams wondering what happened. This talk will focus on some common hurdles encountered when to moving towards the servers as cattle model and discuss some ways to identify and address them.
I probably am doing DevOps without even knowing it. When I discovered the DevOps Dictionary definition of "goat" I fell in love. My perspective on DevOps as a self-taught woman in technology and what the DevOps community could be more inclusive and accessible to me and other people I know.
What can the world of Roleplaying Games teach us about our organizational journey towards DevOps?
We talk about redundancy and security when it comes to our infrastructure and applications, but we rarely think about creating those same things in our teams and ourselves.
From the start-up financial roller coaster to a teammate's marriage (or divorce) to our own personal issues, success, scaling, and our future depend on complex and often chaotic factors.
In order to succeed, we need to create resilience, not just in our technology, but also in our organizations, our teams, and ourselves.
All aspects of DevOps are difficult; acknowledging, implementing, hell even defining. But do you know whats even harder then DevOps? People. Finding, recruiting and retaining.
We’ve seen great strides in the DevOps community in terms of changing the way engineering teams think about process and procedures, but why stop there? Why not use DevOps principles in another aspect of technology that seems to be broken; recruitment.
In Spring of 2016 Braintree decided to rebuild its CI system. At braintree we chose docker to power the CI system. In this talk I will discuss things we learnt with the Docker ecosystem (Docker, Docker-Compose and Docker-Registry).
The point of infrastructure as code is to make managing infrastructure as simple as updating a config file and running a command such as “chef-client” or “terraform apply.” However, as code changes and becomes unruly or tangled, it is time to apply a new development practice - refactoring. Refactoring infrastructure code presents unique challenges - particularly when live, in production infrastructure is involved. This talk will show you how to know when it is time to refactor your infrastructure code and to do it with the least risk possible.
I want to talk about the experience I've been a part of, bringing a large Enterprise company to using AWS for mission critical applications. This required collaboration across Development, Operations, Networking, Legal, Security, Audit, Risk, and Executive Management. Cross-team representatives worked together over several months, developed a written business case, and won executive backing to use AWS for mission critical services, including NPI data. I'll be sharing lessons learned along the way.
Submitting proposals and speaking at conferences can be very stressful, especially as an introvert. This talk will cover tips I have found to help make presenting more pleasant and why it's important to give talks despite being nervous about giving talks.
Do you wake up in a cold sweat when you think about what would happen if one of your devops people were to suddenly vanish, or win the lottery? Could you carry on? Can anyone on your team take vacations to cell-phone dead spots?
Devops is such a dynamic and flexible part of an organization that it is the absolute hardest thing to get documented, and the place where it really makes a difference to burnout if you have managed the miracle.
Where do we start? This is by far the question I’m asked the most when talking to people about implementing continuous delivery. Unlike other types of long journeys, the answer is rarely “at the beginning”.
One of the best ways to determine the best place to start is to figure out where you’re wasting the most resources, and one of the best ways to do that is to create a value stream map.
We’ll go over what a value stream map is, how you can create one, and how it can help you answer some important questions about your business. Questions like “where do we start?”.
’ve been part of growing Puppet from 35 to 450+ people over the last five years. I’ve spent many hundreds of hours on the hiring process - but really want to dig into the interview. I’ll highlight the 10,000 hour rule from Anders Ericsson (made famous by M Gladwell) on experience and measurement of success by tying that in with deliberate practice/continuous improvement when it comes to interviewing. I’ll share some science, some practices (such as my 6 question interview) and some humor to hopefully shift your thoughts interviewing and hiring - all in 5 minutes.
An ignite full of one-liner jokes and fun "facts" about DevOps inspired by the SNL segments of yesteryear.
Have you ever wondered is there's really some truth behind those stories of Bad Operators from Hell and Stifling Security Engineers? Jamesha Fisher, both seasoned in security and operations, hopes to detangle false notions, and uplift the generalized perspective of security and operations, bringing pride, as well as their importance to the DevOps movement.