Deployment method and equipment for network function virtualization infrastructure

Abstract

A method and device for deploying a network function virtualization infrastructure, the method comprising: creating a resource pool hardware description file according to a predefined unified resource pool data model, the unified resource pool data model including all software and hardware information of the resource pool and a unified data format in which the software and hardware information is presented; generating a description file of a target NFVI according to design requirements of a user-defined target NFVI resource pool; generating a unified infrastructure description file for the target NFVI that conforms to the unified resource pool data model based on the resource pool hardware description file and the description file of the target NFVI; calling a deployment tool for the network function virtualization infrastructure, and using the unified infrastructure description file of the target NFVI as input to the deployment tool to deploy the target NFVI. The present invention can improve the deployment efficiency of the network function virtualization infrastructure and reduce manual interaction.

Description

Technical Field

[0001] The present invention relates to the field of mobile communication technologies, and in particular to a method and device for deploying a network function virtualization infrastructure. Background Art

[0002] Network Function Virtualization (NFV) technology uses decoupling and reconstruction to effectively separate storage and transmission resources, meet diverse network needs, and reduce dependence on hardware devices.

[0003] like Figure 1 As shown in the figure, in the context of NFV software and hardware decoupling, a set of network function virtualization infrastructure (NFVInfrastructure, NFVI) is often built as a cloud platform by cooperation between multiple vendors, involving the exchange of various data and information between different roles and vendors, including detailed data from all aspects of the construction and application process from physical resource pools to virtual resource pools, which comes from design planning information, configuration principles, equipment information, etc. The life cycle of this data runs through all stages of hardware construction, virtualization, and application deployment.

[0004] In the existing deployment solution, different roles receive inputs such as hardware design tables, hardware resource architecture diagrams, NFVI software design, and network design, and generate data models for their respective deployment tools.

[0005] Hardware design includes the layout design of hardware resources in the laboratory, rack information, naming design of all equipment, connection design and other information. Software design includes the planning of resource pools, availability zones (AZs), computing clusters, management nodes, software-defined network (SDN) nodes and other storage devices and computing devices and other hardware equipment. Network design includes the configuration of all network planes required to build the cloud platform infrastructure, the node range covered by each plane, the virtual local area network ID (VLAN ID), and the corresponding IP range.

[0006] During actual deployment, each role does not run independently, but needs to interact with other roles. The configuration tools for network devices are inseparable from the network-related information in the software implementation solutions of the virtual layer and storage layer. When the storage tool is deployed, it is also necessary to obtain information such as virtual layer resource information and management network information. After the storage layer and virtual layer are deployed, the storage and virtual layer docking link requires the deployment tool to output docking parameters, such as storage docking configuration files, docking certificates and placement paths, authentication accounts, etc. Therefore, in the entire NFVI deployment process, the way information is presented and the information coverage of each link are not uniform, and manual information acquisition from other roles is required. Summary of the Invention

[0007] At least one embodiment of the present invention provides a method and device for deploying a network function virtualization infrastructure, which can improve the deployment efficiency of the network function virtualization infrastructure and reduce the interoperability of manual interaction.

[0008] According to one aspect of the present invention, at least one embodiment provides a method for deploying a network function virtualization infrastructure, including:

[0009] Creating a resource pool hardware description file according to a predefined unified resource pool data model, wherein the unified resource pool data model includes all software and hardware information of the resource pool and a unified data format in which the software and hardware information is presented;

[0010] Generate a target NFVI description file based on the design requirements of the target NFVI resource pool defined by the user;

[0011] generating a unified infrastructure description file for the target NFVI according to the resource pool hardware description file and the description file of the target NFVI, the unified infrastructure description file conforming to the unified resource pool data model, the unified infrastructure description file including software and hardware information of the target NFVI;

[0012] A deployment tool for a network function virtualization infrastructure is called, and the unified infrastructure description file of the target NFVI is used as input to the deployment tool to deploy the target NFVI.

[0013] Furthermore, according to at least one embodiment of the present invention, creating a resource pool hardware description file according to a predefined unified resource pool data model includes:

[0014] According to the hardware information in the unified resource pool data model and its unified data format, the infrastructure in the resource pool is described to obtain the resource pool hardware description file.

[0015] In addition, according to at least one embodiment of the present invention, the data content of the hardware information includes at least one of the following information: resource pool information, cabinet information in the computer room, hardware and port information of server equipment and network equipment, and network connection information.

[0016] Furthermore, according to at least one embodiment of the present invention, generating a target NFVI description file according to the design requirements of the target network function virtualization infrastructure NFVI resource pool defined by the user includes:

[0017] Receive the global information, computing resource planning information, storage resource planning information, and network planning information of the target NFVI defined by the user according to the predefined NFVI description template;

[0018] Generate a description file of the target NFVI based on the received global information, computing resource planning information, storage resource planning information and network planning information of the target NFVI.

