01-A Smooth Leap To Cloud, Huawei Migration Practice-V1.0
01-A Smooth Leap To Cloud, Huawei Migration Practice-V1.0
Name: Bensen
Time : 2024-12-12
Operation Process :Service Cloudification Process
Readiness For Cloudification APP Integration &Go live O&M
Requirement analysis Cloudification Solution Design Provision Implementation test & Go live Report
Integration Test
/Security Test RePonse
10 13
Cloudification Resource
Solution Approval
No
Requirement Design
Analysis 7
4 Yes
Platform 2 Requirement
Operation Assessment Resource
Team Provision
(Cloud &
Network)
3
8
Methodology of cloud migration
Migration
Cloud Plan Strategy Design Architecture Design Implementation
• Stakeholder • Feasibility analysis • Cloud platform design • Environment setup
Identification • Migration policy • Application deployment • Migration pilot
• Establish a delivery architecture design
• Migration wave • Application migration
team planning • Scalability
•
• Data migration
• Skill preparation • Risk assessment and
Availability
• Performance • Cutover and
• Kickoff Meeting contingency plan switchover
• Security
• Cost Assessment • Knowledge transfer
• Cost
Storage Information
Message MySQL • Data type and volume
Client Nginx • Numbers of small files and large files, respectively
queues Hadoop
cluster
Network and Other Application Information
Elasticsearch • Requirements for the network architecture, high
Cache Network availability (HA), disaster recovery (DR), and deployment
Application MongoDB File • Big data applications and middleware
services • Security configuration and CDN applications
System
(NFS)
Database Information
• OS, database engine, and software versions
• Total, used, and remaining database space
• Application, IP address, host name, instance name, and
physical file location
The 6 R's model for cloud migration can be used to classify cloud migration paths and define migration waves to migrate most applications of
customers to the cloud.
Increased complexity
Re-architect applications to the cloud and advantages of the cloud platform, such
recommended that purchased software support • A customer's ISV needs to take
redesign their architectures to as better scalability, faster deployment,
full charge of the migration by
deliver more extensive features higher efficiency, and improved
cloud-based deployment. and improve performance. reliability.
considering the characteristics of
Application upgrade Huawei Cloud.
• Prioritize using the services already available on (Re-platform) Customers have invested a lot in
cloud, instead of those you need to create. some applications, but the
• The configuration of an application,
• This approach may vary from
• Do not migrate abandoned and idle applications or Lift and shift Re-platform
outcome is not as expected, and
the cost is high. They want to
instead of the overall architecture,
making a few changes to
applications, up to re-
(Re-host) needs to be modified, which reduces
VMs unless a customer has this requirement. introduce some level of
optimization for these
costs.
architecture of some
components.
applications.
Constraints Retain • This is the cheapest and easiest way to
It is not recommended to migrate the applications that Customers want to migrate their migrate to the cloud. (Only OS clones,
simple applications and a large data transfer, and data copies are • Customers need to provide
cannot use cloud resources through re-platforming or Re-host
number of data files to the cloud required.) support for verification.
re-architecting due to the following constraints: Retire without major alterations. • Highly automated tools can be used in
this migration approach.
• Hardware: For example, special hardware like
encryption card and special peripherals like voice
service boards are used. Cloud Migration Paths
• Licenses: For example, the license of an application System
Manual Manual Manual data performance
closely relies on hardware, or it becomes invalid Rehost tests Cutover
installation configuration migration
after cloud resources are used.
• Third-party products: For example, fixed IP Re- Workload Data migration
System Beta and
addresses or host names are required. platform migration integration security tests
Migration tool testing
Framework Platform
• Other constraints: For example, there are modification connection
deployment
dependencies on technologies or services not Re-
supported by the cloud platform. architect
Application Environment Application Database
redesign deployment coding conversion
➢ Core databases
before those deployed in a cluster.
Application complexity
Availability design
Ensure that applications on the cloud can maintain availability,
stability, reliability, and continuity in the event of various
exceptions.
• Set the migration bandwidth based on site requirements to reduce the impact on resources in the source environment.
• Migrate services during off-peak hours.
Service • Keep the services running on source servers during data migration until the last incremental migration and service switchover are
interruptions complete.
• Ensure that both the source and destination platforms are running in active/standby mode.
• Ensure that each operation can be rolled back.
• Build a dedicated network to greatly improve network stability and accelerate migration.
Network instability • Migrate source VMs by importing images to reduce the dependency on the network, and manually synchronize incremental data.
• Apply for the migration time window and cooperate with the platform to release a notice.
• Back up the source data before migration (the customer).
Data inconsistency • Perform a full synchronization. Then, perform incremental synchronizations for multiple times to keep data consistent. Stop writing
data on source servers and perform an incremental synchronization for the last time.
• Perform sufficient performance tests before migration and optimize application and infrastructure configurations.
Service • Optimize applications running in the cloud to improve performance and response speed.
• Migrate applications in batches. Migrate a small number of key applications and data, test and verify the migration, and then
performance perform the next migration wave.
deterioration • Establish a comprehensive monitoring and troubleshooting mechanism to detect and resolve system instability. Ensure system
reliability and performance.
Survey Design
Switchover
Migration Deployment Client Huawei Cloud Stack
Small cycle
Application target
Application system 1
Verification Migration Migration architecture 1
Overall wave planning
Migration
Scenario
Cloud Service Hosting
Application (For migration Migration
or Technical Data/Incremental HCS Migration Solution Design Guideline
Component approaches, see approach
Component Data
the migration
panorama.)
Nginx Nginx on ECS No Reconfiguration; migration not required Server migration Re-host
LVS ELB No Reconfiguration; more focuses on ELB and performance issues Host migration Re-host
If the application configuration is complex and the data volume is small, server migration
Applications ECS Yes/Not sure is recommended. If the application configuration is simple, the application can be Host migration Re-host
redeployed.
If the application configuration is complex and the data volume is small, server migration Server and
Applications +
ECS+PaaS Yes/Not sure is recommended. If the application configuration is simple, the application can be middleware Re-Platform
middleware
redeployed. migration
Relational
RDS/GaussDB Yes/Yes Choose migration approaches based on database types and downtime requirements. Database migration Re-Platform
databases
Choose a migration approach matching customers' cloud requirements. Distinguish
Storage file Storage data
OBS/EVS Yes/Yes dynamic data (added, deleted, or updated) from unchanged data based on data volume, Re-Platform
system migration
and then conduct the migration.
Cache database Redis Yes/Yes Choose migration approaches based on database types and downtime requirements. Database migration Re-Platform
Big data MRS Yes/Yes Choose migration approaches based on database types and downtime requirements. Big data migration Re-Platform
Search database Elasticsearch Yes/Yes Choose migration approaches based on database types and downtime requirements. Big data migration Re-Platform
200+
OS migration
90%+ 500+ 100+
Oracle Syntax
Automatic Conversion Best practice cases Tasks parallel migration
100%
MySQL compatible
Scenarios: Cloud Server Migration/Storage Migration/Database Migration/Data Lake Migration (Data Warehouse & Lakehouse)
Automatic & Intelligent /Container Migration
1 Install an agent.
5 Replace the drive. Advantages
2 Create and
start a VM.
• High source compatibility:
200+ common OS versions are supported.
Scenarios
• Object storage data compatible with the standard
Amazon S3 protocol needs to be migrated to Huawei
HCS Cloud Stack OBS.
IDC/3rd public cloud
HSMS Advantages
• Scheduled traffic control makes full use of bandwidth
while ensuring service stability.
Scenarios
Application • Oracle -> GaussDB
• MySQL -> RDS for MySQL
DRS: Traffic Replay Performance
SQL Recording SQL Replay Report Key Steps
1. Migration survey and 7. Service logic migration
SQL Cache File
evaluation 8. Application migration and
2. Migration solution design rewriting
3. Migration drill 9. Data verification and
4. User, role, and permission service test
Agent
UGO migration 10.Performance tuning
5. Schema migration 11.Rollout and cutover
Syntax analysis
Oracle 6. Data migration 12.Trial run assurance
GaussDB Advantages
• One-stop tools support smooth service migration.
Full migration
Schema
SQL file
Conversion process Scenarios
• Teradata -> DWS
ETL script Import files. Convert syntax using Verify
the SQL translator Export files.
conversion syntax.
from Teradata.
PREL file
Key Steps
1. Migration survey and 6. Self-evaluation
Source Destination evaluation 7. Data migration
database Export data using GSDump database 2. Migration solution design 8. Data verification and
Migration4DWS and import data using 3. Migration drill service test
GaussDB GSQL.
Export data using JDBC
4. Grammar transform 9. Performance tuning
and import data using Destination 5. Metadata migration 10.Rollout and cutover
Metabase migration GSQL.
metabase
Export data using Tbuilder and
Teradata import data using GSQL.
Key Steps
Load ELB
balancer 1. Plan resources for a target cluster.
2. Migrate resources outside a source cluster to the
IDC on-premises cluster A 3. Install migration tools. Container 1. Plan resources target cluster.
for a target cluster.
cluster 3. Install migration tools.
Service Service 4. Migrate resources within the source cluster to the
5. Update resources target cluster.
accordingly.
5. Update resources accordingly.
Deployment Application Application Deployment
Backup files 6. Verify services, switch traffic, and bring the source
StatefulSet backup restoration StatefulSet
...
... cluster offline.
• Service interruption
RVTools Migration4MRS • Final synchronization
Survey Switchover •
Migration tool center Service verification
• Service rollout
VMware Information input Huawei Cloud Stack
Design
HCS Designer Migration4DWS
1. Professional architecture design: cloud architecture survey and planning, provided by professional teams
2. Huawei Cloud Stack one-stop migration center: tools supporting migration of hosts, containers, storage, databases, and big data
3. Professional migration services: end-to-end assurance for survey, planning, migration, and switchover
Top 1
On-premises cloud service provider in China
Orange is the largest operator in Cote d'Ivoire and provides wireless and wired services nationwide.
Orange has five distributed data centers, mainly physical servers and virtualization, resource utilization rate is low.
60%↑
↑ 50%+
Complex O&M 20%
Lumiere DC 5-year TCO Resource Usage O&M Efficiency
Five distributed data centers,
physical servers, virtualization from
multi vendor, difficult to manage Villa DC KM4 DC Cloud-Powered Strategy
DC Consolidation ➢ Cloud First transformation, align with Orange’s strategy to digital,
efficient and agile operations
High TCO RP DC Yakro DC
One-stop Cloud Migration
Server virtualization on the live
Cloud Migration ➢ One-stop migration tools and services to support smooth
network is less than 30%, Low
resource utilization migration of core applications: 30+ PMs, 1900+ VMs, 30+ OS
➢ Online and incremental migration, maximum concurrent task 100