Flow table information deletion method and device, equipment, storage medium and program product

Abstract

The invention relates to a flow table information deletion method and device, equipment, a storage medium and a program product. The method comprises the steps of firstly obtaining all flow table information on a host machine, evaluating link connectivity of a network where the host machine is located under the condition of determining that target flow table information exists in all the flow table information, obtaining a first evaluation result, and deleting the target flow table information according to the first evaluation result, the target flow table information is flow table information which does not correspond to the current version number of the controller where the host machine is located. According to the method, under the condition that the flow table information which does not correspond to the current version number of the controller where the host machine is located exists on the host machine, the link connectivity of the network where the host machine is located is assessed firstly, and under the condition that the link connectivity of the network where the host machine is located meets the preset connectivity requirement, the flow table information corresponding to the current version number of the controller is assessed. And deleting the flow table information which does not correspond to the current version number of the controller to ensure the link connectivity of the network where the host machine is located.

Description

Technical Field

[0001] The present application relates to the field of cloud platform technology, and in particular to a method, device, equipment, storage medium and program product for deleting flow table information. Background Art

[0002] With the increasing popularity of cloud computing, the development of communication technology and the increasing demand of users for cloud computing platforms, the resource pool function of cloud computing platforms needs to be continuously updated. As a result, the version of the Cloud Network Plateform (CNP) controller in the cloud computing platform also needs to be iterated.

[0003] Since the CNP controller manages multiple hosts, each host will issue a corresponding flow table when the network is flowing. Different versions of CNP controllers have different flow tables issued by the corresponding hosts. Therefore, with the iterative update of the CNP controller version, the flow table corresponding to the host also needs to be updated, that is, the flow table corresponding to the old version of the CNP controller is deleted to ensure the stability of the currently used network.

[0004] However, currently, directly deleting the flow table corresponding to the old version of the CNP controller during the operation of the cloud platform may easily lead to poor network stability. Summary of the invention

[0005] Based on this, it is necessary to provide a method, device, equipment, storage medium and program product for deleting flow table information of flow tables corresponding to old versions of controllers while ensuring network stability in response to the above technical problems.

[0006] In a first aspect, the present application provides a method for deleting flow table information, comprising:

[0007] Get all flow table information on the host;

[0008] When it is determined that the target flow table information exists in all the flow table information, the link connectivity of the network where the host machine is located is evaluated to obtain a first evaluation result, and the target flow table information is deleted according to the first evaluation result; the target flow table information is the flow table information that does not correspond to the current version number of the controller where the host machine is located.

[0009] In one of the embodiments, the deleting operation on the target flow table information according to the first evaluation result includes:

[0010] If the first evaluation result indicates that the link connectivity of the network meets the preset link requirements, the target flow table information is deleted, and after the deletion operation is performed, the link connectivity of the network is evaluated for the second time to obtain a second evaluation result, and if the second evaluation result indicates that the link connectivity of the network fails to meet the preset link requirements, the deletion operation is balanced according to the second evaluation result.

[0011] In one embodiment, before evaluating the link connectivity of the network where the host machine is located, the method further includes:

[0012] Send high-priority specific flow table information to the host; high-priority specific flow table information is necessary information for effectively evaluating link connectivity;

[0013] When the second evaluation result indicates that the link connectivity of the network meets the preset link requirement, the high-priority specific flow table information on the host is deleted.

[0014] In one embodiment, the above-mentioned balancing process of the deletion operation according to the second evaluation result includes:

[0015] Send the flow table information corresponding to the current version number to the host machine;

[0016] A third evaluation is performed on the link connectivity of the network to obtain a third evaluation result, and when the third evaluation result indicates that the link connectivity of the network fails to meet the preset link requirement, the deletion operation is balanced according to the third evaluation result.

[0017] In one embodiment, the above-mentioned balancing processing of the deletion operation according to the third evaluation result includes:

[0018] Send all flow table information to the host;

[0019] The link connectivity of the network is evaluated for the fourth time to obtain a fourth evaluation result, and when the fourth evaluation result indicates that the link connectivity of the network meets the preset link requirement, the process of the deletion operation is terminated.

[0020] In one embodiment, the method further comprises:

[0021] Back up and store all flow table information.

[0022] In one embodiment, the method further comprises:

[0023] Determine whether the target flow table information exists in all flow table information;

[0024] Determine whether the target flow table information exists in all flow table information, including:

[0025] If there is flow table information that does not correspond to the current version number of the controller in all the flow table information, determining that there is target flow table information in all the flow table information;

[0026] If all the flow table information corresponds to the current version number of the controller, it is determined that the target flow table information does not exist in all the flow table information.

[0027] In a second aspect, the present application also provides a device for deleting flow table information, including:

[0028] The acquisition module is used to obtain all flow table information on the host;

[0029] A deletion module is used to evaluate the link connectivity of the network where the host machine is located, obtain a first evaluation result, and delete the target flow table information according to the first evaluation result when it is determined that the target flow table information exists in all the flow table information; the target flow table information is the flow table information that does not correspond to the current version number of the controller where the host machine is located.

[0030] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0031] The acquisition module is used to obtain all flow table information on the host;

