Method for automatically deploying network element data plane

Abstract

The invention provides a method for automatically deploying a network element data surface, relates to the technical field of automatic operation and maintenance, and aims to solve the problems that the deployment steps of an existing cloud computing network element server data surface are complicated, and the deployment time is long in a scene with a large number of network elements. The method comprises the following steps: compiling a deployment instruction according to a deployment task; acquiring information of each network element server in the cluster from the configuration file, and establishing target connection with each network element server according to the information; and generating a temporary deployment script according to the deployment instruction, and sending the temporary deployment script to each network element server in a cluster through the target connection, so that the network element server executes the temporary deployment script to realize configuration deployment, and the temporary deployment script is used for realizing a function corresponding to the deployment task.

Description

Technical Field

[0001] The present application relates to the field of automated operation and maintenance technology, and in particular to a method for automatically deploying network element data planes. Background Art

[0002] At present, the cloud computing service industry is developing more and more rapidly, and the demand for network element servers that provide essential underlying network forwarding services for cloud computing is also increasing. In order for network element servers to provide customized network forwarding services, the services need to be deployed on the network element servers.

[0003] Currently, most of the deployment of network element servers still relies on manual deployment of multiple instructions and multiple network elements one by one. The deployment process is cumbersome and complicated, with a high rate of manual intervention. It is very easy to make mistakes when writing configurations and executing numerous deployment instructions. In addition, it is necessary to log in to the network element servers one by one for deployment. For scenarios with a large number of network element servers in a cluster, the deployment time cost is huge, and because of manual deployment one by one, the error rate of operation is also greatly increased.

[0004] Therefore, the existing cloud computing network element server data plane deployment steps are complicated and the deployment takes a long time in scenarios with a large number of network elements. Summary of the invention

[0005] In view of the above problems, an embodiment of the present application provides a method for automatically deploying a network data plane, so as to overcome the above problems or at least partially solve the above problems.

[0006] In a first aspect of an embodiment of the present application, a method for automatically deploying a network element plane is disclosed, which is applied to deploy a server, and the method includes: Write deployment instructions based on deployment tasks; Obtain information of each network element server in the cluster from the configuration file, and establish a target connection with each network element server according to the information; A temporary deployment script is generated according to the deployment instruction, and the temporary deployment script is sent to each network element server under the cluster through the target connection, so that the network element server executes the temporary deployment script to implement configuration deployment. The temporary deployment script is used to implement the function corresponding to the deployment task.

[0007] Optionally, the deployment task includes automatic configuration generation, pre-deployment check, network element system initialization, data plane service deployment, and post-deployment check; and writing deployment instructions according to the deployment task includes: Encapsulate different deployment tasks into scripts, including: automatic generation of configuration scripts, pre-deployment check scripts, network element system initialization scripts, data plane service deployment scripts, and post-deployment check scripts; The scripts are assembled into deployment instructions in the order in which they are executed.

[0008] Optionally, generating a temporary deployment script according to the deployment instruction includes: Run the deployment instruction to determine the target deployment task; According to the target deployment task, the corresponding script is called to generate a temporary deployment script.

[0009] Optionally, when the deployment task is to automatically generate configuration, different deployment tasks are encapsulated as scripts, including: Generate a configuration file in a target format according to a network planning file, wherein the network planning file includes relevant network configuration information of a network element; The configuration file is packaged into an automatic configuration script.

[0010] Optionally, when the deployment task is a pre-deployment check, different deployment tasks are encapsulated as scripts, including: The function of checking whether the actual configuration of the current network element server meets the requirements of integrated deployment is encapsulated as the first pre-deployment check script; The function of comparing and checking conflicts between the configuration generated by the automatic configuration generation and the actual configuration of the current network element server is encapsulated as a second pre-deployment check script; A pre-deployment check script is obtained according to the first pre-deployment check script and the second pre-deployment check script.

[0011] Optionally, when the deployment task is network element system initialization, different deployment tasks are encapsulated into scripts, including: Integrate the system initialization function of the network element server into the network element system initialization script; Among them, the system initialization function includes a first configuration function, a second configuration function, a third configuration function, and a fourth configuration function; the first configuration function is used to download and install dependencies, drivers, kernels and data plane service programs from the target source; the second configuration function is used to install dependency tools through the target source; the third configuration function is used to upgrade and downgrade the kernel and driver of the network element server when the kernel and driver versions of the network element server do not meet the requirements; the fourth configuration function is used to specify the allocated large page memory size and number of pages in the startup script of the network element server.

[0012] Optionally, when the deployment task is data plane service deployment, different deployment tasks are encapsulated into scripts, including: Integrate data plane service functions into data plane service scripts; Among them, the data plane service function includes a first service function, a second service function, and a third service function; the first service function is used to download and install the service program through the target source; the second service function is used to read the configuration file generated by the automatic generation configuration, and generate a configuration for program operation on the network element server; the third service function is used to start the service program after the service program is installed and configured.

[0013] Optionally, when the deployment task is a post-deployment check task, different deployment tasks are encapsulated as scripts, including: Integrate the post-deployment check functionality into a post-deployment check playbook; Among them, the post-deployment inspection function includes: a first inspection service, a second inspection service, a third inspection service, a fourth inspection service, and a fifth inspection service; the first inspection service is used to check whether the program is running normally; the second inspection service is used to check whether the version of the data plane program running after deployment is consistent with the version in the deployment configuration; the third inspection service is used to check the connectivity between the internal and external network network cards to the gateway; the fourth inspection service is used to check whether the connection with the switch neighbor is normal; the fifth inspection service is used to check whether the network element has completed the reconciliation and synchronization with the control plane configuration.

[0014] Optionally, the method further comprises: Receiving an execution result of the temporary deployment script returned from the network element server; Delete the temporary deployment script.

