Seth Vargo

Re-thinking secrets with Vault

As organizations adopt cloud technologies, traditional security practices must adapt. When you can't wrap the cloud in a firewall, how do you secure data, communication, and credentials on inherently untrusted infrastructure. This talk highlights the challenges of security in the cloud, using an open source tool - HashiCorp Vault. What if your secrets could be as dynamic, elastic, and ephemeral as the cloud? With Vault, they can.


Tom McLaughlin

Operations in a serverless world

With the rise of serverless architecture, many of the common day-to-day operations tasks will change dramatically, if not disappear completely. We as Operations professionals will be challenged to redefine our roles and responsibilities within the technology organization as serverless abstracts away the server and its respective OS to cloud service providers. No stranger to this scenario, we will not only be tasked with solving these engineering obstacles introduced by the new serverless paradigm, but we will also need to prove our value to the business in the face of a changing technology landscape… again.

The time is now to start defining what Operations will look like in a serverless world. As a community that has reinvented ourselves time and again, we have another chance to shape the vision of new digital world.

In this talk, I will walk through the current state of serverless architecture, and discuss the many possibilities of how serverless may evolve so that we as an Operations community can not only begin preparing for the change, but lead this revolution again.

A few areas I'll discuss include:

  • Team structures and how to redefine your purpose
  • How to demonstrate your value to the business
  • Serverless architectural decision making
  • Performance management and cost containment
  • Failure monitoring and service handling

If you're an Operations engineer and you had all your host and OS related work removed from you, would you know what to do to stay busy and demonstrate your value to your organization?


Matty Jones

Ansible and Pagerduty, the Good, the Bad, the Oh Dear Lord Why

How do you manually manage 100+ people, over a dozen teams, and who knows how many services and escalation policies in Pagerduty? Certainly not by hand, you need to automate that. The problem is that not many people have done it yet, or at least done it and open sourced the code.

My team inherited this type of a Pagerduty configuration with the mandate to make is stable with the ability to fork-lift it into another account if needed. This means we needed to automate only the Pagerduty users and other entities we were responsible for but leave everything else alone. Simple, right?

Ansible was the tool chosen for this but no capability existed yet to manage Pagerduty in this way so I set about writing a series of modules to do this. The lessons I learned and problems I had to solve in order to do this properly tell quite a story of how to scope a project effectively, how to handle management that wants a push button solution, how to write something for the community and your company that won't get you laughed at by the everyone, and most importantly...whitespace...lots and lots of whitespace.


Lisa Hagemann

Infrastructure As Code: What is it good for?

We hear about Infrastructure as Code all the time. We've been hearing about it nearly since the advent of configuration management. As the tooling around automating your infrastructure deployments gain popularity, are we hitting some of the same problems we saw with configuration management? We have this one tool, so is everything a nail?

In this talk I will discuss the difference between Configuration Management and Infrastructure as Code; What advantages you have with Infrastructure as code and when perhaps Infrastructure as Code won't work for you. We will discuss and maybe debate(?) what constitutes Infrastructure, and how you want to manage these maybe not so obvious bits of your infrastructure.


Anubhav Mishra

Taming Terraform workflow using Terraform Modules and Github for change management

Today's cloud infrastructure is really complex. What if you could truly make this infrastructure a black box? What if you could mutate infrastructure safely and easily? See how to use Terraform efficiently across hundreds of developers while leveraging a simple Github workflow and Terraform modules.

Hootsuite was one of the early adopters of Terraform and faced some challenges early on with Terraform workflow.

  • This session will cover how Hootsuite uses Terraform modules and leverages them to bridge the gap between devs and operations.
  • We will discuss how we came up with our own state management system that helps us safely mutate the state of our infrastructure from one state to the other. How you can organize your Terraform states across multiple tiers of your infrastructure. We will also talk about our own HTTP remote state store on top of S3 that enables us to edit states and rollback.
  • Most importantly, we came up with our own Terraform workflow that uses github pull requests to do approvals and state locking so we don't corrupt Terraform states for our infrastructure.

For the demo portion of the session we will take an example of a real infrastructure deployment and see the lifecycle through the Terraform workflow using Atlantis, Hootsuite's Terraform workflow tool. This demo will showcase:

  • Use of Terraform modules
  • Use of multiple remote state dependencies
  • Github workflow for approvals
  • Environment locking using Atlantis

Atlantis Github Repo: https://github.com/hootsuite/atlantis


PJ Hagerty

Urban Legends: What You Code Makes You Who You Are

If you were a carpenter, would your skills at building be more important than the tools you use to build? Skills, right? Tools are just a means to an end. So why do developers think the language they use defines the problems they solve?

This talk will take a look at misconceptions across the board, some experiences, both positive and negative, people have had crossing barriers to new languages, and show some of the benefits thinking of one's self as a coder and not a "Ruby coder" or a "PHP dev" can have on being a better problem solver.


Jay McCarthy

Lessons in Software Reliability from the Graybeards

There are some domains of software engineering where errors are completely unacceptable, such as aviation, medical, nuclear control, etc. Since late 1960s, these domains have developed tools and expertise for ensuring the correctness of their software. In this talk, I will briefly discuss a variety of techniques and given an introduction how they can be applied in your development and deployment to increase reliability. In particular, I will discuss type safety, software contracts, model checking, fuzz testing, and formal verification. In each case, I will define the practice and demonstrate it in the Web domain.


Douglas Hubler

IETF standards are your friend

Building and managing infrastructure is hard and only going to get harder with microservices. Tools help but won't be enough. Luckily the IETF has a solution with a series of standards that are already proving effective. Learn about these standards and how you can use them.


Questions?!?


Need to submit a presentation? Want to sponsor? Reach out!