[0019] Furthermore, according to at least one embodiment of the present invention, generating a unified infrastructure description file that conforms to the unified resource pool data model for the target NFVI based on the resource pool hardware description file and the description file of the target NFVI includes:

[0020] generating software information of the target NFVI according to the resource pool hardware description file and the description file of the target NFVI and in accordance with the unified resource pool data model;

[0021] The software information of the target NFVI is aggregated with the hardware information in the resource pool hardware description file to obtain a unified infrastructure description file of the target NFVI.

[0022] In addition, according to at least one embodiment of the present invention, the data content of the software information includes at least one of the following information: switch configuration information, resource pool host group information and node information list, management node list, storage pool information and storage node information list, and software docking parameters.

[0023] Furthermore, according to at least one embodiment of the present invention, the deployment tool includes a network tool, a storage deployment tool, a virtual layer deployment tool, and a docking tool; calling the deployment tool of the network function virtualization infrastructure and using the unified infrastructure description file of the target NFVI as input to the deployment tool to deploy the target NFVI includes:

[0024] Invoking the network tool, storage deployment tool, and virtual layer deployment tool, taking the unified infrastructure description file of the target NFVI as input, and respectively deploying the network, storage, and virtual layers of the target NFVI;

[0025] The docking tool is called to identify and dock the docking parameters output by the storage deployment tool and the virtual layer deployment tool to obtain the target NFVI.

[0026] Furthermore, according to at least one embodiment of the present invention, calling the docking tool, identifying and docking the docking parameters output by the storage deployment tool and the virtual layer deployment tool, and obtaining the target NFVI includes:

[0027] Output the docking parameters output by the storage deployment tool and the virtual layer deployment tool to the corresponding docking configuration file according to a uniformly defined parameter format, wherein the parameter format includes the docking certificate name, certificate path, and the name and absolute path of the docking configuration file;

[0028] The docking tool is called to read and identify the docking parameters in the docking configuration files output by the storage deployment tool and the virtual layer deployment tool according to the uniformly defined parameter format, and perform the docking.

[0029] According to another aspect of the present invention, at least one embodiment provides a deployment apparatus for a network function virtualization infrastructure, including:

[0030] A creation module, configured to create a resource pool hardware description file according to a predefined unified resource pool data model, wherein the unified resource pool data model includes all software and hardware information of the resource pool and a unified data format in which the software and hardware information is presented;

[0031] The first generation module is configured to generate a description file of a target NFVI according to the design requirements of a target network function virtualization infrastructure NFVI resource pool defined by a user;

[0032] a second generating module, configured to generate a unified infrastructure description file for the target NFVI that conforms to the unified resource pool data model based on the resource pool hardware description file and the description file of the target NFVI, wherein the unified infrastructure description file includes software and hardware information of the target NFVI;

[0033] The calling module is used to call a deployment tool of the network function virtualization infrastructure, and use the unified infrastructure description file of the target NFVI as input of the deployment tool to deploy the target NFVI.

[0034] Furthermore, according to at least one embodiment of the present invention, the creation module is further configured to describe the infrastructure in the resource pool according to the hardware information in the unified resource pool data model and its unified data format, and obtain the resource pool hardware description file.

[0035] In addition, according to at least one embodiment of the present invention, the data content of the hardware information includes at least one of the following information: resource pool information, cabinet information in the computer room, hardware and port information of server equipment and network equipment, and network connection information.

[0036] In addition, according to at least one embodiment of the present invention, the first generation module is also used to receive the global information, computing resource planning information, storage resource planning information and network planning information of the target NFVI defined by the user according to the predefined NFVI description template; and generate a description file of the target NFVI based on the received global information, computing resource planning information, storage resource planning information and network planning information of the target NFVI.

[0037] In addition, according to at least one embodiment of the present invention, the second generation module is further used to generate software information of the target NFVI based on the resource pool hardware description file and the description file of the target NFVI, and in accordance with the unified resource pool data model; and aggregate the software information of the target NFVI with the hardware information in the resource pool hardware description file to obtain a unified infrastructure description file of the target NFVI.

[0038] In addition, according to at least one embodiment of the present invention, the data content of the software information includes at least one of the following information: switch configuration information, resource pool host group information and node information list, management node list, storage pool information and storage node information list, and software docking parameters.

[0039] In addition, according to at least one embodiment of the present invention, the deployment tool includes a network tool, a storage deployment tool, a virtual layer deployment tool and a docking tool; the calling module is further used to call the network tool, storage deployment tool and virtual layer deployment tool, and use the unified infrastructure description file of the target NFVI as input to respectively deploy the network, storage and virtual layers of the target NFVI; call the docking tool to identify and dock the docking parameters output by the storage deployment tool and the virtual layer deployment tool to obtain the target NFVI.