[0015] A second aspect of the embodiment of the present application discloses a method for automatically deploying a network element data plane, which is applied to a network element server, and the method includes: Receiving a temporary deployment script from a deployment server, wherein the temporary deployment script is generated by the deployment server according to a deployment instruction, and the temporary deployment script is used to implement a function corresponding to the deployment task; Execute the temporary deployment script to implement configuration deployment.

[0016] In a third aspect of an embodiment of the present application, a device for automatically deploying a network element plane is disclosed, which is applied to a deployment server, and the device includes: A writing module, used to write deployment instructions according to deployment tasks, wherein the deployment tasks include: automatic configuration generation, pre-deployment check, network element system initialization, data plane service deployment, and post-deployment check; A connection module, used to obtain information of each network element server in the cluster from a configuration file, and establish a target connection with each network element server according to the information; A generation module is used to generate a temporary deployment script according to the deployment instruction, and send the temporary deployment script to each network element server under the cluster through the target connection, so that the network element server executes the temporary deployment script to implement configuration deployment. The temporary deployment script is used to implement the function corresponding to the deployment task.

[0017] In a fourth aspect of the embodiments of the present application, a device for automatically deploying a network element data plane is disclosed, which is applied to a network element server, and the device includes: A receiving module, used to receive a temporary deployment script from a deployment server, wherein the temporary deployment script is generated by the deployment server according to a deployment instruction, and the temporary deployment script is used to implement a function corresponding to the deployment task; The execution module is used to execute the temporary deployment script to implement configuration deployment.

[0018] According to a fifth aspect of an embodiment of the present application, an electronic device is disclosed, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps of the method for automatically deploying network element data planes described in the first aspect of the embodiment of the present application are implemented, or the steps of the method for automatically deploying network element data planes described in the second aspect of the embodiment of the present application are implemented.

[0019] The fourth aspect of the embodiments of the present application discloses a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the method for automatically deploying network element data planes described in the first aspect of the embodiments of the present application are implemented, or the steps of the method for automatically deploying network element data planes described in the second aspect of the embodiments of the present application are implemented.

[0020] The fifth aspect of the embodiments of the present application discloses a computer program product, including a computer program, which, when executed by a processor, implements the steps of the method for automatically deploying network data planes described in the first aspect of the embodiments of the present application, or the steps of the method for automatically deploying network data planes described in the second aspect of the embodiments of the present application.

[0021] The embodiments of the present application include the following advantages: In the embodiment of the present application, deployment instructions are written according to deployment tasks; information of each network element server under the cluster is obtained from the configuration file, and a target connection is established with each network element server according to the information; a temporary deployment script is generated according to the deployment instruction, and the temporary deployment script is sent to each network element server under the cluster through the target connection, so that the network element server executes the temporary deployment script to implement configuration deployment. In this way, all deployment tasks are integrated into deployment instructions, and one-click automatic deployment of the network element server is completed through one deployment instruction, without the need to execute cumbersome and complex deployment processes, solving the problem of complex data plane deployment steps of the current cloud computing network element server; and multiple network element servers in the cluster can be deployed at the same time, saving deployment time, and solving the problem of long deployment time for each network element server when there are a large number of network element servers under the cluster. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments of the present application 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 drawings can be obtained based on these drawings without paying any creative labor.

[0023] Figure 1 It is a structural diagram of a system for automatically deploying network data planes provided in an embodiment of the present application; Figure 2 It is a flowchart of the steps of a method for automatically deploying network element data planes applied to a deployment server provided in an embodiment of the present application; Figure 3 It is a flowchart of the steps of a method for automatically deploying network element data plane applied to a network element server provided in an embodiment of the present application; Figure 4 It is a flowchart of the steps of a method for automatically deploying network data plane provided by an embodiment of the present application; Figure 5 It is a deployment flow chart of a network element server provided in an embodiment of the present application; Figure 6 It is a structural diagram of another system for automatically deploying network data planes provided in an embodiment of the present application; Figure 7 It is a structural diagram of a device for automatically deploying network element data planes for deploying a server provided in an embodiment of the present application; Figure 8 It is a structural diagram of a device for automatically deploying network element data plane applied to a network element server provided in an embodiment of the present application; Fig. 9It is a structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0024] In order to make the above-mentioned purposes, features and advantages of the present application more obvious and understandable, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0025] In order to better understand the technical solution of the present application, the technical possibilities involved in the present application are explained.

[0026] Ansible: An automated operation and maintenance tool developed based on Python. It combines the advantages of many operation and maintenance tools (puppet, chef, func, fabric), and realizes functions such as batch system configuration, batch program deployment, and batch command execution.

[0027] Yum (Yellow dog Updater, Modified): is a Shell front-end package manager in Fedora, RedHat and CentOS. Based on RPM package management, it can automatically download RPM packages from a specified server and install them. It can automatically handle dependency relationships and install all dependent packages at once without the tedious downloading and installation again and again.

[0028] Numa (Non-Uniform Memory Access): is a computer architecture that allows multiple processors to access the system's physical memory through shared memory, but different memory areas may be processed by different processors. This memory access method is called "non-uniform memory access". In this architecture, each processor has its own local memory, but they can access the memory of other processors. This architecture can improve the performance of multi-processor systems and make the system more scalable.

[0029] In the related technologies, the deployment of network element servers mostly still remains at the stage of manual deployment of multiple instructions and multiple network elements one by one. The deployment process is cumbersome and complicated, with a high rate of manual intervention. It is very easy to make mistakes when writing configurations and executing numerous deployment instructions. In addition, it is necessary to log in to the network element servers one by one for deployment. For scenarios with a large number of network element servers in a cluster, the deployment time cost is huge, and because it is manually deployed one by one, the operation error rate is also greatly increased.

[0030] In addition, the deployment environment of the network element server is not automatically initialized. During the deployment process, many problems will occur in which the network element server does not meet the deployment requirements. For example, the required installation package cannot be downloaded from the yum source, dependent tools are missing, the system kernel or driver version is too low, the network card model, CPU and NUMA number do not meet the deployment requirements, and the data plane program cannot allocate memory. These problems need to be manually solved before or during deployment; and the inspection mechanism is not integrated into the deployment system. During the deployment process, the network element server often fails to meet the deployment integration requirements, or the data plane program cannot run normally after the deployment is completed.

