CN117997719A

CN117997719A - Flow transfer method and related equipment

Info

Publication number: CN117997719A
Application number: CN202211347886.8A
Authority: CN
Inventors: 梁亦历; 郜忠华
Original assignee: Huawei Cloud Computing Technologies Co Ltd
Current assignee: Huawei Cloud Computing Technologies Co Ltd
Priority date: 2022-10-31
Filing date: 2022-10-31
Publication date: 2024-05-07

Abstract

The embodiment of the application provides a traffic transfer method and related equipment, which are used for solving the problem of service faults of tenants and improving the service reliability of a cloud service network. The method of the embodiment of the application comprises the following steps: the first node acquires a first topological structure, forwards the flow of the first service of the VM to the second node according to the first topological structure, and forwards the flow of the first service of the VM to the third node after the first node acquires a fault signal indicating that the first service of the VM is abnormal in configuration. When the first service configuration abnormal condition of the VM on the second node is obtained, the first node stops forwarding the flow of the first service of the VM to the second node and forwards the flow of the first service of the VM to the third node, so that when the first service of the VM on the second node has service configuration faults, the flow of the first service of the VM is transferred to the third node in time, the availability of the first service of the VM is maintained, and the service reliability of the cloud service network is improved.

Description

Flow transfer method and related equipment

Technical Field

The embodiment of the application relates to the field of cloud service, in particular to a traffic transfer method and related equipment.

Background

With the continuous development of cloud services, for better economic benefit, operators usually rent virtual machines in a form of logical multi-renting, that is, a network element cluster runs services of multiple tenants at the same time. To avoid the reduction of transmission effect caused by huge workload of some nodes and idle condition of some nodes, traffic load is usually balanced to each node of the network element cluster through equivalent routing configuration on the switch.

In order to ensure the reliability of the network, the network element cluster is generally deployed by adopting double availability zones (availability zone, AZ) or multiple AZs, so that when a certain AZ fails, the service running in the failed AZ can be transferred to other AZs capable of normally working, so that the normal running of the service is ensured.

The network element cluster is judged whether to be available by detecting the connectivity of an underlying bearing (underley) network plane, and the fault detection mode of AZ is only suitable for the situation that physical equipment such as a host fault, a cabinet power failure, a machine room power failure or a switch fault is failed, however, in a specific application scene, the situation that a certain service of a certain tenant is failed due to abnormal network element cluster service configuration is also possible, if a certain service of the tenant is failed but is not repaired, the service is invalid, so that the tenant cannot use the service related to the service, and the problem of service fault of the tenant is solved, so that the service reliability of the cloud service network is improved.

Disclosure of Invention

The embodiment of the application provides a traffic transfer method and related equipment, which are used for solving the problem of service faults of tenants and improving the service reliability of a cloud service network.

The first aspect of the embodiment of the application provides a flow transfer method, which comprises the following steps: the method comprises the steps that a first node obtains information of a first topology, the information of the first topology indicates that the first node is respectively connected with a second node and a third node, the second node supports a first service, and the third node supports the first service; the first node forwards traffic of first traffic of a Virtual Machine (VM) to the second node; the first node acquires a fault signal, wherein the fault signal indicates that the first service configuration of the VM is abnormal; the first node forwards traffic of the first traffic of the VM to the third node.

In the embodiment of the application, after the first node acquires the first topological structure, forwarding the flow of the first service of the VM to the second node according to the first topological structure, and after the first node acquires the fault signal indicating that the first service configuration of the VM is abnormal, stopping forwarding the flow of the first service of the VM to the second node and forwarding the flow of the first service of the VM to the third node. The first topological structure means that a first node is respectively connected with a second node and a third node, the second node supports a first service, and the third node supports the first service. According to the embodiment of the application, by acquiring the abnormal condition of the first service configuration of the VM on the second node, if the abnormal condition of the first service configuration of the VM on the second node is detected, the first node stops forwarding the flow of the first service of the VM to the second node and forwards the flow of the first service of the VM to the third node, so that when the service configuration fault occurs to the first service of the VM on the second node, the flow of the first service of the VM is timely transferred to the third node, the availability of the first service of the VM is maintained, and the service reliability of the cloud service network is improved.

In a possible implementation manner of the first aspect, the fault signal includes a first detection exception signal, where the first detection exception signal indicates a first service configuration exception of the virtual machine on the second node; before the first node obtains the fault signal, the method further includes: the first node sends a first service detection signal to a first service of the virtual machine on the second node, wherein the first service detection signal is used for detecting a first service configuration condition of the virtual machine.

In the embodiment of the application, a first node sends a first service detection signal to a first service of a virtual machine on a second node, acquires a first detection abnormal signal, and acquires a first service configuration abnormality of the virtual machine on the second node through the first detection abnormal signal. The first service detection signal is used for detecting a first service configuration condition of the virtual machine on the second node. By monitoring the first service configuration condition of the virtual machine on the second node, the moment of abnormal first service configuration of the virtual machine on the second node is timely obtained, and therefore the flow of the first service of the virtual machine on the second node is efficiently transferred, and the influence of flow transfer on other services or services in the virtual machine is reduced.

In a possible implementation manner of the first aspect, the obtaining, by the first node, a first detection anomaly signal includes: and in a first time period after a first time, the first node does not receive a first feedback signal sent by a first service of the virtual machine on the second node, the first node acquires the first detection abnormal signal, the first time is the time when the first node sends the first service detection signal, and the first feedback signal indicates that the first service configuration of the virtual machine on the second node is normal. In the embodiment of the application, in a first time period after a first time, the first node does not receive a first feedback signal sent by a first service of a virtual machine on a second node, the first node acquires a first detection abnormal signal, the first time is the time when the first node sends the first service detection signal, and the first feedback signal indicates that the first service configuration of the virtual machine on the second node is normal, so that a specific implementation mode is provided for the scheme provided by the application, and the feasibility of the scheme is improved.

In a possible implementation manner of the first aspect, the fault signal includes a second detected anomaly signal, the second detected anomaly signal indicating a first service configuration anomaly running in the first topology based on the first service; before the first node obtains the fault signal, the method further includes: the first node sends a second service detection signal to the second node, wherein the second service detection signal is used for detecting the configuration condition of the first service. In the embodiment of the application, the first node sends the second service detection signal to the second node, acquires the second detection abnormal signal, and acquires the configuration abnormality of the first service of the virtual machine on the second node and/or the configuration abnormality of the first service based on the first service operation of the virtual machine on the second node through the second detection abnormal signal. The second service detection signal is used for detecting a first service configuration condition of the virtual machine on the second node and a configuration condition of a first service running based on the first service of the virtual machine on the second node. By monitoring the configuration condition of the first service, the abnormal configuration of the first service of the virtual machine on the second node and/or the abnormal configuration moment of the first service based on the operation of the first service of the virtual machine on the second node are timely obtained, so that the flow of the first service of the virtual machine on the second node is efficiently transferred, and the influence of the flow transfer on other services or services in the virtual machine is reduced.

In a possible implementation manner of the first aspect, the obtaining, by the first node, the second detection anomaly signal includes: after a second duration of a first time, the first node does not receive a first feedback signal and/or a second feedback signal sent by the second node, the first node obtains the second detection abnormal signal, the first time is the time when the first node sends the second service detection signal, the first feedback signal indicates that the first service configuration of the virtual machine on the second node is normal, and the second feedback signal indicates that the first service configuration based on the first service operation of the virtual machine is normal. In the embodiment of the application, in a first time period after a first time, the first node does not receive the first feedback signal and/or the second feedback signal sent by the second node, the first node acquires a second detection abnormal signal, the second time is the time when the first node sends the second service detection signal, the first feedback signal indicates that the first service configuration of the virtual machine on the second node is normal, and the second feedback signal indicates that the first service configuration based on the first service operation of the virtual machine is normal.

In a possible implementation manner of the first aspect, the first node, the second node and the third node are located in a first availability zone AZ. In the embodiment of the application, the first node, the second node and the third node are positioned at the first AZ, so that the switching of the first service of the virtual machine in the AZ is realized.

In a possible implementation manner of the first aspect, the first node and the second node are located in a first availability zone AZ, and the third node is located in a second AZ. In the embodiment of the application, the first node and the second node are provided to be positioned at the first AZ, and the third node is provided to be positioned at the second AZ, so that the switching of the first service of the virtual machine among AZ is realized.

In a possible implementation manner of the first aspect, before the first node obtains the fault signal, the method further includes: the first node obtains a first signal indicating that when the fault signal is obtained, the first node forwards a first service of the virtual machine to the third node. In the embodiment of the application, the first node acquires the flow switching rule set by the tenant by acquiring the first signal, so that the flexibility of the scheme is improved. The first signal indicates that when the fault signal is acquired, the first node forwards first service of the virtual machine to the third node.

In a possible implementation manner of the first aspect, the second node supports a second service, and the third node supports the second service; before the first node obtains the fault signal, the method further includes: the first node forwards the traffic of the second service of the virtual machine to the second node; after the first node obtains the fault signal, the method further includes: and the first node forwards the traffic of the second service of the virtual machine to the third node. In the embodiment of the application, the second node supports the second service, the third node supports the second service, and after the first node acquires the first signal, the first node can also switch the flow of the second service of the virtual machine originally forwarded to the second node, and the first node forwards the flow of the second service of the virtual machine to the third node. And taking the tenant as the minimum granularity, switching the traffic of the first service and the second service of the VM to a third node. Providing more possibilities for implementation of the scheme.

A second aspect of an embodiment of the present application provides a first node, including:

The system comprises an acquisition unit, a first service generation unit and a second service generation unit, wherein the acquisition unit is used for acquiring information of a first topology, the information of the first topology indicates that a first node is respectively connected with a second node and a third node, the second node supports a first service, and the third node supports the first service;

a sending unit, configured to forward, to the second node, traffic of a first service of a virtual machine;

the obtaining unit is further configured to obtain a fault signal, where the fault signal indicates that the first service configuration of the virtual machine is abnormal;

The sending unit is further configured to forward, to the third node, traffic of the first service of the virtual machine.

In a possible implementation manner of the second aspect, the fault signal includes a first detection exception signal, and the first detection exception signal indicates a first service configuration exception of the virtual machine on the second node;

the sending unit is further configured to send a first service detection signal to a first service of the virtual machine on the second node, where the first service detection signal is used to detect a first service configuration situation of the virtual machine.

In a possible implementation manner of the second aspect, the obtaining unit is specifically configured to, after a first duration of a first time, not receive a first feedback signal sent by a first service of the virtual machine on the second node, where the first node obtains the first abnormal detection signal, and the first time is a time when the first node sends the first service detection signal, and the first feedback signal indicates that a first service configuration of the virtual machine on the second node is normal.

