Skip to content

Commit 5f28de7

Browse files
Adding initial program for MSP 2019
1 parent e2b9a4f commit 5f28de7

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

48 files changed

+582
-14
lines changed

Diff for: content/events/2019-minneapolis/program.md

+13
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
+++
2+
Title = "Program for devopsdays Minneapolis 2019"
3+
Type = "program"
4+
Description = "Program for devopsdays Minneapolis 2019"
5+
+++
6+
7+
<div class = "row">
8+
<div class = "col">
9+
<hr />
10+
If Open Space is new to you, you may be interested in <a href="/pages/open-space-format">more details about Open Space</a>.
11+
<hr />
12+
</div>
13+
</div>
+12
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
+++
2+
Talk_date = ""
3+
Talk_start_time = ""
4+
Talk_end_time = ""
5+
Title = "The Container Operator’s Manual (Closing Keynote)"
6+
Type = "talk"
7+
Speakers = ["alice-goldfuss"]
8+
+++
9+
10+
Containers have been the future for five years now, featured on the stage of every major distributed systems conference in the world. But beyond the hype and the swag is a real technical solution, with real technical challenges, used for real problems at scale. And for the companies and engineers looking to adopt this solution, there’s little content on what awaits them.
11+
12+
In this talk, we’ll discuss some of the advantages and disadvantages of running containers, in production, at scale. We’ll address why to use containers, why not to, and the tradeoffs required at both the technical and human levels for implementing them. You will walk away with a better understanding of how containers could fit into your own architecture and what you’ll need to do to make that rollout a reality. Containers can be a great infrastructure solution, but no one should drive them without a manual.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
+++
2+
Talk_date = ""
3+
Talk_start_time = ""
4+
Talk_end_time = ""
5+
Title = "Blameless Postmortems: How to Actually Do Them"
6+
Type = "talk"
7+
Speakers = ["lilia-gutnik", "matty-stratton"]
8+
+++
9+
10+
So you’ve had an incident. Restoring service is just the first step; your team should also be prepared to learn from incidents and outages. In this workshop, you will learn some best practices around postmortems/incident reviews to help your team and organization see incidents as a learning opportunity and not just a disruption in service.
11+
12+
In this workshop, attendees will:
13+
14+
* Get an overview of blameless postmortems
15+
* Learn techniques for effective information sharing
16+
* Learn how to run a postmortem meeting effectively
17+
* Understand the difference between “blame” and “accountability”
18+
* Step through a real-world postmortem that occurred at a major SaaS organization
19+
20+
*Prerequisites:*
21+
22+
Come ready to interact! No computer needed.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
+++
2+
Talk_date = ""
3+
Talk_start_time = ""
4+
Talk_end_time = ""
5+
Title = "Chaos Engineering 101"
6+
Type = "talk"
7+
Speakers = ["ana-medina", "rich-burroughs"]
8+
+++
9+
10+
Chaos engineering is the facilitation of controlled experiments to uncover systemic weaknesses.
11+
12+
Ana Medina and Rich Burroughs lead a hands-on tutorial on chaos engineering, covering the tools and practices you need to implement chaos engineering in your organization. Even if you’re already using chaos engineering, you’ll learn to identify new ways to use chaos engineering within your engineering organization and discover how other companies are using chaos engineering—and the positive results they have had using chaos to create reliable distributed systems.
13+
14+
*Prerequisites:*
15+
16+
- A laptop with the ability to SSH into a remote server. (You'll be provided with cloud infrastructure.)
17+

Diff for: content/events/2019-minneapolis/program/cnab.md

+22
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
+++
2+
Talk_date = ""
3+
Talk_start_time = ""
4+
Talk_end_time = ""
5+
Title = "Pack your bags: Build Cloud Native Application Bundles"
6+
Type = "talk"
7+
Speakers = ["carolyn-van-slyck", "jeremy-rickard"]
8+
+++
9+
10+
When we deploy to the cloud, most of us aren't dealing with just a single cloud provider or even deployment tool. It seems like even the simplest of deployments today needs a load balancer, SSL certificates, persistent file storage, DNS... and somewhere in there is your application.
11+
12+
That is a lot to figure out! The Cloud Native Application Bundles specification was created to help address that problem, helping you manage everything in a single package and focus on what you know best: your application. [Porter](https://porter.sh) is a tool that delivers an easy to use, declarative approach to packaging your application using existing technologies. Porter helps you build bundles without needing to be a CNAB expert.
13+
14+
In this workshop, learn how Porter makes it easier to manage cloud native applications in the messy imperfect hybrid cloud world that we live in. We will use Docker, Terraform, and Kubernetes to build a bundle and deploy a bundle with Porter.
15+
16+
*Prerequisites:*
17+
18+
Attendees should bring a laptop with Docker installed. We'll provide Github repos for the workshop material.
19+
20+
*Takeaways:*
21+
22+
The audience will come away with familiarity of the core aspects of the CNAB specification, when CNAB should be used and how to use Porter to author bundles for their own applications. They'll also become aware of other tooling in the CNAB eco-system.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
+++
2+
Talk_date = ""
3+
Talk_start_time = ""
4+
Talk_end_time = ""
5+
Title = "Container Security"
6+
Type = "talk"
7+
Speakers = ["michael-ducy"]
8+
+++
9+
10+
In this workshop we'll cover how to implement runtime security for containerized environments using the open source project [Falco](https://falco.org). We'll cover the following:
11+
12+
* Learn how to create rules for an application. We'll take a containerized application and create Falco rules to detect abnormal behavior in the application. We'll profile an application's system calls, then use the profile to create application specific rules.
13+
14+
* Learn how to alert on Kubernetes audit events like deployment creation, kubectl exec, privileged container creation, and other interactions with the Kubernetes API.
15+
16+
* Learn how to leverage Serverless frameworks to react to security incidents. Delete offending pods, prevent nodes from being scheduled, and alert to Slack.
17+
18+
19+
*Prerequisites:*
20+
21+
* Comfort using a command line and a text editor
22+
* Familiarity with Docker & Linux
23+
* A laptop with a web browser and SSH client installed
+14
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
+++
2+
Talk_date = ""
3+
Talk_start_time = ""
4+
Talk_end_time = ""
5+
Title = "Principles of Collaborative Automation"
6+
Type = "talk"
7+
Speakers = ["jessica-kerr"]
8+
+++
9+
10+
How can we make our tools work with our team? Like a good team member, great tools keep us informed, implement our decisions, and help us understand errors. Drawing from aviation, medicine, and software, here are strategies for choosing and building tools that enhance us and do not frustrate us.
11+
12+
Great automation doesn’t replace humans; it enhances us. When we are choosing or building tools for our team, we want them to play like team members: keep us informed, make the easy decisions repeatably, and pass the hard decisions to the humans along with the information we need to make them.
13+
14+
Based on research in human-centered design, this talk enumerates principles and challenges of collaboration for programs. It lists strategies for eliminating “human error” as well as human frustration. Our tools should make us smarter, not hide knowledge from us. In aviation and medicine, this is a million-dollar investment–-but when we construct our own tools, collaborative automation is within our reach.
+11
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
+++
2+
Talk_date = ""
3+
Talk_start_time = ""
4+
Talk_end_time = ""
5+
Title = "A Day, a Week, a Month in the Life of a Cascading Failure"
6+
Type = "talk"
7+
Speakers = ["john-engelman"]
8+
+++
9+
10+
Microservice architectures provide immense benefits to the flexibility and speed of development, but they also introduce significant complexity in the way the distributed components interact with each other. Eventually, all distributed systems will encounter an error or failure. Sometimes these errors can express themselves outside of the isolation of single component and cause a series of cascading failures in interconnected system. This is the story of one such failure, the lessons learned, and how it's influenced our architecture and design decisions moving forward.
11+
+14
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
+++
2+
Talk_date = ""
3+
Talk_start_time = ""
4+
Talk_end_time = ""
5+
Title = "Cultivating Production Excellence: Taming Complex Distributed Systems (Opening Keynote)"
6+
Type = "talk"
7+
Speakers = ["liz-fong-jones"]
8+
+++
9+
10+
Taming the complex distributed systems we're responsible for requires changing not just the tools and technical approaches we use; it also requires changing who is involved in production, how they collaborate, and how we measure success.
11+
12+
In this talk, you'll learn about several practices core to production excellence: giving everyone a stake in production, collaborating to ensure observability, measuring with Service Level Objectives, and prioritizing improvements using risk analysis.
13+
14+
+10
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
+++
2+
Talk_date = ""
3+
Talk_start_time = ""
4+
Talk_end_time = ""
5+
Title = "Intelligent Deployment Pipelines"
6+
Type = "talk"
7+
Speakers = ["martez-reed"]
8+
+++
9+
10+
A deployment pipeline often consists of a Jenkins pipeline and a few commands to deploy a service. The problem with this is that most pipelines lack the intelligence necessary to make decisions based upon real-time data being generated. While not quite as bleeding edge as AI driven pipelines, it is a step in that direction where the pipeline knows how to make decisions using disparate data from the environment. The goal of the presentation is to provide an end to end example of how a deployment pipeline can become more intelligent by harnessing data that is already being captured in existing systems within the environment.
+14
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
+++
2+
Talk_date = ""
3+
Talk_start_time = ""
4+
Talk_end_time = ""
5+
Title = "Ghost in the Machine: The Consequences of Bias in AI"
6+
Type = "talk"
7+
Speakers = ["nivia-henry"]
8+
+++
9+
10+
What if the code you’ve written alienated some of its users? Or what if it caused a group of people real-life harm? If you're a responsible engineer, these should be among your biggest concerns.
11+
12+
Artificial Intelligence and Machine Learning has introduced a new paradigm wherein code can do actual harm outside of its contained environment. While some of the effects may be comical (think: bad art made by AI), others can be deeply unfair to large groups of your users.
13+
14+
Come with Nivia, an engineering manager at Spotify, on a journey to explore the world of machine learning. We'll explore how algorithms are created, trained, and implemented, and more importantly, discuss practical steps to mitigate and eliminate such biases.
+12
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
+++
2+
Talk_date = ""
3+
Talk_start_time = ""
4+
Talk_end_time = ""
5+
Title = "Timber! Security Logging at UnitedHealth Group"
6+
Type = "talk"
7+
Speakers = ["serena-tiede"]
8+
+++
9+
10+
Logs: they’re not interesting beyond debugging and service monitoring, until you’ve been breached and then everyone wants them. As your security people sift through the logs you find out that the logs aren’t standardized, and the logs on your compromised server have been erased.
11+
12+
Now imagine a different scenario where all the logs are normalized, as most SIEM (Security Incident and Event Management) tools cannot parse custom application logs super well. And for incident response, it's key to get as much security data as possible off a compromised endpoint and into a central repository. All it takes is a schema, kafka, and several very busy people. The key takeaways are why you need to normalize your logs, why you need to stream logs, and how to run a large platform with a small team.
+12
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
+++
2+
Talk_date = ""
3+
Talk_start_time = ""
4+
Talk_end_time = ""
5+
Title = "Secure Enough: Building Security in Without Handcuffing the Business"
6+
Type = "talk"
7+
Speakers = ["yolonda-smith"]
8+
+++
9+
10+
Balancing business requirements with security initiatives is tough. Not only are you concerned with scale, latency, resiliency, availability AND delivery of new features, but you also have to pore through mostly generic, sometimes contradictory guidance and 'hair on fire' exclamations from security claiming that the end is nigh because there's an instance of cross site scripting on a help page. Is cross site scripting really that bad in this case?
11+
12+
It's been said that 'perfect is the enemy of good' and nowhere is that more true than in devops. But how do you know when you've reached good when it comes to securing your product, service or API? The answer, actually, has very little to do with technology and everything to do with how well you know your end users and your ability to quantify how security tradeoffs will enhance or degrade the trust your users place in your company. In this talk, I will highlight the major security obligations of any application and provide some techniques to help you evaluate whether your security is 'good enough'.

Diff for: content/events/2019-minneapolis/propose.md

+5-3
Original file line numberDiff line numberDiff line change
@@ -3,17 +3,19 @@ Title = "Propose"
33
Type = "event"
44
Description = "Propose a talk for devopsdays Minneapolis 2019"
55
+++
6-
{{< cfp_dates >}}
76

87
<hr>
98

109
There are three ways to propose a topic for devopsdays Minneapolis 2019:
1110
<ol>
12-
<li><strong><em>A 30-minute talk</em></strong> presented during the conference. We're currently accepting proposals for 30-minute talks via the form below.</li>
13-
<li><strong><em>An Ignite talk</em></strong> presented during the <a href="/pages/ignite-talks-format">Ignite sessions</a> (we have Ignites at our evening event on Tuesday night). These are 5 minutes slots with slides changing every 15 seconds (20 slides total). We will open the call for Ignite talks closer to the time of the conference.</li>
11+
<li> We've selected our lineup of 30-minute & workshop {{< event_link page="speakers" text="speakers!" >}}
1412
<li><strong><em>Open Space</em></strong>: If you'd like to lead a group discussion during the attendee-suggested <a href="/pages/open-space-format">Open Space</a> breakout sessions, it is not necessary to propose it ahead of time. Those topics are suggested in person at the conference. If you'd like to demo your product or service, you should <a href="../sponsor">sponsor the event</a> and demo it at your table.
13+
<li><strong>We're currently accepting proposals through May 24th for <em>an <a href="/pages/ignite-talks-format">Ignite talk</a></em></strong> presented during the Tuesday evening event. These are 5 minutes slots with slides changing every 15 seconds (20 slides total).</li>
1514
</ol>
1615

16+
17+
<iframe src="https://docs.google.com/forms/d/1cmTX8zzgy_Z81Vid1IHuqy8zGhEJPx4j13t0TgNFXNU/viewform?embedded=true" width="900" height="1600" frameborder="0" marginheight="0" marginwidth="0">Loading...</iframe>
18+
1719
<hr>
1820

1921
Choosing talks is part art, part science; here are some factors we consider when trying to assemble the best possible program for our local audience:

Diff for: content/events/2019-minneapolis/speakers.md

+5
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
+++
2+
Title = "Speakers"
3+
Type = "speakers"
4+
Description = "Speakers for devopsdays Minneapolis 2019"
5+
+++
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
+++
2+
Title = "Alice Goldfuss"
3+
Twitter = "alicegoldfuss"
4+
image = "alice-goldfuss.png"
5+
type = "speaker"
6+
linktitle = "alice-goldfuss"
7+
8+
+++
9+
10+
Alice Goldfuss is a systems punk currently helping GitHub run their cutting-edge container platform. She loves kernel crashes, memory design, and performance hacks. {{< emoji ":rainbow:" >}} {{< emoji ":floppy_disk:" >}} <img src="/images/octocat.png" height="24" width="24">
11+
12+
Alice has consulted on some books (_Docker: Up & Running_, _Effective DevOps_, _Site Reliability Engineering vol 2_), presented at some conferences (SREcon, Velocity, Container Summit), and run some others (LISA17, DevOps Days Portland). You can follow her on Twitter {{< emoji ":bird:" >}} (<a href="https://twitter.com/alicegoldfuss">@alicegoldfuss</a>), but you’ll probably regret it.
+10
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
+++
2+
Title = "Ana Medina"
3+
Twitter = "Ana_M_Medina"
4+
image = "ana-medina.png"
5+
type = "speaker"
6+
linktitle = "ana-medina"
7+
8+
+++
9+
10+
Ana is a Software Engineer living in San Francisco. She is currently working as a Chaos Engineer at Gremlin, helping companies avoid outages by running proactive chaos engineering experiments. She last worked at Uber where she was an engineer on the SRE and Infrastructure teams specifically focusing on chaos engineering and cloud computing. Catch her tweeting at @Ana_M_Medina mostly about traveling, diversity in tech and mental health.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
+++
2+
Title = "Carolyn Van Slyck"
3+
Twitter = "jrrickard"
4+
image = "carolyn-van-slyck.png"
5+
type = "speaker"
6+
linktitle = "carolyn-van-slyck"
7+
8+
+++
9+
10+
Carolyn is a software developer based in the wilds of suburban Chicago, working remote on the Microsoft Cloud Native Team. Her passion is developer tools, and building vibrant inclusive open-source communities around them.
11+
12+
She is maintainer for the CNAB Spec, Duffle and Porter, Kubernetes Service Catalog and the GoMods Athens Proxy. Carolyn runs Women Who Go, and organizes for the Chicago chapters of Women Who Go and Write/Speak/Code.
13+
14+
In between code reviews, Carolyn hauls her cookies around the world to share her love of open-source, containers, and excessive emoji. {{< emoji ":rainbow:" >}} {{< emoji ":sparkles:" >}}
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
+++
2+
Title = "Jeremy Rickard"
3+
Twitter = "jrrickard"
4+
image = "jeremy-rickard.png"
5+
type = "speaker"
6+
linktitle = "jeremy-rickard"
7+
8+
+++
9+
10+
Jeremy Rickard is a software engineer on the Azure Container Compute team working remotely in Colorado. He works on a number of open source projects, including Virtual Kubelet, Open Service Broker for Azure, Service Catalog and Cloud Native Application Bundle tooling. Before that, he worked at VMware and helped build infrastructure and services that support VMware Cloud Services and built services using Spring, Cloud Foundry and Kubernetes.
+10
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
+++
2+
Title = "Jessica Kerr"
3+
Twitter = "jessitron"
4+
image = "jessica-kerr.png"
5+
type = "speaker"
6+
linktitle = "jessica-kerr"
7+
8+
+++
9+
10+
Jessica Kerr is a developer of development automation. She works at Atomist, where she writes delivery automation in TypeScript on Node. She also speaks at conferences around the world; last year she keynoted in seven cities in the US and Australia, at conferences from DDD to Mob Programming to Future of Software. Her true love is symmathesy: people and software collaborating to build something useful in the world.
+10
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
+++
2+
Title = "John Engelman"
3+
Twitter = "johnrengelman"
4+
image = "john-engelman.png"
5+
type = "speaker"
6+
linktitle = "john-engelman"
7+
8+
+++
9+
10+
John Engelman is the Principal Engineer for Platform Services at Target in Minneapolis, MN. In this role, he oversees the developer experience on the Target Application Platform including the platform’s API and build/deployment tooling. Previously, John was the Chief Technologist for DevOps at Object Partners, a software consulting company, and a Software/Systems Engineer for Lockheed Martin. John is a core maintainer for the Ratpack project, the author of the Gradle Shadow plugin, and a regular contributor to open source projects including Terraform, Gradle, and Spinnaker.
+10
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
+++
2+
Title = "Lilia Gutnik"
3+
Twitter = "superlilia"
4+
image = "lilia-gutnik.png"
5+
type = "speaker"
6+
linktitle = "lilia-gutnik"
7+
8+
+++
9+
10+
Lilia Gutnik comes to PagerDuty by way of 10+ years of designing data-driven products for enterprise customers. As a product owner at PagerDuty, she's passionate about helping people learn from data to make decisions and solve problems. In her spare time, Lilia plays keyboard in the PagerDuty band (the OnCalls), volunteers for Code2040, and watches any movie Keanu Reeves is in.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
+++
2+
Title = "Liz Fong-Jones"
3+
Twitter = "lizthegrey"
4+
image = "liz-fong-jones.png"
5+
type = "speaker"
6+
linktitle = "liz-fong-jones"
7+
8+
+++
9+
10+
Liz is a developer advocate, labor and ethics organizer, and Site Reliability Engineer (SRE) with 15+ years of experience. She is an advocate at Honeycomb.io for the SRE and Observability communities, and previously was an SRE working on products ranging from the Google Cloud Load Balancer to Google Flights.
11+
12+
She lives in Brooklyn with her wife, metamours, and a Samoyed/Golden Retriever mix, and in San Francisco and Seattle with her other partners. She plays classical piano, leads an EVE Online alliance, and advocates for transgender rights as a board member of the National Center for Transgender Equality.

0 commit comments

Comments
 (0)