DevOps and Integrated Deployment

Editor's Notes

• #4: Is there a Job Description? Do I need to hire against this? I don’t have a headcount. Are you giving me more work?
• #5: What does it run on? Do I need to purchase something? Training?
• #6: Devs are now doing IT? IT is not going to like that. Devs are reckless..
• #7: Is IT learning dev? Do they need to be trained?
• #8: Harmony..
• #9: Lets look at the new delivery model that works with DevOps to define it. Plan – work with biz to identify and prototype. Ops and Devs involved Develop – quick prototyping, build what was just planned Release – work with QA and Ops on deploying to test Operate – tools to run the software in production and monitor All if the FEEDBACK Loop, where you Build, Measure and Learn on an iterative basis. No waiting 6-12 months to go “live” Abandons the Waterfall method – that takes too long with the changing market.
• #10: So what is this Continuous model? Continuous everything.. Not sure portions are parts but everything. Integration with code and team Deploy the solution Gather feedback all the time Improve the product based on feedback Follow loo[p.
• #12: CEO or Marketing says this…
• #13: Business is moving too fast..
• #15: So lets look at the model again and see where DevOps can help
• #17: Planning stages – discussions can revolve around scaling.. How can we scale if our product takes off. Scaling from a team standpoint. Offices and teams all over
• #18: Well, deploy TFS for distributed teams and release management. Work with the agile framework to build out what is needed. Scale instantaneously..more later on that
• #19: What about developing? When devs work they are isolated or distrubted. How can they work together quickly? And what about environments. Test does not match QA, QA does not match production.
• #20: With distributed source control that takes care of your team. System Center can manage all environments from one location.
• #21: How can we release in this continuous model? Wont we step on toes?
• #22: Release management is integrated into the tools. Perform configuration based deployments using VS and the defined environment it is going to.
• #23: When we are running how can we manage issue or incidents?
• #24: TFS and System center has tools in place for ops to do this. Use debuggers and intellitrace to find out issues and put them back into the “plan”
• #25: So how does Azure help with all of this? It has a suite of tools and services to do all of this. IAAS – for testing/developing. VMs, Point to Site VPNs Storage – use as you want PASS – maybe it is just storage or mobile services to support an app. CDN’s SAAS – even eaiser, maybe it is just a web site. Use as you see fit for your biz
• #26: 25
• #27: [Click 1]We can use Management Portal or PowerShell to deploy a Windows Azure VM on demand. (Ops) [Click 2]With Windows Azure virtual networks, establish a pint-to-site VPN connection to connect a developer’s laptop with a Windows Azure VM. (Ops) [Click 3]With Visual Studio, we can create projects and develop apps. (Dev) [Click 4]And easily publish it to the VM. (Dev and Ops) [Click 5]Or connect to an existing a VM with a target app and debug applications. (Dev and Ops) All these can happen on demand and be carried out with integrated and coordinated activities of development and operations.
• #28: Fire up Manage.WindowsAzure.com Then fire up the demo