Cloud service providing method and device

Abstract

The invention discloses a cloud service providing method and device, and belongs to the technical field of cloud services. The method comprises the following steps: a cloud platform provides a network configuration interface for a user, the network configuration interface prompts the user to input network feature information, and the network feature information indicates a cloud service network required for realizing a target cloud service; the cloud platform provides a network association interface for a user, the network association interface prompts the user to input association information, the association information indicates a plurality of service nodes associated with a cloud service network, the service nodes are used for deploying application programs of the user, and the application programs are used for realizing a target cloud service; the plurality of service nodes are obtained based on resource deployment in one or more resource deployment areas; and the cloud platform establishes an association relationship among the plurality of service nodes based on the network feature information and the association information to obtain a cloud service network. According to the invention, the performance of the cloud service provided by the cloud service network is improved.

Description

[0001] This application claims priority to Chinese patent application No. 202310919132.3, filed on July 25, 2023, with invention name “Network system based on cloud service”, the entire contents of which are incorporated by reference in this disclosure. Technical Field

[0002] The present application relates to the field of cloud service technology, and in particular to a method and device for providing cloud services. Background Art

[0003] With the continuous development of information technology, especially the advancement of Internet technology, more and more users such as enterprises and organizations (also called tenants or cloud tenants) use cloud services to realize their own business.

[0004] Currently, before users use cloud services, their developers need to use the various resources provided by the cloud platform according to the user's demand for cloud services, create various network objects, and configure the network objects in order to build a cloud service network on the cloud platform to realize the cloud services required by users.

[0005] However, the current deployment of cloud service networks is subject to various restrictions, which affects the performance of cloud services provided by the cloud service networks. Summary of the invention

[0006] The present application provides a cloud service provision method and device. The present application improves the performance of cloud services provided by a cloud service network. The technical solutions provided by the present application are as follows:

[0007] In a first aspect, the present application provides a method for providing cloud services. The method is applied to a cloud platform. The method includes: the cloud platform provides a network configuration interface to the user, the network configuration interface prompts the user to input network feature information, and the network feature information indicates the cloud service network required to implement the target cloud service; the cloud platform provides a network association interface to the user, the network association interface prompts the user to input association information, and the association information indicates multiple service nodes associated with the cloud service network, the service nodes are used to deploy the user's application, the application is used to implement the target cloud service, and the multiple service nodes are obtained based on the resource deployment in one or more resource deployment areas; the cloud platform establishes an association relationship between multiple service nodes based on the network feature information and the association information to obtain a cloud service network.

[0008] In the cloud service providing method provided in the present application, since multiple service nodes of the cloud service network are obtained based on resource deployment in one or more resource deployment areas, the cloud service network is not limited to being obtained based on resource deployment in a certain resource deployment area. The cloud service network can be regarded as a global network, which can utilize resources deployed in multiple resource deployment areas to provide services to users, thereby expanding the scope of cloud services provided by the cloud service network and improving the performance of cloud services provided by the cloud service network.

[0009] In one implementation, the multiple service nodes meet one or more of the following requirements: they are deployed based on cloud resources in different cloud resource deployment areas in the cloud platform; and they are deployed based on at least two of public network resources, cloud resources in the cloud resource deployment area, and the user's own resources.

[0010] Furthermore, for any service node, the service node may be optionally obtained based on resource deployment in one or more resource deployment areas. For example, the service node satisfies one or more of the following: it is obtained based on cloud resource deployment in different cloud resource deployment areas in the cloud platform; and it is obtained based on at least two of public network resources, cloud resources in cloud resource deployment areas, and the user's own resources. At this time, since the service node is not limited to being obtained based on resource deployment in a certain resource deployment area, it can be seen that the service node can use resources deployed in multiple resource deployment areas to provide services to users, and the service node can be regarded as a global service node.

[0011] Optionally, multiple service nodes use different monitoring protocols. When multiple service nodes in a cloud service network use different monitoring protocols, the cloud service network can support access to applications using different monitoring protocols, such as supporting services using layer 4 networks and layer 7 networks, thereby increasing the diversity of cloud services provided by the cloud service network.

[0012] In one implementation, the plurality of first resource sets used to deploy the service node can also use different network protocols. In this case, the service node can support access using different network protocols, such as supporting mutual access between IPv4 and IPv6.

[0013] Furthermore, the multiple first resource sets used to deploy the multiple service nodes use different network protocols. In this case, the cloud service network can support access using different network protocols, such as supporting mutual access between IPv4 and IPv6.

[0014] As an optional implementation method, the method also includes: the cloud platform deploys a service agent for the service node, the service agent is used to convert the destination address and source address of the message transmitted between the service node and the transit network into an address that complies with the network protocol used by the service node and the receiving end in the transit network when the service node and the transit network of the cloud service network use different network protocols, and the transit network is used to associate different service nodes.

[0015] The cloud platform deploys service agents for service nodes and uses the service agents to perform automatic conversion of network protocols, so that service nodes can support application mutual access using different network protocols without the need to modify the service nodes. This enables the cloud service provision method provided in this application to provide cloud services in a variety of scenarios, and its application scenarios do not need to be restricted by network protocols, thereby expanding the application scope of the cloud service provision method.

[0016] Optionally, before the cloud platform establishes an association relationship between multiple service nodes based on network feature information and association information to obtain a cloud service network, the method also includes: the cloud platform provides a service configuration interface to the user, the service configuration interface prompts the user to input service feature information, the service feature information indicates all first resource sets required to deploy the service node, and all resources in any first resource set are deployed in the same resource deployment area; the cloud platform uses all first resource sets to deploy the service node.

[0017] In some implementation scenarios, users can also deploy clients in the cloud service network. There are many ways to deploy clients, and the following three are used as examples to illustrate them.

[0018] In a first implementation, the service feature information or the network feature information further indicates that the service node is reused as a client. The service feature information indicates all first resource sets required to deploy the service node. The method also includes: the cloud platform uses all first resource sets to deploy the client and associate the client with the cloud service network.

[0019] In a second implementation, the service characteristic information or the network characteristic information also indicates that any first resource set among all first resource sets is also used to deploy the client, and the service characteristic information indicates all first resource sets required to deploy the service node. The method also includes: the cloud platform deploys the client based on any first resource set and associates the client with the cloud service network.

[0020] In a third implementation, the method also includes: the cloud platform provides a client configuration interface to the user, the client configuration interface prompts the user to input client characteristic information, the client characteristic information indicates the client and a second resource set required to deploy the client; the cloud platform uses the second resource set to deploy the client and associate the client with the cloud service network.

[0021] When the cloud service network also includes a client, the resource set of the client and the resource set of the service node are deployed using different network protocols. In this case, the cloud service network supports application access using different network protocols.

[0022] As one implementation method, the method also includes: the cloud platform uses a resource collection for deploying the client to deploy a client agent for the client, and the client agent is used to convert the destination address and source address of the message transmitted between the client and the transit network into an address that complies with the network protocol used by the service node and the receiving end in the transit network when the client and the transit network of the cloud service network use different network protocols. The transit network is used to associate different service nodes.

[0023] In addition, when the cloud service network also includes a client, as an implementation method for supporting mutual access between applications with different monitoring protocols, the method also includes: the cloud platform uses a resource set for deploying the client to deploy a second client agent and a third client agent for the client; the second client agent is used to forward the message to the destination of the message according to the first monitoring protocol when the client sends a message using the first monitoring protocol, and forward the message to the third client agent when the client sends a message using the second monitoring protocol; the third client agent is used to forward the message to the destination of the message according to the second monitoring protocol. In this way, the cloud service network can support mutual access between applications at layer 4 and layer 7.

[0024] Optionally, a client can be associated with one or more cloud service networks, and multiple cloud service networks are used to carry different cloud services. When application requirements require a client to be associated with multiple cloud service networks, the user can optionally enter all cloud service networks associated with the client in the client configuration interface.

[0025] In this application, multiple service nodes of a cloud service network may be optionally deployed by the same user, or may be deployed by multiple users respectively. When multiple service nodes of a cloud service network are deployed by different users, the cloud service network may be considered to support cross-account access.

[0026] The user who instructs the deployment of the cloud service network and the user who instructs the deployment of all service nodes in the cloud service network may be the same or different. For example, the management department of a company instructs the deployment of a cloud service network, and multiple business departments of the company instruct the deployment of multiple service nodes respectively. When the user who instructs the deployment of the cloud service network and the user who instructs the deployment of all service nodes in the cloud service network are different, the cloud service network can be considered to support cross-account access.

[0027] Optionally, a service node can be associated with one or more cloud service networks, and multiple cloud service networks are used to implement different cloud services. When application requirements require a service node to be associated with multiple cloud service networks, the user can optionally enter all cloud service networks associated with the service node in the service configuration interface.

[0028] After the cloud platform obtains the association information, it can establish the association relationship between the multiple service nodes indicated by the association information in the public platform to obtain the cloud service network. Establishing the association relationship between the multiple service nodes is actually to open up a network for multiple service nodes in the cloud service network to access each other. Optionally, the implementation process includes: the cloud platform creates a transit network based on the network feature information and the association information, and associates the multiple service nodes with the transit network to obtain the cloud service network.

[0029] Optionally, the transit network is also used to convert the addresses of multiple service nodes. Since different service nodes in the cloud service network need to pass through the transit network when visiting each other, the transit network can obtain the addresses of all service nodes in the cloud service network, and when the addresses of different service nodes conflict, uniformly assign addresses to these service nodes, and convert the addresses of the service nodes into unique addresses in the cloud service network, so that the addresses of the service nodes no longer conflict. For example, when multiple service nodes in the cloud service network all use the IPv4 protocol, and the addresses of some of the service nodes conflict, the transit network can uniformly plan the addresses of the service nodes by converting the addresses for these service nodes, thereby solving the problem of address conflicts of the IPv4 protocol for multiple service nodes. In this way, the cloud service network can solve the problems of IPv4 address conflicts and insufficient address space, so that users do not need to plan the network and address space, further improving the availability of cloud services provided by the cloud platform.

[0030] Optionally, the service node associated with the cloud service network can be created by the user. Before the cloud platform provides the user with a service configuration interface, the method further includes: the cloud platform provides the user with a resource configuration interface, the resource configuration interface prompts the user to input resource feature information, the resource feature information indicates the resources required by the user; the cloud platform obtains a first resource set including the resources indicated by the resource feature information, and the first resource set is used to create the service node.

[0031] In one implementation, the resource characteristic information also indicates that the resources and the source of the virtual LAN are provided in the form of a virtual LAN, the virtual LAN includes multiple computing instances with specified network relationships, and the cloud platform obtains a first resource set including the resources indicated by the resource characteristic information, including: when the resource characteristic information indicates that a virtual LAN is created based on the resources, the cloud platform uses the resources to create a virtual LAN and obtains the first resource set; when the resource characteristic information indicates that an existing virtual LAN is used, the cloud platform obtains the existing virtual LAN and obtains the first resource set.

[0032] Optionally, the first resource set includes one or more computing instances, and the computing instances include: virtual machines, containers, functions, and bare metal servers.

[0033] In the second aspect, the present application provides a cloud service providing device. The device is applied to a cloud platform. The device includes: an interactive module, which is used to provide a network configuration interface to the user, the network configuration interface prompts the user to input network feature information, and the network feature information indicates the cloud service network required to implement the target cloud service; the interactive module is also used to provide a network association interface to the user, the network association interface prompts the user to input association information, and the association information indicates multiple service nodes associated with the cloud service network. The service nodes are used to deploy the user's application program, and the application program is used to implement the target cloud service. The multiple service nodes are obtained based on the resource deployment in one or more resource deployment areas; the processing module is used to establish an association relationship between multiple service nodes based on the network feature information and the association information to obtain a cloud service network.

[0034] Optionally, the multiple service nodes meet one or more of the following requirements: they are deployed based on cloud resources in different cloud resource deployment areas in the cloud platform; and they are deployed based on at least two of public network resources, cloud resources in the cloud resource deployment area, and the user's own resources.

[0035] Optionally, the service node is obtained based on resource deployment in one or more resource deployment areas.

[0036] Optionally, the service node satisfies one or more of the following: is deployed based on cloud resources in different cloud resource deployment areas in the cloud platform; and is deployed based on at least two of public network resources, cloud resources in the cloud resource deployment area, and the user's own resources.

[0037] Optionally, multiple service nodes use different monitoring protocols.

[0038] Optionally, the multiple first resource sets used to deploy the service node use different network protocols.

[0039] Optionally, the multiple first resource sets used to deploy the multiple service nodes use different network protocols.

[0040] Optionally, the processing module is also used to deploy a service agent for the service node. The service agent is used to convert the destination address and source address of the message transmitted between the service node and the transit network into an address that complies with the network protocol used by the service node and the receiving end in the transit network when the service node and the transit network of the cloud service network use different network protocols. The transit network is used to associate different service nodes.

[0041] Optionally, the interaction module is also used to provide a service configuration interface to the user, the service configuration interface prompts the user to enter service feature information, the service feature information indicates all first resource sets required to deploy the service node, all resources in any first resource set are deployed in the same resource deployment area; the cloud platform uses all first resource sets to deploy the service node.

[0042] Optionally, the service characteristic information or network characteristic information also indicates that the service node is reused as a client, and the service characteristic information indicates all first resource sets required to deploy the service node; the processing module is also used to utilize all first resource sets to deploy the client and associate the client with the cloud service network.

[0043] Optionally, the service characteristic information or network characteristic information also indicates that any first resource set among all first resource sets is also used to deploy the client, and the service characteristic information indicates all first resource sets required to deploy the service node; the processing module is also used to deploy the client based on any first resource set and associate the client with the cloud service network.

[0044] Optionally, the interaction module is also used to provide a client configuration interface to the user, which prompts the user to enter client characteristic information, and the client characteristic information indicates the client and a second resource set required to deploy the client; the processing module is also used to utilize the second resource set to deploy the client and associate the client with the cloud service network.

