+ 
+ |
+DevOpsDays Minneapolis 2016 information is available at DevOpsDays Minneapolis 2016!
+ +DevOpsDays Minneapolis 2015 was Wednesday & Thursday July 8-9, 2015. It was held at the {{< event_link page="location" text="downtown Minneapolis Hilton" >}}. + +You can view the DevOpsDays Minneapolis 2015 {{< event_link page="program" text="program of 30-min talks & Ignites" >}}. + -DevOps Days is coming to {{< event_location >}}! +{{< event_link page="contact" text="Email the organizers" >}}. - - -
diff --git a/static/events/2015-minneapolis/devopsmsp-logo-2015.png b/static/events/2015-minneapolis/devopsmsp-logo-2015.png new file mode 100644 index 00000000000..63ef41dd94e Binary files /dev/null and b/static/events/2015-minneapolis/devopsmsp-logo-2015.png differ diff --git a/static/events/2015-minneapolis/proposals/A DevOps Philosophy/index.html b/static/events/2015-minneapolis/proposals/A DevOps Philosophy/index.html new file mode 100644 index 00000000000..1ed4889af5b --- /dev/null +++ b/static/events/2015-minneapolis/proposals/A DevOps Philosophy/index.html @@ -0,0 +1,379 @@ + + + + + +
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Adoption of ChatOps/index.html b/static/events/2015-minneapolis/proposals/Adoption of ChatOps/index.html
new file mode 100644
index 00000000000..a9d5c137151
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Adoption of ChatOps/index.html
@@ -0,0 +1,370 @@
+
+
+
+
+
+
+
+
+
+
+
+  +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+A DevOps Philosophy+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: +One of the main tenets of the Devops movement is empathy. One might even say it is the "essence" of Devops. + +Throughout history, great philosophers, writers, and thinkers have passed along important thoughts and ideologies about our relationships, our passions, our purpose, and our place in this world. Time and time again, they return to the idea of empathy in one form or another. + +Henry David Thoreau wrote "Could a greater miracle take place than for us to look through each other's eye for an instant?" Heinz Kohut, an American clinical psychologist, was the first to consider empathy as a form of internal scientific inquiry. "Our task must be to free ourselves from this prison by widening our circle of compassion to embrace all living creatures and the whole of nature in its beauty." wrote Albert Einstein. Even the Golden Rule of "One should treat others as one would like others to treat oneself." is a message passed down through scripture. You know - "Do unto others" + +Philosophy, like the DevOps movement, forces us to ask questions of ourselves and our place in the bigger picture. How do we interact & communicate with others? What does it take to be a contributing member of a team and how can you be a better teammate? + +We will use this as a platform to explore additional parallels of basic philosophy and the ideals that are a part of that and how they can be woven into the fabric of Devops. Call it a different approach at explaining the Devops message and movement. + +Additionally, we'll touch on the fact that (like in philosophy), "leaders" and "teachers" will surface to "Show you the way" (of Devops). Some have the best of intentions, others may just be looking out for themselves or trying to make money on the movement. (i.e. DevOps Institute?) + +Where do casual observers of Devops "best practices" fall in to this? Compare that to those who follow the Devops methodology by the book and rarely deviate. Is one better than the other? + +By placing the ideals of Devops in to a different context, perhaps we can spark other interesting thoughts and dialogues that may help others to seek what Devops may mean to them and how they can apply it to their own situations within an organization. + +Speaker: +Speaker 8 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Building Reactive Infrastructure with Consul/index.html b/static/events/2015-minneapolis/proposals/Building Reactive Infrastructure with Consul/index.html
new file mode 100644
index 00000000000..e0645bb58da
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Building Reactive Infrastructure with Consul/index.html
@@ -0,0 +1,376 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Adoption of ChatOps for non-distributed teams+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +ChatOps is a topic that has really started to gain traction within the last year. As teams begin to adopt the practice of inserting tools right within their conversations, more and more questions are being raised. Many of those questions are simply "how do I get started?" + +In many cases, teams are distributed across the country or broader and adopting the practice of ChatOps is easy and the benefits are clear. Conversely, for those teams who all work together, it's tougher to find obvious motivation to adopt the practice. + +We'll address methods of bringing non-distributed teams in to the modern age of ChatOps by highlighting the primary benefits of the practice with a focus on what is important even when your entire team works under one roof. + +Speaker: +Speaker 8 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Building SaaS Applications on AWS/index.html b/static/events/2015-minneapolis/proposals/Building SaaS Applications on AWS/index.html
new file mode 100644
index 00000000000..bcddc4a5cb3
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Building SaaS Applications on AWS/index.html
@@ -0,0 +1,366 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Building Reactive Infrastructure with Consul+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract + +This talk will cover many of the high-level features of Consul as they relate to monitoring. While this talk may seem deeply technical on the surface, it is aimed at a very large audience. I will not discuss setup or installation of Consul, but I will demonstrate the Consul Web UI and command line. There will be some commands/code on slides, but there will be no live demos. + +One of the goals of this talk is to demonstrate the Consul is more than a monitoring solution - it is a runtime for the modern datacenter. Consul allows infrastructure to adapt to the changing needs of any environment. + +Descripton + +Consul is an open source tool for service discovery, monitoring, and infrastructure configuration. There are two sides to monitoring -- exposing problems with alerts and acting upon those alerts to automatically resolve them when possible or notify an operator. + +For exposing problems, Consul works much like other monitoring solutions. Users can define any script for Consul to intelligently check and report the health status of a node in a cluster. In this way, Consul is compatible with Nagios and Sensu style checks, but the problem with monitoring systems like Nagios or Sensu is that they are knowledge silos. They are designed to ingest health information and expose them to human operators. Consul supports health monitoring using Nagios-style plugins, but it is designed to expose that information in a way that is both machine and human actionable. + +With Consul custom watches and service discovery integration, infrastructure can automatically react and adjust around failures. If a web node is reporting an unhealthy state, Consul can automatically remove the node from the load balancer. If a disk space health check is low, Consul can automatically run logrotate and delete everything in Speaker: +Speaker 1 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Cheffing Etsy/index.html b/static/events/2015-minneapolis/proposals/Cheffing Etsy/index.html
new file mode 100644
index 00000000000..16fd2dd7ac5
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Cheffing Etsy/index.html
@@ -0,0 +1,390 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Building SaaS Applications on AWS+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +The software industry is rapidly moving to a Software-as-a-Service (SaaS) model. Compared to traditionally licensed software, SaaS greatly shortens release cycles, significantly shrinks support costs, and allows publishers to reach the global market. As part of this agile evolution, more and more developers are choosing to create their SaaS products in the public cloud. This talk will introduce the experienced web developer to building a highly-scalable, self-healing SaaS application on Amazon Web Services. Some of the things you'll take back to work: The business reasons for building a SaaS product over an installed product, the scalability and security challenges introduced by serving thousands of customers from a single instance of an application, and the different tenancy models and the tradeoffs of each. + +Speaker: +Speaker 14 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Choose Boring Technology/index.html b/static/events/2015-minneapolis/proposals/Choose Boring Technology/index.html
new file mode 100644
index 00000000000..f068d92b8af
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Choose Boring Technology/index.html
@@ -0,0 +1,370 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Cheffing Etsy: Do too many cooks really spoil the soup?+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +It's an oft-quoted adage that too many cooks spoil the soup. But is this always true? At Etsy, we have roughly 40 Ops and Developers making upwards of 20 or 30 Chef changes per day. + +In this talk, I'll look at the tools, techniques and workflows we leverage to enable tens of people spread across teams, timezones and even countries to work together to continuously deliver Chef changes with nearly the same frequency we ship code. Although the specific tooling discussed in this talk is designed to work with Chef, many of the techniques and practices I'll talk about are applicable to many other engineering disciplines - the importance of communication and visibility in a Continuously Delivered world, the importance of testing and metrics, and optimising your workflows to remove friction and enable agility while also satisfying the requirements of your stakeholders. + +This talk will break down roughly as follows: + +
Slides: + + + + ++ + Video: + + + + +Speaker: +Speaker Jon Cowie + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Code like a Beginner with the Insight of a Pro/index.html b/static/events/2015-minneapolis/proposals/Code like a Beginner with the Insight of a Pro/index.html
new file mode 100644
index 00000000000..1db6716eac4
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Code like a Beginner with the Insight of a Pro/index.html
@@ -0,0 +1,370 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Choose Boring Technology+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +How do you choose the technology to run your business? The prevailing advice du jour is something like: "use the best tool for the job." This is obviously right, but it is also devoid of meaning in an unfortunate way that lets people define the words "best" and "job" as myopically as they like. + +This talk aims to give shape to these nebulous terms. Your job is to keep your company in business. The best tools tend to be the ones that solve the widest array of problems while requiring the least amount of operational overhead. If innovation happens when preparation meets opportunity, I submit that opportunity rarely appears in the form of an unforeseen data loss bug. + +Choose boring technology. If you can get past this, you can be exciting in ways you can't imagine. + +Speaker: +Speaker 17 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/DevOops Unintended War Stories/index.html b/static/events/2015-minneapolis/proposals/DevOops Unintended War Stories/index.html
new file mode 100644
index 00000000000..76442c24446
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/DevOops Unintended War Stories/index.html
@@ -0,0 +1,369 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Code like a Beginner with the Insight of a Pro+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +Too often, the most experienced people on your team, the ones who have so much to teach, are also the hardest to understand. Documentation frequently falls out of date, intimidated rookies become the norm, and perl golf jokes get thrown around (and actually implemented). + +For this reason, its really important to establish a natural method of knowledge transfer. Too many people have work that cant be completed or improved upon by others due to siloed strategies and implementations. Collaborative work using things like wiki's, git repositories, code reviews, partner programming (even in reactive situations), allows you to get things done right, improve processes, and move forward in all areas of work. This gives you the best bang for your buck and keeps things progressing. + +Documentation becomes universally understood. Information spreads naturally through the organization. Decisions get made quicker and concensus is established early. Walking through these strategies allows us to find ways where everyone of every level can contribute, and even those experts, really hone their skills and consider things they originally didnt think about. Everyone improves and everyone becomes an expert. + +Speaker: +Speaker 13 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/DevOps Day 2 - People and Process/index.html b/static/events/2015-minneapolis/proposals/DevOps Day 2 - People and Process/index.html
new file mode 100644
index 00000000000..383e3ee73c8
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/DevOps Day 2 - People and Process/index.html
@@ -0,0 +1,376 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+DevOops: The (Unintended) War Stories+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: +It's your birthday, and the day before your vacation starts. You arrive at the office, prep your workstation, get a drink, and start the day. Almost immediately, you start to receive indicators that multiple core systems are beginning to have critical failures as the slow trickle of alerts increases to multiple alarms sounding. By now the systems are entirely inaccessible due to system load, and you watch the count of outgoing alerts plummet. It's 10:52 am; it's your aircraft. + +These are the PagerDuty (Unintended) War Stories. + +In this talk we'll discuss the failures, the successes, and the outcomes of unexpected incidents at PagerDuty. This includes the technical details of the outage, and how an internal incident commander was used to coordinate the recovery work across multiple teams cohesively. + +Speaker: +Speaker 26 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/DevOps Next Steps - Event Driven Operations/index.html b/static/events/2015-minneapolis/proposals/DevOps Next Steps - Event Driven Operations/index.html
new file mode 100644
index 00000000000..6134b0a2557
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/DevOps Next Steps - Event Driven Operations/index.html
@@ -0,0 +1,366 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+DevOps Day 2: People and Process+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +DevOps is often heralded as the solution to all the problems within IT - planning, slow delivery, large team, etc. All solved via automation. Yet, DevOps is not a technology problem at core, but rather a business problem. Once the dust settles and the new tools are implemented, the more challenging problems begin. Implementation of a DevOps type practice requires change and adaptation of the practices within the framework of the existing culture, and these challenges are often overlooked or poorly addressed.
Speaker: +Speaker 15 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/DevOps The Missing Pieces/index.html b/static/events/2015-minneapolis/proposals/DevOps The Missing Pieces/index.html
new file mode 100644
index 00000000000..37f8bc65f7e
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/DevOps The Missing Pieces/index.html
@@ -0,0 +1,378 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+DevOps Next Steps: Event Driven Operations+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +The most critical component of building out successful a DevOps culture is creating a successful merger of sustainable technology and process. ChatOps practices help teams accelerate delivery by bringing in technology operations inline with conversations already happening today. This in turn helps turns operations into simple events than can be chained together to make teams even more powerful and flexible than ever before! This talk discusses the practical implementations of ChatOps and how it can be used to grow teams of all types and sizes. + +Speaker: +Speaker 15 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/DevOps as understood by a young IBM developer/index.html b/static/events/2015-minneapolis/proposals/DevOps as understood by a young IBM developer/index.html
new file mode 100644
index 00000000000..942f0c9daaf
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/DevOps as understood by a young IBM developer/index.html
@@ -0,0 +1,379 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+DevOps: The Missing Pieces+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Opening Keynote: + +Devops has come a long way in the 5+ years since its inception. From simply breaking down silos and automating/measuring all the things, we’ve grown and started talking recently about complexity and inclusivity, burnout and empathy. We started trying to make people's professional lives better in the fields of development and operations; this expanded in two dimensions: both including more teams (QA! Databases! Even security!) and outside of the office, encouraging people to think about burnout and work-life balance. + +What’s missing from this picture? Or rather, what’s next for devops? I’d like to propose that, as the lines between the “online” world and the “real” world blur and fade away to nothing, we expand our view of devops to cover this whole new world. Let’s expand our empathy beyond just the tech industry, following the examples of B Corporations who work towards social and environmental good. And let’s talk about how we can make the world better, more empathetic, and safer for everyone, online and off. + +Slides: + + + + +Video: + + + + +Speaker: +Katherine Daniels + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/DevOps for the Masses/index.html b/static/events/2015-minneapolis/proposals/DevOps for the Masses/index.html
new file mode 100644
index 00000000000..3f39cb7ec30
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/DevOps for the Masses/index.html
@@ -0,0 +1,383 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+DevOps as understood by a young IBM developer+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +Most of us have heard about what DevOps is, and what are its merits and challenges. Many of us practice it everyday. In this conference and its past editions, we have heard what the early adopters did to catch the DevOps boat. 1) Various change catalysts in the tech industry. viz. environment, competition, process need, leader's vision, curiosity. 4) What developers need to know when they embark on DevOps transformation? + +I would like the attendees to take this away from my presentation: + +1) Understand what challenges development teams face during the transition to DevOps. Speaker: +Speaker 16 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/DevOps from an investors perspective/index.html b/static/events/2015-minneapolis/proposals/DevOps from an investors perspective/index.html
new file mode 100644
index 00000000000..bc8fe033221
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/DevOps from an investors perspective/index.html
@@ -0,0 +1,366 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+DevOps for the Masses+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +Two core tenets of DevOps are culture and sharing. While devOps is An understanding of the robustness that diversity provides only complicates Please join me as we explore: + +-The perceived threat of diversity Speaker: +Speaker 4 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/DevOps in IBM Power System Testing/index.html b/static/events/2015-minneapolis/proposals/DevOps in IBM Power System Testing/index.html
new file mode 100644
index 00000000000..624eba07da9
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/DevOps in IBM Power System Testing/index.html
@@ -0,0 +1,372 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+DevOps from an investor's perspective+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +Investors - like VCs and strategy planners inside companies - are starting to hear about DevOps and are curious how they might profit from it. This talk is a DevOpsDays version of what those investors want to know, explaing how they view emerging markets like DevOps and evaluate investment into the markets. It contains a "case" for evaluating investments in DevOps, covering the viablity of DevOps from their perspective and possible ways that "DevOps" could effect the models and valuations that investors are performing. The question being answered is: "should I invest in DevOps? Does that even make sense?" + +Speaker: +Speaker 9 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/DevOps in the Machine/index.html b/static/events/2015-minneapolis/proposals/DevOps in the Machine/index.html
new file mode 100644
index 00000000000..0ced87910d5
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/DevOps in the Machine/index.html
@@ -0,0 +1,369 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+DevOps in IBM Power System Testing+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +In this presentation we are going to talk about how DevOps with Jenkins and Urban Code Deploy is used in verifying IBM Power Systems. Is it just the hardware we are testing? No. FSP, PHYP and HMC (Hardware Management Console) are being the major component and they all together makes IBM Power Server a whole product. So how are we going to test different components? How do they work together in achieving extended iterative development process beyond Continuous Integration and achieve Continuous Release, Continuous Delivery and Continuous Testing? + +Is DevOps everything? Will it be sufficient to verify the IBM Power Systems? Obviously Not. There are different test teams. We will see how the quality products are delivered from DevOps to all other test teams. + +We will also see how each team automated their component testing and how do they screen for defects in their respective subsystems using DevOps? And how effective was it? Was it worth moving to DevOps? What was the outcome? Did it improve the product quality ? Did it improve the feedback time to development? + +How did the overall system test cycle improve? Did it improve really? What are the future plans? Let's wait and see. + +Speaker: +Speaker 21 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Effortless WebPerf Monitoring/index.html b/static/events/2015-minneapolis/proposals/Effortless WebPerf Monitoring/index.html
new file mode 100644
index 00000000000..74fb7c44d30
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Effortless WebPerf Monitoring/index.html
@@ -0,0 +1,382 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+DevOps in the Machine+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +In this ignite, a set of tweets from @petechesbot will be selected and presented. Pete Chesbot is the ultimate DevOps bot, distilling down the thought leadership of Pete Cheslock into much more consumable, and often more coherent, ideas. The presenter will explain the truth behind these constructed tweets, and we will all learn some deep insight into the "DevOps in the Machine". + + + + +Speaker: +Matt Stratton + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Empathy Fairness and Contentment/index.html b/static/events/2015-minneapolis/proposals/Empathy Fairness and Contentment/index.html
new file mode 100644
index 00000000000..06ead7036fa
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Empathy Fairness and Contentment/index.html
@@ -0,0 +1,369 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Effortless WebPerf Monitoring+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +Monitoring isn't just for ops people and application developers. Front-end developers need just as much visibility into their work as anyone else. + +When thinking about the things we monitor with our configuration-managed monitoring pipelines, we rarely include the front-end development team or consider their needs from the outset. As the statistics that browser APIs can collect have become more robust, it is becoming easier to standardize the collection of WebPerf stats. + +Inspired by the UK GDS team's event-store project, the team at Critical Mass created a Go program that can collects Navigation Timing API data, Javascript Error Reports, and CSP Reports. The application became the focus of one of our monitoring recipes, and has since become standard on any node serving web pages to end-users. Our front-end developers have developed drop-in javascript functions to interact with this service and thus made WebPerf monitoring relatively turnkey. + +In this ignite, I'd like to talk about the conversations and brainstorming that lead to this initiative, about some of the mechanics of collecting the data, and how it has changed the way front-end developers relate to the production applications and monitoring dashboards used by the team. I plan to focus on the cultural aspects of the experience, but will also be able to share the architecture and code. + +Slides: + + + + +Video: + + + + +Speaker: +Michael Lanyon + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Enabling DevOps Through End to End Performance Monitoring/index.html b/static/events/2015-minneapolis/proposals/Enabling DevOps Through End to End Performance Monitoring/index.html
new file mode 100644
index 00000000000..e748760b0c3
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Enabling DevOps Through End to End Performance Monitoring/index.html
@@ -0,0 +1,379 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Empathy, Fairness, and Contentment+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +Empathy, Fairness, and Contentment + + + + +Speaker: +Jason Walker + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Fear and Failure/index.html b/static/events/2015-minneapolis/proposals/Fear and Failure/index.html
new file mode 100644
index 00000000000..78a7026b8b0
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Fear and Failure/index.html
@@ -0,0 +1,366 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Enabling DevOps Through End to End Performance Monitoring+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +A typical HTTP request lifecycle could be divided on three stages: + +
A request can span dozens of diverse systems and platforms, and with that, many monitoring tools controlled by diverse teams in development, operations, performance and QA. These teams cannot collaborate efficiently as they lack unified data, leaving each team with different limited understanding of what is really happening.With the full lifecycle of the request not well understood and teams operating in silos,its no wonder the end result is unnecessary finger pointing during troubleshooting efforts such as performance incidents. + +For a DevOps team to be successful, they must see the big picture and know the answers to key questions such as:. Where to spend your resources to improve application performance?How to do root cause analysis for performance issues along the entire path?What metrics to use? Identify, in real time, what is and isn't working through the request flow? What your CDN is contributing to this picture? What out-of-your-control performance issues from systems such as mobile carriers or corporate gateways impact your site? + +This talk will look at the tools available to monitor each stage of the request, and then examine how to unify this data into a single real time global view of the request lifecycle. During the presentation you will learn how unified monitoring of the request flow enables DevOps teams to see the big picture and collaborate using an unified set of metrics over a global dashboard. + +Speaker: +Speaker 22 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/GameOps/index.html b/static/events/2015-minneapolis/proposals/GameOps/index.html
new file mode 100644
index 00000000000..ee93ad8dcee
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/GameOps/index.html
@@ -0,0 +1,369 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Fear & Failure+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +Fear & Failure is a soft talk (with no technical content), discussing imposter syndrome, fear of failure, and how to combat them; I follow this up with a discussion on ways to cope with inevitable failure and benefit from it. This talk was inspired by one I saw at the Madison Ruby conference last year, "What Stuttering Taught Me About Marketing", which triggered a lot of self-reflection about why I let my fears hold me back personally and professionally. + +Speaker: +Speaker 3 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Good Bad and Ugly of devOps/index.html b/static/events/2015-minneapolis/proposals/Good Bad and Ugly of devOps/index.html
new file mode 100644
index 00000000000..302f8daaabf
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Good Bad and Ugly of devOps/index.html
@@ -0,0 +1,365 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+GameOps+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +Board games for community building. + + + + +Speaker: +Jason Clifford + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Helping Developers Monitor Their Own Application/index.html b/static/events/2015-minneapolis/proposals/Helping Developers Monitor Their Own Application/index.html
new file mode 100644
index 00000000000..2e9112b6ae9
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Helping Developers Monitor Their Own Application/index.html
@@ -0,0 +1,378 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Good, Bad and Ugly of devOps - A case study of cloud delivery pipeline+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: +Continuous delivery in the cloud requires infrastructure that enables everyone to deliver "good" code any time. In order to build a delivery pipeline infrastructure which can throw bad code you need to build right cloud deployment tools and change management process. Essentially, there are three main stages of a pipeline - image baking stage, acceptance stage and production stage. Code should move through these stages with a trusted infrastructure which can validate for quality, resiliency and security. This talk will showcase real case study of successful cloud deployment pipeline developed by IBM Cloud data services team. I will also talk about some radical ideas of Runbook automation, monitoring and log analytics. + +Speaker: +Speaker 7 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Home is the New Dev/index.html b/static/events/2015-minneapolis/proposals/Home is the New Dev/index.html
new file mode 100644
index 00000000000..916e9178b51
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Home is the New Dev/index.html
@@ -0,0 +1,370 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Helping Developers Monitor Their Own Application+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +I'm a developer. I barely know what Nagios is, let alone how to set it up or configure new alerts. But I do know a lot about the application I'm working on, and I know how to code. By building a framework for easily adding new monitoring rules, the operations team at Swiftype has opened up application-level monitoring for the whole development team. I'll talk about the tools we wrote and explain how they allow developers to easily add new monitoring checks that probe our application (including web services, queues, and database) and alert the team by email, chat, or phone. + +I'll show how to use the monitoring framework we wrote, but I'll also use this collaboration as a jumping off point to discuss how I think developers and operations can work together to build software faster and keep it reliable, based on our experiences at Swiftype. + +Slides: + + + + +Video: + + + + +Speaker: +Luke Francl + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/How to Hire a Good DevOps Engineer/index.html b/static/events/2015-minneapolis/proposals/How to Hire a Good DevOps Engineer/index.html
new file mode 100644
index 00000000000..8ba3c040ff7
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/How to Hire a Good DevOps Engineer/index.html
@@ -0,0 +1,366 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Home is the New Dev+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +Running a homelab is a great way to keep your skills fresh and direct your career trajectory. It's easy to get bogged down by all of the work that you already have in your day job, but using the things you learn on the job and applying it in the form of a fun hobby extends your skillset and keeps you flexible when approaching problems in the real working world. + +In your day job, it can be difficult to get new technologies implemented as there can be perceived risks such as lack of knowledge across your team, new tech not necessarily being fully proven, or just a general unwillingness to change. This does not have to be where the conversation around new technology ends. With effective projects in your home that model some of the ways that you wish your work environment was structured, you get to fully run through your implementation strategy across multiple arenas. + +You become your own dev, ops, QA, and architecture team. You call the shots and get to see what the pain points will be for each and every one of these organizations. Additionally, you expand your skillset to more than just the niche areas you cover normally in your day to day work. Gaining this insight is invaluble and allows you to explore well outside of the normal bounds you would encounter typically in your day job. You make mistakes at home, take responsibility for them without fear or judgement and correct your path. You iterate, learn, develop and gain insight into how to approach problems all without needing any approval. Plus you get to have a little bit of fun doing it. + +Speaker: +Speaker 13 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/How to Teach DevOps with Cookies/index.html b/static/events/2015-minneapolis/proposals/How to Teach DevOps with Cookies/index.html
new file mode 100644
index 00000000000..66040b4307a
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/How to Teach DevOps with Cookies/index.html
@@ -0,0 +1,390 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+How to Hire a Good DevOps Engineer+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +There's a good and a bad side to any role in any industry and devOps is no different. Hiring to help ensure quality and optimize workflows is not anything new but the discipline has changed a lot over the years. We'll cover the history, evolution, and some experiences of this profession that will not only help find homes for wayward DevOps Engineers but empower them to have the desired effect too. + +Speaker: +Speaker 4 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Humanizing Technology/index.html b/static/events/2015-minneapolis/proposals/Humanizing Technology/index.html
new file mode 100644
index 00000000000..5b838180a57
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Humanizing Technology/index.html
@@ -0,0 +1,368 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+How to Teach DevOps with Cookies+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +DevOps can optimize any process that results in an artifact by applying lessons learned from manufacturing and agile software development. Unfortunately not many people firmly understand how either industry works, never mind both of them. Come learn how using a cookie company as a model for devOps provides an example that anyone can grasp. + +When dealing with a new concept it's often convenient to have a base case example to fall back to for reference. In this presentation you'll learn how to teach devOps with cookies by working as a group to apply devOps models like CALMS, ICE, and the Three Ways to our cookie company as that base case reference. Not only are cookies and the baking process a good instructional aid for explaining devOps methodologies and concepts, but the snacks encourage the collaboration needed to work through difficult conversations and problems as well. + +-Why We Use Cookies and Not Gravel + +-Applying Different DevOps Models + +-How to Use Simple Descriptive Statistics + +-How to Use Simple Predictive Statistics + +-How to Manage what Drives Business Prioritization + +-Optimizing Hand Offs and Transitions + +-Defining a Thin Line Between a POC and a MVP + +By the end of the presentation you should be able to form an actionable devOps game plan with a clear next step. + +Attendees will need: + +An network capable device, preferably a phone or a tablet + +A problematic process or concept they're looking to establish or improve with the help of devOps + +Speaker: +Speaker 4 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/If you want to have an impact/index.html b/static/events/2015-minneapolis/proposals/If you want to have an impact/index.html
new file mode 100644
index 00000000000..e32d60c600e
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/If you want to have an impact/index.html
@@ -0,0 +1,368 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Humanizing Technology+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +The promise of technology, and of automation particularly, is that they can free people to do the things that people excel at by assuming the rote, repetitive tasks that are better suited to machines. That promise has largely gone unfulfilled, as the demands and structure of the modern workplace have instead compelled people to behave more like machines than like people: consider the assembly-line worker, the sysadmin on call, the siloed teams accepting input from and providing output to one another. Too often, technological work diminishes the humanity of those who do the work. One of the most exciting aspects of the DevOps movement is its power to affirm that humanity. + +This talk will focus on the potential of DevOps principles and practices to create environments where technology enriches not only organizations, but also the lives of their people. + +Speaker: +Speaker 11 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Insert Keynote Here/index.html b/static/events/2015-minneapolis/proposals/Insert Keynote Here/index.html
new file mode 100644
index 00000000000..d6dd7c10235
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Insert Keynote Here/index.html
@@ -0,0 +1,366 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+If you want to have an impact+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: +If you want to have an impact, DevOps is not enough. + + + + +Speaker: +Sara Cowles + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Lets Safety Dance/index.html b/static/events/2015-minneapolis/proposals/Lets Safety Dance/index.html
new file mode 100644
index 00000000000..0f0d2d933a4
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Lets Safety Dance/index.html
@@ -0,0 +1,378 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+[INSERT KEYNOTE HERE]+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +Abstract: DevOps is just one part of a bucket of "trends" you hear about in every keynote, the riders of the digital apocalypse. You've heard these talks: Software is eating the world! Cloud! Millennials! Mobile! DevOps! Change or die! You must buy our products! These trends are cast out as imperatives with little analysis of what they mean and if they're real. This talk looks at those keynote cliches and answers the question, "do I really need to do anything about them?" + +Speaker: +Speaker 9 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Magic Myth and the DevOps/index.html b/static/events/2015-minneapolis/proposals/Magic Myth and the DevOps/index.html
new file mode 100644
index 00000000000..aff36ba4a83
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Magic Myth and the DevOps/index.html
@@ -0,0 +1,368 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Let's Safety Dance+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +I hate computers. How many times have you heard those words? Or said them yourself. Systems crash and go boom all the time. The easiest thing to do is to blame the person touching the keyboard when it happens. Especially when that person touching the keyboard is you. But how do we build safer systems? How do we build humane systems, systems that actually engage and even delight the user? Sidney Dekker says "Safety improvements come from organizations monitoring the gap between procedures and practice". How can you build a system for safety if the way the system is designed isn't actually how it's used. Of course it doesn't work, you were doing it wrong. We have to stop shoving users into systems with procedures that aren't based on reality. + +In this talk I address these questions through my experience building tools for developers. Every tool works in an ideal world and on my machine. But the hard part is building tools that "work" even when they don't. Understanding the gap between procedure and practice can be a real challenge, and if you don't approach that problem with a big dose of empathy you won't have much luck closing that gap. + +Slides: + + + + +Video: + + + + +Speaker: +Andy Fleener + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Managing Your Mental Stack/index.html b/static/events/2015-minneapolis/proposals/Managing Your Mental Stack/index.html
new file mode 100644
index 00000000000..3a83a0d9aeb
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Managing Your Mental Stack/index.html
@@ -0,0 +1,368 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Magic, Myth, and the DevOps+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +"Once upon a time": powerful words that begin many oral narratives and indicate that the story to be told will be imbued with magic and myth. Organizational folklore can be a very powerful force for instilling or perpetuating behavior, systems, and culture within an organization. + +Too often, fear and negativity are the driving forces in the folklore behind many organizational traditions. A positive narrative that embraces the customs and traditions of a healthy, balanced feedback loop can help jumpstart your DevOps journey. This talk will help you frame your narrative alongside metrics and use folklore as a catalyst for positive change. + +Speaker: +Speaker 27 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Performance Metrics Driven Continuous Delivery/index.html b/static/events/2015-minneapolis/proposals/Performance Metrics Driven Continuous Delivery/index.html
new file mode 100644
index 00000000000..1c75e7ca709
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Performance Metrics Driven Continuous Delivery/index.html
@@ -0,0 +1,372 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Managing Your Mental Stack+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +It's information overload these days -- how can a technology professional manage to keep up with everything that is new and exciting in the world of DevOps? What are the best methods for absorbing content and developing skills? Just how useful are podcasts, anyway? + +In this talk (inspired by an episode of my [Podcast Name] podcast) I will share strategies for consuming information about techniques, concepts, and stories about DevOps. I will include practical methods for acquiring information, managing intake of blogs, articles, and studies, and absorbing and synthesizing this information in an applicable way. + +Speaker: +Speaker 2 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Philosophy of Configuration Management/index.html b/static/events/2015-minneapolis/proposals/Philosophy of Configuration Management/index.html
new file mode 100644
index 00000000000..89690536181
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Philosophy of Configuration Management/index.html
@@ -0,0 +1,366 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Performance Metrics Driven Continuous Delivery+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +As organizations move towards implementing DevOps related concepts one of the building blocks is typically a Continuous Integration and Continuous Delivery pipeline. Traditional processes revolve around simple functional tests with Boolean pass/fail and do not encompass non-functional elements. This can result in more rollbacks as code is deployed that may be functionally sound but unstable or non-performant. + +In this talk we will show you how to automatically capture and report on key performance and scalability metrics (such as # of SQL Queries, time spent in components, # of resources on a page) through every stage of your deployment pipeline. + +Tracking these metrics across all stages and comparing them between builds will help ensure higher quality releases and ensure something like a database killing bug does not make it all the way into production! + +Less time spent rolling back suboptimal releases means more time spent delivering new features and happier customers. + +Speaker: +Speaker 19 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Putting the R in Sports/index.html b/static/events/2015-minneapolis/proposals/Putting the R in Sports/index.html
new file mode 100644
index 00000000000..04ad528cc68
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Putting the R in Sports/index.html
@@ -0,0 +1,378 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Philosophy of Configuration Management+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +Dive into the theories behind a system of profound knowledge, how one can build positive interactions, develop and understand flow and see the very foundations of what we call devops. I would talk about how to think through reliability, systems and human interactions and show how wrapping all of this together gives people the power to probe, sense, act and respond and managers & employees the tools they need to build a system of profound knowledge. This knowledge can then be codified, iterated and experimented with and the process of human management can be closely aligned with systems management to make both flexible and aware of each others requirements and easily communicated. + +Speaker: +Speaker 5 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Rolling Your Own vs SaaS/index.html b/static/events/2015-minneapolis/proposals/Rolling Your Own vs SaaS/index.html
new file mode 100644
index 00000000000..94b596a229f
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Rolling Your Own vs SaaS/index.html
@@ -0,0 +1,376 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Sports Stats 101+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +I love sports and my Dad loves programming. Our compromise is learning statistics with computers. In this presentation I will share what I learned about statistics working with all sorts of sports data. + +Slides: + + + + ++ + Video: + + + + +Speaker: +Daniel Willis + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Saved or Sabotaged/index.html b/static/events/2015-minneapolis/proposals/Saved or Sabotaged/index.html
new file mode 100644
index 00000000000..93b0c4a2c43
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Saved or Sabotaged/index.html
@@ -0,0 +1,384 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Rolling Your Own vs SaaS: Tradeoffs & Considerations+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Description + +At Bloom Health, we're operating in a highly regulated environment (including HIPAA & PII) while at the same time running our infrastructure in public cloud. This leads to a number of considerations and tradeoffs when choosing the various parts of our stack. I'll detail the considerations we've undertaken, the compromises and winding paths towards workable solutions, and the specific technologies we've found work better for us as in-house solutions versus those where we've found SaaS to be the optimal (or at least acceptable) choice. + +Slides: + + + + +Video: + + + + +Speaker: +Colleen Velo + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Shedding the Stigmas of Golden Images/index.html b/static/events/2015-minneapolis/proposals/Shedding the Stigmas of Golden Images/index.html
new file mode 100644
index 00000000000..daec3e53fad
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Shedding the Stigmas of Golden Images/index.html
@@ -0,0 +1,377 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Saved or Sabotaged? Seven Deadly Wastes in Your DevOps Practice+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +Every software development organization on the planet has a software supply chain that is consuming a massive volume of open source and third-party components at extremely high velocity. To provide a much clearer perspective to this volume and velocity, we can see that a global population more than 11 million developers consumed over 20 billion components in 2014. + +Those in DevOps who have pursued improved visibility, supplier choices, and control mechanisms across their software supply chains have boosted developer productivity by 15%, crumbled mountains of technical debt, and shifted millions of dollars from sustaining operations to accelerating innovation. + +Yet the vast majority of organizations developing software are blind to their free-for-all consumption volume, patterns, and velocity. Their software supply chain practices are silently sabotaging efforts to accelerate development, improve efficiency and maintain quality. + +In May, I authored the 2015 State of the Software Supply Chain Report. It is a quantitative analysis of more than 160,000 software development organizations consuming billions of open source and third-party software components from over 15,000 suppliers. Your organization is most likely among those I analyzed. + +While the average organization in the study consumed 240,000 open source and third party software components in 2014, the study revealed evidence of seven deadly wastes in their operations: (1) inefficient software sourcing practices, (2) building in outdated software components, (3) using redundant software components, (4) bypassing quality control mechanisms, (5) extending build times, (6) limiting traceability, and (7) electively sourcing software with known security vulnerabilities or risky license types that result in unplanned rework. + +These practices have resulted in: + +An average of 27 versions of software components consumed, meaning development teams are electively building in outdated parts and creating mountains of technical debt + +An average of 15,337 components consumed included known security flaws, impacting the integrity of operations + +Over 30 days of build time wasted annually as a result of poor sourcing practices + +But this discussion is not intended to simply shed light on bad practices, it is about learning. Attendees will gain new visibility as to what’s happening in their own software supply chains, how to avoid the seven deadly wastes, and how leading organizations like eBay, ServiceNow, Blackboard, Aetna, the US Air Force, Federal Reserve and Department of Homeland Security are applying proven supply chain principles from other industries toward improving their DevOps practices. + +Speaker: +Speaker 34 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Simplifying Cloud Template Management Using Packer/index.html b/static/events/2015-minneapolis/proposals/Simplifying Cloud Template Management Using Packer/index.html
new file mode 100644
index 00000000000..d87c2601b7c
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Simplifying Cloud Template Management Using Packer/index.html
@@ -0,0 +1,367 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Shedding the Stigmas of Golden Images+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +Description + +It's time to bring golden images to the new age of automation. Using new tools, it is possible to automatically create golden images on top of configuration management best practices. Not only is this possible for a single platform, but for multiple platforms (AWS, VMware, OpenStack, etc.) all at the same time. Unlock new potential, increase organizational agility, and improve system stability. + +Abstract + +Golden images have been thrown to wayside in the past few years in favor of using configuration management tools on top of clean OS installations. Historically, golden images have been tedious to maintain, slow to create, and represented archaic operations practices. + +But golden images also offer a variety of benefits. Instead of waiting 10 to 30 minutes for configuration management to complete on a new server, you can have a new server up and running in seconds. You can comprehensively test golden images before deploying them to production and confidently know that production will have stable configurations. Instead of manually building development environments, you can give developers golden image virtual machines, getting their development environments up and running in seconds. The list goes on. + +It is time to bring golden images to the new age of automation. Using new tools, it is possible to automatically create golden images built on top of configuration management best practices. And not only is this possible for a single platform, but for multiple platforms (AWS, VMware, OpenStack, etc.) all at the same time. Generate development images for VMware identical to production images that run in AWS. And do it all quickly, automatically, and using pre-existing configuration management scripts. Speaker: +Speaker 1 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Stop Blogging About Women In Tech/index.html b/static/events/2015-minneapolis/proposals/Stop Blogging About Women In Tech/index.html
new file mode 100644
index 00000000000..09c3c1d0dcd
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Stop Blogging About Women In Tech/index.html
@@ -0,0 +1,369 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Simplifying Cloud Template Management Using Packer+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +While installing OpenStack or CloudStack is a fairly simple prospect, the promise of cloud efficiency comes from a viable template +management process. Creating the first template, or attempting to migrate existing VMs into that new cloud can be quite problematic. In this session we'll learn how Packer plugins can be used to both create that initial set of templates, and to clone existing VMs into the cloud. When cloning existing VMs, a process will be presented where users aren't impacted when migrating existing functionality to a cloud. + +Speaker: +Speaker 25 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Testing in an Agile DevOps World/index.html b/static/events/2015-minneapolis/proposals/Testing in an Agile DevOps World/index.html
new file mode 100644
index 00000000000..4569f4793dc
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Testing in an Agile DevOps World/index.html
@@ -0,0 +1,382 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Stop Blogging About Women In Tech+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +Stop blogging about women in tech; start doing something about it. + + + + +Speaker: +Jenna Pederson + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/The 10 Myths of DevOps/index.html b/static/events/2015-minneapolis/proposals/The 10 Myths of DevOps/index.html
new file mode 100644
index 00000000000..efb467bdea1
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/The 10 Myths of DevOps/index.html
@@ -0,0 +1,366 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Testing in an Agile DevOps World+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +Type:Moderated General Discussion + +Description: + +This session would focus on how testing changes in an agile DevOps world.Discussion points would include: + + What is the best combination of white box, grey box, and black box testing?
+ Should there be separate test teams and what testing should they own?
+ Is there still a concept of System Test in an Agile DevOps world? I would provide the following to start the discussion: + Generally accepted definitions of white box, grey box, and black box testing + Working models of agile testing in a DevOps world (a couple of views that can be discussed) + Breakdown of what is typically done during System Test so we can discuss what is still needed + Breakdown of the other type of testing (Accessibility, Usability, Performance, and so on) so we can discuss when and how this should be done + +Speaker: +Speaker 18 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/The Emergence of ChatOps/index.html b/static/events/2015-minneapolis/proposals/The Emergence of ChatOps/index.html
new file mode 100644
index 00000000000..a97df7fea26
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/The Emergence of ChatOps/index.html
@@ -0,0 +1,376 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+The 10 Myths of DevOps+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +Although not officially coined until 2009, DevOps ideals have been explicitly discussed since at least 2006. Recently, however, the term "DevOps" has gained increasing popularity across a variety of fields and industries. DevOps is not a development methodology or technology; DevOps is an ideology. It is a way to facilitate organizational prosperity and growth while increasing each individual employee's happiness along the way. As DevOps has gained in prominence, a gap has been created between the original definition of DevOps and this new "enterprise-ready" buzzword. I present to you the 10 Myths of DevOps! + +Speaker: +Speaker 1 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/The Five Love Languages of DevOps/index.html b/static/events/2015-minneapolis/proposals/The Five Love Languages of DevOps/index.html
new file mode 100644
index 00000000000..2106a2b00b2
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/The Five Love Languages of DevOps/index.html
@@ -0,0 +1,372 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+The Emergence of ChatOps+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +The Emergence of ChatOps + +Slides: + + + + +Video: + + + + +Speaker: +Jason Hand + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/The Hello World of DevOps/index.html b/static/events/2015-minneapolis/proposals/The Hello World of DevOps/index.html
new file mode 100644
index 00000000000..fa5c9382f2e
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/The Hello World of DevOps/index.html
@@ -0,0 +1,370 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+The Five Love Languages of DevOps+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +The title of this session is inspired by the self-help book The Five Love Languages by Gary Chapman, but the similarities end there. When we are working to bring about cultural change in our organization, it's essential for us to understand that not everyone speaks the same "language" of DevOps as we do. The CFO has different drivers and communication style than your friend in the QA department, who is still different than the DBA in that remote office. In this talk, I will work to help provide techniques and strategies for identifying the drivers of your peers and decision-makers. We will talk about beliefs, perceptions, and communication styles, all with the express intent of helping YOU drive home the value of the DevOps philosophies and work-practices to make your organization succeed! + +Content will include a discussion of the DiSC model, as well as discerning drivers for different individuals to adjust the conversation. + +The DiSC model provides a common language that people can use to better understand themselves and to adapt their behaviors with others. The four areas of DiSC are Dominance, Influence, Steadiness, and Conscientiousness. + +Approximately 25% of the talk will be background on DiSC and methods for identifying the communication styles of others. 25% will be based upon identifying drivers of example roles in an organization (finance, product, tech ops, etc), and the remaining will be focused on use cases and strategies for applying this skill towards organizational change. + +Speaker: +Speaker 2 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/The New New Software Development Game/index.html b/static/events/2015-minneapolis/proposals/The New New Software Development Game/index.html
new file mode 100644
index 00000000000..ac9afa7abcc
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/The New New Software Development Game/index.html
@@ -0,0 +1,375 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+The 'Hello, World' of DevOps+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +we talk about DevOps as a process of dissolving organizational silos. We also focus a lot on automation. Both of these activities require a lot of time and energy. Are they absolutely necessary prerequisites? Can we do DevOps across silos, or even across company boundaries? What is the 'Hello, World' of DevOps? Is it possible to do anything useful without significant investment in organizational redesign and system retooling? + +This talk will tackle this question in simple, concrete terms by presenting a DevOps transformation case study from 2004. This case study involves a highly dysfunctional relationship between a SaaS provider and its outsourced hosting vendor. It describes the simple transformation that repaired that relationship, and allowed the client to dramatically increase the quality of their service as well as their satisfaction with their vendor. + +The talk will conclude by describing precisely what it was about the repair process that led to success. It will illustrate the difference between healthy and dysfunctional inter-organizational relationships. It will explore ways that any IT organization, regardless of its structure, can begin to reap the benefits of DevOps. + +Speaker: +Speaker 10 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/The donkeys are coming/index.html b/static/events/2015-minneapolis/proposals/The donkeys are coming/index.html
new file mode 100644
index 00000000000..c80554b2f84
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/The donkeys are coming/index.html
@@ -0,0 +1,366 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+The New New Software Development Game+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +We spent a lot of time over the last decade talking about teams, stories, and WIP. We laid the groundwork for a big change in the way software is developed. Now is the time to change the conversation – from process to technology. We agree that we must dramatically shorten the feedback loop from idea to outcome – but how? + +It’s time to focus on the tools and techniques that make it possible for small teams to deploy small changes to large systems very rapidly and very safely. Consider architecture: we are learning how to break monolithic systems into micro services – small, independently deployable components. Look at packaging: we now have standard containers that move freely across environments. Examine reliability: contract tests have proven effective at isolating the impact of component changes. + +In the end the important question is: How long does it take you to deploy a single line a code, learn something useful, and act on the information? + +Video: + + + + +Speaker: +Mary Poppendieck + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/They Dont Call it Continuous Integration for Nothing/index.html b/static/events/2015-minneapolis/proposals/They Dont Call it Continuous Integration for Nothing/index.html
new file mode 100644
index 00000000000..b18175cffb1
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/They Dont Call it Continuous Integration for Nothing/index.html
@@ -0,0 +1,367 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+The donkeys are coming!+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +DevOps is growing in popularity and even usage in "the real world." It seems like we're slowly getting past unicorns only and seeing many "horses" do DevOps. Soon we'll see the mainstream market - the "donkeys" - start to pick it up and bend DevOps to its will. This talk will go over "the state of the union" of DevOps and provide some guidance for how to prepare for the donkey apocalypse. + +Speaker: +Speaker 9 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Vulnerability/index.html b/static/events/2015-minneapolis/proposals/Vulnerability/index.html
new file mode 100644
index 00000000000..d78aeba9c13
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Vulnerability/index.html
@@ -0,0 +1,369 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+They Don't Call it Continuous Integration for Nothing!+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +This talk will dig deep into the process of continuous integration (CI) and the key processes that make up the overall CI process. We will discuss the relationships and process flows between change management, configuration management, and release/build management and how the CI process, when coupled with a solid performance engineering discipline across the product lifecycle, can result in a better user experience for your web & mobile application. We will speak about the entire lifecycle, the "conveyor belt" of the application lifecycle, with concentration on the "Big 3" processes that support the overall CI strategy. Speaker: +Speaker 12 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Why orchestration tools should understand your app/index.html b/static/events/2015-minneapolis/proposals/Why orchestration tools should understand your app/index.html
new file mode 100644
index 00000000000..3849fdac517
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Why orchestration tools should understand your app/index.html
@@ -0,0 +1,366 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Vulnerability+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +With learning and empathy being critical tenets of a healthy DevOps environment, you need to be vulnerable. Being vulnerable allows you to show that you are not perfect, and the rest of your team will feel safe to share successes and failures more freely. This attitude needs to flow to your whole life. + + + + +Speaker: +Larye Pohlman + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/Why you should care about DevOps in the public sector/index.html b/static/events/2015-minneapolis/proposals/Why you should care about DevOps in the public sector/index.html
new file mode 100644
index 00000000000..a49f7aff9e0
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/Why you should care about DevOps in the public sector/index.html
@@ -0,0 +1,381 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Why orchestration tools should understand your app+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +Configuration management tools have made it possible to manage complex distributed applications. Their power can be further enhanced with a model of the application architecture. Benefits of a model based tool include ease of use, increased safety, consistency of what is managed, rich functionality, and many more we will discuss during this session. We will walk you through how we manage a large-scale, distributed system in AWS using a single, model-based tool. + +Speaker: +Speaker 28 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/You Me and StatsD/index.html b/static/events/2015-minneapolis/proposals/You Me and StatsD/index.html
new file mode 100644
index 00000000000..6fb548f2446
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/You Me and StatsD/index.html
@@ -0,0 +1,379 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Why you should care about DevOps in the public sector+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +The IT community in the public sector has a sizeable, but frequently forgotten influence on peoples lives. Have you tried to renew a license plate online recently? How about navigated https://www.healthcare.gov/ to get health insurance? Used online learning tools for a public educational institution? Have any of these experiences been pleasant, or what you would expect from a well run modern website? These websites are your tax dollars at work. +Are there reasons why we maybe aren't seeing the cultural ideas of DevOps reaching public sector IT shops as quickly? + +Public sector organizations differ greatly from private sector organizations with regards to structure, motivations and funding. Other factors such as government mandates for the existence of these organizations, tenured employees and reliance on antiquated domain specific applications can exacerbate the issues caused by these differences. + +In the past year or so, we've seen how the discussions around DevOps in enterprise organizations have opened up discussion of many of these cultural ideas to more traditional corporate settings. For DevOps ideas to gain influence the thousands of public sector IT workers, we need to recognize that they too have a separate subset of problems and challenges and start a conversation about how to tackle these issues. This talk will seek to begin that conversation, explain some of the cultural differences between the public and private sectors, explain some of the challenges the public sector faces when trying to break down silos and explain why and how we should evangelize to public sector employees. + +Slides: + + + + +Video: + + + + +Speaker: +Joshua Zimmerman + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/index.html b/static/events/2015-minneapolis/proposals/index.html
new file mode 100644
index 00000000000..8c31bf543bc
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/index.html
@@ -0,0 +1,265 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+You, Me & StatsD+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +"Maybe we have too many metrics" ~ said nobody. + +Biz team wants revenue. Devs want key method call times. Ops want response times and throughput. + +We ALL want metrics, but instrumenting, viewing and monitoring these metrics normally involves a stack of tools, tons of coordination and worries about overhead. + +Until now. + +Let's spend 5 minutes and explore StatsD, an open-sourced network daemon that listens, collects and aggregates statistics for backend services. We'll take a quick look at what StatsD can collect, what a typical StatsD stack looks like - and a little bit about how teams can leverage StatsD to instrument (all the things). + +Walk away with a great head start on a technology you've heard a lot about - but haven't had the chance to explore. + + + + +Speaker: +Mark Morris + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/linux command-fu for developers/index.html b/static/events/2015-minneapolis/proposals/linux command-fu for developers/index.html
new file mode 100644
index 00000000000..2abf6096ded
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/linux command-fu for developers/index.html
@@ -0,0 +1,366 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Minneapolis 2015 + - proposals+
+
+
+Gold Medal sponsors+ +
+
+
+
+
+
+
+
+
+This page lists the proposals we have received. Help the presenters with your feedback! + +Conference Talks+ + +
Ignite Talks+ + +
+
+
+
+
+
+
+
+
+ 
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
++ + Silver Lake sponsors+ + +
+
+
+
+
+
++ + Stone Arch sponsors+ + +
+
+
++ + Media sponsors+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/static/events/2015-minneapolis/proposals/not all devops luminaries/index.html b/static/events/2015-minneapolis/proposals/not all devops luminaries/index.html
new file mode 100644
index 00000000000..7b721746dfd
--- /dev/null
+++ b/static/events/2015-minneapolis/proposals/not all devops luminaries/index.html
@@ -0,0 +1,371 @@
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+linux command-fu for developers+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +As a developer, for years I wrote code in a graphical IDE on Windows or a Mac. I have written hundreds of thousands of lines likely to only click a button to compile, build, deploy locally or even push to repositories. Coming from the development side of the house I regularly feel like a fraud when working with the system. I have had this feeling before, since I didn't study computer science in school. I will cover techniques I used to ramp up quickly on system commands and string together my favorite commands to understand a system quickly. Even experienced system admins will likely get an interesting tidbit or 2. + +Speaker: +Speaker 31 + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+not all devops luminaries+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abstract: + +A far-reaching and thought-provoking closing keynote by an early influencer in the devops movement. + +Video: + + + + +Speaker: +Andrew Clay Shafer + +
+
+
+
+
+
+
+blog comments powered by Disqus
+
+
+
++
+
+
+
+
+
+
+
+
+
+
+
+ Past+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Future+
+
+
+
+
+
+ |
