CN113301089B - A cloud service node deployment method and device - Google Patents

Abstract

The application provides a cloud service node deployment method and device, wherein the method comprises the following steps: acquiring a cloud service instance purchase request of a user; responding to the instance purchase request, and acquiring a main available area deployment mode and a standby available area deployment mode which are designated by a user, wherein the main available area deployment mode and the standby available area deployment mode are designated by the user respectively; and deploying the main nodes according to the main available area deployment mode, and deploying the standby nodes according to the standby available area deployment mode. The problems of low flexibility and low resource utilization rate caused by the existing active-standby available area combination deployment are solved through the scheme, and the technical effects of effectively improving the deployment flexibility and the resource utilization rate are achieved.

Description

A cloud service node deployment method and device

Technical Field

The present application belongs to the field of cloud service technology, and in particular, relates to a cloud service node deployment method and device.

Background technique

Application service providers usually purchase some cloud services to assist in the effective operation of their own application services. For example, database services. For cloud services, there is usually only one service node to provide services to users. In order to ensure the high availability of cloud services, a master node is usually deployed in a certain availability zone to provide services, and then one or more standby nodes are deployed in other availability zones. The data of the standby node is generally synchronized from the master node through the network, and the data and configuration in the standby node are consistent with the master node. When the master node fails while providing services, the cloud service platform will perform disaster recovery switching, switch the standby node to the master node, and continue to provide services to users through the switched master node.

Currently, for the selection of multiple availability zones, cloud service platforms generally preset some combinations of availability zones, and users select from these combinations when requesting an availability zone.

However, deploying availability zones in this way will lead to inflexible deployment and low resource scheduling efficiency. Currently, no effective solution has been proposed for the problems existing in the deployment of the above-mentioned combined availability zones.

Summary of the invention

The purpose of the present application is to provide a cloud service node deployment method and device to solve the problems of low success rate and low resource scheduling efficiency in the existing combined availability zone deployment.

The present application provides a cloud service node deployment method and device which are implemented as follows:

A cloud service node deployment method, comprising:

Obtain the user's cloud service instance purchase request;

In response to the instance purchase request, obtaining a primary availability zone deployment mode and a backup availability zone deployment mode specified by a user, wherein the primary availability zone deployment mode and the backup availability zone deployment mode are respectively specified by the user;

Deploy the master node according to the deployment mode of the primary availability zone, and deploy the standby node according to the deployment mode of the standby availability zone.

A cloud service node deployment method, comprising:

Receive a cloud service instance purchase request from a user;

In response to the instance purchase request, displaying an availability zone deployment selection interface, wherein the availability zone deployment selection interface includes: a primary availability zone deployment mode selection area and a backup availability zone deployment mode selection area;

Receive the user's selected operation in the primary availability zone deployment mode area and the user's selected operation in the backup availability zone deployment mode area, and use the selected items corresponding to the selected areas as the primary availability zone deployment mode and the backup availability zone deployment mode specified by the user;

The primary availability zone deployment mode and the backup availability zone deployment mode specified by the user are carried in the cloud service instance purchase request and sent to the cloud platform management system.

A cloud service node deployment device, located in a cloud platform management system, includes:

A first acquisition module is used to acquire a user's cloud service instance purchase request;

A second acquisition module is used to respond to the instance purchase request and acquire a primary availability zone deployment mode and a backup availability zone deployment mode specified by a user, wherein the primary availability zone deployment mode and the backup availability zone deployment mode are respectively specified by the user;

The deployment module is used to deploy the master node according to the deployment mode of the primary availability zone and deploy the standby node according to the deployment mode of the standby availability zone.

A cloud service node deployment device, located in a terminal, comprising:

A first receiving module, configured to receive a cloud service instance purchase request from a user;

A display module is used to display an available zone deployment selection interface in response to the instance purchase request, wherein the available zone deployment selection interface includes: a primary available zone deployment mode selection area and a backup available zone deployment mode selection area;

The second receiving module is used to receive the user's selection operation in the primary availability zone deployment mode area and the user's selection operation in the backup availability zone deployment mode area, and use the selection items corresponding to the selected areas as the primary availability zone deployment mode and the backup availability zone deployment mode specified by the user;

The sending module is used to carry the primary availability zone deployment mode and the backup availability zone deployment mode specified by the user in the cloud service instance purchase request and send them to the cloud platform management system.

A server device includes a processor and a memory for storing instructions executable by the processor, wherein the processor implements the following method steps when executing the instructions:

Obtain the user's cloud service instance purchase request;

In response to the instance purchase request, obtaining a primary availability zone deployment mode and a backup availability zone deployment mode specified by a user, wherein the primary availability zone deployment mode and the backup availability zone deployment mode are respectively specified by the user;

Deploy the master node according to the deployment mode of the primary availability zone, and deploy the standby node according to the deployment mode of the standby availability zone.

A terminal device comprises a processor and a memory for storing instructions executable by the processor, wherein when the processor executes the instructions, the steps of the following method are implemented:

Receive a cloud service instance purchase request from a user;

In response to the instance purchase request, displaying an availability zone deployment selection interface, wherein the availability zone deployment selection interface includes: a primary availability zone deployment mode selection area and a backup availability zone deployment mode selection area;

Receive the user's selected operation in the primary availability zone deployment mode area and the user's selected operation in the backup availability zone deployment mode area, and use the selected items corresponding to the selected areas as the primary availability zone deployment mode and the backup availability zone deployment mode specified by the user;

The primary availability zone deployment mode and the backup availability zone deployment mode specified by the user are carried in the cloud service instance purchase request and sent to the cloud platform management system.

A computer-readable storage medium having computer instructions stored thereon, wherein the instructions, when executed, implement the steps of the method described below:

Obtain the user's cloud service instance purchase request;

In response to the instance purchase request, obtaining a primary availability zone deployment mode and a backup availability zone deployment mode specified by a user, wherein the primary availability zone deployment mode and the backup availability zone deployment mode are respectively specified by the user;

Deploy the master node according to the deployment mode of the primary availability zone, and deploy the standby node according to the deployment mode of the standby availability zone.

A computer-readable storage medium having computer instructions stored thereon, wherein the instructions, when executed, implement the steps of the following method:

Receive a cloud service instance purchase request from a user;

In response to the instance purchase request, displaying an availability zone deployment selection interface, wherein the availability zone deployment selection interface includes: a primary availability zone deployment mode selection area and a backup availability zone deployment mode selection area;

Receive the user's selected operation in the primary availability zone deployment mode area and the user's selected operation in the backup availability zone deployment mode area, and use the selected items corresponding to the selected areas as the primary availability zone deployment mode and the backup availability zone deployment mode specified by the user;

The primary availability zone deployment mode and the backup availability zone deployment mode specified by the user are carried in the cloud service instance purchase request and sent to the cloud platform management system.

The cloud service node deployment method and device provided by the present application, when a user requests to purchase a cloud service instance, the primary availability zone deployment mode and the backup availability zone deployment mode are separately specified by the user, rather than adopting a primary and backup availability zone combination mode. This method solves the problems of low flexibility and low resource utilization caused by the existing primary and backup availability zone combination deployment, and achieves the technical effect of effectively improving deployment flexibility and resource utilization.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

FIG1 is an architecture diagram of a cloud service node deployment system provided by the present application;

FIG2 is a schematic diagram of an existing combination deployment method of available zones provided by the present application;

FIG3 is a deployment diagram of selecting a primary availability zone and a backup availability zone respectively provided by the present application;

FIG4 is a schematic diagram of a deployment of randomly selected primary availability zones and backup availability zones provided by the present application;

FIG5 is a schematic diagram of a deployment in which both primary and backup availability zones are randomly deployed as provided by the present application;

FIG6 is a schematic diagram of deployment of a backup availability zone and a primary availability zone in the same zone provided by the present application;

FIG7 is a method flow chart of a cloud service node deployment method provided by the present application;

FIG8 is a method flow chart of a cloud service node deployment method provided by the present application;

FIG9 is a diagram showing the architecture of a computer terminal provided by the present application;

FIG10 is a structural block diagram of the cloud service node deployment device provided in the present application.

Detailed ways

In order to enable those skilled in the art to better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.

When publishing service applications, application or service publishers often need to request some services from the cloud platform, such as cloud storage services. To this end, the cloud platform can provide a service purchase page, where users can log in to purchase the required services (such as cloud computing services, cloud storage services, etc.). When purchasing services, users only need to select the region and the deployment method of the primary and backup nodes.

The master node is the node that provides user services for cloud product instances, and the backup node is the disaster recovery node of the master node. It has the same data and configuration as the master node and is used to replace the master node to provide services when the master node fails. For nodes, they are set in the availability zone. The availability zone where the master node is located is called the primary availability zone, and the availability zone where the backup node is located is called the backup availability zone.

As shown in FIG. 1 , a cloud service node deployment system is provided, which may include: a client 101 , a cloud platform management system 102 , and a to-be-deployed area 103 .

The client 101 may provide a service purchase interface to the user. The user logs into the service purchase interface and may select a region and a node deployment mode, thereby triggering the purchase of the service.

The cloud platform management system 102 can be a single cloud server or a cloud server cluster, which is used to receive user selections, deploy service nodes in the area to be deployed according to the user's selections, and centrally manage and control each availability zone in the area to be deployed during the service provision phase.

The area to be deployed 103 may include multiple regions, where a region is the physical location of a cloud vendor's data center (such as Region A, Region B, and Region C in FIG1 ), each region has a data center, and each region generally has multiple availability zones (such as Availability Zone 1, Availability Zone 2, etc. in FIG1 ). The cloud platform management system 102 may determine in which availability zone of which region to deploy the master node, and in which availability zone to deploy the standby node, based on the user's selection.

The above-mentioned cloud platform management system 102 may include: the cloud service sales page and cloud vendor management system in Figure 2, wherein the cloud service sales page is a page for users to purchase cloud services, and users can choose to purchase cloud services in different regions through the cloud service sales page; the cloud vendor management system is a system for users to operate and manage cloud services, which may include: a metadata database for recording cloud service information configuration, a resource management service for user resource scheduling, a high-availability service for ensuring high availability of cloud services, and other management services. Specifically, the metadata database is used to record the basic information of cloud product instances, and also records the availability zone deployment information of the instances; the resource scheduling service is used to integrate and schedule the computing resources of the data center and manage the underlying resources for cloud products; the high-availability service will intervene when an abnormality occurs in a cloud product to try to ensure that the services provided by the product are not affected.

As shown in FIG. 2 , the data center is a cloud vendor data center in a certain region of the above-mentioned area to be deployed 103 , which is used to provide computing and storage resources for user services and cloud services. Both user services and cloud services are deployed in the data center.

In order to allow users to select availability zones for deployment, the existing platforms generally provide multiple combinations of availability zones, and then users select availability zones from these combinations for resource scheduling and deployment to corresponding service applications. That is, as shown in Figure 2, multiple combinations are pre-set for availability zone selection: multiple availability zones (A+B), multiple availability zones (A+C), and multiple availability zones (B+C). When users purchase cloud services, they can only choose from these preset combinations. This results in the user being unable to configure the primary availability zone when they need to, and can only choose from these combinations, and cannot flexibly set it themselves, which results in low flexibility and accuracy in deployment configuration.

Specifically, the above method of only being able to select from preset combinations mainly has the following problems:

1) The combination needs to be pre-configured, the configuration operation is relatively complicated, and the configured combination needs to be maintained. In general, the number of combinations that can be provided in a region is very limited, which makes it difficult to meet the various deployment requirements of different users.

2) Users can only select a combination (for example, they can only choose to deploy in two availability zones, A and B), but cannot specify in which availability zones the master node and the standby node are located. For example, if A+B availability zones are selected, the master node may be in A or B. If the user's application service is deployed in A, and the user hopes that the master node of the cloud service provided by the cloud platform is also in A, this method cannot be implemented, resulting in the user's service being deployed in a different availability zone from the master node.

3) The resource scheduling scope of this combination of availability zones must be the availability zones in the corresponding combination of availability zones, for example: A+B availability zones. In this case, resources can only be allocated in availability zones A and B. If there are no resources in one availability zone, the allocation will fail, which will lead to a sales failure. That is, the probability of a successful sale of an availability zone will be reduced.

In response to the problems existing in the preset combined availability zones, this example provides an availability zone setting method, which gives the user the right to choose the primary and backup availability zones. That is, the user can select the setting method of the primary availability zone as needed (for example, specifying a certain availability zone as the primary availability zone, or selecting a randomly set availability zone as the primary availability zone), and can select the setting method of the backup availability zone as needed (for example, specifying a certain availability zone as the backup availability zone, or selecting a randomly set availability zone as the backup availability zone). That is, the primary and backup availability zones are set separately. After the user sets the primary and backup availability zones, the back-end system manages them according to the user's selection.

Specifically, as shown in FIG3, the cloud service sales page may be displayed as shown in FIG3, including: region selection items, primary availability zone selection items, and backup availability zone selection items. Among them, the region selection items may include: Hangzhou, Beijing, Shanghai and other region identifiers, and the user clicks to determine the physical location of the desired cloud vendor data center. For example, if the user clicks "Hangzhou" as the selected region, multiple availability zones under the "Hangzhou" region can be displayed in the primary and backup availability zone selection items.

There are multiple options in the primary availability zone option, which are mainly divided into: random and multiple availability zones. Among them, selecting random means that an availability zone can be randomly selected from multiple availability zones in the Hangzhou region as the primary availability zone. The user does not care about the location of the primary availability zone. If random is not selected, the user needs to select an availability zone from multiple availability zones as the primary availability zone (for example: availability zone A). In this case, the backend system needs to set the master node in availability zone A and maintain this setting all the time.

There are multiple options in the backup availability zone option, which are mainly divided into: random and multiple availability zones. Among them, selecting random means that an availability zone can be randomly selected from multiple availability zones in the Hangzhou region as the backup availability zone. The user does not care about the location of the backup availability zone. If random is not selected, the user needs to select an availability zone from multiple availability zones as the backup availability zone (for example: availability zone B). In this case, the backend system needs to set the backup node in availability zone B and maintain this setting all the time.

That is, the user can set the region, primary availability zone, and backup availability zone as shown in Figure 3. When the backend management and control system receives the user's request, it will deploy the nodes according to the primary and backup node deployment method selected by the user.

According to different usage requirements, there may be but are not limited to the following situations:

Case 1:

Some users' services are deployed in multiple availability zones, and users want to perform disaster recovery management for the services. In this case, the availability zone deployment of the cloud product must be consistent with the service. For example, if the user's service is deployed in availability zone A and availability zone B, then the user wants the cloud product's master node to be deployed in availability zone A and the standby node to be deployed in availability zone B.

This situation can be shown in Figure 3:

After the user selects the region, the primary availability zone will select availability zone A, and the backup availability zone will select availability zone B. That is, the user selects the primary availability zone A + backup availability zone B. After the selection, this selection information will enter the cloud vendor's management and control system for management, and this selection information will be recorded in the metadata database. Correspondingly, the cloud vendor's management and control system will be deployed in the data center, that is, the primary node will be deployed in availability zone A, and the backup node will be deployed in availability zone B. During the operation and maintenance of the database instance, relevant operations will be performed based on the configuration recorded in the metadata database to ensure that the availability zone deployment method of the user instance remains unchanged. Specifically, under this setting:

1) When the master node fails, the high-availability system will promptly switch to the backup database. After the master node automation system is repaired, the node in availability zone A will be reset to the master node within the user-configured maintenance time to provide services, thereby ensuring that the instance's availability zone deployment remains unchanged;

2) When upgrading the specifications of a database instance or migrating an instance, it is also necessary to ensure that the instance's availability zone deployment remains unchanged, that is, deploy the primary node in availability zone A and the standby node in availability zone B.

Case 2:

Sometimes users only care about the deployment location of the master node, not the deployment location of the standby node. In this case, users only need to select the availability zone corresponding to the master node, and can choose to randomly deploy instance nodes for the standby node. For example, many of the user's services are deployed in availability zone B, so the user wants to deploy the master node in availability zone B and the standby node can be randomly deployed.

This situation can be shown in Figure 4:

After the user selects the region, the primary availability zone will select availability zone B, and the backup availability zone will select a random one. That is, the user selects the primary availability zone B + the backup availability zone randomly. After the selection, this selection information will enter the cloud vendor's management and control system for management, and this selection information will be recorded in the metadata database. Correspondingly, the cloud vendor's management and control system will be deployed in the data center, that is, the primary node will be deployed in availability zone B, and the backup node will be deployed randomly (for example, it can be deployed in availability zone C, A, or B). During the operation and maintenance of the database instance, relevant operations will be performed based on the configuration recorded in the metadata database to ensure that the primary availability zone deployment of the user instance remains unchanged and the backup availability zone is deployed randomly.