[0045] Optionally, the resource set of the deployment client and the resource set of the deployment service node use different network protocols.

[0046] Optionally, the processing module is also used to deploy a client agent for the client using the resource set used to deploy the client. The client agent is used to convert the destination address and source address of the message transmitted between the client and the transit network into an address that complies with the network protocol used by the service node and the receiving end in the transit network when the client and the transit network of the cloud service network use different network protocols. The transit network is used to associate different service nodes.

[0047] Optionally, the processing module is also used to deploy a second client agent and a third client agent for the client using a resource set for deploying the client; the second client agent is used to forward the message to the destination of the message in accordance with the first listening protocol when the client sends a message using the first listening protocol, and to forward the message to the third client agent when the client sends a message using the second listening protocol; the third client agent is used to forward the message to the destination of the message in accordance with the second listening protocol.

[0048] Optionally, the client is associated with multiple cloud service networks, and the multiple cloud service networks are used to implement different cloud services.

[0049] Optionally, the multiple service nodes are deployed by multiple users respectively.

[0050] Optionally, the cloud service network and the multiple service nodes are deployed by multiple users respectively.

[0051] Optionally, the service node is associated with multiple cloud service networks, and the multiple cloud service networks are used to implement different cloud services.

[0052] Optionally, the processing module is specifically used to: the cloud platform creates a transit network based on the network feature information and the associated information, and associates the multiple service nodes with the transit network to obtain a cloud service network.

[0053] Optionally, the transit network is also used to convert addresses of multiple service nodes.

[0054] Optionally, the interaction module is also used to provide a resource configuration interface to the user, the resource configuration interface prompts the user to input resource feature information, the resource feature information indicates the resources required by the user; the processing module is also used to obtain a first resource set including resources indicated by the resource feature information, the first resource set is used to create a service node.

[0055] Optionally, the resource characteristic information also indicates that the resources and the source of the virtual LAN are provided in the form of a virtual LAN, and the virtual LAN includes multiple computing instances with specified network relationships. The processing module is specifically used to: when the resource characteristic information indicates that a virtual LAN is created based on resources, the cloud platform uses the resources to create a virtual LAN to obtain a first resource set; when the resource characteristic information indicates that an existing virtual LAN is used, the cloud platform obtains the existing virtual LAN to obtain a first resource set.

[0056] Optionally, the first resource set includes one or more computing instances, and the computing instances include: virtual machines, containers, functions, and bare metal servers.

[0057] In a third aspect, the present application provides a computing device including a memory and a processor, wherein the memory stores program instructions, and the processor runs the program instructions to execute the method provided in the first aspect of the present application and any possible implementation thereof.

[0058] In a fourth aspect, the present application provides a computing device cluster, including multiple computing devices, the multiple computing devices including multiple processors and multiple memories, the multiple memories storing program instructions, and the multiple processors running the program instructions, so that the computing device cluster executes the method provided in the first aspect of the present application and any possible implementation thereof.

[0059] In a fifth aspect, the present application provides a computer-readable storage medium, which is a non-volatile computer-readable storage medium, and the computer-readable storage medium includes program instructions. When the program instructions are executed on a computing device, the computing device executes the method provided in the first aspect of the present application and any possible implementation thereof.

[0060] In a sixth aspect, the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method provided in the first aspect of the present application and any possible implementation thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0061] Figure 1 It is a structural diagram of an implementation scenario involved in a cloud service providing method provided in an embodiment of the present application;

[0062] Figure 2 It is a schematic diagram of resource deployment in a cloud platform provided in an embodiment of the present application;

[0063] Figure 3 It is a flow chart of a cloud service providing method provided by an embodiment of the present application;

[0064] Figure 4 It is a schematic diagram for indicating the creation of a VPC in a resource configuration interface provided in an embodiment of the present application;

[0065] Figure 5 It is a schematic diagram of indicating the use of an existing VPC in a resource configuration interface provided in an embodiment of the present application;

[0066] Figure 6 is a schematic diagram of a service configuration interface provided in an embodiment of the present application;

[0067] Figure 7 It is a schematic diagram of a network association interface provided by an embodiment of the present application as a part of a network configuration interface;

[0068] Figure 8 is a schematic diagram of a network model provided in an embodiment of the present application;

[0069] Fig. 9 is a flow chart of another cloud service providing method provided in an embodiment of the present application;

[0070] Fig.10 is a flow chart of another cloud service providing method provided in an embodiment of the present application;

[0071] Fig.11 It is a flow chart of another cloud service providing method provided in an embodiment of the present application;

[0072] Fig.12 is a schematic diagram of a second client agent and a third client agent provided in an embodiment of the present application;

[0073] Fig.13 It is a schematic diagram of the structure of a cloud service network provided in an embodiment of the present application;

[0074] Fig.14 is a schematic diagram of the structure of another cloud service network provided in an embodiment of the present application;

[0075] Fig.15 It is a schematic diagram of the structure of a cross-region global cloud service network provided by an embodiment of the present application;

[0076] Fig.16 It is a schematic diagram of a cloud service network provided by an embodiment of the present application that is a cross-region global network, and a service node that is a cross-region global application;

[0077] Fig.17 It is a schematic diagram of a cloud service network provided by an embodiment of the present application, which is a global network across regions, public networks and customer offline computer rooms;

[0078] Fig.18 This is a schematic diagram of a global network for cross-account and departmental collaboration of an enterprise provided in an embodiment of the present application;

[0079] Fig.19 It is a schematic diagram of the relationship between accounts involved in the cloud service network provided by an embodiment of the present application;

[0080] Fig. 20 is a schematic diagram of a cloud service providing device provided in an embodiment of the present application;

[0081] Fig.21 is a schematic diagram of the structure of a computing device provided in an embodiment of the present application;

[0082] Fig. 22 It is a structural diagram of a computing device cluster provided in an embodiment of the present application. DETAILED DESCRIPTION

[0083] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0084] To facilitate understanding, the technology and background involved in the embodiments of the present application are first explained below.

[0085] Virtual private cloud (VPC) is a network isolation through logical means, providing a secure and isolated network environment. Users can define virtual networks in VPC that are no different from traditional networks, while providing advanced network services such as elastic internet protocol (EIP) and security groups. From a service perspective, VPC refers to a cloud, a cloud computing service, and a collection of resources that runs on a public cloud and isolates a portion of public cloud resources for a certain user for private use by this user. It is managed by the public cloud and runs on public resources, but it ensures that the resources between each user are isolated, and when users use them, they are not affected by other users and feel like they are using their own private cloud. For example, a virtual private network includes multiple computing instances (such as virtual machines) with specified network relationships.

[0086] Network address translation (NAT) technology is a technology used in computer networks. It converts a set of Internet Protocol (IP) addresses into another set of IP addresses. For example, by replacing the address information in the IP message header, at least one of the destination IP address and the source IP address of the message to be sent is converted. NAT technology may include: destination network address translation (DNAT) technology, source network address translation (SNAT) technology, and source / destination network address translation (Full Network Address Translation, FullNAT). DNAT refers to address translation of the destination IP address of the message. SNAT refers to address translation of the source IP address of the message. FullNAT refers to address translation of both the destination IP address and the source IP address of the message. NAT is usually used to map a set of private IP addresses to a public IP address. This can help solve the problem of Internet Protocol version 4 (IPv4) address shortage and enhance network security. For example, NAT64 can translate Internet Protocol version 6 (IPv6) packets into IPv4 packets. Similarly, NAT46 can translate IPv4 packets into IPv6 packets.

[0087] Load balancing (LB) is a network technology that distributes traffic to multiple servers or devices in order to balance the load and improve the reliability, availability, and performance of the system.

[0088] Cloud Backbone is a software defined wide area network (SD-WAN), which is a network abstracted from hardware, creating a virtualized network coverage. It enables customers to build, manage and monitor a unified global network faster and easier, allowing customers to connect offline Internet data centers (IDCs), branches and public clouds to a unified global network through the global cloud service panel, and customers can get a unified view of the global network.

[0089] Internet data center (IDC) is an Internet-based network that provides operation and maintenance facilities and related service systems for centralized data collection, storage, processing and transmission equipment. Conceptually, it can be understood as a public commercial Internet "computer room". At the same time, it is also an IT professional service and an important infrastructure for the IT industry. IDC is not only a service concept, but also a network concept. It constitutes a part of the basic network resources. Just like the backbone network and access network, it provides a high-end data transmission service and high-speed access service. Generally speaking, the user's offline IDC can be understood as the user's offline computer room, which is a standardized telecommunications professional-level computer room environment established by the user using the existing Internet communication lines and bandwidth resources to provide a full range of services such as server hosting, leasing and related value-added services.

[0090] The elastic internet protocol (EIP) address, also known as the elastic public network interconnection protocol address, refers to the IP address used by computer devices in the private network to access the public network.

[0091] Virtual machine (VM): refers to a complete computer system with complete hardware system functions and running in a completely isolated environment, which is simulated by virtualization technology. Some instruction subsets of the virtual machine can be processed in the host machine, and other instructions can be executed in a simulated manner. Users can purchase cloud services by renting virtual machines. As a possible implementation of a virtual machine, the virtual machine in the embodiment of the present application can be an elastic cloud server (elastic compute service, ECS).

[0092] A gateway is also called an internetwork connector or a protocol converter. A gateway implements network interconnection above the network layer. It is a relatively complex network interconnection device and is usually used for interconnection between two networks with different high-level protocols. A gateway can be used for both wide area network interconnection and local area network interconnection. In addition, since a gateway is used between two systems with different network protocols, data formats or languages, or even completely different architectures, the gateway is also used to perform the important task of conversion between the two systems. It should be noted that the gateways involved in the embodiments of the present application may be deployed using a virtual machine or a physical server, and the embodiments of the present application do not specifically limit them.

[0093] A virtual private network (VPN) can be understood as a virtual internal dedicated line of an enterprise. It can establish a dedicated communication line between two or more enterprise intranets located in different places connected to the Internet through a special encrypted communication protocol.

[0094] Cloud Connect (CC) can provide a high-speed, high-quality, and stable network capability to quickly build cross-region VPCs and multiple VPCs on the cloud and multiple data centers under the cloud, helping users build a global cloud network with enterprise-level scale and communication capabilities.

[0095] Enterprise routers (ER) can connect to VPC or local networks to build hub-and-spoke networks. They are large-scale, high-bandwidth, and high-performance centralized routers on the cloud. Enterprise routers use the border gateway protocol (BGP), support route learning, dynamic routing, and link switching, greatly improving network scalability and operation and maintenance efficiency, thereby ensuring business continuity.

[0096] Domain name resolution is to point a domain name to the IP of a website space. It is a service that allows users to easily access a website through a registered domain name. An IP address is a digital address that identifies a site on the Internet. An IP address is usually a piece of data with a fixed length and is difficult to remember. In order to facilitate memory, a domain name is used instead of an IP address to identify a site address. Therefore, domain name resolution is the process of converting a domain name to an IP address. For example, the process of obtaining the IP address corresponding to a host name through a host name is called domain name resolution (or host name resolution), without having to remember the IP number string that can be directly read by a machine. Domain name resolution operations are usually performed by a domain name system (DNS). DNS is a distributed database on the Internet that maps domain names and IP addresses to each other, enabling users to access the Internet more conveniently.

[0097] Currently, before users use cloud services, their developers need to use the various resources provided by the cloud platform according to the user's demand for cloud services, create various network objects, and configure the network objects in order to build a cloud service network on the cloud platform to realize the cloud services required by users.

[0098] However, the current deployment of cloud service networks is subject to various restrictions, which affects the performance of cloud services provided by cloud service networks. On the one hand, the deployment of cloud service networks depends on the resources provided by the cloud platform, and the deployment location of resources affects the scope of cloud services provided by the cloud service network. On the other hand, cloud service networks usually include a large number of network objects, and the connection relationship between different network objects is complex. When implementing cloud services on the cloud platform, the network configuration that developers need to perform on the cloud platform is becoming more and more complex, which creates certain difficulties for developers. For example, an application is usually composed of multiple components and services, which may be distributed in multiple VPCs in different regions. In order to support the scalability, high availability and flexibility of the application, developers need to perform complex network configuration. At the same time, with the continuous increase of network security threats, security has become particularly important, so developers also need to configure more fine-grained access control and security policies for the network, which will also increase the complexity of network configuration. At the same time, different applications and services have different network requirements, such as low latency, high bandwidth, higher security and reliability, which will also increase the complexity of network configuration. In addition, different public cloud vendors provide different cloud services and solutions on cloud platforms, which lack standardization. For example, when connecting networks across regions, you can use cloud connections, dedicated lines, VPNs, and other methods, which requires developers to master a variety of different network configuration methods. In addition, when customer applications are deployed in multiple VPCs, VPC address conflicts require manual planning, and the configuration is complex and prone to errors. This also leads to poor availability of cloud services provided by cloud platforms.

[0099] For example, under the current cloud platform providing cloud services, the steps for building the cloud service network mainly include:

[0100] 1. Create a VPC in the specified region, configure the subnet segment and plan the address. When the cloud service network includes multiple VPCs, you need to avoid address conflicts between different VPCs when planning the address. In addition, when using IPv4 networking, you also need to pay attention to the problem of insufficient address space because the addresses of multiple VPCs across regions cannot conflict.

[0101] 2. Deploy the customer's application in each VPC, purchase a load balancer gateway, and configure the application's computing resources to the backend of the load balancer gateway.

[0102] 3. Purchase gateways such as cloud connections and enterprise routers, and configure them to connect VPCs in different regions.

[0103] 4. Configure security groups and other rules in the VPC where each application is located, and configure and register DNS.

[0104] 5. Provide public network access or services to access the public network and configure EIP.

[0105] 6. If the cloud service also needs to access the offline IDC, a VPN or DC needs to be established to connect to the offline IDC.

[0106] It can be seen that the current network configuration for building a cloud service network is relatively complex, resulting in poor availability of cloud services provided by the cloud platform.

