DevOps Days Podcast

• How to make a shift from traditional model to DevOps? (Namrata Rao)• Repository as an deployment artifact (Inny So)• Developer Happiness at RedMart (Surya Dharma Tio)• DevOps and the CFO (Benjamin Henshall)

This is a story of an Infrastructure team at Zalora that implemented DevOps using Haskell and Nix.

The story is about:

• drowning in inherent complexity of existing Puppet configuration• establishing a functional programming community inside the company• implementing configuration management using purely-functional language and package manager Nix and using NixOS as the base OS• challenges of using new tools at scale• building cloud infrastructure tools using Haskell• building a code-driven deployment platform borrowing design practices from Erlang/OTP, Mesos and other successful distributed system frameworks, accommodating engineering team growth• overcoming adoption failures and finally reaching operational happiness

This presentation covers the current state of the Devops movement as presented by one of the original "Core Organizers" of the movement. The presentation will look at some of the taxonomies that have been used to describe Devops such as CAMS and ICE. It will also cover the recent 2015 Devops Survey and we will end up with a discussion about how Devops is being adopted in the enterprise.

At Viki, we run a number of micro services that process thousands of requests per second in various geographical regions. Micro service architecture helps us break down the complexity of building a large distributed system, but also introduces the complexity of debugging an issue.

This talk is about log processing at scale - building an Elasticsearch cluster that can handle tens of thousands of events per second from all levels of a micro-service container based architecture.

My first exposure to a DevOps Days was in 2010. I was an early adopter of most of the tools, took part in the heated iClassify debate, was contributing to Chef before it had a name, back when it was still a pet project at HJK Solutions.. As things evolved, we tried the offshoots that we hoped would fill the gaps.. MCollective, opscode-agent, but really we were just trading one problem for another..

DevOps Days was started in this gap, and over the years I have seen more and more vendor and product encroachment, and fewer people (especially outside of SF) who grasp the roots and the spirit out of which this event was born.

I will be talking about the original spirit of DevOps Days, which i feel started in 1942, and has mutated into a flavor specific to our modern world. I will not be discussing any vendor products, and this is not a sales pitch for anything.

• Sustainable Innovation - the Business Mantra for DevOps in Enterprise (Anoop Kumar Bhat)• The Power of Personal Influence (Kimble Ngo)• Agile: Break it down (Yue Lin Choong)• #noprojects (Evan Leybourn)• Crawl before you Run, Implementing DevOps (Jason Man)• Automated Docker Image Builds with Jenkins, Packer, and Kubernetes (Oyvind Roti)

We will share our success stories and lessons learned on working toward Continuous Delivery on a public facing web application for a popular website. This will cover Infrastructure Engineering, Build and Release Engineering, End to End Auditability and Tracability, 1 Click Application Deployments, and Security from the Infrastructure to the Application Workflow.

As service providers(Telco's) begin to transform their business to embrace Virtualization & Cloud ( ie SDN & NFV) their network operations/service delivery teams needs to evolve. While Virtualization & Cloud make it easy to rapidly expand the size of infrastructure, but the habits and practices they used in the past with hardware-based infrastructure don't keep up. The Network operations teams need to adopt IT’s DevOps practices to maximize the potential benefits of the evolving software-defined infrastructure. This includes adopting new tools that enhance agility, implementing agile operational and organizational models and procedures, and in some cases adopting a new culture. The benefits of such an approach are compelling: lower costs and increased agility, including the ability to implement new services in days rather than weeks or months

In this session, we will look at how to take advantage of technologies like cloud, virtualization, and configuration automation to manage IT infrastructure using patterns, practices, and ideas that have been adopted from software development, especially Agile concepts, and brought into the Network Operations world as part of the DevOps movement. Also, we will also go through the challenges and problems created by all these new tools, and the principles and mindset changes that a team needs to make to use them effectively.

There was a company which had typical long running releases and the business was not happy. Business wanted change but IT was not sure how to deliver. Then they heard about Agile. It looked like the magic potion to all their problems.They started doing Agile but it just meant more work for the team and a chaos during the last days of the sprint. Operations was still not happy. Then they heard about another magic potion called Devops, which forced them to think about continuous delivery. I'll talk about the various tools being used in order to bring about this change and what were the challenges that they faced in this journey.The talk has two dimensions: First, The tool chain and Second, how the team was convinced to hop on this journey of continuos delivery. Let me begin by saying that both of the points are equally important and correlated because convincing a team to change is very difficult if the tool selection is not right. I'll also get into a demo of the working pipeline using this toolset.

REA Group is the parent company of one of the most popular Australian websites - realestate.com.au.

Over the past 7 years REA Group has scaled from a 30 odd IT workforce to 200 across multiple locations.

From Waterfall to Agile. From archaic to an employer of choice.

Over my 7 years at REA we have lessons which I’d love to share on

• Hiring Operations and Developers• Getting Operations and Developers to collaborate• Optimising teams to be more effective• Overcoming cultural differences in a distributed team - particularly Asian and Western cultures• How to knowledge share technical information across the entire company