When random availability zone deployment is selected, resource scheduling only needs to evaluate all availability zones in the region and then select an availability zone with sufficient resources for deployment.

It is worth noting that the cloud platform is unaware of the availability zone location of the user service. Only the user knows it. There is no correlation between the availability zone where the user service is located and the availability zone where the primary and standby nodes are located. The availability zones of the primary and standby nodes are deployed only based on user settings.

Case 3: The user only needs a cloud database instance that is accessible from the public network and does not care about the availability zones where the primary and standby nodes are deployed. In this case, the user can choose to randomly deploy both the primary and standby nodes of the instance.

This situation can be shown in Figure 5:

After the user selects the region, both the primary and backup availability zones will be randomly selected. That is, the user selects the primary availability zone randomly + the backup availability zone randomly. After the selection, this selection information will enter the cloud vendor's management and control system for management, and this selection information will be recorded in the metadata database. Correspondingly, the cloud vendor's management and control system will deploy in the data center, that is, the primary node deployment will be randomly deployed (for example, it can be deployed in availability zone C, A, or B), and the backup node will be randomly deployed (for example, it can be deployed in availability zone C, A, or B). During the operation and maintenance of the database instance, relevant operations will be performed based on the configuration recorded in the metadata database, that is, the primary and backup nodes are randomly deployed.

When random availability zone deployment is selected, resource scheduling only needs to evaluate all availability zones in the region and then select an availability zone with sufficient resources for deployment.

It is worth noting that the cloud platform is unaware of the availability zone location of the user service. Only the user knows it. There is no correlation between the availability zone where the user service is located and the availability zone where the primary and standby nodes are located. The availability zones of the primary and standby nodes are deployed only based on user settings.

By introducing the random deployment method, all operation and maintenance operations on the database instance do not need to excessively maintain the availability zone where the node was deployed previously, which can optimize resource integration.

Case 4: For some performance-sensitive users who do not have much demand for cross-zone disaster recovery, the primary and backup nodes of the cloud service can be deployed in the same zone to reduce the performance loss caused by network latency between different zones.

This situation can be shown in Figure 6:

After the user selects the region, the available zones for the primary zone and the backup zone are displayed. In order to meet user needs, an option "Deploy in the same zone as the primary zone" is added to the backup zone in Figure 6. If the user chooses to deploy the backup zone in the same zone as the primary zone, if the primary zone is selected as zone A, then the backup zone is also zone A. If the primary zone is randomly deployed, then the backup zone follows the primary zone. If the primary zone is randomly deployed to zone B, then the backup zone is also deployed to zone B. If the primary zone is randomly deployed to zone C, then the backup zone is also deployed to zone C. The user's selection is stored in the metadata database. During the operation and maintenance of the database instance, relevant operations are performed based on the configuration recorded in the metadata database, that is, the backup zone is deployed in the same zone as the primary zone.

In the above example, the primary and backup availability zones can be specified separately or randomly selected, and the backend system manages them according to the user settings.

Specifically, for the selection of primary and backup availability zones in the cloud service sales page in Figures 3 to 6, the availability zone options can be displayed simultaneously with the region, or can be displayed after the region is selected. For example, after the user selects the region "Hangzhou", the cloud vendor management and control system determines which availability zones in the data center under the Hangzhou region have sufficient resources, and displays the availability zones with sufficient resources as selectable availability zones in the selection area. For example, if it is determined that availability zones A and C are sufficient in resources, and availability zone B is insufficient in resources, then availability zones A and C can be displayed, but availability zone B is not displayed. It is also possible to directly display all availability zones in the data center under the Hangzhou region, and then determine whether the availability zone resources are sufficient when the node is deployed. The specific method can be selected according to needs.

However, it is worth noting that the above-mentioned scene drawings and embodiments are only exemplary descriptions. The display method, display order, and regional selection of the actual cloud service sales page can be modified to a certain extent according to actual needs and circumstances, and this application does not limit this.

When users choose to deploy the availability zone randomly, all operation and maintenance operations on the database instance do not need to maintain the availability zone where the node was deployed too much, which is conducive to the integration and optimization of resources. Because users can freely choose to combine the availability zones according to their service needs, it solves the problem of limited number of combinations that need to be pre-configured. For the availability zone where the user specifies the node deployment, the cloud service backend will record the user's specified configuration, and the relevant operation and maintenance operations will ensure that the user's node availability zone deployment remains unchanged to meet the user's expectations, solving the problem of unclear node deployment availability zone. In the case of user random node deployment availability zone, node deployment is unbound from the availability zone, so that any availability zone with resources in the region can be flexibly selected, and resource scheduling efficiency is higher, thereby improving the sales success rate. In the case of random node deployment availability zone, resource scheduling can be carried out between different availability zones, thereby reducing resource fragmentation caused by unequal resources in different availability zones and improving resource utilization. Because resources are selected from multiple availability zones instead of in one availability zone, the resource pool is equivalent to becoming larger, which can improve the sales success rate of cloud products; different availability zones can be freely combined to meet the diverse needs of users.

Figure 7 is a method flow chart of an embodiment of a cloud service node deployment method described in the present application. Although the present application provides method operation steps or device structures as shown in the following embodiments or drawings, more or fewer operation steps or module units may be included in the method or device based on routine or no creative labor. In the steps or structures where there is no necessary causal relationship logically, the execution order of these steps or the module structure of the device is not limited to the execution order or module structure described in the embodiments of the present application and shown in the drawings. When the method or module structure is applied to an actual device or terminal product, it can be connected according to the method or module structure shown in the embodiment or drawings for sequential execution or parallel execution (for example, a parallel processor or a multi-threaded processing environment, or even a distributed processing environment).

Specifically, as shown in FIG7 , a cloud service node deployment method provided by an embodiment of the present application may include:

Step 701: Obtain a user's cloud service instance purchase request;

That is, when users publish their own services, they sometimes need to purchase cloud services, such as cloud database services, etc. At this time, users can log in to the cloud service sales page to purchase cloud services.

Step 702: In response to the instance purchase request, obtaining a primary availability zone deployment mode and a backup availability zone deployment mode specified by the user, wherein the primary availability zone deployment mode and the backup availability zone deployment mode are respectively specified by the user;

When purchasing cloud services, users are generally required to select the primary and backup availability zones. The existing sales methods generally use a primary and backup combination, which results in relatively limited choices and can easily lead to sales failures due to insufficient resources. Therefore, in this example, the primary and backup availability zone deployment methods are specified by the user, and random deployment methods and fixed node deployment methods are introduced in the deployment methods.

That is, multiple selection methods are provided. For the availability zone where the user specifies the node deployment, the cloud service backend will record the user's specified configuration, and the relevant operation and maintenance operations will ensure that the user's node availability zone deployment remains unchanged to meet user expectations, solving the problem of unclear node deployment availability zone. In the case of random node deployment availability zones, the node deployment is unbound from the availability zone, so that any availability zone with resources in the region can be flexibly selected, and resource scheduling efficiency is higher, thereby improving the sales success rate. In the case where the node deployment availability zone can be random, resource scheduling can be performed between different availability zones, thereby reducing resource fragmentation caused by unequal resources in different availability zones and improving resource utilization.

Step 703: deploy the master node according to the deployment mode of the primary availability zone, and deploy the standby node according to the deployment mode of the standby availability zone.

The above-mentioned primary availability zone deployment method may include but is not limited to at least one of the following: random deployment, deployment in a user-specified availability zone; the above-mentioned backup availability zone deployment method may include but is not limited to at least one of the following: random deployment, deployment in a user-specified availability zone, and deployment in the same zone as the primary availability zone.

In order to solve the problem of unclear node deployment availability zones, the cloud service backend will record the user's specified configuration, and related operation and maintenance operations will ensure that the user's node availability zone deployment remains unchanged to meet user expectations. Specifically, after obtaining the primary availability zone deployment method and backup availability zone deployment method specified by the user, the primary availability zone deployment method and backup availability zone deployment method specified by the user can be stored; when operating and maintaining the user's cloud service instance, operations are performed according to the primary availability zone deployment method and backup availability zone deployment method specified by the user to ensure that the primary availability zone deployment method and backup availability zone deployment method of the cloud service instance specified by the user remain unchanged.

In the case of random node deployment in the availability zone, the node deployment is unbound from the availability zone, so that any availability zone with resources in the region can be flexibly selected, and resource scheduling efficiency is higher, thereby improving the success rate of sales. In the case where the node deployment availability zone can be random, resource scheduling can be performed between different availability zones, thereby reducing resource fragmentation caused by unequal resources in different availability zones and improving resource utilization. To this end, in the case where the user selects the primary availability zone deployment method for random deployment, deploying the master node according to the primary availability zone deployment method may include: randomly selecting an availability zone with resources from the availability zone as the primary availability zone to deploy the master node. That is, randomly selecting an availability zone from the availability zones with sufficient resources as the primary availability zone or the backup availability zone for deployment.

Considering that data centers are divided by region, users need to select a region when purchasing cloud services, and the primary and backup availability zones are also availability zones under the selected region. That is, in response to the instance purchase request, obtaining the primary availability zone deployment mode and the backup availability zone deployment mode specified by the user may include: in response to the instance purchase request, obtaining the region selected by the user; returning the availability zones under the region selected by the user for selection by the user; receiving the primary availability zone deployment mode and the backup availability zone deployment mode specified by the user.

When returning the available zones in the region selected by the user, all available zones in the region selected by the user can be traversed; the available zones with resource values greater than the preset resource amount are determined; and the available zones with resource values greater than the preset resource amount are returned as available zones in the region selected by the user for selection by the user. For example, after the user selects the region "Hangzhou", the cloud vendor management and control system determines which available zones in the data center in the region of Hangzhou have sufficient resources, and displays the available zones with sufficient resources as selectable available zones in the selection area. For example, if it is determined that available zones A and C have sufficient resources, and available zones B have insufficient resources, then available zones A and C can be displayed, but available zone B is not displayed. It is also possible to directly display all available zones in the data center in the region of Hangzhou, and then determine whether the available zone resources are sufficient when the node is deployed. The specific method can be selected according to needs.

For the user terminal, a cloud service node deployment method is provided, which can be shown in FIG8 and includes the following steps:

Step 801: receiving a cloud service instance purchase request from a user;

Step 802: In response to the instance purchase request, display an availability zone deployment selection interface, wherein the availability zone deployment selection interface includes: a primary availability zone deployment mode selection area and a backup availability zone deployment mode selection area;

Step 803: receiving the user's selection operation in the primary availability zone deployment mode area and the user's selection operation in the backup availability zone deployment mode area, and using the selection items corresponding to the selected areas as the primary availability zone deployment mode and the backup availability zone deployment mode specified by the user;

Step 804: The primary availability zone deployment mode and the backup availability zone deployment mode specified by the user are carried in the cloud service instance purchase request and sent to the cloud platform management system.

In the above step 802, the primary availability zone deployment method may include but is not limited to at least one of the following: random deployment, deployment in a user-specified availability zone. The backup availability zone deployment method may include but is not limited to at least one of the following: random deployment, deployment in a user-specified availability zone, and deployment in the same zone as the primary availability zone.

Specifically, during implementation, in response to the instance purchase request, displaying the available zone deployment selection interface may include: in response to the instance purchase request, displaying the region selection interface; receiving the user's selection operation on the region selection interface to determine the region selected by the user; sending the region selected by the user to the cloud platform management system; receiving and displaying the available zones under the user-selected region returned by the cloud platform management system for the user to select.