[0040] In addition, according to at least one embodiment of the present invention, the calling module is further used to output the docking parameters output by the storage deployment tool and the virtual layer deployment tool to the corresponding docking configuration file in accordance with a uniformly defined parameter format, wherein the parameter format includes the docking certificate name, certificate path, the name of the docking configuration file and its absolute path; and call the docking tool to read and identify the docking parameters in the docking configuration file output by the storage deployment tool and the virtual layer deployment tool in accordance with the uniformly defined parameter format to perform the docking.

[0041] According to another aspect of the present invention, at least one embodiment provides a deployment device for a network function virtualization infrastructure, comprising: a processor, a memory, and a program stored on the memory and executable on the processor, wherein the program implements the steps of the method described above when executed by the processor.

[0042] According to another aspect of the present invention, at least one embodiment provides a computer-readable storage medium having a program stored thereon. When the program is executed by a processor, the steps of the method described above are implemented.

[0043] Compared to existing technologies, the network function virtualization infrastructure deployment method and device provided by the embodiments of the present invention, by introducing a unified resource pool data model, enables different tools to directly read a unified infrastructure description file, thereby improving the efficiency of network function virtualization infrastructure deployment and reducing manual interoperability. Furthermore, the embodiments of the present invention can flexibly respond to user design requirements and design changes. Users do not need to understand the underlying hardware information and software implementation details; they only need to specify the overall design plan to build the infrastructure. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Various other advantages and benefits will become apparent to those skilled in the art upon reading the detailed description of the preferred embodiment below. The accompanying drawings are for illustration purposes only and are not to be considered as limiting the present invention. The same reference symbols are used throughout the drawings to represent the same components. In the drawings:

[0045] Figure 1 A schematic diagram of a process for deploying NFVI in the existing technology;

[0046] Figure 2 A schematic diagram of a network function virtualization infrastructure deployment according to an embodiment of the present invention;

[0047] Figure 3 A flowchart of a method for deploying a network function virtualization infrastructure according to an embodiment of the present invention;

[0048] Figure 4 An example diagram of a resource pool deployment process provided by an embodiment of the present invention;

[0049] Figure 5 A schematic diagram of a structure of a deployment device for a network function virtualization infrastructure according to an embodiment of the present invention;

[0050] Figure 6 Another structural diagram of a deployment device for a network function virtualization infrastructure according to an embodiment of the present invention. DETAILED DESCRIPTION

[0051] Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the present invention and to fully convey the scope of the present invention to those skilled in the art.

[0052] The terms "first", "second" etc. in the specification and claims of the present application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable in appropriate circumstances, so that the embodiments of the present application described herein, for example, can be implemented in an order other than those illustrated or described herein. In addition, the terms "comprise" and "have" and any of their variations are intended to cover non-exclusive inclusions, for example, the process, method, system, product or equipment comprising a series of steps or units need not be limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or that are intrinsic to these processes, methods, products or equipment. "And / or" in the specification and claims represents at least one of the connected objects.

[0053] As described in the background, existing NFVI deployments rely on manual integration between multiple vendors. Currently, there is no effective solution for inter-vendor collaboration. The main issues are:

[0054] 1) Different data types have different representations and structures, making them difficult to identify directly using other tools. Instead, manual conversion is required.

[0055] 2) The management of various data contents is fragmented and inconsistent at different stages, making content changes difficult to trace;

[0056] 3) Currently, due to the manual communication between different roles, the construction of NFVI takes a long time. If the design changes, it is difficult to flexibly build and modify it.

[0057] To solve at least one of the above problems, Figure 2As shown, an embodiment of the present invention provides a cloud resource pool infrastructure deployment method based on a unified data model, which uniformly defines a data model of the cloud resource pool infrastructure (also referred to as a unified resource pool data model in this article) for describing a unified data format and data content of a file. The data model content summarizes the data models (parameters) specific to each role and displays them in a unified machine-readable format, so that different tools can directly read the same data model file, and then, based on the uniformly defined data model, it is possible to flexibly deploy the cloud resource pool according to the user's resource pool design. By defining and managing the unified resource pool data model, it is possible to respond more flexibly and quickly when the user proposes a design or design change, complete the deployment of the resource pool infrastructure, and achieve interoperability without human interaction.

[0058] Please refer to Figure 3 , the embodiment of the present invention provides a method for deploying a network function virtualization infrastructure, including:

[0059] Step 31 : creating a resource pool hardware description file according to a predefined unified resource pool data model, wherein the unified resource pool data model includes all software and hardware information of the resource pool and a unified data format in which the software and hardware information is presented.

[0060] The unified resource pool data model defines the specific data content of all software and hardware information within the resource pool and defines a unified data format for presenting this data. This ensures that the data can be automatically recognized by deployment tools used by various partners, eliminating the need for manual data conversion. Based on this unified resource pool data model, corresponding resource pool hardware description files are created for the hardware within the resource pool.

