A method for automating deployment of a data plane of a network element

Abstract

The application provides a method for automatically deploying a data plane of a network element, and relates to the technical field of automatic operation and maintenance, and aims to solve the problem of long deployment time in the scene of complex deployment steps of the existing cloud computing network element server data plane and large number of network elements. The method comprises the following steps: writing a deployment instruction according to a deployment task; obtaining information of each network element server under a cluster from a configuration file, and establishing a target connection with each network element server according to the information; generating a temporary deployment script according to the deployment instruction, and sending 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 realize configuration deployment, and the temporary deployment script is used to realize the function corresponding to the deployment task.

Description

Technical Field

[0001] This application relates to the field of automated operation and maintenance technology, and in particular to a method for automating the deployment of network data plane. Background Technology

[0002] The cloud computing service industry is booming, and the demand for network element servers that provide essential underlying network forwarding services for cloud computing is increasing. To enable network element servers to provide customized network forwarding services, the services need to be deployed on the network element servers.

[0003] Currently, the deployment of network element servers mostly relies on manual deployment of multiple commands and network elements one by one. The deployment process is cumbersome and complex, with a high rate of human intervention. Writing configurations and executing numerous deployment commands is very prone to errors. Furthermore, it requires logging into each network element server one by one for deployment, which is a huge time cost for scenarios with a large number of network element servers in a cluster. Moreover, because it is a manual deployment, the error rate is greatly increased.

[0004] Therefore, existing cloud computing network element server data plane deployment steps are complex, and deployment is time-consuming in scenarios with a large number of network elements. Summary of the Invention

[0005] In view of the above problems, embodiments of this application provide a method for automatically deploying network data planes in order to overcome or at least partially solve the above problems.

[0006] A first aspect of this application discloses a method for automatically deploying network data planes, applied to a deployment server, the method comprising:

[0007] Write deployment instructions based on the deployment tasks;

[0008] Obtain information about each network element server in the cluster from the configuration file, and establish target connections with each network element server based on the information.

[0009] A temporary deployment script is generated according to the deployment instruction, and the temporary deployment script is sent to each network element server in the cluster through the target connection, so that the network element server executes the temporary deployment script to realize the configuration deployment. The temporary deployment script is used to implement the function corresponding to the deployment task.

[0010] Optionally, the deployment task includes automated configuration generation, pre-deployment checks, network element system initialization, data plane service deployment, and post-deployment checks; and writing deployment instructions based on the deployment task, including:

[0011] Different deployment tasks are encapsulated into scripts, which include: automated configuration generation script, pre-deployment check script, network element system initialization script, data plane service deployment script, and post-deployment check script;

[0012] The scripts are assembled into deployment instructions according to their execution order.

[0013] Optionally, a temporary deployment script is generated according to the deployment instructions, including:

[0014] Run the deployment command to determine the target deployment task;

[0015] Based on the target deployment task, the corresponding script is invoked to generate a temporary deployment script.

[0016] Optionally, when deployment tasks are configured to be automatically generated, different deployment tasks can be encapsulated into playbooks, including:

[0017] Based on the network planning document, generate a configuration file in the target format, wherein the network planning document includes relevant network configuration information of the network elements;

[0018] The configuration file is encapsulated into an automated configuration script generation tool.

[0019] Optionally, when the deployment task is a pre-deployment check, different deployment tasks can be encapsulated into playbooks, including:

[0020] The function of checking whether the actual configuration of the current network element server meets the integration and deployment requirements is encapsulated as the first pre-deployment check script.

[0021] The function of comparing and checking for conflicts between the configuration generated by the automated configuration generation and the actual configuration of the current network element server is encapsulated as a second pre-deployment check script.

[0022] The pre-deployment check script is obtained based on the first pre-deployment check script and the second pre-deployment check script.

[0023] Optionally, when the deployment task is to initialize the network element system, different deployment tasks are encapsulated into scripts, including:

[0024] The system initialization function of the network element server is integrated into the network element system initialization script;

[0025] 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, kernel, and data plane service programs from the target source. The second configuration function is used to install dependent tools through the target source. The third configuration function is used to upgrade or downgrade the network element server kernel and driver when the version does not meet the requirements. The fourth configuration function is used to specify the allocated large page memory size and number of pages in the network element server's startup script.

[0026] Optionally, when the deployment task is a data plane service deployment, different deployment tasks can be encapsulated into playbooks, including:

[0027] Integrate data plane service functions into a data plane service script;

[0028] 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 automated configuration generation and generate the program running configuration on the network element server; the third service function is used to start the service program after the service program is installed and configured.

[0029] Optionally, when the deployment task is a post-deployment inspection task, different deployment tasks can be encapsulated into playbooks, including:

[0030] Integrate the post-deployment inspection functionality into a post-deployment inspection script;

[0031] 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 from the internal and external network cards to the gateway; the fourth inspection service is used to check whether the connection with the switch neighbor is established normally; and the fifth inspection service is used to check whether the network element has completed the reconciliation and synchronization with the control plane configuration.

[0032] Optionally, the method further includes:

[0033] Receive the execution result of the temporary deployment script returned by the network element server;

[0034] Delete the temporary deployment script.

