DevOps – Moving from Agile Dev toAgile Ops using Continuous DeliveryKalyan KumarVP-CFS & Chief Technology ArchitectEmail: ...
Anti Pattern #1 - Config Mgmt = DevOps4ToolsProcessCulture
Anti-Pattern #2- Rebranding Ops as the DevOps team or Creating separate team5(Yet Another Silo)Act as a change agent
Anti-Pattern #3 - Sell it as a buzzword6
7Anti-Pattern #4 – Deploy Software Manually
8Anti-Pattern #5 - Manual Configuration of Production Environments
9Anti-Pattern #6 - Believe chef/puppet will solve all your problems 
Anti-Pattern #7 - Deploy to production after testing in Dev without testing in Production-Like
Traditional Dev and Ops Model12They don’t have common goals.They don’t use the same toolsNo visibility into one others’ pr...
Symptoms and causes13The project was kicked off last week. The dev environment isn’t readyyet.There are multiple tracks in...
Agile is needed in all the phases of SDLC. Not just in development.14Continuous Buildand Integration• Key part of Agiledev...
DevOps – Move beyond Continuous Integration to Continuous Delivery15Provisioning•Provisioning ofservers with pre-requisite...
VersionManagementUser Interface/APIHave a Platform to Deliver DevOps VisionEnvironment ManagementEnvironmentBaselinesOrche...
TraditionalTransitionAgileTransitionLeavingDevCome Back Soon!Welcome ToOpsDrive Safe!LeavingDevCome Back Soon!Welcome ToOp...
18Be the Iron Man and not the RobotBe the Automator and NOT the Automated 
Thank You* All logos, trademarks, copyrights referred in this deck belong to the respectivecompanies or Creative Commons L...
DevOps - From Agile Dev to Agile Ops for Continuous Delivery
DevOps - From Agile Dev to Agile Ops for Continuous Delivery
DevOps - From Agile Dev to Agile Ops for Continuous Delivery
Upcoming SlideShare
Loading in …5
×

DevOps - From Agile Dev to Agile Ops for Continuous Delivery

1,052 views

Published on

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,052
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

DevOps - From Agile Dev to Agile Ops for Continuous Delivery

  1. 1. DevOps – Moving from Agile Dev toAgile Ops using Continuous DeliveryKalyan KumarVP-CFS & Chief Technology ArchitectEmail: kalyank@hcl.comTwitter: @kklive
  2. 2. Anti Pattern #1 - Config Mgmt = DevOps4ToolsProcessCulture
  3. 3. Anti-Pattern #2- Rebranding Ops as the DevOps team or Creating separate team5(Yet Another Silo)Act as a change agent
  4. 4. Anti-Pattern #3 - Sell it as a buzzword6
  5. 5. 7Anti-Pattern #4 – Deploy Software Manually
  6. 6. 8Anti-Pattern #5 - Manual Configuration of Production Environments
  7. 7. 9Anti-Pattern #6 - Believe chef/puppet will solve all your problems 
  8. 8. Anti-Pattern #7 - Deploy to production after testing in Dev without testing in Production-Like
  9. 9. Traditional Dev and Ops Model12They don’t have common goals.They don’t use the same toolsNo visibility into one others’ processesCharacteristics of traditional Dev and Ops teams:Development Teams• Driven by change• Focus is to deliver valueexecuting projects ontime and within budget• Measured by improvedbusiness capability andagility• Higher frequency ofreleases• Rapid pace of innovationin tools and technologies Different implementation methodologiesOperations Teams• Driven by stability• Focus is to keep theenterprise running withless to zero downtime• Measured by uptime andstability of the productionsystem• Encourage fewer releases• Typically small teamsconsumed by fire-fighting
  10. 10. Symptoms and causes13The project was kicked off last week. The dev environment isn’t readyyet.There are multiple tracks in the project. Build is broken more often thannot. Takes a lot of time to identify the issue.Application is deployed to QA environment successfully. But I can’t loginto the application.Tedious testing cycle. Takes too much time to setup test bed, execute testcases, report results and even more time to repeat this cycle.Takes too much time to follow the release notes and deploy theapplication.No easy way tospawnenvironmentsContinuousIntegrationLack of releasemanagementprocessContinuousTestingDeploymentautomationProgramManagerDevelopmentManager/LeadQA Lead/teamProgrammanagerOps/Deployment teamsCauseSymptomImpacted party
  11. 11. Agile is needed in all the phases of SDLC. Not just in development.14Continuous Buildand Integration• Key part of Agiledevelopment• Integrate code frommultiple tracks/modulesas early as possible• Unit tested build delivered• Assign build version beforedeploying to QAContinuousTesting• QA the code for functionaland non-functionalaspects in a prod-likeenvironment• QA reports defects on aspecific build version• Dev fixes the defects anddelivers another build.This loop continues till QAcertifies the build• Improves confidence inthe entire team if code isbeing tested regularlyContinuousDeployment• Objective is to get thesystem to the users’ handsas often as possible• Deploy the QA certifiedbuild in prod• Build tools to automatethe deployment• Opportunity for Ops toprovide feedback to Devon the structure of thebuild early in the life cycle• Continually deployingcode will improve thequality of tools and makethe deployment seamlessContinuousMonitoring• Use monitoring tools tomeasure system andapplication health• Opportunities to identifybottlenecks and issuesearly• Communicateperformance/scalabilityissues to dev earlyContinuous Delivery
  12. 12. DevOps – Move beyond Continuous Integration to Continuous Delivery15Provisioning•Provisioning ofservers with pre-requisites•AutomationDeploymentAutomation•ContinuousIntegration•Continuous Testing•Build dependencies•Config filesDeploymentArchitecture•Caching•Load balancing•Content DeliveryNetworksReleaseManagement•Continuous release•Code promotions•Code rollbacksEnvironmentManagement•Inventorymanagement•Auto scaling basedon policies•ApprovalsApplicationPerformance andMonitoring•System healthmonitoring•Application healthmonitoring•Root cause analysisProject InitiationProjectImplementationProject Rollout FeedbackDevOpsContinuous DeliveryCulture Process Tools
  13. 13. VersionManagementUser Interface/APIHave a Platform to Deliver DevOps VisionEnvironment ManagementEnvironmentBaselinesOrchestration & CollaborationConfiguration ManagementBuildBuildRepositoryQA PerformanceTestUAT ProductionEnvConfigApplicationFilesProcess ManagementCultureApplication Performance ManagementProgrammable Infrastructure
  14. 14. TraditionalTransitionAgileTransitionLeavingDevCome Back Soon!Welcome ToOpsDrive Safe!LeavingDevCome Back Soon!Welcome ToOpsDrive Safe!Agile Dev meets Agile OpsRelease Management is Too SlowStreamlined Release Management
  15. 15. 18Be the Iron Man and not the RobotBe the Automator and NOT the Automated 
  16. 16. Thank You* All logos, trademarks, copyrights referred in this deck belong to the respectivecompanies or Creative Commons License

×