[0032] A deletion module is used to evaluate the link connectivity of the network where the host machine is located, obtain a first evaluation result, and delete the target flow table information according to the first evaluation result when it is determined that the target flow table information exists in all the flow table information; the target flow table information is the flow table information that does not correspond to the current version number of the controller where the host machine is located.

[0033] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0034] The acquisition module is used to obtain all flow table information on the host;

[0035] A deletion module is used to evaluate the link connectivity of the network where the host machine is located, obtain a first evaluation result, and delete the target flow table information according to the first evaluation result when it is determined that the target flow table information exists in all the flow table information; the target flow table information is the flow table information that does not correspond to the current version number of the controller where the host machine is located.

[0036] In a fifth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0037] The acquisition module is used to obtain all flow table information on the host;

[0038] A deletion module is used to evaluate the link connectivity of the network where the host machine is located, obtain a first evaluation result, and delete the target flow table information according to the first evaluation result when it is determined that the target flow table information exists in all the flow table information; the target flow table information is the flow table information that does not correspond to the current version number of the controller where the host machine is located.

[0039] The above-mentioned method, device, equipment, storage medium and program product for deleting flow table information first obtain all flow table information on the host machine, and when it is determined that the target flow table information exists in all the flow table information, evaluate the link connectivity of the network where the host machine is located, obtain a first evaluation result, and delete the target flow table information according to the first evaluation result. The target flow table information is the flow table information that does not correspond to the current version number of the controller where the host machine is located. The above-mentioned method implements a method in which, when there is flow table information on the host machine that does not correspond to the current version number of the controller where the host machine is located, the link connectivity of the network where the host machine is located is first evaluated, and when the link connectivity of the network where the host machine is located meets the preset connectivity requirements, the flow table information that does not correspond to the current version number of the controller is deleted to ensure the link connectivity of the network where the host machine is located. Compared with the existing method of directly deleting the flow table information that does not correspond to the current version number of the controller, the above-mentioned method takes into account the link connectivity of the network and ensures the link stability of the network to a certain extent. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0041] Figure 1 An application environment diagram of a method for deleting flow table information in an embodiment;

[0042] Figure 2 A schematic diagram of a flow chart of a method for deleting flow table information in an embodiment;

[0043] Figure 3 A schematic diagram of a flow chart of a method for deleting flow table information in another embodiment;

[0044] Figure 4 A schematic diagram of a flow chart of a method for deleting flow table information in another embodiment;

[0045] Figure 5A schematic diagram of a flow chart of a method for deleting flow table information in another embodiment;

[0046] Figure 6 A schematic diagram of a flow chart of a method for deleting flow table information in another embodiment;

[0047] Figure 7 A schematic diagram of a flow chart of a method for deleting flow table information in another embodiment;

[0048] Figure 8 A schematic diagram of a flow chart of a method for deleting flow table information in another embodiment;

[0049] Fig. 9 A schematic diagram of a flow chart of a method for deleting flow table information in another embodiment;

[0050] Fig.10 is a structural block diagram of a device for deleting flow table information in an embodiment;

[0051] Fig.11 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0052] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0053] With the increasing popularity of cloud computing, the development of communication technology and the increasing demand of users for cloud computing platforms, the resource pool function of cloud computing platforms needs to be continuously updated. As a result, the version of the Cloud Network Plateform (CNP) controller in the cloud computing platform also needs to be iterated.

[0054] Since the CNP controller manages multiple hosts, each host will issue a corresponding flow table when the network is flowing. Different versions of CNP controllers have different flow tables issued by the corresponding hosts. Therefore, with the iterative update of the CNP controller version, the flow table corresponding to the host also needs to be updated, that is, the flow table corresponding to the old version of the CNP controller is deleted to ensure the stability of the currently used network.

[0055] However, currently, directly deleting the flow table corresponding to the old version of the CNP controller during the operation of the cloud platform easily leads to the problem of poor network stability. This application aims to solve this problem.

[0056] After introducing the background technology of the method for deleting flow table information provided by the embodiment of the present application, the following briefly describes the implementation environment involved in the method for deleting flow table information provided by the embodiment of the present application. The method for deleting flow table information provided by the embodiment of the present application can be applied to Figure 1 The cloud platform shown in FIG. 1 includes a controller 102 and multiple host machines 104, wherein the controller 102 is connected to each host machine 104, and the controller 102 is used to control each host machine 104, for example, the controller 102 sends certain control instructions to each host machine 104, so that each host machine 104 completes the corresponding control operation according to the control instruction, and after the operation is completed, the operation result is fed back to the controller 102, or the controller 102 obtains all flow table information on the host machine 104, and determines the target flow table information corresponding to the old version of the controller 102 from all the flow table information, and sends an instruction to delete the target flow table information to the host machine 104, so that the host machine 104 deletes the target flow table information after receiving the instruction to delete the target flow table information.

[0057] In other possible implementations, the method for deleting flow table information provided in the embodiment of the present application can also be applied to terminals, which can be, but are not limited to, various personal computers, laptops, smart phones, tablet computers, IoT devices, and portable wearable devices. IoT devices can be smart speakers, smart TVs, smart air conditioners, smart car-mounted devices, etc. Portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc.

[0058] After introducing the application scenarios of the method for deleting flow table information provided by the embodiments of the present application, the following focuses on introducing the method for deleting flow table information described in the present application.