The method embodiments provided in the above embodiments of the present application can be executed in a computer terminal, a computer terminal or a similar computing device. Taking running on a computer terminal as an example, FIG9 is a hardware structure block diagram of a computer terminal of a cloud service node deployment method in an embodiment of the present invention. As shown in FIG9, the computer terminal 10 may include one or more (only one is shown in the figure) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission module 106 for communication functions. It can be understood by those of ordinary skill in the art that the structure shown in FIG9 is only for illustration, and it does not limit the structure of the above-mentioned electronic device. For example, the computer terminal 10 may also include more or fewer components than those shown in FIG9, or have a configuration different from that shown in FIG9.

The memory 104 can be used to store software programs and modules of application software, such as program instructions/modules corresponding to the cloud service node deployment method in the embodiment of the present invention. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, the cloud service node deployment method of the above-mentioned application is realized. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

The transmission module 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission module 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission module 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

At the software level, the above device may be as shown in FIG10 and may include:

The first receiving module 1001 is used to receive a cloud service instance purchase request from a user;

The display module 1002 is used to display an availability zone deployment selection interface in response to the instance purchase request, wherein the availability zone deployment selection interface includes: a primary availability zone deployment mode selection area and a backup availability zone deployment mode selection area;

The second receiving module 1003 is used to receive the user's selection operation in the primary available zone deployment mode area and the user's selection operation in the backup available zone deployment mode area, and use the selection items corresponding to the selected areas as the primary available zone deployment mode and the backup available zone deployment mode specified by the user;

The sending module 1004 is used to carry the primary availability zone deployment mode and the backup availability zone deployment mode specified by the user in the cloud service instance purchase request and send them to the cloud platform management system.

In one embodiment, the above-mentioned primary availability zone deployment method may include but is not limited to at least one of the following: random deployment, deployment in a user-specified availability zone.

In one embodiment, the above-mentioned deployment mode of the backup availability zone may include but is not limited to at least one of the following: random deployment, deployment in a user-specified availability zone, and deployment in the same zone as the primary availability zone.

In one embodiment, the display module 1002 may include: a first display unit, used to display a region selection interface in response to the instance purchase request; a receiving unit, used to receive a user's selection operation on the region selection interface to determine the region selected by the user; a sending unit, used to send the region selected by the user to the cloud platform management system; and a second display unit, used to receive and display the available area in the region selected by the user returned by the cloud platform management system for the user to select.

At the software level, the cloud service node deployment device deployed on the server side may include:

A first acquisition module is used to acquire a user's cloud service instance purchase request;

A second acquisition module is used to respond to the instance purchase request and acquire a primary availability zone deployment mode and a backup availability zone deployment mode specified by the user, wherein the primary availability zone deployment mode and the backup availability zone deployment mode are respectively specified by the user;

The deployment module is used to deploy the master node according to the deployment mode of the primary availability zone and deploy the standby node according to the deployment mode of the standby availability zone.

In one embodiment, the deployment method of the primary availability zone may include but is not limited to at least one of the following: random deployment, deployment in a user-specified availability zone; the deployment method of the backup availability zone may include but is not limited to at least one of the following: random deployment, deployment in a user-specified availability zone, and deployment in the same zone as the primary availability zone.

In one embodiment, the above-mentioned cloud service node deployment device may also include: a storage module, which is used to store the primary availability zone deployment mode and the backup availability zone deployment mode specified by the user after obtaining the primary availability zone deployment mode and the backup availability zone deployment mode specified by the user; an operation module, which is used to operate according to the primary availability zone deployment mode and the backup availability zone deployment mode specified by the user when operating and maintaining the user's cloud service instance, so as to ensure that the primary availability zone deployment mode and the backup availability zone deployment mode of the cloud service instance specified by the user remain unchanged.

In one embodiment, the deployment module is specifically used to randomly select an availability zone with resources from the availability zones as the primary availability zone to deploy the master node when the user selects the primary availability zone deployment mode for random deployment.

In one embodiment, the above-mentioned second acquisition module can be specifically used to respond to the instance purchase request, obtain the region selected by the user; return the available zone under the region selected by the user for user selection; and receive the primary available zone deployment method and the backup available zone deployment method specified by the user.

In one embodiment, returning the available zones in the region selected by the user may include: traversing all available zones in the region selected by the user; determining available zones having resource values greater than a preset resource amount; and returning available zones having resource values greater than the preset resource amount as available zones in the region selected by the user for the user to select.

The embodiments of the present application also provide a specific implementation of an electronic device capable of implementing all the steps in the cloud service node deployment method in the above embodiments, wherein the electronic device specifically includes the following contents: a processor, a memory, a communication interface, and a bus; wherein the processor, the memory, and the communication interface communicate with each other through the bus; the processor is used to call a computer program in the memory, and when the processor executes the computer program, all the steps in the cloud service node deployment in the above embodiments are implemented. For example, when the processor executes the computer program, the following steps are implemented:

Step 1: Obtain the user's cloud service instance purchase request;

Step 2: in response to the instance purchase request, obtaining a primary availability zone deployment mode and a backup availability zone deployment mode specified by the user, wherein the primary availability zone deployment mode and the backup availability zone deployment mode are respectively specified by the user;

Step 3: Deploy the master node according to the deployment mode of the primary availability zone, and deploy the standby node according to the deployment mode of the standby availability zone.

Alternatively, the processor implements the following steps when executing the computer program:

Step 1: Receive a user's cloud service instance purchase request;

Step 2: In response to the instance purchase request, displaying an availability zone deployment selection interface, wherein the availability zone deployment selection interface includes: a primary availability zone deployment mode selection area and a backup availability zone deployment mode selection area;

