CN115412440A

CN115412440A - VNF device distributed deployment method and device

Info

Publication number: CN115412440A
Application number: CN202210996570.5A
Authority: CN
Inventors: 郭雷
Original assignee: Inspur Cisco Networking Technology Co Ltd
Current assignee: Inspur Cisco Networking Technology Co Ltd
Priority date: 2022-08-19
Filing date: 2022-08-19
Publication date: 2022-11-29
Anticipated expiration: 2042-08-19
Also published as: CN115412440B

Abstract

The embodiment of the application discloses a VNF device distributed deployment method and device. Analyzing the received VNF configuration model through a model analysis engine; the VNF configuration model comprises basic configuration node information and network element type node information; based on the analysis result, acquiring the group number of the anti-affinity group corresponding to the VNF equipment to be deployed currently, and determining information of other VNF equipment in the anti-affinity group based on the group number of the anti-affinity group; wherein the device labels of the plurality of VNF devices in the same anti-affinity group are different from each other; and acquiring a network element description file of an anti-affinity group corresponding to the current VNF device to be deployed, and respectively deploying the current VNF device to be deployed and other VNF devices in the anti-affinity group on different computing node servers under the condition that the network element description file is determined to be introduced into the anti-affinity strategy. By the method, the problem of unbalanced load of the computing node server is solved.

Description

VNF device distributed deployment method and device

Technical Field

The present application relates to the field of communications devices, and in particular, to a distributed VNF device deployment method and device.

Background

A VNF Manager (virtual Network Function Manager) is a VNF deployment, configuration, and life cycle management system that conforms to ETSI NFV specifications, and can manage a plurality of physical servers through a cloud host, and flexibly configure required resources according to user service requirements, thereby completing creation and deployment of VNF devices. Meanwhile, the VNF Manager can establish connection with the VNF device through protocols such as Netconf and Telnet, and issue the required initial configuration to the VNF device, so as to ensure that the VNF device performs life cycle management on the VNF device after being started.

In the prior art, a cloud host is generally selected according to a control node and an available domain computing node, and a cloud host server where a VNF to be deployed is located is determined. And the VNF Manager abstracts the VNF Descriptor network element description file with the custom attribute value according to the selection of the user, analyzes parameters in the VNF Descriptor according to the specified VNF Descriptor network element description file, and then informs the cloud host to rapidly deploy a type of VNF equipment with the custom attribute.

However, in the prior art, in a mode that the VNF Manager collects and randomly allocates according to the load use condition of the current computing node, it is difficult to ensure distributed deployment of VNF devices, so that the problem of unbalanced server load of the computing node is likely to occur.

Disclosure of Invention

The embodiment of the application provides a VNF device distributed deployment method and device, which are used for solving the following technical problems: the existing VNF equipment deployment is easy to cause the problem of unbalanced load of a computing node server.

The embodiment of the application adopts the following technical scheme:

the embodiment of the application provides a VNF device distributed deployment method. Analyzing a received VNF configuration model through a model analysis engine; the VNF configuration model comprises basic configuration node information and network element type node information; based on the analysis result, acquiring a group number of an inverse affinity group corresponding to the VNF equipment to be deployed currently, and determining information of other VNF equipment in the inverse affinity group based on the group number of the inverse affinity group; wherein the device labels of the plurality of VNF devices in the same anti-affinity group are different from each other; and acquiring a network element description file of a reverse affinity group corresponding to the current VNF device to be deployed, and respectively deploying the current VNF device to be deployed and other VNF devices in the reverse affinity group on different computing node servers under the condition that the network element description file is determined to introduce a reverse affinity strategy.

According to the embodiment of the application, the received VNF configuration model is analyzed through the model analysis engine, static resources required by different types and different quantities of VNF equipment to be deployed can be prepared at one time, preparation is made for rapid deployment of the VNF, and the overall deployment process of the VNF equipment is greatly simplified. Secondly, by constructing the inverse affinity group and introducing the inverse affinity policy, the embodiment of the application can distribute and deploy a plurality of VNF devices using the same VNF Descriptor introduced with the inverse affinity policy on different computing node servers, thereby solving the problem of unbalanced load of the computing node servers.

In an implementation manner of the present application, the deploying of the current VNF device to be deployed and other VNF devices in the anti-affinity group are respectively deployed on different computing node servers, which specifically includes: determining deployed VNF equipment corresponding to the same network element description file with current VNF equipment to be deployed; acquiring reference computing node information respectively corresponding to deployed VNF equipment, and deleting the reference computing node information; and screening out one computing node from the rest computing nodes based on a load balancing algorithm so as to deploy the VNF equipment to be deployed currently.

In an implementation manner of the present application, after obtaining a network element description file of an anti-affinity group corresponding to a current VNF device to be deployed, the method further includes: and constructing an inverse affinity attribute in the network element description file, determining an attribute value corresponding to the inverse affinity attribute, and determining inverse affinity strategies of the VNF devices corresponding to the network element description file on the basis of the attribute value corresponding to the inverse affinity attribute.

In an implementation manner of the present application, before obtaining a network element description file of an anti-affinity group corresponding to a current VNF device to be deployed, the method further includes: performing anti-affinity group number detection on the deployed VNF equipment; in the deployed VNF device, if there is a reference VNF device having the same anti-affinity group number as the current VNF device to be deployed, the network element description file of the reference VNF device is used as the network element description file of the VNF device to be deployed.

In an implementation manner of the present application, before parsing, by a model parsing engine, a received VNF configuration model, the method further includes: constructing basic configuration node information based on basic configuration parameters of VNF equipment to be deployed; the basic configuration parameters at least comprise one or more of control channel VLAN and network segments, data channel VLAN and network segments, the number of various VNF devices and label ranges corresponding to the various VNF devices among the VNF devices; constructing network element type node information based on the category parameters of the VNF equipment to be deployed; the category parameters at least comprise one or more of the CPU core number, the memory size, the hard disk size, the interface name and the interface type of the VNF equipment; and constructing a VNF configuration model based on the basic configuration node information and the network element type node information.

In an implementation manner of the present application, after the VNF configuration model is constructed based on the basic configuration node information and the network element type node information, the method further includes: and constructing the VNF configuration model into a uniform format file, and uploading the uniform format file to a VNF Manager system.

In an implementation manner of the present application, before parsing, by a model parsing engine, a received VNF configuration model, the method further includes: dividing the VNF equipment to be deployed into a plurality of classes based on the class parameters of the VNF equipment to be deployed; determining equipment labels respectively corresponding to VNF equipment to be deployed in each category; and dividing a plurality of VNF devices to be deployed with different device labels in each category into the same anti-affinity group, and labeling each anti-affinity group with a group number.

In one implementation of the present application, determining information of other VNF devices in the anti-affinity group based on the anti-affinity group number specifically includes: determining a plurality of equipment labels corresponding to the anti-affinity group number; other VNF device information within the anti-affinity group is determined based on the plurality of device labels.

In an implementation manner of the present application, after parsing, by a model parsing engine, a received VNF configuration model, the method further includes: determining the sequence of the analyzed information of the plurality of VNF devices to be deployed; creating a service deployment workflow; and deploying the plurality of VNF devices to be deployed based on the sequence of the service deployment workflow and the analyzed information of the plurality of VNF devices to be deployed.

An embodiment of the present application provides a VNF device distributed deployment device, including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to cause the at least one processor to: analyzing the received VNF configuration model through a model analysis engine; the VNF configuration model comprises basic configuration node information and network element type node information; based on the analysis result, acquiring a group number of an anti-affinity group corresponding to the VNF equipment to be deployed currently, and determining information of other VNF equipment in the anti-affinity group based on the anti-affinity group number; wherein the device labels of the plurality of VNF devices in the same anti-affinity group are different from each other; and acquiring a network element description file of an anti-affinity group corresponding to the current VNF device to be deployed, and respectively deploying the current VNF device to be deployed and other VNF devices in the anti-affinity group on different computing node servers under the condition that the network element description file is determined to be introduced into the anti-affinity strategy.

The embodiment of the application adopts at least one technical scheme which can achieve the following beneficial effects: according to the embodiment of the application, the received VNF configuration model is analyzed through the model analysis engine, static resources required by different types and different quantities of VNF equipment to be deployed can be prepared at one time, preparation is made for rapid deployment of the VNF, and the overall deployment process of the VNF equipment is greatly simplified. Secondly, by constructing the inverse affinity group and introducing the inverse affinity policy, the embodiment of the application can distribute and deploy a plurality of VNF devices using the same VNF Descriptor introducing the inverse affinity policy on different computing node servers, thereby solving the problem of unbalanced load of the computing node servers.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort. In the drawings:

fig. 1 is a flowchart of a distributed VNF device deployment method according to an embodiment of the present disclosure;