[0059] In one embodiment, Figure 2 As shown, a method for determining flow table information is provided, and the method is applied to Figure 1 The controller 102 in the example is used as an example to illustrate, and the following steps are included:

[0060] S201. Obtain all flow table information on the host machine.

[0061] The host machine is any host machine managed by a controller in the cloud platform, and all flow table information includes flow table information corresponding to an old version of the controller and flow table information corresponding to a current version of the controller.

[0062] It should be noted that the flow tables sent by the host machines corresponding to different versions of controllers are also different. There is a one-to-one correspondence between a version of the controller and the flow table information sent by the host machine under that version. For example, there is a one-to-one correspondence between the old version of the controller and the flow table information sent by the host machine under the old version, and there is a one-to-one correspondence between the current version of the controller and the flow table information sent by the host machine under the current version.

[0063] For example, the flow table cookie information sent by the controller to the host is 64 bits in total. For example, the flow table cookie information can be: 0x0000000000000000, where each bit is a hexadecimal number [63 62 …0]. The high bit [59 … 40] of the flow table cookie information is taken as the version flag bit. Under this premise, it is assumed that the version number of the controller is: 1.2.3, where 1 represents the current implementation framework. If the framework of the controller is reconstructed, the value is incremented by 1. 2 represents a stable stable version. Each time the controller releases a stable version, the value is incremented by 1. 3 represents that the previous stable version needs to release an SP version, and the value based on the original stable version is incremented in sequence. Therefore, the version number of the controller (1.2.3) is integrated into the flow table cookie information, that is, the flow table cookie information 0x0102030000000000 integrated with the controller version number is obtained, thereby realizing a one-to-one correspondence between the flow table cookie information and the controller version number.

[0064] In an embodiment of the present application, when it is necessary to update the flow table corresponding to the host machine, it is necessary to delete the flow table information on the host machine that does not correspond to the current version number of the controller. At this time, the controller needs to first obtain all the flow table information on the host machine, so as to subsequently analyze all the flow table information to determine the flow table information that does not correspond to the current version number of the controller, and provide a data basis for deleting the flow table information that does not correspond to the current version number of the controller.

[0065] S202: When it is determined that the target flow table information exists in all the flow table information, evaluate the link connectivity of the network where the host machine is located to obtain a first evaluation result, and delete the target flow table information according to the first evaluation result.

[0066] The target flow table information is flow table information that does not correspond to the current version number of the controller where the host machine is located.

[0067] The first evaluation result includes that the link connectivity of the network meets the preset connectivity requirement and that the link connectivity of the network does not meet the preset connectivity requirement.

[0068] In the embodiment of the present application, after all the flow table information on the host machine is obtained as mentioned above, it can be determined one by one whether all the flow table information is the flow table information corresponding to the current version number of the controller. If there is no flow table information corresponding to the current version number of the controller in all the flow table information, it means that all the flow table information is the target flow table information. If there is flow table information corresponding to the current version number of the controller in all the flow table information, and there is also flow table information corresponding to the current version number of the controller, it means that the flow table information corresponding to the current version number of the controller is the target flow table information. If there is no flow table information that does not correspond to the current version number of the controller in all the flow table information, it means that all the flow table information is not the target flow table information, that is, the target flow table information does not exist in all the flow table information.

[0069] Furthermore, when it is determined that the target flow table information exists in all the flow table information, the link connectivity of the network where the host machine is located is evaluated to obtain a first evaluation result; optionally, the link connectivity test of the network can be implemented by performing a gateway ping test through a vpping test script, that is, the controller can call the vpping test script to perform a gateway ping test to obtain a first evaluation result that the network link connectivity corresponding to the host machine meets the preset connectivity requirements, or the network link connectivity of the host machine does not meet the preset connectivity requirements.

[0070] It should be noted that the function of the vpping test script is to monitor the virtual machine traffic corresponding to the host machine, and whether the virtual machine traffic remains consistent before and after the target flow table information is deleted. It should be noted that the vpping test script will be called at the time nodes before and after the target flow table information is deleted to verify the connectivity of the virtual machine traffic network link, and the results of the two ping tests can be compared. This solution also takes into account that the virtual machine may be prohibited from pinging. Therefore, during the execution of the script, the gateway information corresponding to the virtual machine will be found according to the virtual machine information, and then the high-priority specific flow table information for inbound and outbound release gateways will be automatically added. Before deleting the residual flow table, the connectivity of the ping link from the tenant gateway to the virtual machine is guaranteed, and the gateway ping test of the virtual machine is performed as soon as the target flow table information is deleted, and the results before and after the residual flow table is deleted are compared. If the link connectivity of the network meets the preset connectivity conditions before deleting the target flow table information, and the link connectivity of the network does not meet the preset connectivity conditions after deleting the target flow table information, it can be considered that the flow table pipeline is interrupted, the target flow table information is still used, and the relevant flow tables involved in the currently running stable version have not been issued. This ping test method can quickly perceive whether the customer business is damaged, and further discover whether the code introduces problems.

[0071] Furthermore, when the first evaluation result indicates that the network link connectivity corresponding to the host machine meets the preset connectivity requirements, the controller may delete the target flow table information; and when the first evaluation result indicates that the network link connectivity corresponding to the host machine does not meet the preset connectivity requirements, the controller may not delete the target flow table information.

