Yashasree barve power of dev ops - ai 2012 - 1.0-share

transcript

The power of DevOpsTransforming a big Enterprise group into a super agile one

Yashasree BarveTata Consultancy Services

About Me

Technologist @ TCS since last 14 years

An Agile Developer & Architect since 2007

I'm lovin' it

Agile India 2012 Presentation by Yashasree Barve

Not so long ago

There lived an Enterprise

An Enterprise with

Well Established Development Group

An Enterprise with

A well established Operations Group

with Well set processes

An Enterprise with

Well defined Environments

Brought us many advantages

• Happy Sponsors

• Great Return on Investment

• Reduced Time to Market

agile = to be able to move quickly

Being agile for Dev Team

Test Match

ReleaseOnce in 3 months

One Day T 20

ReleaseOnce per month

ReleaseMany times a week

Being agile for Ops team

SomeTickets

MoreTickets

Many ManyMore Tickets

Being agile

Really brought in its own

Challenges

We faced challenges such as

High time

to take

changes

production

Overhead

of processes

to move code

across

environments

Discomfort

With frequent

releases &

documentation

Longer time

to debug

issues

in production

confidence

deployments

It all often ended in

Main Reasons for This Divide

Not to forget

Different Hierarchies & Departments

For us DevOps started as

Building Relationship

What is DevOps?

Well I think

What we can make out of it

What DevOps meant to us

Piloting DevOps

The most widely used Application

in the Enterprise

Structure of our team

Thinking out aloud

How we aligned ourselves to DevOps

ProcessTechnology

People

The People Challenges

“WE” don’t know how “THEY” function

Face Time – It Matters

• Sitting Together

• Video Conference

• Tele Conference

• WebEx

Collaborate

• Deploy / Debug production issues together

• Testing Party Together

• Proactively Inform issues to one another

Dare to Share

• Agile

• Functionality

• Deployment

• Monitoring Tools

• Most troublesome modules

Dev Team Ops Team

Optimal Documentation

• Ops team now accesses the story board

• Dev Team updates a Wiki page to detail deployment requests for production– Date of deployment– Tag number– Functional changes that go in the release

Process Challenges

• Heavy processes to move code to production

• Debugging production issues

• Ops team did not appreciate Agile

Getting Engaged

Opening doors to Ops

Opened doors for Dev also

Read only access to app directory

Access to Error Logs

Access to Execute Tasks

Engineering Practices

Automated deployment scripts

Continuous Integration

AUTOMATION

Less Tickets Movement

• No more tickets for Deployments till QA

• Just drop an email with a CC to a group

• Ticket auto-generated for tracking purpose

Led us to Ticketless travel

Ticket Busters

• Identify the most troublesome tickets through Support teams

• Bust those through Do It Yourself screens

Technology Enablers

• Virtualization: Spin off servers on the fly

• Hoptoad – The Error App– Debug prod issues faster– Analyze a trend of issues proactively

How it helped

• Frictionless Teams and Deployments

• Light processes

• Ops team felt belonged to a product

• Ops team now prepared to cater to frequent releases

• More confidence about the product

• Open and Approachable Environment

Challenges we faced

• Resistance to change and being open

• Security concerns

• Working shifts

• Extra work!

Road Ahead

• Ticketless travel to production

• Expanding to other technologies

• Continue Collaboration

• Extend to other Agile teams as well as Ops teams

So Wish us Luck!

Happy to take Questions

Hope This Session Helps!

Thank you