Configuration issuing verification method and device for SDN controller, and medium

Abstract

The invention discloses a configuration issuing verification method and device for an SDN (Software Defined Network) controller and a medium. The method comprises the following steps: the SDN controller extracts a service type and a device type from service data; converting the service data according to the service type and the equipment type to generate a recognizable command line; in a command template database, matching the service type with the equipment type to obtain a target command template; according to the target command template, performing configuration integrity verification on the recognizable command line; performing data correctness verification on the recognizable command line according to the service data; performing configuration conflict verification on the recognizable command line according to the historical configuration content; and when the configuration integrity check, the data correctness check and the configuration conflict check are all passed, performing configuration issuing on the recognizable command line. And the configuration issuing accuracy can be effectively ensured.

Description

Technical Field

[0001] The present application relates to the field of SDN control technology, and in particular to a configuration delivery verification method, device and medium for an SDN controller. Background Art

[0002] With the development of SDN technology, business launch is operated through the graphical interface provided by the SDN controller. Business information is transmitted to the background of the SDN controller through the front-end interface for processing. The SDN background code translates the business information and converts it into command lines that can be recognized by hardware network devices and sends it to the hardware devices.

[0003] However, due to the complexity of the network environment, services may affect each other, and the network configuration is complex. When errors occur in the service configuration, the service configuration cannot be sent to the hardware device, thereby affecting the service launch. Therefore, it is necessary to effectively ensure the accuracy of the configuration sent by the SDN controller. Summary of the invention

[0004] The embodiments of the present application provide a configuration delivery verification method, device and medium for an SDN controller, which are used to solve the problem of effectively ensuring the accuracy of configuration delivery of the SDN controller.

[0005] The present application embodiment adopts the following technical solutions:

[0006] On the one hand, an embodiment of the present application provides a configuration delivery verification method for an SDN controller, the method comprising: the SDN controller extracts a service type and a device type from service data; according to the service type and the device type, the service data is converted to generate a recognizable command line; in a command template database, the service type and the device type are matched to obtain a target command template; according to the target command template, a configuration integrity check is performed on the recognizable command line; according to the service data, a data correctness check is performed on the recognizable command line; according to the historical configuration content, a configuration conflict check is performed on the recognizable command line; when the configuration integrity check, the data correctness check and the configuration conflict check are all passed, the configuration of the recognizable command line is delivered.

[0007] In one example, the configuration integrity check of the recognizable command line is performed based on the target command template, specifically including: determining whether the total number of lines of the recognizable command line is consistent with the total number of lines of the target command template; if they are consistent, determining in turn whether the number of lines of each line in the recognizable command line is consistent with the number of lines of each line in the target command template; if they are consistent, determining that the configuration integrity check of the recognizable command line has passed.

[0008] In one example, the data correctness check of the recognizable command line is performed based on the business data, specifically including: determining whether the key parameter content in the recognizable command line is consistent with the business content in the business data; if consistent, determining that the data correctness check of the recognizable command line has passed.

[0009] In one example, performing a configuration conflict check on the recognizable command line based on historical configuration content specifically includes: searching the historical configuration content to see whether there is a configuration record of the business type and the device type; if not, determining that the configuration conflict check of the recognizable command line passes.

[0010] In one example, the method further includes: generating verification results of configuration integrity check, data correctness check and configuration conflict check; calling the managed device topology map of the SDN controller; and displaying the verification results in a graphical manner in the managed device topology map.

[0011] In one example, the method further includes: when a verification fails, determining the managed device model location corresponding to the device type in the managed device topology map; and displaying the reason for the verification failure in a preset display area of ​​the managed device model location.

[0012] In one example, before matching the business type and the device type in the command template database to obtain the target command template, the method also includes: acquiring sample business types and sample device types, and constructing sample command templates of the sample business types and sample device types; establishing a mapping relationship between the sample business types and sample device types and the sample command templates; outputting the sample command templates to the command template database, and associating the mapping relationship with the sample command template in the command template database.

[0013] In one example, the SDN controller extracts the service type and the device type from the service data, specifically including: the SDN controller obtains the service data through a display interface; according to a preset writing rule of the service data, extracts the service type in the data position of the service type, and extracts the device type in the data position of the device type.

[0014] On the other hand, an embodiment of the present application provides a configuration delivery verification device for an SDN controller, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute any one of the above-described configuration delivery verification methods for an SDN controller.