[0072] The method for deleting flow table information provided in the embodiment of the present application first obtains all flow table information on the host machine, and when it is determined that the target flow table information exists in all the flow table information, evaluates the link connectivity of the network where the host machine is located, obtains a first evaluation result, and deletes the target flow table information according to the first evaluation result, and the target flow table information is the flow table information that does not correspond to the current version number of the controller where the host machine is located. The above method implements a method in which, when there is flow table information on the host machine that does not correspond to the current version number of the controller where the host machine is located, the link connectivity of the network where the host machine is located is first evaluated, and when the link connectivity of the network where the host machine is located meets the preset connectivity requirements, the flow table information that does not correspond to the current version number of the controller is deleted to ensure the link connectivity of the network where the host machine is located. Compared with the existing method of directly deleting the flow table information that does not correspond to the current version number of the controller, the above method takes into account the link connectivity of the network and ensures the link stability of the network to a certain extent.

[0073] In one embodiment, Figure 2 Based on the embodiment shown, the process of deleting the target flow table information according to the first evaluation result can be described, see Figure 3 , that is, the above S202 "deleting the target flow table information according to the first evaluation result" includes:

[0074] S203. If the first evaluation result indicates that the link connectivity of the network meets the preset link requirements, the target flow table information is deleted, and after the deletion operation is performed, the link connectivity of the network is evaluated for the second time to obtain a second evaluation result, and when the second evaluation result indicates that the link connectivity of the network fails to meet the preset link requirements, the deletion operation is balanced according to the second evaluation result.

[0075] The second evaluation result includes that the link connectivity of the network meets the preset connectivity requirement and that the link connectivity of the network does not meet the preset connectivity requirement.

[0076] In an embodiment of the present application, when the first evaluation result is obtained as mentioned above, if the first evaluation result indicates that the link connectivity of the network meets the preset link requirements, the target flow table information is deleted, and after detecting that the host machine has completely deleted the target flow table information, the link connectivity of the network where the host machine is located is evaluated for the second time to obtain a second evaluation result that the link connectivity of the network meets the preset connectivity requirements, or a second evaluation result that the link connectivity of the network does not meet the preset connectivity requirements. If the second evaluation result is that the link connectivity of the network meets the preset connectivity requirements, it is considered that the deleted target flow table information is flow table information that is no longer in use. If the second evaluation result is that the link connectivity of the network does not meet the preset connectivity requirements, it is considered that there is still flow table information in the deleted target flow table information that is in use. Deleting these in use flow table information makes the link connectivity of the network not meet the preset connectivity conditions. Therefore, it is necessary to identify the flow table information in use in the target flow table information again, and do not delete the flow table information in use to ensure the link connectivity of the network.

[0077] It should be noted that the second evaluation is used to test the link connectivity of the network, which can be achieved by performing a gateway ping test through the vpping test script, that is, the controller can call the vpping test script to perform a gateway ping test to obtain a second evaluation result that the network link connectivity corresponding to the host machine meets the preset connectivity requirements, or the network link connectivity of the host machine does not meet the preset connectivity requirements.

[0078] The above-mentioned method for deleting flow table information, by evaluating the network link connectivity of the host machine after deleting the target flow table information, can not only ensure that the network link connectivity after deleting the target flow table information meets the requirements, but also ensure that when the network link connectivity after deleting the target flow table information does not meet the requirements, the host machine is further processed, thereby ensuring that the network link connectivity of the host machine meets the requirements under any circumstances.

[0079] In one embodiment, Figure 3 Based on the embodiment shown, before evaluating the link connectivity of the network where the host is located, refer to Figure 4 , the above method further comprises:

[0080] S204: Send high-priority specific flow table information to the host machine.

[0081] The high-priority specific flow table information is necessary information for effectively evaluating link connectivity. By adding the high-priority specific flow table information, the host machine ensures that when evaluating the link connectivity of the network later, the client's virtual machine does not have a PING ban.

[0082] In an embodiment of the present application, before evaluating the link connectivity of the network where the host machine is located, the controller can first send high-priority specific flow marker information to the host machine, so that the host machine adds the high-priority specific flow marker information, thereby avoiding the situation where PING is prohibited for the customer's virtual machine when performing subsequent network link connectivity evaluation.

[0083] S205: When the second evaluation result indicates that the link connectivity of the network meets the preset link requirement, the high-priority specific flow table information on the host is deleted.

[0084] In an embodiment of the present application, when the second evaluation result is obtained as mentioned above, if the second evaluation result indicates that the link connectivity of the network meets the preset link requirements, it is considered that the deleted target flow table information is the flow table information that is no longer used, that is, deleting the target flow table information has no effect on the link connectivity of the network. At this time, a deletion command can be sent to the host machine to enable the host machine to delete the high-priority specific flow label information on it.

[0085] The method for deleting flow table information provided in the embodiment of the present application avoids the situation where PING is prohibited on the customer's virtual machine when performing subsequent link connectivity evaluation of the network by adding high-priority specific flow table information on the host machine.

[0086] In one embodiment, Figure 3 Based on the embodiment shown, the process of performing balanced processing on the deletion operation according to the second evaluation result can be described, see Figure 5 , that is, the above S203 "balance the deletion operation according to the second evaluation result" includes:

[0087] S301. Send the flow table information corresponding to the current version number to the host machine.

[0088] In an embodiment of the present application, when the above-mentioned second evaluation result indicates that the link connectivity of the network fails to meet the preset link requirements, it means that there is flow table information in use in the target flow table information to be deleted. At this time, in order to exclude the flow table information corresponding to the current version number of the controller from being deleted, the flow table information of the current version number can be re-sent to the host machine.

[0089] S302: Perform a third evaluation on the link connectivity of the network to obtain a third evaluation result, and when the third evaluation result indicates that the link connectivity of the network fails to meet the preset link requirement, perform a balanced processing on the deletion operation according to the third evaluation result.

[0090] In an embodiment of the present application, after detecting that the host machine has received the flow table information corresponding to the current version number, the link connectivity of the network where the host machine is located can be evaluated for the third time to obtain a third evaluation result that the link connectivity of the network meets the preset connectivity requirements, or a third evaluation result that the link connectivity of the network does not meet the preset connectivity requirements. If the third evaluation result is that the link connectivity of the network meets the preset connectivity requirements, it is considered that the deleted target flow table information includes the flow table information corresponding to the current version number, and there is an erroneous deletion. If the third evaluation result is that the link connectivity of the network does not meet the preset connectivity requirements, it is considered that the flow table information corresponding to the historical version number is still in use in the deleted target flow table information. Deleting the flow table information corresponding to the historical version numbers in use makes the link connectivity of the network fail to meet the preset connectivity conditions. Therefore, it is necessary to identify the flow table information in use in the target flow table information again, and the flow table information in use is not deleted to ensure the link connectivity of the network.

[0091] Optionally, if the third evaluation result is that the link connectivity of the network meets the preset connectivity requirements, it is considered that the deleted target flow table information includes the flow table information corresponding to the current version number, and there is an accidental deletion. At this time, the high-priority specific flow table information on the host machine can be deleted.

[0092] It should be noted that the third evaluation is used to test the link connectivity of the network, which can be achieved by performing a gateway ping test through the vpping test script, that is, the controller can call the vpping test script to perform a gateway ping test to obtain a third evaluation result that the network link connectivity corresponding to the host machine meets the preset connectivity requirements, or the network link connectivity of the host machine does not meet the preset connectivity requirements.

[0093] The above-mentioned method for deleting flow table information ensures whether the network link unavailability is caused by the accidental deletion of the flow table information corresponding to the current version number by evaluating the network link connectivity of the host machine after the flow table information corresponding to the current version number is issued, and further processes the host machine when the network link unavailability is not caused by the accidental deletion of the flow table information corresponding to the current version number, thereby ensuring that the connectivity of the network link of the host machine meets the requirements under any circumstances.

[0094] In one embodiment, Figure 5 Based on the embodiment shown, the process of performing balanced processing on the deletion operation according to the third evaluation result can be described, see Figure 6 , that is, the above S302 "balance the deletion operation according to the third evaluation result" includes:

[0095] S401. Send all flow table information to the host machine.

[0096] In an embodiment of the present application, when the third evaluation result indicates that the link connectivity of the network fails to meet the preset link requirements, it means that the deleted target flow table information contains flow table information corresponding to the historical version in use. At this time, all flow table information can be re-sent to the host machine.

[0097] S402: Perform a fourth evaluation on the link connectivity of the network to obtain a fourth evaluation result, and when the fourth evaluation result indicates that the link connectivity of the network meets the preset link requirement, end the process of the deletion operation.

[0098] In an embodiment of the present application, after detecting that the host machine has received all the flow table information, the link connectivity of the network where the host machine is located can be evaluated for the fourth time to obtain a fourth evaluation result that the link connectivity of the network meets the preset connectivity requirements, or a fourth evaluation result that the link connectivity of the network does not meet the preset connectivity requirements. If the fourth evaluation result is that the link connectivity of the network meets the preset connectivity requirements, it is considered that the target flow table information to be deleted includes the flow table information corresponding to the historical version number in use, and the deletion operation process needs to be terminated. After the flow table information corresponding to the historical version number in use is completed, the deletion operation can be performed again to ensure the link connectivity of the network.

[0099] Optionally, if the fourth evaluation result is that the link connectivity of the network meets the preset connectivity requirement, the high-priority specific flow table information on the host machine may be deleted.

[0100] It should be noted that the fourth evaluation is used to test the link connectivity of the network, which can be achieved by performing a gateway ping test through the vpping test script, that is, the controller can call the vpping test script to perform a gateway ping test to obtain a fourth evaluation result that the network link connectivity corresponding to the host machine meets the preset connectivity requirements, or the network link connectivity of the host machine does not meet the preset connectivity requirements.

[0101] The above-mentioned method for deleting flow table information ensures whether the network link failure is caused by the accidental deletion of the flow table information corresponding to the historical version number by evaluating the network link connectivity of the host machine after all the flow table information is sent, and ends the deletion operation if the network link failure is caused by the accidental deletion of the flow table information corresponding to the historical version number.

[0102] In one embodiment, Figure 2-Figure 6 Based on the embodiment shown, see Figure 7 , the above method further comprises:

[0103] S206: Back up and store all flow table information.

[0104] In an embodiment of the present application, when it is determined that the target flow table information exists in all the flow table information, all the flow table information can be backed up and stored first, and after the backup and storage of all the flow table information is completed, the flow table information corresponding to the current version number is re-sent to the host machine, and the link connectivity of the network where the host machine is located is evaluated to obtain a first evaluation result.

[0105] The method for backing up and storing all flow table information provided in the embodiment of the present application provides a data basis for subsequently sending all flow table information to the host machine.

[0106] In one embodiment, Figure 2-Figure 6 Based on the embodiment shown, see Figure 8 , the above method further comprises:

[0107] S207: Determine whether target flow table information exists in all flow table information.

[0108] In an embodiment of the present application, after all the flow table information on the host machine is obtained as mentioned above, it can be determined whether each flow table information in all the flow table information corresponds to the current version number of the controller. If each flow table information corresponds to the current version number of the controller, it means that the target flow table information does not exist in all the flow table information; if there is flow table information in all the flow table information that does not correspond to the current version number of the controller, it means that the target flow table information exists in all the flow table information.

[0109] Optionally, the above S207 "determine whether there is target flow table information in all flow table information" includes: if there is flow table information in all flow table information that does not correspond to the current version of the controller, then determine that there is target flow table information in all flow table information; if all flow table information corresponds to the current version of the controller, then determine that there is no target flow table information in all flow table information.

[0110] The method for deleting flow table information provided in the present application determines the target flow table information in all flow table information through the version number of the controller, thereby providing a data basis for the subsequent deletion of the target flow table information.

[0111] In one embodiment, see Fig. 9 , and also provides a method for deleting flow table information, including:

[0112] S10, obtain all flow table information on the host;

[0113] S11, back up and store all flow table information;

[0114] S12. When it is determined that the target flow table information exists in all the flow table information, send the high-priority specific flow table information to the host machine;

[0115] S13, evaluating the link connectivity of the network where the host machine is located, and obtaining a first evaluation result;

[0116] S14. When the first evaluation result indicates that the link connectivity performance of the network meets the preset link requirement, the target flow table information is deleted;

[0117] S15. After executing the deletion operation, performing a second evaluation on the link connectivity of the network to obtain a second evaluation result;

[0118] S16. When the second evaluation result indicates that the link connectivity of the network fails to meet the preset link requirement, the flow table information corresponding to the current version number is sent to the host machine;

[0119] S17, performing a third evaluation on the link connectivity of the network to obtain a third evaluation result;

[0120] S18. When the third evaluation result indicates that the link connectivity of the network fails to meet the preset link requirement, all flow table information is sent to the host machine;

[0121] S19. Perform a fourth evaluation on the link connectivity of the network to obtain a fourth evaluation result. When the fourth evaluation result indicates that the link connectivity of the network meets the preset link requirement, end the deletion operation process and delete the high-priority specific flow table information.

[0122] The above method implements a method in which, when there is flow table information on the host machine that does not correspond to the current version number of the controller where the host machine is located, the link connectivity of the network where the host machine is located is first evaluated, and when the link connectivity of the network where the host machine is located meets the preset connectivity requirements, the flow table information that does not correspond to the current version number of the controller is deleted to ensure the link connectivity of the network where the host machine is located. Compared with the existing method of directly deleting the flow table information that does not correspond to the current version number of the controller, the above method takes into account the link connectivity of the network and ensures the link stability of the network to a certain extent.

[0123] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0124] Based on the same inventive concept, the embodiment of the present application also provides a flow table information deletion device for implementing the flow table information deletion method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the one or more flow table information deletion device embodiments provided below can refer to the limitations of the flow table information deletion method above, and will not be repeated here.

[0125] In an exemplary embodiment, Fig.10 As shown, a device for deleting flow table information is provided, including: an acquisition module 10 and a deletion module 11, wherein:

[0126] The acquisition module 10 is used to acquire all flow table information on the host machine.

[0127] The deletion module 11 is used to evaluate the link connectivity of the network where the host machine is located, obtain a first evaluation result, and delete the target flow table information according to the first evaluation result when it is determined that the target flow table information exists in all the flow table information; the target flow table information is the flow table information that does not correspond to the current version number of the controller where the host machine is located.

[0128] In an exemplary embodiment, the above-mentioned deletion module 11 includes: a first deletion unit, which is specifically used to perform a deletion operation on the target flow table information when the first evaluation result indicates that the link connectivity performance of the network meets the preset link requirements, and after performing the deletion operation, perform a second evaluation on the link connectivity of the network to obtain a second evaluation result, and when the second evaluation result indicates that the link connectivity of the network fails to meet the preset link requirements, balance the deletion operation according to the second evaluation result.

[0129] In an exemplary embodiment, before evaluating the link connectivity of the network where the host machine is located, the apparatus further includes: a sending unit and a second deleting unit, wherein:

[0130] The sending unit is specifically used to send high-priority specific flow table information to the host; the high-priority specific flow table information is necessary information for effectively evaluating link connectivity;

[0131] The second deleting unit is specifically configured to delete the high-priority specific flow table information on the host machine when the second evaluation result indicates that the link connectivity of the network meets the preset link requirement.