[0031] Therefore, the existing deployment methods mainly have the following four problems: 1) The operation steps are complicated, and multiple instructions need to be executed in multiple steps to complete the deployment of the service, which is not user-friendly; 2) Since the deployment is carried out one by one on each network element, the deployment time is long for scenarios with a large number of network element servers, and the more network elements there are, the more time it takes; 3) Since the network element server is not automatically initialized before deployment, the network element server does not meet the deployment or data plane program running conditions, resulting in deployment failure or network element data plane service problems, or the network element server is manually initialized before deployment, the operation is complicated and prone to errors; 4) It is impossible to detect whether the deployment configuration conflicts and whether the network element server meets the deployment requirements before deployment, resulting in deployment failure or abnormal program or service operation after deployment, and the data plane program and service operation status cannot be discovered in time after deployment, and need to be checked separately through other methods or scripts.

[0032] In order to overcome the limitations of related technologies, an embodiment of the present application provides a method for automatically deploying network element data planes. The method integrates deployment tasks into a deployment instruction, and completes one-click automatic deployment of network element servers by executing the deployment instruction, thereby greatly reducing the deployment complexity, enhancing the ease of deployment, and solving the problem of complex data plane deployment steps of current cloud computing network element servers; and multiple network element servers in a cluster can be deployed at the same time, and the time spent on deploying multiple network elements is basically equivalent to the time spent on deploying one network element, which greatly saves deployment time.

[0033] The following describes a method for automatically deploying network data planes according to an embodiment of the present application in conjunction with the accompanying drawings.

[0034] Reference Figure 1 As shown, Figure 1This is a structural diagram of a system for automatically deploying network element data planes provided by an embodiment of the present application. Specifically, the system includes a deployment server and a cluster including multiple network element servers. Ansible is deployed on the deployment server. Ansible is a very lightweight operation and maintenance tool. Only one deployment server is needed to establish target connections with multiple other network element servers at the same time, and deploy each network element server according to the written deployment instructions. Based on this one-to-many concurrent deployment mode, for scenarios with a large number of network element servers in the cluster, it can greatly save deployment time and avoid the problem of easy operational errors in manual deployment of each server.

[0035] The embodiment of the present application provides a method for automatically deploying network data plane, which is applied to deploying a server. Figure 2 As shown, Figure 2 1 is a flowchart of a method for automatically deploying network element data planes for deploying a server provided in an embodiment of the present application. Figure 2 As shown, the method for automatically deploying network data plane may include steps S210 to S230: Step S210: Compile deployment instructions according to the deployment task.

[0036] Step S220: Acquire information of each network element server in the cluster from the configuration file, and establish a target connection with each network element server according to the information.

[0037] Step S230: Generate a temporary deployment script according to the deployment instruction, and send the temporary deployment script to each network element server under the cluster through the target connection, so that the network element server executes the temporary deployment script to implement configuration deployment. The temporary deployment script is used to implement the function corresponding to the deployment task.

[0038] In the embodiment of the present application, the deployment task refers to the tasks related to the deployment of the network element server, such as the initialization of the network element system. The deployment tasks are aggregated into one deployment instruction. In this way, there is no need to execute numerous and complex deployment instructions or scripts. The network element server can be deployed by executing the deployment execution. There is no need to execute tedious and complex deployment processes. The operability and user-friendliness are greatly improved, and the ease of use is high.

[0039] Before deploying the network element server, firstly, based on obtaining the information of each network element server in the cluster from the configuration file, a target connection between the deployment server and each network element server is established. In some embodiments, the information of each network element server in the cluster can be a cluster host IP list (i.e., a list of network element servers in the cluster) and corresponding SSH account information. The configuration file is read by the ansible program to obtain the cluster host IP list and the corresponding SSH account information, and then an SSH connection (i.e., a target connection) is established with all network element servers in the cluster based on the information.

[0040] After establishing a target connection with each network element server, execute the deployment instruction to generate a temporary deployment script, and send the temporary deployment script to each network element server under the cluster through the target connection. The temporary deployment script is used to implement the function corresponding to the deployment task, so the network element server can implement the corresponding deployment by executing the temporary deployment script.

[0041] By adopting the technical solution of the embodiment of the present application, all deployment tasks are integrated into deployment instructions, and one-click automatic deployment of the network element server is completed through a deployment instruction. There is no need to execute cumbersome and complicated deployment processes, which solves the problem of complex data plane deployment steps of current cloud computing network element servers; and multiple network element servers in the cluster can be deployed at the same time, saving deployment time and solving the problem of time-consuming deployment of each network element server when there are a large number of network element servers in the cluster.

[0042] In combination with the above embodiments, in one implementation, the embodiment of the present application further provides a method for automatically deploying network element data planes. In this method, the deployment tasks include automatically generating configurations, pre-deployment checks, network element system initialization, data plane service deployment, and post-deployment checks; the above step S110 "writing deployment instructions according to deployment tasks" specifically includes the following steps S110-1 to S110-2: Step S110-1: Encapsulate different deployment tasks into scripts, which include: automatically generated configuration scripts, pre-deployment check scripts, network element system initialization scripts, data plane service deployment scripts, and post-deployment check scripts.

[0043] Step S110 - 2 : According to the execution order of the scripts, the scripts are assembled into deployment instructions.

[0044] In the embodiment of the present application, automatically generating configuration refers to automatically generating relevant configuration information required by the network element server; pre-deployment check refers to checking the actual configuration of the network element server and the relevant configuration information generated by the automatically generated configuration before deploying the network element server, so as to find out whether the deployment configuration conflicts and whether the network element server meets the deployment requirements; network element system initialization refers to automatically initializing the network element server before deployment, so as to avoid the network element server not meeting the deployment or data plane program running conditions, resulting in deployment failure or network element data plane business problems; data plane service deployment refers to the deployment of network element server-based services and programs; post-deployment check refers to the necessary inspection of data plane services after the network element server deployment is completed, so as to prevent abnormal operation of data plane service programs or businesses.