[0015] On the other hand, an embodiment of the present application provides a non-volatile computer storage medium for configuration delivery verification of an SDN controller, storing computer executable instructions, and the computer executable instructions can execute any of the above-mentioned configuration delivery verification methods for an SDN controller.

[0016] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects:

[0017] Before the service configuration is issued, the constructed command template can be used to verify the configuration integrity of the service configuration and identify incomplete recognizable command lines in advance. In addition, in combination with the service data, the recognizable command lines are verified for data correctness, and recognizable command lines with conversion errors can be identified in advance. In addition, in combination with the historical configuration content, the recognizable command lines are verified for configuration conflicts, so as to identify in advance whether the service configuration is issued repeatedly. In this way, the configuration to be issued can be comprehensively verified in advance through the three dimensions of configuration completeness, configuration data correctness, and existing configuration conflicts, effectively ensuring that the service configuration can be correctly issued to the hardware device, improving the effectiveness of configuration issuance, and avoiding network interruptions caused by configuration anomalies to the greatest extent. It is equivalent to providing an intuitive, fast and comprehensive configuration pre-verification result to avoid configuration errors or configuration conflicts from affecting the stability of the network. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solution of the present application, some embodiments of the present application will be described in detail below in conjunction with the accompanying drawings, in which:

[0019] Figure 1 A flowchart of a configuration delivery verification method for an SDN controller provided in an embodiment of the present application;

[0020] Figure 2 A schematic diagram of the structure of a configuration delivery verification device for an SDN controller provided in an embodiment of the present application. DETAILED DESCRIPTION

[0021] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0022] Some embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0023] Figure 1 A flow chart of a configuration delivery verification method for an SDN controller provided in an embodiment of the present application. The method can be applied to different business fields, such as the Internet financial business field, the e-commerce business field, the instant messaging business field, the game business field, the official business field, etc. The process can be executed by a computing device in the corresponding field, and some input parameters or intermediate results in the process allow manual intervention and adjustment to help improve accuracy.

[0024] The analysis method involved in the embodiments of the present application can be implemented by a terminal device or a server, and the present application does not impose any special restrictions on this. For the convenience of understanding and description, the following embodiments are described in detail by taking a server as an example.

[0025] It should be noted that the server may be a single device or a system consisting of multiple devices, that is, a distributed server, and this application does not make any specific limitation on this.

[0026] Figure 1 The process in includes the following steps:

[0027] S101: The SDN controller extracts a service type and a device type from service data.

[0028] In some embodiments of the present application, the SDN controller obtains service data through a display interface. For example, a user inputs service data on the display interface of the SDN controller.

[0029] Then, according to the preset writing rules of the business data, the business type is extracted from the data position of the business type, and the device type is extracted from the data position of the device type.

[0030] For example, the device type is switch model A, and the service type is ACL policy.

[0031] S102: Convert the service data according to the service type and the device type to generate a recognizable command line.

[0032] In the command line format mapping relationship table, the service type and the device type are searched to obtain the target command line format, so that the relevant parameters of the service data are converted according to the target command line format to obtain a recognizable command line.

[0033] S103: Match the service type and the device type in a command template database to obtain a target command template.

[0034] In some embodiments of the present application, it is necessary to pre-build a command template database, which includes multiple command templates.

[0035] Specifically, first, sample service types and sample device types are obtained, and sample command templates of the sample service types and sample device types are constructed. Then, a mapping relationship between the sample service types and sample device types and the sample command templates is established. Thus, the sample command templates are output to a command template database, and in the command template database, the mapping relationship is associated with the sample command templates.

[0036] It should be noted that certain service types and device types have fixed configuration command lines, so a command template can be set, and the command template is actually a command line that can be issued for configuration.

[0037] S104: Performing configuration integrity verification on the recognizable command line according to the target command template.

[0038] In some embodiments of the present application, the process of performing configuration integrity verification on the recognizable command line is as follows:

[0039] First, determine whether the total number of lines of the recognizable command line is consistent with the total number of lines of the target command template. If they are consistent, then determine whether the number of lines of each line in the recognizable command line is consistent with the number of lines of each line in the target command template. If they are consistent, it is determined that the configuration integrity check of the recognizable command line has passed.