In a possible implementation manner of the second aspect, the fault signal includes a second detected anomaly signal, and the second detected anomaly signal indicates that a first service configuration based on the first service running in the first topology is anomalous;

the sending unit is further configured to send a second service detection signal to the second node, where the second service detection signal is used to detect a configuration situation of the first service.

In a possible implementation manner of the second aspect, the obtaining unit is specifically configured to, after a second duration of a first time, not receive a first feedback signal and/or a second feedback signal sent by the second node, where the first node obtains the second detection abnormal signal, the first time is a time when the first node sends the first service detection signal, the first feedback signal indicates that a first service configuration of a virtual machine on the second node is normal, and the second feedback signal indicates that a first service configuration running based on a first service of the virtual machine is normal.

In a possible implementation manner of the second aspect, the first node, the second node and the third node are located in a first availability zone AZ.

In a possible implementation manner of the second aspect, the first node and the second node are located in a first availability zone AZ, and the third node is located in a second AZ.

In a possible implementation manner of the second aspect, the obtaining unit is further configured to obtain a first signal, where the first signal indicates that, when the failure signal is obtained, the first node forwards the first service of the virtual machine to the third node.

In a possible implementation manner of the second aspect, the second node supports a second service, and the third node supports the second service;

the sending unit is further configured to forward, to the second node, traffic of a second service of the virtual machine;

The sending unit is further configured to forward, to the third node, a traffic of the second service of the virtual machine.

A third aspect of the embodiment of the present application provides a first node, including a processor and a memory, where the processor is coupled to the memory, and the memory is configured to store a program;

the processor is configured to execute a program in the memory, so that the method as described in the foregoing first aspect or one of the possible implementation manners of the first aspect is performed.

A fourth aspect of the embodiments of the present application provides a computer readable storage medium comprising a program which, when run on a computer, causes the computer to perform the method as described in the first aspect or one of the possible implementations of the first aspect.

A fifth aspect of the embodiments of the application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method as described in the first aspect or one of the possible implementations of the first aspect.

Drawings

Fig. 1 is a schematic diagram of a network topology according to an embodiment of the present application;

FIG. 2 is a schematic flow chart of a flow diversion method according to an embodiment of the present application;

FIG. 3a is a schematic diagram of a first topology according to an embodiment of the present application;

FIG. 3b is a schematic diagram of another configuration of a first topology according to an embodiment of the present application;

FIG. 4a is a schematic diagram of a list of nodes available for a first service according to an embodiment of the present application;

FIG. 4b is another schematic diagram of a list of nodes available for the first service according to an embodiment of the present application;

fig. 5a is another schematic diagram of a node list available for a first service according to an embodiment of the present application;

FIG. 5b is another schematic diagram of a list of nodes available for the first service according to an embodiment of the present application;

FIG. 6 is a schematic flow chart of another flow diversion method according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a first node according to an embodiment of the present application;

Fig. 8 is another schematic structural diagram of a first node according to an embodiment of the present application.

Detailed Description

Embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. The terminology used in the description of the embodiments of the application herein is for the purpose of describing particular embodiments of the application only and is not intended to be limiting of the application. As one of ordinary skill in the art can know, with the development of technology and the appearance of new scenes, the technical scheme provided by the embodiment of the application is also applicable to similar technical problems.

The terms first, second and the like in the description and in the claims and in the above-described figures, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances and are merely illustrative of the manner in which embodiments of the application have been described in connection with the description of the objects having the same attributes. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of elements is not necessarily limited to those elements, but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.

The public cloud network service and the private cloud network service are realized independently of a network element cluster, and the network element cluster is used as a core component for forwarding cloud network business and occupies an indispensable position in a cloud service network. For better economic benefit, operators typically rent VMs in a logical multi-tenant form, i.e. a network element cluster is running the services of multiple tenants at the same time. To avoid the reduction of transmission effect caused by huge workload of some nodes and idle condition of some nodes, traffic load is usually balanced to each node of the network element cluster through equivalent routing configuration on the switch.

In order to ensure the reliability of the network, the network element cluster is generally deployed by adopting double AZ or multiple AZ, so that when a certain AZ fails, the service running in the failed AZ can be transferred to other AZ capable of normally working, and the normal running of the service is ensured.

Based on the above problems, the present application proposes that, by acquiring topology information of a network element cluster supporting a certain service in a network element cluster of a cloud service, a device for non-equivalent load sharing (unequal cost multiple path, UCMP) traffic distribution may forward traffic of a virtual machine for the service to any network element cluster in a topology structure according to the topology information, when the device for UCMP traffic distribution acquires that the service of the virtual machine has abnormal service configuration, the device stops forwarding the traffic of the service to the network element cluster, and forwards the traffic of the service of the virtual machine to other network element clusters in the topology structure. In the cloud service, service switching is realized according to service configuration conditions, and service reliability of the cloud service network is improved.

First, a network topology structure according to the solution of the present application is described, referring to fig. 1, fig. 1 is a schematic diagram of a network topology structure provided by an embodiment of the present application.

