You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/events/2016-minneapolis/program.md
+26-20
Original file line number
Diff line number
Diff line change
@@ -8,27 +8,29 @@ type = "event"
8
8
+++
9
9
10
10
<hr>
11
-
<divclass="span-16 last ">If you are new to the Open Space concept you may <ahref="/pages/open-space-format">want to read some more details</a>.</div>
11
+
<divclass="span-14 last ">With talks in the morning and attendee-suggested <ahref="/pages/open-space-format">Open Space</a> breakout discussions in the afternoon, we have two full days of content! </div>
12
12
</center>
13
13
<hr />
14
14
15
15
16
-
<center><b><h2>The Schedule</h2></b></center>
16
+
<center><b><h2>Schedule</h2></b></center>
17
17
<divclass="span-7 append-bottom border">
18
18
19
19
<divclass="span-7 last">
20
-
<h4>Day 1</h4>
20
+
<h4>Wednesday July 20</h4>
21
21
</div>
22
22
23
23
<divclass="span-2">08:00-09:00</div><divclass="span-4 box last">Registration, Breakfast, and Sponsor Booths Open</div>
<ahref="/events/2016-minneapolis/program/nicole-forsgren">Nicole Forsgren (Chef) - The Data on DevOps: Making the Case for Awesome</a> (Opening keynote)
<divclass="span-2">13:00-14:00</div><divclass="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space Opening</div>
55
58
56
-
<divclass="span-2">13:30-14:00</div><divclass="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space Opening</div>
59
+
<divclass="span-2">14:00-14:45</div><divclass="span-4 box last"><strong>attendee-suggested <ahref="/pages/open-space-format">Open Space</a> breakout discussions</strong> Open Space #1</div>
57
60
58
-
<divclass="span-2">14:00-14:45</div><divclass="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space #1</div>
<divclass="span-2">15:00-15:45</div><divclass="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space #2</div>
63
+
<divclass="span-2">15:00-15:45</div><divclass="span-4 box last"><strong>attendee-suggested <ahref="/pages/open-space-format">Open Space</a> breakout discussions</strong> Open Space #2</div>
61
64
62
-
<divclass="span-2">16:00-16:45</div><divclass="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space #3</div>
65
+
<divclass="span-2">15:45-16:30</div><divclass="span-4 box last"><strong>attendee-suggested <ahref="/pages/open-space-format">Open Space</a> breakout discussions</strong> Open Space #3</div>
63
66
64
-
<divclass="span-2">16:45-17:00</div><divclass="span-4 box last"><strong></strong>Close Day & Logistics</div>
<ahref="/events/2016-minneapolis/program/charity-majors">Charity Majors (Hound) - Making good choices with software (and other impossible things)</a> (Closing keynote)
<divclass="span-2">13:00-14:00</div><divclass="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Sponsor Raffle & Open Space Opening</div>
111
117
112
-
<divclass="span-2">13:30-14:00</div><divclass="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space Opening</div>
118
+
<divclass="span-2">14:00-14:45</div><divclass="span-4 box last"><strong>attendee-suggested <ahref="/pages/open-space-format">Open Space</a> breakout discussions</strong> Open Space #1</div>
113
119
114
-
<divclass="span-2">14:00-14:45</div><divclass="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space #1</div>
<divclass="span-2">15:00-15:45</div><divclass="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space #2</div>
122
+
<divclass="span-2">15:00-15:45</div><divclass="span-4 box last"><strong>attendee-suggested <ahref="/pages/open-space-format">Open Space</a> breakout discussions</strong> Open Space #2</div>
117
123
118
-
<divclass="span-2">16:00-16:45</div><divclass="span-4 box last"><strong>Open Space</strong> (Open Space) <br /> Open Space #3</div>
124
+
<divclass="span-2">15:45-16:30</div><divclass="span-4 box last"><strong>attendee-suggested <ahref="/pages/open-space-format">Open Space</a> breakout discussions</strong> Open Space #3</div>
119
125
120
-
<divclass="span-2">17:00</div><divclass="span-4 box last"><strong></strong>Close Day & Farewell</div>
<p>Docker and Kubernetes provide delightful APIs to show various statuses of our applications. Whether CPU, Load average, HTTP response times, etc., we have all that we need to make sure our app is running healthily. When things are on fire, we Ops people twiddle some knobs like spin up more Pods to keep things going. We mostly use our experience and knowledge of the systems that we are running to know what to do.
20
+
</p>
21
+
<p>
22
+
However, if you look at everyday things like your air conditioner and thermostat, they don't have an Ops team that gets paged to set the correct level of the coolant to set your room to the right temperature. They use some math called <i>Control Theory</i> to keep your room's temperature stable. In this talk, I will show how we can use the same concepts to autoscale and manage the health of our applications on Kubernetes.
We keep hearing that to 'do DevOps right' we need to tear down all the silos in order to get everyone collaborating as well as just cooperating. How do we continue to benefit from DevOps practices when the silos are there for the foreseeable future and may actually have some benefit, even if only perceived?
21
+
</p>
22
+
<p>
23
+
In a large enterprise, dedicated operations groups frequently serve multiple development groups, using the specialization of these groups to increase efficiency by having a smaller operations staff. These organizations use separation of duties to avoid real or apparent conflicts of interest and a higher level of security. Silos become firmly embedded because they work in these situations.
24
+
</p>
25
+
<p>
26
+
When silos are entrenched and can’t be torn down, or even when they’re just dictated above our pay grades, how can we use DevOps to increase collaboration and empathy? What other concepts of DevOps can we use to reduce the pain? What can operations teach development and learn from development to make systems more reliable and IT more successful?
27
+
</p>
28
+
<p>
29
+
In this session, I’ll present my version of the DevOps philosophy and how it can be applied in an enterprise environment without tearing down all the silos. I’ll tell success stories and failures as well as discussing continuing challenges to make improvements and change the culture in the trenches.
Making good choices with software (and other impossible things) (Closing Keynote)
15
+
</p>
16
+
17
+
<p><strong>Description:</strong></p>
18
+
19
+
<p>
20
+
Once upon a time there was a LAMP stack, and a data center, and making reasonably good technical decisions was a thing that ordinary mortals could do. Over the last few years we've seen an explosion of complexity -- composable infrastructure, polyglot persistence, and third-party platforms or services who claim they can solve your problems for you (sometimes this is even true!).
21
+
</p>
22
+
<p>
23
+
24
+
What does this mean for you and me? It means that good technical judgment is both more challenging and more important than ever before. In this talk we will cover things like about when to use boring technology, versus when to take a flyer on something new and shiny. We'll also talk about how to resist software sprawl, gating new technologies into production, and how to balance speed of development vs operational impact over time. So don't despair! With just a little bit of discipline, we can still build systems that ordinary humans can understand and maintain, even in the face of skyrocketing complexity and problems of scale."
A good monitoring stack is more than the software that says ‘monitoring’ on the label. Maybe your monitoring system is a bunch of cron scripts that send email when things happen. Maybe you dropped $100K on licensed software that can email reports and has its own mobile app. When used as part of systemic approach to monitoring, both approaches can lead your organization to success.
21
+
</p>
22
+
<p>
23
+
24
+
Monitoring is a stack, and like most web applications there are discrete components that all systems have. Sometimes they’re automated, sometimes they’re 100% people-driven. What matters is that you have the system that works for you and your organization.
25
+
</p>
26
+
<p>
27
+
28
+
We will cover what those components are and how they work together. What’s more, we’ll touch on the conversations you should have as you work to systematize your monitoring practices. We won’t tell you what technology you should use, that’s entirely up to you."
Your organization is rolling out DevOps and everyone is excited and on-board! Life is going to be perfect post-devops, because DevOps is the cure for all that ails your company. Because levels expectations and levels of disappointment seem to have a relationship, I’d like to talk to you about our experience with the DevOps transformation.
21
+
</p>
22
+
<p>
23
+
Come join Jeff Smith as he walks through the trials and tribulations of destroying the silos in your organization. Buried inside all of the hype of DevOps are hurdles, people problems and mission creep that can derail your transformation. We’ll cover areas like:
24
+
</p>
25
+
<p>
26
+
* Toolchain Paralysis - With all the tools out there to help you realize the DevOps dream, its easy to get caught up in the tools/solution hype cycle. Don’t let the community tell you what is a must-do. We’ll talk about making sure you solve your problems instead of Google’s or Facebook’s.
27
+
</p>
28
+
<p>
29
+
* Skill set augmentation - DevOps chats are famous for the adage “Hire the Right People”. But I’m guessing you already thought you were doing that. How do you get developers and ops to gain skills in the other’s discipline?
30
+
</p>
31
+
<p>
32
+
* On Call Support - When you disperse Ops staff into stream teams, you also have the potential to dilute the number of on-call people who can handle issues. There are tons of options and all of them have a downside.
33
+
</p>
34
+
<p>
35
+
and more! Don’t think these hurdles are new or unique. You’ll get through them, and hopefully we’ll help show you how.
Security 101 principles often conflict with how organizations function in the real world. Developers need flexibility in order to solve hard problems; companies need a stable product to satisfy customers. Employees don’t want to click through ten different screens to complete daily tasks; auditors and regulators demand logs and accountability.
21
+
</p>
22
+
<p>
23
+
24
+
Legacy systems need to be monitored. New projects need to be nurtured. And, while you’re doing all of that, attackers are constantly rattling the doorknobs to find a foothold in your network. I’ll go over a few lessons I’ve learned about how security departments can lobby for continuous improvement, while collaborating with others and even occasionally saving the organization money.
25
+
</p>
26
+
<p>
27
+
28
+
Over my career, I’ve worked in .com, retail, and academia. While the challenges in each of these realms are unique, there is a common thread in all of the successful outcomes I’ve witnessed. Effective security departments are optimists who play well with others.
29
+
</p>
30
+
<p>
31
+
32
+
It's fun to pretend you're the smartest person in the room ... until no one wants to play with you. The “us versus the world” mindset isn’t constructive. In this talk I’ll illustrate how security can work for change without alienating everyone else on the playground.
What’s the value proposition of DevOps? Does culture change show up in the bottom line? What practices predict high IT performance? We hear many stories to inspire and inform us, but the plural of anecdote is not data. Let’s dive into the research and find out which DevOps practices drive optimal IT and business outcomes.
21
+
</p>
22
+
23
+
<p>
24
+
The data shows that the best IT performers have the highest throughput and reliability while contributing to organizational profitability, productivity, and market share goals. Industry trends around security, containers, continuous delivery, and lean management relate to IT performance and quality: let’s talk about how.
25
+
</p>
26
+
27
+
<p>
28
+
Management and practitioners alike will leave with a better understanding of how to achieve the best outcomes, while armed with the data they need to make the case for change.
0 commit comments