[0061] Specifically, the infrastructure in the resource pool can be described according to the hardware information in the unified resource pool data model and its unified data format to obtain the resource pool hardware description file, wherein the data content of the hardware information generally includes at least one of the following information: resource pool information, cabinet information in the computer room, hardware and port information of server equipment and network equipment, network connection information and other information.

[0062] Step 32: Generate a target NFVI description file based on the design requirements of the target NFVI resource pool defined by the user.

[0063] Here, the user can enter the design requirements for the target NFVI resource pool, such as software and hardware requirements. Based on the above design requirements, a description file of the target NFVI is generated, which defines various requirements information of the target NFVI resource pool.

[0064] To facilitate user input of requirement information, embodiments of the present invention provide a predefined NFVI description template. This template includes description formats for various requirement information, specifically including the target NFVI's global information, computing resource planning information, storage resource planning information, and network planning information. Thus, users can directly enter relevant requirement information into the template according to the description formats. This allows the template to receive the target NFVI's global information, computing resource planning information, storage resource planning information, and network planning information defined by the user according to the NFVI description template and generate a description file for the target NFVI based on the received global information, computing resource planning information, storage resource planning information, and network planning information.

[0065] Step 33: Generate a unified infrastructure description file that complies with the unified resource pool data model for the target NFVI based on the resource pool hardware description file and the description file of the target NFVI, wherein the unified infrastructure description file includes the software and hardware information of the target NFVI.

[0066] Here, embodiments of the present invention can generate software information for the target NFVI based on the resource pool hardware description file and the target NFVI description file, and in accordance with the unified resource pool data model. The software information includes at least one of the following: switch configuration information, resource pool host group information and node information list, management node list, storage pool information and storage node information list, and software interconnection parameters. The software information for the target NFVI is then aggregated with the hardware information in the resource pool hardware description file to obtain a unified infrastructure description file for the target NFVI.

[0067] Step 34: Call a deployment tool for the network function virtualization infrastructure, and use the unified infrastructure description file of the target NFVI as input to the deployment tool to deploy the target NFVI.

[0068] Through the above steps, the embodiment of the present invention generates a unified infrastructure description file for the target NFVI based on the predefined unified resource pool data model. Due to the use of a unified data model, the description file can be automatically recognized by the deployment tools of various partners, avoiding the process of manual data conversion and improving the deployment efficiency of the network function virtualization infrastructure.

[0069] In step 34, the deployment tools include a network tool, a storage deployment tool, a virtualization layer deployment tool, and a docking tool. This embodiment of the present invention can deploy the network, storage, and virtualization layers of the target NFVI by invoking the network tool, storage deployment tool, and virtualization layer deployment tool, respectively, using the unified infrastructure description file of the target NFVI as input. The docking tool is then invoked to identify and dock the docking parameters output by the storage deployment tool and virtualization layer deployment tool, thereby obtaining the target NFVI.

[0070] In order to avoid compatibility issues between deployment tools from different manufacturers, in an embodiment of the present invention, when calling the docking tool to identify and dock the docking parameters output by the storage deployment tool and the virtual layer deployment tool, the docking parameters output by the storage deployment tool and the virtual layer deployment tool can be output to the corresponding docking configuration file in accordance with a uniformly defined parameter format, wherein the parameter format includes the docking certificate name, certificate path, the name of the docking configuration file and its absolute path. Then, the docking tool is called to read and identify the docking parameters in the docking configuration file output by the storage deployment tool and the virtual layer deployment tool in accordance with the uniformly defined parameter format to perform the docking. In this way, by uniformly defining the docking parameters, the embodiment of the present invention avoids the problem in the prior art that the docking process cannot be automatically implemented due to the fact that the docking parameters output by deployment tools from different manufacturers have similar contents and functions but inconsistent names and paths, and require manual adaptation one by one.

[0071] The method of the above embodiment of the present invention is further illustrated below through a more specific example.

[0072] This example is used to deploy a cloud resource pool infrastructure. First, based on the hardware design and physical resource architecture, hardware resource data information is generated in accordance with a unified (cloud) resource pool data model and a unified data structure. This information is a machine-recognizable data representation. Then, based on the user's design of the cloud platform infrastructure, a unified resource pool data model that includes both hardware and software information is automatically generated. This part of the content contains the information required by all roles and is provided in a unified structure. All cloud platform deployment tools can recognize it at one time, without the need for the one-by-one adaptation process in the existing technology. End-to-end automatic deployment of cloud platform infrastructure is completed, and configurable data definitions based on user input (such as YAML files, YAML is a concise non-markup language) are implemented to build a network function virtualization infrastructure. The above construction process is also called network function virtualization infrastructure as code.

[0073] The resource pool deployment process of this example is as follows Figure 4 Shown, including:

[0074] Step 41: Create a resource pool hardware description file according to the definition of the unified resource pool data model.

[0075] Step 42: Define a description file of the user's network function virtualization infrastructure (NFVI).

[0076] In step 43, based on the user settings in step 42 and the resource pool hardware description file in step 41, a complete unified resource pool infrastructure description file of NFVI is generated in accordance with the definition of the unified resource pool data model, including all hardware information and software information.

[0077] In step 44, the NFVI unified resource pool infrastructure description file generated in step 43 is used as the input of the deployment tool, and the corresponding deployment tools are called respectively to deploy the network, deploy the storage, deploy the virtual layer, and realize automatic docking.

[0078] In step 41 above:

[0079] According to the definition of the unified resource pool data model, a resource pool hardware description file is created to describe the data center's infrastructure in a declarative manner. By writing a configuration file that conforms to the format, a resource description of the data center's hardware-level infrastructure can be obtained. The specific hardware description content of the resource pool data model usually includes: resource pool information, information about all cabinets in the computer room, all hardware and port information of servers and network devices, all network connection information, etc.

[0080] In existing technologies, each role typically generates the data models required by their tools directly based on hardware design diagrams and software plans. Hardware design diagrams are difficult to read, requiring different roles to combine hardware design and the integrator's LLD after hardware construction is complete to obtain data. The integrator's data is not uniformly represented, and the ability to identify different roles and manufacturers is poor.

[0081] This example allows you to pre-translate the hardware design layout all at once and present all the hardware information in a list, row by row. This output format allows for machine- and program-readable data, eliminating the inconsistencies in data structure caused by manual translation. This data is then provided to each role as input. This unified structure and data ensures consistent information across all roles, ensuring machine-readable data and eliminating the need for individual translations and data adaptation.

[0082] Table 1 provides an example of hardware information of a server.

[0083]

[0084] Table 1

[0085] In step 42 above:

[0086] This example defines a fixed resource pool description template (NFVI description template). Based on this fixed template, users define resource pool design requirements and network requirements, and provide a description file for the network function virtualization infrastructure, including computing resource design, storage resource design, and network design.

[0087] The content of a resource pool design is shown in Table 2:

[0088]

[0089] Table 2

[0090] An example of resource pool design properties is provided below:

[0091] #Global Information

[0092]

[0093]

[0094]

[0095] In the above example, global parameters are specified in the global information to deploy software version information, which is used to call the corresponding software version during deployment.

[0096] Based on the user definition in step 42 and the data basis (hardware resource data) of step 41, in accordance with the definition of the unified resource pool data model, the software information part of the NFVI unified resource pool model is generated, and the hardware information in step 41 is summarized into a complete unified resource pool model containing software and hardware information.

[0097] In the prior art, each role and each deployment tool only accesses its own tool parameters; other parameters must be obtained through interaction with other roles. This embodiment of the present invention, through the definition of a unified resource pool data model, aggregates the parameters required by all roles and serves as input for all deployment tools. By aggregating the parameters of all relevant roles, this eliminates the manual steps required by the prior art for deployment tools to interact with and obtain parameters from other parties.

[0098] Furthermore, existing virtualization layer deployment tools and storage layer deployment tools often output different docking parameters, including file names, parameter names, and file paths, which increases tool adaptation difficulties. The data model in this embodiment further defines unified docking parameters, including the docking certificate name, certificate path, and the docking configuration file name and its absolute path. This allows the deployment and storage tools to output corresponding files according to these uniformly defined parameters, allowing the docking tool to automatically identify the file contents and perform docking.

[0099] By defining the docking parameters in a unified manner, the embodiment of the present invention avoids the problem in the prior art that, although the docking parameters output by deployment tools of different manufacturers have similar contents and functions, the docking process cannot be automatically implemented due to the inconsistency of the name paths, and manual adaptation is required one by one.

[0100] In step 44 above:

[0101] The output of step 43 includes a unified resource pool model of all hardware and software information. Because the model contains the information required by all tools, network tools, deployment tools, and docking tools can be called in sequence to flexibly deploy the resource pool.

[0102] In addition, the embodiment of the present invention mainly focuses on generating a unified data model based on resource pool attributes and then triggering the deployment process. The automated deployment tool belongs to the manufacturer's tool capabilities and will not be described in detail in this article.

[0103] As can be seen, the embodiments of the present invention optimize the resource pool data model, integrating all hardware and software information into a unified model. By aggregating information and optimizing the format, a unified resource pool data model is automatically recognized by various partner deployment tools. Furthermore, by executing code or inputting user configuration files, NFV infrastructure is built based on configurable data definitions (such as YAML files), achieving NFVI as code.