The network topology structure comprises at least one AZ, at least one VM and at least two service clusters are operated in the AZ, the virtual machine is connected with the UCMP gateway in a communication mode, and the UCMP gateway is connected with the service clusters in a communication mode. As shown in fig. 1, the network topology includes AZ1, AZ2 and AZ3, where the AZ1 runs on VM1, the AZ2 runs on VM2, the AZ3 runs on VM3, the AZ1 includes UCMP gateway 1, service cluster 1 and service cluster 2, the UCMP gateway 1 is communicatively connected to the service cluster 1 and the service cluster 2, the AZ2 includes UCMP gateway 2 and service cluster 3, the UCMP gateway 2 is communicatively connected to the service cluster 3, and the AZ3 includes UCMP3.

The tenant accesses the UCMP gateway 1 through the service 1 set by the VM1, and consumes a subnet IP, where the subnet IP is used to create the service 1 running in the service cluster 1 or the service cluster 2, and the UCMP gateway 1 forwards the traffic of the service 1 created by the VM1 running on the AZ1 to the service cluster 1 or the service cluster 2 of the AZ according to the network element cluster configurations of different AZs.

When the tenant accesses the UCMP gateway 3 through the service 2 set by the VM3, as no service cluster exists in the AZ, the service 2 is distributed to the service cluster 1, the service cluster 2 and/or the service cluster 3 by adopting a load balancing method.

The scheme provided by the application and the application scenario of the embodiment of the application are described briefly, when the service fails, the scheme provided by the application can carry out flow transfer by taking the service of the tenant as a unit and also can carry out flow transfer by taking the tenant as a unit, and the scheme is described below with reference to the accompanying drawings respectively:

first, referring to fig. 2, fig. 2 is a schematic flow chart of a flow transfer method provided by an embodiment of the present application, which is described with respect to a scenario in which a flow transfer is performed by taking a service of a tenant as a unit when a service fails.

201. The method comprises the steps that a first node obtains information of a first topology;

The first node acquires information of a first topology, the first node is located in the first topology, the information of the first topology indicates that the first node is connected with the second node and the third node in a communication mode respectively, the second node supports a first service, and the third node supports the first service.

Based on different networking modes, the topology structure described in the information of the first topology may be as follows, refer to fig. 3a and fig. 3b, where fig. 3a is a schematic structural diagram of the first topology provided by the embodiment of the present application, and fig. 3b is another schematic structural diagram of the first topology provided by the embodiment of the present application.

As can be seen from fig. 3a, the first AZ includes a first node, a second node, and a third node, and the VM runs on the first AZ. Wherein the first node is communicatively coupled to the second node and the first node is communicatively coupled to the third node.

As can be seen from fig. 3b, the first AZ includes a first node and a second node, and the VM operates in the first AZ. The second AZ includes a second node, wherein the first node is communicatively coupled to the second node, and the first node is communicatively coupled to the third node.

It will be appreciated that the description of the first topology is merely an example, and the first topology described in the information of the first topology may be the topology shown in fig. 3a, or may be the topology shown in fig. 3b, and may be set according to requirements in practical applications, which is not limited herein.

It will be appreciated that the steps 201 and 202 are not explicitly sequenced, and the sequencing described herein is merely illustrative, and in practical applications, may be set in connection with specific application scenarios, and is not limited herein.

202. The first node acquires a first service creation request sent by a VM;

the first node obtains a first service creation request sent by the VM. Specifically, after the tenant creates the first service through the VM, the VM generates a first service creation request, and sends the first service creation request to the first node. For example, the tenant checks a first service through the interactive interface, and the first service indicates that the service is commonly implemented through the private cloud and the public cloud. After the VM obtains the checking result, a first service creating request is generated and forwarded to the first node.

It should be noted that, the description of the specific content of the first service is only an example, and in practical application, the specific application scenario should be set, for example, the first service may also refer to that the service is implemented through a private cloud or that the service is implemented through a public cloud, which is not limited herein.

203. The first node generates a first subnet IP;

After the first node obtains the first service creation request, the first node generates a first subnet IP according to the information of the first topology.

Specifically, taking the first topology shown in fig. 3b as an example, the first node is described as generating the first subnet IP.

After the first node obtains the first service creation request, the first node preferentially selects the node supporting the first service in the AZ to perform configuration of the first service, as can be seen from fig. 3b, the first node and the second node are located in the first AZ, the third node is located in the second AZ, and the VM runs in the first AZ. Because traffic flow forwarding across AZ may have a situation of catton or the like due to an overlong data transmission path, the traffic flow of the first service of the VM is preferentially forwarded through the node in the AZ, so that the first node generates a first subnet IP, which is an IP address accessed when the VM runs the first service through the second node.

Optionally, the first node may further generate the first subnet IP and the second subnet IP according to the information of the first topology.

Specifically, taking the first topology shown in fig. 3a as an example, the first node generates a first subnet IP and a second subnet IP.

After the first node obtains the first service creation request, the node supporting the first service in the AZ is preferentially selected to perform configuration of the first service, as can be seen from fig. 3a, the first node, the second node and the third node are located in the first AZ, and the VM operates in the first AZ, so that a first subnet IP and a second subnet IP are generated, where the first subnet IP is an IP address accessed when the VM operates the first service through the second node, and the second subnet IP is an IP address accessed when the VM operates the first service through the third node.

It will be understood that, in the context of the different first topologies, the manner in which the first subnet IP is generated is merely an example, in practical application, the first subnet IP and/or the second subnet IP should be generated in combination with a specific application scenario, for example, when there is no node supporting the first service in the first AZ, the first node generates the third subnet IP, which is an IP address accessed when the VM runs the first service through the fourth node, the fourth node is located at any AZ except the first AZ, and the fourth node supports the first service, which is not limited herein.

204. The first node forwards the traffic of the first service of the VM to the second node;

after generating the first subnet IP, the first node forwards the traffic of the first service of the VM to the second node according to the first subnet IP generated in the first node.

Illustratively, taking the first topology described in the information of the first topology as the topology shown in fig. 3b as an example, after generating the first subnet IP, the first node forwards the traffic of the first service of the VM to the second node according to the first subnet IP generated in the first node.

In a possible implementation manner, the first topology described in the information of the first topology is the topology shown in fig. 3a, after the first node generates the first subnet IP and the second subnet IP, the first node randomly selects the first subnet IP, forwards the traffic of the first service of the VM to the second node according to the first subnet IP, or the first node selects the first subnet IP by using a short burst of load balancing, and forwards the traffic of the first service of the VM to the second node according to the first subnet IP.

It can be understood that, here, the manner of selecting the first subnet IP by different methods for the first node under the condition that the first topology is different, and forwarding the traffic of the first service of the VM to the second node according to the first subnet IP is merely an example, and in practical application, the method should be set in combination with a specific scenario, which is not limited herein.

205. The first node sends a first service detection signal to a first subnet IP;

After forwarding the traffic of the first service of the VM to the second node according to the first subnet IP generated in the first node, the first node continuously sends a first service detection signal to the first subnet IP to monitor whether the first service of the VM arranged at the second node is available.

206. The first node acquires a first detection abnormal signal;

After the first node sends a first service detection signal to the first subnet IP, a first detection abnormal signal is obtained.

Illustratively, since the first node may determine whether the first service of the VM is available by monitoring whether the first subnet IP is reachable. After the first node sends the first service detection signal to the first subnet IP, if the first service configuration of the VM on the second node is abnormal, the second node does not send a feedback signal to the first node; if the first service configuration of the VM on the second node is normal, the second node sends a feedback signal to the first node within 3 s; and therefore, if the feedback signal is not received after 3 seconds, the first detection abnormal signal is considered to be acquired.

It should be understood that the description herein of the first node acquiring the first detection abnormal signal is merely an example, and in practical application, the description should be set in connection with a specific application scenario, which is not limited herein.

207. The first node forwards traffic of the first traffic of the VM to the third node.

After the first node acquires the first detection abnormal signal, the first node stops forwarding the traffic of the first service of the VM to the second node and forwards the traffic of the first service of the VM to the third node.

Optionally, the first node maintains a list of available nodes of each service in the first AZ, when the first subnet IP is unavailable, the first node queries whether there is an available node in the list of available nodes of each service in the first AZ, if so, randomly selects a subnet IP corresponding to the node 1 from the list, or selects a subnet IP corresponding to the node 1 by using a load balancing mode, and forwards the traffic of the first service of the VM to the node 1. If there is no available node in the list, randomly selecting a node 2 from the network reachable by the first node, and forwarding the traffic of the first service of the VM to the node 2.

Specifically, when the first topology is shown in fig. 3b, a list of first AZ first service available nodes maintained in the first node is shown in fig. 4a, and fig. 4a is a schematic diagram of a list of first service available nodes provided in an embodiment of the present application. The node list includes an identification of the first service, a first subnet IP, and an absence (default). After the first node obtains the first abnormal detection signal, updating a node list available for the first service, deleting the first subnet IP therein, and obtaining a new node list available for the first service, wherein the specific form and content are shown in fig. 4b, and fig. 4b is another schematic diagram of the node list available for the first service provided by the embodiment of the present application.

Based on the list of nodes available for the first service depicted in fig. 4b, the first node selects a third node supporting the first service from the nodes reachable by the first node, and the first node forwards the traffic of the first service of the VM to the third node.

In another possible implementation manner, when the first topology is shown in fig. 3a, a list of first AZ first service available nodes maintained in the first node is shown in fig. 5a, and fig. 5a is another schematic diagram of a list of first service available nodes provided by an embodiment of the present application. The node list shown in fig. 5a includes: the method comprises the steps of identifying a first service, a first subnet IP, a second subnet IP and default. After the first node obtains the first abnormal detection signal, updating a node list available for the first service, deleting the first subnet IP therein, and obtaining a new node list available for the first service, wherein the specific form and content are shown in fig. 5b, and fig. 5b is another schematic diagram of the node list available for the first service provided by the embodiment of the present application.

Based on the node list of the first service available described in fig. 5b, the first node selects a second subnet IP corresponding to the third node from the node list of the first service available, and the first node forwards the traffic of the first service of the VM to the third node.

It may be understood that the description herein of the first node switching the traffic of the first service to the third node according to the node list available for the first service is merely an example, and in practical application, the disclosure should be set in connection with a specific application scenario, which is not limited herein.

In the embodiment of the application, by acquiring the information of the first topology, whether the first service configuration of the VM on the second node is normal or not is continuously monitored in the process of forwarding the first service flow of the VM to the second node according to the information of the first topology, and when the first service configuration of the VM on the second node is abnormal, the first service flow is switched to the third node. Wherein the information of the first topology indicates that the first node is communicatively connected with the second node and the third node, respectively, each of the second node and the third node supporting the first service. In the method, whether the first service configuration of the VM forwarded on the second node is abnormal or not is monitored, when the first service configuration of the VM on the second node is abnormal, the first service of the VM is taken as granularity to conduct flow transfer in time, the reliability of the network is improved, the influence on other services of the tenant is reduced, and the service reliability of the cloud service network is improved efficiently.

