migrating web applications to azure

Notes de l'éditeur

• #6: Start the presentation by reading the word and then definition aloud. Slowly on the definition for emphasis.
• #7: On a snowy Christmas Eve in 2007, Garret Camp was in Paris, France. He was looking for a ride to a party. But not just any ride: he was looking for something special. Something that fit the occasion.
• #8: Garret Camp wanted a high-end, private ride. Something with leather seats. Something clean. Something in a color other than yellow. So he ordered a private car. It cost him 800$. For one ride. In one car. That’s an expensive ride.
• #9: Garret though, “this is crazy”. Why is a good ride so hard to afford? He thought that people should be able to get a private, high-end ride without having to break the bank. Garret though, “this is crazy”. Why is a good ride so hard to afford? Then he had an idea. Make nice cab rides available to anyone, anywhere. He figured this should be easy to do, if you could connect riders directly with drivers. And then he realized…
• #10: We’re already all connected. Some of you already know how this story ends. This is the story of Uber. In the next 12 years, Uber would completely upend the traditional taxi business, creating millions of new jobs, billions in revenue and jumpstarting the gig economy.
• #11: The question is, how did this happen? How did Uber manage to upend an entire industry that had been established for decades and entrenched in most countries and even political structures? Technology. They leveraged technology to build a better experience. The better experience always wins. Cab companies were simply not able to move quickly enough to leverage currently available technology to improve their service. What Uber did is called, “Disruption”.
• #12: This is the medical definition of disruption. In the case of Uber, this sounds more accurate to me. They literally broke apart the taxi industry with a smartphone app. Well Established companies have been watching this “disruption” phenomenon. They can see that if they aren’t able to move quickly and leverage technology. they will become the next taxi business. We refer to this “move quick and leverage technology” as “Digital Transformation”. 
• #13: Read the definition with emphasis. The cloud is essential for digital transformation. It is the bedrock. It is what enables you to move quickly, mitigate risk, and respond to disruption. 
• #14: But not every application is born in the cloud.  Most of them are, right now, as we speak, hosted in on-premises data centers all over the world. See, digital transformation is not just about the apps you build for tomorrow. It’s really about how you move quickly with the apps you have today. And as long as those apps are in a data center somewhere, you are significantly limited in how fast you can move.  Today we’re going to take a look at how you can modernize your existing applications, by getting them into the cloud.
• #15: Why modernize? I mean, sure, you don’t want to be caught with your hands in your pockets when a competitor like Uber shows up. But what is it about the cloud that makes it so essential to your ability to stay at the top of your game? TODO: Expound on these bullets OK. So modernizing is good. The cloud seems like a clear and obvious win. Why don’t we do it?
• #16: Listen, migrating apps is no cake walk. Anyone who tells you otherwise is not being honest about it. But don’t worry. You’re not the first to face down the challenge of modernization. We’ve helped a lot of customers make the move, and we’ve got a few tricks to show you today.
• #17: Migrations are TOUGH. Period. They are not easy. I’m sure you’ve got an application or two where you work that everyone is afraid to touch. Don’t even look at! Everyone just close your eyes and pray that it keeps working. What do we do about those apps?
• #19: Let’s talk about the different methods you can use for migrating into the cloud. Rebuild – completely rebuild your application for cloud native Refactor – repackage your app, but no major code changes Rearchitect – modernizing your code, breaking monoliths into microservices
• #23: While migrating applications and data to a public cloud like Azure can seem risky, Microsoft has been able to move much of that risk by defining a three step process of: Discover, Migrate, and Optimize/Modernize. Tools like Azure Migrate allow you to do a complete inventory of your virtualized environment and identify those applications, workloads and databases most appropriate for a proof of concept migration. Other tools, both Microsoft’s and third-party, help simplify the migration itself. Once the migration has been tested, the applications and services can be further optimized on the Azure environment. After a successful proof of concept, companies then have both the experience and confidence to move on to more complicated applications.
• #24: But today our focus will be on lift and shift migrations… The lift and shift model involves moving your existing applications or services to Azure-based virtual machines, with an operating system and networking configuration as close to their current on-premises configuration as is possible on a cloud platform. A successful lift and shift migration takes advantage of the infrastructure benefits and management features of the cloud, while minimizing the both the migration cost and decreasing the time required to complete the migration.
• #30: IaaS quickly scales up and down with demand, letting you pay only for what you use. It helps you avoid the expense and complexity of buying and managing your own physical servers and other datacenter infrastructure. Each resource is offered as a separate service component, and you only need to rent a particular one for as long as you need it (Give a short explain on no need to: Manage physical gear Manage network switches, firewalls Build and manage datacenters – compliance, security, redundancy)
• #31: Deploy virtual machines featuring up to 128 vCPUs and 6 TB of memory. Get up to 3.7 million local storage IOPS per VM. Take advantage of up to 30 Gbps Ethernet and 100 Gbps InfiniBand networks. Keep using your existing Microsoft, Oracle, IBM, and SAP applications, build new ones, or choose from thousands of pre-built applications in the Azure Marketplace. 
• #32: Improve your availability and keep your site reliable using scalesets and loadbalacners You can confidently deploy hundreds of identical virtual machines in minutes. With easy updates at scale, focus more on what matters—your application—and less on the infrastructure. Virtual Machine Scale Sets integrate with Azure networking resources such as Azure Load Balancer and Application Gateway.  Easily spread your workloads across the virtual machines in your Virtual Machine Scale Set
• #33: There are also PaaS (platform as a service) options for you – if you check out sessions like APPS30 you’ll learn how to migrate your apps into this service.
• #34: Obviously, this all has to cost something. The VM pricing calculator will give you ideas on how to estimate your costs in the short and long term.
• #35: Le Pounchki !
• #37: So let’s get in the habit of less rack and stack Let’s use the tools where we can point, click and type to create our infrastructure.
• #39: My favorite fake newspaper, the daily news… the world’s most MEH newspaper has announced that tailwind traders has agreed to aquire old guard company northwind Wow this is huge! This makes them now the world’s biggest fake company!
• #40: That means tons of new fake company applications to manage, anyone remember this from northwind? Well looks like there’s a bit more news.
• #41: With all the big money associated with this deal, there comes some other kind of trouble that Tailwind need to deal with. Technical debt. You know, the leftovers of ugly datacenters, held together apps, the jenga!
• #42: This web store is part of the technical debt for tailwind traders, and it’s a pretty simple application… just a web app that handles customer retail
• #43: And it’s like many other apps of this kind, a backend for the management of the store… mobile apps, tons of stuff to maintain over the course of the application.
• #44: And our main app is a net core application – this is the api that handles functions to send info in and out of the database for the store.
• #45: And react acts as the front end interface for the store. This is installed via npm on the webserver the app is hosted on.
• #46: And we have a trusty bash deployment script. How many of you still have this kind of deployment method in house? We use things like this because they work, they are repeatable, and for many of us – it pre-dates the automation tools that are available.
• #47: So lets pick up and start to lift and shift our application to our new servers.
• #48: We’ll do this all from the azure cloud shell and portal – no need to install anything on your computer to manage these systems!
• #52: SPOKEN "We're going to create a resource group, in this command I'll name it ignitemod10, put it in my subscription specific to my app and then provide a location where our metadata for our resource group will be held” az group create --subscription "Ignite The Tour" --name ignitemod10 --location eastus 
• #53: SPOKEN "I've created a resource group, I have a network for our applications, now it's time we build a virtual machine for our application to be installed on." az network vnet create --name ignitemod10vnet --subscription "Ignite The Tour" --resource-group ignitemod10 --subnet-name default 
• #54: SPOKEN "I've created a resource group, I have a network for our applications, now it's time we build a virtual machine for our application to be installed on." Create Ubuntu 18.04 VM in PortalUse local ssh key in your cloud shellSelect same vnet and location as your resource groupStandard B4msopen port 22/80do not provision extra disks, explain they are available
• #55: SPOKEN "I've created a resource group, I have a network for our applications, now it's time we build a virtual machine for our application to be installed on.” Show deployment overview as resources build. Explain what’s happening (arm is provisioning the resources you requested – you can save these as a template and redeploy as needed) 
• #56: SPOKEN "I've created a resource group, I have a network for our applications, now it's time we build a virtual machine for our application to be installed on.” Connect to server via ssh in cloud shell – su to root 
• #57: SPOKEN "I've created a resource group, I have a network for our applications, now it's time we build a virtual machine for our application to be installed on.” curl https://raw.githubusercontent.com/jaydestro/mod10-docs/master/deploy.sh > deploy.sh 
• #58: SPOKEN "I've created a resource group, I have a network for our applications, now it's time we build a virtual machine for our application to be installed on.” Edit and add connection stringsLine 29/30 of deploy.sh 
• #59: SPOKEN "I've created a resource group, I have a network for our applications, now it's time we build a virtual machine for our application to be installed on." explain bash deploy.shExplain what is going onRepo installed, dependencies installed, database connection strings added.Installs nginx reverse proxy to move traffic to react app
• #60: SPOKEN "I've created a resource group, I have a network for our applications, now it's time we build a virtual machine for our application to be installed on." 
• #61: And that’s a statement around how we feel about Azure. We want to invent with purpose in how we think about it what we deliver to you but also enable you to invent with purpose. And we do that in some key ways. TRANSITION: I talk about these ways as our promises to you on what Azure will always deliver and why we’ll help you.