[0107] To this end, an embodiment of the present application provides a cloud service provision method. In this method, the cloud platform needs to provide a network configuration interface and a network association interface to the user, and then associate multiple service nodes (services) based on the information entered by the user in these interfaces, so that a cloud service network for implementing the target cloud service can be obtained. Among them, the service node is used to deploy the user's application. The application is used to implement the target cloud service. The network configuration interface prompts the user to enter network feature information. The network feature information indicates the cloud service network that implements the target cloud service. The network association interface prompts the user to enter association information. The association information indicates multiple service nodes associated with the cloud service network. After the cloud platform obtains the network feature information and association information from the network configuration interface, it can establish an association relationship between multiple service nodes based on the network feature information and association information, and obtain a cloud service network, so as to provide the target cloud service to the user through the cloud service network.

[0108] In this cloud service network, since multiple service nodes are deployed based on resources in one or more resource deployment areas, the cloud service network is not limited to being deployed based on resources in a certain resource deployment area. The cloud service network can be regarded as a global network, which can use resources deployed in multiple resource deployment areas to provide services to users, thereby expanding the scope of cloud services provided by the cloud service network and improving the performance of cloud services provided by the cloud service network.

[0109] This article provides a detailed introduction to the technical solution of the present application from multiple perspectives, including implementation scenarios, method flow, hardware devices, and software devices.

[0110] The following first describes the application scenarios of the embodiments of the present application with examples.

[0111] Figure 1 It is a schematic diagram of the structure of the implementation environment involved in this application. Figure 1As shown, the implementation environment includes: a cloud platform 1 and a client 2. A communication connection can be established between the cloud platform 1 and the client 2 through a network. Optionally, the network can be a local area network, the Internet, or other networks, which is not limited in the embodiments of the present application. A user can interact with the cloud platform 1 through the client 2. For example, a user can send instructions and cloud service requests and other information to the cloud platform 1 through the client 2. The cloud platform 1 is used to respond based on the information sent by the client 2 to the cloud platform 1.

[0112] A large number of basic resources owned by the cloud service provider are deployed in the cloud platform 1, such as computing resources, storage resources, and network resources. For example, computing resources can be computing devices (such as servers, etc.) that can provide computing capabilities. The cloud platform can use this large number of basic resources to implement the cloud service provision method provided in the embodiment of the present application. In the embodiment of the present application, the cloud platform 1 can be a cloud platform of a central cloud, a cloud platform of an edge cloud, or a cloud platform including a central cloud and an edge cloud, and the embodiment of the present application does not make specific limitations on it. In addition, when the cloud platform 1 is a cloud platform including a central cloud and an edge cloud, the technical solution provided in the embodiment of the present application can be partially executed by a cloud platform deployed in an edge cloud and partially executed by a cloud platform deployed in a central cloud. In addition, the cloud platform 1 can be a cloud platform of a private cloud or a public cloud, and the embodiment of the present application does not make specific limitations on it.

[0113] In one implementation, Figure 2 As shown in the figure, the location of resources in the cloud platform can be described by regions and availability zones (AZs). Users can create resources in specific regions and AZs. Regions are divided based on geographical location and network latency. Public services such as elastic computing, block storage, object storage, VPC network, EIP, and mirroring are shared within the same region. Regions are divided into general regions and dedicated regions. General regions refer to regions that provide general cloud services to public tenants. Dedicated regions refer to dedicated regions that only carry the same type of business or only provide business services to specific tenants. AZ is a collection of one or more physical data centers. AZ logically divides computing, network, storage and other resources into multiple clusters. Usually a region can include multiple AZs. Multiple AZs in a region are connected by high-speed optical fibers to meet the needs of users to build high-availability systems across AZs.

[0114] The client 2 can be a computer, a personal computer, a laptop computer, a mobile phone, a smart phone, a tablet computer, a cloud host 1111, a portable mobile terminal, a multimedia player, an e-book reader, a wearable device, a smart home appliance, an artificial intelligence device, a smart wearable device, a smart vehicle-mounted device or an Internet of Things device, etc.

[0115] In the embodiment of the present application, the user can access the cloud platform through the client 2, input information in the interface provided by the cloud platform, so that the cloud platform creates a cloud service network for the user according to the input information, and the cloud service network is used to implement the user's cloud service. At this time, the function of the cloud platform to create a cloud service network for the user can be abstracted into a cloud service by the cloud service provider on the cloud platform. The cloud service can be provided as an independent cloud service or as an additional service of other cloud services.

[0116] In one implementation, the cloud service providing method provided in the embodiment of the present application can be implemented by running an executable program on a computing device in the cloud platform 1. For example, in the cloud service providing method, the cloud platform provides an interface to the user, and performs related operations based on the information input by the user in the interface. The functions can be presented in the form of an application installation package. After the computing device in the cloud platform 1 installs the application installation package, the corresponding functions can be implemented by running the executable program therein.

[0117] It should be understood that the above content is an illustrative description of the application scenarios of the cloud service providing method provided in the embodiments of the present application, and does not constitute a limitation on the application scenarios of the cloud service providing method. Ordinary technicians in this field can know that as business needs change, its application scenarios can be adjusted according to application needs, and the embodiments of the present application do not list them one by one.

[0118] The following is an explanation of the cloud service providing method provided in the embodiment of the present application. Figure 3 As shown, the cloud service providing method includes the following steps:

[0119] Step 301: The cloud platform receives a cloud service provision request sent by a user.

[0120] When a user needs the cloud platform to provide cloud services to him, he can perform specified operations on the client used by the user to instruct the client to send a cloud service provision request to the cloud platform to request the cloud platform to provide the corresponding cloud service to the user.

[0121] Step 302: The cloud platform provides a resource configuration interface to the user based on the cloud service provision request. The resource configuration interface prompts the user to input resource feature information. The resource feature information indicates the resources required by the user.

[0122] In the present application, after the cloud platform receives the cloud service provision request sent by the user, it can provide the user with a resource configuration interface to prompt the user to enter resource feature information. The resource feature information indicates the resources required by the user, that is, the resources used by the user to deploy the service node. For the cloud service network used in the present application to implement user cloud services, it can be obtained based on the resource deployment of different resource deployment areas in the cloud platform. The resources in each resource deployment area can be regarded as belonging to a resource type. Then the resource configuration interface needs to prompt the user to select the resource type required by the user from a variety of resource types. For example, the resources available for users to choose in the present application include: public network resources, cloud resources in the cloud resource deployment area, and resources in multiple resource deployment areas such as the user's own resources. It should be understood that with the development of cloud service technology, the selectable resource types can be adjusted according to application requirements, and the embodiments of the present application do not list them one by one.

[0123] Public network resources are resources deployed on the Internet. When a cloud service network is created based on public network resources, it is optional to directly use services that have been created on the Internet to create a cloud service network. Then the resource configuration interface needs to prompt the user to enter the identification information of the created service, and the resource feature information includes the identification information. For example, the identification information of the service is the IP address or domain name of the service.

[0124] Cloud resources are a large number of basic resources owned by cloud service providers. For example, a region or a combination of multiple regions can be called a cloud resource deployment area. Alternatively, an AZ or a combination of multiple AZs can be called a cloud resource deployment area. When a cloud service network is created based on cloud resources, the resource configuration interface needs to prompt the user to enter the indication information of the cloud resources, and the resource feature information includes the indication information. In one implementation, the indication information indicates the specifications and quantity of the cloud resources, so that the cloud platform can determine the cloud resources used to create cloud services based on the specifications and quantity. Furthermore, the indication information also indicates the cloud resource deployment area to which the cloud resources belong, such as the region to which the cloud resources belong, that is, at this time the user needs to specify the cloud resource deployment area to which the cloud resources belong. It should be understood that the presentation form of the indication information can be optionally adjusted according to application requirements, as long as it is ensured that the cloud platform can determine the cloud resources based on the indication information.

[0125] Owned resources are resources owned by users and located outside the cloud platform. For example, owned resources are resources in the user's offline computer room, such as IDC, or resources in other cloud platforms purchased by the user. When a cloud service network is created based on owned resources, the cloud platform can choose to directly use the services created in its own resources to create a cloud service network. Then the resource configuration interface needs to prompt the user to enter the identification information of the created service, and the resource feature information includes the identification information. For example, the identification information of the service is the IP address of the service, etc.

