CN112887118B - VNF information acquisition and control method and device, NFVO, VNFM and storage medium - Google Patents
VNF information acquisition and control method and device, NFVO, VNFM and storage medium Download PDFInfo
- Publication number
- CN112887118B CN112887118B CN201911207569.4A CN201911207569A CN112887118B CN 112887118 B CN112887118 B CN 112887118B CN 201911207569 A CN201911207569 A CN 201911207569A CN 112887118 B CN112887118 B CN 112887118B
- Authority
- CN
- China
- Prior art keywords
- vnf
- information
- virtual resource
- nfvo
- resource information
- 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 59
- OOXMVRVXLWBJKF-DUXPYHPUSA-N n-[3-[(e)-2-(5-nitrofuran-2-yl)ethenyl]-1,2,4-oxadiazol-5-yl]acetamide Chemical compound O1C(NC(=O)C)=NC(\C=C\C=2OC(=CC=2)[N+]([O-])=O)=N1 OOXMVRVXLWBJKF-DUXPYHPUSA-N 0.000 title claims abstract 16
- 238000007726 management method Methods 0.000 claims description 92
- 230000006870 function Effects 0.000 claims description 34
- 238000004590 computer program Methods 0.000 claims description 20
- 238000004891 communication Methods 0.000 claims description 8
- 238000012545 processing Methods 0.000 claims description 8
- 238000004458 analytical method Methods 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 claims description 3
- 230000008569 process Effects 0.000 description 20
- 238000010586 diagram Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 5
- 230000003993 interaction Effects 0.000 description 3
- 238000012544 monitoring process Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 210000001503 joint Anatomy 0.000 description 2
- 238000003032 molecular docking Methods 0.000 description 2
- 238000013475 authorization Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000007493 shaping process Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000007723 transport mechanism Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 238000012795 verification 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/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0659—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities
- H04L41/0661—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities by reconfiguring faulty entities
-
- 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/0803—Configuration setting
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 invention provides a method, a device, an NFVO, a VNFM and a storage medium for obtaining and controlling VNF information, wherein the NFVO can carry out VNF arrangement and configuration according to the virtual resource information which is obtained from a VIM resource pool and generates a VNF arrangement configuration packet comprising the VNF virtual resource information and VNF life cycle management data; the VNFM may obtain a VNF orchestration configuration packet obtained by reverse orchestration from the NFVO, and manage, according to VNF lifecycle management data in the VNF orchestration configuration packet, a target resource in the VIM resource pool that matches with VNF virtual resource information included in the VNF orchestration configuration packet; therefore, for a manually created VNF, even if there is no VNF lifecycle management data corresponding to the VNF on the VNFM before, the VNF lifecycle management data can be incorporated into the management of the orchestration of NFVO and VNFM by the method provided by the embodiment of the present invention.
Description
Technical Field
The present invention relates to the field of communications, and in particular, to a method and apparatus for acquiring and controlling VNF information, NFVO, VNFM, and a storage medium.
Background
Network function virtualization (Network Function Virtualization, NFV), the core idea of NFV technology is to decouple logical network functions from physical hardware devices, so as to greatly reduce the network construction cost and operation cost of the basic telecommunication network operator, and network function implementation requires separating the basic telecommunication network control plane from the data plane, and implementing the virtualized network functions by using a programmable software platform.
In NFV technology, life cycle management of VNFs (Virtualised Network Function, virtualized network functions) is the basis of VNF applications. In the related art, the life cycle management for VNF has the following problems:
For manually established VNFs, because it is not registered on NFVO (Network Functions Virtualisation Orchestrator, network function virtualization orchestrator) and VNFM (Virtualised Network Function Manager, virtualized network function module manager), NFVO and VNFM cannot obtain life cycle management data of the VNF, resulting in that monitoring management of this part of VNF cannot be performed. Including failure to perform anomaly detection, alarm handling, resource management, etc. on this part of the VNF through NFVO and VNFM.
In addition, in the current NFV technology, management of VNFs is performed based on the arrangement information of VNFs stored on VNFM. When the VNFM fails, resulting in loss of stored data or failure to acquire or read errors normally, the VNF cannot be managed any more.
Disclosure of Invention
The method, the device, the NFVO, the VNFM and the storage medium for obtaining and controlling the VNF information provided by the embodiment of the invention solve the problems of how to realize management of the manually established VNF and how to manage the VNF when the arrangement information of the VNF stored on the VNFM can not be obtained normally.
To solve the above technical problem, an embodiment of the present invention provides a VNF information obtaining method, including:
acquiring created virtual resource information from a Virtual Infrastructure Manager (VIM) resource pool;
the network function VNF of the obtained virtual resource information is virtualized to generate VNF arranging elements;
Configuring the VNF arrangement elements to generate a VNF arrangement configuration package comprising VNF virtual resource information and VNF life cycle management data;
sending the VNF orchestration configuration package to a virtualized network function module manager VNFM
In order to solve the above technical problem, the embodiment of the present invention further provides a VNF management method, including:
obtaining a VNF orchestration configuration package obtained by the VNF information obtaining method described above from the NFVO;
analyzing the VNF arrangement configuration package to obtain VNF virtual resource information and VNF life cycle management data;
matching the VNF virtual resource information with the virtual resource information which is acquired and created in the VIM resource pool, and establishing and storing a VNF life cycle management instance according to the VNF life cycle management data;
And managing target virtual resources successfully matched with the VNF virtual resource information in the VIM resource pool according to the VNF life cycle management instance.
To solve the above technical problem, an embodiment of the present invention further provides a VNF information acquiring apparatus, which is characterized by including:
The resource information acquisition module is used for acquiring the created virtual resource information from the VIM resource pool;
the reverse arrangement module is used for carrying out VNF arrangement on the obtained virtual resource information and generating VNF arrangement elements;
A VNF package generating module, configured to configure the VNF orchestration element, to generate a VNF orchestration configuration package including VNF virtual resource information and VNF lifecycle management data;
And the sending module is used for sending the VNF arrangement configuration packet to a virtualized network function module manager VNFM.
To solve the above technical problem, an embodiment of the present invention further provides a VNF management device, including:
a VNF packet obtaining module, configured to obtain, from the NFVO, a VNF orchestration configuration packet obtained by the VNF information obtaining method described above;
the VNF packet analysis module is used for analyzing the VNF arrangement configuration packet to acquire VNF virtual resource information and VNF life cycle management data;
The processing module is used for matching the VNF virtual resource information with the virtual resource information which is acquired and created in the VIM resource pool, and establishing and storing a VNF life cycle management instance according to the VNF life cycle management data;
and the management module is used for managing target virtual resources successfully matched with the VNF virtual resource information in the VIM resource pool according to the VNF life cycle management instance.
To solve the above technical problem, an embodiment of the present invention further provides an NFVO, including a first processor, a first memory, and a first communication bus for connecting the first processor and the first memory;
The first processor is configured to execute a first computer program stored in the first memory to implement the steps of the VNF information acquisition method as described above.
In order to solve the technical problem, the embodiment of the invention also provides a VNFM, which comprises a second processor, a second memory, and a second communication bus for connecting the second processor and the second memory;
The second processor is configured to execute a second computer program stored in the second memory to implement the steps of the VNF management method as described above.
To solve the above technical problem, an embodiment of the present invention further provides a computer readable storage medium, where the computer readable storage medium stores a first computer program, where the first computer program is executable by a first processor to implement the steps of the VNF information acquisition method described above;
Or alternatively, the first and second heat exchangers may be,
The computer readable storage medium stores a second computer program executable by a second processor to implement the steps of the VNF management method as described above.
Advantageous effects
According to the VNF information acquiring and controlling method, device, NFVO, VNFM and storage medium provided by the embodiments of the present invention, the NFVO may perform VNF arrangement according to the virtual resource information that has been created acquired from a VIM (Virtual Infrastructure Manager ) resource pool, generate VNF arrangement elements, and configure the obtained VNF arrangement elements, generate a VNF arrangement configuration packet including VNF virtual resource information and VNF lifecycle management data; thus, manually created VNFs may also be incorporated into NFVO orchestration; the VNFM may obtain a VNF orchestration configuration packet obtained by reverse orchestration from the NFVO, and manage, according to VNF lifecycle management data in the VNF orchestration configuration packet, a target resource in the VIM resource pool that matches with VNF virtual resource information included in the VNF orchestration configuration packet; therefore, for the manually created VNF, even if the VNF life cycle management data corresponding to the VNF is not available on the VNFM before, the manually created VNF can be incorporated into the VNFM for implementing management by the method provided by the embodiment of the invention;
In addition, according to the method provided by the embodiment, even if the arrangement information of the VNFs stored on the VNFM cannot be normally acquired, the VNFM can still perform VNF arrangement through the NFVO according to the created virtual resource information acquired from the VIM resource pool, so as to obtain VNF arrangement configuration packages corresponding to each VNF, and further manage each VNF normally; that is, when the VNFM failure causes that the arrangement information of the VNF cannot be normally acquired, the reconstruction of the VNFM may be achieved by the method provided in this embodiment.
Additional features and corresponding advantages of the invention will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the invention.
Drawings
FIG. 1 is a schematic diagram of an NFV architecture;
fig. 2 is a schematic diagram of a forward instantiation process of a VNF;
Fig. 3 is a schematic flow chart of a VNF information obtaining method according to a first embodiment of the present invention;
fig. 4 is a schematic flow chart of a VNF management method according to a first embodiment of the present invention;
fig. 5 is a schematic structural diagram of a VNF information acquiring apparatus according to a second embodiment of the present invention;
fig. 6 is a schematic structural diagram of a VNF management device according to a second embodiment of the present invention;
FIG. 7 is a schematic diagram of a reverse instantiation process according to a second embodiment of the present invention;
FIG. 8 is a schematic diagram of NFVO structure according to third embodiment of the present invention;
fig. 9 is a schematic view of the VNFM structure of the third embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the following detailed description of the embodiments of the present invention is given with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
Embodiment one:
In this embodiment, in order to facilitate accurate understanding of the scheme, the technical background of NFV is first described in the following with reference to the NFV architecture schematic diagram illustrated in fig. 1. It should be understood that the following description is only for ease of understanding and is not intended to limit the present invention.
Please refer to fig. 1, wherein:
NFVO, mainly used for implementing network function virtualization function VNF arrangement and management; the NFVO may set a corresponding encoder according to specific requirements to implement VNF arrangement.
VNFM, mainly used for implementing VNF lifecycle management, including but not limited to VNF instantiation, VNF termination, VNF elastic scaling VDU (Virtualization Deployment Unit, virtualized deployment unit), etc.
The VIM is mainly used for managing virtualized resources based on infrastructure hardware resources. For example, virtual machine resources may include, but are not limited to, computing resources, storage resources, and network resources; the VIM faces the upper VNFM providing it with a virtualized resource pool.
The VNF is a virtual network element to realize a certain network function unit; these VNFs may be automatically instantiated through NFVO and VNFM, or may be established directly manually on VIM.
In the NFV system architecture, three layers of VIM, VNFM and NFVO are decoupled, and information interaction can be carried out among the three layers through an opened standard interface; the NFVO can thus obtain relevant virtual resource information by interacting with the VIM.
An example flow for automatically instantiating a VNF through an NFVO and a VNFM is shown in fig. 2, including:
S201: and programming and arranging the VNF on the NFVO, then making a VNF programming and arranging a configuration package, and finally deploying and registering the VNF programming and arranging the configuration package on the NFVO.
S202: a VNF instantiation request is initiated at the NFVO to the VNFM, which may include a VNF orchestration configuration package.
S203: and the VNM checks the virtualized resource quota of the VNF to be created according to the VNF instantiation request, acquires authorization authentication and prepares for resource creation.
S204: the VNFM and VIM interactions complete the creation of the virtual deployment unit VDU and related network, stored resources.
S205: if the virtual network function involves version deployment, the version deployment flow is completed with the VNF interaction.
S206: the VNFM completes instantiation, and VNF life cycle management data are put in storage;
s207: the VNFM notifies the NFVO that instantiation is over, completing other work.
In this embodiment, for VNFs (which may include at least one of VNFs automatically created through NFVO and VNFM, and VNFs manually created on VIM) already established in the network, the VNF orchestration configuration package thereof may be obtained through reverse orchestration by the VNF information obtaining method shown in fig. 3, and the obtaining process is shown in fig. 3, and includes:
S301: the created virtual resource information is obtained from the virtual infrastructure manager VIM resource pool.
In this embodiment, this step may be, but is not limited to, NFVO obtaining the created virtual resource information from the VIM resource pool. It should be understood that, according to the specific application scenario requirement, the NFVO obtains the created virtual resource information from the VIM resource pool, which may be for obtaining virtual resource information for the manually created VNF, or may also obtain virtual resource information for the VNF automatically created by the NFVO and the VNFM according to the specific application scenario requirement; or the virtual resource information of the manually created VNF and the automatically created VNF is acquired, and specifically can be flexibly set according to the current requirements.
For example, in one example, when virtual resource information for a manually created VNF needs to be acquired, NFVO acquiring the created virtual resource information from the VIM resource pool may include: virtual resource information that is currently created and does not belong to the VNF orchestration configuration package registered on the NFVO is obtained from the VIM resource pool. For example, assume that 10 VNFs, VNFs 1 to 10, are currently created in the network, where VNFs 1 to 7 are automatically created by NFVO and VNFM, so that VNF orchestration configuration packages corresponding to VNFs 1 to 7 are registered on NFVO, and only virtual resource information corresponding to VNFs 8 to 10 that are not registered on NFVO needs to be acquired, and the virtual resource information does not belong to the VNF orchestration configuration packages registered on NFVO.
For another example, in one instance, when only virtual resource information for an automatically created VNF needs to be acquired, the NFVO acquiring the created virtual resource information from the VIM resource pool may include: virtual resource information which is currently created and is attributed to the VNF orchestration configuration package registered on the network function virtualization orchestrator NFVO is obtained from the VIM resource pool. For example, it is still assumed that 10 VNFs, VNFs 1 to 10, respectively, are currently created in the network, where VNFs 1 to 7 are automatically created through NFVO and VNFM, so that VNF orchestration configuration packets corresponding to VNFs 1 to 7 are registered on the NFVO, and only virtual resource information corresponding to VNFs 1 to 7 registered on the NFVO needs to be acquired.
Of course, in some examples, when virtual resource information of both the manually created VNF and the automatically created VNF needs to be acquired, the acquisition of the virtual resource information may be performed in combination with the above two examples.
S302: and carrying out Virtual Network Function (VNF) arrangement on the obtained virtual resource information, and generating a VNF arrangement element.
In this embodiment, the NFVO may generate the VNF orchestration element through, but not limited to, network function VNF orchestration that virtualizes the obtained virtual resource information by using an orchestrator. The VNF layout element generated reversely can be regarded as a layout sketch of the VNF, and the VNF layout configuration package can be generated after the configuration of the relevant information is confirmed on the basis; the reverse arrangement mode can greatly reduce arrangement workload and improve arrangement efficiency and accuracy.
S303: and configuring the VNF layout elements to generate a VNF layout configuration package comprising the VNF virtual resource information and the VNF life cycle management data.
In this step, the NFVO may configure VNF orchestration elements automatically or according to an instruction of a configurator, and generate a VNF orchestration configuration package including VNF virtual resource information and VNF lifecycle management data.
For example, in some examples, the VNF virtual resource information includes virtual resource deployment unit VDU information, and may further include, but is not limited to, at least one of network information, storage resource information, computing resource information, mirror information, operating system information, user information;
The NFVO performs association configuration on the VNF orchestration element, generates a VNF orchestration configuration package including VNF lifecycle management data, including: with the VDU included in the VNF orchestration element as granularity, lifecycle management data (e.g., including but not limited to performance acquisition policies, alarm policies, monitoring policies) is configured according to the configuration instructions, and at least one of VDU specification information, network information (e.g., network type DHCP, fixed IP, subinterface, etc.), elasticity information, mirror information, user information is configured according to the configuration instructions.
In one example, when the NFVO performs the configuration of the life cycle management data according to the configuration instruction, the configuration of the life cycle management data of the VNF may include, but is not limited to, performing the configuration of the life cycle management data according to the configuration instruction from at least one dimension of a VDU resource, a storage resource, a network resource, an elastic resource, and an operation maintenance resource.
S304: and sending the VNF arrangement configuration packet to a virtualized network function module manager (VNM).
In some examples, the NFVO may actively wrap the VNF orchestration configuration resulting from the reverse orchestration to the VNFM. For example, the NFVO may send a reverse instantiation request to the VNFM, thereby triggering the VNFM to trigger a reverse instantiation process according to the VNF orchestration configuration package obtained by reverse orchestration.
In other application examples, the NFVO may also passively send the VNF orchestration configuration packet obtained by reverse orchestration to the VNFM according to the VNFM's request. For example, the VNFM may send a reverse instantiation request to the NFVO to obtain a reverse orchestrated VNF orchestration configuration package and trigger the VNFM to trigger a reverse instantiation process according to the reverse orchestrated VNF orchestration configuration package.
In this embodiment, in the process of performing reverse instantiation by the VNFM according to the VNF orchestration configuration packet obtained by reverse orchestration, the virtual resource creation step may not be performed interactively with the VIM, and only the virtual resource matching and the association of management data to the virtual resource that is successfully matched may be completed.
In this embodiment, when the NFVO obtains the created virtual resource information from the VIM resource pool, including obtaining the virtual resource information for the manually created VNF, after obtaining the VNF orchestration configuration packet through reverse orchestration in step S303, when the VNF orchestration configuration packet is an unregistered VNF orchestration configuration packet on the NFVO (i.e., an orchestration configuration packet corresponding to the manually created VNF), the NFVO may further include registering the VNF orchestration configuration packet generated through reverse orchestration on the NFVO; thereby incorporating the manually established VNF into the orchestration of the NFVO.
On the basis of the above example, this embodiment further provides a VNF management method, as shown in fig. 4, including:
s401: the VNF orchestration configuration package acquired by the VNF information acquisition method shown above is acquired from the NFVO.
In this step of the present embodiment, the VNFM may actively or passively obtain the VNF orchestration configuration package generated by the reverse orchestration described above from the NFVO. The active acquisition is that the VNFM may send a reverse instantiation request to the NFVO and then receive the VNF orchestration configuration packet sent by the NFVO according to the reverse instantiation request.
In this embodiment, the arrangement information of the VNF arrangement configuration packet acquired by the VNFM needs to be consistent with the VDU information of the resource pool, for example, the VNF based on OpenStack generally includes information of virtual machines, networks, storage, and the like, and other basic resource pool platforms are similar.
S402: and analyzing the VNF arrangement configuration package to obtain the VNF virtual resource information and the VNF life cycle management data.
In this step of this embodiment, the VNFM may parse the VNF orchestration configuration package to obtain VNF virtual resource information (e.g., virtual resource deployment unit VDU information, and may also include, but is not limited to, at least one of network information, storage resource information, computing resource information, image information, operating system information, user information, and the like) and VNF lifecycle management data (e.g., configuration data including, but not limited to, performance acquisition policies, alarm policies, monitoring policies, and the like).
Taking the VIM based on OpenStack as an example, the VNFM can parse out virtual machine names, virtual machine specifications, network names, subnet names, IP information or network segments, disk names and sizes, elastic group information, and so on;
S403: and matching the VNF virtual resource information obtained by the analysis with the virtual resource information which is obtained and created in the VIM resource pool, and establishing and storing a VNF life cycle management instance according to the VNF life cycle management data.
In this embodiment, the process of matching the VNF virtual resource information obtained by the parsing with the created virtual resource information obtained from the VIM resource pool by the VNFM may include:
The VNM queries the VDU created on the VIM according to the analyzed resources, and further queries the resource information of the VDU, such as network, storage and the like; and finally, associating the corresponding reverse generated VNF arrangement configuration package (such as the VNF life cycle management data in the package) with the target resource information successfully matched with the VIM to generate life cycle management data corresponding to the target resource information.
In this embodiment, when the VNF virtual resource information in the existing part of the dynamic arrangement information cannot be directly associated with the VIM resource pool information, matching may be performed according to, but not limited to, the following rules:
matching for the ejected VDU: the names of the VDUs are all regular, e.g. the names contain prefixes. When querying such VDUs, a prefix may be used to match to find a certain VDU.
Matching for network information: after the VDU is found, the network information on the VDU can be further matched; for fixed IP direct mapping, for non-fixed IP can be matched per network segment.
In addition, in the related art, for the VNF that is automatically instantiated, when a resource change such as a VDU needs to be performed, and a maintainer does not operate synchronously from the VNFM, or because the VNFM does not have a certain resource change capability, the maintainer may have to operate directly on the resource manually, which results in inconsistent management data of the VNF and actual resource usage of the VNF by the VNFM over time, and no scheme capable of detecting whether the resource recorded in the management data of the VNF is consistent with the actual resource exists at present.
In view of the above problem, in this embodiment, the NFVO obtaining the created virtual resource information from the VIM resource pool may include obtaining virtual resource information that is currently created and is attributed to the VNF orchestration configuration package registered on the network function virtualization orchestrator NFVO from the VIM resource pool. At this time, the VNFM may further include, after obtaining the VNF virtual resource information by analyzing the VNF orchestration configuration packet:
When determining that the reverse generated VNF orchestration configuration package has corresponding VNF orchestration information registered on the VNFM, the VNFM determines whether VNF virtual resource information included in the reverse generated VNF orchestration configuration package is consistent with VNF virtual resource information recorded by the VNF orchestration information; if so, indicating that the resources recorded in the management data of the VNF are consistent with the actual resources; otherwise, it indicates that the resources recorded in the management data of the VNF are inconsistent with the actual resources, and at least one of alarm processing, or synchronization processing of the recorded resource data may be performed, but is not limited to, the alarm processing.
S404: and managing target virtual resources successfully matched with the VNF virtual resource information in the VIM resource pool according to the VNF life cycle management instance.
It can be seen that the VNF information acquiring and controlling method provided in this embodiment has at least the following advantages:
For uncontrolled VNFs, e.g., manually created VNFs, it can be incorporated into NFVO orchestration and VNFM lifecycle management by reverse orchestration and reverse instantiation;
through the reverse synchronous operation, the problem that management data is inconsistent with actual resource use can be solved;
when the VNFM fails and cannot continue to be used, the failed VNFM can be rebuilt based on the VDU by reverse instantiation. For example, even if the arrangement information of the VNFs stored on the VNFM cannot be normally obtained, the VNFM can still perform VNF arrangement through the NFVO according to the created virtual resource information obtained from the VIM resource pool, so as to obtain VNF arrangement configuration packets corresponding to each VNF, and further manage each VNF normally, so that reconstruction of the VNFM is achieved, and meanwhile, the state of the VNF is not affected.
The complexity of the VNM upgrade can also be reduced; if the new version of the VNFM differs greatly, a new VNFM may be created, and the life cycle management capabilities of the new VNFM are restored by reverse instantiation.
Compared with the forward instantiation process, the reverse instantiation process provided by the embodiment has fewer modules and simple steps, and is a lightweight method for establishing life cycle management. On one hand, the process of re-registering a packet on the NFVO, uploading a mirror image and the like can be omitted; on the other hand, the process of reconstructing the VDU and deploying the service is avoided.
Embodiment two:
on the basis of the foregoing embodiment, this embodiment provides a VNF information acquisition device disposed in an NFVO and used for VNF information acquisition, as shown in fig. 5, including:
a resource information obtaining module 501, configured to obtain created virtual resource information from a virtual infrastructure manager VIM resource pool; the specific acquisition process is shown in the above embodiment, and will not be described herein.
The reverse arrangement module 502 is configured to perform VNF arrangement on the obtained virtual resource information, and generate a VNF arrangement element; the specific layout process is shown in the above embodiments, and will not be described herein.
A VNF package generating module 503, configured to configure the VNF orchestration element, and generate a VNF orchestration configuration package including VNF virtual resource information and VNF lifecycle management data; the specific packet generation process is shown in the above embodiment, and will not be described herein.
A sending module 504, configured to send the VNF orchestration configuration packet to a virtualized network function module manager VNFM.
On the basis of the foregoing embodiment, this embodiment provides a VNF management device disposed in a VNFM for VNF management, as shown in fig. 6, which includes:
A VNF package obtaining module 601, configured to obtain, from the NFVO, a VNF orchestration configuration package obtained by the VNF information obtaining method described above; the specific acquisition process is shown in the above embodiment, and will not be described herein.
The VNF package parsing module 602 is configured to parse the VNF orchestration configuration package to obtain VNF virtual resource information and VNF lifecycle management data; the specific parsing process is shown in the above embodiments, and will not be described herein.
A processing module 603, configured to match the VNF virtual resource information with the virtual resource information obtained from the VIM resource pool, and establish and store a VNF lifecycle management instance according to the VNF lifecycle management data; the specific processing procedure is shown in the above embodiment, and will not be described herein.
And the management module 604 is configured to manage, according to the VNF lifecycle management instance, a target virtual resource in the VIM resource pool that is successfully matched with the VNF virtual resource information.
For easy understanding, the following description of the present embodiment is given with reference to the flow shown in fig. 7, where a complete reverse instantiation process is illustrated, and referring to fig. 7, the process includes:
s701: triggering the reverse generation flow of VNF orchestration on NFVO.
In some examples, the reverse generation flow of VNF orchestration may be manually triggered in the NFVO system by an NFVO system administrator; an automatic triggering procedure, such as a timing trigger, may also be set in the NFVO system.
S702: the NFVO queries virtual resource information of the VNF in the butt joint VIM, and generates VNF layout basic elements of the VNF layout reversely.
For example, may include virtual deployment units, network resources, computing resources, storage resources, virtual specifications, and the like.
S703: according to the instruction of the NFVO system administrator, dividing the essential elements of the VNF arrangement generated in the reverse direction into elements required by the VNF, and finishing the shaping of the VNF arrangement; finally, the self-incorporated VNF internally custom orchestration goes to the reverse generated VNF orchestration configuration package. Optionally, registration may also be performed for the resulting reverse-generated VNF orchestration configuration package that is not currently registered on the NFVO.
S704: and triggering the reverse instantiation process of the VNF in the VNFM system.
In this embodiment, the VNFM may trigger the reverse instantiation process of the VNF according to the instruction of the VNFM system administrator.
S705: the VNFM interfaces with the NFVO to obtain the reverse generated VNF orchestration configuration package.
In this step, a VNF orchestration configuration package may be downloaded from the NFVO, and the VNF orchestration configuration package is parsed to obtain VNF orchestration elements; and finishing the basic verification of the integrity, the legality and the like of the VNF orchestration configuration package.
S706: and the VNM is in butt joint with the VIM, and the matching of the VNF arrangement configuration package and the corresponding target virtual resources in the VIM is completed according to the mirror image, the virtual resource specification, the virtual deployment unit, the network port, the data disk, the VIM user quota and the like related to the virtual resource query VNF which are analyzed in the VNF arrangement configuration package.
In this embodiment, the VNFM may store the checked VNF arrangement configuration packet information, and complete registration of the VNF arrangement information on the VNFM.
S707: the VNFM establishes VNF lifecycle management instances from dimensions of a virtual deployment unit, a storage disk, a network, an elastic resource, operation maintenance management, and the like, and stores the instantiation data.
S708: the VNFM manages the VNF according to the corresponding docking VNF for docking the VNF lifecycle management instance. The VNF is managed, for example, according to mechanisms such as an alarm policy, a performance acquisition policy, etc. in the VNF lifecycle management instance.
Embodiment III:
the present embodiment also provides an NFVO, referring to fig. 8, which includes a first processor 801, a first memory 802, and a first communication bus 803 for connecting the first processor 801 and the first memory 802;
the first processor 801 is configured to execute a first computer program stored in the first memory 802 to implement the steps of the VNF information acquisition method as described in the above embodiments.
The present embodiment also provides a VNFM, as shown in fig. 9, comprising a second processor 901, a second memory 902, and a second communication bus 903 for connecting the second processor 901 and the second memory 902;
the second processor 901 is configured to execute a second computer program stored in the second memory 902 to implement the steps of the VNF management method as described in the above embodiments.
The present embodiments also provide a computer-readable storage medium including volatile or nonvolatile, removable or non-removable media implemented in any method or technology for storage of information, such as computer-readable instructions, data structures, computer program modules or other data. Computer-readable storage media includes, but is not limited to, RAM (Random Access Memory ), ROM (Read-Only Memory), EEPROM (ELECTRICALLY ERASABLE PROGRAMMABLE READ ONLY MEMORY, charged erasable programmable Read-Only Memory), flash Memory or other Memory technology, CD-ROM (Compact Disc Read-Only Memory), digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.
In one example, the computer readable storage medium in the present embodiment may be used to store the first computer program described above, which may be executed by the first processor to implement the steps of the VNF information acquisition method as in the above embodiments.
In another example, the computer readable storage medium in the present embodiment may be used to store the second computer program described above, which may be executed by the second processor to implement the steps of the VNF management method as in the above embodiments.
The present embodiment also provides a first computer program (or first computer software) that may be distributed on a computer readable medium and executed by a computable device to implement the steps of the VNF information acquisition method in the above embodiments. And in some cases at least one of the steps shown or described may be performed in a different order than that described in the above embodiments.
The present embodiment also provides a second computer program (or second computer software) that may be distributed on a computer readable medium and executed by a computable device to implement the steps of the VNF management method in the above embodiments. And in some cases at least one of the steps shown or described may be performed in a different order than that described in the above embodiments.
The present embodiment also provides a computer program product comprising computer readable means having stored thereon any one of the computer programs as described above. The computer readable means in this embodiment may comprise a computer readable storage medium as shown above.
It will be apparent to one skilled in the art that all or some of the steps of the methods, systems, functional modules/units in the apparatus disclosed above may be implemented as software (which may be implemented in computer program code executable by a computing apparatus), firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between the functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed cooperatively by several physical components. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit.
Furthermore, as is well known to those of ordinary skill in the art, communication media typically embodies computer readable instructions, data structures, computer program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and may include any information delivery media. Therefore, the present invention is not limited to any specific combination of hardware and software.
The foregoing is a further detailed description of embodiments of the invention in connection with the specific embodiments, and it is not intended that the invention be limited to the specific embodiments described. It will be apparent to those skilled in the art that several simple deductions or substitutions may be made without departing from the spirit of the invention, and these should be considered to be within the scope of the invention.
Claims (14)
1. A VNF information acquisition method applied to a network function virtualization orchestrator NFVO, comprising:
acquiring created virtual resource information from a Virtual Infrastructure Manager (VIM) resource pool;
the network function VNF of the obtained virtual resource information is virtualized to generate VNF arranging elements;
Configuring the VNF arrangement elements to generate a VNF arrangement configuration package comprising VNF virtual resource information and VNF life cycle management data;
and sending the VNF arrangement configuration packet to a virtualized network function module manager VNFM.
2. The VNF information acquisition method of claim 1, wherein the acquiring the created virtual resource information from the VIM resource pool includes:
Virtual resource information which is currently created and does not belong to the VNF orchestration configuration package registered on the network function virtualization orchestrator NFVO is obtained from the VIM resource pool.
3. The VNF information acquisition method of claim 2, wherein the generating the VNF orchestration configuration package including VNF management data further comprises registering the generated VNF orchestration configuration package on the NFVO.
4. The VNF information acquisition method of any one of claims 1 to 3, wherein the acquiring the created virtual resource information from the VIM resource pool includes:
Virtual resource information which is currently created and is attributed to a registered VNF orchestration configuration package on a network function virtualization orchestrator NFVO is obtained from the VIM resource pool.
5. The VNF information acquisition method of any one of claims 1 to 3, wherein the virtual resource information includes virtual resource deployment unit VDU information, and further includes at least one of network information, storage resource information, computing resource information, mirror information, operating system information, user information;
The configuring the VNF orchestration element to generate a VNF orchestration configuration package including VNF lifecycle management data, including:
And configuring life cycle management data according to configuration instructions by taking VDUs included in the VNF arrangement elements as granularity, and configuring at least one of VDU specification information, network information, elasticity information, mirror image information and user information according to the configuration instructions.
6. The VNF information acquisition method of claim 5, wherein the configuring the lifecycle management data according to the configuration instruction includes:
And according to the configuration instruction, the life cycle management data is configured from at least one dimension of the VDU resource, the storage resource, the network resource, the elastic resource and the operation maintenance resource.
7. A VNF management method is applied to a virtualized network function module manager VNFM, and comprises the following steps:
Acquiring a VNF orchestration configuration package acquired by the VNF information acquisition method of any one of claims 1 to 5 from the NFVO;
analyzing the VNF arrangement configuration package to obtain VNF virtual resource information and VNF life cycle management data;
matching the VNF virtual resource information with the virtual resource information which is acquired and created in the VIM resource pool, and establishing and storing a VNF life cycle management instance according to the VNF life cycle management data;
And managing target virtual resources successfully matched with the VNF virtual resource information in the VIM resource pool according to the VNF life cycle management instance.
8. The VNF management method of claim 7, wherein the obtaining the VNF orchestration configuration package from the NFVO, the VNF orchestration configuration package being obtained by the VNF information obtaining method of any one of claims 1-6, comprises:
sending a reverse instantiation request to the NFVO;
And receiving a VNF arrangement configuration packet sent by the NFVO according to the reverse instantiation request.
9. The VNF management method of claim 7 or 8, wherein the obtaining the created virtual resource information from the VIM resource pool includes: when virtual resource information which is currently created and belongs to a VNF orchestration configuration package registered on a network function virtualization orchestrator NFVO is obtained from the VIM resource pool, the analyzing the VNF orchestration configuration package, after obtaining the VNF virtual resource information, further includes:
And when determining that the VNF arrangement configuration packet has the corresponding VNF arrangement information registered on the VNFM, determining whether the VNF virtual resource information included in the VNF arrangement configuration packet is consistent with the VNF virtual resource information recorded by the VNF arrangement information.
10. A VNF information acquisition apparatus, comprising:
The resource information acquisition module is used for acquiring the created virtual resource information from the VIM resource pool;
the reverse arrangement module is used for carrying out VNF arrangement on the obtained virtual resource information and generating VNF arrangement elements;
A VNF package generating module, configured to configure the VNF orchestration element, to generate a VNF orchestration configuration package including VNF virtual resource information and VNF lifecycle management data;
And the sending module is used for sending the VNF arrangement configuration packet to a virtualized network function module manager VNFM.
11. A VNF management apparatus, comprising:
A VNF package obtaining module, configured to obtain, from the NFVO, a VNF orchestration configuration package obtained by the VNF information obtaining method according to any one of claims 1-6;
the VNF packet analysis module is used for analyzing the VNF arrangement configuration packet to acquire VNF virtual resource information and VNF life cycle management data;
The processing module is used for matching the VNF virtual resource information with the virtual resource information which is acquired and created in the VIM resource pool, and establishing and storing a VNF life cycle management instance according to the VNF life cycle management data;
and the management module is used for managing target virtual resources successfully matched with the VNF virtual resource information in the VIM resource pool according to the VNF life cycle management instance.
12. An NFVO comprising a first processor, a first memory, and a first communication bus for connecting said first processor and said first memory;
The first processor is configured to execute a first computer program stored in the first memory to implement the steps of the VNF information acquisition method of any one of claims 1 to 6.
13. A VNFM comprising a second processor, a second memory, and a second communication bus for connecting the second processor and the second memory;
The second processor is configured to execute a second computer program stored in the second memory to implement the steps of the VNF management method of any one of claims 7 to 9.
14. A computer readable storage medium storing a first computer program executable by a first processor to implement the steps of the VNF information acquisition method of any one of claims 1 to 6;
Or alternatively, the first and second heat exchangers may be,
The computer readable storage medium stores a second computer program executable by a second processor to implement the steps of the VNF management method of any one of claims 7 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911207569.4A CN112887118B (en) | 2019-11-29 | 2019-11-29 | VNF information acquisition and control method and device, NFVO, VNFM and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911207569.4A CN112887118B (en) | 2019-11-29 | 2019-11-29 | VNF information acquisition and control method and device, NFVO, VNFM and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112887118A CN112887118A (en) | 2021-06-01 |
| CN112887118B true CN112887118B (en) | 2024-05-31 |
Family
ID=76039206
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911207569.4A Active CN112887118B (en) | 2019-11-29 | 2019-11-29 | VNF information acquisition and control method and device, NFVO, VNFM and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112887118B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105955824A (en) * | 2016-04-21 | 2016-09-21 | 华为技术有限公司 | Method and device for configuring virtual resource |
| CN107145380A (en) * | 2017-03-27 | 2017-09-08 | 华为技术有限公司 | Virtual resource method of combination and device |
| EP3249860A1 (en) * | 2015-01-23 | 2017-11-29 | Nec Corporation | Method, device, and program for management and orchestration of network functions virtualization |
| CN107948006A (en) * | 2018-01-09 | 2018-04-20 | 重庆邮电大学 | A kind of method of combination and device for virtualizing network function |
| CN108156095A (en) * | 2016-12-02 | 2018-06-12 | 中兴通讯股份有限公司 | Resource determining method and device, NFVO |
| CN108886492A (en) * | 2016-04-28 | 2018-11-23 | 日本电气株式会社 | Network function virtual management and layout device, methods and procedures |
| CN109889377A (en) * | 2019-01-29 | 2019-06-14 | 京信通信系统（中国）有限公司 | The method and apparatus of VNF are disposed in NFV system based on Openstack |
| CN110365508A (en) * | 2018-04-10 | 2019-10-22 | 中国移动通信有限公司研究院 | The method and network function of virtual network function instantiation virtualize composer |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190052528A1 (en) * | 2016-03-28 | 2019-02-14 | Nec Corporation | Network function virtualization management orchestration apparatus, method |
-
2019
- 2019-11-29 CN CN201911207569.4A patent/CN112887118B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3249860A1 (en) * | 2015-01-23 | 2017-11-29 | Nec Corporation | Method, device, and program for management and orchestration of network functions virtualization |
| CN105955824A (en) * | 2016-04-21 | 2016-09-21 | 华为技术有限公司 | Method and device for configuring virtual resource |
| CN108886492A (en) * | 2016-04-28 | 2018-11-23 | 日本电气株式会社 | Network function virtual management and layout device, methods and procedures |
| CN108156095A (en) * | 2016-12-02 | 2018-06-12 | 中兴通讯股份有限公司 | Resource determining method and device, NFVO |
| EP3550775A1 (en) * | 2016-12-02 | 2019-10-09 | ZTE Corporation | Resource determination method and device, and nfvo |
| CN107145380A (en) * | 2017-03-27 | 2017-09-08 | 华为技术有限公司 | Virtual resource method of combination and device |
| CN107948006A (en) * | 2018-01-09 | 2018-04-20 | 重庆邮电大学 | A kind of method of combination and device for virtualizing network function |
| CN110365508A (en) * | 2018-04-10 | 2019-10-22 | 中国移动通信有限公司研究院 | The method and network function of virtual network function instantiation virtualize composer |
| CN109889377A (en) * | 2019-01-29 | 2019-06-14 | 京信通信系统（中国）有限公司 | The method and apparatus of VNF are disposed in NFV system based on Openstack |
Non-Patent Citations (2)
| Title |
|---|
| A. Morton ; AT amp ; amp ; amp ; T Labs ; .Considerations for Benchmarking Virtual Network Functions and Their Infrastructure draft-ietf-bmwg-virtual-net-01.IETF .2015,全文. * |
| 基于NFV的移动核心网可靠性研究;刘利锋;通信技术;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112887118A (en) | 2021-06-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10700947B2 (en) | Life cycle management method and device for network service | |
| US10347542B2 (en) | Client-initiated leader election in distributed client-server systems | |
| US10642638B2 (en) | Virtual machine placement with automatic deployment error recovery | |
| EP3291499B1 (en) | Method and apparatus for network service capacity expansion | |
| US9626172B2 (en) | Deploying a cluster | |
| WO2019184164A1 (en) | Method for automatically deploying kubernetes worker node, device, terminal apparatus, and readable storage medium | |
| EP3300298B1 (en) | Method and apparatus for switching vnf | |
| CN107005426B (en) | Method and device for managing life cycle of virtual network function | |
| CN110224860B (en) | Load balancing application creation method and device, computer equipment and storage medium | |
| CN110661647A (en) | Life cycle management method and device | |
| EP3249871A1 (en) | Method and device for updating network service descriptor | |
| CN109358967B (en) | ME platform APP instantiation migration method and server | |
| US20160203014A1 (en) | Managing virtual machines using globally unique persistent virtual machine identifiers | |
| US9971589B2 (en) | Upgrade management for a shared pool of configurable computing resources | |
| US11586447B2 (en) | Configuration after cluster migration | |
| US8639908B2 (en) | Dynamically managing available data storage within an automated data storage system | |
| US20220206836A1 (en) | Method and Apparatus for Processing Virtual Machine Migration, Method and Apparatus for Generating Virtual Machine Migration Strategy, Device and Storage Medium | |
| CN111506388B (en) | Container performance detection method, container management platform and computer storage medium | |
| CN107360015B (en) | Method and device for switching shared storage | |
| CN112887118B (en) | VNF information acquisition and control method and device, NFVO, VNFM and storage medium | |
| CN114008545A (en) | Configurable memory device connected to a microprocessor | |
| US10223241B2 (en) | Resuming a remote debugging session using a backup node | |
| US11405277B2 (en) | Information processing device, information processing system, and network communication confirmation method | |
| CN112889247B (en) | VNF service instantiation method and device | |
| CN112379845B (en) | Cluster capacity expansion method and device, computing equipment and storage medium |
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 |