[0045] Different deployment tasks can be encapsulated into corresponding scripts through the target script mode and syntax, and each script can be executed in sequence through commands according to the execution order of the script to realize the deployment function of each deployment task and integrate them into a deployment instruction, where the execution order of the script is: automatic generation of configuration script, pre-deployment check script, network element system initialization script, data plane service deployment script, and post-deployment check script. For example, different deployment tasks can be encapsulated into corresponding scripts based on the script mode and syntax of Ansible, and then the five scripts can be executed in sequence through shell scripts through shell commands to realize the deployment function of the five deployment tasks and integrate them into a shell deployment instruction.

[0046] By adopting the technical solution of the embodiment of the present application, different deployment tasks are compiled into one deployment instruction, and one-click automatic deployment such as network element server system initialization, service installation, service configuration, service startup, and service inspection can be completed by executing one deployment instruction; because the tasks such as network element system initialization and post-deployment inspection are integrated into the deployment instruction, the problems such as the network element server not meeting the deployment integration requirements and the lack of a deployment inspection mechanism are solved; and the network element system initialization script in the deployment instruction ensures compatibility with deployment of different kernels, driver versions and other models, and ensures the compatibility and versatility of the deployment system. In this way, there is no need to manually fill in and check the configuration, check the program operation status and business operation status, and execute tedious deployment steps, so that rapid deployment can be achieved and the deployment effect is better.

[0047] In combination with the above embodiments, in one implementation, the present application embodiment further provides a method for automatically deploying network element data planes. In this method, the "generating a temporary deployment script according to the deployment instruction" in the above step S130 specifically includes the following steps S130-1 to S130-2: Step S130 - 2 : Execute the deployment instruction to determine the target deployment task.

[0048] Step S130-2: According to the target deployment task, call the corresponding script to generate a temporary deployment script.

[0049] In an embodiment of the present application, different target deployment tasks correspond to different temporary deployment scripts. The deployment instructions bring together different deployment tasks. The target deployment tasks that need to be executed are determined based on the current running progress, and then a temporary deployment script is generated by calling the corresponding script.

[0050] For example, when the deployment instruction runs to the stage of executing the pre-deployment check, the pre-deployment check script is called to generate a corresponding temporary deployment script, and the temporary deployment script is sent to the network element server so that the network element server can perform the pre-deployment check; when the deployment instruction runs to the stage of executing the network element system initialization, the network element system initialization script is called to generate a corresponding temporary deployment script, and the temporary deployment script is sent to the network element server so that the network element server can perform the network element system initialization.

[0051] By adopting the technical solution of the embodiment of the present application, by running the deployment instruction, a temporary deployment script corresponding to each deployment task is automatically generated, so that the network element server can implement the corresponding deployment based on the temporary deployment script. In this way, the user only needs to execute the deployment instruction to complete the entire deployment with one click, without having to execute a cumbersome and complicated deployment process, which greatly improves operability and user-friendliness, and is easy to use.

[0052] In combination with the above embodiments, in one implementation, the present application embodiment further provides a method for automatically deploying network data plane. In this method, in addition to the above steps, the following steps are also included: Step S140: receiving the execution result of the temporary deployment script returned from the network element server.

[0053] Step S150: Delete the temporary deployment script.

[0054] In the embodiment of the present application, the temporary deployment script can be sent to multiple network element servers under the cluster for deployment at the same time. After executing the temporary deployment script, the network element server will feedback the execution result of the temporary deployment script to the deployment server, so that the deployment server deletes the temporary deployment script, avoiding the temporary deployment script that has been executed occupying memory resources; and the deployment server can clearly see the deployment status of each network element server according to the execution result. Compared with the complex deployment process with multiple instructions and the method of logging in to the network element one by one for deployment, it can greatly improve the deployment efficiency, shorten the deployment time, and has high efficiency.

[0055] The following describes how to encapsulate different deployment tasks into scripts.

[0056] In an optional example, when the deployment task is to automatically generate a configuration, different deployment tasks are encapsulated into scripts, including: generating a configuration file in a target format based on a network planning file, wherein the network planning file includes relevant network configuration information of the network element; and encapsulating the configuration file into an automatically generated configuration script.

[0057] In the embodiment of the present application, the network planning file can be in json format, and the configuration file can be in yml format. Specifically, according to the network planning file, a configuration file in a target format is generated, and a python script can automatically parse the network planning file, and then generate a yml format configuration file that can be read by Ansible according to the parsing result, and integrate it into the automatic generation of configuration scripts for Ansible.

[0058] In this way, when performing automated deployment later, you can directly call the automatically generated configuration script, eliminating the steps of manually filling in the deployment configuration, improving ease of use and deployment efficiency.

[0059] In an optional example, when the deployment task is a pre-deployment check, different deployment tasks are encapsulated into scripts, including: the function of checking whether the actual configuration of the current network element server meets the integrated deployment requirements is encapsulated as a first pre-deployment check script; the function of comparing and conflict checking the configuration generated by the automatically generated configuration with the actual configuration of the current network element server is encapsulated as a second pre-deployment check script; and the pre-deployment check script is obtained according to the first pre-deployment check script and the second pre-deployment check script.

[0060] In an embodiment of the present application, the pre-deployment check is encapsulated into two scripts. The first pre-deployment check script can be implemented by using a shell script. The function of checking whether the actual configuration of the current network element server meets the requirements of the integrated deployment is encapsulated as the first pre-deployment check script; wherein, whether the actual configuration of the current network element server meets the requirements of the integrated deployment includes: the operating system kernel version, the number of NUMAs of the CPU, whether hyperthreading is turned off, the network card name, the internal and external network network card binding NUMA, the network card model and transmission rate, the server network management service, etc., whether they meet the requirements of the integrated deployment specifications.