[0126] Optionally, the resource can be provided in the form of a virtual local area network. A virtual local area network includes multiple computing instances with a specified network relationship. For example, the virtual local area network is a virtual private cloud. The source of the virtual local area network can be created based on the resources selected by the user, or the virtual local area network can be selected by the user from an existing virtual local area network (also known as a stock virtual local area network). The resource configuration interface also needs to prompt the user to enter the source of the virtual local area network, and the resource feature information includes information indicating the source. For example, Figure 4 Schematic diagram of a resource configuration interface for indicating the creation of a VPC provided by an embodiment of the present application. Figure 4 As shown in FIG. 1 , when the user chooses to automatically create a VPC, the resource configuration interface also presents a purchase option to the user to prompt the user to select the resource type required to create the VPC, such as computing resources and / or container resources. When the user selects one of the types, the corresponding resource purchase interface continues to be presented to the user (the interface is in Figure 4 ), for the user to select the quantity and specifications of the resources. Figure 5 Schematic diagram of indicating the use of existing VPC in a resource configuration interface provided by an embodiment of the present application. Figure 5 As shown, when the user chooses not to automatically create a VPC, the resource configuration interface presents the user with a drop-down selection box of existing VPCs, so that the user can select the desired VPC from the existing VPCs. At the same time, the resource configuration interface also presents the user with a drop-down selection box for selecting the desired instance type and instance identification number from the existing VPCs. For example, the user selects VPC1 and VPC2 according to the drop-down selection box, and selects the virtual machine with identification number 12343523242 in VPC1, and the container with identification number 12343523243 in VPC2. Furthermore, the resource configuration interface can also present the user with a resource list of resources owned by the user ( Figure 4 and Figure 5 The resource list contains the following information: resource identification number, name, status (such as running or not running) and available zone. It should be noted that when selecting a virtual local area network, the user can select some or all resources in the virtual local area network. In addition, the user can select one or more virtual local area network deployment service nodes.

[0127] Among them, the resources used to create a cloud service network in this application may optionally include one or more computing instances. For example, computing instances include: virtual machines, containers, functions, and bare metal servers. The resource configuration interface also provides the user with the type of computing instance to enter in the interface. Correspondingly, the resource configuration interface also needs to prompt the user to enter the type of computing instance of the resource, and the resource feature information also includes indication information of the type of computing instance.

[0128] In addition, when the cloud platform prompts the user to enter the resources they need, the user can choose to select resources in units of service nodes or in units of resource collections. Since service nodes can be deployed based on one or more resource collections, when resources are selected in units of service nodes, the resource configuration interface will prompt the user to enter all the resources required for a service node in the interface. When resources are selected in units of resource collections, the cloud platform can optionally display one or more resource configuration interfaces to the user, each of which prompts the user to enter the resources included in a resource collection. At this time, the resource configuration interface is also used to prompt the user to enter the name of the resource collection to distinguish between different resource collections. The resource feature information also indicates the name of the resource collection. Among them, the resource collection is also called a member group.

[0129] Furthermore, the user can also indicate the network protocol used by the resource set used to deploy the service node. At this time, the resource configuration interface also needs to prompt the user to enter the network protocol used by the resource set. When the user enters the resource feature information in the resource configuration interface, the network protocol that the current resource set needs to use can be entered according to the application requirements. The resource feature information also indicates the network protocol used by the resource set. For example, the resource configuration interface presents the user with a drop-down selection box for selecting the network protocol used by the resource, so that the user can select the network protocol used by the resource set in the drop-down selection box. The options for the network protocol are: Ipv4, Ipv6, and Remote Direct Memory Access (RDMA) protocol, etc.

[0130] Optionally, multiple service nodes in the cloud service network may use different network protocols, that is, multiple resource sets used to deploy multiple service nodes in the cloud service network use different network protocols. In this case, the cloud service network can support access using different network protocols, such as supporting mutual access between IPv4 and IPv6. Similarly, when the same service node is deployed based on multiple resource sets, the multiple resource sets used to deploy the service node may also use different network protocols. In this case, the service node can support access using different network protocols, such as supporting mutual access between IPv4 and IPv6. Among them, multiple service nodes in the cloud service use different network protocols, including: the network protocols used by all service nodes in the cloud service network are different, or some service nodes in the cloud service network use the same network protocol, and some service nodes use different network protocols. Multiple resource sets used to deploy service nodes use different network protocols, including: the network protocols used by multiple resource sets used to deploy service nodes are different, or some resource sets in multiple resource sets used to deploy service nodes use the same network protocol, and some resource sets use different network protocols.

[0131] Step 303: The cloud platform obtains resource feature information from the resource configuration interface.

[0132] After the user enters resource feature information in the resource configuration interface, the cloud platform can obtain the resource feature information entered by the user from the resource configuration interface.

[0133] Step 304: The cloud platform obtains a first resource set including resources indicated by resource characteristic information.

[0134] To facilitate the distinction from the resource set used to deploy the client, the resource set used to deploy the service node is referred to as the first resource set in this article, and the resource set used to deploy the client is referred to as the second resource set. After the cloud platform obtains the resource feature information, it is necessary to obtain the first resource set based on the resource feature information. All resources in any first resource set are deployed in the same resource deployment area. Its implementation process includes: based on the indication of the resource feature information, determining the resources indicated by the resource feature information in the resource deployment area, and determining it as belonging to the first resource set for deploying the service node. For example, when the resource feature information indicates the specifications and quantity of cloud resources that the first resource set needs to include, the cloud platform obtains the first resource set including: using the basic resources in the cloud resource deployment area, creating resources that meet the specifications and quantity indicated by the resource feature information, and marking the resource as a resource in the first resource set. For another example, when the resource feature information also indicates the cloud resource deployment area to which the cloud resource belongs, the cloud platform uses the basic resources in the cloud resource deployment area to create resources of the first resource set. For another example, when the resource characteristic information indicates that a new virtual LAN and the number and specifications of the resources it depends on need to be created, the cloud platform uses the basic resources in the cloud resource deployment area to create a virtual LAN that meets the specifications and quantity indicated by the resource characteristic information, and marks the virtual LAN as a resource of the first resource set. For another example, when the resource characteristic information indicates the use of resources of an existing virtual LAN, the cloud platform may mark the existing virtual LAN as a resource of the first resource set. Furthermore, when the resource characteristic information indicates that the resources used to deploy the service node are all or part of the resources in the virtual LAN, the cloud platform needs to select all or part of the resources indicated by the resource characteristic information in the virtual LAN, such as selecting computing resources of deployed applications in the existing virtual LAN, and mark the selected resources as resources of the first resource set.

[0135] In addition, when the resource feature information also includes information indicating the type of the computing instance, when the cloud platform obtains the first resource set, the type of the computing instance in the first resource set is the type that conforms to the type indicated by the indication information. For example, when the resource feature information indicates that the type of the computing instance is a virtual machine, all the computing instances in the first resource set are virtual machines. When the resource feature information indicates that the type of the computing instance includes virtual machines and containers, some of the computing instances in the first resource set are virtual machines and some are containers.

[0136] It should be noted that if the resource characteristic information also indicates the network protocol used by the first resource set of the deployment service node, the cloud platform needs to select resources that use the network protocol when acquiring the first resource set. If the resource characteristic information does not indicate the network protocol used by the resource, the cloud platform does not need to pay special attention to the network protocol used by the resource when acquiring the first resource set. For example, when the resource characteristic information indicates that the resource uses the Ipv4 protocol, the cloud platform needs to select ports that use the Ipv4 protocol when determining the ports in the first resource set. When the resource characteristic information indicates that the resource uses the Ipv6 protocol, the cloud platform needs to select ports that use the Ipv6 protocol when determining the ports in the first resource set.

[0137] It should be noted that the above content is explained by taking the example of requiring the user to select the resources that constitute the first resource set in the resource configuration interface, but it does not exclude the implementation process in which the user does not need to select the resources for deploying the service node, and the user does not need to deploy the service node. For example, when the first resource set already exists in the cloud platform, or there are surplus first resource sets created by the user in the previous process of deploying cloud services, when the user needs to create a cloud service network, he can choose to directly select the first resource set required for deploying the service node from these existing first resource sets, without selecting the resources that constitute the first resource set in the resource configuration interface. For another example, when the user does not need to deploy the service node, the user does not need to select the resources that constitute the first resource set in the resource configuration interface. It should be understood that when the user does not need to select the resources that constitute the first resource set in the resource configuration interface, there is no need to perform the above steps 302 to 304.

[0138] Step 305: The cloud platform provides a service configuration interface to the user. The service configuration interface prompts the user to enter service feature information. The service feature information indicates the service node and all first resource sets required to deploy the service node. The service node is used to deploy the user's application, and the application is used to implement the target cloud service.

[0139] In the present application, the cloud platform can provide a service configuration interface to the user to prompt the user to input service feature information so that the cloud platform creates a service node in the cloud service network according to the service feature information. The service feature information indicates the service node and all first resource sets required to deploy the service node. In one implementation, the service configuration interface prompts the user to input the name of the service node and the names of all first resource sets required to deploy the service node, so as to identify the service node by the name of the service node and identify the first resource set required to deploy the service node by the name of the first resource set. Accordingly, the service feature information carries the name of the service node and the names of all first resource sets required to deploy the service node.

[0140] In one implementation, for any service node, the service node can be optionally deployed based on resources in one or more resource deployment areas. By way of example, the service node satisfies one or more of the following: it is deployed based on cloud resources in different cloud resource deployment areas in the cloud platform; and it is deployed based on at least two of public network resources, cloud resources in cloud resource deployment areas, and the user's own resources. At this time, since the service node is not limited to being deployed based on resources in a certain resource deployment area, it can be seen that the service node can use resources deployed in multiple resource deployment areas to provide services to users, then the service node can be regarded as a global service node. When a user wants to deploy a global service node, it is necessary to indicate multiple first resource sets for deploying the service node in the service configuration interface, so as to convey to the cloud platform service feature information indicating that the service node is deployed based on multiple first resource sets. Among them, all resources in any first resource set are deployed in the same resource deployment area. By way of example, Figure 6 Schematic diagram of a service configuration interface provided by an embodiment of the present application. Figure 6 As shown, according to the service feature information currently input in the service configuration interface, it can be obtained that the name of the service node is App1, and all the first resource sets required by it are: member group1, member group2 and membergroup3. It can be seen that the service node needs to be deployed based on the resources in the three resource deployment areas, and the service node that the user needs to deploy is a global service node.

[0141] Similarly, the cloud service network may be optionally a global network. The global network includes multiple service nodes, and the multiple service nodes are deployed based on resources in multiple resource deployment areas. For example, multiple service nodes meet one or more of the following: multiple service nodes are deployed based on cloud resources in different cloud resource deployment areas in the cloud platform; and multiple service nodes are deployed based on at least two of public network resources, cloud resources in cloud resource deployment areas, and users' own resources. Therefore, the global network is not limited to being deployed based on resources in a certain resource deployment area, and can provide services to users using resources deployed in multiple resource deployment areas. If the user wants to deploy a global network, the first resource set for deploying service nodes in the global network can be optionally indicated in the service configuration interface according to demand, without worrying about whether the first resource set conflicts with the resources used to deploy other service nodes. Moreover, in the present application, different service nodes may also be optionally deployed based on the same resource set, and the at least two service nodes may optionally belong to the same cloud service network or to different cloud service networks. When indicating the first resource set for deploying the service node in the service configuration interface, there is no need to consider whether the first resource set conflicts with the resources for deploying other service nodes.

[0142] Since it is also necessary to configure listeners and routing rules for the service nodes when deploying the service nodes, the service configuration interface also needs to prompt the user to enter the listener information and related rules, and the service feature information also includes the listener information and related rules. Among them, the listener information indicates the listening protocol used by the service node and the port used by the listener and other information. Multiple service nodes in the cloud service network can optionally use the same or different listening protocols. When multiple service nodes in the cloud service network use different listening protocols, the cloud service network can support access to applications using different listening protocols, thereby improving the diversity of cloud services provided by the cloud service network. In one implementation, the service configuration interface presents an input box for information such as ports to the user, so that the user can enter information such as ports of the service node. Similarly, the service configuration interface presents a drop-down selection box for selecting the listening protocol used by the service node to the user, so that the user can select the listening protocol used by the service node. Optionally, the alternative listening protocols include: transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), hypertext transfer protocol over secure socket layer (HTTPS), quick UDP Internet connection (QUIC) protocol, etc. The listening protocol used by the service node determines the application type of the service node. For example, when the service node uses the TCP protocol, the application type of the service node is a layer 4 (layer 4, L4) application. When the service node uses the http protocol, the application type of the service node is a layer 7 (layer 7, L7) application. Figure 6 As shown, according to the service characteristic information currently input in the service configuration interface, it can be obtained that the listening protocol used by the service node is the http protocol, and the http port of the listener is port 80, so the service node is a seven-layer application.

[0143] The service configuration interface also prompts the user to enter the routing rules (rules) and corresponding operations (actions) of the service node. The routing rules indicate the first resource set to which the traffic of the service node should be sent. The operations indicate the operations that should be performed when the traffic is sent to the first resource set. The service configuration interface is also provided with buttons for adding routing rules, deleting routing rules, adding operations, and deleting operations, so that users can add or delete routing rules and operations as needed. When the service node is deployed based on multiple first resource sets, the service configuration interface also allows users to enter multiple routing rules. Each routing rule is set with priority, path conditions, and operations. Each operation is bound to a first resource set and a weight is set. When a request matches the path condition of the routing rule, it will be sent to the corresponding first resource set with a corresponding probability according to the weight of the corresponding operation, otherwise it will be sent according to the default routing rule. The default routing rule can be selected as a rule without a path condition. For example Figure 6 As shown, according to the service feature information currently input in the service configuration interface, it can be obtained that: the routing rule indicates that 50% of the traffic is routed to member group 1, 20% of the traffic is routed to member group 2, and 30% of the traffic is routed to member group 3, and member group 1 is located in region Beijing 1, member group 2 is located in region Shanghai 2, and member group 3 is located in region Guangzhou 3.

[0144] In addition, the service configuration interface also prompts the user to enter the cloud service network associated with the service node, and the service feature information also indicates the cloud service network associated with the service node. Figure 6 As shown, according to the service feature information currently input in the service configuration interface, it can be obtained that the service node App1 is associated with a cloud service network named Global Network 1. Optionally, a service node can be associated with one or more cloud service networks, and multiple cloud service networks are used to implement different cloud services. When the application needs require a service node to be associated with multiple cloud service networks, the user can choose to enter all cloud service networks associated with the service node in the service configuration interface.

[0145] Step 306: The cloud platform obtains service feature information from the service configuration interface.

[0146] After the user enters the service feature information in the service configuration interface, the cloud platform can obtain the service feature information entered by the user from the service configuration interface. Optionally, the cloud platform can also obtain the identity information of the user who deploys the service node. In one implementation, the service feature information also indicates the user who deploys the service node. For example, there is content in the service configuration interface that prompts the user to enter the identity information. After the user enters the identity information in the service configuration interface, the cloud platform can obtain the identity information of the user who indicates the deployment of the service node. Alternatively, there is no content in the service configuration interface that prompts the user to enter the identity information, but the cloud platform can automatically identify the user's identity according to the user's input operation in the service configuration interface to obtain service feature information including the user's identity information. Alternatively, the cloud service provision request sent by the user to the cloud platform carries the user's identity information. Alternatively, before sending the cloud service request to the cloud platform, the user sends authentication information to the cloud platform, and the authentication information carries the user's identity information. In the present application, multiple service nodes of the cloud service network can be optionally deployed by the same user, or deployed by multiple users respectively. When multiple service nodes of a cloud service network are deployed by different users, the cloud service network can be considered to support cross-account access.

[0147] Step 307: The cloud platform deploys service nodes using all first resource sets based on instructions of the service feature information.

[0148] After the cloud platform obtains the service feature information, it can deploy the service node based on all the first resource sets indicated by the service feature information. In one implementation, the process of deploying the service node is actually to deploy an instance of the application program for running the service node (such as plugging a network card into the instance), and the related equipment required for the instance to provide services. The related equipment is responsible for forwarding the data packet between the nodes that transmit the data packet with the service node. By way of example, the related equipment is a NAT gateway or an elastic load balancing (ELB) gateway, etc.

[0149] According to the previous description, the user can indicate the listening protocol used by the service node through the resource feature information, and the relevant device should also be configured with relevant functions that match the listening protocol used by the service node to support the use of the listening protocol. For example, when the service node is a seven-layer application, the ELB gateway of the service node also has the function of supporting seven-layer application access.

[0150] According to the above description, the user can indicate the network protocol used by the first resource set for deploying the service node through resource feature information, and multiple first resource sets for deploying the same service node use different network protocols. At this time, the method also includes: the cloud platform uses the first resource set for deploying the service node to deploy a service agent for the service node. The service agent is used to perform address conversion on the messages sent and received by the service node so that the service node can support mutual access of applications using different network protocols. In one implementation, when different service nodes in the cloud service network are associated with a transit network, the service agent is used to convert the destination address and source address of the message transmitted between the service node and the transit network when the service node and the transit network use different network protocols to an address that conforms to the network protocol used by the service node and the receiving end in the transit network. Optionally, the implementation form of the service agent is a NAT gateway or an ELB gateway. For example, when the transit network uses the Ipv6 protocol and the service node uses the Ipv4 protocol, the ELB gateway of the service node is used as a service agent, and the ELB gateway occupies an Ipv6 address in the transit network. When a data packet whose source and destination IP addresses are both IPv6 addresses needs to be sent to a service node via a transit network, the ELB gateway is used to convert both the source and destination IP addresses of the data packet into IPv4 addresses. When a data packet whose source and destination IP addresses are both IPv4 addresses needs to be sent to other service nodes via a transit network, the ELB gateway is used to convert both the source and destination IP addresses of the data packet into IPv6 addresses.

[0151] The cloud platform deploys service agents for service nodes and uses the service agents to perform automatic conversion of network protocols, so that service nodes can support application mutual access using different network protocols without the need to modify the service nodes. This enables the cloud service provision method provided in this application to provide cloud services in a variety of scenarios, and its application scenarios do not need to be restricted by network protocols, thereby expanding the application scope of the cloud service provision method.

[0152] It should be noted that the above content is described with the example of requiring the user to deploy the service node, but it does not exclude the implementation process without the user deploying the service node. For example, when the service node that the cloud service network needs to be associated with already exists, when the user creates the cloud service network, he can choose to directly associate the service node without first deploying the service node. It should be understood that when the user does not need to deploy the service node, it is not necessary to perform the above steps 302 to 307.

[0153] Step 308: The cloud platform provides a network configuration interface to the user. The network configuration interface prompts the user to input network characteristic information. The network characteristic information indicates a cloud service network for implementing a target cloud service.

[0154] In the present application, the cloud platform can provide a network configuration interface to the user to prompt the user to enter network feature information so that the cloud platform creates a cloud service network based on the network feature information. Creating a cloud service network here refers to creating a public platform that can provide cloud services, and does not include creating service nodes for providing services. In one implementation, the network feature information optionally includes the name of the cloud service network, which is used to indicate the cloud service network. Among them, the network configuration interface also prompts the user to enter all resource deployment areas covered by the cloud service network. Alternatively, the network configuration interface does not prompt the user to enter the resource deployment area covered by the cloud service network. At this time, the resource deployment area covered by the cloud service network can be automatically determined based on the resource deployment areas of multiple service nodes associated with the cloud service network. Optionally, the network configuration interface also prompts the user to enter all service nodes associated with the cloud service network.