[0132] In an exemplary embodiment, the above-mentioned second deletion unit is specifically used to send the flow table information corresponding to the current version number to the host machine; perform a third evaluation on the link connectivity of the network to obtain a third evaluation result, and when the third evaluation result indicates that the link connectivity of the network fails to meet the preset link requirements, the deletion operation is balanced according to the third evaluation result.

[0133] In an exemplary embodiment, the above-mentioned second deletion unit is specifically used to send all flow table information to the host machine; perform a fourth evaluation on the link connectivity of the network to obtain a fourth evaluation result, and when the fourth evaluation result indicates that the link connectivity of the network meets the preset link requirements, end the deletion operation process.

[0134] In an exemplary embodiment, the above-mentioned device further includes: a backup module, which is used to back up and store all flow table information.

[0135] In an exemplary embodiment, the above-mentioned device further includes: a determination module, configured to determine whether there is target flow table information in all flow table information;

[0136] The determination module includes: a first determination unit and a second determination unit, wherein:

[0137] A first determining unit is specifically configured to determine whether target flow table information exists in all flow table information when flow table information that does not correspond to the current version number of the controller exists in all flow table information;

[0138] The second determining unit is specifically configured to determine that the target flow table information does not exist in the entire flow table information when all the flow table information corresponds to the current version number of the controller.

[0139] Each module in the above-mentioned flow table information deletion device can be implemented in whole or in part by software, hardware, or a combination thereof. Each of the above-mentioned modules can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each of the above modules.

[0140] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Fig.11As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store flow table information data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for deleting flow table information is implemented.

[0141] Those skilled in the art will understand that Fig.11 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0142] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0143] Get all flow table information on the host;

[0144] When it is determined that the target flow table information exists in all the flow table information, the link connectivity of the network where the host machine is located is evaluated to obtain a first evaluation result, and the target flow table information is deleted according to the first evaluation result; the target flow table information is the flow table information that does not correspond to the current version number of the controller where the host machine is located.

[0145] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0146] If the first evaluation result indicates that the link connectivity of the network meets the preset link requirements, the target flow table information is deleted, and after the deletion operation is performed, the link connectivity of the network is evaluated for the second time to obtain a second evaluation result, and if the second evaluation result indicates that the link connectivity of the network fails to meet the preset link requirements, the deletion operation is balanced according to the second evaluation result.

[0147] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0148] Send high-priority specific flow table information to the host; high-priority specific flow table information is necessary information for effectively evaluating link connectivity;

[0149] When the second evaluation result indicates that the link connectivity of the network meets the preset link requirement, the high-priority specific flow table information on the host is deleted.

[0150] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0151] Send the flow table information corresponding to the current version number to the host machine;

[0152] A third evaluation is performed on the link connectivity of the network to obtain a third evaluation result, and when the third evaluation result indicates that the link connectivity of the network fails to meet the preset link requirement, the deletion operation is balanced according to the third evaluation result.

[0153] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0154] Send all flow table information to the host;

[0155] The link connectivity of the network is evaluated for the fourth time to obtain a fourth evaluation result, and when the fourth evaluation result indicates that the link connectivity of the network meets the preset link requirement, the process of the deletion operation is terminated.

[0156] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0157] Back up and store all flow table information.

[0158] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0159] Determine whether the target flow table information exists in all flow table information;

[0160] Determine whether the target flow table information exists in all flow table information, including:

[0161] If there is flow table information that does not correspond to the current version number of the controller in all the flow table information, determining that there is target flow table information in all the flow table information;

[0162] If all the flow table information corresponds to the current version number of the controller, it is determined that the target flow table information does not exist in all the flow table information.

[0163] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0164] Get all flow table information on the host;

[0165] When it is determined that the target flow table information exists in all the flow table information, the link connectivity of the network where the host machine is located is evaluated to obtain a first evaluation result, and the target flow table information is deleted according to the first evaluation result; the target flow table information is the flow table information that does not correspond to the current version number of the controller where the host machine is located.

[0166] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0167] If the first evaluation result indicates that the link connectivity of the network meets the preset link requirements, the target flow table information is deleted, and after the deletion operation is performed, the link connectivity of the network is evaluated for the second time to obtain a second evaluation result, and if the second evaluation result indicates that the link connectivity of the network fails to meet the preset link requirements, the deletion operation is balanced according to the second evaluation result.

[0168] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0169] Send high-priority specific flow table information to the host; high-priority specific flow table information is necessary information for effectively evaluating link connectivity;

[0170] When the second evaluation result indicates that the link connectivity of the network meets the preset link requirement, the high-priority specific flow table information on the host is deleted.

[0171] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0172] Send the flow table information corresponding to the current version number to the host machine;

[0173] A third evaluation is performed on the link connectivity of the network to obtain a third evaluation result, and when the third evaluation result indicates that the link connectivity of the network fails to meet the preset link requirement, the deletion operation is balanced according to the third evaluation result.

[0174] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0175] Send all flow table information to the host;

[0176] The link connectivity of the network is evaluated for the fourth time to obtain a fourth evaluation result, and when the fourth evaluation result indicates that the link connectivity of the network meets the preset link requirement, the process of the deletion operation is terminated.

[0177] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0178] Back up and store all flow table information.

[0179] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0180] Determine whether the target flow table information exists in all flow table information;

