Agenda

• DevOps – Why now?

• Application lifecycle challenges

• Demo

– Problem detection

– Troubleshooting

– Deployment automation

• Q & A

DevOps – Agile Operations

Patrick Dubois, father of DevOps

Dynamic IT

"With Dynamic IT, we are bringing together the capabilities of the

core infrastructure and the application and development

platforms to help customers build integrated systems that will

make IT a stronger partner to the business."

Bob Muglia, VP of Server & Tools @ Microsoft, TechEd 2007

Why DevOps Now?

Cloud computingNew technology enabled value opportunities

Compete velocityDirect-to-consumer Mobility and devices proliferation

Business modernization

The business of IT is business modernization

Balancing agility with quality, scale, and compliance

Taking the business forward

Maximizing economies of scale

Faster time-to-market

Continuous value delivery

Why DevOps Now?

8 | Presentation title in Segoe 8pt

Application

Lifecycle

Application Lifecycle – common challenges

DevelopRapid reaction

to feedback OperateSoftware to value

delivery

MonitorFix

No actionable feedback

resulting in high MTTR

Isolated operations tools and

workflows

Long deployment cycle times

Users detect defects in

production

Production incidents are hard to

debug

Unable to reproduce error in

development environment

10 | Integrating development and operations for the last mile velocity

Development

• Day job: Increase/Maintain business viability by

introducing change to support market demand

• When problem occurs: the goal is to understand

the root cause to prevent future occurrences –

(ideally) attach DEBUGGER or collect DUMP!

• Time pressure: Sprints (3-4 weeks)

The problem: Development vs Operations

Operations

• Day job: Increase/Maintain business operational

availability by eliminating/controlling change

• When problem occurs: the goal is to restore

operation back to normal – REBOOT!

• Time pressure: SLA 99.9% (about 43 min/month)

Misaligned goals, priorities and “silo” mentality

11 | Integrating development and operations for the last mile velocity

• Shared artifacts

Output of Dev process is natively consumed by Operational tooling and vice versa

• Automation

Release to an (any) environment is automated through self-service experience

• Common goal

Common MTTR metrics that all Dev and Ops are tracking/responsible for

The solution: Dev + Ops = DevOps

Collaborative culture where all stakeholders work together

across entire application lifecycle

12 | Integrating development and operations for the last mile velocity

• Shared artifacts

VS Web tests can be used as TIP tests by SC Global Service Monitoring service

SC Operations Manager can collect root cause data in IntelliTrace format

• Automation

SC Orchestrator natively communicates with TFS and can be used to automate deployments

• Common goal

Operational alerts can be escalated from SC Operations Manager directly to TFS as

Operational Incidents WI

DevOps Today

VS, TFS and SC offers a platform to build collaborative DevOps

processes

13 | Presentation title in Segoe 8pt

Demo

Application Lifecycle – common challenges

DevelopRapid reaction

to feedback OperateSoftware to value

delivery

MonitorFix

WORKING SOFTWARE

Actionable feedback

ALM integrated tools and

workflows

Deployment and configuration

automation

Testing in production

Non-intrusive diagnostics

Production captured debug data

http://www.microsoft.com/visualstudio/eng/alm/operate

http://technet.microsoft.com/en-us/library/jj883936.aspx

http://technet.microsoft.com/en-us/library/jj883935.aspx