[0155] It should be noted that the user who instructs the deployment of the cloud service network and the user who instructs the deployment of all service nodes in the cloud service network can be the same or different. For example, the management department of a company instructs the deployment of a cloud service network, and multiple business departments of the company instruct the deployment of multiple service nodes respectively. When the user who instructs the deployment of the cloud service network is different from the user who instructs the deployment of all service nodes in the cloud service network, the cloud service network can be considered to support cross-account access.

[0156] Step 309: The cloud platform obtains network feature information from the network configuration interface.

[0157] After the user enters the network characteristic information in the network configuration interface, the cloud platform can obtain the network characteristic information entered by the user from the network configuration interface.

[0158] Step 310: The cloud platform provides a network association interface to the user. The network association interface prompts the user to input association information. The association information indicates multiple service nodes associated with the cloud service network.

[0159] In the present application, the cloud platform can provide a network association interface to the user to prompt the user to input association information, so that the cloud platform can associate multiple service nodes according to the association information to obtain a cloud service network including multiple service nodes. The association information indicates multiple service nodes associated with the cloud service network. In terms of implementation, the network association interface can be selected as a separate interface, or as a part of other interfaces. For example, after the cloud platform provides the user with a service configuration interface and a network configuration interface, it also provides the user with a separate network association interface to prompt the user to input association information in the separate network association interface. Alternatively, when the service configuration interface is able to prompt the user to input the cloud service network associated with the service node, the small block interface in the service configuration interface that serves as the prompt can be called a network association interface, that is, the network association interface is part of the service configuration interface. Alternatively, when the network configuration interface is able to prompt the user to input all service nodes associated with the cloud service network, the small block interface in the network configuration interface that serves as the prompt can be called a network association interface, that is, the network association interface is part of the network configuration interface. By way of example, Figure 7 It is a schematic diagram of a network association interface provided in an embodiment of the present application as a part of a network configuration interface.

[0160] Step 311: The cloud platform obtains association information from the network association interface.

[0161] After the user inputs the association information in the network association interface, the cloud platform can obtain the association information input by the user from the network association interface.

[0162] Step 312: The cloud platform establishes associations between multiple service nodes based on the network feature information and association information to obtain a cloud service network.

[0163] After the cloud platform obtains the network characteristic information, it can create a public platform that can provide cloud services indicated by the network characteristic information. After the cloud platform obtains the association information, it can establish an association relationship between multiple service nodes indicated by the association information in the public platform to obtain a cloud service network. Establishing an association relationship between multiple service nodes is actually to open up a network for multiple service nodes in the cloud service network to access each other. Optionally, its implementation process includes: the cloud platform creates a transit network based on the network characteristic information and the association information, associates multiple service nodes with the transit network, and obtains a cloud service network. In addition, when the cloud service network is deployed across resource deployment areas, the transit network needs to associate the service nodes obtained based on the deployment across resource deployment areas. In one implementation, association refers to assigning an address to the service node from the transit network, binding the address to the service node, and using the address as the access entry of the service node. For example, when a service agent (such as an ELB gateway) is configured for a service node, the association process is actually to assign an address to the service agent and bind the service agent to the address. For example: when the transit network uses the Ipv6 protocol, the cloud platform will allocate the Ipv6 address 2001:db8:1234:1d02::a to the ELB1 corresponding to service node 2, and allocate the Ipv6 address 2001:db8:1234:1b03::b to the ELB2 corresponding to service node 3 during the process of associating service node 2 and service node 3. Optionally, the transit network can be implemented through cloud connection or SD-WAN. Among them, associating multiple service nodes through a transit network is an example, and those skilled in the art should know that there are other implementation methods that can realize this function, and the embodiments of the present application do not list them one by one.

[0164] In addition, when the service node is deployed based on public network resources, the cloud platform can choose to directly use the services created in the public network to create a cloud service network. When associating service nodes, it is necessary to associate the created service with other service nodes in the cloud service network. When the cloud service network is created based on its own resources, the cloud platform can choose to directly use the services created in its own resources to create a cloud service network. When associating service nodes, it is necessary to associate the created service with other service nodes in the cloud service network.

[0165] Optionally, the transit network is also used to convert the addresses of multiple service nodes. Since different service nodes in the cloud service network need to pass through the transit network when visiting each other, the transit network can obtain the addresses of all service nodes in the cloud service network, and when the addresses of different service nodes conflict, uniformly assign addresses to these service nodes, and convert the addresses of the service nodes into unique addresses in the cloud service network, so that the addresses of the service nodes no longer conflict. For example, when multiple service nodes in the cloud service network all use the IPv4 protocol, and the addresses of some of the service nodes conflict, the transit network can uniformly plan the addresses of the service nodes by converting the addresses for these service nodes, thereby solving the problem of address conflicts of the IPv4 protocol for multiple service nodes. In this way, the cloud service network can solve the problems of IPv4 address conflicts and insufficient address space, so that users do not need to plan the network and address space, further improving the availability of cloud services provided by the cloud platform.

[0166] In addition, when creating a cloud service network, you can also create a domain name server in the cloud service network to avoid exposing the IP address of the service node. The domain name server automatically configures domain name resolution in the DNS of VPC1 in application 1: app2.com:192.18.0.2, app3.com:192.18.0.3. After deploying the service node, the cloud platform assigns a domain name to the service node, such as assigning the domain name app2.com to the service node App2 and the domain name app3.com to the service node App3. Then, the cloud platform creates a domain name mapping table in the domain name server, which records the correspondence between the domain name and IP address of the service node in the cloud service network. The domain name server is used to perform domain name resolution based on the domain name mapping table. For example, the IP address corresponding to app2.com is 192.18.0.2, and the IP address corresponding to app3.com is 192.18.0.3. When the domain name server receives a domain name resolution request carrying the domain name app2.com, it can obtain its corresponding IP address as 192.18.0.2 according to the domain name mapping table. In addition, when the domain name mapping relationship of the service node changes, the domain name mapping table needs to be updated accordingly. In addition, the cloud platform can create a domain name server for each virtual local area network, and the domain name server is responsible for the domain name resolution task in the virtual local area network.

[0167] It can be seen from this that the embodiment of the present application provides an application-oriented network model. The network model includes a resource layer, a service node layer, and a cloud service network layer. Due to the existence of this network model, when a user needs a cloud platform to provide cloud services to the user, the cloud platform needs to provide the user with a resource configuration interface, a service configuration interface, a network configuration interface, and a network association interface to obtain information related to the user input, and perform related operations according to the information input by the user, so as to obtain a cloud service network for providing the cloud services required by the user, and use the cloud service network to provide cloud services to the user. In this way, in the process of providing the cloud service, the user does not need to perform complex network configuration, which reduces the difficulty for the user to use the cloud services provided by the cloud platform, and helps to improve the availability of the cloud services provided by the cloud platform.

[0168] like Figure 8 As shown, the network model includes the following three layers: cloud service network, service node and first resource set. Figure 8 The cloud service network is a global network, the service node is a service, and the first resource set is a member group. The main features of the network model are shown in Table 1.

[0169] Table 1

[0170]

[0171]

[0172] Optionally, the user can also deploy the client in the cloud service network. There are many ways to deploy the client, and the following three are used as examples to illustrate them.

[0173] In the first implementation, the service configuration interface or network configuration interface also prompts the user to select whether the service node is reused as a client, and the service feature information or network configuration information also indicates that the specified service node is reused as a client. In this case, the cloud service network associated with the service node and the client obtained by reuse is the same. Fig. 9 As shown, the method further includes: step 313, the cloud platform uses all the first resource sets for deploying service nodes to deploy the client and associate the client with the cloud service network. Figure 7 As shown, each service node is also configured with an option to select whether the service node "actively accesses other applications". When the user does not need to reuse the service node as a client, do not check this option. When the user needs to reuse the service node as a client, check this option. At this time, the network configuration information also indicates that the service node is reused as a client. Figure 7The network characteristic information currently input in the network configuration interface can be obtained: service nodes service1 and service2 are reused as clients, and service3 is not reused as a client. After the cloud platform obtains the network characteristic information, it can deploy client 1 based on all the first resource sets used to deploy service node service1, and associate client 1 with the cloud service network, and deploy client 2 based on all the first resource sets used to deploy service node service2, and associate client 2 with the cloud service network. Among them, the process of creating a client is actually to deploy an instance of an application for running the client and the related equipment required for the instance to access. The related equipment is responsible for forwarding the data packet between the nodes that transmit the data packet with the client. For example, the related equipment is a NAT gateway, etc., and the NAT gateway is used to proxy the service node to the local network segment of the client, such as: 198.18.0.0 / 15. In addition, when the first resource set is presented in the form of a virtual local area network, if the resources used to deploy the service node include multiple virtual local area networks, when creating a NAT gateway and other equipment for the client, it is necessary to create a NAT gateway and other equipment for each virtual local area network. Associating the client with the cloud service network is actually binding the client with the cloud service network. For its implementation method, please refer to the implementation method of associating the service node with the cloud service network, which will not be repeated here.

[0174] In a second implementation, the service configuration interface or the network configuration interface further prompts the user to input whether any of the first resource sets used to deploy the service node is also used to deploy the client, and the service feature information or the network configuration information further indicates that the specified first resource set is also used to deploy the client. In this case, the client is associated with the same cloud service network as the specified first resource set. Fig.10 As shown, the method further includes: step 314, the cloud platform deploys the client based on the specified first resource set, and associates the client with the cloud service network. For example, if the service feature information also indicates that VPC1 of the first resource set is also used to deploy the client, then after the cloud platform obtains the service feature information, it can deploy client 1 based on VPC1 used to deploy service node service1, and associate client 1 with the cloud service network. For the implementation method, please refer to the relevant description in the first implementation method of the client, which will not be repeated here.

[0175] In the third implementation, Fig.11As shown, the method further includes: step 315, the cloud platform provides a client configuration interface to the user, the client configuration interface prompts the user to enter the client feature information, the client feature information indicates the client and the second resource set required for deploying the client. Step 316, the cloud platform obtains the client feature information from the client configuration interface. Step 317, the cloud platform deploys the client using the second resource set based on the indication of the client feature information, and associates the client with the cloud service network.

[0176] In the present application, the cloud platform can provide the user with a client configuration interface to prompt the user to input the client characteristic information so that the cloud platform creates a client in the cloud service network according to the client characteristic information. The client characteristic information indicates the client and all second resource sets required to deploy the client. In one implementation, the client configuration interface prompts the user to input the name of the client and the names of all second resource sets required to deploy the client, so as to identify the client by the name of the client and identify the second resource sets required to deploy the client by the name of the second resource set. Accordingly, the client characteristic information carries the name of the client and the names of all second resource sets required to deploy the client.

[0177] In one implementation, the client can be optionally obtained based on resource deployment in one or more resource deployment areas. For example, the client satisfies one or more of the following: it is obtained based on cloud resource deployment in different cloud resource deployment areas in the cloud platform; and it is obtained based on at least two of public network resources, cloud resources in cloud resource deployment areas, and the user's own resources. At this time, since the client is not limited to being obtained based on resource deployment in a certain resource deployment area, it can be seen that the client can use resources deployed in multiple resource deployment areas to achieve access, then the client can be regarded as a global client. When the user wants to deploy a global client, it is necessary to indicate multiple second resource sets for deploying the client in the client configuration interface, so as to convey to the cloud platform the client feature information indicating that the client is deployed based on multiple second resource sets. Among them, all resources in any second resource set are deployed in the same resource deployment area.

[0178] In addition, the client configuration interface also prompts the user to enter the cloud service network associated with the client, and the client characteristic information also indicates the cloud service network associated with the client. Optionally, a client can be associated with one or more cloud service networks, and multiple cloud service networks are used to carry different cloud services. When application requirements require a client to be associated with multiple cloud service networks, the user can choose to enter all cloud service networks associated with the client in the client configuration interface.

[0179] In the third implementation, the user who indicates the deployment of the client may be the same or different from the user who indicates the deployment of the cloud service network and the user who indicates the deployment of the service node, and the embodiment of the present application does not specifically limit it. This implementation is equivalent to binding a second resource set (such as a virtual local area network) that is not bound to any client as a client. When this implementation deploys the client based on the virtual local area network of the resource set, when creating devices such as a NAT gateway for the client, it is necessary to create devices such as a NAT gateway for each virtual local area network.

[0180] When the cloud service network also includes a client, the resource set for deploying the client and the resource set for deploying the service node can optionally use the same or different network protocols. At this time, the cloud service network supports application access using different network protocols. As an implementation method thereof, the method also includes: the cloud platform uses the resource set for deploying the client to deploy a client agent for the client. The client agent is used to perform address conversion on the messages sent and received by the client so that the client can access applications using different network protocols. In one implementation method, when the service node and the client in the cloud service network are associated using a transit network, the client agent is used to convert the destination address and source address of the message transmitted between the client and the transit network when the client and the transit network of the cloud service network use different network protocols to an address that conforms to the network protocol used by the service node and the receiving end in the transit network. Optionally, the implementation form of the client agent is a NAT gateway. In this way, when some service nodes in the cloud service network use the Ipv4 protocol and some service nodes use the Ipv6 protocol, the client agent can realize the mutual conversion between the Ipv4 address and the Ipv6 address, so that the cloud service network supports application access using different network protocols. For example, when the second resource set used to deploy the client uses the IPv4 protocol and the transit network uses the IPv6 protocol, the data packets passing through the NAT gateway of the client will be converted from source IP address and destination IP address both being IPv4 addresses to source IP address and destination IP address both being IPv6 addresses.