[0061] The second pre-deployment check script can be implemented using a python script to compare and conflict the configuration generated by the automatically generated configuration with the actual configuration of the current network element server; for example, check whether the configuration automatically generated by the network planning file, such as IP, cluster information, etc., conflicts with the actual configuration of the current network element server.

[0062] In this way, before deployment, it is possible to automatically check whether the configuration of the network element server meets the specified requirements, and whether the planned configuration conflicts with the actual configuration of the current network element server, to prevent the impact of service interruption caused by deployment with incorrect configuration. For example, in the expansion scenario, deploying the expansion network element with incorrect configuration may cause abnormal service of the original network element in the existing network and cause failure. It also avoids the tediousness and unreliability of manual inspection, and improves the reliability and usability of the deployment system.

[0063] In an optional time example, when the deployment task is network element system initialization, different deployment tasks are encapsulated into scripts, including: integrating the system initialization function of the network element server into a network element system initialization script; Among them, the system initialization function includes a first configuration function, a second configuration function, a third configuration function, and a fourth configuration function; the first configuration function is used to download and install dependencies, drivers, kernels and data plane service programs from the target source; the second configuration function is used to install dependency tools through the target source; the third configuration function is used to upgrade and downgrade the kernel and driver of the network element server when the kernel and driver versions of the network element server do not meet the requirements; the fourth configuration function is used to specify the allocated large page memory size and number of pages in the startup script of the network element server.

[0064] Specifically, the system initialization function of the network element server can be implemented using shell scripts and integrated into a network element system initialization script (i.e., a script that can be called by Ansible). The first configuration function refers to configuring the repo file yum source, and then downloading and installing dependencies, drivers, kernels, and data plane service programs from the target source (e.g., yum source).

[0065] The second configuration function is to install dependency tools, which are installed through yum. Some necessary dependency tools are installed. The necessary dependency tools can be tools related to network services, necessary tools that data plane programs depend on for running, etc.

[0066] The third configuration function refers to upgrading and upgrading the kernel and driver. When the kernel and driver versions of the network element server do not meet the requirements, the kernel and driver are upgraded to meet the requirements. Upgrading the kernel uses yum to install the required kernel version and dependencies, and sets the kernel startup sequence in the startup file to start the system according to the required kernel version. Upgrading the driver will first uninstall the original driver and then install the specified version of the driver.

[0067] The fourth configuration function is to configure large page memory. By specifying the allocated large page memory size and number of pages in the system startup script, the system allocates and executes large page memory according to the startup script after startup, so that the data plane service program can obtain and use memory from the allocated large page memory.

[0068] In the embodiment of the present application, the network element system initialization script is automatically executed through a script before the data plane service program is deployed, and the network element server environment is initialized so that the network element server meets the deployment and data plane program running requirements, thereby preventing errors in the deployment or operation of the data plane service program due to the server environment not meeting the requirements, thereby improving the deployment compatibility of network element machines with different system kernels and driver versions, and preventing high-risk operations such as manual upgrades and downgrades of the kernel, network card driver, and configuration of large pages to modify the system configuration, which may cause system crashes and network card loss of connection, thereby improving the security and ease of use of the deployed system.

[0069] In an optional time example, when the deployment task is data plane service deployment, different deployment tasks are encapsulated into scripts, including: integrating data plane service functions into a data plane service script; Among them, the data plane service function includes a first service function, a second service function, and a third service function; the first service function is used to download and install the service program through the target source; the second service function is used to read the configuration file generated by the automatic generation configuration, and generate a configuration for program operation on the network element server; the third service function is used to start the service program after the service program is installed and configured.

[0070] Specifically, you can use ansible's yml script, j2 template script, and shell script to integrate the data plane service functions into a data plane service script for automated deployment and calling. The first service function refers to the installation of the service program. The service program can be downloaded and installed through the target source (for example, the yum source). Specifically, it can be installed according to the program version in the configuration file, or a specific service version can be specified for installation through the command line. The second service function refers to service configuration, which is to read the automatically generated configuration file and generate the configuration for program operation on the network element server. The third service function refers to service startup, which is to start the service program after the service program is installed and configured.

[0071] In the embodiment of the present application, it is only necessary to automatically install the data plane service program according to the deployment configuration, generate the corresponding configuration, and start the data plane program to implement the data plane service deployment. In addition, the concurrent deployment mechanism of Ansible can be used to install and deploy multiple network element servers at the same time, eliminating the tedious and error-prone problems of manually deploying network elements one by one, and achieving efficient deployment.

[0072] In an optional example, when the deployment task is a post-deployment check task, different deployment tasks are encapsulated into scripts, including: integrating the post-deployment check function into a post-deployment check script, Among them, the post-deployment inspection function includes: a first inspection service, a second inspection service, a third inspection service, a fourth inspection service, and a fifth inspection service; the first inspection service is used to check whether the program is running normally; the second inspection service is used to check whether the version of the data plane program running after deployment is consistent with the version in the deployment configuration; the third inspection service is used to check the connectivity between the internal and external network network cards to the gateway; the fourth inspection service is used to check whether the connection with the switch neighbor is normal; the fifth inspection service is used to check whether the network element has completed the reconciliation and synchronization with the control plane configuration.

[0073] Specifically, shell and python scripts can be used to implement the post-deployment check function, integrating it into a post-deployment check script (i.e., ansible script). The first service check refers to checking the running status of the service program process, for example, the process running time, whether a coredump file is generated, etc. The second service check refers to checking the program version, by checking whether the version of the data plane program running after deployment is consistent with the version in the deployment configuration, to prevent deployment of other versions. The third service check refers to checking the connectivity of the network card, checking the connectivity of the internal and external network network cards to the gateway, which can be achieved through ping to ensure that the network card is connected. The fourth service check refers to checking the BGP neighbor connection, that is, checking whether the connection with the switch neighbor is normal. The fifth service check refers to checking configuration synchronization, that is, checking whether the network element has completed the reconciliation and synchronization with the control plane configuration to ensure that the configuration issued by the control plane has been synchronized to the data plane program.

