All up-dev ops
•Download as PPTX, PDF•
3 likes•396 views
The document provides contact information for Dan Stolts and Ian Philpot of Microsoft, including their blog URLs, Twitter handles, and areas of specialization related to DevOps, containers, cloud computing, and more. It also includes definitions for MTTD (mean time to detect) and MTTR (mean time to resolve) and discusses how containers can provide increased application density and deployment flexibility compared to virtual machines.
Recommended
More Related Content
What's hot
What's hot (14)
Similar to All up-dev ops
Similar to All up-dev ops (20)
More from Ian Philpot
Recently uploaded
Recently uploaded (20)
All up-dev ops
- 1. @ITProGuru Dan Stolts (@ITProGuru) Chief Technology Strategist Microsoft US DX North East – Audience Blog: ITProGuru.com dstolts@Microsoft.com www.linkedin.com/in/danstolts Twitter @ITProGuru DevOps Containers and Azure @ITProGuruSpecializations: DevOps, Containers, Cloud, Virtualization, Windows Server aka.ms/70-534-book Ian Philpot Sr. Technical Evangelist, Microsoft US DX - Audience – South East Blog: tripdubroot.com Twitter @tripdubroott http://LinkedIn.com/in/ianphilpot
- 3. MTTD and MTTR MTTD = “mean time to detect” MTTR “mean time to resolve” They refer to how long it takes to detect an issue in production, and how long it takes to resolve that issue once it’s detected.
- 8. Introducing containers for Windows Server Containers Traditional virtual machines = hardware virtualization VM VM VM Applications Kernel = Operating system virtualization Container Container Container Windows Server containers Maximum speed and density Container Container Container Hyper-V containers Isolation plus performance Container Container Container
- 9. Session VS VM (or VDI) Parent OS workloads Hardware / Hypervisor Level Application(s) Session Based Computing VM or VDI Based Computing
- 10. Containers Parent OS workloads Hardware / Hypervisor Level Application(s) Container Based Density Advantages App App App App App App App App App App App App App App App App Linux VM App App App App App App App App App App App App App App App App App App App App App App Container Based Computing VM Isolation
- 11. How Containers Run Virtual Machines Hyper-V Containers Windows Server Containers Docker Containers Linu x VM Windows Server Containers on VM Hyper-V Containers on VM Azure Abstract s VM Azure Containers ACS … Containers As A Service Windows Containers can run on Windows 10 and Nano too!
- 12. Securityand Management Hybrid Operations Securityand Management Hybrid Operations Microsoft Azure Stack and Cloud Platform System Microsoft Azure Cloud Public, Global, Shared
- 13. Cloud is a new way to think about a datacenter VIRTUAL MACHINES VM SCALE SETS CONTAINER SERVICE SERVICE FABRIC Cloud Foundry, Marathon, Deis, OpenShift etc. Docker Swarm Mesos, etc., Windows and Linux .NET, Java, Python, PHP, Ruby, GO, Node.JS I AM SPECIAL WE ALL LOOK ALIKE Build on Infrastructure Mindset Ultimate Control System Admin Build on Platform Mindset Cost and Agility Developer Traditional Model Cloud Model Azure is Open at Every Layer
- 14. Public CloudPrivate Cloud Hybrid Cloud Data Applications Management Frameworks & Tools Infrastructure SQL Server .NET Visual Studio SharePoint Dynamics System Center OMS Exchange Windows Server Addressing Your Enterprise Cloud Needs in a Trustworthy Way DevOps & PaaS Team Foundation Services Trust In Microsoft ..... Now Across Your Entire Stack! Enterprise Linux Cloud Infrastructure Development & Testing Open Source Data Infrastructure High Performance Computing Java Enterprise Platforms Web Applications How Can We Help You On Your Journey?
- 16. 65 Visual Studio Code Extensions 5,910 Visual Studio Gallery Extensions 90 Visual Studio Sim-Ship Partners 48 VS Team Services Extensions Open + Flexible Tool Chain 1,177 Visual Studio Code Extensions 6,538 Visual Studio Gallery Extensions 90 Visual Studio Sim-Ship Partners 171 VS Team Services Extensions
- 18. Plan 1 Monitor + Learn ReleaseDevelop + Test 2 Development Production 4 3
- 19. 1
- 20. 2 Once the iteration starts, developers turn great ideas into features…
- 21. cspkg
- 22. cspkg
- 24. cspkgcspkg
- 28. Virtual Machine Cloud Service Website Network Storage SQL Database Service Bus Resource Groups Scheduler Monitoring Search HDInsight Mobile Services Azure AD Not a complete list
- 30. 4
Editor's Notes
- Title: Windows Server 2016, Containers and Next Generation Micro Services Abstract: Are you up to speed with the next HUGE WAVE of virtualization… containers and micro services? How will these great technologies impact our datacenters as they move into the mainstream with the soon to be released Windows Server 2016? Come to this session to have a look at the near future as well as the soon to be released tools to help us meet the demands of our businesses. On this journey, we will explore what and why of micro services and containers, how these new virtualization technologies will change our world and at what pace. We will show off some great new technologies built into Windows Server 2016 and get an understanding on how these new technologies will RAPIDLY change not only the virtualization landscape but also the cloud landscape. Name of Presenter: Dan Stolts Bio of Presenter (max 500 spaces): Dan Stolts “ITProGuru” is a technology expert who is a master of systems management and security. He is Chief Technology Strategist for Microsoft, owns several businesses and is a published author. Reach him on his primary blog http://itproguru.com or twitter @ITProGuru. He is proficient in many datacenter technologies (Windows Server, System Center, Virtualization, Cloud, Etc) and holds many certifications including MCT, MCITP, MCSE, TS, etc. Dan is currently specializing in system management, virtualization and cloud technologies. Dan is and has been a very active member of the user group community. Dan is an enthusiastic advocate of technology and is passionate about helping others. See more at: http://itproguru.com/about
- Taken from: http://dev2ops.org/2010/02/what-is-devops/ Development kicks things off by “tossing” a software release “over the wall” to Operations. Operations picks up the release artifacts and begins preparing for their deployment. Operations manually hacks the deployment scripts provided by the developers or creates their own scripts. They also hand edit configuration files to reflect the production environment, which is significantly different than the Development or QA environments. At best they are duplicating work that was already done in previous environments, at worst they are about to introduce or uncover new bugs. Operations then embarks on what they understand to be the currently correct deployment process, which at this point is essentially being performed for the first time due to the script, configuration, process, and environment differences between Development and Operations. Of course, somewhere along the way a problem occurs and the developers are called in to help troubleshoot. Operations claims that Development gave them faulty artifacts. Developers respond by pointing out that it worked just fine in their environments, so it must be the case that Operations did something wrong. Developers are having a difficult time even diagnosing the problem because the configuration, file locations, and procedure used to get into this state is different then what they expect (if security policies even allow them to access the production servers!). Time is running out on the change window and, of course, there isn’t a reliable way to roll the environment back to a previously known good state. So what should have been an eventless deployment ended up being an all-hands-on-deck fire drill where a lot of trial and error finally hacked the production environment into a usable state.
- PEOPLE = Culture and not JUST Dev and Ops, anyone involved in delivering value to customers. Fundamental attributes of successful cultures: Shared mission and incentives: infrastructure as code, apps as services, DevOps/all as teams Rally around agile, shared metrics, CI, service owners on call, etc. PROCESS = DevOps is about Lean and eliminating waste in the process of delivering value to end users. PRODUCTS = You can’t buy “the DevOps” in or outside of Microsoft. That being said part of what DevOps is about is automation and you can’t automate without tools or products to help you. Also tools or products are only as effective as the people groups using them and processes they are bound by. For instance if only one small pocket of developers are using a script to build their infrastructure from scratch, but Ops still has a separate different manually configured infrastructure – it really is of only limited value if not detrimental.
- But how is it that some companies like Netflix, Amazon, Etsy, and Facebook regularly deliver new features and innovation to their customers while other companies must wait weeks or months to release software updates? Today, we see continual frustration on all sides: Business, customers and IT all suffer from a lack of collaboration and communication between development and operations in software projects This increases time and labor involved in delivering and maintaining software systems – not a good thing in a world where fast time to market is key Add to that the problem that much of what we build is based on assumptions instead of hard data and you can see how this could easily lead a team to build the wrong thing The inability to deliver software efficiently and react quickly to changes can lead to much more than just frustration –in the long run, this can threaten your entire business!
- In the real world, there are real consequences if you are unable to deliver high-quality software quickly or build the wrong thing to begin with: 40% of implementations end up getting reworked because they don’t meet the users’ original requirements The average cost of one hour downtime of a customer-facing app is calculated at 100.000 dollars per hour – and this does not take into account the damage to reputation, which can be even greater. Fixing such production issues takes on average 200 minutes per incident Three quarters of development teams have adopted Agile methodologies today, enabling them to develop faster. While this is a great number, it does not help if a development team is Agile but deployment still takes weeks or months because IT Ops is perceived as not being Agile These are just 3 very high-level examples but all the data we have today points toward the same conclusion – this is about more than just frustration or minor delays. Lack of collaboration between dev and ops can have substantial impact on a company’s bottom line and success According to a recent report by Steven Elliot of IDC, hourly downtime costs can range from $1.25 to $2.5 billion for a Fortune 1000 firm, and the average cost of a critical application failure is $500,000 to $1 million per hour. http://info.appdynamics.com/rs/appdynamics/images/DevOps-metrics-Fortune1K.pdf
- Over the past 5 years, the State of DevOps report has surveyed more than 25,000 technical professionals world wide with companies of ALL sizes and verticals. Employees in high-performing teams were 2.2x more likely to recommend their organization as a great place to work. (2016 – employee Net Promoter Score)
- When it comes to applications, historically, IT administrators deployed with a 1:1 application to server ratio. When a new application was required by the business, it was deployed onto a newly provisioned physical system, to ensure no conflicts with existing applications and workloads. This resulted in a huge number of physical servers, all with very low utilization. Fast forward to a more modern datacenter, where virtualization is now prevalent, and you’ll find significantly higher consolidation ratios, much greater utilization and significantly accelerated app deployment speeds as administrators deploy applications in minutes, compared with hours, days or weeks in a purely physical datacenter. Compared with applications that ran on individual physical servers, the compatibility of those same apps to run inside virtual machines was typically very high. After all, the virtual machine just presents virtual hardware to the same operating system that was running in the physical world. The only consideration being, if that application or workload has a requirement for a specific piece of hardware, such as a PCI-E card, that couldn’t be virtualized and presented through to the guest operating system. In addition, once that application was encapsulated inside the virtual machine, it benefited from higher levels of redundancy, and also mobility, through features such as live migration. There is however, a new and increasingly popular way to build, ship, deploy and instantiate applications. Containers can further accelerate application deployment and streamline the way IT operations and development teams collaborate to deliver applications to the business. But what are containers? Well, to give the computer science definition, containers are an operating system-level isolation method for running multiple applications on a single control host. With developers building, and then packaging their applications into containers, and providing them to IT to run on a standardized platform, it reduces the overall effort to deploy applications, and can streamline the whole dev and test cycle, ultimately reducing costs. As containers can run on a host OS which itself could be physical or virtual, it provides IT with flexibility, and the opportunity to drive an increased level of server consolidation, all whilst maintaining a level of isolation that allows many containers to share the same host operating system. Windows Server containers are isolated behind their own network compartment. This can be provided a NAT DHCP or Static IP. Each container has an independent session namespace, which helps to provide isolation and security. The kernel object namespace is isolated per container. Hyper-V Containers take a slightly different approach to containerization. To create more isolation, Hyper-V Containers each have their own copy of the Windows kernel and have memory assigned directly to them, a key requirement of strong isolation
- Public Cloud, Private Cloud, On-Premises – it’s not either-or and the world is never just black or white It’s your choice and Microsoft offers a hybrid cloud solution that is tailor-made for your organization and your applications Microsoft Azure Stack is a new hybrid cloud platform product that enables your organization to deliver Azure services from your own datacenter to help you achieve more Get the power of cloud services, yet maintain control of your datacenter for true hybrid cloud agility You decide where to keep your data and applications - in your own datacenter or with a hosting service provider Easily access public cloud resources to scale at busy times of the year, for dev-test, or whenever you need them Only Microsoft builds and runs its own hyper-scale datacenters and delivers that proven innovation to your datacenter
- Notes coming soon – please check back on http://aka.ms/opensource for latest version
- Notes coming soon – please check back on http://aka.ms/opensource for latest version
- Azure is open and flexible – you bring what you know and simply continue to use it – there are no second class citizens in the Microsoft cloud Whether it’s platforms, languages, tools or apps – we support an ever-growing set of OSS and proprietary technologies, tools and standards With Azure, you have choices - choices that help you maximize your existing investments You bring the tools you love and skills you already have, and run virtually any application, using your data sources, with your operating system, on your devices Or - complement what you’ve already built by using Azure to add additional value to your app Augment your iOS or Android mobile application with identity and access management through Azure Active Directory, or cloud-powered insights through Azure Data Lake Analytics Run Linux batch processes to support your .NET applications And tap a growing ecosystem of open source solutions available from Azure Marketplace that enable rapid deployment in the cloud At Microsoft, open source is a part of our day-to-day approach to cloud innovation We are also constantly looking for ways to improve developer and user experiences with SDKs for open source languages and an open API Plus, we are committed to sharing our cloud learnings with you and for your datacenters, thanks to Linux and open source support in Azure Resource Manager and Azure Stack
- VSTS and TFS goes FAR beyond simple source code and build and are KEY building blocks to enabling Agile and numerous DevOps practices regardless of your programming language, application architecture, or infrastructure provider. Our DevOps solution is flexible and adapts to you instead of forcing you to change the way you work or the tools you use Our DevOps solution is open and extensible with a large ecosystem of partners building best-of-breed extensions and integrations Features in Visual Studio Team Services get released once every three weeks and around once per quarter those features get rolled up and put into an update which goes into the on-premises Team Foundation Server. So no matter whether you prefer to do your business in the cloud, hybrid, or on-premises, Microsoft has you covered.
- Main point to land – VSTS/TFS is open, flexible, and integrates with your tools and if the integration isn‘t there yet you can build it in our marketplace. You can go all-in OR just pick the bits and pieces of functionality you‘d like to use. Tasks are open source on GitHub. Optionally choose some partners to highlight which resonate with your local audience. i.e. If you want to use GitHub for your source code and then use VSTS for builds you can do this. You can use Jenkins for builds and use VSTS for release management.
- https://github.com/julienstroheker/hackathon_GetStarted – gives you an automated way to populate your own VSTS subscription with Kanban data to do a more interesting demo.
- Release Management in the Visual Studio Team Services Service (or on-prem product which not easy to access for hackathon) Deployment Slots + CI/CD solution with VSTS + Azure Websites
- David Note: Make sure to highlight customer pain points, “bullet train”, Poll??
- PowerShell & xPlat-CLI – http://azure.microsoft.com/en-us/documentation/articles/install-configure-powershell/ MAML – https://www.nuget.org/packages?q=Microsoft.WindowsAzure.Management&prerelease=true&sortOrder=relevance Resource Groups - Chef - http://channel9.msdn.com/Shows/Edge/Edge-Show-93-Chef-deployments-to-Windows-Azure Puppet - http://blogs.msdn.com/b/interoperability/archive/2013/12/12/windows-azure-provisioning-of-linux-and-windows-via-puppet.aspx Vagrant - https://github.com/MSOpenTech/vagrant-azure
- Roll-forward means making a fix to the code Check-in fix, quickly test, “roll-forward” by pushing a new release
- Microsoft also invests heavily in the open source ecosystem and enables you to keep your existing investments in open source tools while potentially enabling integration with our own technologies. In fact, we have an entire organization called MS OpenTech who are dedicated to this pursuit. In this slide you can see a number of different open source products we have interoperability with which play different roles across the entire application lifecycle. These open source tools often play a part in more than one aspect of the product lifecycle, but they are listed here based on the primary integration point with a Microsoft technology. Last but not least, I’d like to point out that the Microsoft Cloud OS platform where you might decide to host your application supports various programming languages like node.js, php, and java as well as underlying open source operating systems like Linux. http://msopentech.com/blog/project-categories/devops/
- The First Way emphasizes the performance of the entire system, as opposed to the performance of a specific silo of work or department - this can be as large as a division (e.g., Development or IT Operations) or as small as an individual contributor (e.g., a developer, system administrator). It begins when requirements are identified (e.g., by the business or IT), are built in Development, and then transitioned into IT Operations, where the value is delivered to the customer. When we think as a system, we can focus clearly on the business value that flows between business, dev, ops, and end users. The outcomes of putting the First Way into practice include never passing a known defect to downstream work centers, never allowing local optimization to create global degradation, always seeking to increase flow, and always seeking to achieve profound understanding of the whole system. For more information on the Three Ways, check out: http://itrevolution.com/a-personal-reinterpretation-of-the-three-ways/
- The Second Way is about creating right to left feedback loops. The goal of almost any process improvement initiative is to shorten feedback loops so necessary corrections can be made quickly and continuously. The outcomes of the Second Way include understanding and responding to all customers, internal and external, shortening and amplifying all feedback loops, and embedding knowledge where we need it.
- The Third Way is about creating a culture that fosters two things: continual experimentation, taking risks and learning from failure; and understanding that repetition and practice is the prerequisite to mastery. Experimentation and taking risks are what ensures that we keep pushing to improve, even if it means going deeper into the danger zone than we’ve ever gone. And we need mastery of the skills that can help us retreat out of the danger zone when we’ve gone too far. The outcomes of the Third Way include allocating time for the improvement of daily work, creating rituals that reward the team for taking risks, and introducing faults into the system to increase resilience.
- Shortening cycle times through advanced release management and automation tools Optimizing resources and eliminating waste, and Increasing quality and availability of your solutions
- Today, we work very differently and we strive to deliver innovation quickly, without sacrificing quality It was a fun journey and we are still learning – but now, we see positive results every day For us, the key to success is the close collaboration between development and operations disciplines - we are one team
- This slide is just to show what we have to offer in the DevOps space. Microsoft is uniquely positioned as the only vendor to have everything you need to build a DevOps Pipeline.