[0181] In addition, when the cloud service network also includes a client, as an implementation method that supports mutual access between applications with different listening protocols, the method also includes: the cloud platform uses a resource set for deploying the client to deploy a second client agent and a third client agent for the client. The second client agent is used to forward the message to the destination of the message according to the first listening protocol when the client sends a message using the first listening protocol, and to forward the message to the third client agent when the client sends a message using the second listening protocol. The third client agent is used to forward the message to the destination of the message according to the second listening protocol. As a possible implementation method, Fig.12As shown, the second client agent is a client agent that supports access to four-layer applications (referred to as a four-layer agent, such as Fig.12 The third client agent is a client agent that supports access to the seven-layer application (referred to as the seven-layer agent, such as Fig.12 L7-LB in the example). The four-layer proxy uses the four-layer information (such as IP address and port, etc.) to forward the message. The seven-layer proxy uses the seven-layer information (such as Uniform Resource Locator (URL) and tags, etc.) to forward the message, and the four-layer proxy cannot obtain the seven-layer information. When the client accesses the four-layer application, the message sent by the client is a four-layer message. At this time, the four-layer proxy can obtain the four-layer information from the message, and then use the listening protocol used by the four-layer application to forward the message to the destination of the message. When the client accesses the seven-layer application, the message sent by the client is a seven-layer message, and the four-layer proxy cannot obtain the seven-layer information from the message. After receiving the message, the seven-layer proxy obtains the seven-layer information from the message, and based on the seven-layer information, forwards the message to the destination of the message according to the listening protocol used by the seven-layer application. In this way, the cloud service network can support mutual access between four-layer and seven-layer applications.

[0182] Fig.13 Schematic diagram of a cloud service network provided by an embodiment of the present application. Fig.13As shown in the figure, application 1 is deployed as a client in VPC-1 of region1 and actively accesses application 2 and application 3. Application 2 is deployed in VPC-2 of region2 and provides services through the IPv6 protocol. The domain name of application 2 is app2.com. Application 3 is deployed in VPC-3 of region1 and provides services through the IPv4 protocol. The VPC3 address conflicts with the VPC1 address of application 1. The domain name of application 3 is app3.com. Application 1, application 2, and application 3 are associated through a transit network, which uses the IPv6 protocol. It can be seen that the cloud service network crosses regions and IPv4 / IPv6 applications visit each other, involving 3 applications. The cloud service network also includes a DNS application, a NAT gateway, an ELB1 gateway, and an ELB2 gateway. The DNS application is used to perform domain name resolution for application 1. The NAT gateway is used to perform source / destination network address translation for application 1, and to perform address translation based on the network used by application 1 and the transit network. The ELB1 gateway is responsible for traffic forwarding of application 2 and performing address translation based on the network used by application 2 and the transit network. The ELB2 gateway is responsible for traffic forwarding of application 3 and performing address translation based on the network used by application 3 and the transit network. The IPv4 address of application 1 is 10.0.1.2. The IPv6 address of application 2 is 2001:db8:1234:1d02::1. The IPv4 address of application 3 is 10.0.1.10. The IPv6 address of the transit network bound to the NAT gateway is 2001:db8:1234:1b03::a. The IPv6 address of the transit network bound to the ELB1 gateway is 2001:db8:1234:1c03::b. The IPv6 address of the transit network bound to the ELB2 gateway is 2001:db8:1234:1b03::b.

[0183] When application 1 accesses application 2, the domain name of application 2, app2.com, is resolved to 192.18.0.2 through the private DNS. The source IP (SIP) of the data packet from application 1 to application 2 is 10.0.1.2, and the destination IP (DIP) is 198.18.0.2. It is forwarded to the NAT gateway through the routing in VPC-1. The NAT gateway performs Full-NAT on the data packet according to the configuration of the cloud platform, and DNATs the destination IP to 2001:db8:1234:1c03::b bound to ELB1. The data packet is routed to the ELB1 gateway in region2 through the transit network, and the ELB1 gateway forwards it to the backend application 2 through load balancing. Fig.13 The dotted arrows indicate the flow direction during the access process, and the addresses in the dotted boxes indicate the source IP and destination IP of the data packets.

[0184] When application 1 accesses application 3, the domain name of application 3, app3.com, is resolved to 192.18.0.3 through the private network DNS. The source IP (SIP) of the data packet from application 1 to application 3 is 10.0.1.2, and the destination IP (DIP) is 192.18.0.3. It is forwarded to the NAT gateway through the routing in VPC-1. The NAT gateway performs Full-NAT on the data packet according to the configuration of the cloud platform, and DNATs the destination IP to 2001:db8:1234:1b03::b bound to ELB1. The data packet is routed to the ELB2 gateway in region1 through the transit network, and the ELB2 gateway forwards it to the backend application 3 through load balancing. Fig.13 The double-dotted arrow in the middle indicates the flow direction during the access process, and the address in the double-dotted box indicates the source IP and destination IP of the data packet.

[0185] Fig.14 is the cloud service network created according to the above steps. Fig.14 As shown in the figure, the cloud service network is associated with 6 service nodes, which correspond to different scenarios, including cross-region, IDC, and Internet. The cloud service network interconnects these heterogeneous service nodes without the customer having to perceive the details. It also supports four-layer applications and seven-layer applications to publish services in the cloud service network.

[0186] Service Node 1 is deployed on the public cloud. It is a regional four-layer application. It consists of two computing forces with different IP protocols in region 1, namely Member Group 1 using the IPv4 protocol and Member Group 2 using the IPv6 protocol. Service Node 1 is both a service provider and a service consumer of other service nodes on the cloud service network. Service Node 2 and Service Node 3 are deployed in the customer's IDC and only serve as service providers. Service Node 4 is deployed on the public cloud. It is a global seven-layer application. Service Node 4 consists of cross-region computing forces, namely Member Group 3 in region 1 and Member Group 4 in region 2. Service Node 5 and Service Node 6 are deployed on the Internet. They are both service providers and service consumers of other service nodes on the cloud service network.

[0187] The following uses several scenarios of cloud service networks as examples to illustrate the types of cloud service networks and the process of creating a cloud service network on a cloud platform.

[0188] The first scenario involves cross-region application inter-access, that is, multiple service nodes in the cloud service network are distributed and deployed in different regions. Here, the cloud service network is a cross-region global network, and users can use this global network to achieve application inter-access. Fig.15 A schematic diagram of a cloud service network provided in an embodiment of the present application. Fig.15 As shown, the cloud service network involves three service nodes, and the three service nodes implement different applications. The creation process of the cloud service network includes the following S11 to S13:

[0189] S11. Create a Member Group for the application based on the user's instructions and configure a service object. The implementation process includes:

[0190] Create Member Group 1 and service 1 in region 1, specify the Member Group type as IPv4, configure the listener http port 8090, and configure rules to route 100% of the traffic to Member Group 1.

[0191] Create Member Group 2 and service 2 in region 2, specify the Member Group type as IPv6, configure the listener http port 8090, and configure rules to route 100% of the traffic to Member Group 2.

[0192] Create Member Group 3 and service 3 in region 2, specify the Member Group type as IPv4, configure the listener http port 8090, and configure rules to route 100% of the traffic to Member Group 3.

[0193] S12: deploying the application backend based on the user's instructions, the implementation process includes:

[0194] Specify Member Group 1 to purchase a group of virtual machines in region 1, deploy the service 1 program in the virtual machines, and configure the program to listen to port 8090 of http.

[0195] Specify Member Group2 to purchase a group of virtual machines in region2, deploy the service2 program in the virtual machines, and configure the program to listen to http port 8090.

[0196] Specify Member Group 3 to purchase a group of virtual machines in region 3, deploy the service 3 program in the virtual machines, and configure the program to listen to http port 8090.

[0197] Note: The three services specify Member Group deployment and release. The VPC and subnet used to deploy the services are automatically created, and customers do not need to be aware of them. The service2 program publishes services through IPv6.

[0198] S13. Create a cloud service network object based on the user's instructions and associate it with the relevant service publishing service. The implementation process includes:

[0199] Create a cloud service network object and associate it with service1, service2, and service3. When associating service1 and service2, you need to check "Actively access other applications" so that service1 and service2 can actively access service3.

[0200] After the above configuration is completed, service1 can actively access service3, and this cloud service network will automatically solve the IPv4 address conflict problem; service2 can actively access service3, and this cloud service network will automatically solve the problem of mutual access due to IPv4 and IPv6 protocol differences.

[0201] The second scenario involves cross-region global applications, that is, at least one service node in the cloud service network is distributed and deployed in different regions. Here, the cloud service network is a cross-region global network, and the service node is a cross-region global application. Users can use the global network to achieve application inter-access. Fig.16 A schematic diagram of a cloud service network provided in an embodiment of the present application. Fig.16 As shown, the cloud service network involves 3 service nodes, and the 3 service nodes implement different applications. The cloud service network can be modified based on the cloud service network in the first scenario, providing services for service3 by adding a backend Member Group and using the virtual machines pre-deployed in region1, and transforming service3 into a global application. The process of completing the above requirements includes the following S21 to S22:

[0202] S21. Based on the user's instructions, a virtual machine is purchased in region1 and the service3 program is deployed. The implementation process includes:

[0203] Purchase a group of virtual machines in VPC4 of region1 and deploy the service3 program. The subnet of VPC4 is (10.0.2.0 / 24). Configure the service3 program to listen to port 8090 of http.

[0204] S22. Based on the user's instructions, create a Member Group for service3 and configure the service object, transforming service3 into a global service. The implementation process includes: creating Member Group 4 in region1, specifying the MemberGroup type as IPv4, selecting the backend type as virtual machine, selecting the related virtual machine of service3 in the existing VPC4, configuring Member Group 4 to bind with service3, and configuring rules to route 50% of the traffic to Member Group 3 and 50% of the traffic to Member Group 4.

[0205] After the above configuration is completed, Member Group 3 and Member Group 4 bound to service3 are in different regions, and service3 publishes services in multiple regions. When service1 actively accesses service3, it accesses the backend service corresponding to Member Group 4 nearby, and when service2 actively accesses service3, it accesses the backend service corresponding to Member Group 3 nearby.

[0206] The third scenario involves a global network across regions, public networks, and customer offline data centers, that is, multiple service nodes in the cloud service network are distributed and deployed in different resource deployment areas. Here, the cloud service network is a global network across regions, public networks, and customer offline data centers, and users can use this global network to achieve application interoperability. Fig.17 A schematic diagram of a cloud service network provided in an embodiment of the present application. Fig.17 As shown, the cloud service network involves 3 service nodes, and the 3 service nodes implement different applications. The 3 applications are: service1 deployed in region1, where the subnet 1 where the virtual machine is located is an Ipv4only subnet, and the network segment is 10.0.1.0 / 24; service2 deployed on the Internet, whose public IP is 18.6.7.4; service3 deployed in the customer's offline IDC, the network segment is 10.0.1.0 / 24, which conflicts with the network segment address of service1. Among them, service1 needs to access service2 and service3. The creation process of the cloud service network includes the following S31 to S33:

[0207] S31. Deploy the application backend based on the user's instructions, and the implementation process includes:

[0208] Purchase a group of virtual machines in VPC1 of region1 and deploy the service1 program. The subnet of VPC1 is (10.0.1.0 / 24). Configure the program to listen to port 8090 of http.

[0209] Deploy the service3 program in the virtual machine of the offline IDC. The network segment of the virtual machine's network card is 10.0.1.0 / 24. Configure the program to listen to port 8090 of http.

[0210] S32: Create a Member Group for the application based on the user's instructions and configure a service object. The implementation process includes:

[0211] Create Member Group 1 in region1, select VM as the backend type, and specify the VMs related to VPC1 in region1.

[0212] Create service1, configure the listener for http port 8090, and configure rules to route 100% of the traffic to Member Group1.

[0213] Create Member Group2, select the backend type as public network service, and bind the public IP of service2.

[0214] Create service2, configure the listener for http port 8090, and configure rules to route 100% of the traffic to Member Group2.

[0215] Create Member Group 3, select the backend type as offline IDC, select dedicated DC or VPN, and bind the IP address of the offline IDCservice3 virtual machine.

[0216] Create service3, configure the listener http port 8090, and configure rules to route 100% of the traffic to Member Group3.

[0217] S33: Create a global network based on the user's instructions and associate related services. The implementation process includes:

[0218] Create a cloud service network object and associate it with service1, service2, and service3. When associating service1, you need to check "Actively access other applications" so that service1 can actively access service2 and service3. However, service2 and service3 are not consumers, so service2 and service3 do not actively access service1.

[0219] The fourth scenario involves a global network of cross-account and departmental collaboration. For example, Fig.18 A schematic diagram of a cloud service network provided in an embodiment of the present application. Fig.18 As shown, Enterprise A consists of three departments: Business Department 1, Business Department 2, and AI Department. In addition to the administrator account, independent member accounts are created for each department. Fig.19 It is the relationship between the accounts involved in the cloud service network. This scenario mainly consists of the following three application scenarios: Application scenario ①: service1 operates the RDS database; Application scenario ②: service1 and service2 visit each other across departments and VPCs; Application scenario ③: AI department purchases public cloud MA to access the RDS database of business department 1. The creation process of the cloud service network includes the following S41 to S46:

[0220] S41. Perform the following operations based on the instructions of the administrator account:

[0221] Create a cloud service network;

[0222] Configure access control policies for the cloud service network to allow only accounts in the organization to access resources;

[0223] Share the cloud service network with member accounts of the three departments of the company, as well as the public cloud RDS service OP account and the public cloud MA service OP account, and review and approve the service application after association;

[0224] Configure access control to allow the organization to access resources for the enterprise and public clouds;

[0225] Configure access control to allow only users vpc-1 and op_ma vpc to access serviceRDS1.

[0226] S42. Based on the instructions of the member account of business department 1, the following operation process is performed:

[0227] Deploy the service code on the computing resources of user vpc-1;

[0228] Create Member Group 1 for the above computing resources;

[0229] Create service1, configure service routing policy, and associate it with Member Group1;

[0230] Associate service1 with the cloud service network and check the "Access as client" option;

[0231] Purchase the RDS database service instance rds1 in the public cloud.

[0232] S43. Based on the instructions of the member account of business department 2, the following operation process is performed:

[0233] Deploy the service code on the computing resources of user vpc-2;

[0234] Create Member Group 2 for the above computing resources;

[0235] Create service2, configure service routing policy, and associate it with Member Group2;

[0236] Associate service1 with the cloud service network and check the "Access as client" option.

[0237] S44. Execute the operation process based on the instructions of the public cloud op_rds account:

[0238] Use the database instance rds1 purchased by the customer as the Member Group and create the service serviceRDS1;

[0239] Associate serviceRDS1 with the cloud service network.

[0240] S45. Perform the following operations based on the instructions of the AI ​​department member account:

[0241] Purchase the public cloud ModelArts instance ma1 and deploy AI training tasks.

[0242] S46. Perform the following operations based on the instructions of the public cloud op_ma account:

[0243] Associate the VPC where the user instance is located with the cloud service network;

[0244] Configure the security group to allow access only to the computing resources of instance ma1.

[0245] To summarize, in the cloud service providing method provided in the embodiments of the present application, since multiple service nodes of the cloud service network are obtained based on resource deployment in one or more resource deployment areas, the cloud service network is not limited to being obtained based on resource deployment in a certain resource deployment area. The cloud service network can be regarded as a global network, which can utilize resources deployed in multiple resource deployment areas to provide services to users, thereby expanding the scope of cloud services provided by the cloud service network and improving the performance of cloud services provided by the cloud service network.

[0246] Moreover, it can be seen from the cloud service provision method that the method provides an application-oriented network model. The network model includes a resource layer, a service node layer, and a cloud service network layer. Due to the existence of the network model, when a user needs the cloud platform to provide cloud services to the user, the cloud platform needs to provide the user with a resource configuration interface, a service configuration interface, a network configuration interface, and a network association interface to obtain information related to the user input, and perform related operations according to the information input by the user, so as to obtain a cloud service network for providing the cloud service required by the user, and use the cloud service network to provide cloud services to the user. In this way, in the process of providing the cloud service, the user does not need to perform complex network configuration, which reduces the difficulty for the user to use the cloud services provided by the cloud platform, and helps to improve the availability of the cloud services provided by the cloud platform.

[0247] In addition, the present application provides an application-oriented network model or object, supports full-scenario access across resource deployment areas, such as supporting full-scenario access such as region, IDC, Internet, etc., supports application mutual access of different network protocols, such as supporting Ipv4 / Ipv6 application mutual access, and supports application mutual access of different monitoring protocols, such as supporting four-layer and seven-layer application mutual access, and customers do not need to modify the application. In addition, the present application also supports the deployment and release of global applications, which helps to provide application multi-site active, cross-regional flow, cross-regional disaster recovery and other capabilities, and makes application consumers unaware of the global evolution of applications. At the same time, the present application provides a three-layer network model. When users deploy a cloud service network, after entering relevant information in the corresponding interface of the three-layer network model, the cloud platform can automatically create a cloud service network based on this information, which can greatly simplify the global network configuration and management, and provide one-click automatic interconnection capabilities between applications. In addition, customers do not need to open up network interconnection and address planning between applications, and can automatically solve problems such as Ipv4 address conflicts and insufficient address space in multiple VPCs.

[0248] In addition, currently public cloud vendors generally divide public clouds into different regions based on geographical locations, and each region independently deploys various cloud resources and cloud services. In recent years, with the advancement of globalization and digitalization, enterprises and organizations need to provide efficient and reliable services and applications across the entire region, and cross-region access and global applications will gradually become common. Since the cloud service provision method provided in the embodiment of the present application can provide global application deployment and access capabilities, it helps to meet customer application expansion, low-latency access, high reliability and low cost requirements.

[0249] It should be noted that the order of steps in the cloud service providing method provided in the embodiment of the present application can be adjusted appropriately, and the steps can be increased or decreased accordingly according to the situation. Any technician familiar with the technical field can easily think of a change within the technical scope disclosed in this application, which should be included in the protection scope of this application, so it will not be repeated.

[0250] The following is an example of a virtual device in an embodiment of the present application.

[0251] The above introduces the cloud service providing method of the embodiment of the present application. Corresponding to the above method, the embodiment of the present application also provides a cloud service providing device. Fig. 20 This is a schematic diagram of the structure of a cloud service providing device provided in an embodiment of the present application. Fig. 20 The following multiple components are shown: Fig. 20 The cloud service providing device shown can perform all or part of the operations in the above-mentioned cloud service providing method. It should be understood that the device may include more additional components than the components shown or omit some of the components shown, and the embodiments of the present application are not limited to this. Optionally, the cloud service providing device can be configured on a cloud platform. Fig. 20 As shown, the cloud service providing device 200 may include:

[0252] The interactive module 2001 is used to provide a network configuration interface to the user, and the network configuration interface prompts the user to enter network feature information, and the network feature information indicates the cloud service network required to implement the target cloud service. Here, the detailed working process of the interactive module 2001 is described in the previous method embodiment. For example, refer to the relevant description of the aforementioned step 308.

[0253] The interaction module 2001 is also used to provide a network association interface to the user, the network association interface prompts the user to enter association information, the association information indicates multiple service nodes associated with the cloud service network, the service nodes are used to deploy the user's application, the application is used to implement the target cloud service, and the multiple service nodes are obtained based on the resource deployment in one or more resource deployment areas. Here, the detailed working process of the interaction module 2001 is described in the previous method embodiment. For example, refer to the relevant description of the aforementioned step 310.

[0254] The processing module 2002 is used to establish an association relationship between multiple service nodes based on the network feature information and the association information to obtain a cloud service network. Here, the detailed working process of the processing module 2002 is described in the previous method embodiment. For example, refer to the relevant description of the aforementioned step 311.

[0255] Optionally, the multiple service nodes meet one or more of the following requirements: they are deployed based on cloud resources in different cloud resource deployment areas in the cloud platform; and they are deployed based on at least two of public network resources, cloud resources in the cloud resource deployment area, and the user's own resources.

[0256] Optionally, the service node is obtained based on resource deployment in one or more resource deployment areas.

[0257] Optionally, the service node satisfies one or more of the following: is deployed based on cloud resources in different cloud resource deployment areas in the cloud platform; and is deployed based on at least two of public network resources, cloud resources in the cloud resource deployment area, and the user's own resources.

[0258] Optionally, multiple service nodes use different monitoring protocols.

[0259] Optionally, the multiple first resource sets used to deploy the service node use different network protocols.

[0260] Optionally, the multiple first resource sets used to deploy the multiple service nodes use different network protocols.

[0261] Optionally, the processing module 2002 is also used to deploy a service agent for the service node, and the service agent is used to convert the destination address and source address of the message transmitted between the service node and the transit network into an address that conforms to the network protocol used by the service node and the receiving end in the transit network when the service node and the transit network of the cloud service network use different network protocols. The transit network is used to associate different service nodes. Here, please refer to the description in the previous method embodiment for the detailed working process of the processing module 2002. For example, refer to the relevant description in the aforementioned step 307.

[0262] Optionally, the interaction module 2001 is also used to provide a service configuration interface to the user, the service configuration interface prompts the user to enter service feature information, the service feature information indicates all first resource sets required to deploy the service node, and all resources in any first resource set are deployed in the same resource deployment area; the cloud platform uses all first resource sets to deploy the service node. Here, please refer to the description in the previous method embodiment for the detailed working process of the interaction module 2001. For example, refer to the relevant description in the aforementioned step 305.

[0263] Optionally, the service feature information or network feature information further indicates that the service node is reused as a client, and the service feature information indicates all first resource sets required to deploy the service node; the processing module 2002 is also used to use all first resource sets to deploy the client and associate the client with the cloud service network. Here, please refer to the description in the previous method embodiment for the detailed working process of the processing module 2002. For example, refer to the relevant description in the aforementioned step 313.

[0264] Optionally, the service feature information or network feature information further indicates that any first resource set among all first resource sets is also used to deploy the client, and the service feature information indicates all first resource sets required to deploy the service node; the processing module 2002 is further used to deploy the client based on any first resource set and associate the client with the cloud service network. Here, please refer to the description in the previous method embodiment for the detailed working process of the processing module 2002. For example, refer to the relevant description in the aforementioned step 314.

[0265] Optionally, the interaction module 2001 is further used to provide a client configuration interface to the user, the client configuration interface prompts the user to enter client feature information, the client feature information indicates the client and the second resource set required for deploying the client. Here, the detailed working process of the interaction module 2001 is described in the previous method embodiment. For example, refer to the relevant description in the aforementioned step 315.

[0266] Correspondingly, the processing module 2002 is also used to deploy the client using the second resource set and associate the client with the cloud service network. Here, please refer to the description in the previous method embodiment for the detailed working process of the processing module 2002. For example, refer to the relevant description in the aforementioned step 317.

[0267] Optionally, the resource set of the deployment client and the resource set of the deployment service node use different network protocols.

[0268] Optionally, the processing module 2002 is further used to deploy a client agent for the client using the resource set for deploying the client, and the client agent is used to convert the destination address and source address of the message transmitted between the client and the transit network into an address that complies with the network protocol used by the service node and the receiving end in the transit network when the client and the transit network of the cloud service network use different network protocols, and the transit network is used to associate different service nodes. Here, please refer to the description in the previous method embodiment for the detailed working process of the processing module 2002.

[0269] Optionally, the processing module 2002 is further used to deploy a second client agent and a third client agent for the client using the resource set for deploying the client; the second client agent is used to forward the message to the destination of the message according to the first listening protocol when the client sends a message using the first listening protocol, and forward the message to the third client agent when the client sends a message using the second listening protocol; the third client agent is used to forward the message to the destination of the message according to the second listening protocol. Here, please refer to the description in the previous method embodiment for the detailed working process of the processing module 2002.

[0270] Optionally, the client is associated with multiple cloud service networks, and the multiple cloud service networks are used to implement different cloud services.

[0271] Optionally, the multiple service nodes are deployed by multiple users respectively.

[0272] Optionally, the cloud service network and the multiple service nodes are deployed by multiple users respectively.

[0273] Optionally, the service node is associated with multiple cloud service networks, and the multiple cloud service networks are used to implement different cloud services.

[0274] Optionally, the processing module 2002 is specifically used to: the cloud platform creates a transit network based on the network feature information and the associated information, associates multiple service nodes with the transit network, and obtains a cloud service network. Here, the detailed working process of the processing module 2002 is described in the previous method embodiment. For example, refer to the relevant description in the aforementioned step 312.

[0275] Optionally, the transit network is also used to convert addresses of multiple service nodes.

[0276] Optionally, the interaction module 2001 is further used to provide a resource configuration interface to the user, the resource configuration interface prompts the user to input resource feature information, and the resource feature information indicates the resources required by the user. Here, the detailed working process of the interaction module 2001 is described in the previous method embodiment. For example, refer to the relevant description in the aforementioned step 302.

[0277] The processing module 2002 is further used to obtain a first resource set including resources indicated by resource feature information, and the first resource set is used to create a service node. Here, the detailed working process of the processing module 2002 is described in the previous method embodiment. For example, refer to the relevant description in the above step 304.

[0278] Optionally, the resource feature information further indicates that the resource and the source of the virtual local area network are provided in the form of a virtual local area network, and the virtual local area network includes multiple computing instances with a specified network relationship. The processing module 2002 is specifically used to: when the resource feature information indicates that a virtual local area network is created based on resources, the cloud platform uses the resources to create a virtual local area network to obtain a first resource set; when the resource feature information indicates that an existing virtual local area network is used, the cloud platform obtains the existing virtual local area network to obtain the first resource set. Here, please refer to the description in the previous method embodiment for the detailed working process of the processing module 2002. For example, refer to the relevant description in the aforementioned step 304.

[0279] Optionally, the first resource set includes one or more computing instances, and the computing instances include: virtual machines, containers, functions, and bare metal servers.

[0280] To summarize, in the cloud service providing device provided in the embodiments of the present application, since multiple service nodes of the cloud service network are obtained based on resource deployment in one or more resource deployment areas, the cloud service network is not limited to being obtained based on resource deployment in a certain resource deployment area. The cloud service network can be regarded as a global network, which can utilize resources deployed in multiple resource deployment areas to provide services to users, thereby expanding the scope of cloud services provided by the cloud service network and improving the performance of cloud services provided by the cloud service network.

[0281] Moreover, it can be seen from the cloud service providing device that the device provides an application-oriented network model. The network model includes a resource layer, a service node layer, and a cloud service network layer. Due to the existence of this network model, when a user needs the cloud platform to provide cloud services to the user, the cloud platform needs to provide the user with a resource configuration interface, a service configuration interface, a network configuration interface, and a network association interface to obtain information related to the user input, and perform related operations according to the information input by the user, so as to obtain a cloud service network for providing the cloud service required by the user, and use the cloud service network to provide cloud services to the user. In this way, in the process of providing the cloud service, the user does not need to perform complex network configuration, which reduces the difficulty for the user to use the cloud services provided by the cloud platform, and helps to improve the availability of the cloud services provided by the cloud platform.

[0282] In addition, the present application provides an application-oriented network model or object, supports full-scenario access across resource deployment areas, such as supporting full-scenario access such as region, IDC, Internet, etc., supports application mutual access of different network protocols, such as supporting Ipv4 / Ipv6 application mutual access, and supports application mutual access of different monitoring protocols, such as supporting four-layer and seven-layer application mutual access, and customers do not need to modify the application. In addition, the present application also supports the deployment and release of global applications, which helps to provide application multi-site active, cross-regional flow, cross-regional disaster recovery and other capabilities, and makes application consumers unaware of the global evolution of applications. At the same time, the present application provides a three-layer network model. When users deploy a cloud service network, after entering relevant information in the corresponding interface of the three-layer network model, the cloud platform can automatically create a cloud service network based on this information, which can greatly simplify the global network configuration and management, and provide one-click automatic interconnection capabilities between applications. In addition, customers do not need to open up network interconnection and address planning between applications, and can automatically solve problems such as Ipv4 address conflicts and insufficient address space in multiple VPCs.

[0283] In addition, currently public cloud vendors generally divide public clouds into different regions based on geographical locations, and each region independently deploys various cloud resources and cloud services. In recent years, with the advancement of globalization and digitalization, enterprises and organizations need to provide efficient and reliable services and applications across the entire region, and cross-region access and global applications will gradually become common. Since the cloud service provision device provided in the embodiment of the present application can provide global application deployment and access capabilities, it helps to meet customer demands for application expansion, low-latency access, high reliability and low cost.

[0284] The interaction module 2001 and the processing module 2002 can be implemented by software or hardware. For example, the interaction module 2001 is taken as an example to introduce the implementation of the interaction module 2001. Similarly, the implementation of the processing module 2002 can refer to the implementation of the interaction module 2001.

[0285] As an example of a software functional unit, the interaction module 2001 may include code running on a computing instance. Among them, the computing instance may include at least one of a physical host (computing device), a virtual machine, and a container. Further, the above-mentioned computing instance may be one or more. For example, the interaction module 2001 may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the code may be distributed in the same region (region) or in different regions. Furthermore, the multiple hosts / virtual machines / containers used to run the code may be distributed in the same availability zone (AZ) or in different AZs, each AZ including a data center or multiple data centers with similar geographical locations. Among them, usually a region may include multiple AZs.

[0286] Similarly, multiple hosts / virtual machines / containers used to run the code can be distributed in the same virtual private cloud (VPC) or in multiple VPCs. Usually, a VPC is set up in a region. For cross-region communication between two VPCs in the same region and between VPCs in different regions, a communication gateway needs to be set up in each VPC to achieve interconnection between VPCs through the communication gateway.

[0287] As an example of a hardware functional unit, the interaction module 2001 may include at least one computing device, such as a server, etc. Alternatively, the interaction module 2001 may also be a device implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), etc. The PLD may be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0288] The multiple computing devices included in the interaction module 2001 can be distributed in the same region or in different regions. The multiple computing devices included in the interaction module 2001 can be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the interaction module 2001 can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