Referring to fig. 6, fig. 6 is another flow chart of the flow transfer method provided by the embodiment of the present application.

601. The method comprises the steps that a first node obtains information of a first topology;

The topology described in the information of the first topology is similar to that described in the foregoing fig. 3b, and as can be seen from fig. 3b, the first AZ includes the first node and the second node, and the VM operates in the first AZ. The second AZ includes a second node, wherein the first node is communicatively coupled to the second node, and the first node is communicatively coupled to the third node.

It will be appreciated that the description of the first topology is only an example, and the first topology described in the information of the first topology may be the topology shown in fig. 3b, which may be set according to the needs in practical applications, and is not limited herein.

It will be appreciated that the steps 601 and 602 are not explicitly sequenced, and the sequencing described herein is merely illustrative, and in practical applications, the steps may be set in connection with specific application scenarios, which are not limited herein.

602. The first node acquires a first service creation request sent by a VM;

The embodiment of step 602 is similar to the embodiment of step 202 in fig. 2, and detailed description thereof will be omitted herein, with reference to step 202 in fig. 2.

603. The first node generates a first subnet IP;

604. The first node forwards the traffic of the first service of the VM to the second node;

605. The first node acquires a first signal;

the first node acquires a first signal indicating that when the second detection exception signal is acquired, the first node forwards the first traffic of the VM to the third node. Wherein the second probing anomaly signal indicates a first service configuration anomaly that is based on the first service operating in the first topology. The first signal may be that the tenant transfers the traffic of all the services of the VM in the first AZ to the second AZ if the first service is abnormal, which is checked by the tenant through the interactive interface.

The first business indication service is realized by the private cloud and the public cloud together, and the first service is realized by the public cloud and the private cloud together.

It will be appreciated that the description herein of the first service is merely an example, and in practical application, the first service may be any service in any form, and is not limited herein.

It will be appreciated that the steps 605 and 601 to 604 have no explicit sequence, and the sequence described herein is merely illustrative, and may be set in practical application in combination with a specific application scenario, which is not limited herein.

606. The first node sends a second service detection signal to the first subnet IP;

after forwarding the traffic of the first service of the VM to the second node according to the first subnet IP generated in the first node, the first node continuously transmits a second service probe signal to the first subnet IP to monitor whether the first service of the VM arranged at the second node is available or not and whether the configuration of the first service based on the first service is abnormal or not

It will be appreciated that the steps 606 and 605 are not explicitly sequenced, and the sequencing described herein is merely illustrative, and in practical applications, may be set in connection with specific application scenarios, and is not limited herein.

607. The first node acquires a second abnormal detection signal;

and after the first node sends the second service detection signal to the first subnet IP, acquiring a second detection abnormal signal.

Illustratively, since the first node may determine whether the first service of the VM is available by monitoring whether the first subnet IP is reachable. After the first node sends the first service detection signal to the first subnet IP, if the first service configuration of the VM on the second node is abnormal, the second node does not send a feedback signal to the first node; if the first service configuration of the VM on the second node is normal, the second node sends a feedback signal to the first node within 3 s; and therefore, if no feedback signal is received after 3s, the second abnormal detection signal is considered to be acquired. In addition, the first traffic on the second node manages the first service in a similar manner, and if the first traffic on the second node does not detect the feedback signal for obtaining the first service, the second detection abnormality signal is considered to be obtained.

Based on the above description, when the first service configuration of the VM on the second node is abnormal and/or the first service configuration based on the operation of the first service is abnormal, the first node is considered to acquire the second detection abnormal signal.

It should be understood that the description herein of the first node acquiring the second detection abnormal signal is merely an example, and in practical application, the description should be set in connection with a specific application scenario, which is not limited herein.

608. The first node forwards traffic of the first traffic of the VM to the third node.

After the first node acquires the second abnormal detection signal, according to the first signal acquired by the first node, stopping forwarding the flow of the first service of the VM to the second node and forwarding the flow of the first service of the VM to the third node.

Optionally, the first node may further forward traffic of the second service of the VM to a third node, the third node supporting the second service, wherein the second node supports the second service, and the traffic of the second service of the VM is forwarded by the second node.

In the embodiment of the application, after the first node acquires the first signal, when the second abnormal signal is acquired, the first node stops forwarding the flow of the first service of the VM to the second node, and simultaneously, other services running in the first AZ of the VM are migrated to the second AZ, so that more choices are provided for tenants.

In the embodiment of the application, the first node determines the migration standard of the flow of the first service of the VM by acquiring the first signal set by the tenant based on the first signal defined by the tenant, and further, the migration destination of the flow of the first service of the VM can be indicated in the first signal defined by the tenant, so that the flow transfer operation with high tenant compliance is realized, and the flexibility and the operability of the scheme are improved.

The method for transferring the flow provided by the embodiment of the application is described above, and the first node provided by the embodiment of the application is described below with reference to the accompanying drawings.

Referring to fig. 7, fig. 7 is a schematic structural diagram of a first node according to an embodiment of the present application.

A first node, comprising:

An obtaining unit 701, configured to obtain information of a first topology, where the information of the first topology indicates that a first node is connected to a second node and a third node, where the second node supports a first service, and the third node supports the first service;

a sending unit 702, configured to forward, to the second node, a traffic of a first service of a virtual machine;

