Shulou(Shulou.com)06/02 Report--

The Age of the Cloud:

The cloud era has come. After choosing the cloud, the first question for enterprises is how to migrate to the cloud. This will affect the migration cycle and the business service quality after migration, so the migration must be in accordance with a certain methodology and process, rather than blind migration. The most basic is to follow these five processes: planning, design, migration, operation and optimization, in which you can fine-tune according to your actual business situation.

Of all the cloud vendors, AWS has the most complete migration methodology. For example, CAF (using the cloud framework), LandingZone,Well-architected (good architecture) and three-day migration training courses can make you realize what kind of model it will be like to use the cloud and solve your questions during use. Personally, I think it is more critical for a beginner of AWS to learn the methodology of CAF, which will give you a deeper experience with the cloud.

Using our past experience for reference, we suggest that customers study more professional terms in AWS after having a small amount of application on Well-architected,Well-architected. We suggest that we can carry out simple application practice after preliminary understanding, and constantly consolidate knowledge points in the later stage of practice in order to grasp the essence of this part. Of course, there is also a way to shorten the study time, that is to choose an experienced AWS Partner to give a detailed explanation and accompany you to the cloud practice, they will tell you what is the best practice according to the health of your business.

Practice sharing:

Based on a summary of the practices we have experienced in a large number of migrations, let's share the two most critical stages in the migration process, planning and design. They are the most basic part of the whole migration, just like the foundation of a building. We will discuss how to do a good job in these two stages in detail. I hope it will be helpful to you and your business.

1) Plan:

It is recommended that you make a migration priority list before planning, which must contain several core fields, such as operating system version / actual data volume / application provider / business dependent services / technical complexity / RTO/RPO, etc., which determine which migration model (smoothing / replacement / refactoring) and what migration tools you choose. Because they affect the length and effectiveness of your migration cycle (of course, some enterprises also have some special metrics, such as compatibility (the possibility of moving to other clouds). Please complete this form before making the overall migration plan, instead of planning without any basis.

According to the above indicators, you may feel that the operating system version is not important, in fact, it is very important, first of all, it is necessary to know whether AWS supports this kind of AMI, and if AWS does not provide it, is there Marketplace and the community? (if you are very concerned about security, it is recommended not to use community AMI.) you can also choose to make your own AMI (choose Vmware method), and our suggestion is to use AMI provided by AWS, so that performance, stability, function and troubleshooting will be more reliable. To take an example of the communications industry that we have practiced, customers have conducted a simple functional test of AMI before going to AWS, but not the performance test of the AMI of CentOS in which they modified the kernel in On-premises. Various faults are found during the performance test after the actual migration, and the after-sales technology of AWS can not be solved at this time. Based on our experience, we recommend that you try to use the AMI provided by AWS, and if you do have very strict requirements for AMI, then please do all the necessary tests. Application provider, which plays a decisive role in whether applications can be migrated, such as: License, version and software provider still exist? Business depends on services, this indicator describes the data interaction between businesses, the tight coupling relationship between businesses, how much service data exists between them, or they are just data providers of other businesses. Please note that "in fact, sometimes other businesses just rely on the database data of this business, not on the business itself," so it doesn't matter whether the business exists or not. RTO/RPO, this indicator will determine the migration cost, to keep the business uninterrupted, the more expensive the migration cost. According to our practical experience, RTO/RPO is more suitable for disaster recovery and backup scenarios. In migration scenarios, we think that the time of business interruption is more critical, because this is the time used for data synchronization and business switching. The most important thing is: "Please do not think that your business will never be interrupted" (this results in a waste of migration costs, or even non-migration). There are three related factors that determine the length of migration time: data synchronization technology, network bandwidth and data volume.

Take the above indicators, as well as the indicators required by the customer, do relevant evaluation and verification (the "design" of the next stage is the most important verification test of the "plan" at this stage) in order to determine the priority of business migration, the mode of business migration, the tools of business migration, and the time of business migration.

2) Design:

After having the above comprehensive migration priority list, architecture design and verification testing will be carried out at this stage to ensure that the migration model, migration tools and migration priority are correctly selected, which also shows that the design and plan are the connecting link between the preceding and the following. Not independent. Through the business analysis and evaluation during the planning phase, you can already design the appropriate architecture and conduct relevant verification tests (which is very important in the cloud era) in order to adjust the migration priority and migration model. The more businesses are validated at this stage, the less risk and time is involved in the migration phase. For example, one of our customers in the high-tech manufacturing industry, after a detailed evaluation and analysis of the existing business architecture of a cloud manufacturer with us before AWS, has come to the conclusion that their most critical verification tests are EC2-based K8S and network VPC, so they are fully tested, such as the License validity period of K8S, the Autoscaling,K8S of K8S is divided into different business groups and the network test of K8S. And do some critical business migration tests. Due to full testing in the design phase, the formal migration saves two weeks. If possible, it is recommended to use a verification test environment at 1:1 with the production environment. After the verification is completed, the resources can be Stop, and only part of the resources are charged, such as EBS, EIP, S3, etc. For those resources that must be deleted, you can choose to make a backup in preparation for the formal migration, and you can use Cloudformation to make templates, which can reduce the preparation work for the formal migration.

Summary of practice:

Many enterprises like to perform the migration with or without verification, and encounter a variety of problems in the execution process, some of which make them unable to continue and have to start from scratch. From our past experience, it is recommended that it is best to migrate simple businesses to the cloud first, preferably smoothly, and to be fully prepared for verification testing in the first two stages. Design a data synchronization method for some services that are really uninterruptible (in fact, DNS domain name switching still needs to be interrupted for a few minutes) (mainly database data synchronization, you can use AWS DMS or third-party software specifically for database real-time synchronization). There will be a certain delay in data synchronization, taking into account the delay range that the business can bear. Be sure to remember and understand that there is a strict relationship between each stage.

The three stages of migration, operation and optimization are also very critical, and if you are fully prepared in the first two stages of migration, it will be relatively easy to migrate. You only need to pay attention to risk assessment and personnel assignment. Operation and optimization belong to the advanced stage. The business after migration is gradually optimized in terms of stability, performance, security, availability and cost. If there are any mistakes in this article, please correct them. Thank you! )

Refer to the learning address:

Https://d0.awsstatic.com/whitepapers/AWS_CAF_Security_Perspective.pdf

Https://aws.amazon.com/cn/architecture/well-architected/

[about Bosiyun]

As a professional cloud computing service enterprise, Bosiyun provides operational services on AWS: including architecture consulting services, migration services, cloud security integration services, hybrid cloud management services, big data services and DevOps services. At present, Bosiyun has obtained manufacturer certification in big data, DevOps, architecture, database and operating system, and has branches in Shanghai, Nanjing, Hangzhou, Wuhan and other places. In order to innovate the service model and lead the development of IT service industry, Bosiyun will continue to invest resources to carry out the research and development of intelligent hybrid cloud management platform and map database.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.