[0035] A second aspect of this application discloses a method for automatically deploying network element data planes, applied to a network element server, the method comprising:

[0036] Receive a temporary deployment script from the deployment server, the temporary deployment script being generated by the deployment server according to the deployment instructions, the temporary deployment script being used to implement the functions corresponding to the deployment task;

[0037] The temporary deployment script is executed to perform the configuration deployment.

[0038] A third aspect of this application discloses an apparatus for automatically deploying network data planes, applied to a deployment server, the apparatus comprising:

[0039] A module is used to write deployment instructions based on deployment tasks, which include: automated configuration generation, pre-deployment checks, network element system initialization, data plane service deployment, and post-deployment checks.

[0040] The connection module is used to obtain information about each network element server in the cluster from the configuration file and establish target connections with each network element server based on the information.

[0041] The generation module is used to generate a temporary deployment script according to the deployment instructions, and send the temporary deployment script to each network element server in the cluster through the target connection, so that the network element server executes the temporary deployment script to realize the configuration deployment. The temporary deployment script is used to implement the function corresponding to the deployment task.

[0042] A fourth aspect of this application discloses an apparatus for automatically deploying network element data planes, applied to a network element server, the apparatus comprising:

[0043] A receiving module is used to receive a temporary deployment script from a deployment server. The temporary deployment script is generated by the deployment server according to the deployment instructions and is used to implement the function corresponding to the deployment task.

[0044] The execution module is used to execute the temporary deployment script to implement the configuration deployment.

[0045] A fifth aspect of this application discloses an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps of the method for automatically deploying network data planes as described in the first aspect of this application, or the steps of the method for automatically deploying network data planes as described in the second aspect of this application.

[0046] A fourth aspect of this application discloses a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method for automatically deploying network data planes as described in the first aspect of this application, or the steps of the method for automatically deploying network data planes as described in the second aspect of this application.

[0047] A fifth aspect of this application discloses a computer program product, including a computer program that, when executed by a processor, implements the steps of the method for automatically deploying network data planes as described in the first aspect of this application, or the steps of the method for automatically deploying network data planes as described in the second aspect of this application.

[0048] The embodiments of this application have the following advantages:

[0049] In this embodiment, deployment instructions are written according to the deployment task; information of each network element server in the cluster is obtained from the configuration file, and target connections are established with each network element server based on the information; a temporary deployment script is generated according to the deployment instructions, and the temporary deployment script is sent to each network element server in the cluster through the target connections, so that the network element server executes the temporary deployment script to achieve configuration deployment. In this way, all deployment tasks are integrated into a deployment instruction, and a single deployment instruction completes the one-click automated deployment of network element servers, eliminating the need for cumbersome and complex deployment processes and solving the problem of complex deployment steps for current cloud computing network element server data planes; moreover, multiple network element servers in the cluster can be deployed simultaneously, saving deployment time and solving the problem of long deployment times for each network element server when there are many network element servers in the cluster. Attached Figure Description

[0050] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments of this application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0051] Figure 1 This is a schematic diagram of the structure of a system for automatically deploying network data planes according to an embodiment of this application;

[0052] Figure 2 This is a flowchart illustrating the steps of a method for automatically deploying network data planes on a deployment server, as provided in an embodiment of this application.

[0053] Figure 3 This is a flowchart illustrating the steps of a method for automatically deploying network element data planes applied to a network element server, as provided in an embodiment of this application.

[0054] Figure 4 This is a flowchart illustrating the steps of a method for automatically deploying network data plane according to an embodiment of this application;

[0055] Figure 5 This is a deployment flowchart of a network element server provided in an embodiment of this application;

[0056] Figure 6 This is a schematic diagram of the structure of another system for automatically deploying network data planes provided in an embodiment of this application;

[0057] Figure 7 This is a schematic diagram of a device for automatically deploying network data planes for deployment servers, provided in an embodiment of this application.

[0058] Figure 8 This is a schematic diagram of a device for automatically deploying network element data planes applied to a network element server, provided in an embodiment of this application.

[0059] Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0060] To make the above-mentioned objectives, features, and advantages of this application more apparent and understandable, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0061] To better understand the technical solution of this application, the technical probabilities involved in this application will be explained.

[0062] Ansible is 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.

[0063] Yum (Yellow dog Updater, Modified) is a shell-based package manager for Fedora, Red Hat, and CentOS. Based on RPM package management, it can automatically download and install RPM packages from specified servers, automatically handle dependencies, and install all dependent packages at once, eliminating the need for tedious downloading and installation.

[0064] NUMA (Non-Uniform Memory Access) is a computer architecture that allows multiple processors to access the system's physical memory through shared memory. However, different memory regions may be handled 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 multiprocessor systems and make the system more scalable.

[0065] In related technologies, the deployment of network element servers is still mostly based on manual deployment of multiple commands and multiple network elements one by one. The deployment process is cumbersome and complex, with a high rate of human intervention. Writing configurations and executing numerous deployment commands is very prone to errors. Furthermore, it requires logging into each network element server one by one for deployment. For scenarios with a large number of network element servers in a cluster, the deployment time cost is enormous, and because it is a manual deployment, the error rate is also greatly increased.

