Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Azure Saturday 2019 - Keep Calm and "Lift&Shift" on Azure
Similar to Azure Saturday 2019 - Keep Calm and "Lift&Shift" on Azure (20)
Azure Saturday 2019 - Keep Calm and "Lift&Shift" on Azure
- 1. #azuresatpn Azure Saturday 2019 Keep calm and "Lift&Shift" on Azure Lo Zen della migrazione su Azure di un data center on-premises Daniele Scrivano @Dan_Writer
- 2. #azuresatpn La decisione: si va in cloud!! Aaaaaaaaaaaaaaaaaa…….zure!! 😃
- 3. #azuresatpn
- 4. #azuresatpn La consulenza Il fai da te
- 5. #azuresatpn Cinque step imprescindibili!! ASSESSMENT MODEL DESIGN MIGRATE GOVERNANCE
- 6. #azuresatpn Step 1 - Assessment Raggruppare per Isole Applicative i server/macchine virtuali Verificare le interdipendenze Verificare il consumo delle risorse nel data center Verificare la topologia di rete
- 7. #azuresatpn STEP 1 – ASSESSMENT - OBIETTIVI Dimensionamento servizi Requisiti di sicurezza Requisiti di resilienza Consumi mensili
- 8. #azuresatpn Assolve a due degli step del Lift&Shift: Analisi e migrazione (IaaS & PaaS) Assessment virtual machine (Vmware e Hyper-v) e non solo Sizing VM su Azure (maybe!) Replica VM su Azure (ora agentless per Vmware) Configurazione VM su Azure: Nome – Size – Network Finalizzazione migrazione!! Azure Migrate: Project
- 9. #azuresatpn
- 10. #azuresatpn
- 11. #azuresatpn
- 12. #azuresatpn
- 13. #azuresatpn
- 14. #azuresatpn
- 15. #azuresatpn
- 16. #azuresatpn Agentless Azure Site Recovery
- 17. #azuresatpn
- 18. #azuresatpn Step 2 -Scelta modalità servizi Cloud IaaS, PaaS o SaaS? RETIRE REPLACE RETAIN, WRAP, AND EXPAND REHOST REENVISION Le 5 R del cambiamento
- 19. #azuresatpn Step 2 – IaaS, PaaS o SaaS – Esempi IaaS PaaS SaaSTipoApplicazioni Legacy Database CloudReady Modernize
- 20. #azuresatpn Scegliere la modalità di erogazione in cloud: All-in-one subscription o Multi-subscription? • Pros • Contro Scegliere tipo di connessione verso l’on-premises: VPN, ExpressRoute Scegliere design di rete: All-in-one vNET o Hub-Spoke topology? • Pros • Contro Inserimento o meno di NVA in Azure Step 3 – Design La rete in cloud non è come la rete on-premises: inutile tentare di copiarla fedelmente, bisogna giungere a dei compromessi!!
- 21. #azuresatpn Step 3 – Design - Subscription Single subscription Production-and- non-production pattern Workload separation pattern Application category pattern Functional pattern Business unit pattern Geographyc pattern
- 22. #azuresatpn Step 3 – Design - Subscription
- 23. #azuresatpn Step 3 – Design – Hub&Spoke
- 24. #azuresatpn Step 3 – Design – Componenti Basic subnet vnic UDR Service Endpoint Balance LB Frontdoor Traffice Manager AGW Connection VNG PIP ExpressRoute Storage Storage Account Azure Backup Azure Netapp Monitoring Monitor MonitorLogAnalytics NPM Activity Log Automation NVA Security Azure Firewall KeyVaultNSG+ASG Security Center SentinelDDOS Protection vNet
- 25. #azuresatpn Punti fondamentali design SICUREZZA SLA (ALTA DISPONIBILITÀ, RESILIENZA) DISASTER RECOVERY CONSUME
- 26. #azuresatpn Step 4 – Migrazione - Pilot ENVIRONMENT DEV/TEST EASY APPLICATION TEST
- 27. #azuresatpn Step 4 – Migrazione - Full PIANIFICAZIONE TEST LAB FULL DESIGN FULL MIGRATION CYCLE HYBRID NETWORK
- 28. #azuresatpn Step 5 – Governance Ottimizzazione consumi Raccomandation and compliance Trasformazione PaaS Disaster Recovery
- 29. #azuresatpn Step 5 – Governance – Tools Azure Monitor Azure Security Center Azure Advisor Azure Cost and Management Billing
- 31. #azuresatpn Link utili • https://cafbaseline.com/ • http://aka.ms/fusionnavigator • https://docs.microsoft.com/en-us/azure/architecture/patterns/
- 32. #azuresatpn Enjoy and jump to cloud!
- 33. #azuresatpn Azure Saturday 2019 GRAZIE!! Q&A Time Daniele Scrivano daniele.scrivano@hotmail.it @Dan_Writer
Editor's Notes
- • Retire Of course, if a legacy application is providing little value compared to its costs, the enterprise should consider it a candidate for retirement. When few people are using an application relative to its cost impact, the enterprise needs to run a cost–benefit analysis to determine if it is worth the expense. Additionally, some functionality provided by legacy systems can be rolled into a consolidated modern application running in the cloud, allowing some applications to be retired while others are replaced and modernized. • Replace Often, a legacy application is providing some value, but an off-the-shelf replacement with a lower total cost of ownership (TCO) is available. Many legacy applications were originally built because there was no alternative at that time. A modern, readily available application that is better suited to running in the cloud—most cost-effectively of all, a SaaS application—might now exist that you can use to replace the older one. Also, when a legacy application is replaced with a more comprehensive modern solution, there might be a chance to consolidate functionality from several older applications, thereby replacing multiple applications with a single system. Retain, wrap, and expand If a legacy application is providing good value and not incurring a high TCO, the best approach might be to retain it but put a modern “wrapper” around it in order to gain additional value and benefits. Examples of the “retain and wrap” approach include the following: • Using API management tools, such as Microsoft Azure API Management, add an API so that authorized external applications can exercise the functionality of the application. • Extend a legacy application with third-party tools; for example, by using a C# wrapper around older applications, or by making their data available through Extract, Transform, and Load (ETL) or other approaches, connect them to other software components, such as analytics applications, machine learning, or mobile access. • Rehost If a legacy application is providing good value but is expensive to run, it might be a candidate for rehosting. Rehosting involves keeping the same basic functionality, but moving it to the cloud where it is easier to manage and less expensive to run. This is also called “lift and shift.” In a rehosting situation, the legacy application might currently be located either on a local virtual machine (VM) or on local hardware. Some VMs might be eligible to move with a simple migration. Those on local hardware might be able to be converted with a physical-to-virtual migration and then hosting the VM in the cloud. Some VMs, especially older ones, might not relocate easily to the cloud without some significant work. In those cases, you might want to consider reenvisioning and building the application in the cloud. • Reenvision If a legacy application is providing good value but cannot be easily moved, the best solution might be to reenvision it and build it again in the cloud. Reenvisioning is a process of rebuilding the application in the cloud using modern technology, a new architecture, and best practices; it normally also involves adding more business value to core functionality, such as improving market differentiation. Reenvisioning an application might require rewriting the main logic using a modern development language and tools and making it service-oriented. Reenvisioning an application can be facilitated by starting with VMs in the cloud which can be instantiated in a matter of minutes.
- • Retire Of course, if a legacy application is providing little value compared to its costs, the enterprise should consider it a candidate for retirement. When few people are using an application relative to its cost impact, the enterprise needs to run a cost–benefit analysis to determine if it is worth the expense. Additionally, some functionality provided by legacy systems can be rolled into a consolidated modern application running in the cloud, allowing some applications to be retired while others are replaced and modernized. • Replace Often, a legacy application is providing some value, but an off-the-shelf replacement with a lower total cost of ownership (TCO) is available. Many legacy applications were originally built because there was no alternative at that time. A modern, readily available application that is better suited to running in the cloud—most cost-effectively of all, a SaaS application—might now exist that you can use to replace the older one. Also, when a legacy application is replaced with a more comprehensive modern solution, there might be a chance to consolidate functionality from several older applications, thereby replacing multiple applications with a single system. Retain, wrap, and expand If a legacy application is providing good value and not incurring a high TCO, the best approach might be to retain it but put a modern “wrapper” around it in order to gain additional value and benefits. Examples of the “retain and wrap” approach include the following: • Using API management tools, such as Microsoft Azure API Management, add an API so that authorized external applications can exercise the functionality of the application. • Extend a legacy application with third-party tools; for example, by using a C# wrapper around older applications, or by making their data available through Extract, Transform, and Load (ETL) or other approaches, connect them to other software components, such as analytics applications, machine learning, or mobile access. • Rehost If a legacy application is providing good value but is expensive to run, it might be a candidate for rehosting. Rehosting involves keeping the same basic functionality, but moving it to the cloud where it is easier to manage and less expensive to run. This is also called “lift and shift.” In a rehosting situation, the legacy application might currently be located either on a local virtual machine (VM) or on local hardware. Some VMs might be eligible to move with a simple migration. Those on local hardware might be able to be converted with a physical-to-virtual migration and then hosting the VM in the cloud. Some VMs, especially older ones, might not relocate easily to the cloud without some significant work. In those cases, you might want to consider reenvisioning and building the application in the cloud. • Reenvision If a legacy application is providing good value but cannot be easily moved, the best solution might be to reenvision it and build it again in the cloud. Reenvisioning is a process of rebuilding the application in the cloud using modern technology, a new architecture, and best practices; it normally also involves adding more business value to core functionality, such as improving market differentiation. Reenvisioning an application might require rewriting the main logic using a modern development language and tools and making it service-oriented. Reenvisioning an application can be facilitated by starting with VMs in the cloud which can be instantiated in a matter of minutes.