[0074] In the embodiment of the present application, the post-deployment check script automatically performs necessary checks on the data plane service after deployment to prevent abnormal operation of the data plane service program or business, thereby eliminating tedious manual inspection steps and improving deployment efficiency and reliability.

[0075] The embodiment of the present application provides a method for automatically deploying a network element data plane, and the method is applied to a network element server. Figure 3 As shown, Figure 3 1 is a flowchart of a method for automatically deploying network element data planes applied to a network element server provided in an embodiment of the present application. Figure 3 As shown, the method for automatically deploying network data plane may include steps S310 to S320: Step S310: receiving a temporary deployment script from a deployment server, wherein the temporary deployment script is generated by the deployment server according to a deployment instruction, and the temporary deployment script is used to implement a function corresponding to a deployment task.

[0076] Step S320: Execute the temporary deployment script to implement configuration deployment.

[0077] In an embodiment of the present application, the network element server under the cluster implements the corresponding deployment by executing a temporary deployment script. The temporary deployment script may be a temporary deployment script generated by calling an automatically generated configuration script, a pre-deployment check script, a network element system initialization script, a data plane service deployment script, and a post-deployment check script. In this way, automated deployment can be achieved by continuously receiving temporary deployment scripts from the deployment server and executing the temporary deployment script.

[0078] Specifically, after executing the temporary deployment script, the network element server will feed back the execution result of each temporary deployment script to the deployment server, so that the deployment server deletes the temporary deployment script, thereby avoiding the temporary deployment script that has been executed occupying memory resources, and each deployment server can clearly know the deployment status of each network element server based on the execution result.

[0079] By adopting the technical solution of the embodiment of the present application, all deployment tasks are integrated into deployment instructions, and one-click automatic deployment of the network element server is completed through one deployment instruction. There is no need to execute cumbersome and complicated deployment processes, which solves the problem of complex data plane deployment steps of current cloud computing network element servers; and multiple network element servers in the cluster can be deployed at the same time, saving deployment time and solving the problem of time-consuming deployment of each server when there are a large number of network element servers in the cluster; because tasks such as network element system initialization and post-deployment inspection are integrated into the deployment instructions, the problems of network element servers not meeting deployment integration requirements and lacking a deployment inspection mechanism are solved, and a better deployment effect is achieved.

[0080] The following is a specific embodiment to illustrate the method for automatically deploying network data plane provided by the present application. Figure 4 As shown, Figure 4 4 is a flowchart of a method for automatically deploying a network element data plane provided by an embodiment of the present application. Specifically, the method includes the following steps S410 to S460: Step S410: The deployment server encapsulates different deployment tasks into scripts; and collects the scripts into deployment instructions in the order of script execution. The scripts include: automatically generated configuration scripts, pre-deployment check scripts, network element system initialization scripts, data plane service deployment scripts, and post-deployment check scripts.

[0081] Step S420: the deployment server obtains information of each network element server in the cluster from the configuration file, and establishes a target connection with each network element server according to the information.

[0082] Step S430: The deployment server runs the deployment instruction to determine the target deployment task; based on the target deployment task, the corresponding script is called to generate a temporary deployment script.

[0083] Step S440: The deployment server sends the temporary deployment script to each network element server in the cluster through the target connection.

[0084] Step S450: the network element server receives the temporary deployment script from the deployment server, executes the temporary deployment script, and feeds back the execution result of the temporary deployment script to the deployment server.

[0085] Step S460: The deployment server receives the execution result of the temporary deployment script and deletes the temporary deployment script.

[0086] In the embodiment of the present application, based on the script mode of Ansible, the deployment tasks such as automatic configuration generation, pre-deployment check, network element system initialization, data plane service deployment, and post-deployment check are written as Ansible scripts and integrated into one deployment instruction. In this way, users do not need to execute numerous and complex deployment instructions or scripts. They can easily complete the deployment by executing one instruction. There is no need to execute tedious and complex deployment processes. The operability and user-friendliness are greatly improved, and the ease of use is high.

[0087] Moreover, thanks to the concurrent execution mechanism of Ansible, all network element servers in the cluster can be deployed concurrently at the same time, and the deployment status of each network element server can be clearly known based on the return results of Ansible execution. Compared with the complex deployment process of multiple instructions and the method of logging in to the network element server one by one for deployment, it can greatly improve the deployment efficiency, shorten the deployment time, and is highly efficient.

[0088] Before deployment, the NE server environment will be initialized to ensure that the NE yum source configuration, kernel, driver, large page memory, dependency tools, etc. meet the conditions for NE data plane program deployment and operation. Even if a machine with a kernel, driver, large page, etc. that does not meet the conditions is encountered, it can be deployed normally, which improves the compatibility and versatility of the deployment system.

[0089] Before deployment, the actual configuration of the network element server will be checked to see if it meets the integrated deployment specifications, and a conflict check will be performed between the deployed configuration and the actual configuration of the current network element server. It is possible to detect in advance whether the network element server is non-standard and whether there is a conflict in the configuration, thereby avoiding abnormal operation of the network element server program and services after deployment. Expansion scenarios may cause failures that affect the existing network element server services. After deployment, the operation of the data plane program and related services on the network element server will be checked to prevent abnormal network element services and services after deployment, ensuring that the network element data plane program is correctly deployed with high reliability. In addition, after deployment, necessary checks are automatically performed on the data plane service to prevent abnormal operation of the data plane service program or service, eliminating tedious manual inspection steps, improving deployment efficiency and reliability, and thereby ensuring that the network element server meets the deployment and data plane program operation conditions before the data plane service is deployed, and that the data plane service program and services run normally after deployment.