fig. 2 is a schematic structural diagram of a distributed VNF device deployment device according to an embodiment of the present disclosure.

Detailed Description

The embodiment of the application provides a VNF device distributed deployment method and device.

In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without making any inventive step based on the embodiments of the present disclosure, shall fall within the scope of protection of the present disclosure.

In the prior art, a cloud host is generally selected according to a control node, an available domain or a computing node, and a cloud host server where a VNF to be deployed is located is determined. The VNF Manager abstracts the VNF Descriptor network element description file with the custom attribute value according to user selection, and according to the specified VNF Descriptor network element description file, the VNF Manager analyzes parameters in the VNF Descriptor and then informs the cloud host to rapidly deploy one type of VNF equipment with the custom attribute.

In order to solve the foregoing problems, embodiments of the present application provide a distributed VNF device deployment method and device. The received VNF configuration model is analyzed through the model analysis engine, static resources required by different types and different quantities of VNF equipment to be deployed can be prepared at one time, preparation is made for rapid deployment of the VNF, and the overall deployment process of the VNF equipment is greatly simplified. Secondly, by constructing the inverse affinity group and introducing the inverse affinity policy, the embodiment of the application can distribute and deploy a plurality of VNF devices using the same VNF Descriptor introduced with the inverse affinity policy on different computing node servers, thereby solving the problem of unbalanced load of the computing node servers.

The technical solutions proposed in the embodiments of the present application are described in detail below with reference to the accompanying drawings.

Fig. 1 is a flowchart of a distributed VNF device deployment method according to an embodiment of the present application. As shown in fig. 1, the distributed VNF device deployment method includes the following steps:

s101, analyzing the received VNF configuration model through a model analysis engine, wherein the VNF configuration model comprises basic configuration node information and network element type node information.

In an embodiment of the present application, basic configuration node information is constructed based on basic configuration parameters of VNF devices to be deployed, where the basic configuration parameters at least include one or more of control channel VLANs and network segments, data channel VLANs and network segments between the VNF devices, the number of each type of VNF device, and label ranges corresponding to each type of VNF device. And constructing network element type node information based on the category parameters of the VNF equipment to be deployed, wherein the category parameters at least comprise one or more of the CPU core number, the memory size, the hard disk size, the interface name and the interface type of the VNF equipment. And constructing a VNF configuration model based on the basic configuration node information and the network element type node information.

Specifically, in order to implement rapid deployment, in the embodiment of the present application, instead of selecting configuration parameters in a deployment process of each VNF, a Yang file is used to define all configuration models of VNFs to be deployed in a deployment process, where two types of nodes need to be defined in the models: a basic configuration node and a network element type node.

Further, the basic configuration node mainly includes some basic configuration parameters, such as control channel VLAN and network segment, data channel VLAN and network segment, number of various VNFs and label range thereof among VNF devices. The VNF device labels are unique labels of each VNF in one-time deployment service, each type of VNF device plans a certain VNF label range, VNF device label ranges among different VNF devices cannot have intersection, and the number of VNF devices corresponds to the VNF label ranges one to one.

Further, the network element type node is mainly used to define configuration parameter information of a certain type of VNF device, such as the number of CPU cores, the size of memory, the size of hard disk, the name of interface, the type of interface, and the like. The number of VNF type nodes corresponds to the kind of VNF device to be deployed.

In an embodiment of the application, the VNF configuration model is constructed as a uniform format file, and the uniform format file is uploaded to the VNF Manager system.

Specifically, after the model definition is completed, the model files are packaged into a VNF package in a specific format, and uploaded to a VNF Manager to be identified and analyzed by a model analysis engine.

By defining the VNF configuration model and constructing the VNF Package in the uniform format, the static resources required by different types and quantities of VNF equipment to be deployed can be prepared at one time, preparation is made for rapid deployment of the VNF, and the overall deployment process of the VNF equipment is greatly simplified.

In an embodiment of the application, the VNF devices to be deployed are divided into multiple categories based on category parameters of the VNF devices to be deployed, and device labels corresponding to the VNF devices to be deployed in each category are determined. And dividing a plurality of VNF devices to be deployed with different device labels in each category into the same anti-affinity group, and labeling each anti-affinity group with a group number.

Specifically, the problem of unbalanced load of the computing node server is easily caused by selecting the cloud host according to the computing nodes during distributed deployment. Therefore, a problem that how to ensure that every two VNF devices are stacked to form a primary device and the secondary device are distributed and deployed in different servers when the VNF devices are deployed according to a control node or an available domain is to be solved.