[0104] This embodiment of the present invention manages a unified infrastructure description file as code, allowing its contents to directly reflect the actual infrastructure situation and be directly applied throughout the planning, construction, and testing phases. In the context of NFV hardware and software decoupling, this eliminates the need for detailed interaction between roles, improving the efficiency of network cloud resource pool infrastructure construction. Furthermore, this embodiment of the present invention flexibly responds to user design requirements and design changes. Users do not need to understand the underlying hardware information or software implementation details; they only need to specify the overall design plan to build the infrastructure.

[0105] The above describes various methods of the embodiments of the present invention. The following further provides apparatuses for implementing the above methods.

[0106] Please refer to Figure 5 , an embodiment of the present invention provides a deployment device for a network function virtualization infrastructure, comprising:

[0107] A creation module 51 is configured to create a resource pool hardware description file according to a predefined unified resource pool data model, wherein the unified resource pool data model includes all software and hardware information of the resource pool and a unified data format in which the software and hardware information is presented;

[0108] A first generating module 52 is configured to generate a description file of a target NFVI according to the design requirements of a target network function virtualization infrastructure NFVI resource pool defined by a user;

[0109] A second generating module 53 is configured to generate a unified infrastructure description file that conforms to the unified resource pool data model for the target NFVI based on the resource pool hardware description file and the description file of the target NFVI, wherein the unified infrastructure description file includes software and hardware information of the target NFVI;

[0110] The calling module 54 is configured to call a deployment tool for the network function virtualization infrastructure, and use the unified infrastructure description file of the target NFVI as input to the deployment tool to deploy the target NFVI.

[0111] Optionally, the creation module is further configured to describe the infrastructure in the resource pool according to the hardware information in the unified resource pool data model and its unified data format, and obtain the resource pool hardware description file.

[0112] Optionally, the data content of the hardware information includes at least one of the following information: resource pool information, cabinet information in the computer room, hardware and port information of server equipment and network equipment, and network connection information.

[0113] Optionally, the first generation module is also used to receive the global information, computing resource planning information, storage resource planning information and network planning information of the target NFVI defined by the user according to a predefined NFVI description template; and generate a description file of the target NFVI based on the received global information, computing resource planning information, storage resource planning information and network planning information of the target NFVI.

[0114] Optionally, the second generation module is further used to generate software information of the target NFVI based on the resource pool hardware description file and the description file of the target NFVI and in accordance with the unified resource pool data model; and aggregate the software information of the target NFVI with the hardware information in the resource pool hardware description file to obtain a unified infrastructure description file of the target NFVI.

[0115] Optionally, the data content of the software information includes at least one of the following information: switch configuration information, resource pool host group information and node information list, management node list, storage pool information and storage node information list, and software docking parameters.

[0116] Optionally, the deployment tool includes a network tool, a storage deployment tool, a virtual layer deployment tool and a docking tool; the calling module is further used to call the network tool, storage deployment tool and virtual layer deployment tool, and use the unified infrastructure description file of the target NFVI as input to respectively deploy the network, storage and virtual layers of the target NFVI; call the docking tool to identify and dock the docking parameters output by the storage deployment tool and the virtual layer deployment tool to obtain the target NFVI.

[0117] Optionally, the calling module is also used to output the docking parameters output by the storage deployment tool and the virtual layer deployment tool to the corresponding docking configuration file in accordance with a uniformly defined parameter format, wherein the parameter format includes the docking certificate name, certificate path, the name of the docking configuration file and its absolute path; and call the docking tool to read and identify the docking parameters in the docking configuration file output by the storage deployment tool and the virtual layer deployment tool in accordance with the uniformly defined parameter format to perform the docking.

[0118] It should be noted that the device in this embodiment is the same as the above Figure 3 The device corresponding to the method shown, the implementation methods in the above embodiments are all applicable to the embodiments of the device, and can also achieve the same technical effects. The above device provided by the embodiment of the present invention can implement all the method steps implemented by the above method embodiment and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as those of the method embodiment will not be detailed here.

[0119] Please refer to Figure 6 , another structural diagram of a deployment device for a network function virtualization infrastructure provided by an embodiment of the present invention, the terminal includes: a processor 601, a transceiver 602, a memory 603, a user interface 604 and a bus interface.

[0120] In the embodiment of the present invention, the terminal further includes: a program stored in the memory 603 and executable on the processor 601 .

[0121] When the processor 601 executes the program, the following steps are implemented:

[0122] Creating a resource pool hardware description file according to a predefined unified resource pool data model, wherein the unified resource pool data model includes all software and hardware information of the resource pool and a unified data format in which the software and hardware information is presented;

[0123] Generate a target NFVI description file based on the design requirements of the target NFVI resource pool defined by the user;

[0124] generating a unified infrastructure description file for the target NFVI according to the resource pool hardware description file and the description file of the target NFVI, the unified infrastructure description file conforming to the unified resource pool data model, the unified infrastructure description file including software and hardware information of the target NFVI;

