Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Global (IoT) Enterprise Cloud Please contact us at Migration Eplexity– We can put together Summary of this document with your team . [email protected] Findings 1 Agenda 2 • Current state analysis • The value of migrating to Public Cloud (AWS) • Cloud Migration Approach and Timelines • Investment Summary • Q/A Executive Overview Acme is dedicated to serving the Client through quality data and rerch available anywhere and at anytime. This creates a cultural climate that demands: • High levels of quality across many customer touch points: – Availability of systems is not only critical, lives depend on it • Adapting to Client markets and opportunities – – Significant growth in IS – keeping up with demand is paramount Expansion into new geos while meeting Client regulatory requirements • Need to be able to move quickly AND securely 3 Infrastructure Findings… 4 Summary • Environment A: lift and shift to the cloud is targeted for 80+% of workloads – Sparc workloads cannot be directly shifted to AWS and will need to be refactored for the cloud. – PSTN, Telco, and SAT connectivity will remain during migration › Recommendations is to take hybrid approach during lift-and-shift. – Many systems have operating systems that are past EOL. If possible these workloads should be upgraded or containerized prior to migration. – Systems improvements such as DNS implementation and increased, temporary Internet bandwidth are recommended prior to migration – Time synchronization will need to be calibrated for the cloud to support LDN 5 Summary • Environment B: lift and shift to the cloud is targeted for 95+% of workloads – Consists primarily of five HPC clusters and three database clusters. – All workloads can be directly converted to AWS infrastructure via lift and shift or containerization – Due to the high peak utilization and low average utilization of the HPC clusters we recommend optimizing each workload to use burst capabilities of AWS – storage systems are EOL and have a limited number recoverable disk failures. – Firewalls at do not support VPN to AWS, recommend direct connect for the duration of the migration. – A subset of cluster will need to remain in place for up to two years to support the Google Makani project 6 Summary • Environment C: lift and shift to the cloud is targeted for 85+% of workloads – PSTN, Telco connectivity will remain during migration – Recommendations is to take hybrid approach during lift-andshift – All workloads can be directly converted to AWS infrastructure via lift and shift or containerization – Many systems have operating systems that are past EOL. If possible these workloads should be upgraded or containerized prior to migration. – VNX 5500 SAN storage is nearing EOL and will require third party support contract in order to replace failed disks. 7 Summary • Environment D: lift and shift to the cloud is targeted for 85+% of workloads – PSTN, Telco, SAT connectivity will remain during migration – Recommendations is to take hybrid approach during liftand-shift – All workloads can be directly converted to AWS infrastructure via lift and shift or containerization – Avicast and Checktime can be deprecated instead migrated utilizing AWS natives services for DR. – VNX SAN storage is no longer under support. 8 Overall Summary • Underutilized systems that require short periods of compute capacity but are required to run 24/7 • Hardware and software that is out of support, End of Life, or nearing End of Life • Single points of failure for production applications in support devices such as load balancers or storage. • Updates to systems is overly complicated. This affects keeping upto-date quickly with the latest security patches and bug fixes. 9 The cloud opportunity 10 Pre-TOM Management, Monitoring & Alerting Comprehensive: The breadth and depth of our IT infrastructure must be inventoried and regularly cataloged into a CMDB (Configuration Management Database). o Decreased MTTR (Mean Time To Repair) and increased MTBF (Mean Time Between Failures) o Reduce costly over-deployment of patchwork software to fill support and monitoring gaps Correlative/Predictive: Faults at any layer alert multiple workgroups and the Business/customers on related layers. A centralized and completely transparent correlation engine (NOC/SOC) instead of silos delivers granular Business service alerting and significantly drives down MTTR and increases MTBF. o Significant increase in the identification of root cause which minimizes repetition of incidents. o Decreased human errors arising from best-guess troubleshooting methodology o Enhanced client and end-user customer experiences Customer Focused: Whether in the start-up or mature business stage, we must ensure high system availability, usability, and consistency. o Reduced headcount and labor costs to cover process and technology shortcomings Accountable: Changes will be detected across the Enterprise o Reduce/eliminate client contract breach of terms leading to refunds of fees, loss of client confidence, possible adverse legal actions and the loss of Acme goodwill. Pag 11 e © Vaisala 6/27/2017 Internal use Every counts. [Name] customer Post-TOM Management, Monitoring & Alerting o Allows Acme WIS to concentrate on our core Focus: Personnel are stationed closer to our customers and focused on their core competence: our applications. Removes the burden of managing the environment, power, routers, physical servers, and circuits. competencies: our customers and our applications. o Self-healing and self-scaling systems. o Reuse of components, processes, code, data, Salable: Our Service Catalog provides the data store of record for services, costs, compatibility, sales collateral, and usage. personnel, management tools, certificates. o Minimizes human error through wholesale replacement of failed components. o Reduced headcount and labor costs to cover process and technology shortcomings o “Leap frogs” Acme into instant demonstrable Cloud compliance with 50+ global, industry, and national Every customer counts. standards. Pag 12 e © Vaisala 6/27/2017 Internal use Geo-flexible, compliant and scalable: Allows Acme to deploy a completely configured and properlysized compute environment anywhere in the world in minutes. [Name] Transition to the cloud: what we get 13 What we get Benefit Multi-geography architecture Excellent app responsiveness across the globe Satisfies governmental restrictions Reduces costs Reduces impactful maintenance windows Standards Body Certifications (ISO, FIPS, NIST) Certified compliant solutions Increased credibility and tender wins Cloud / DevOps allow for rapid prototyping Customers are able to quickly experience and evaluate the viability of solutions. Increases customer intimacy and probability customers will receive what they want the first time Capability to comply with customer security standards Improved focus on security for weather data Compliance with customer requirements Cloud allows for responsive scaling Increased margins Enhanced cost competitiveness of products Rapid and flexible input/output of data (in addition to our standard interfaces) Acme seen as flexible partner Customer does not have to be flexible or develop new, costly and unsustainable solutions Increased application resiliency and availability Less down-time Increased customer satisfaction and retention Reduce Ops headcount by 14 and reduce OpEx by 1M€ Improved profitability Increased market competitiveness HLD Highlights: • Multi-DC redundancy • Recovery strategy greatly enhanced through snapshot technology • Ability to clone entire application and run within any AWS geo – hours, not days/months • Improved security posture through east-towest security filtering 14 GLD360 Hybrid Architecture Migration Approach & Timeline 15 COST The migration bubble. Planning • Planning and assessments • Duplicate Environments • Staff Training • Migration Consulting • 3rd party tooling's Inflection Point: ROI • Lease Penalties Operation & Optimize 16 TIME Application Migration Level of Effort Very Low Low Medium High Very High 2-4 hours 4-6 hours 6-8 hours 10-14 hours 20-24 hours ✓ Basic workload ✓ Basic workload ✓ Contains multiple components ✓ Multiple components including database ✓ Multiple components including database ✓ Current/ supported OS on ✓ target Cloud Partial documented components ✓ Additional effort to document components ✓ System may include greater than five disks ✓ Complex system configuration (e.g. numerous disks) ✓ Known / documented ✓ No database ✓ No database ✓ Limited downtime permitted ✓ Contains several dependencies ✓ No database ✓ May require re-platforming ✓ (i.e. OS) Production servers likely to impact business if unavailable for an extended period of time ✓ Limited to No acceptable downtime ✓ Project to migrate with basic tools ✓ Schedule outage is OK ✓ Few dependencies ✓ Schedule outage is OK May require re-platforming ✓ (i.e. OS change / upgrade) ✓ Outage with advanced planning ✓ Require advanced detailed assessment and planning ✓ Business impact possible for production servers ✓ High-touch migration ∙ ∙ Host Cloning Live Migration ∙ ∙ Live Migration App Containerization Migration Method ∙ ∙ 17 VM Conversion Host Cloning ∙ ∙ Conversion Host Cloning ∙ ∙ Live Migration App Containerization Evaluation of effort to migration to the AWS cloud for ~600 workloads across the Acme enterprise. Mean Migration Effort Across Hosts: 8.5 hours This is a shared responsibility between Acme and the Migration Partner to keep Acme focused on running and growing the business 18 Number of Hosts Agile Migration Plan/Roadmap in Waves Effort Agile Migration Plan/Roadmap in Waves Wave 1 Wave 2 US Migration Prep US - DC to AWS connectivi ty US LDAP Thunderst orm Manager US - VPN strategy US Monitorin g US – PSTN connectivi ty US Utilities Q2 2017 Start 19 Wave 3 Wave 4 Wave 5 Wave 6 Wave 7 Wave 8 Roads US EU Migration Prep EU – DC to AWS connectivi ty EU LDAP AVICAST ttle Web Services ttle IT Services EU – VPN connectivi ty EU Monitorin g Checktime Cyclops Orochi EU – PSTN connectivi ty EU Utilities Wave 9 Wave 10 Wave 11 Wave 12 Wave 13 EU LDM EU Roads GLD360 NALDN US LDM ICE Gorgon TLP Baluar Stheno Each Wave – 2 Week Sprint + 2 days lesson learned Q2-3 2018 Completion Sprint Overview Week 1 Application Overview Meeting Week 2 Document Success Criteria Verify VPC Connectivity Review Existing Blueprints Initial Architecture Design Application Dependencies App Architecture Review Identify Testing Process Update Final Design Document VPC Architecture Design Resolve Dependencies Conflicts App Owner Review Identify Enhancement Opportunities Intra-Port Requirements Deploy AMIs Identify Application Artifacts Allocate Credentials Data Migration Requirements VPC Port Exception Verify Subnet Connectivity Connectivity Requirements Application Installation Baseline Performance Firewall Port Determination Complete Artifact Checklist 20 Verify IT Tools Connectivity Firewall Requests Migrate Data Test Application Connectivity End to End Testing Owner Sign-off Investment Summary 21 Investment Summary AWS On-Premise $1,251 $2,154 • 3 Yr on-premise costs: $7,594m • 3 Yr AWS costs: $4,528m • 1-Time Migration Services: $95K (Estimated @ $250K – Eplexity Rebate Program) Communication $738 $738 • 1-Time Software Purchase for Migration – $90K Software $263 $591 Maintenance $540 $470 • Annual Savings: $3,066m Support Staff $1,704 $3,641 $32 $72 $4,528 $7,594 Infrastructure Training Total On-premise Costs Includes HW/SW upgrades - *AWS MAP: Credits will be available to offset data center migration costs.* 22 An approximant $1M investment to current snapshot of business How do we get there: migration strategies 23 Thank you [email protected] 24