Add an eventSessions at RailsConf 2012 about Deployment with video
Tuesday 24th April 2012
-
Taming the Kraken - How Operations enables developer productivity
Are you having trouble launching new features because of friction between development and operations? At CustomInk, we've reduced this friction by making changes to our teams, processes, and tools. Come find out what we've been up to and learn how you can implement similar changes in your own environment.
There's always a bit of tension when getting features from idea to production. In this talk, we'll look at some of the changes CustomInk has made to reduce this friction and keep the new features coming. Gone are the days of bi-monthly deploys, office pools dedicated to guessing when this deploy will be rolled back, and the ceremony surrounding the deploy-rollback-fix-deploy cycle. Today, ideas flow from product managers to developers to production with ease thanks to a number of changes that we've made to our teams, processes and tools.
During this talk, we'll look at:
- How product managers drive the release cycle
- Ideas and customer feedback
- Prioritizing development requests
- Managing branch merges and deployments (yes, product managers can help here!)
- How operations enables developer productivity
- Spinning up development environments - Vagrant, Chef
- Infrastructure Automation - Chef
- Enabling Continuous Deployment - Capistrano and caphub
- Failing gracefully - Fault-tolerant load balancing with ldirectord
- How developers get their code running in production
- Staging environments
- Continuous Integration - Jenkins, Green Screen
- Staying on topic: Deploying changes when they're ready
- Getting rid of the over-the-wall mentality - Dev & Ops working together
- Enabling developers to do it themselves
- Pair programing infrastructure automation
- Keeping the process light and the communication flowing
-
Stack Smashing
"Stack Smashing" refers to an internal project where I took our production Rails application environment down from over 100 virtual machines to 2 physical machines. Our application environment for Major League Gaming consists of 13+ inter-connected applications with millions of users to provide functionality such as single-sign on, online video (both video on demand and UGC), news and live competition information, photo galleries, profiles, and much more. We simply needed a simpler infrastructure in which to develop and deploy our applications. In this talk, we will cover the following:
- Network topology before and after, as well as the makeup of our virtual and physical machines.
- Detailed discussion of Chef recipes, NGINX, HAProxy configurations and updates to standard configurations.
- Application and service monitoring and configuration.
- Application migration from the old stack to the new stack.
- Rails 3 to Rails 3.1 upgrade insights.
- Unicorns!
- Strategies for service configuration to handle failure.
- Offline processing with queueing and queue management.
- Simplifying, standardizing and sexy-fying your Capistrano-based deployment tasks into a reusable gem.
- Behavior driven infrastructure monitoring and validation.
- Adopting an opt-in continuous deployment strategy that is integrated with our continuous integration environment.
This will be a very code and example-focused talk. Come and learn about the ways that you can simplify your existing infrastructure.
-
Zero downtime deploys for Rails apps
by Pedro Belo
What does it take to deploy an application without any downtime?
More than most Ruby developers would expect, turns out; what is aggravated by the lack of documentation and other resources on this topic.
In this talk we'll dive into both development practices (hot compatibility, database migrations, caching) and deployment setup (Heroku, Unicorn, HAProxy), covering everything you need to know in order to ship code without affecting a single customer.