[0040] It should be noted that when the total number of lines of the recognizable command line is inconsistent with the total number of lines of the target command template, it is determined that the configuration integrity check of the recognizable command line has not passed, and the number of lines of each line is no longer determined. In addition, when the number of lines of each line in the recognizable command line is inconsistent with the number of lines of each line in the target command template, it is determined that the configuration integrity check of the recognizable command line has not passed.

[0041] For example, if the number of lines between the third line of the recognizable command line and the third line of the target command template is different, it is determined that the configuration integrity check of the recognizable command line has failed.

[0042] S105: Performing data correctness verification on the recognizable command line according to the business data.

[0043] In some embodiments of the present application, in order to prevent errors in business data during the process of converting business data into recognizable command lines, the business content of the specific configuration is verified.

[0044] Specifically, first, it is determined whether the key parameter content in the recognizable command line is consistent with the business content in the business data. If they are consistent, it is determined that the correctness check of the recognizable command line data has passed.

[0045] It should be noted that the key parameter content of the identifiable command line is obtained by converting the business content in the business data.

[0046] When the key parameter content in the identifiable command line is inconsistent with the business content in the business data, it is determined that the correctness check of the identifiable command line data has failed.

[0047] S106: Performing configuration conflict check on the recognizable command line according to historical configuration content.

[0048] In some embodiments of the present application, it is necessary to detect whether there is a conflict with an existing configuration, that is, whether the configuration has been issued.

[0049] Specifically, in the historical configuration content, it is searched whether there is a configuration record of the service type and the device type. If not, it is determined that the configuration conflict check of the recognizable command line has passed. If so, it is determined that the configuration conflict check of the recognizable command line has not passed.

[0050] S107: When the configuration integrity check, the data correctness check, and the configuration conflict check are all passed, the recognizable command line is configured and issued.

[0051] It should be noted that if any of the configuration integrity check, data correctness check and configuration conflict check fails, the configuration of the recognizable command line will no longer be issued, but a configuration issuance failure notification message will be generated and fed back to the user.

[0052] In some embodiments of the present application, in order to intuitively display the configuration pre-check results in a graphical manner, a managed device topology map is constructed.

[0053] Specifically, the verification results of configuration integrity check, data correctness check and configuration conflict check are generated. Then, the managed device topology map of the SDN controller is called. Finally, the verification results are displayed in the managed device topology map in a graphical manner.

[0054] Among them, when there is a failure in verification, the location of the managed device model corresponding to the device type is determined in the managed device topology map. Therefore, the reason for the failure of verification is displayed in the preset display area of ​​the managed device model location. Therefore, the failure information can be displayed at a specific location in the entire network topology map.

[0055] It can be seen that the location of the specific configuration conflict is displayed on the topology map in a graphical manner, which facilitates troubleshooting if a pre-check failure occurs.

[0056] Generally, in SDN scenarios, when the SDN controller sends configurations to hardware devices, it is necessary to ensure the correctness of the configurations to avoid errors in sending new configurations that affect service launches, and to avoid conflicts between new configurations and existing service configurations that affect existing services. Therefore, the SDN controller performs a pre-verification of the new configuration before sending it, and displays the verification results in a graphical manner to intuitively display problematic configurations to prevent problematic configurations from affecting network stability.

[0057] It should be noted that although the embodiments of the present application are based on Figure 1 Steps S101 to S107 are described in sequence, but this does not mean that steps S101 to S107 must be performed in a strict order. Figure 1 The order shown in the figure is to introduce and explain step S101 to step S107 in sequence, in order to facilitate those skilled in the art to understand the technical solution of the embodiment of the present application. In other words, in the embodiment of the present application, the order between step S101 to step S107 can be appropriately adjusted according to actual needs.

[0058] pass Figure 1 The method can verify the completeness of the business configuration through the constructed command template before the business configuration is issued, and identify incomplete recognizable command lines in advance. In addition, in combination with business data, the recognizable command lines are verified for data correctness, and recognizable command lines with conversion errors can be identified in advance. In addition, in combination with historical configuration content, configuration conflicts are verified for recognizable command lines, so as to identify in advance whether the business configuration is repeatedly issued, so as to comprehensively verify the configuration to be issued in advance through the three dimensions of configuration completeness, configuration data correctness, and existing configuration conflicts, effectively ensuring that the business configuration can be correctly issued to the hardware device, improving the effectiveness of configuration issuance, and avoiding network interruptions caused by configuration anomalies to the greatest extent, which is equivalent to providing an intuitive, fast and comprehensive configuration pre-verification result to avoid configuration errors or configuration conflicts from affecting the stability of the network.