Further, in the embodiment of the present application, a reverse affinity group is introduced for VNF devices of the same type, and it is required that two VNF devices belonging to the same reverse affinity group form a primary and secondary stack and are distributed in different servers, that is, VNF devices in the same reverse affinity group have reverse affinity with each other.

Further, each anti-affinity group is correspondingly provided with an unique identification of an anti-affinity group number, and each anti-affinity group can include two VNF devices with different device labels, so that various VNF devices required to be deployed in a distributed manner are guaranteed to belong to different anti-affinity groups. And two VNF devices with the same anti-affinity group number belong to the same anti-affinity group.

It should be noted that, in the embodiment of the present application, it is preferable to divide two VNFs with different device labels into the same anti-affinity group, and in an application, the number of VNF devices in one anti-affinity group may be adjusted according to an actual situation, which is not limited in the embodiment of the present application.

And S102, acquiring a group number of an inverse affinity group corresponding to the current VNF device to be deployed based on the analysis result, and determining information of other VNF devices in the inverse affinity group based on the group number of the inverse affinity group, wherein the device labels of a plurality of VNF devices in the same inverse affinity group are different from each other.

In one embodiment of the present application, a plurality of device designations corresponding to the anti-affinity group number are determined. Other VNF device information within the anti-affinity group is determined based on the plurality of device labels.

Specifically, the model parsing engine parses the VNF Package, and determines the inverse affinity group to which the VNF device belongs according to the VNF device label. After the anti-affinity group is determined, a plurality of VNF devices in the anti-affinity group are determined according to the group number of the anti-affinity group. The multiple VNF devices in the same anti-affinity group are master devices and slave devices.

S103, acquiring a network element description file of an anti-affinity group corresponding to the current VNF device to be deployed, and respectively deploying the current VNF device to be deployed and other VNF devices in the anti-affinity group on different computing node servers under the condition that the anti-affinity policy is introduced into the network element description file.

In an embodiment of the present application, an inverse affinity attribute is constructed in a network element description file, and an attribute value corresponding to the inverse affinity attribute is determined, so as to determine an inverse affinity policy of a plurality of VNF devices corresponding to the network element description file based on the attribute value corresponding to the inverse affinity attribute.

Specifically, the VNF Manager can abstract a VNF Descriptor network element description file including custom specification attributes such as mirror image, hardware configuration, interface binding, and the like, and accordingly create a type of VNF having the custom specification attributes. And newly introducing the anti-affinity attribute into the VNF Descriptor network element description file, and defining that a counter-affinity strategy is introduced into the VNF Descriptor when the value of the anti-affinity attribute is true, namely that all VNF devices using the VNF Descriptor have counter-affinity mutually.

In an embodiment of the present application, performing anti-affinity group number detection on deployed VNF devices, and in the deployed VNF devices, when a reference VNF device having the same anti-affinity group number as a current VNF device to be deployed exists, taking a network element description file of the reference VNF device as a network element description file of the VNF device to be deployed.

Specifically, in a process of deploying each VNF device by the VNF Manager, a group number of a corresponding anti-affinity group is determined according to a VNF device label, and if it is detected that an anti-affinity group number of a certain VNF device in the deployed VNF devices is the same as that of a VNF device to be currently deployed, a VNF Descriptor that is the same as the VNF Descriptor is used, otherwise, a VNF Descriptor is newly created. That is, multiple VNF devices of the same anti-affinity group are deployed, and the same VNF Descriptor introducing the anti-affinity policy is used.

In an embodiment of the application, a sequence of the analyzed pieces of VNF device information to be deployed is determined, and a service deployment workflow is created. And deploying the plurality of VNF devices to be deployed based on the sequence of the service deployment workflow and the analyzed information of the plurality of VNF devices to be deployed.

Specifically, the VNF Manager analyzes the received basic configuration node and network element type node of the configuration model through the model analysis engine, sequentially calculates the anti-affinity group numbers of each VNF device, and divides the VNF devices into different anti-affinity groups. And finally abstracting the corresponding VNF Descriptor and introducing an inverse affinity strategy. And after the model analysis is completed, creating a service deployment workflow, and preparing to create the VNF according to the abstracted VNF Descriptor in sequence.

Further, after a specific physical server is decided, the VNF Manager enters a VNF creation process, and a part of configuration in the VNF Descriptor is converted into an initial configuration file and stored in a certain agreed location, which is usually hung as a disk drive in a virtual device. The startup process of the VNF mounting the mirrored operating system reads the initial configuration file and executes it one by one.