[0066] Furthermore, the deployment environment of the network element servers was not automatically initialized, resulting in numerous issues during deployment where the network element servers failed to meet deployment requirements. These issues included failure to download necessary installation packages from the yum repository, missing dependency tools, outdated system kernel or driver versions, incompatible network card models, CPU and NUMA counts, and data plane programs failing to allocate memory. These problems required manual resolution before or during deployment. Additionally, the lack of an integrated inspection mechanism in the deployment system led to frequent instances where network element servers failed to meet deployment integration requirements or, after deployment, the data plane programs failed to run properly.

[0067] Therefore, the existing deployment method has the following four main problems: 1) The operation steps are complex, requiring multiple steps and multiple instructions to complete the service deployment, which is not user-friendly; 2) Since the deployment is carried out one network element at a time, the deployment time is long for scenarios with a large number of network element servers, and the more network elements there are, the longer the time will be; 3) Since the network element servers are not automatically initialized before deployment, the network element servers may not meet the deployment or data plane program operation conditions, resulting in deployment failure or network element data plane service problems, or the network element servers are manually initialized before deployment, which is complicated and prone to errors; 4) It is impossible to detect whether there are deployment configuration conflicts or whether the network element servers meet the deployment requirements before deployment, resulting in deployment failure or abnormal operation of programs or services after deployment, and it is impossible to detect the operation status of data plane programs and services in a timely manner after deployment, requiring separate checks through other methods or scripts.

[0068] To overcome the limitations of related technologies, this application provides a method for automating the deployment of network element data plane. This method integrates deployment tasks into a single deployment command, which enables one-click automated deployment of network element servers. This significantly reduces deployment complexity, enhances ease of use, and solves the problem of complex deployment steps for current cloud computing network element server data planes. Furthermore, it allows for the simultaneous deployment of multiple network element servers in a cluster, with the time required to deploy multiple network elements being roughly equivalent to the time required to deploy a single network element, thus greatly saving deployment time.

[0069] The method for automatically deploying network data planes according to embodiments of this application will now be described with reference to the accompanying drawings.

[0070] Reference Figure 1 As shown, Figure 1 This is a schematic diagram of the structure of a system for automatically deploying network element data planes according to an embodiment of this application. Specifically, the system includes a deployment server and a cluster containing 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 simultaneously and deploy each network element server according to the pre-written deployment instructions. Based on this one-to-many concurrent deployment mode, it can greatly save deployment time in scenarios with a large number of network element servers in the cluster, and avoid the problem of easy operation errors in manual deployment one by one.

[0071] This application provides a method for automatically deploying network data planes, which is applied to a deployment server. (Refer to...) Figure 2 As shown, Figure 2 This is a flowchart illustrating the steps of a method for automatically deploying network data planes on a deployment server, as provided in an embodiment of this application. Figure 2 As shown, the method for automatically deploying network data planes may include steps S210 to S230:

[0072] Step S210: Write deployment instructions based on the deployment task.

[0073] Step S220: Obtain information about each network element server in the cluster from the configuration file, and establish target connections with each network element server based on the information.

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

[0075] In this embodiment of the application, the deployment task refers to the relevant task of deploying the network element server, such as the initialization of the network element system. The deployment tasks are combined into a single deployment instruction, so that there is no need to execute numerous and complex deployment instructions or scripts. The network element server can be deployed by executing this deployment instruction. There is no need to execute a cumbersome and complex deployment process, which greatly improves operability and user-friendliness and makes it easy to use.

[0076] Before deploying the network element servers, the deployment server first establishes target connections with each network element server by obtaining information about each network element server in the cluster from the configuration file. In some embodiments, the information about each network element server in the cluster may be a list of cluster host IPs (i.e., a list of network element servers in the cluster) and corresponding SSH account information. The Ansible program reads the configuration file to obtain the list of cluster host IPs and corresponding SSH account information, and then establishes SSH connections (i.e., target connections) with all network element servers in the cluster based on this information.

[0077] After establishing a target connection with each network element server, a deployment command is executed to generate a temporary deployment script, and the temporary deployment script is sent to each network element server in 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 achieve the corresponding deployment by executing the temporary deployment script.

[0078] The technical solution of this application integrates all deployment tasks into a deployment command, and completes the one-click automated deployment of network element servers with a single deployment command. This eliminates the need for cumbersome and complex deployment processes, solving the problem of complex deployment steps for current cloud computing network element server data planes. Moreover, it can deploy multiple network element servers in the cluster simultaneously, saving deployment time and solving the problem of long deployment times for each network element server when there are many network element servers in the cluster.

[0079] In conjunction with the above embodiments, in one embodiment, this application also provides a method for automatically deploying network element data plane. In this method, the deployment task includes automated configuration generation, pre-deployment checks, network element system initialization, data plane service deployment, and post-deployment checks; step S110 above, "writing deployment instructions according to the deployment task," specifically includes the following steps S110-1 to S110-2:

[0080] Step S110-1: Encapsulate different deployment tasks into scripts, which include: automated configuration generation script, pre-deployment check script, network element system initialization script, data plane service deployment script, and post-deployment check script.

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