[0181] Determine whether the target flow table information exists in all flow table information, including:

[0182] If there is flow table information that does not correspond to the current version number of the controller in all the flow table information, determining that there is target flow table information in all the flow table information;

[0183] If all the flow table information corresponds to the current version number of the controller, it is determined that the target flow table information does not exist in all the flow table information.

[0184] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0185] Get all flow table information on the host;

[0186] When it is determined that the target flow table information exists in all the flow table information, the link connectivity of the network where the host machine is located is evaluated to obtain a first evaluation result, and the target flow table information is deleted according to the first evaluation result; the target flow table information is the flow table information that does not correspond to the current version number of the controller where the host machine is located.

[0187] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0188] If the first evaluation result indicates that the link connectivity of the network meets the preset link requirements, the target flow table information is deleted, and after the deletion operation is performed, the link connectivity of the network is evaluated for the second time to obtain a second evaluation result, and if the second evaluation result indicates that the link connectivity of the network fails to meet the preset link requirements, the deletion operation is balanced according to the second evaluation result.

[0189] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0190] Send high-priority specific flow table information to the host; high-priority specific flow table information is necessary information for effectively evaluating link connectivity;

[0191] When the second evaluation result indicates that the link connectivity of the network meets the preset link requirement, the high-priority specific flow table information on the host is deleted.

[0192] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0193] Send the flow table information corresponding to the current version number to the host machine;

[0194] A third evaluation is performed on the link connectivity of the network to obtain a third evaluation result, and when the third evaluation result indicates that the link connectivity of the network fails to meet the preset link requirement, the deletion operation is balanced according to the third evaluation result.

[0195] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0196] Send all flow table information to the host;

[0197] The link connectivity of the network is evaluated for the fourth time to obtain a fourth evaluation result, and when the fourth evaluation result indicates that the link connectivity of the network meets the preset link requirement, the process of the deletion operation is terminated.

[0198] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0199] Back up and store all flow table information.

[0200] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0201] Determine whether the target flow table information exists in all flow table information;

[0202] Determine whether the target flow table information exists in all flow table information, including:

[0203] If there is flow table information that does not correspond to the current version number of the controller in all the flow table information, determining that there is target flow table information in all the flow table information;

[0204] If all the flow table information corresponds to the current version number of the controller, it is determined that the target flow table information does not exist in all the flow table information.

[0205] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0206] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0207] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0208] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be construed as limiting the scope of the present application. It should be noted that, for a person of ordinary skill in the art, several modifications and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A method for deleting flow table information, characterized in that: The method comprises: Get all flow table information on the host; When it is determined that target flow table information exists in all the flow table information, the link connectivity of the network where the host machine is located is evaluated to obtain a first evaluation result, and the target flow table information is deleted based on the first evaluation result; the target flow table information is the flow table information that does not correspond to the current version number of the controller where the host machine is located.

2. The method according to claim 1, characterized in that: The deleting operation on the target flow table information according to the first evaluation result includes: If the first evaluation result indicates that the link connectivity performance of the network meets the preset link requirements, the target flow table information is deleted, and after performing the deletion operation, the link connectivity of the network is evaluated for the second time to obtain a second evaluation result, and if the second evaluation result indicates that the link connectivity of the network fails to meet the preset link requirements, the deletion operation is balanced according to the second evaluation result.

3. The method according to claim 2, characterized in that Before evaluating the link connectivity of the network where the host machine is located, the method further includes: Sending high-priority specific flow table information to the host machine; the high-priority specific flow table information is necessary information for effectively evaluating link connectivity; When the second evaluation result indicates that the link connectivity of the network meets the preset link requirement, the high-priority specific flow table information on the host is deleted.

4. The method according to claim 2, characterized in that: The performing balanced processing on the deletion operation according to the second evaluation result includes: Sending the flow table information corresponding to the current version number to the host machine; The link connectivity of the network is evaluated for the third time to obtain a third evaluation result, and when the third evaluation result indicates that the link connectivity of the network fails to meet the preset link requirement, the deletion operation is balanced according to the third evaluation result.

5. The method according to claim 4, characterized in that The performing balanced processing on the deletion operation according to the third evaluation result includes: Sending all the flow table information to the host machine; The link connectivity of the network is evaluated for the fourth time to obtain a fourth evaluation result, and when the fourth evaluation result indicates that the link connectivity of the network meets the preset link requirement, the process of the deletion operation is terminated.

6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: Back up and store all the flow table information.

7. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: Determine whether the target flow table information exists in all the flow table information; The determining whether the target flow table information exists in the entire flow table information includes: If flow table information that does not correspond to the current version number of the controller exists in all the flow table information, determining that the target flow table information exists in all the flow table information; If all the flow table information corresponds to the current version number of the controller, it is determined that the target flow table information does not exist in the all the flow table information.

8. A device for deleting flow table information, characterized in that: The device comprises: The acquisition module is used to obtain all flow table information on the host; A deletion module is used to evaluate the link connectivity of the network where the host machine is located, obtain a first evaluation result, and delete the target flow table information according to the first evaluation result when it is determined that the target flow table information exists in all the flow table information; the target flow table information is the flow table information that does not correspond to the current version number of the controller where the host machine is located.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images