[0090] parameter Figure 5 As shown, Figure 5 It is a deployment flow chart of a network element server provided in an embodiment of the present application. Based on the execution order of the script, the network element server performs the following deployments in sequence: configure the repo file yum source, check and configure the network element, install dependent tools, upgrade and downgrade the kernel and driver, configure large page memory, install the data plane service program, configure and start the data plane program, check the operation status of the service program process, and check the business status, and finally complete the deployment of the network element server.

[0091] In conjunction with a system for automatically deploying network element data planes, the following describes an execution process of the method for automatically deploying network element data planes in an embodiment of the present application in the system.

[0092] Reference Figure 6 As shown, Figure 6 It is a structural diagram of another system for automatically deploying network element data planes provided in an embodiment of the present application. Specifically, the system includes a deployment server (i.e., a control node Control-Node, a DPOS control node) and a cluster consisting of multiple network element servers (Host-Node), each network element server includes multiple hosts (GroupHost), Ansible is deployed on the deployment server, as well as DPOS tools-script (i.e., a tool script for the network element node), Host&Ansible-cfg (i.e., Ansible-cfg system configuration and Host host configuration file).

[0093] When executing deployment instructions for automated deployment, Ansible reads the configuration file Config (including template configuration and host interface configuration) through the automated script (‌Playbook) used to configure, deploy and manage controlled nodes to obtain the information of each network element server, namely, the role (Roles). The roles include J2-Tempalte (i.e., the configuration template of DPOS, which generates the dpos.conf file, the dpos startup initialization file, etc.), Task-install, Task-config, Task-cheak, Task-init, Task-uniastall, handle-Restart. Then, based on the information of each network element server, an SSH connection is established with all network element servers in the cluster, and finally, each network element server is deployed according to the written deployment instructions. Based on this one-to-many concurrent deployment mode, for scenarios with a large number of network element servers in the cluster, it can greatly save deployment time and avoid the problem of easy operational errors in manual deployment of each server.

[0094] The present application also provides a device for automatically deploying network data plane, referring to Figure 7 As shown, Figure 7 1 is a schematic diagram of a structure of a device for automatically deploying network element data planes for deploying a server provided in an embodiment of the present application, the device comprising: A writing module 710 is used to write deployment instructions according to deployment tasks, wherein the deployment tasks include: automatic configuration generation, pre-deployment check, network element system initialization, data plane service deployment, and post-deployment check; The connection module 720 is used to obtain information of each network element server in the cluster from the configuration file, and establish a target connection with each network element server according to the information; Generation module 730 is used to generate a temporary deployment script according to the deployment instruction, and send the temporary deployment script to each network element server under the cluster through the target connection, so that the network element server executes the temporary deployment script to implement configuration deployment. The temporary deployment script is used to implement the function corresponding to the deployment task.

[0095] In an optional embodiment, the deployment task includes automatic configuration generation, pre-deployment check, network element system initialization, data plane service deployment, and post-deployment check; the writing module includes: The encapsulation module is used to encapsulate different deployment tasks into scripts, including: automatic generation of configuration scripts, pre-deployment check scripts, network element system initialization scripts, data plane service deployment scripts, and post-deployment check scripts; The collection module is used to collect the scripts into deployment instructions according to the execution order of the scripts.

[0096] In an optional embodiment, the generating module includes: An operation module is used to execute the deployment instruction and determine the target deployment task; The generation submodule is used to call the corresponding script to generate a temporary deployment script according to the target deployment task.

[0097] In an optional embodiment, when the deployment task is to automatically generate a configuration, the encapsulation module is also used to: generate a configuration file in a target format based on a network planning file, wherein the network planning file includes relevant network configuration information of a network element; and encapsulate the configuration file into an automatically generated configuration script.

[0098] In an optional embodiment, when the deployment task is a pre-deployment check, the encapsulation module is also used to: encapsulate the function of checking whether the actual configuration of the current network element server meets the integrated deployment requirements into a first pre-deployment check script; encapsulate the function of comparing and conflict checking the configuration generated by the automatically generated configuration with the actual configuration of the current network element server into a second pre-deployment check script; and obtain a pre-deployment check script based on the first pre-deployment check script and the second pre-deployment check script.

[0099] In an optional embodiment, when the deployment task is network element system initialization, the encapsulation module is also used to: integrate the system initialization function of the network element server into a network element system initialization script; wherein the system initialization function includes a first configuration function, a second configuration function, a third configuration function, and a fourth configuration function; the first configuration function is used to download and install dependencies, drivers, kernels and data plane service programs from a target source; the second configuration function is used to install dependency tools through the target source; the third configuration function is used to upgrade and downgrade the network element server kernel and driver versions when the network element server kernel and driver versions do not meet the requirements; the fourth configuration function is used to specify the allocated large page memory size and number of pages in the startup script of the network element server.

[0100] In an optional embodiment, when the deployment task is data plane service deployment, the encapsulation module is also used to: integrate data plane service functions into a data plane service script; wherein the data plane service functions include a first service function, a second service function, and a third service function; the first service function is used to download and install a service program through a target source; the second service function is used to read a configuration file generated by the automatic generation configuration, and generate a configuration for program operation on the network element server; the third service function is used to start the service program after the service program is installed and configured.

[0101] In an optional embodiment, when the deployment task is a post-deployment check task, the encapsulation module is also used to: integrate the post-deployment check function into a post-deployment check script; wherein the post-deployment check function includes: a first check service, a second check service, a third check service, a fourth check service, and a fifth check service; the first check service is used to check whether the program is running normally; the second check service is used to check whether the version of the data plane program running after deployment is consistent with the version in the deployment configuration; the third check service is used to check the connectivity between the internal and external network network cards and the gateway; the fourth check service is used to check whether the connection with the switch neighbor is normal; the fifth check service is used to check whether the network element has completed the reconciliation and synchronization with the control plane configuration.