In an embodiment of the present application, deployed VNF devices corresponding to the same network element description file as a VNF device to be currently deployed are determined. And acquiring reference computing node information respectively corresponding to the deployed VNF devices, and excluding the reference computing node information. Based on a load balancing algorithm, one computing node is screened out from the rest computing nodes so as to deploy the VNF equipment to be deployed currently.

Specifically, the VNF Manager, as a Manager of the VNF device resources, may collect computing nodes of all cloud hosts managed by the VNF Manager, and load conditions of the computing nodes, where the load includes the number of VNFs started on the physical server, a memory utilization rate, a CPU utilization rate, and the like.

Further, after the anti-affinity policy is introduced in the embodiment of the present application, if the VNF Manager identifies that the anti-affinity attribute value of the specified VNF Descriptor is true, it first checks whether VNF devices using the same VNF Descriptor exist in the currently deployed VNF, and if so, obtains a computing node where the specified VNF is located, and excludes the computing node from the cloud host computing nodes queried according to the control node or the available domain. And then, according to the existing load balancing algorithm, a proper physical server is decided from other available computing nodes, so that a plurality of VNF devices of the same VNF Descriptor introducing the inverse affinity strategy are distributed and deployed on different computing node servers.

Further, the steps are repeatedly executed according to the number of different types of VNFs defined in the model until all VNF devices are created, and finally, model-driven VNF inverse affinity distributed rapid deployment is achieved.

In an embodiment of the present application, since a unified internal control channel and an internal data channel are configured between created VNF devices, network connectivity can be established even if the VNF devices are distributed in different computing nodes. Two VNFs of the same anti-affinity group are deployed on different servers to construct a main-standby stack, VNF devices which are started preferentially serve as main devices, VNFs of the other VNFs serve as standby devices, and reliable operation of VNF device functions is guaranteed.

By defining a VNF configuration model and constructing a VNF Package in a uniform format, static resources required by different types and different quantities of VNF devices to be deployed can be prepared at one time, preparation is made for rapid deployment of the VNF, and the overall deployment process of the VNF devices is greatly simplified. Secondly, by defining a calculation method of an anti-affinity group and an anti-affinity group number, the embodiment of the application can calculate the anti-affinity group to which the VNF device belongs according to the VNF device label classification, VNF devices in the same anti-affinity group are master and slave, and each anti-affinity group abstracts a corresponding VNF Descriptor and introduces an anti-affinity policy. And then, a plurality of VNF devices using the same VNF Descriptor introducing the inverse affinity strategy are distributed and deployed on different computing node servers through the VNF Manager. In addition, in the deployment process of the embodiment of the application, only the deployment mode that the cloud host is selected according to the control node or the available domain needs to be selected once, and the VNF Manager can automatically select different computing nodes for all the VNF devices to be deployed according to the inverse affinity policy, so that the problem that a user needs to select different computing nodes and load imbalance respectively when deploying the VNF each time is avoided, and user interaction operation is reduced.

Fig. 2 is a schematic structural diagram of a distributed VNF device deployment device according to an embodiment of the present application. As shown in fig. 2, a VNF device distributed deployment device includes:

at least one processor; and the number of the first and second groups,

a memory communicatively coupled to the at least one processor; wherein,

the memory stores instructions executable by the at least one processor to enable the at least one processor to:

analyzing the received VNF configuration model through a model analysis engine; the VNF configuration model comprises basic configuration node information and network element type node information;

based on the analysis result, acquiring a group number of an anti-affinity group corresponding to the VNF equipment to be deployed currently, and determining information of other VNF equipment in the anti-affinity group based on the group number of the anti-affinity group; wherein the device labels of the plurality of VNF devices in the same anti-affinity group are different from each other;

and acquiring a network element description file of a reverse affinity group corresponding to the current VNF device to be deployed, and respectively deploying the current VNF device to be deployed and other VNF devices in the reverse affinity group on different computing node servers under the condition that a reverse affinity policy is introduced into the network element description file.

The embodiments in the present application are described in a progressive manner, and the same and similar parts among the embodiments can be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the embodiments of the apparatus, the device, and the nonvolatile computer storage medium, since they are substantially similar to the embodiments of the method, the description is simple, and for the relevant points, reference may be made to the partial description of the embodiments of the method.