[0125] A deployment tool for a network function virtualization infrastructure is called, and the unified infrastructure description file of the target NFVI is used as input to the deployment tool to deploy the target NFVI.

[0126] Optionally, when executing the program, the processor further implements the following steps:

[0127] According to the hardware information in the unified resource pool data model and its unified data format, the infrastructure in the resource pool is described to obtain the resource pool hardware description file.

[0128] Optionally, the data content of the hardware information includes resource pool information, cabinet information in the computer room, hardware and port information of server equipment and network equipment, and network connection information.

[0129] Optionally, when executing the program, the processor further implements the following steps:

[0130] Receive the global information, computing resource planning information, storage resource planning information and network planning information of the target NFVI defined by the user according to the predefined NFVI description template; generate a description file of the target NFVI based on the received global information, computing resource planning information, storage resource planning information and network planning information of the target NFVI.

[0131] Optionally, when executing the program, the processor further implements the following steps:

[0132] generating software information of the target NFVI according to the resource pool hardware description file and the description file of the target NFVI and in accordance with the unified resource pool data model;

[0133] The software information of the target NFVI is aggregated with the hardware information in the resource pool hardware description file to obtain a unified infrastructure description file of the target NFVI.

[0134] Optionally, the data content of the software information includes at least one of the following information: switch configuration information, resource pool host group information and node information list, management node list, storage pool information and storage node information list, and software docking parameters.

[0135] Optionally, the deployment tool includes a network tool, a storage deployment tool, a virtual layer deployment tool, and a docking tool; when the processor executes the program, the processor further implements the following steps:

[0136] Invoking the network tool, storage deployment tool, and virtual layer deployment tool, taking the unified infrastructure description file of the target NFVI as input, and respectively deploying the network, storage, and virtual layers of the target NFVI;

[0137] The docking tool is called to identify and dock the docking parameters output by the storage deployment tool and the virtual layer deployment tool to obtain the target NFVI.

[0138] Optionally, when executing the program, the processor further implements the following steps:

[0139] Output the docking parameters output by the storage deployment tool and the virtual layer deployment tool to the corresponding docking configuration file according to a uniformly defined parameter format, wherein the parameter format includes the docking certificate name, certificate path, and the name and absolute path of the docking configuration file;

[0140] The docking tool is called to read and identify the docking parameters in the docking configuration files output by the storage deployment tool and the virtual layer deployment tool according to the uniformly defined parameter format, and perform the docking.

[0141] It is understandable that in the embodiment of the present invention, when the computer program is executed by the processor 601, the above Figure 3 The various processes of the method embodiment shown can achieve the same technical effect, and to avoid repetition, they will not be described again here.

[0142] exist Figure 6 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 601 and memory represented by memory 603. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 602 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium. For different user devices, the user interface 604 may also be an interface capable of connecting external or internal devices as required, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, etc.

[0143] The processor 601 is responsible for managing the bus architecture and general processing, and the memory 603 can store data used by the processor 601 when performing operations.

[0144] It should be noted that the device in this embodiment is the same as the above Figure 3 The device corresponding to the method shown in the embodiment is applicable to the implementation methods in the above embodiments and can achieve the same technical effects. In the device, the transceiver 602 and the memory 603, as well as the transceiver 602 and the processor 601, can be communicatively connected via a bus interface. The functions of the processor 601 can also be implemented by the transceiver 602, and the functions of the transceiver 602 can also be implemented by the processor 601. It should be noted that the above-mentioned device provided by the embodiment of the present invention can implement all the method steps implemented by the above-mentioned method embodiment and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as those of the method embodiment will not be detailed here.

[0145] In some embodiments of the present invention, a computer-readable storage medium is further provided, on which a program is stored. When the program is executed by a processor, the following steps are implemented:

[0146] Creating a resource pool hardware description file according to a predefined unified resource pool data model, wherein the unified resource pool data model includes all software and hardware information of the resource pool and a unified data format in which the software and hardware information is presented;

[0147] Generate a target NFVI description file based on the design requirements of the target NFVI resource pool defined by the user;

[0148] generating a unified infrastructure description file for the target NFVI according to the resource pool hardware description file and the description file of the target NFVI, the unified infrastructure description file conforming to the unified resource pool data model, the unified infrastructure description file including software and hardware information of the target NFVI;

[0149] A deployment tool for a network function virtualization infrastructure is called, and the unified infrastructure description file of the target NFVI is used as input to the deployment tool to deploy the target NFVI.

[0150] When the program is executed by the processor, it can implement all the implementation methods of the above-mentioned network function virtualization infrastructure deployment method and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0151] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present invention.

[0152] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0153] In the embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0154] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected according to actual needs to achieve the objectives of the embodiments of the present invention.