The obtaining unit 701 is further configured to obtain a fault signal, where the fault signal indicates that the first service configuration of the virtual machine is abnormal;

The sending unit 702 is further configured to forward, to the third node, a traffic of the first service of the virtual machine.

Optionally, the fault signal includes a first detected exception signal, where the first detected exception signal indicates that a first service configuration of the virtual machine on the second node is abnormal;

The sending unit 702 is further configured to send a first service detection signal to a first service of the virtual machine on the second node, where the first service detection signal is used to detect a first service configuration situation of the virtual machine.

Optionally, the obtaining unit 701 is specifically configured to not receive, in a first period of time after a first time, a first feedback signal sent by a first service of the virtual machine on the second node, where the first node obtains the first detection abnormal signal, the first time is a time when the first node sends the first service detection signal, and the first feedback signal indicates that a first service configuration of the virtual machine on the second node is normal.

Optionally, the fault signal includes a second detected anomaly signal, the second detected anomaly signal indicating a first service configuration anomaly operating in the first topology based on the first service;

the sending unit 702 is further configured to send a second service detection signal to the second node, where the second service detection signal is used to detect a configuration situation of the first service.

Optionally, the obtaining unit 701 is specifically configured to, in a second period after a first time, not receive a first feedback signal and/or a second feedback signal sent by the second node, where the first node obtains the second detection abnormal signal, the first time is a time when the first node sends the first service detection signal, the first feedback signal indicates that a first service configuration of a virtual machine on the second node is normal, and the second feedback signal indicates that a first service configuration based on a first service operation of the virtual machine is normal.

Optionally, the first node, the second node and the third node are located in a first availability zone AZ.

Optionally, the first node and the second node are located in a first availability zone AZ, and the third node is located in a second AZ.

Optionally, the obtaining unit 701 is further configured to obtain a first signal, where the first signal indicates that, when the fault signal is obtained, the first node forwards, to the third node, a first service of the virtual machine.

Optionally, the second node supports a second service, and the third node supports the second service;

the sending unit 702 is further configured to forward, to the second node, a traffic of a second service of the virtual machine;

The sending unit 702 is further configured to forward, to the third node, a traffic of the second service of the virtual machine.

Referring to fig. 8, fig. 8 is a schematic diagram of another structure of a first node according to an embodiment of the present application.