[0082] In this embodiment, automated configuration generation refers to automatically generating the 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 automated configuration before deployment, in order 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 to avoid deployment failure or problems with network element data plane services due to the network element server not meeting the deployment or data plane program running conditions; data plane service deployment refers to deploying services and programs based on the network element server; post-deployment check refers to performing necessary checks on the data plane services after the network element server deployment is completed to prevent abnormal operation of data plane service programs or services.

[0083] Different deployment tasks can be encapsulated into corresponding scripts using target script patterns and syntax. Commands are then used to execute these scripts sequentially according to their execution order to achieve the deployment functionality of each task, and these scripts are integrated into a single deployment command. The execution order of the scripts is as follows: automated configuration generation script, pre-deployment check script, network element system initialization script, data plane service deployment script, and post-deployment check script. For example, based on Ansible's script patterns and syntax, different deployment tasks can be encapsulated into corresponding scripts. Then, shell scripts can be used to execute these five scripts sequentially via shell commands to achieve the deployment functionality of these five tasks, and these scripts can be integrated into a single shell deployment command.

[0084] The technical solution adopted in this application integrates different deployment tasks into a single deployment command. Executing this single command enables one-click automated deployment of network element server systems, including system initialization, service installation, service configuration, service startup, and service checks. Because network element system initialization and post-deployment checks are integrated into the deployment command, it solves problems such as network element servers not meeting deployment integration requirements and lacking deployment check mechanisms. Furthermore, the network element system initialization script in the deployment command ensures compatibility with different kernels, driver versions, and other machine types, guaranteeing system compatibility and versatility. Thus, without the need for manual configuration entry and checks, program and business operation checks, or cumbersome deployment steps, rapid deployment with better results can be achieved.

[0085] In conjunction with the above embodiments, in one embodiment, this application also provides a method for automatically deploying network data plane. In this method, step S130, "generating a temporary deployment script according to the deployment instruction," specifically includes the following steps S130-1 to S130-2:

[0086] Step S130-2: Run the deployment command to determine the target deployment task.

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

[0088] In this embodiment of the application, different target deployment tasks correspond to different temporary deployment scripts. The deployment instructions set up different deployment tasks. The target deployment task to be executed is determined according to the current running progress, and then a temporary deployment script is generated by calling the corresponding script.

[0089] For example, when the deployment command reaches the point of executing pre-deployment checks, the pre-deployment check script is invoked to generate a corresponding temporary deployment script, which is then sent to the network element server so that the network element server can execute the pre-deployment checks. When the deployment command reaches the point of executing network element system initialization, the network element system initialization script is invoked to generate a corresponding temporary deployment script, which is then sent to the network element server so that the network element server can execute the network element system initialization.

[0090] By employing the technical solution of this application embodiment, temporary deployment scripts corresponding to each deployment task are automatically generated by running deployment instructions, enabling the network element server to perform the corresponding deployment based on the temporary deployment scripts. In this way, users only need to execute the deployment instruction to complete the entire deployment with one click, eliminating the need for cumbersome and complex deployment processes. Operability and user-friendliness are greatly improved, resulting in high ease of use.

[0091] In conjunction with the above embodiments, in one implementation, this application also provides a method for automatically deploying network data plane. This method, in addition to the steps described above, further includes the following steps:

[0092] Step S140: Receive the execution result of the temporary deployment script returned by the network element server.

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

[0094] In this embodiment, a temporary deployment script can be sent to multiple network element servers in the cluster for deployment simultaneously. After executing the temporary deployment script, the network element server will feed back the execution result of the temporary deployment script to the deployment server, thereby deleting the temporary deployment script and avoiding the occupation of memory resources by the already executed temporary deployment script. Furthermore, the deployment server can clearly see the deployment status of each network element server based on the execution result. Compared with the complex deployment process with multiple instructions and the method of logging into each network element one by one for deployment, it can greatly improve deployment efficiency, shorten deployment time, and achieve high efficiency.

[0095] The following sections explain how to encapsulate different deployment tasks into scripts.

[0096] In one alternative scenario, when the deployment task is to automatically generate configurations, different deployment tasks are encapsulated into scripts, including: generating a configuration file in a target format based on a network planning document, wherein the network planning document includes relevant network configuration information of network elements; and encapsulating the configuration file into an automatically generated configuration script.

[0097] In this embodiment, the network planning file can be in JSON format, and the configuration file can be in YAML format. Specifically, generating the target format configuration file based on the network planning file can be achieved by a Python script automatically parsing the network planning file, generating a YAML format configuration file that Ansible can read based on the parsing results, and integrating it into Ansible's automated configuration script generation.

[0098] In this way, subsequent automated deployments can directly call the automatically generated configuration script, saving the step of manually filling in the deployment configuration, thus improving ease of use and deployment efficiency.

[0099] In one alternative scenario, when the deployment task is a pre-deployment check, different deployment tasks are encapsulated into scripts, including: encapsulating the function of checking whether the actual configuration of the current network element server meets the integration deployment requirements into a first pre-deployment check script; encapsulating the function of comparing and checking for conflicts between the configuration generated by the automated configuration generation and the actual configuration of the current network element server into a second pre-deployment check script; and obtaining the pre-deployment check script based on the first pre-deployment check script and the second pre-deployment check script.