Step 3: Receive the user's selected operation in the primary availability zone deployment mode area and the user's selected operation in the backup availability zone deployment mode area, and use the selected items corresponding to the selected areas as the primary availability zone deployment mode and the backup availability zone deployment mode specified by the user;

Step 4: The primary availability zone deployment mode and the backup availability zone deployment mode specified by the user are carried in the cloud service instance purchase request and sent to the cloud platform management system.

From the above description, it can be seen that in the embodiment of the present application, when a user requests to purchase a cloud service instance, the primary availability zone deployment mode and the backup availability zone deployment mode are specified by the user separately, rather than adopting a primary and backup availability zone combination. This method solves the problems of low sales success rate and low resource utilization caused by the existing primary and backup availability zone combination, and achieves the technical effect of effectively improving the sales success rate and resource utilization.

The embodiments of the present application also provide a computer-readable storage medium capable of implementing all the steps in the cloud service node deployment method in the above embodiments. The computer-readable storage medium stores a computer program. When the computer program is executed by a processor, all the steps in the cloud service node deployment method in the above embodiments are implemented. For example, when the processor executes the computer program, the following steps are implemented:

Step 1: Obtain the user's cloud service instance purchase request;

Step 2: in response to the instance purchase request, obtaining a primary availability zone deployment mode and a backup availability zone deployment mode specified by the user, wherein the primary availability zone deployment mode and the backup availability zone deployment mode are respectively specified by the user;

Step 3: Deploy the master node according to the deployment mode of the primary availability zone, and deploy the standby node according to the deployment mode of the standby availability zone.

Alternatively, the processor implements the following steps when executing the computer program:

Step 1: Receive a user's cloud service instance purchase request;

Step 2: In response to the instance purchase request, displaying an availability zone deployment selection interface, wherein the availability zone deployment selection interface includes: a primary availability zone deployment mode selection area and a backup availability zone deployment mode selection area;

Step 3: Receive the user's selected operation in the primary availability zone deployment mode area and the user's selected operation in the backup availability zone deployment mode area, and use the selected items corresponding to the selected areas as the primary availability zone deployment mode and the backup availability zone deployment mode specified by the user;

Step 4: The primary availability zone deployment mode and the backup availability zone deployment mode specified by the user are carried in the cloud service instance purchase request and sent to the cloud platform management system.

From the above description, it can be seen that in the embodiment of the present application, when a user requests to purchase a cloud service instance, the primary availability zone deployment mode and the backup availability zone deployment mode are specified by the user separately, rather than adopting a primary and backup availability zone combination. This method solves the problems of low sales success rate and low resource utilization caused by the existing primary and backup availability zone combination, and achieves the technical effect of effectively improving the sales success rate and resource utilization.

Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the hardware + program embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

The above is a description of a specific embodiment of the present specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

Although the present application provides method operation steps as described in the embodiments or flowcharts, more or fewer operation steps may be included based on conventional or non-creative labor. The order of steps listed in the embodiments is only one way of executing the order of many steps and does not represent the only execution order. When the actual device or client product is executed, it can be executed in the order of the method shown in the embodiments or the drawings or in parallel (for example, in a parallel processor or multi-threaded processing environment).

The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a vehicle-mounted human-computer interaction device, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

Although the present specification embodiment provides the method operation steps as described in the embodiment or flow chart, more or less operation steps may be included based on conventional or non-creative means. The order of steps listed in the embodiment is only one way of executing the order of many steps, and does not represent a unique execution order. When the device or terminal product in practice is executed, it can be executed in sequence or in parallel (such as a parallel processor or a multi-threaded processing environment, or even a distributed data processing environment) according to the method shown in the embodiment or the accompanying drawings. The term "include", "include" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, product or equipment including a series of elements not only includes those elements, but also includes other elements that are not clearly listed, or also includes elements inherent to such process, method, product or equipment. In the absence of more restrictions, it is not excluded that there are other identical or equivalent elements in the process, method, product or equipment including the elements.

For the convenience of description, the above devices are described in various modules according to their functions. Of course, when implementing the embodiments of this specification, the functions of each module can be implemented in the same or more software and/or hardware, or the module implementing the same function can be implemented by a combination of multiple sub-modules or sub-units. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

Those skilled in the art also know that, in addition to implementing the controller in a purely computer-readable program code, the controller can be made to implement the same function in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, such a controller can be considered as a hardware component, and the devices for implementing various functions included therein can also be considered as structures within the hardware component. Or even, the devices for implementing various functions can be considered as both software modules for implementing the method and structures within the hardware component.

The present invention is described with reference to the flowchart and/or block diagram of the method, device (system), and computer program product according to the embodiment of the present invention. It should be understood that each process and/or box in the flowchart and/or block diagram, as well as the combination of the process and/or box in the flowchart and/or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

In a typical configuration, a computing device includes one or more processors (CPU), input/output interfaces, network interfaces, and memory.

The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and/or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems or computer program products. Therefore, the embodiments of this specification may take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, the embodiments of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

The present specification embodiments may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present specification embodiments may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

Each embodiment in this specification is described in a progressive manner, and the same and similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment. In the description of this specification, the description of the reference terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the embodiment of this specification. In this specification, the schematic representation of the above terms does not necessarily target the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner. In addition, in the absence of contradiction, a person skilled in the art can combine and combine the different embodiments or examples described in this specification and the features of different embodiments or examples.

The above is only an example of the embodiment of the present specification and is not intended to limit the embodiment of the present specification. For those skilled in the art, the embodiment of the present specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the embodiment of the present specification shall be included in the scope of the claims of the embodiment of the present specification.

Claims (13)