[0155] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0156] If the functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the portion that contributes to the prior art, or the portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned storage medium includes various media that can store program code, such as a USB flash drive, a mobile hard drive, ROM, RAM, a magnetic disk, or an optical disk.

[0157] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. A method for deploying a network function virtualization infrastructure, characterized in that: include: Creating a resource pool hardware description file according to a predefined unified resource pool data model, wherein the unified resource pool data model includes all software and hardware information of the resource pool and a unified data format in which the software and hardware information is presented; Generate a target NFVI description file based on the design requirements of the target NFVI resource pool defined by the user; generating a unified infrastructure description file for the target NFVI according to the resource pool hardware description file and the description file of the target NFVI, the unified infrastructure description file conforming to the unified resource pool data model, the unified infrastructure description file including software and hardware information of the target NFVI; Invoking a deployment tool of a network function virtualization infrastructure, and using the unified infrastructure description file of the target NFVI as input to the deployment tool, to deploy the target NFVI; The step of generating a unified infrastructure description file that conforms to the unified resource pool data model for the target NFVI based on the resource pool hardware description file and the description file of the target NFVI includes: generating software information of the target NFVI based on the resource pool hardware description file and the description file of the target NFVI and in accordance with the unified resource pool data model; and aggregating the software information of the target NFVI with the hardware information in the resource pool hardware description file to obtain the unified infrastructure description file of the target NFVI.

2. The method according to claim 1, wherein The step of creating a resource pool hardware description file according to a predefined unified resource pool data model includes: According to the hardware information in the unified resource pool data model and its unified data format, the infrastructure in the resource pool is described to obtain the resource pool hardware description file.

3. The method according to claim 2, wherein The data content of the hardware information includes at least one of the following information: resource pool information, cabinet information in the computer room, hardware and port information of server equipment and network equipment, and network connection information.

4. The method according to claim 1, wherein The generating of a target NFVI description file according to the design requirements of the target network function virtualization infrastructure NFVI resource pool defined by the user includes: Receive the global information, computing resource planning information, storage resource planning information, and network planning information of the target NFVI defined by the user according to the predefined NFVI description template; Generate a description file of the target NFVI based on the received global information, computing resource planning information, storage resource planning information and network planning information of the target NFVI.

5. The method according to claim 1, wherein The data content of the software information includes at least one of the following information: switch configuration information, resource pool host group information and node information list, management node list, storage pool information and storage node information list, and software docking parameters.

6. The method according to claim 1, wherein The deployment tool includes a network tool, a storage deployment tool, a virtual layer deployment tool, and a docking tool. The deployment tool for the network function virtualization infrastructure is called, and the unified infrastructure description file of the target NFVI is used as input to the deployment tool to deploy the target NFVI, including: Invoking the network tool, storage deployment tool, and virtual layer deployment tool, taking the unified infrastructure description file of the target NFVI as input, and respectively deploying the network, storage, and virtual layers of the target NFVI; The docking tool is called to identify and dock the docking parameters output by the storage deployment tool and the virtual layer deployment tool to obtain the target NFVI.

7. The method according to claim 6, wherein The calling of the docking tool, identifying and docking the docking parameters output by the storage deployment tool and the virtual layer deployment tool, and obtaining the target NFVI includes: Output the docking parameters output by the storage deployment tool and the virtual layer deployment tool to the corresponding docking configuration file according to a uniformly defined parameter format, wherein the parameter format includes the docking certificate name, certificate path, and the name and absolute path of the docking configuration file; The docking tool is called to read and identify the docking parameters in the docking configuration files output by the storage deployment tool and the virtual layer deployment tool according to the uniformly defined parameter format, and perform the docking.

8. A network function virtualization infrastructure deployment device, characterized in that: include: A creation module, configured to create a resource pool hardware description file according to a predefined unified resource pool data model, wherein the unified resource pool data model includes all software and hardware information of the resource pool and a unified data format in which the software and hardware information is presented; The first generation module is configured to generate a description file of a target NFVI according to the design requirements of a target network function virtualization infrastructure NFVI resource pool defined by a user; a second generating module, configured to generate a unified infrastructure description file for the target NFVI that conforms to the unified resource pool data model based on the resource pool hardware description file and the description file of the target NFVI, wherein the unified infrastructure description file includes software and hardware information of the target NFVI; A calling module is configured to call a deployment tool of a network function virtualization infrastructure, and use the unified infrastructure description file of the target NFVI as input to the deployment tool to deploy the target NFVI; The second generation module is further configured to generate software information of the target NFVI based on the resource pool hardware description file and the target NFVI description file and in accordance with the unified resource pool data model; and aggregate the software information of the target NFVI with the hardware information in the resource pool hardware description file to obtain a unified infrastructure description file of the target NFVI.

9. A deployment device for a network function virtualization infrastructure, characterized in that: include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the method according to any one of claims 1 to 7.

Images