[0100] In this embodiment, the pre-deployment check is encapsulated into two scripts. The first pre-deployment check script can be implemented using a shell script, which encapsulates the function of checking whether the actual configuration of the current network element server meets the integration deployment requirements. Whether the actual configuration of the current network element server meets the integration deployment requirements refers to whether the operating system kernel version, the number of NUMA CPUs, whether hyper-threading is disabled, the network card name, the binding of internal and external network cards to NUMA, the network card model and transmission rate, and the server network management service meet the integration deployment specification requirements.

[0101] The second pre-deployment check script can be implemented using a Python script to compare and check for conflicts between the automatically generated configuration and the actual configuration of the current network element server; for example, checking whether the configurations automatically generated through the network planning document, such as IP addresses and cluster information, conflict with the actual configuration of the current network element server.

[0102] In this way, the system can automatically check whether the configuration of the network element server meets the specified requirements before deployment, and whether the planned configuration conflicts with the actual configuration of the current network element server. This prevents service disruptions caused by deployment with incorrect configurations. For example, deploying network elements with incorrect configurations in a capacity expansion scenario may cause abnormalities in the existing network element services, leading to failures. Moreover, it avoids the tediousness and unreliability of manual checks, improving the reliability and ease of use of the deployment system.

[0103] In one alternative scenario, when the deployment task is to initialize the network element system, 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.

[0104] 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, kernel, and data plane service programs from the target source. The second configuration function is used to install dependent tools through the target source. The third configuration function is used to upgrade or downgrade the network element server kernel and driver when the version does not meet the requirements. The fourth configuration function is used to specify the allocated large page memory size and number of pages in the network element server's startup script.

[0105] Specifically, shell scripts can be used to implement and integrate the system initialization function of the network element server 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, so that dependencies, drivers, kernel and data plane service programs can be downloaded and installed from the target source (e.g., yum source).

[0106] The second configuration function refers to installing dependent tools, which is done via yum. These necessary dependent tools can be network service-related tools, data plane program-dependent tools, etc.

[0107] The third configuration function refers to upgrading and downgrading the kernel and drivers. When the kernel and driver versions of the network element server do not meet the requirements, the kernel and drivers are upgraded or downgraded to meet the requirements. Upgrading and downgrading the kernel uses yum to install the required kernel version and dependencies, and sets the kernel boot order in the startup file to achieve the goal of starting the system with the required kernel version. Upgrading and downgrading the driver will first uninstall the original driver and then install the specified version of the driver.

[0108] The fourth configuration function refers to configuring large page memory. By specifying the size and number of large page memory to be allocated 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.

[0109] In this embodiment, the network element system initialization script is executed automatically via script before the deployment of the data plane service program. This initializes the network element server environment, ensuring that the network element server meets the deployment and data plane program operation requirements. This prevents errors during the deployment or operation of the data plane service program due to an unmet server environment, improves the deployment compatibility of network element machines with different system kernels and driver versions, and prevents system crashes and network card disconnection caused by high-risk operations such as manually upgrading or downgrading the kernel, network card driver, or modifying system configurations such as configuration pages. This enhances the security and usability of the deployed system.

[0110] In one alternative scenario, when the deployment task is a data plane service deployment, different deployment tasks are encapsulated into playbooks, including: integrating data plane service functions into a data plane service playbook;

[0111] 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 automated configuration generation and generate the program running configuration on the network element server; the third service function is used to start the service program after the service program is installed and configured.

[0112] Specifically, Ansible's YAML scripts, J2 template scripts, and shell scripts can be used to integrate data plane service functions into data plane service scripts for automated deployment. The first service function refers to service program installation, which can be downloaded and installed from a target source (e.g., a yum repository). Specifically, it can be installed according to the program version specified in the configuration file, or a specific service version can be specified via the command line. The second service function refers to service configuration, which involves reading the automatically generated configuration file and generating the program's runtime configuration on the network element server. The third service function refers to service startup, which involves starting the service program after installation and configuration.

[0113] In this embodiment, data plane service deployment can be achieved simply by automatically installing the data plane service program according to the deployment configuration, generating the corresponding configuration, and starting the data plane program. Furthermore, by employing Ansible's concurrent deployment mechanism, multiple network element servers can be installed and deployed simultaneously, eliminating the tedious and error-prone manual deployment of each network element individually, thus achieving efficient deployment.

[0114] In one alternative scenario, where the deployment task is a post-deployment check task, different deployment tasks are encapsulated into playbooks, including: integrating post-deployment check functionality into a post-deployment check playbook.

[0115] 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 from the internal and external network cards to the gateway; the fourth inspection service is used to check whether the connection with the switch neighbor is established normally; and the fifth inspection service is used to check whether the network element has completed the reconciliation and synchronization with the control plane configuration.