1. A cloud service node deployment method, comprising: Obtain the user's cloud service instance purchase request; In response to the instance purchase request, obtaining a primary availability zone deployment mode and a backup availability zone deployment mode specified by a user, wherein the primary availability zone deployment mode and the backup availability zone deployment mode are respectively specified by the user; Deploy the master node according to the deployment mode of the primary availability zone, and deploy the standby node according to the deployment mode of the standby availability zone; Among them, the deployment method of the primary availability zone includes at least one of the following: random deployment, deployment in a user-specified availability zone; the deployment method of the backup availability zone includes at least one of the following: random deployment, deployment in a user-specified availability zone, and deployment in the same zone as the primary availability zone. 2. The method according to claim 1, characterized in that after obtaining the primary availability zone deployment mode and the backup availability zone deployment mode specified by the user, it also includes: Storing the primary availability zone deployment mode and the backup availability zone deployment mode specified by the user; When operating and maintaining the user's cloud service instance, operations are performed according to the primary availability zone deployment mode and the backup availability zone deployment mode specified by the user to ensure that the primary availability zone deployment mode and the backup availability zone deployment mode of the cloud service instance specified by the user remain unchanged. 3. The method according to claim 1, characterized in that, when the user selects the primary availability zone deployment mode versus random deployment, deploying the master node according to the primary availability zone deployment mode comprises: A random availability zone with resources is selected from the availability zones as the primary availability zone to deploy the master node. 4. The method according to claim 1, characterized in that, in response to the instance purchase request, obtaining the primary availability zone deployment mode and the backup availability zone deployment mode specified by the user comprises: In response to the instance purchase request, obtaining a region selected by the user; Returns the available zones in the region selected by the user for the user to select; Receive the primary and backup zone deployment modes specified by the user. 5. The method according to claim 1, wherein returning the available zones in the region selected by the user comprises: Traverse all available zones in the region selected by the user; Determine the available zone whose resource value is greater than the preset resource amount; The availability zones with a greater resource volume than the preset amount are returned as the availability zones in the region selected by the user for selection by the user. 6. A cloud service node deployment method, characterized by comprising: Receive a cloud service instance purchase request from a user; In response to the instance purchase request, displaying an availability zone deployment selection interface, wherein the availability zone deployment selection interface includes: a primary availability zone deployment mode selection area and a backup availability zone deployment mode selection area; Receive the user's selected operation in the primary availability zone deployment mode area and the user's selected operation in the backup availability zone deployment mode area, and use the selected items corresponding to the selected areas as the primary availability zone deployment mode and the backup availability zone deployment mode specified by the user; Sending the primary availability zone deployment mode and the backup availability zone deployment mode specified by the user to the cloud platform management system along with the cloud service instance purchase request; Among them, the deployment method of the primary availability zone includes at least one of the following: random deployment, deployment in a user-specified availability zone; the deployment method of the backup availability zone includes at least one of the following: random deployment, deployment in a user-specified availability zone, and deployment in the same zone as the primary availability zone. 7. The method according to claim 6, wherein in response to the instance purchase request, displaying an availability zone deployment selection interface comprises: In response to the instance purchase request, displaying a region selection interface; Receive a selection operation from the user on the region selection interface to determine the region selected by the user; Send the region selected by the user to the cloud platform management system; Receive and display the available zones in the region selected by the user returned by the cloud platform management system for the user to select. 8. A cloud service node deployment device, located in a cloud platform management system, characterized in that it includes: A first acquisition module is used to acquire a user's cloud service instance purchase request; A second acquisition module is used to respond to the instance purchase request and acquire a primary availability zone deployment mode and a backup availability zone deployment mode specified by a user, wherein the primary availability zone deployment mode and the backup availability zone deployment mode are respectively specified by the user; A deployment module is used to deploy the master node according to the deployment mode of the primary availability zone and to deploy the standby node according to the deployment mode of the standby availability zone; Among them, the deployment method of the primary availability zone includes at least one of the following: random deployment, deployment in a user-specified availability zone; the deployment method of the backup availability zone includes at least one of the following: random deployment, deployment in a user-specified availability zone, and deployment in the same zone as the primary availability zone. 9. A cloud service node deployment device, located in a terminal, characterized in that it includes: A first receiving module, configured to receive a cloud service instance purchase request from a user; A display module is used to display an available zone deployment selection interface in response to the instance purchase request, wherein the available zone deployment selection interface includes: a primary available zone deployment mode selection area and a backup available zone deployment mode selection area; The second receiving module is used to receive the user's selection operation in the primary availability zone deployment mode area and the user's selection operation in the backup availability zone deployment mode area, and use the selection items corresponding to the selected areas as the primary availability zone deployment mode and the backup availability zone deployment mode specified by the user; A sending module, used to carry the primary availability zone deployment mode and the backup availability zone deployment mode specified by the user in the cloud service instance purchase request and send them to the cloud platform management system; Among them, the deployment method of the primary availability zone includes at least one of the following: random deployment, deployment in a user-specified availability zone; the deployment method of the backup availability zone includes at least one of the following: random deployment, deployment in a user-specified availability zone, and deployment in the same zone as the primary availability zone. 10. A server device, comprising a processor and a memory for storing processor executable instructions, wherein the processor implements the steps of the method according to any one of claims 1 to 5 when executing the instructions. 11. A terminal device, comprising a processor and a memory for storing processor executable instructions, wherein the processor implements the steps of the method according to claim 6 or 7 when executing the instructions. 12. A computer-readable storage medium having computer instructions stored thereon, wherein the instructions, when executed, implement the steps of the method according to any one of claims 1 to 5. 13. A computer-readable storage medium having computer instructions stored thereon, wherein the instructions implement the steps of the method according to claim 6 or 7 when executed.