[0289] It should be noted that, in other embodiments, any one of the interaction module 2001 and the processing module 2002 can be used to execute any step in the cloud service provision method. The steps that the interaction module 2001 and the processing module 2002 are responsible for implementing can be specified as needed, and the interaction module 2001 and the processing module 2002 respectively implement different steps in the cloud service provision method to realize all functions of the cloud service provision device.

[0290] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of each component described above can refer to the corresponding content in the aforementioned method embodiment, and will not be repeated here.

[0291] The following is an illustration of the basic hardware structure involved in the embodiments of the present application.

[0292] The embodiment of the present application provides a computing device. The computing device is used to implement part or all of the functions of the cloud service providing method provided in the embodiment of the present application. Fig.21 Schematic diagram of a computing device provided in an embodiment of the present application. Fig.21As shown, the computing device 2100 includes a processor 2101, a memory 2102, a communication interface 2103 and a bus 2104. The processor 2101, the memory 2102 and the communication interface 2103 are connected to each other through the bus 2104.

[0293] Processor 2101 may include a general-purpose processor and / or a dedicated hardware chip. A general-purpose processor may include: a central processing unit (CPU), a microprocessor or a graphics processing unit (GPU). The CPU is, for example, a single-core processor (single-CPU) or a multi-core processor (multi-CPU). A dedicated hardware chip is a hardware module for high-performance processing. A dedicated hardware chip includes at least one of a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or a network processor (NP). Processor 2101 may also be an integrated circuit chip having signal processing capabilities. In the implementation process, some or all of the functions of the cloud service provision method of the present application may be completed by hardware integrated logic circuits in processor 2101 or instructions in software form.