[0116] Specifically, this can be implemented using shell and Python scripts, integrating post-deployment checks into a post-deployment check playbook (i.e., an Ansible playbook). The first check service examines the running status of service programs, such as process runtime and whether coredump files are generated. The second check service checks the program version, verifying that the version running on the data plane program after deployment matches the version configured in the deployment configuration, preventing deployment of a different version. The third check service checks network interface card (NIC) connectivity, verifying the connectivity between internal and external NICs and the gateway, which can be achieved through ping to ensure NIC connectivity. The fourth check service checks BGP neighbor establishment, i.e., verifying whether neighbor connections with the switch are established normally. The fifth check service checks configuration synchronization, i.e., verifying whether network elements have completed reconciliation and synchronization with the control plane configuration, ensuring that the configuration issued by the control plane has been synchronized to the data plane program.

[0117] In this embodiment, 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, eliminating tedious manual check steps and improving deployment efficiency and reliability.

[0118] This application provides a method for automatically deploying network element data planes, which is applied to a network element server. (Refer to...) Figure 3 As shown, Figure 3 This is a flowchart illustrating the steps of a method for automatically deploying network element data planes applied to a network element server, as provided in an embodiment of this application. Figure 3 As shown, the method for automatically deploying network data planes may include steps S310 to S320:

[0119] Step S310: Receive a temporary deployment script from the deployment server. The temporary deployment script is generated by the deployment server according to the deployment instructions and is used to implement the functions corresponding to the deployment task.

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

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

[0122] 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 can delete the temporary deployment script, avoid the temporary deployment scripts that have been executed occupying memory resources, and allow each deployment server to clearly know the deployment status of each network element server based on the execution result.

[0123] The technical solution adopted in this application integrates all deployment tasks into a deployment command, enabling one-click automated deployment of network element servers with a single command. This eliminates the need for cumbersome and complex deployment processes, solving the problem of complex deployment steps for current cloud computing network element server data planes. Furthermore, it allows simultaneous deployment of multiple network element servers in a cluster, saving deployment time and addressing the issue of time-consuming individual deployment when there are many network element servers in a cluster. Since tasks such as network element system initialization and post-deployment checks are integrated into the deployment command, it solves problems such as network element servers not meeting deployment integration requirements and lacking deployment check mechanisms, resulting in better deployment performance.

[0124] The method for automatically deploying network data plane provided in this application will be described below with a specific embodiment. (Refer to...) Figure 4 As shown, Figure 4 This is a flowchart illustrating the steps of an automated deployment method for network data plane according to an embodiment of this application. Specifically, the method includes the following steps S410 to S460:

[0125] Step S410: The deployment server encapsulates different deployment tasks into scripts; and according to the execution order of the scripts, it sets the scripts into deployment instructions. The scripts include: automated configuration generation script, pre-deployment check script, network element system initialization script, data plane service deployment script, and post-deployment check script.

[0126] Step S420: The deployment server obtains information about each network element server in the cluster from the configuration file, and establishes target connections with each network element server based on the information.

[0127] Step S430: The deployment server runs the deployment command to determine the target deployment task; based on the target deployment task, it calls the corresponding script to generate a temporary deployment script.

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

[0129] Step S450: The network element server receives a temporary deployment script from the deployment server, executes the temporary deployment script, and sends the execution result of the temporary deployment script back to the deployment server.

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

[0131] In this embodiment, based on the Ansible script mode, deployment tasks such as automated configuration generation, pre-deployment checks, network element system initialization, data plane service deployment, and post-deployment checks are written into Ansible scripts and integrated into a single deployment command. This way, users do not need to execute numerous and complex deployment commands or scripts; they can easily complete the deployment by executing a single command. There is no need to perform tedious and complex deployment processes, which greatly improves operability and user-friendliness, and makes it highly easy to use.

[0132] Furthermore, thanks to Ansible's concurrent execution mechanism, all network element servers in the cluster can be deployed concurrently. The deployment status of each network element server can be clearly seen from the return results of Ansible's execution. Compared with the complex deployment process with multiple commands and the method of logging into each network element server one by one for deployment, it can greatly improve deployment efficiency, shorten deployment time, and achieve high efficiency.

[0133] Before deployment, the network element server environment is initialized to ensure that the network element yum source configuration, kernel, driver, huge page memory, and dependent tools meet the conditions for deployment and operation of network element data surface programs. Even if the kernel, driver, huge page, or other conditions are not met, deployment can still be completed normally, improving the compatibility and versatility of the deployment system.

[0134] Before deployment, the system checks whether the actual configuration of the network element server meets the integration deployment specifications and performs conflict checks between the deployed configuration and the current actual configuration of the network element server. This proactively identifies whether the network element server is non-standard and whether there are configuration conflicts, preventing abnormal operation and business of the network element server program after deployment. In cases of expansion, this could lead to failures that affect the existing network element server business. After deployment, the system checks the operation of the data plane program and related business on the network element server to prevent abnormal network element services and business after deployment, ensuring that the network element data plane program is correctly deployed and highly reliable. In addition, necessary checks on the data plane service are automatically performed after deployment to prevent abnormal operation of the data plane service program or business, eliminating tedious manual checking steps, improving deployment efficiency and reliability, and thus ensuring that the network element server meets the deployment and data plane program operation conditions before data plane service deployment, and that the data plane service program and business operate normally after deployment.