The foregoing description of specific embodiments of the present application has been presented. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art to which the embodiments of the present application pertain. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the embodiments of the present application should be included in the scope of the claims of the present application.

Claims

1. A VNF device distributed deployment method, the method comprising:

based on the analysis result, acquiring a group number of an inverse affinity group corresponding to the VNF equipment to be deployed currently, and determining information of other VNF equipment in the inverse affinity group based on the group number of the inverse affinity group; wherein the device labels of the plurality of VNF devices in the same anti-affinity group are different from each other;

and acquiring a network element description file of an anti-affinity group corresponding to the current VNF device to be deployed, and respectively deploying the current VNF device to be deployed and other VNF devices in the anti-affinity group on different computing node servers under the condition that the network element description file is determined to be introduced into an anti-affinity strategy.

2. The distributed deployment method of VNF devices of claim 1, wherein the respectively deploying the current VNF device to be deployed and other VNF devices in the anti-affinity group on different computing node servers specifically comprises:

determining deployed VNF equipment corresponding to the same network element description file with the current VNF equipment to be deployed;

acquiring reference computing node information respectively corresponding to the deployed VNF devices, and excluding the reference computing node information;

and based on a load balancing algorithm, screening out one computing node from the rest computing nodes so as to deploy the VNF equipment to be deployed currently.

3. The distributed deployment method of VNF devices of claim 1, wherein after the network element description file of the anti-affinity group corresponding to the current VNF device to be deployed is obtained, the method further comprises:

and constructing an inverse affinity attribute in the network element description file, determining an attribute value corresponding to the inverse affinity attribute, and determining an inverse affinity policy of the plurality of VNF devices corresponding to the network element description file based on the attribute value corresponding to the inverse affinity attribute.

4. The distributed deployment method of VNF devices of claim 1, wherein before the obtaining the network element description file of the anti-affinity group corresponding to the current VNF device to be deployed, the method further comprises:

performing anti-affinity group number detection on the deployed VNF equipment;

and in the deployed VNF equipment, when reference VNF equipment with the same anti-affinity group number as the current VNF equipment to be deployed exists, taking the network element description file of the reference VNF equipment as the network element description file of the VNF equipment to be deployed.

5. The distributed deployment method of VNF devices of claim 1, wherein before parsing the received VNF configuration model by the model parsing engine, the method further comprises:

constructing the basic configuration node information based on the basic configuration parameters of the VNF equipment to be deployed; the basic configuration parameters at least comprise one or more of control channel VLAN and network segments, data channel VLAN and network segments, the number of various VNF devices and label ranges corresponding to the various VNF devices among the VNF devices; and

constructing the network element type node information based on the category parameters of the VNF equipment to be deployed; the category parameters at least comprise one or more of the CPU core number, the memory size, the hard disk size, the interface name and the interface type of the VNF equipment;

and constructing the VNF configuration model based on the basic configuration node information and the network element type node information.

6. The distributed deployment method of VNF devices of claim 5, wherein after the constructing the VNF configuration model based on the basic configuration node information and the network element type node information, the method further comprises:

and constructing the VNF configuration model into a uniform format file, and uploading the uniform format file to a VNF Manager system.

7. The distributed deployment method of VNF devices of claim 5, wherein before parsing the received VNF configuration model by the model parsing engine, the method further comprises:

dividing VNF equipment to be deployed into a plurality of classes based on class parameters of the VNF equipment to be deployed;

determining equipment labels respectively corresponding to VNF equipment to be deployed in each category;

and dividing a plurality of VNF devices to be deployed with different device labels in each category into the same anti-affinity group, and labeling each anti-affinity group with a group number.

8. The distributed deployment method of VNF devices of claim 7, wherein the determining information of other VNF devices in the anti-affinity group based on the group number of the anti-affinity group specifically includes:

determining a plurality of device labels corresponding to the anti-affinity group number;

determining other VNF device information within the anti-affinity group based on the plurality of device labels.

9. The distributed deployment method of VNF devices of claim 1, wherein after parsing the received VNF configuration model by the model parsing engine, the method further comprises:

determining the sequence of the analyzed information of the plurality of VNF devices to be deployed;

creating a service deployment workflow;

and deploying the plurality of VNF devices to be deployed based on the sequence of the service deployment workflow and the analyzed information of the plurality of VNF devices to be deployed.

10. A VNF device distributed deployment device, comprising:

at least one processor; and the number of the first and second groups,

a memory communicatively coupled to the at least one processor; wherein,