[0059] Based on the same idea, some embodiments of the present application also provide devices and non-volatile computer storage media corresponding to the above methods.

[0060] Figure 2 A structural diagram of a configuration delivery verification device for an SDN controller provided in an embodiment of the present application includes:

[0061] at least one processor; and,

[0062] a memory communicatively connected to the at least one processor; wherein,

[0063] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute any one of the above-mentioned configuration delivery verification methods for the SDN controller.

[0064] Some embodiments of the present application provide a non-volatile computer storage medium for verifying configuration delivery of an SDN controller, storing computer executable instructions, wherein the computer executable instructions can execute any of the above-mentioned methods for verifying configuration delivery of an SDN controller.

[0065] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0066] The devices and media provided in the embodiments of the present application correspond one-to-one to the methods. Therefore, the devices and media also have similar beneficial technical effects as the corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

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

[0068] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0069] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0070] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

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

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

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

[0074] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0075] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the technical principle of the present application should all fall within the protection scope of the present application.

Claims

1. A configuration delivery verification method for an SDN controller, characterized in that: The method comprises: The SDN controller extracts the service type and device type from the service data; According to the service type and the device type, the service data is converted to generate a recognizable command line; In a command template database, the service type and the device type are matched to obtain a target command template; Performing configuration integrity verification on the recognizable command line according to the target command template; According to the business data, performing data correctness verification on the recognizable command line; Performing configuration conflict check on the recognizable command line according to historical configuration content; When the configuration integrity check, the data correctness check, and the configuration conflict check are all passed, the recognizable command line is configured and issued.

2. The method according to claim 1, characterized in that The performing configuration integrity check on the recognizable command line according to the target command template specifically includes: Determine whether the total number of lines of the recognizable command line is consistent with the total number of lines of the target command template; If they are consistent, then determine in turn whether the number of lines in each line of the recognizable command line is consistent with the number of lines in each line of the target command template; If they are consistent, it is determined that the configuration integrity check of the recognizable command line has passed.

3. The method according to claim 1, characterized in that The performing data correctness verification on the recognizable command line according to the business data specifically includes: Determining whether the key parameter content in the recognizable command line is consistent with the business content in the business data; If they are consistent, it is determined that the data correctness check of the recognizable command line has passed.

4. The method according to claim 1, characterized in that: The performing configuration conflict check on the recognizable command line according to the historical configuration content specifically includes: In the historical configuration content, searching whether there is a configuration record of the business type and the device type; If not, it is determined that the configuration conflict check of the recognizable command line passes.

5. The method according to claim 1, characterized in that: The method further comprises: Generate verification results for configuration integrity, data correctness, and configuration conflict; Calling the managed device topology of the SDN controller; The verification result is displayed graphically in the managed device topology diagram.

6. The method according to claim 5, characterized in that The method further comprises: If the verification fails, the location of the managed device model corresponding to the device type is determined in the managed device topology map; The reason why the verification failed is displayed in the preset display area of ​​the managed device model location.

7. The method according to claim 1, characterized in that Before matching the service type and the device type in the command template database to obtain the target command template, the method further includes: Obtain sample business types and sample device types, and construct sample command templates for the sample business types and sample device types; Establishing a mapping relationship between the sample service type and the sample device type and the sample command template; The sample command template is output to a command template database, and in the command template database, the mapping relationship is associated with the sample command template.

8. The method according to claim 1, characterized in that The SDN controller extracts the service type and device type from the service data, specifically including: The SDN controller obtains service data through the display interface; According to the preset writing rule of the business data, the business type is extracted from the data position of the business type, and the device type is extracted from the data position of the device type.

9. A configuration delivery verification device for an SDN controller, characterized in that: include: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the configuration delivery verification method for the SDN controller described in any one of claims 1 to 8.

10. A non-volatile computer storage medium for verifying the configuration of an SDN controller, storing computer executable instructions, characterized in that: The computer executable instructions can execute a configuration delivery verification method for an SDN controller as described in any one of claims 1 to 8.

Images