[0135] parameter Figure 5 As shown, Figure 5This is a deployment flowchart of a network element server provided in an embodiment of this application. Based on the execution order of the script, the network element server performs the following deployments in sequence: configuring the repo file yum source, checking and configuring the network element, installing dependent tools, upgrading and downgrading the kernel and drivers, configuring large page memory, installing the data plane service program, configuring and starting the data plane program, checking the running status of the service program process, and checking the business status, and finally completing the deployment of the network element server.

[0136] The following describes the execution process of the method for automatically deploying network data planes according to the embodiments of this application in the system, using the system for automatically deploying network data planes as an example.

[0137] Reference Figure 6 As shown, Figure 6 This is a schematic diagram of the structure of another automated network element data plane deployment system provided in this application embodiment. Specifically, the system includes a deployment server (i.e., a control node, DPOS control node) and a cluster consisting of multiple network element servers (Host-Nodes). Each network element server contains multiple hosts (GroupHosts). Ansible, DPOS tools-script (i.e., tool scripts for network element nodes), and Host & Ansible-cfg (i.e., Ansible-cfg system configuration and Host host configuration files) are deployed on the deployment server.

[0138] When executing deployment commands for automated deployment, Ansible reads the configuration file (including template configuration and host interface configuration) through the automation scripts (Playbooks) used to configure, deploy, and manage the controlled nodes. This information is used to obtain the roles of each network element server, including J2-Tempalte (the DPOS configuration template, generating the dpos.conf file, dpos startup initialization file, etc.), Task-install, Task-config, Task-cheak, Task-init, Task-unicast, and handle-restart. Based on this information, Ansible establishes SSH connections with all network element servers in the cluster. Finally, it deploys each network element server according to the pre-written deployment commands. This one-to-many concurrent deployment mode significantly reduces deployment time for scenarios with a large number of network element servers in the cluster and avoids the error-prone problem of manual deployment.

[0139] This application also provides an apparatus for automatically deploying network data planes, referring to... Figure 7 As shown, Figure 7This is a schematic diagram of a device for automatically deploying network data planes on a deployment server, provided in an embodiment of this application. The device includes:

[0140] The module 710 is used to write deployment instructions according to the deployment task, which includes: automatic configuration generation, pre-deployment checks, network element system initialization, data plane service deployment, and post-deployment checks.

[0141] The connection module 720 is used to obtain information about each network element server in the cluster from the configuration file and establish target connections with each network element server based on the information.

[0142] The 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 in the cluster through the target connection, so that the network element server executes the temporary deployment script to realize the configuration deployment. The temporary deployment script is used to implement the function corresponding to the deployment task.

[0143] In one optional embodiment, the deployment task includes automated configuration generation, pre-deployment checks, network element system initialization, data plane service deployment, and post-deployment checks; the writing module includes:

[0144] The encapsulation module is used to encapsulate different deployment tasks into scripts, which include: automated configuration generation script, pre-deployment check script, network element system initialization script, data plane service deployment script, and post-deployment check script;

[0145] The collection module is used to collect the scripts into deployment instructions according to the execution order of the scripts.

[0146] In one optional embodiment, the generation module includes:

[0147] The execution module is used to run the deployment instructions and determine the target deployment task;

[0148] The generation submodule is used to generate a temporary deployment script by calling the corresponding script based on the target deployment task.

[0149] In an optional embodiment, when the deployment task is to automatically generate configurations, the encapsulation module is further configured to: generate a configuration file in a target format based on a network planning file, the network planning file including relevant network configuration information of network elements; and encapsulate the configuration file into an automatically generated configuration script.

[0150] In an optional embodiment, when the deployment task is a pre-deployment check, the encapsulation module is further configured to: encapsulate the function of checking whether the actual configuration of the current network element server meets the integration deployment requirements into a first pre-deployment check script; encapsulate the function of comparing and checking for conflicts between the configuration generated by the automated configuration generation and 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.

[0151] In an optional embodiment, when the deployment task is network element system initialization, the encapsulation module is further configured 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, kernel, and data plane service programs from the target source; the second configuration function is used to install dependent tools through the target source; the third configuration function is used to upgrade or downgrade the network element server kernel and driver 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 network element server startup script.

[0152] In an optional embodiment, when the deployment task is a data plane service deployment, the encapsulation module is further configured to: integrate the 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 configured to download and install the service program through the target source; the second service function is configured to read the configuration file generated by the automated configuration generation and generate the program execution configuration on the network element server; the third service function is configured to start the service program after the service program is installed and configured.

[0153] In an optional embodiment, when the deployment task is a post-deployment check task, the encapsulation module is further configured 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 runs 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 from the internal and external network cards to the gateway; the fourth check service is used to check whether the connection with the switch neighbor is normal; and the fifth check service is used to check whether the network element has completed the reconciliation and synchronization with the control plane configuration.

[0154] In an optional embodiment, the device further includes:

[0155] The first result receiving module is used to receive the execution result of the temporary deployment script returned by the network element server;

[0156] The deletion module is used to delete the temporary deployment script.

[0157] This application also provides an apparatus for automatically deploying network data planes, referring to... Figure 8 As shown, Figure 8 This is a schematic diagram of a device for automatically deploying network element data planes in a network element server, as provided in an embodiment of this application. The device includes:

[0158] The receiving module 810 is used to receive a temporary deployment script from the deployment server. The temporary deployment script is generated by the deployment server according to the deployment instructions and is used to implement the function corresponding to the deployment task.

[0159] The execution module 820 is used to execute the temporary deployment script to implement the configuration deployment.

[0160] This application also provides an electronic device, which is described in reference to... Figure 9 , Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 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 for communication. The memory 910 stores a computer program that can run on the processor 920 to implement the steps of the method for automatically deploying network data planes as described in the embodiments of this application.

[0161] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the method for automatically deploying network data planes as described in this application.

[0162] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the method for automatically deploying network data planes as described in this application.

[0163] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0164] This application describes embodiments of methods and apparatus according to flowchart illustrations and / or block diagrams. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal device, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0165] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing terminal device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0166] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal equipment, causing a series of operational steps to be performed on the computer or other programmable terminal equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable terminal equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0167] Although preferred embodiments of the present application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the embodiments of the present application.

[0168] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.

[0169] The above provides a detailed description of a method for automatically deploying network data planes provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A method for automating deployment of a data plane of a network element, the method comprising: The method applied to a deployment server comprises: writing a deployment instruction according to a deployment task; obtaining information of each network element server under a cluster from a configuration file, and establishing a target connection with each network element server according to the information; generating a temporary deployment script according to the deployment instruction, and sending 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 realize configuration deployment, the temporary deployment script being used to realize a function corresponding to the deployment task; wherein the deployment task comprises automatic configuration generation, pre-deployment check, network element system initialization, data plane service deployment, and post-deployment check; writing a deployment instruction according to a deployment task comprises: encapsulating different deployment tasks into scripts, the scripts comprising an automatic configuration generation script, a pre-deployment check script, a network element system initialization script, a data plane service deployment script, and a post-deployment check script; collecting the scripts into a deployment instruction according to an execution order of the scripts; wherein generating a temporary deployment script according to the deployment instruction comprises: running the deployment instruction to determine a target deployment task; generating a temporary deployment script according to the target deployment task by calling a corresponding script.

2. The method of claim 1, wherein, in the case of the deployment task being automatic configuration generation, encapsulating different deployment tasks into scripts comprises: generating a configuration file in a target format according to a network planning file, the network planning file comprising related network configuration information of a network element; encapsulating the configuration file into an automatic configuration generation script.

3. The method of claim 1, wherein, in the case of the deployment task being pre-deployment check, encapsulating different deployment tasks into scripts comprises: encapsulating a function of checking whether an actual configuration of a current network element server conforms to integrated deployment requirements into a first pre-deployment check script; encapsulating a function of comparing and checking conflicts between a configuration generated by the automatic configuration generation and the actual configuration of the current network element server into a second pre-deployment check script; obtaining a pre-deployment check script according to the first pre-deployment check script and the second pre-deployment check script.

4. The method of claim 1, wherein, in the case of the deployment task being network element system initialization, encapsulating different deployment tasks into scripts comprises: integrating system initialization functions of a network element server into a network element system initialization script; wherein the system initialization functions comprise 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 installation dependencies, drivers, kernels, and data plane service programs from a target source; the second configuration function is used to install a dependency tool through the target source; the third configuration function is used to upgrade or downgrade a kernel and a driver of the network element server when the kernel and the driver do not meet requirements; and the fourth configuration function is used to specify sizes of allocated large pages and numbers of pages in a start script of the network element server.

5. The method of claim 1, wherein, in the case of the deployment task being data plane service deployment, encapsulating different deployment tasks into scripts comprises: integrating data plane service functions into a data plane service script; The data plane service function comprises a first service function, a second service function and a third service function; the first service function is used for downloading and installing a service program through a target source; the second service function is used for reading a configuration file generated through the automatic generation configuration and generating a configuration for program running on the network element server; and the third service function is used for starting the service program after the service program is installed and configured.

6. The method of claim 1, wherein, In the case that the deployment task is a post-deployment checking task, different deployment tasks are encapsulated into a script, including: The post-deployment checking function is integrated into a post-deployment checking script. The post-deployment checking function comprises a first checking service, a second checking service, a third checking service, a fourth checking service and a fifth checking service; the first checking service is used for checking whether a program is normally running; the second checking service is used for checking whether a version of a data plane program running after deployment is consistent with a version in deployment configuration; the third checking service is used for checking connectivity of an internal and external network card to a gateway; the fourth checking service is used for checking whether a connection with a switch neighbor is normal; and the fifth checking service is used for checking whether a network element has completed a check and synchronization with a control plane configuration.

7. The method according to any of claims 1 to 6, characterized in that The method further comprises: receiving an execution result of the temporary deployment script returned from the network element server; deleting the temporary deployment script.

8. A method for automating deployment of a data plane of a network element, the method comprising: The method applied to a network element server comprises: receiving a temporary deployment script from a deployment server, the temporary deployment script being generated by the deployment server according to the method for automatically deploying a data plane of a network element according to any one of claims 1-7, the temporary deployment script being used for realizing a function corresponding to a deployment task; executing the temporary deployment script to realize configuration deployment.

Images