The first node 800 includes: processor 810, communication interface 820, and memory 830. The processor 810, the communication interface 820, and the memory 830 may be connected to each other through an internal bus 840, or may communicate through other means such as wireless transmission. In the embodiment of the present application, the bus 840 is exemplified by a peripheral component interconnect (PERIPHERAL COMPONENT INTERCONNECT, PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, etc. the bus 840 may be a Peripheral Component Interconnect (PCI) bus. The bus 840 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in fig. 8, but not only one bus or one type of bus.

The processor 810 may be comprised of at least one general purpose processor, such as a central processing unit (Central Processing Unit, CPU), or a combination of CPU and hardware chips. The hardware chip may be an Application-specific integrated Circuit (ASIC), a programmable logic device (Programmable Logic Device, PLD), or a combination thereof. The PLD may be a complex Programmable Logic device (Complex Programmable Logic Device, CPLD), a Field-Programmable gate array (Field-Programmable GATE ARRAY, FPGA), a general-purpose array Logic (GENERIC ARRAY Logic, GAL), or any combination thereof. The processor 810 executes various types of digitally stored instructions, such as software or firmware programs stored in the memory 830, which enable the first node 800 to provide a variety of services.

The memory 830 is used for storing program codes and is controlled by the processor 810 to execute the processing steps of the occlusion recognition method in the above embodiment. The program code may include one or more software modules, which may be a software module provided in fig. 7, for example, an acquiring unit, a generating unit, or a sending unit, where the acquiring unit is configured to acquire association information of the first AP; the generating unit is used for generating a first management message according to the association information of the first AP, and the first management message indicates the first AP to send the first message to the first STA in the first time slot; and the sending unit is used for sending the second message to the second STA in the first time slot.

It should be noted that, the present embodiment may be implemented by a general physical server, for example, an ARM server or an X86 server, or may be implemented by a virtual machine implemented by combining an NFV technology with a general physical server, where the virtual machine refers to a complete computer system that is simulated by software and has a complete hardware system function and operates in a completely isolated environment, and the present application is not limited in particular.

Memory 830 may include Volatile Memory (Volatile Memory), such as random access Memory (Random Access Memory, RAM); the Memory 830 may also include a Non-Volatile Memory (Non-Volatile Memory), such as Read-Only Memory (ROM), flash Memory (Flash Memory), hard disk (HARD DISK DRIVE, HDD), or Solid state disk (Solid-state disk-STATE DRIVE, SSD); memory 830 may also include combinations of the above. The memory 830 may store program codes to perform the actions performed by the first node in fig. 2 or fig. 6, which will not be described herein.

Communication interface 820 may be a wired interface (e.g., an ethernet interface), may be an internal interface (e.g., a high-speed serial computer expansion bus (PERIPHERAL COMPONENT INTERCONNECT EXPRESS, PCIe) bus interface), a wired interface (e.g., an ethernet interface), or a wireless interface (e.g., a cellular network interface or using a wireless local area network interface) for communicating with other devices or modules.

It should be noted that fig. 8 is only one possible implementation of the embodiment of the present application, and in practical applications, the first node 800 may further include more or fewer components, which is not limited herein. For details not shown or described in the embodiments of the present application, reference may be made to the foregoing description about the first node in fig. 2 or fig. 6, which is not repeated here.

Embodiments of the present application also provide a computer-readable storage medium comprising computer-readable instructions which, when run on a computer, cause the computer to perform any one of the implementations shown in the foregoing method embodiments.

The embodiment of the application also provides a computer program product, which comprises a computer program or instructions, which when run on a computer, cause the computer to execute any one of the implementation modes as shown in the embodiment of the method.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.

In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in part or all of the technical solution or in part in the form of a software product stored in a storage medium, including instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random-access memory (RAM, random access memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

Claims

1. A method of flow diversion, comprising:

The method comprises the steps that a first node obtains information of a first topology, the information of the first topology indicates that the first node is respectively connected with a second node and a third node, the second node supports a first service, and the third node supports the first service;

The first node forwards the traffic of the first service of the virtual machine to the second node;

the first node acquires a fault signal, wherein the fault signal indicates that the first service configuration of the virtual machine is abnormal;

And the first node forwards the traffic of the first service of the virtual machine to the third node.

2. The method of claim 1, wherein the fault signal comprises a first detected exception signal indicating a first traffic configuration exception of the virtual machine on the second node;

Before the first node obtains the fault signal, the method further includes:

The first node sends a first service detection signal to a first service of the virtual machine on the second node, wherein the first service detection signal is used for detecting a first service configuration condition of the virtual machine.

3. The method of claim 2, wherein the first node obtaining a first detected anomaly signal comprises:

And in a first time period after a first time, the first node does not receive a first feedback signal sent by a first service of the virtual machine on the second node, the first node acquires the first detection abnormal signal, the first time is the time when the first node sends the first service detection signal, and the first feedback signal indicates that the first service configuration of the virtual machine on the second node is normal.

4. The method of claim 1, wherein the fault signal comprises a second detected anomaly signal indicating a first service configuration anomaly that operates in the first topology based on the first service;

Before the first node obtains the fault signal, the method further includes:

The first node sends a second service detection signal to the second node, wherein the second service detection signal is used for detecting the configuration condition of the first service.

5. The method of claim 4, wherein the first node obtaining a second detected anomaly signal comprises:

And in a second time period after a first time, the first node does not receive a first feedback signal and/or a second feedback signal sent by the second node, the first node acquires the second detection abnormal signal, the first time is the time when the first node sends the first service detection signal, the first feedback signal indicates that the first service configuration of the virtual machine on the second node is normal, and the second feedback signal indicates that the first service configuration based on the first service operation of the virtual machine is normal.

6. The method according to any of claims 1 to 5, wherein the first node, the second node and the third node are located in a first availability zone AZ.

7. The method according to any of claims 1 to 5, wherein the first node and the second node are located in a first availability zone AZ and the third node is located in a second AZ.

8. The method according to any one of claims 1 to 7, wherein before the first node obtains the fault signal, the method further comprises:

the first node obtains a first signal indicating that when the fault signal is obtained, the first node forwards a first service of the virtual machine to the third node.

9. The method according to any of claims 1 to 8, wherein the second node supports a second service and the third node supports the second service;

Before the first node obtains the fault signal, the method further includes:

The first node forwards the traffic of the second service of the virtual machine to the second node;

after the first node obtains the fault signal, the method further includes:

And the first node forwards the traffic of the second service of the virtual machine to the third node.

10. A first node, comprising:

11. The first node of claim 10, wherein the fault signal comprises a first detected exception signal indicating a first traffic configuration exception of the virtual machine on the second node;

12. The first node of claim 11, wherein the obtaining unit is specifically configured to, in a first duration after a first time, not receive a first feedback signal sent by a first service of the virtual machine on the second node, where the first node obtains the first detection exception signal, and the first time is a time when the first node sends the first service detection signal, where the first feedback signal indicates that a first service configuration of the virtual machine on the second node is normal.

13. The first node of claim 10, wherein the fault signal comprises a second detected anomaly signal indicating a first service configuration anomaly based on the first service operating in the first topology;

14. The first node according to claim 13, wherein the obtaining unit is specifically configured to, in a second period after a first time, not receive a first feedback signal and/or a second feedback signal sent by the second node, where the first node obtains the second detection abnormal signal, the first time is a time when the first node sends the first service detection signal, the first feedback signal indicates that a first service configuration of a virtual machine on the second node is normal, and the second feedback signal indicates that a first service configuration based on a first service operation of the virtual machine is normal.

15. The first node according to any of the claims 10 to 14, characterized in that the first node, the second node and the third node are located in a first availability zone AZ.

16. The first node according to any of the claims 10 to 14, wherein the first node and the second node are located in a first availability zone AZ and the third node is located in a second AZ.

17. The first node according to any of the claims 10 to 16, wherein the obtaining unit is further configured to obtain a first signal, the first signal indicating that the first node forwards the first traffic of the virtual machine to the third node when the failure signal is obtained.

18. A first node according to any of claims 10 to 17, wherein the second node supports a second service and the third node supports the second service;

19. A first node comprising a processor and a memory, the processor coupled to the memory, wherein the memory is configured to store a program;

The processor for executing a program in the memory, such that the method of any of claims 1 to 9 is performed.

20. A computer readable storage medium comprising a program which, when run on a computer, causes the computer to perform the method of any one of claims 1 to 9.

21. A computer program product containing instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1 to 9.