Day 2
+Wednesday, April 27th, 2016
+
+ by Jeff Bragdon and Anton Ouzounov +
+
+
+ + Affecting Change in Your Organization – Being an Agent of Change +
+ by Josh Goldman +
+ +
+ Critical Incident? WTF (What’s the format)? - Minimum Viable Runbooks +
+ by Will La +
+ +
+ Driven Off a Cliff: the Effects of Tool-Driven Architecture
-
-
+ Are YOU the Change Agent your Organization is Looking For…? +
+ by Drew Nienaber -
Open Space Opening
Open Space Opening
Open Space #1
Open Space #1
Open Space #2
Open Space #2
Open Space #3
Open Space #3
Conference Talks
- -TBD - need to create a template/shortcode for finding all the proposals diff --git a/content/events/2016-atlanta/propose.md b/content/events/2016-atlanta/propose.md index 8f37d5b2284..0c2b2c27918 100644 --- a/content/events/2016-atlanta/propose.md +++ b/content/events/2016-atlanta/propose.md @@ -1,6 +1,4 @@ +++ -City = "Atlanta" -Year = "2016" date = "2016-03-06T22:47:24-06:00" title = "propose" type = "event" diff --git a/content/events/2016-atlanta/registration.md b/content/events/2016-atlanta/registration.md index 74f6cdcbc57..ad89921763c 100644 --- a/content/events/2016-atlanta/registration.md +++ b/content/events/2016-atlanta/registration.md @@ -1,6 +1,4 @@ +++ -City = "Atlanta" -Year = "2016" date = "2016-03-06T21:28:23-06:00" title = "registration" type = "event" diff --git a/content/events/2016-atlanta/sponsor.md b/content/events/2016-atlanta/sponsor.md index f88b59ac369..7bb4ef0d8b2 100644 --- a/content/events/2016-atlanta/sponsor.md +++ b/content/events/2016-atlanta/sponsor.md @@ -1,50 +1,90 @@ +++ -City = "Atlanta" -Year = "2016" date = "2016-03-06T21:17:14-06:00" title = "sponsor" type = "event" +++ + We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}]. -+
+ +DevOpsDays is a self-organizing conference +for practitioners that depends on sponsorships. +We do not sell product presentations +or distributee attendee contact lists. +Sponsors have the opportunity for +short elevator pitches during the program, +recognition on the website, +and social media before, during, and after the event. -DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session. -
-Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees. -
+Sponsors are encouraged to represent themselves by actively participating +and engaging with the attendees as peers. +Any attendee has the opportunity +to demo products/projects as part of an open space session. +All attendees are welcome to propose any subject they want during the open spaces, +but this is a community-focused conference, +so heavy marketing will probably work against you when trying to make a good impression on the attendees. The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms. -
-
- -
diff --git a/content/events/2016-atlanta/welcome.md b/content/events/2016-atlanta/welcome.md index a6b3a81e0ef..d4ed2dee4a4 100644 --- a/content/events/2016-atlanta/welcome.md +++ b/content/events/2016-atlanta/welcome.md @@ -1,6 +1,4 @@ +++ -City = "Atlanta" -Year ="2016" date = "2016-03-06T21:15:25-06:00" title = "welcome" type = "event" @@ -11,45 +9,49 @@ aliases = ["/events/2016-atlanta"] ## {{< event_start >}} - {{< event_end >}} -DevOps Days is coming to Atlanta! -
+ "There ain't no revolution, only evolution, but every time I'm in Georgia I 'eat a peach' for peace."
+
+ - Dwayne Allman
+
+ Full Agenda
+
+Putting the Service in Microservices
+by author & consultant Jeff Sussna
+
+Burnout
+by Docker Evangelist & DevOps Pioneer John Willis
+
Register Now
+ +| Dates | -{{< event_start >}} - {{< event_end >}} - | ||
| {{< event_link page="location" text="The Historic Academy of Medicine at Georgia Tech">}} | +|||
| Sponsors | -{{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to attract new talent and promote your organization. | +If your organization is interested in sponsoring Atlanta 2016, please {{< event_link page="sponsor" text="email us" >}}. | |
| Contact | -{{< event_link page="contact" text="Get in touch with the Organizers" >}} | +Questions? | +{{< event_link page="contact" text="Email the Organizers" >}} |
| - | - {{< event_twitter devopsdaysatl >}} - | + +
diff --git a/data/events/2016-atlanta.yml b/data/events/2016-atlanta.yml index 3484bed8b08..65cd88b4a40 100644 --- a/data/events/2016-atlanta.yml +++ b/data/events/2016-atlanta.yml @@ -1,48 +1,80 @@ -name: 2016-atlanta # The name of the event. Four digit year with the city name in lower-case, with no spaces. +name: "2016-atlanta" # The name of the event. Four digit year with the city name in lower-case, with no spaces. year: 2016 # The year of the event. Make sure it is in quotes. city: "Atlanta" # The city name of the event. Capitalize it. friendly: "2016-atlanta" # Four digit year and the city name in lower-case. Don't forget the dash! status: "past" # Options are "past" or "current". startdate: 2016-04-26 # The start date of your event, in YYYY-MM-DD format. Leave blank if you don't have a date yet. enddate: 2016-04-27 # The end date of your event, in YYYY-MM-DD format. Leave blank if you don't have a date yet. -cfp_date_start: 2016-04-01 -cfp_date_end: 2016-05-01 -cfp_date_announce: 2016-05-07 +cfp_date_start: 2016-01-25 +cfp_date_end: 2016-03-01 +cfp_date_announce: 2016-03-07 coordinates: "30.2500, -97.7500" # The corrodinates of your venue. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html location: "Georgia Tech Historic Academy of Medicine" # The name of your location -navigationelements: ["welcome", "contact", "location", "program", "propose", "proposals", "registration", "conduct", "sponsor"] # List of pages you want to show up in the navigation of your page. Remove any that aren't relevent yet. -team: ["Tom Hall", "John Dyer", "Ian Buchanan", "Laura Little", "Chris Corriere"] + + +nav_elements: # List of pages you want to show up in the navigation of your page. + - name: welcome + - name: location + - name: program + - name: registration + url: https://www.eventbrite.com/e/devopsdaysatl-tickets-21363190879 + - name: sponsor + - name: contact + - name: conduct + +# These are the same people you have on the mailing list and Slack channel. +team_members: # Name is the only required field for team members. + - name: "Tom Hall" + - name: "Ian Buchanan" + - name: "John Dyer" + - name: "Chris Corriere" + - name: "Laura Little" + - name: "John Vincent" + - name: "Parker DeBardelaben" organizer_email: "organizers-atlanta-2016@devopsdays.org" # Put your organizer email address here proposal_email: "proposals-atlanta-2016@devopsdays.org" # Put your proposal email address here sponsors: # List all of your sponsors here along with what level of sponsorship they have. - - id: chef + - id: versionone level: gold - id: pivotal level: gold - - id: versionone + - id: victorops + level: gold + - id: sumologic level: gold - id: redislabs level: gold - - id: victorops + - id: coxautomotive level: gold - - id: autotrader + - id: chef level: gold - - id: sumologic + - id: pindrop + level: gold + - id: newrelic + level: gold + - id: datalex level: gold - id: mailchimp level: silver + - id: tropo + level: silver - id: salesforcepardot level: bronze - id: careerbuilder level: bronze + - id: blacksintechnology + level: media - id: arresteddevops level: media - - id: oreilly + - id: sonatype level: media - - id: blacksintechnology + - id: devopsdotcom level: media - - id: upguard - level: badges + - id: pindrop + level: eveningevent + - id: cprime + level: wireless + sponsor_levels: # In this section, list the level of sponsorships and the label to use. - id: gold label: Gold @@ -52,5 +84,7 @@ sponsor_levels: # In this section, list the level of sponsorships and the label label: Bronze - id: media label: Media - - id: badges - label: Badges + - id: eveningevent + label: Evening Event + - id: wireless + label: Wireless diff --git a/data/sponsors/coxautomotive.yml b/data/sponsors/coxautomotive.yml new file mode 100644 index 00000000000..2f74272a7b8 --- /dev/null +++ b/data/sponsors/coxautomotive.yml @@ -0,0 +1,2 @@ +name: coxautomotive +url: https://jobs.coxautoinc.com/ diff --git a/data/sponsors/cprime.yml b/data/sponsors/cprime.yml new file mode 100644 index 00000000000..ce927b841d8 --- /dev/null +++ b/data/sponsors/cprime.yml @@ -0,0 +1,2 @@ +name: cprime +url: https://www.cprime.com diff --git a/data/sponsors/datalex.yml b/data/sponsors/datalex.yml new file mode 100644 index 00000000000..00c37768506 --- /dev/null +++ b/data/sponsors/datalex.yml @@ -0,0 +1,2 @@ +name: datalex +url: http://www.datalex.com diff --git a/data/sponsors/devopsdotcom.yml b/data/sponsors/devopsdotcom.yml new file mode 100644 index 00000000000..ed41c98eeea --- /dev/null +++ b/data/sponsors/devopsdotcom.yml @@ -0,0 +1,2 @@ +name: devopsdotcom +url: http://www.devops.com diff --git a/data/sponsors/pindrop.yml b/data/sponsors/pindrop.yml new file mode 100644 index 00000000000..99c0bdd96a2 --- /dev/null +++ b/data/sponsors/pindrop.yml @@ -0,0 +1,2 @@ +name: pindrop +url: http://www.pindrop.com diff --git a/data/sponsors/sonatype.yml b/data/sponsors/sonatype.yml new file mode 100644 index 00000000000..47760fef89c --- /dev/null +++ b/data/sponsors/sonatype.yml @@ -0,0 +1,2 @@ +name: "Sonatype" +url: "https://www.sonatype.com/" diff --git a/data/sponsors/tropo.yml b/data/sponsors/tropo.yml new file mode 100644 index 00000000000..a8559f01801 --- /dev/null +++ b/data/sponsors/tropo.yml @@ -0,0 +1,2 @@ +name: tropo +url: https://www.tropo.com diff --git a/static/events/2016-atlanta/logo.png b/static/events/2016-atlanta/logo.png index a30d38a2bc5..84e3c6d8bfe 100644 Binary files a/static/events/2016-atlanta/logo.png and b/static/events/2016-atlanta/logo.png differ diff --git a/static/events/2016-atlanta/proposals/Building an End to End Windows or Linux Application Deployment Pipeline/index.html b/static/events/2016-atlanta/proposals/Building an End to End Windows or Linux Application Deployment Pipeline/index.html new file mode 100644 index 00000000000..a4e01194ac1 --- /dev/null +++ b/static/events/2016-atlanta/proposals/Building an End to End Windows or Linux Application Deployment Pipeline/index.html @@ -0,0 +1,364 @@ + + + + + +
+
+ 
+ Home
+ |
+
+ 
+ Contact
+ |
+
+ 
+ Events
+ |
+
+ 
+ Presentations
+ |
+
+ 
+ Blog
+ |
+
Building an End to End Windows or Linux Application Deployment Pipeline
+
+
+
+
+
+We would like to share our journey towards an OS Agnostic fully automated application deployment pipeline. Our proposal would take our audience through our trial and error, how we chose our tools, how we geared those tools, and were we are headed in the future. As a sample, we would cover things like; Arriving at the conclusion that most DevOps groups focus on a handful of programming languages specific to a single OS. In contrast, CareerBuilder has applications built on both Rails and .NET. Therefore we needed a solution that satisfies both sets of requirements. We also learned that not many examples exist for Windows based deployment pipelines leveraging .Net. Most examples are geared towards Linux and a language like Rails or Node.JS. Even with all available information, it is not easy to create a serviceable solution that supports all language and OS requirements within a single gitflow framework.
+ +Speaker: +Jeff Bragdon
+ ++
Past
+Future
++
|
+
+ Home
+ |
+
+
+ Contact
+ |
+
+
+ Events
+ |
+
+
+ Presentations
+ |
+
+
+ Blog
+ |
+
Developing and Operating an Enterprise Application as a 12Factor App using Docker and Amazon Web Services
+
+
+
+
+
+An application that follows the principles of the 12 Factor results in highly scalable, portable, disposable and manageable deployment. However, making a large scale enterprise or business application into a 12 Factor App is a non-trivial exercise. The technical aspects outlined below are keys to developing and operating a large scale enterprise application as a 12 Factor App:
+ +· Componentization:
+ +o How Spring Boot and microservices architecture could play a big role in breaking a larger monolithic application into finer grained components
+ +o How these finer grained components could be developed, tested and versioned independently
+ +o How Spring Cloud and Netflix libraries could be leveraged to build the plumbing around these microservices components that can provide the binding features such as service look ups, load balancing, graceful failure handling and dynamic routing of requests across these components
+ +o What role unit testing and JUnit frameworks could play to ensure that the developed code is well tested before it reaches the version control system
+ +· Containerization:
+ +o How Docker could be leveraged to build, deliver and deploy the component images with consistent naming and versioning schemes.
+ +o How containerization could help encapsulate the technology stack and application configuration nuances
+ +o How containerization could help us optimize our applications for cross-platform deployments (cloud or on-premise)
+ +· Continuous Integration:
+ +o How a Continuous Integration and Continuous Delivery platform can be built for thoroughly testing microservices components
+ +o Frequency and scheduling of different phases of testing and verification (functional, performance, upgradability and user acceptance) before code can be promoted to staging and production environments
+ +o How CI/CD platform can help developers find the defects in minutes after development
+ +· Cloud Runtime:
+ +o How Amazon Cloud Formation and EC2 Container Service (ECS) can be leveraged to run, scale and manage microservice components on EC2
+ +o How to enable frequent, independent and zero-downtime upgrades of the deployed components
+ +o How to keep the application source-code completely agnostic of the underlying cloud platform such as AWS
+ +My presentation/talk would primarily focus on these four topics and will discuss how an organization can manage getting the developers and deployment engineers work in unison to create a consistent environment for development, testing and production.
+ +Speaker: +Kartik Pandya
+ ++
Past
+Future
++
|
+
+ Home
+ |
+
+
+ Contact
+ |
+
+
+ Events
+ |
+
+
+ Presentations
+ |
+
+
+ Blog
+ |
+
Don’t hit it with a pretty stick: LeanUX Methods for Agile Teams
+
+
+
+
+
+UX is seen as a bottleneck and/or creates lots of rework for Agile teams. I’ll discuss how you can incorporate LeanUX principles within your Agile teams to enable collaboration and continuous learning about your product.
+ +I’ll discuss sharing the design process with the entire team, covering the basics of customer research, interviewing, and how to create lean personas for hypothesis validation.
+ +Speaker: +Virginia Cagwin
+ ++
Past
+Future
++
|
+
+ Home
+ |
+
+
+ Contact
+ |
+
+
+ Events
+ |
+
+
+ Presentations
+ |
+
+
+ Blog
+ |
+
Frameworks for Feedback
+
+
+
+
+
+Code reviews, stand up, retros, and performance reviews — all acknowledge the importance of communication and feedback and they are good starts. But they don’t tell you how to give negative feedback or ensure that you, as a teammate or manager, hear the small things before they become big things.
+ +Let’s talk about feedback and examine frameworks for how to ask for and frame feedback effectively. Not all situations call for the same type of feedback and some are more sensitive than others. We will look at Non-violent communication, techniques from family and marriage therapy, as well as more traditional frameworks for feedback.
+ +Speaker: +Rebecca Miller-Webster
+ ++
Past
+Future
++
|
+
+ Home
+ |
+
+
+ Contact
+ |
+
+
+ Events
+ |
+
+
+ Presentations
+ |
+
+
+ Blog
+ |
+
From 0 to Hero: CareerBuilder DevOps Deployment Pipeline
+
+
+
+
+
+We would like to share our journey towards an OS Agnostic fully automated application deployment pipeline. Our proposal would take our audience through our trial and error, how we chose our tools, how we geared those tools, and were we are headed in the future. As a sample, we would cover things like; Arriving at the conclusion that most DevOps groups focus on a handful of programming languages specific to a single OS. In contrast, CareerBuilder has applications built on both Rails and .NET. Therefore we needed a solution that satisfies both sets of requirements. We also learned that not many examples exist for Windows based deployment pipelines leveraging .Net. Most examples are geared towards Linux and a language like Rails or Node.JS. Even with all available information, it is not easy to create a serviceable solution that supports all language and OS requirements within a single gitflow framework.
+ +Speaker: +Jeff Bragdon and Anton Ouzounov
+ ++
Past
+Future
++
|
+
+ Home
+ |
+
+
+ Contact
+ |
+
+
+ Events
+ |
+
+
+ Presentations
+ |
+
+
+ Blog
+ |
+
Putting the Service in Microservices
+
+
+
+
+
+Opening Keynote:
+ +Conway’s Law expresses Melvin Conway’s observation that we are doomed to design systems that mirror the shapes of our organizations. Forward-thinking companies like Amazon and Netflix use Conway’s Law to their advantage. They structure their organizations to reflect the kinds of systems they want to create by matching microservices architectures with so-called “2-pizza” micro-teams.
+ +Conway also, though, observed that designing a system is just the beginning; it also needs continual redesign. He stressed the importance of organizational flexibility to effective design. How can we achieve this flexibility without descending into re-org madness?
+ +This talk will explore the relationship between organizations and systems. It will delve more deeply into Conway’s original article, and introduce ‘Conway’s Corollary’. By connecting Conway’s work to ideas from service design and Promise Theory, it will present an approach that treats the design and operations of systems and organizations as continuous and inseparable.
+ +Speaker: +Jeff Sussna
+ ++
Past
+Future
++
|
+
+ Home
+ |
+
+
+ Contact
+ |
+
+
+ Events
+ |
+
+
+ Presentations
+ |
+
+
+ Blog
+ |
+
The Unrealized Role of Monitoring & Alerting
+
+
+
+
+
+In today's world, a company must be a "Learning Organization" in order to be successful and innovative. Learning from both failure and success, in order to implement small incremental improvements is critical. But until you implement and apply new information, you haven't truly "learned” anything and you certainly haven’t improved.
+ +According to the 2015 Monitoring Survey, most companies leverage metrics from monitoring and logging purely for performance analytics and trending. If high availability and reliability are important, they also leverage metrics to alert on fault and anomaly detection. Despite these “best practices”, the metrics are primarily only used as context to keep things “running” or return them back to "normal" if there’s a problem. Rarely is that data used as a method to identify areas of improvement once services have been restored. +When an outage occurs to your system, you will absolutely repair and restore services as best you know how, but are you paying attention to the data from the recovery efforts? What were operators seeing during diagnosis and remediation? What were their actions? What was going on with everyone, including conversations? A step-by-step replay of exactly what took place during that outage.
+ +This “old-view” perspective on the purpose of monitoring, logging, and alerting leaves the full value of metrics unrealized. It fails to address what’s important to the overall business objective and it lacks any hope of seeking out innovation or disruption of the status quo.
+ +This talk will illustrate how to identify if your company is making the best use of metrics and ways to not only learn from failure, but to become a "Learning Company".
+ +Speaker: +Jason Hand
+ ++
Past
+Future
++
|
+
+ Home
+ |
+
+
+ Contact
+ |
+
+
+ Events
+ |
+
+
+ Presentations
+ |
+
+
+ Blog
+ |
+
The test automation journey; a labor of love and where are we now?
+
+
+
+
+
+Test automation has long existed at Autotrader. In 2001, QA was using WinRunner. Along the way we've used, LoadRunner, JUnit and HTTPUnit, Selenium, WatiN, QTP, RFT, and A3, Today the foundation of test automation at Autotrader is TestNG, Selenium-WebDriver (Java client), Selenium Grid, BrowserStack, Jenkins, JIRA, and Xenon, an in house test results management tool. +The presentation will include a brief history of test automation at Autotrader.com from 2001 through 2016, the current state of test automation, our future direction and how test automation plays into the vision of continuous delivery going forward.
+ +Speaker: +Lee Blackburn, Chue Her, & Adrian Kosciak
+ ++
Past
+Future
++
|
+
+ Home
+ |
+
+
+ Contact
+ |
+
+
+ Events
+ |
+
+
+ Presentations
+ |
+
+
+ Blog
+ |
+
Two styles of Dev[o|O]ps
+
+
+
+
+
+Many teams and organisations say that they are pacticing Devops successfully, yet when we look there are big differences in organizational structure, team composition and culture. Broadly speaking, we can identify to main "styles" of Devops at present: "single-team Devops" and "two-team DevOps". We'll describe the two styles, benefits and disadvantages of both, and discuss how you can figure out which might be a better fit for your team and organization.
+ +Speaker: +Andrew Phillips
+ ++
Past
+Future
++
|
+
+ Home
+ |
+
+
+ Contact
+ |
+
+
+ Events
+ |
+
+
+ Presentations
+ |
+
+
+ Blog
+ |
+
Burnout
+
+
+
+
+
+Over the past few years, there seems to have been an increase in suicides in our sector of the IT industry. With complexity and responsibility ever increasing in the creation and support of digital services industries, we have seen a correlated increase in stress levels. We have come to know this as a term we call “Burnout.” Burnout was coined by German-American psychologist Herbert Freudenberger in 1974. The Japanese have a word for burnout that leads to death -- "karoshi." When suicide is involved they call it "karojisatsu." In this presentation, we are going to break down what we know about Burnout. We will look at some survey data and try to suggest some ways to achieve healthier outcomes for ourselves and our colleagues.
+ +Speaker: +John Willis
+ ++