[0294] The memory 2102 is used to store computer programs, which include an operating system 2102a and executable codes (i.e., program instructions) 2102b. The memory 2102 is, for example, a read-only memory or other types of static storage devices that can store static information and instructions, or a random access memory or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory, a read-only optical disc or other optical disc storage, an optical disc storage (including a compressed optical disc, a laser disc, an optical disc, a digital versatile disc, a blue-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired executable code in the form of an instruction or data structure and can be accessed by a computer, but is not limited thereto. For example, the memory 2102 is used to store an outbound port queue, etc. The memory 2102 is, for example, independent and connected to the processor 2101 via a bus 2104. Or the memory 2102 and the processor 2101 are integrated together. The memory 2102 can store executable code. When the executable code stored in the memory 2102 is executed by the processor 2101, the processor 2101 is used to perform some or all functions of the cloud service providing method provided in the embodiment of the present application. For the implementation of the process executed by the processor 2101, please refer to the relevant description in the aforementioned embodiment. The memory 2102 may also include software modules and data required for other running processes such as the operating system.

[0295] The communication interface 2103 uses a transceiver module such as, but not limited to, a transceiver to achieve communication with other devices or communication networks. For example, the communication interface 2103 can be any one or any combination of the following devices: a network interface (such as an Ethernet interface), a wireless network card, and other devices with network access functions.

[0296] The bus 2104 is any type of communication bus for interconnecting the internal devices of the computing device (e.g., the memory 2102, the processor 2101, and the communication interface 2103). For example, a system bus. The embodiment of the present application takes the interconnection of the above-mentioned devices inside the computing device through the bus 2104 as an example. Optionally, the above-mentioned devices inside the computing device 2100 can also be connected to each other in communication with each other using other connection methods other than the bus 2104. For example, the above-mentioned devices inside the computing device 2100 are interconnected through an internal logical interface.

[0297] It should be noted that the above-mentioned multiple devices can be respectively arranged on independent chips, or at least partially or completely arranged on the same chip. Whether to independently arrange each device on different chips or to integrate and arrange it on one or more chips often depends on the needs of product design. The embodiments of the present application do not limit the specific implementation form of the above-mentioned devices. The descriptions of the processes corresponding to the above-mentioned figures have different focuses. For the parts not described in detail in a certain process, please refer to the relevant descriptions of other processes.

[0298] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product providing a program development platform includes one or more computer instructions, and when these computer program instructions are loaded and executed on a computing device, all or part of the functions of the cloud service providing method provided in the embodiments of the present application are implemented.

[0299] Furthermore, computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, optical fiber, digital cloud tenant line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium stores computer program instructions that provide a program development platform.

[0300] The embodiment of the present application also provides a computing device cluster. The computing device cluster includes at least one computing device. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smart phone.

[0301] Optionally, the structure of at least one computing device included in the computing device cluster can be found in Fig.21 The computing device 2100 shown. The memory 2102 in one or more computing devices 2100 in the computing device cluster may store the same instructions for executing the cloud service providing method.

[0302] In some possible implementations, the memory 2102 of one or more computing devices 2100 in the computing device cluster may also store some instructions for executing the cloud service providing method. In other words, the combination of one or more computing devices 2100 may jointly execute the instructions for executing the cloud service providing method.

[0303] It should be noted that the memory 2102 in different computing devices 2100 in the computing device cluster can store different instructions, which are respectively used to execute part of the functions of the cloud service provider. That is, the instructions stored in the memory 2102 in different computing devices 2100 can implement the functions of one or more modules in the interaction module 2001 and the processing module 2002.

[0304] In some possible implementations, one or more computing devices in the computing device cluster may be connected via a network, which may be a wide area network or a local area network. Fig. 22 A possible implementation is shown. Fig. 22 As shown, two computing devices 2200A and 2200B are connected via a network. Specifically, the network is connected via a communication interface in each computing device. In this type of possible implementation, computing devices 2200A and 2200B include a bus 2202, a processor 2204, a memory 2206, and a communication interface 2208. The memory 2206 in the computing device 2200A stores instructions for the functions of the interaction module 2001. At the same time, the memory 2206 in the computing device 2200B stores instructions for executing the functions of the processing module 2002.

[0305] It should be understood that Fig. 22 The functions of the computing device 2200A shown in the figure can also be completed by multiple computing devices 2200. Similarly, the functions of the computing device 2200B can also be completed by multiple computing devices 2200. And the deployment mode of the modules used to implement the cloud service providing method in the computing device can also be adjusted according to the application requirements.

[0306] An embodiment of the present application also provides a computer-readable storage medium, which is a non-volatile computer-readable storage medium. The computer-readable storage medium includes program instructions. When the program instructions are executed on a computing device, the computing device implements the cloud service providing method provided in the embodiment of the present application.

[0307] The embodiment of the present application also provides a computer program product including instructions. When the computer program product is executed on a computer, the computer implements the cloud service providing method provided by the embodiment of the present application.

[0308] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0309] It should be noted that the information (including but not limited to cloud tenant device information, cloud tenant personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.) and signals involved in this application are all authorized by the cloud tenant or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions. For example, the original data and executable code involved in this application are all obtained with full authorization.

[0310] In the embodiments of the present application, the terms "first", "second" and "third" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance. The term "at least one" means one or more, and the term "plurality" means two or more, unless otherwise expressly defined.

[0311] The term "and / or" in this application is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0312] The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the concept and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A cloud service providing method, characterized in that: The method is applied to a cloud platform, and the method comprises: The cloud platform provides a network configuration interface to the user, the network configuration interface prompts the user to input network characteristic information, the network characteristic information indicates the cloud service network required to implement the target cloud service; The cloud platform provides a network association interface to the user, the network association interface prompts the user to input association information, the association information indicates a plurality of service nodes associated with the cloud service network, the service nodes are used to deploy the user's application, the application is used to implement the target cloud service, the plurality of service nodes are obtained based on resource deployment in one or more resource deployment areas; The cloud platform establishes an association relationship between the multiple service nodes based on the network feature information and the association information to obtain the cloud service network.

2. The method according to claim 1, characterized in that The multiple service nodes meet one or more of the following requirements: The cloud resource deployment based on different cloud resource deployment areas in the cloud platform is obtained; And, it is obtained based on at least two deployments of public network resources, cloud resources in the cloud resource deployment area, and the user's own resources.

3. The method according to claim 1 or 2, characterized in that The service node is obtained based on resource deployment in one or more resource deployment areas.

4. The method according to claim 3, characterized in that The service node meets one or more of the following requirements: The cloud resource deployment based on different cloud resource deployment areas in the cloud platform is obtained; And, it is obtained based on at least two deployments of public network resources, cloud resources in the cloud resource deployment area, and the user's own resources.

5. The method according to any one of claims 1 to 4, characterized in that: The multiple service nodes use different monitoring protocols.

6. The method according to any one of claims 1 to 5, characterized in that: The multiple first resource sets used to deploy the service node use different network protocols.

7. The method according to any one of claims 1 to 6, characterized in that: The multiple first resource sets used to deploy the multiple service nodes use different network protocols.

8. The method according to any one of claims 1 to 7, characterized in that: Before the cloud platform establishes association relationships between the multiple service nodes based on the network feature information and the association information to obtain the cloud service network, the method further includes: The cloud platform provides a service configuration interface to the user, the service configuration interface prompts the user to input service feature information, the service feature information indicates all first resource sets required to deploy the service node, and all resources in any first resource set are deployed in the same resource deployment area; The cloud platform deploys the service node using all the first resource sets.

9. The method according to any one of claims 1 to 8, characterized in that: The service characteristic information or the network characteristic information further indicates that the service node is reused as a client, and the service characteristic information indicates all first resource sets required to deploy the service node. The method further includes: The cloud platform deploys the client using all the first resource sets and associates the client with the cloud service network.

10. The method according to claim 9, characterized in that The resource set for deploying the client and the resource set for deploying the service node use different network protocols.

11. The method according to claim 9 or 10, characterized in that The client is associated with a plurality of cloud service networks, and the plurality of cloud service networks are used to implement different cloud services.

12. The method according to any one of claims 1 to 11, characterized in that: The multiple service nodes are deployed by multiple users respectively.

13. The method according to any one of claims 1 to 12, characterized in that: The cloud service network and the multiple service nodes are deployed by multiple users respectively.

14. The method according to any one of claims 1 to 13, characterized in that: The service node is associated with a plurality of cloud service networks, and the plurality of cloud service networks are used to implement different cloud services.

15. The method according to any one of claims 1 to 14, characterized in that: The cloud service network includes a transit network, and the transit network is used to associate different service nodes, and the transit network is used to convert addresses of the multiple service nodes.

16. A cloud service providing device, characterized in that: The device is applied to a cloud platform, and comprises: An interaction module, configured to provide a network configuration interface to a user, wherein the network configuration interface prompts the user to input network characteristic information, wherein the network characteristic information indicates a cloud service network required to implement a target cloud service; The interaction module is further used to provide a network association interface to the user, the network association interface prompts the user to input association information, the association information indicates multiple service nodes associated with the cloud service network, the service nodes are used to deploy the user's application, the application is used to implement the target cloud service, and the multiple service nodes are obtained based on resource deployment in one or more resource deployment areas; A processing module is used to establish an association relationship between the multiple service nodes based on the network feature information and the association information to obtain the cloud service network.

17. The device according to claim 16, characterized in that The interaction module is further used to provide a service configuration interface to the user, the service configuration interface prompts the user to input service feature information, the service feature information indicates all first resource sets required to deploy the service node, and all resources in any first resource set are deployed in the same resource deployment area; The cloud platform deploys the service node using all the first resource sets.

18. The device according to claim 16 or 17, characterized in that The service characteristic information or the network characteristic information further indicates that the service node is reused as a client, and the service characteristic information indicates a set of all first resources required to deploy the service node; The processing module is further configured to utilize all the first resource sets to deploy the client and associate the client with the cloud service network.

19. A computing device cluster, characterized in that: The method comprises a plurality of computing devices, wherein the plurality of computing devices comprises a plurality of processors and a plurality of memories, wherein program instructions are stored in the plurality of memories, and the plurality of processors execute the program instructions, so that the computing device cluster executes any one of the methods described in claims 1 to 15.

20. A computer-readable storage medium, characterized in that: The method comprises program instructions, and when the program instructions are executed on a computing device, the computing device is caused to execute the method according to any one of claims 1 to 15.

21. A computer program product comprising instructions, characterized in that When the computer program product is executed on a computer, the computer is enabled to perform the method according to any one of claims 1 to 15.

Images