[0102] In an optional embodiment, the device further includes: A first result receiving module, used to receive the execution result of the temporary deployment script returned from the network element server; A deletion module is used to delete the temporary deployment script.

[0103] The present application also provides a device for automatically deploying network data plane, referring to Figure 8 As shown, Figure 8 1 is a schematic diagram of a structure of a device for automatically deploying a network element data plane applied to a network element server provided in an embodiment of the present application, the device comprising: A receiving module 810 is used to receive a temporary deployment script from a deployment server, wherein the temporary deployment script is generated by the deployment server according to a deployment instruction and is used to implement a function corresponding to the deployment task; The execution module 820 is used to execute the temporary deployment script to implement configuration deployment.

[0104] The present application also provides an electronic device, referring to Fig. 9 , Fig. 9 Schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Fig. 9 As shown, the electronic device 900 includes: a memory 910 and a processor 920. The memory 910 and the processor 920 are connected via a bus communication. A computer program is stored in the memory 810. The computer program can be run on the processor 920, thereby implementing the steps of the method for automatically deploying the network data plane described in the embodiment of the present application.

[0105] The embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of the method for automatically deploying network data plane described in the embodiment of the present application are implemented.

[0106] The embodiment of the present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of the method for automatically deploying network data planes described in the embodiment of the present application.

[0107] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0108] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods and devices according to the embodiments of the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of the 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 terminal device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal 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.

[0109] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product 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.

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

[0111] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present application.

[0112] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal 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, article or terminal device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the elements.

[0113] The above is a detailed introduction to a method for automatically deploying network data planes provided by the present application. This article uses specific examples to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for general technical personnel in this field, based on the ideas of the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A method for automatically deploying network data plane, characterized in that: Applied to a deployment server, the method comprises: Write deployment instructions based on deployment tasks; Obtain information of each network element server in the cluster from the configuration file, and establish a target connection with each network element server according to the information; A temporary deployment script is generated according to the deployment instruction, and the temporary deployment script is sent to each network element server under the cluster through the target connection, so that the network element server executes the temporary deployment script to implement configuration deployment. The temporary deployment script is used to implement the function corresponding to the deployment task.

2. The method according to claim 1, characterized in that The deployment tasks include automated configuration generation, pre-deployment checks, network element system initialization, data plane service deployment, and post-deployment checks; Write deployment instructions based on deployment tasks, including: Encapsulate different deployment tasks into scripts, including: automatic generation of configuration scripts, pre-deployment check scripts, network element system initialization scripts, data plane service deployment scripts, and post-deployment check scripts; The scripts are assembled into deployment instructions in the order in which they are executed.

3. The method according to claim 2, characterized in that Generate a temporary deployment script according to the deployment instruction, including: Run the deployment instruction to determine the target deployment task; According to the target deployment task, the corresponding script is called to generate a temporary deployment script.

4. The method according to claim 2, characterized in that: When the deployment task is to automatically generate configuration, different deployment tasks are encapsulated as scripts, including: Generate a configuration file in a target format according to a network planning file, wherein the network planning file includes relevant network configuration information of a network element; The configuration file is packaged into an automatic configuration script.

5. The method according to claim 2, characterized in that: When the deployment task is a pre-deployment check, different deployment tasks are encapsulated as scripts, including: The function of checking whether the actual configuration of the current network element server meets the requirements of integrated deployment is encapsulated as the first pre-deployment check script; The function of comparing and checking conflicts between the configuration generated by the automatic configuration generation and the actual configuration of the current network element server is encapsulated as a second pre-deployment check script; A pre-deployment check script is obtained according to the first pre-deployment check script and the second pre-deployment check script.

6. The method according to claim 2, characterized in that When the deployment task is to initialize the network element system, different deployment tasks are encapsulated into scripts, including: Integrate the system initialization function of the network element server into the network element system initialization script; Among them, the system initialization function includes a first configuration function, a second configuration function, a third configuration function, and a fourth configuration function; the first configuration function is used to download and install dependencies, drivers, kernels and data plane service programs from the target source; the second configuration function is used to install dependency tools through the target source; the third configuration function is used to upgrade and downgrade the kernel and driver of the network element server when the kernel and driver versions of the network element server do not meet the requirements; the fourth configuration function is used to specify the allocated large page memory size and number of pages in the startup script of the network element server.

7. The method according to claim 2, characterized in that When the deployment task is data plane service deployment, different deployment tasks are encapsulated into scripts, including: Integrate data plane service functions into data plane service scripts; Among them, the data plane service function includes a first service function, a second service function, and a third service function; the first service function is used to download and install the service program through the target source; the second service function is used to read the configuration file generated by the automatic generation configuration, and generate a configuration for program operation on the network element server; the third service function is used to start the service program after the service program is installed and configured.

8. The method according to claim 2, characterized in that: When the deployment task is a post-deployment check task, different deployment tasks are encapsulated as scripts, including: Integrate the post-deployment check functionality into a post-deployment check playbook; Among them, the post-deployment inspection function includes: a first inspection service, a second inspection service, a third inspection service, a fourth inspection service, and a fifth inspection service; the first inspection service is used to check whether the program is running normally; the second inspection service is used to check whether the version of the data plane program running after deployment is consistent with the version in the deployment configuration; the third inspection service is used to check the connectivity between the internal and external network network cards to the gateway; the fourth inspection service is used to check whether the connection with the switch neighbor is normal; the fifth inspection service is used to check whether the network element has completed the reconciliation and synchronization with the control plane configuration.

9. The method according to any one of claims 1 to 8, characterized in that: The method further comprises: Receiving an execution result of the temporary deployment script returned from the network element server; Delete the temporary deployment script.

10. A method for automatically deploying network data plane, characterized in that: Applied to a network element server, the method comprises: Receiving a temporary deployment script from a deployment server, wherein the temporary deployment script is generated by the deployment server according to a deployment instruction, and the temporary deployment script is used to implement a function corresponding to the deployment task; Execute the temporary deployment script to implement configuration deployment.

Images