CN115412440B - Distributed deployment method and device for VNF (virtual network function) device - Google Patents
Distributed deployment method and device for VNF (virtual network function) device Download PDFInfo
- Publication number
- CN115412440B CN115412440B CN202210996570.5A CN202210996570A CN115412440B CN 115412440 B CN115412440 B CN 115412440B CN 202210996570 A CN202210996570 A CN 202210996570A CN 115412440 B CN115412440 B CN 115412440B
- Authority
- CN
- China
- Prior art keywords
- vnf
- deployed
- equipment
- affinity
- affinity group
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 33
- 238000002372 labelling Methods 0.000 claims description 3
- 238000012216 screening Methods 0.000 claims description 3
- 238000001514 detection method Methods 0.000 claims description 2
- 238000002360 preparation method Methods 0.000 description 5
- 230000003068 static effect Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000012163 sequencing technique Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/14—Network analysis or design
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the application discloses a distributed deployment method and device for VNF equipment. 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; acquiring the group number of the anti-affinity group corresponding to the current VNF equipment to be deployed based on the analysis result, and determining the 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 a plurality of VNF devices in the same anti-affinity group are different from each other; acquiring a network element description file of an anti-affinity group corresponding to the current VNF equipment to be deployed, and respectively deploying the current VNF equipment to be deployed and other VNF equipment in the anti-affinity group on different computing node servers under the condition that the network element description file is determined to introduce an anti-affinity strategy. By the method, the problem of unbalanced load of the computing node server is solved.
Description
Technical Field
The present application relates to the field of communications devices, and in particular, to a distributed deployment method and device for VNF devices.
Background
VNF MANAGER (Virtualised Network Function Manager) is a VNF deployment, configuration and lifecycle management system that conforms to the ETSI NFV specification, and is capable of managing multiple physical servers through a cloud host, flexibly configuring required resources according to user service requirements, and completing creation and deployment of VNF devices. Meanwhile, VNF MANAGER can establish connection with the VNF device through Netconf, telnet and other protocols, and issue required initial configuration to the VNF device, so as to ensure that life cycle management is performed on the VNF device after the VNF device is started.
In the prior art, a cloud host is generally selected according to a control node and an available domain computing node mode, and a cloud host server where the VNF to be deployed is located is determined. VNF MANAGER abstracting a VNF Descriptor network element description file with a custom attribute value according to user selection, analyzing parameters in the VNF Descriptor by VNF MANAGER according to the designated VNF Descriptor network element description file, and then notifying a cloud host to rapidly deploy a type of VNF equipment with the custom attribute.
However, in the prior art, by means of VNF MANAGER collecting and randomly distributing according to the load usage situation of the current computing node, it is difficult to ensure distributed deployment of VNF devices, so that the problem of unbalanced load of the computing node server easily occurs.
Disclosure of Invention
The embodiment of the application provides a distributed deployment method and device for VNF equipment, which are used for solving the following technical problems: the existing VNF equipment is deployed, so that the problem of unbalanced load of a computing node server is easy to occur.
The embodiment of the application adopts the following technical scheme:
the embodiment of the application provides a distributed deployment method of VNF equipment. 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; acquiring the group number of the anti-affinity group corresponding to the current VNF equipment to be deployed based on the analysis result, and determining the 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 a plurality of VNF devices in the same anti-affinity group are different from each other; acquiring a network element description file of an anti-affinity group corresponding to the current VNF equipment to be deployed, and respectively deploying the current VNF equipment to be deployed and other VNF equipment in the anti-affinity group on different computing node servers under the condition that the network element description file is determined to introduce an anti-affinity strategy.
According to the embodiment of the application, the received VNF configuration model is analyzed by the model analysis engine, so that static resources required by different types and different numbers of VNF devices to be deployed can be prepared at one time, the preparation is carried out for quick deployment of the VNF, and the overall deployment flow of the VNF device is greatly simplified. Secondly, by constructing the anti-affinity group and introducing the anti-affinity policy, the embodiment of the application can deploy a plurality of VNF devices using the same VNF Descriptor introducing the anti-affinity policy on different computing node servers in a distributed manner, thereby solving the problem of unbalanced load of the computing node servers.
In one implementation of the present application, the deploying of the VNF device to be deployed and other VNF devices in the counteraffinity group are respectively deployed on different computing node servers, and specifically include: determining deployed VNF equipment corresponding to the same network element description file as the current VNF equipment to be deployed; acquiring reference computing node information corresponding to the deployed VNF equipment respectively, and deleting the reference computing node information; and screening one computing node from the rest of computing nodes based on a load balancing algorithm so as to deploy the VNF equipment to be deployed currently.
In one implementation manner of the present application, after obtaining the network element description file of the anti-affinity group corresponding to the VNF device to be deployed currently, the method further includes: and constructing an anti-affinity attribute in the network element description file, and determining an attribute value corresponding to the anti-affinity attribute so as to determine anti-affinity strategies of a plurality of VNF devices corresponding to the network element description file based on the attribute value corresponding to the anti-affinity attribute.
In an implementation manner of the present application, before obtaining the network element description file of the anti-affinity group corresponding to the VNF device to be deployed currently, the method further includes: performing anti-affinity group number detection on the deployed VNF equipment; in the deployed VNF devices, in the case that there is a reference VNF device with 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 one implementation of the present application, before parsing, by the model parsing engine, the received VNF configuration model, the method further includes: constructing basic configuration node information based on basic configuration parameters of the VNF equipment to be deployed; the basic configuration parameters at least comprise one or more of a control channel VLAN and a network segment between the VNF devices, a data channel VLAN and a network segment, the number of various VNF devices and the label range corresponding to the various VNF devices; constructing network element type node information based on category parameters of the VNF equipment to be deployed; the category parameters at least comprise one or more of CPU core number, memory size, hard disk size, interface name and 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 one implementation of the present application, after constructing the VNF configuration model 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 unified format file, and uploading the unified format file to the VNF MANAGER system.
In one implementation of the present application, before parsing, by the model parsing engine, the received VNF configuration model, the method further includes: dividing the VNF equipment to be deployed into a plurality of categories based on category parameters of the VNF equipment to be deployed; determining device labels corresponding to the to-be-deployed VNF devices in each category respectively; and dividing a plurality of to-be-deployed VNF devices with different device labels in each category into the same anti-affinity group, and labeling the group number of each anti-affinity group.
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 counteraffinity group is determined based on the plurality of device labels.
In one implementation of the present application, after parsing, by the model parsing engine, the received VNF configuration model, the method further includes: determining the analyzed sequence of the 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 service deployment workflow and the analyzed sequence of the information of the plurality of VNF devices to be deployed.
The embodiment of the application provides a distributed deployment device of a VNF device, which comprises the following components: 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, the instructions being 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; acquiring a group number of an anti-affinity group corresponding to the current VNF equipment to be deployed based on the analysis result, and determining other VNF equipment information in the anti-affinity group based on the anti-affinity group number; wherein, the device labels of a plurality of VNF devices in the same anti-affinity group are different from each other; acquiring a network element description file of an anti-affinity group corresponding to the current VNF equipment to be deployed, and respectively deploying the current VNF equipment to be deployed and other VNF equipment in the anti-affinity group on different computing node servers under the condition that the network element description file is determined to introduce an anti-affinity strategy.
The above at least one technical scheme adopted by the embodiment of the application can achieve the following beneficial effects: according to the embodiment of the application, the received VNF configuration model is analyzed by the model analysis engine, so that static resources required by different types and different numbers of VNF devices to be deployed can be prepared at one time, the preparation is carried out for quick deployment of the VNF, and the overall deployment flow of the VNF device is greatly simplified. Secondly, by constructing the anti-affinity group and introducing the anti-affinity policy, the embodiment of the application can deploy a plurality of VNF devices using the same VNF Descriptor introducing the anti-affinity policy on different computing node servers in a distributed manner, 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 that are required in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained according to the drawings without inventive effort for a person skilled in the art. In the drawings:
Fig. 1 is a flowchart of a distributed deployment method of VNF devices provided in an embodiment of the present application;
fig. 2 is a schematic structural diagram of a distributed deployment device for VNF devices according to an embodiment of the present application.
Detailed Description
The embodiment of the application provides a distributed deployment method and device for VNF equipment.
In order to make the technical solution of the present application better understood by those skilled in the art, the technical solution of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present application.
In the prior art, a cloud host is generally selected according to a control node, an available domain or a computing node mode, and a cloud host server where the VNF to be deployed is located is determined. VNF MANAGER abstracting a VNF Descriptor network element description file with a custom attribute value according to user selection, analyzing parameters in the VNF Descriptor by VNF MANAGER according to the designated VNF Descriptor network element description file, and then notifying a cloud host to rapidly deploy a type of VNF equipment with the custom attribute.
However, in the prior art, by means of VNF MANAGER collecting and randomly distributing according to the load usage situation of the current computing node, it is difficult to ensure distributed deployment of VNF devices, so that the problem of unbalanced load of the computing node server easily occurs.
In order to solve the above problems, the embodiments of the present application provide a distributed deployment method and device for VNF devices. The received VNF configuration model is analyzed by the model analysis engine, so that static resources required by different types and different numbers of VNF devices to be deployed can be prepared at one time, the preparation is carried out for quick deployment of the VNF, and the overall deployment flow of the VNF devices is greatly simplified. Secondly, by constructing the anti-affinity group and introducing the anti-affinity policy, the embodiment of the application can deploy a plurality of VNF devices using the same VNF Descriptor introducing the anti-affinity policy on different computing node servers in a distributed manner, thereby solving the problem of unbalanced load of the computing node servers.
The following describes the technical scheme provided by the embodiment of the application in detail through the attached drawings.
Fig. 1 is a flowchart of a distributed deployment method of VNF devices according to an embodiment of the present application. As shown in fig. 1, the VNF device distributed deployment method includes the following steps:
S101, analyzing a 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 one 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 include at least one or more of a control channel VLAN and a network segment between VNF devices, a data channel VLAN and a network segment, the number of VNF devices of each type, and a number range of labels corresponding to VNF devices of each type. And constructing network element type node information based on category parameters of the to-be-deployed VNF device, wherein the category parameters at least comprise one or more of CPU core number, memory size, hard disk size, interface name and interface type of the VNF device. 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, the embodiment of the present application does not select configuration parameters in the deployment flow of each VNF, but uses the Yang file to define a configuration model of all VNFs to be deployed in one deployment flow, where two types of nodes need to be defined in the model: a base configuration node and a network element type node.
Further, the basic configuration node mainly contains some basic configuration parameters, such as control channel VLANs and network segments between VNF devices, data channel VLANs and network segments, the number of VNFs of various types and the label ranges thereof. The VNF device labels are unique labels of each VNF in the one-time deployment service, each type of VNF device plans a certain VNF label range, the VNF device label ranges among different VNF devices cannot have an intersection, and the number of VNF devices corresponds to the VNF label range one by one.
Further, the network element type node is mainly used for defining configuration parameter information of a VNF device of a certain type, such as a CPU core number, a memory size, a hard disk size, an interface name, an interface type, and the like. The number of VNF type nodes corresponds to the kind of VNF device to be deployed.
In one embodiment of the application, the VNF configuration model is built as a unified format file and the unified format file is uploaded to the VNF MANAGER system.
Specifically, after the model definition is completed, the model file is packaged VNF PACKAGE in a specific format, and uploaded to VNF MANAGER to be identified and parsed by the model parsing engine.
According to the embodiment of the application, by defining the VNF configuration model and constructing VNF PACKAGE with a unified format, static resources required by different types and different numbers of VNF devices to be deployed can be prepared at one time, so that preparation is made for rapid deployment of the VNF, and the overall deployment flow of the VNF device is greatly simplified.
In one embodiment of the present application, based on a class parameter of a VNF device to be deployed, the VNF device to be deployed is divided into a plurality of classes, and device labels corresponding to the VNF device to be deployed in each class are determined. And dividing a plurality of to-be-deployed VNF devices with different device labels in each category into the same anti-affinity group, and labeling the group number of each anti-affinity group.
Specifically, the problem of unbalanced load of a computing node server easily occurs due to the fact that a cloud host is selected according to the computing nodes during distributed deployment. Therefore, the problem of how to ensure that the VNF devices are stacked in pairs to form a master and slave and the master and slave devices are distributed and deployed on different servers when the cloud host is selected to deploy the VNF devices according to a control node or an available domain is solved.
Further, in the embodiment of the present application, the anti-affinity group is introduced for VNF devices of the same kind, and two VNF devices belonging to one anti-affinity group are required to form a master-slave stack, and VNF devices distributed in different servers, that is, the same anti-affinity group have anti-affinities.
Further, for each anti-affinity group, the anti-affinity group number is uniquely identified, and each anti-affinity group can include two VNF devices with different device labels, so that it is ensured that the VNF devices requiring distributed deployment 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, VNFs with different device numbers are preferably divided into the same anti-affinity group, and in application, the number of VNF devices in one anti-affinity group may be adjusted according to actual situations, which is not limited in the embodiment of the present application.
S102, acquiring a group number of an anti-affinity group corresponding to the VNF equipment to be deployed currently based on an analysis result, and determining information of other VNF equipment in the anti-affinity group based on the group number of the anti-affinity group, wherein equipment labels of a plurality of VNF equipment in the same anti-affinity group are different from each other.
In one embodiment of the application, a plurality of device labels corresponding to the anti-affinity group number are determined. Other VNF device information within the counteraffinity group is determined based on the plurality of device labels.
Specifically, the model parsing engine parses VNF PACKAGE, and determines, according to the VNF device label, an anti-affinity group to which the VNF device belongs. After the anti-affinity group is determined, a plurality of VNF devices within the anti-affinity group are determined according to the group number of the anti-affinity group. Wherein, a plurality of VNF devices in the same anti-affinity group are mutually active and standby.
S103, acquiring a network element description file of an anti-affinity group corresponding to the current VNF equipment to be deployed, and deploying the current VNF equipment to be deployed and other VNF equipment in the anti-affinity group on different computing node servers respectively under the condition that the network element description file is determined to introduce an anti-affinity strategy.
In one embodiment of the present application, an anti-affinity attribute is built in a network element description file, and an attribute value corresponding to the anti-affinity attribute is determined, so as to determine anti-affinity policies of a plurality of VNF devices corresponding to the network element description file based on the attribute value corresponding to the anti-affinity attribute.
Specifically, VNF MANAGER can abstract the VNF Descriptor network element description file containing the custom specification attributes such as mirror image, hardware configuration, interface binding, and the like, and then create a type of VNF with the custom specification attributes according to the VNF Descriptor network element description file. And newly introducing an anti-affinity attribute into the VNF Descriptor network element description file, and defining that the VNF Descriptor is introduced with an anti-affinity strategy when the anti-affinity attribute value is true, namely that all VNF devices using the VNF Descriptor have mutual anti-affinities.
In one embodiment of the present application, the anti-affinity group number of the deployed VNF device is detected, and in the deployed VNF device, when there is a reference VNF device that is the same as the anti-affinity group number of 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.
Specifically, in the process of deploying each VNF device by VNF MANAGER, firstly, determining the group number of the corresponding anti-affinity group according to the VNF device number, if it is checked that the anti-affinity group number of a certain VNF device in the deployed VNF devices is the same as the VNF device to be deployed currently, using the same VNF Descriptor as the VNF device to be deployed currently, otherwise, creating a new VNF Descriptor. I.e. deploying multiple VNF devices of the same anti-affinity group, using the same VNF Descriptor introducing the anti-affinity policy.
In one embodiment of the present application, a service deployment workflow is created by determining a sequencing of the parsed VNF device information for multiple to be deployed. And deploying the plurality of VNF devices to be deployed based on the service deployment workflow and the analyzed sequence of the information of the plurality of VNF devices to be deployed.
Specifically, VNF MANAGER analyzes the basic configuration node and the network element type node of the received configuration model through a model analysis engine, and sequentially calculates the anti-affinity group number of each VNF device, so as to divide the VNF devices into different anti-affinity groups. And finally abstracting the corresponding VNF Descriptor and introducing the anti-affinity policy. After the model analysis is completed, a service deployment workflow is created, and the VNFs are prepared to be created in sequence according to the abstract VNF Descriptor.
Further, after a specific physical server is decided, VNF MANAGER enters a VNF creation flow, and part of the configuration in the VNF Descriptor is converted into an initial configuration file and stored in a certain agreed location, and is usually hung as an optical disc drive into a virtual device. The initial configuration file is read and executed one by one during the startup process of the VNF mounted mirror operating system.
In one embodiment of the present application, a deployed VNF device corresponding to the same network element description file as a currently to be deployed VNF device is determined. And acquiring reference computing node information corresponding to the deployed VNF equipment respectively, and eliminating the reference computing node information. And screening one computing node from the rest of computing nodes based on a load balancing algorithm so as to deploy the VNF equipment to be deployed currently.
Specifically, VNF MANAGER serves as a manager of VNF device resources, and may collect computing nodes of all cloud hosts managed by the computing nodes, and load conditions thereof, where the load includes the number of VNFs started on a physical server, memory utilization, CPU utilization, and the like.
Further, after the anti-affinity policy is introduced in the embodiment of the present application, VNF MANAGER first checks whether there are VNF devices using the same VNF Descriptor in the currently deployed VNF if it is identified that the anti-affinity attribute value of the designated VNF Descriptor is true, and if so, obtains the computing node where the designated VNF is located, and excludes the computing node from the cloud host computing node queried according to the control node or the available domain. And then deciding a proper physical server from other available computing nodes according to the existing load balancing algorithm, so that a plurality of VNF devices of the same VNF Descriptor introducing the anti-affinity policy are distributed and deployed on different computing node servers.
Further, according to the number of different types of VNFs defined in the model, the above steps are repeatedly performed until the creation of all VNF devices is completed, and finally, model-driven VNF anti-affinity distributed rapid deployment is realized.
In one embodiment of the present application, the created VNF devices may establish network connection even if they are distributed in different computing nodes due to the configuration of a unified internal control channel and internal data channel. Two VNFs of the same anti-affinity group are deployed on different servers to construct a master-slave stack, the VNF device role that is preferentially started is the master, and the other role is the slave, and the two VNFs are mutually guaranteed, so that reliable operation of the VNF device functions is ensured.
According to the embodiment of the application, by defining the VNF configuration model and constructing VNF PACKAGE with a unified format, static resources required by different types and different numbers of VNF devices to be deployed can be prepared at one time, so that preparation is made for rapid deployment of the VNF, and the overall deployment flow of the VNF device is greatly simplified. Secondly, by defining the calculation methods of the anti-affinity groups and the anti-affinity group numbers, the embodiment of the application can calculate the anti-affinity groups to which the VNF devices belong according to the number classification of the VNF devices, the VNF devices in the same anti-affinity group are mutually active and standby, and each anti-affinity group abstracts out the corresponding VNF Descriptor and introduces an anti-affinity strategy. And then realizing a plurality of VNF devices using the same VNF Descriptor introducing the anti-affinity strategy through VNF MANAGER, and distributing the VNF devices on different computing node servers. In addition, in the one-time deployment flow of the embodiment of the application, the deployment mode of selecting the cloud host according to the control node or the available domain only needs to be selected once, VNF MANAGER can automatically select different computing nodes for all the VNF devices to be deployed according to the anti-affinity strategy, so that the problem that users need to select different computing nodes and load unbalance respectively when deploying the VNF every time is avoided, and the user interaction operation is reduced.
Fig. 2 is a schematic structural diagram of a distributed deployment device for VNF devices 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
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;
Acquiring the group number of an anti-affinity group corresponding to the current VNF equipment to be deployed based on the analysis result, and determining the 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 a plurality of VNF devices in the same anti-affinity group are different from each other;
acquiring a network element description file of an anti-affinity group corresponding to the current to-be-deployed VNF device, and deploying the current to-be-deployed VNF device and other VNF devices in the anti-affinity group on different computing node servers respectively under the condition that the network element description file is determined to introduce an anti-affinity strategy.
The embodiments of the present application are described in a progressive manner, and the same and similar parts of the embodiments are all referred to each other, and each embodiment is mainly described in the differences from the other embodiments. In particular, for apparatus, devices, non-volatile computer storage medium embodiments, the description is relatively simple, as it is substantially similar to method embodiments, with reference to the section of the method embodiments being relevant.
The foregoing describes certain embodiments of the present application. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can 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 are also possible or may be advantageous.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and changes may be made to the embodiments of the application by those skilled in the art. 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 (2)
1. A method for distributed deployment of VNF devices, the method comprising:
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;
Acquiring the group number of an anti-affinity group corresponding to the current VNF equipment to be deployed based on the analysis result, and determining the 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 a plurality of VNF devices in the same anti-affinity group are different from each other;
Acquiring a network element description file of an anti-affinity group corresponding to the current to-be-deployed VNF device, and respectively deploying the current to-be-deployed VNF device 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 introduce an anti-affinity strategy;
The method for deploying the current VNF equipment to be deployed and other VNF equipment in the counteraffinity group on different computing node servers respectively specifically includes:
Determining deployed VNF equipment corresponding to the same network element description file as the current VNF equipment to be deployed;
Acquiring reference computing node information corresponding to the deployed VNF equipment respectively, and eliminating the reference computing node information;
Screening one computing node from the rest of computing nodes based on a load balancing algorithm so as to deploy the VNF equipment to be deployed currently;
after obtaining the network element description file of the anti-affinity group corresponding to the VNF equipment to be deployed currently, the method further includes:
Constructing an anti-affinity attribute in the network element description file, and determining an attribute value corresponding to the anti-affinity attribute so as to determine anti-affinity strategies of a plurality of VNF devices corresponding to the network element description file based on the attribute value corresponding to the anti-affinity attribute;
before the obtaining the network element description file of the anti-affinity group corresponding to the VNF equipment to be deployed, the method further includes:
Performing anti-affinity group number detection on the deployed VNF equipment;
in the deployed VNF equipment, under the condition that reference VNF equipment with the same anti-affinity group number as the current VNF equipment to be deployed exists, taking a network element description file of the reference VNF equipment as a network element description file of the VNF equipment to be deployed;
after the received VNF configuration model is parsed by the model parsing engine, the method further includes:
Determining the analyzed sequence of the information of the plurality of VNF devices to be deployed;
Creating a service deployment workflow;
deploying the plurality of to-be-deployed VNF devices based on the service deployment workflow and the parsed sequence of the plurality of to-be-deployed VNF device information;
before the received VNF configuration model is parsed by the model parsing engine, the method further includes:
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 a control channel VLAN and a network segment between VNF devices, a data channel VLAN and a network segment, the number of various VNF devices and a label range corresponding to the various VNF devices; and
Constructing the network element type node information based on the category parameters of the VNF equipment to be deployed; which is a kind of
The category parameters at least comprise one or more of CPU core number, memory size, hard disk size, interface name and interface type of the VNF equipment;
Constructing the VNF configuration model based on the basic configuration node information and the network element type node information;
after the constructing the VNF configuration model based on the base configuration node information and the network element type node information, the method further includes:
Constructing the VNF configuration model into a unified format file, and uploading the unified format file to a VNF MANAGER system;
before the received VNF configuration model is parsed by the model parsing engine, the method further includes:
dividing the VNF equipment to be deployed into a plurality of categories based on category parameters of the VNF equipment to be deployed;
determining device labels corresponding to the to-be-deployed VNF devices in each category respectively;
Dividing a plurality of VNF devices to be deployed with different device labels in each category into the same anti-affinity group, and labeling the group number of each anti-affinity group;
The determining, based on the group number of the anti-affinity group, information of other VNF devices in the anti-affinity group specifically includes:
determining a plurality of equipment labels corresponding to the anti-affinity group number;
and determining other VNF device information in the anti-affinity group based on the device labels.
2. A VNF device distributed deployment device, comprising:
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 enable the at least one processor to perform the method of claim 1.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210996570.5A CN115412440B (en) | 2022-08-19 | 2022-08-19 | Distributed deployment method and device for VNF (virtual network function) device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210996570.5A CN115412440B (en) | 2022-08-19 | 2022-08-19 | Distributed deployment method and device for VNF (virtual network function) device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115412440A CN115412440A (en) | 2022-11-29 |
| CN115412440B true CN115412440B (en) | 2024-07-09 |
Family
ID=84159327
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210996570.5A Active CN115412440B (en) | 2022-08-19 | 2022-08-19 | Distributed deployment method and device for VNF (virtual network function) device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115412440B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113794581A (en) * | 2021-08-05 | 2021-12-14 | 新华三大数据技术有限公司 | Distributed CP unified deployment method, network equipment and storage medium |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104142853B (en) * | 2014-08-12 | 2018-02-09 | 华为技术有限公司 | Virtual machine storage resource dispositions method and device |
| CN107846313B (en) * | 2017-10-30 | 2019-04-30 | 中国联合网络通信集团有限公司 | A kind of method and the network equipment of the generation of network service moulding plate |
| CN110098946B (en) * | 2018-01-31 | 2021-09-03 | 华为技术有限公司 | Method and device for deploying virtualized network element equipment |
| CN110324164B (en) * | 2018-03-29 | 2020-10-16 | 华为技术有限公司 | Network slice deployment method and device |
| CN111385114B (en) * | 2018-12-28 | 2022-04-26 | 华为技术有限公司 | VNF service instantiation method and device |
| EP3939207B1 (en) * | 2019-03-14 | 2024-05-01 | Telefonaktiebolaget LM Ericsson (publ) | Semantic detection and resolution of conflicts and redundancies in network function virtualization policies |
-
2022
- 2022-08-19 CN CN202210996570.5A patent/CN115412440B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113794581A (en) * | 2021-08-05 | 2021-12-14 | 新华三大数据技术有限公司 | Distributed CP unified deployment method, network equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115412440A (en) | 2022-11-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11704144B2 (en) | Creating virtual machine groups based on request | |
| US10474508B2 (en) | Replication management for hyper-converged infrastructures | |
| CN112153700B (en) | Network slice resource management method and equipment | |
| US20180375726A1 (en) | Resource Configuration Method, Virtualized Network Function Manager, and Element Management System | |
| US8638674B2 (en) | System and method for cloud computing | |
| US11093296B2 (en) | System, virtualization control apparatus, method for controlling a virtualization control apparatus, and program | |
| US8495352B2 (en) | System and method for instantiation of distributed applications from disk snapshots | |
| US20060235664A1 (en) | Model-based capacity planning | |
| WO2012094757A1 (en) | Determining an optimal computing environment for running an image | |
| CN106663012B (en) | Hardware acceleration method and related equipment | |
| EP3883183A1 (en) | Virtualization management method and device | |
| US20120259960A1 (en) | Dynamic Self-Configuration of Heterogenous Monitoring Agent Networks | |
| US12035156B2 (en) | Communication method and apparatus for plurality of administrative domains | |
| CN113794581B (en) | Distributed CP unified deployment method, network equipment and storage medium | |
| CN115412440B (en) | Distributed deployment method and device for VNF (virtual network function) device | |
| EP4152715A1 (en) | Method and apparatus for determining resource configuration of cloud service system | |
| CN114143235A (en) | NFV automatic test method, device, equipment and storage medium | |
| US20230153725A1 (en) | Techniques for determining service risks and causes | |
| CN112889247B (en) | VNF service instantiation method and device | |
| CN114647488A (en) | Task training method, device, equipment and storage medium | |
| JP2018018415A (en) | Information processing device, information processing system, program and information processing method | |
| US11647105B1 (en) | Generating multi-layer configuration templates for deployment across multiple infrastructure stack layers | |
| US20240152372A1 (en) | Virtual representations of endpoints in a computing environment | |
| US11216263B2 (en) | Policy-based automated generation of software-defined storage deployments | |
| LU501875B1 (en) | Managed entity configurator anomaly detection |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |