WO2019174449A1

WO2019174449A1 - Method and apparatus for deploying virtualized network elements

Info

Publication number: WO2019174449A1
Application number: PCT/CN2019/075742
Authority: WO
Inventors: 张晓伟; 李世涛; 杨旭; 吴勇
Original assignee: 华为技术有限公司
Priority date: 2018-03-13
Filing date: 2019-02-21
Publication date: 2019-09-19
Also published as: CN110275756B; CN110275756A

Abstract

The present invention relates to a method and apparatus for deploying virtualized network elements. The method for deploying virtualized network elements comprises: a center manager receives an instantiation request comprising deployment requirements of virtualized network elements, and the center manager manages the virtualized network elements in one or more logic areas; the center manager determines deployment requirements of virtual machine network elements and deployment requirements of container network elements on the basis of the deployment requirements of the virtualized network elements; the center manager manages life cycles of the virtual machine network elements on the basis of the deployment requirements of the virtual machine network elements; edge managers obtain the deployment requirements of the container network elements from the center manager, the edge managers being in the logic areas managed by the center manager; and the edge managers manage life cycles of containers on the basis of the deployment requirements of the container network elements. The configuration of the center manager and the edge managers can well support the deployment of the containers.

Description

Virtualized network element deployment method and device

This application claims the priority of the Chinese Patent Application No. 201101203961.0, filed on March 13, 2018, with the application number of 201110203961.0, and the invention is entitled "Deployment Method and Device of Virtualized Network Element", the entire contents of which are incorporated by reference. In this application.

Technical field

The present invention relates to the field of computer networks, and in particular, to a method and an apparatus for deploying a virtualized network element.

Background technique

In the past, based on Openstack, a Network Function Virtualization (NFV) platform was established. By using versatile hardware such as x86 and virtualization technology, it carries a lot of functional software processing, thereby reducing the expensive equipment cost of the network. Through software and hardware decoupling and functional abstraction, network device functions are no longer dependent on dedicated hardware. Resources can be fully and flexibly shared, enabling rapid development and deployment of new services, and automatic deployment, elastic scaling, and fault isolation based on actual business requirements. And self-healing.

In the deployment of virtualized network elements in the past, there is a deployment mode that only supports virtual machines, but it cannot be effectively implemented based on Network Functions Virtualization Management and Orchestration (NFV-MANO, hereinafter referred to as MAMO). Good support for container deployment.

Summary of the invention

The embodiment of the invention provides a method and a device for deploying a virtualized network element.

In a first aspect, an embodiment of the present invention is directed to a method for deploying a virtualized network element, including: receiving, by a central manager, an instantiation request, where the instantiation request includes a deployment requirement of a virtualized network element, and the central manager pair The one or more logical areas are managed by the virtualized network element; the central manager determines the deployment requirements of the virtual machine network element and the deployment requirements of the container network element based on the deployment requirements of the virtualized network element, the virtualized network element Included in the virtual machine network element and the container network element, where the virtual machine network element is configured based on a virtual machine, the container network element is configured based on the deployment of the container; the central manager is based on the virtual machine network element The deployment requires managing the life cycle of the virtual machine network element; the edge manager obtains the deployment requirement of the container network element from the central manager, and the edge manager is in each of the management managed by the central manager In the logical area; and the edge manager manages the life cycle of the container based on the deployment requirements of the container network element.

According to the above, MANO-based deployment of virtual machines and containers can be realized. In addition, the virtual machine-based virtual machine network element of all logical areas is subjected to lifecycle management through the central manager, and the container-based container network elements of the respective logical areas are subjected to lifecycle management through an edge manager other than the central manager, thereby Implement hierarchical management, which enables rapid deployment of containers and saves resources.

With the above aspect, in the deployment method, the central manager manages the life cycle of the virtual machine network element based on the deployment requirement of the virtual machine network element, at least: the central manager uses the virtual machine network The deployment of the virtual machine is required to be sent to the virtual machine deployment unit, and the virtual deployment unit performs the deployment of the virtual machine on the logical area managed by itself according to the deployment requirement of the virtual network element; the central manager from the virtual machine The deployment unit obtains the deployment result of the virtual machine.

According to the above, the central edge manager directly manages the life cycle of the virtual machine-based virtual machine network element of all the logical areas managed.

With the above aspect, in the deployment method, the edge manager manages the life cycle of the container based on the deployment requirement of the container network element, at least: the edge manager sends the deployment requirement of the container network element Deploying a unit to a container, the container deployment unit performing deployment of the container on a logical area managed by itself according to a deployment requirement of the container network element; the edge manager obtaining deployment of the container from the container deployment unit a result; and the edge manager sends the deployment result of the container to the central manager.

According to the above, the edge manager manages the life cycle of the container-based container network element of the managed logical area, and can quickly perform the container deployment and effectively implement the life cycle of the container-based container network element. Management reduces latency when generating container-based container NEs and reduces the chances of deployment failures. Thereby, it is possible to effectively utilize a container that is quick to start and consumes less resources.

In conjunction with the above aspects, in the deployment method, the container further includes a virtual machine that deploys the container and a physical machine that deploys the container.

In combination with the above aspect, in the deployment method, the logical area is any one of a data center, a region, an available area, and a host group.

In combination with the above aspect, in the deployment method, the central manager is disposed in any one of the logical regions or in an area other than the logical region.

In a second aspect, an embodiment of the present invention relates to a device for deploying a virtualized network element, including: a central manager that manages virtualized network elements for one or more logical areas; and an edge manager at each of the foregoing In the logical area, the central manager includes: a first receiving unit, configured to receive an instantiation request, where the instantiation request includes a deployment requirement of the virtualized network element, and a determining unit, configured to be based on the virtualized network element The deployment requirements are used to determine the deployment requirements of the virtual machine network element and the deployment requirements of the container network element. The virtualized network element includes a virtual machine network element and a container network element, and the virtual machine network element is configured based on the deployment of the virtual machine. The container network element is configured based on the deployment of the container; and the management unit is configured to manage the life cycle of the virtual machine network element based on the deployment requirement of the virtual machine network element, where the edge manager includes: a receiving unit, configured to acquire a deployment requirement of the container network element from the central manager, and a management unit, configured to: the container based on a deployment requirement of the container network element Life-cycle management.

In conjunction with the above aspect, in the deployment apparatus, the central manager further includes: a sending unit, configured to send a deployment requirement of the virtual machine network element to a virtual machine deployment unit, where the virtual deployment unit is based on the virtual The deployment of the network element requires the deployment of the virtual machine to the logical area managed by the virtual device. The second receiving unit is configured to obtain the deployment result of the virtual machine from the virtual machine deployment unit.

In conjunction with the above aspect, in the deployment apparatus, the edge manager further includes: a first sending unit, configured to send a deployment request of the virtual network element to a container deployment unit, where the container deployment unit is based on the container The deployment of the network element requires the deployment of the container for the logical area managed by itself; the second receiving unit is configured to obtain the deployment result of the container from the container deployment unit; and the second sending unit is configured to: The deployment result of the container is sent to the central manager.

In conjunction with the above aspects, in the deployment apparatus, the container further includes a virtual machine that deploys the container and a physical machine that deploys the container.

In combination with the above aspect, in the deployment apparatus, the logical area is any one of a data center, a region, an available area, and a host group.

In connection with the above aspect, in the deployment apparatus, the center VNFM is disposed in any of the logical areas or in an area other than the logical area.

In a third aspect, an embodiment of the present invention provides a computer readable storage medium having stored thereon instructions that are executed by a computer to implement the methods described in the above aspects.

In a fourth aspect, an embodiment of the present invention provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods described in the various aspects above.

In a fifth aspect, embodiments of the present invention provide a computer program that, when run on a computer, causes the computer to perform the methods described in the various aspects above.

DRAWINGS

1 is a schematic diagram of an NFV architecture according to an embodiment of the present invention;

2 is a schematic diagram showing the relationship of logical areas according to an embodiment of the present invention;

3 is a schematic diagram of a MANO management of a VNF in the past;

4 is an information exchange flow diagram in the MANO of FIG. 3;

FIG. 5 is a schematic diagram showing management of a virtualized network element based on VNFM according to an embodiment of the present invention; FIG.

Figure 6 is a flow diagram showing information interaction in the management of Figure 5;

FIG. 7 is a flowchart showing an example of a method for deploying a virtualized network element according to an embodiment of the present invention;

FIG. 8 is a schematic block diagram of a network device deployed by a virtualized network element according to an embodiment of the present invention.

detailed description

FIG. 1 is a schematic diagram showing an NFV (Network Functions Virtualization) architecture according to an embodiment of the present invention. In NFV technology, it mainly involves the following three aspects: the virtual network function to be set, also called virtualized network element; the network function virtualization infrastructure (NFVI) that implements the above virtualized network element; The management and organization of the network element MAMO.

A virtualized network element is a virtual application that implements functions by deploying VMs (virtual machines) and containers for virtualized network elements. The virtualized network elements may include VMs that implement some or all of their functions. At least one virtual machine network element (also referred to as a VNF), and at least one container network element (referred to as CNF) constructed by the container to perform some or all of its functions. For example, the virtual machine network element VNF can be decomposed into a set of VNFC (Virtual Network Function Unit, VNF Component) and a connection relationship between the VNFCs, and each VNFC is mapped to one VM. The container network element CNF is also the same, including the container and the connection relationship between the containers. Here, the container network element may include a bare metal server that deploys the container, and may also include a virtual machine that deploys the container, and may also include both, and specifically, may be selected according to deployment requirements. In the following description, the container is described by taking Docker and Docker Over VM as an example, but they are only an example of a container, and may be other containers.

NFVI implements virtualized network elements by deploying VMs or Dockers or Docker Over VMs on its physical resources, providing virtualized resources needed to support the execution of virtualized network elements. NFVI combines hardware components and software components, is a resource pool, and is a physical infrastructure connected through a communication network.

MANO is responsible for the management and orchestration of the entire NFVI resources, responsible for the mapping and association of business networks and NFVI resources, including the orchestration and lifecycle management of physical and / or software resources supporting the virtualisation of physical infrastructure, and the life cycle of virtualized network elements. management. MANO is jointly completed/provided by NFVO (Network Functions Virtualization Orchestrator), VNFM (Virtualized Network Functions Manager), and VIM (Virtualized Infrastructure Manager). Features. NFVO mainly provides global resource scheduling capabilities and global business orchestration capabilities. The VNFM is responsible for the lifecycle management of the virtualized network element, including the creation and termination of virtualized network elements, the setting of virtualized network elements, the configuration of virtualized network elements, the monitoring of virtualized network elements (health, performance, etc.), and virtual The ability to automatically recover and relocate the network element failure supports various simple and complex virtualized network elements. VIM is an NFVI management system that includes common physical and virtual resource management, execution resource deployment and scheduling. However, the functional division of the NFVO, VNFM, and VIM of the present invention is not limited thereto, and other functional divisions may be performed.

The above describes the virtualized network elements deployed by MANO, including virtual machine network elements deployed by VM, and container network elements based on Docker-based deployment or container network elements based on Docker Over VM-based deployment. When deploying to a VM, the VIM is, for example, Openstacke or VMware. When deploying a Docker or Docker Over VM, the VIM may be, for example, a container platform of the industry such as kubenates. The container is characterized by fast startup speed and low resource consumption.

2 is a schematic diagram showing a logical area according to an embodiment of the present invention. The logical area includes a data center (DC), a Region, an Availability Zone (AZ), and a Host Aggregate (HA). A DC is a classification of logical areas that are divided from a network connection perspective. The DC can accommodate multiple servers as well as communication devices that are placed together because they have the same environmental and physical security requirements and are placed for ease of maintenance. Region is a classification of physical regions based on geographical regions, such as Central China and East China. Usually a Virtual Private Cloud (VPC) tenant chooses to be in a Region and does not cross the Region. The DC and Region divide the physical region from different dimensions. There may be intersections between the two. One DC may contain multiple Regions, and one Region may span multiple DCs. AZ is an independent, physically isolated Availability Zone, and a Region contains multiple AZs. When an AZ fails, it does not affect other AZs. HA is composed of multiple Hosts in AZ. Multiple HAs can be included in one AZ. An HA can contain multiple Hosts. As shown in FIG. 2, DC1 includes Region1 and Region2, Region3 spans DC2 and DC3, Region1 includes AZ1 and AZ2, and AZ1 includes HA11 and HA12.

FIG. 3 is a schematic diagram showing management of a VNF by a conventional MANO. 4 is an information exchange flow diagram in the MANO of FIG. 3. Description will be made below with reference to FIGS. 3 and 4.

In Figure 3, the VNFs of multiple DCs are managed by the VNFM in MANO. The VNFM can be installed in a DC that deploys the VNF, or it can be installed in a separate DC. In this example, the VNFM is installed in a separate DC0, and multiple VNFs are set in DC1 and DC2, respectively. As shown in FIG. 4, in step S41, the VNFM in the MANO sends a deployment request of the VM of the VNF to the VIM1, and the VM of the VNF of the DC1 is deployed. In step S42, VIM1 feeds back the deployment result of the VM of the VNF to the VNFM. In step S43, the VNFM sends the deployment request of the VNF to the VIM2, and performs the deployment of the VM of the VNF of the DC2. In step S44, the VIM2 feeds back the VM deployment result of the VNF to the VNFM. In this example, the VNFM manages the lifecycle of the VNFs of the various DCs.

In this example, the deployment method only supports VM deployment, does not support Docker deployment, and does not support Docker Over VM deployment.

The invention proposes a VMO based on MAMO to support the deployment method of VM, Docker and Docker Over VM.

The VNFM management node in MANO supports a separate architecture, that is, the VNFM function is split in two steps, one is responsible for VM-based VNF lifecycle management in all regions, and the other is responsible for Docker or Docker Over VM-based CNF in each region. Lifecycle management. FIG. 5 is a schematic diagram of the VNFM-based management of a virtualized network element according to the embodiment. FIG. 6 shows a flow diagram of information interaction in the management of FIG. 5.

In FIG. 5, the request information for deploying the virtualized network element is synchronized to the central VNFM that manages DC0, DC1, and DC2, and the central VNFM performs unified management on the deployed virtual network elements of each DC. Here, the center VNFM may be provided in a separate DC or in one of DC0, DC1, and DC2. In addition, in each of DC0, DC1, and DC2, a VNF/CNF near-end edge side management unit VNFM (hereinafter also referred to as edge VNFM) is provided, and the life of the NF based on Docker and Dokerk Over VM for the logical area is set. The cycle is managed, and the edge VNFM is responsible for the lifecycle management of CNF based on Docker and Docker Over VM in the region. Here, the central VNFM performs VM-based VNF lifecycle management for all logical areas managed, and the overall architecture of the central VNFM and the edge VNFM supports VM, Docker, and Docker Over VM mode deployment.

When receiving the deployment request of the virtualized network element, the central VNFM determines the deployment request of the VM-based virtual machine network element and the deployment request of the container-based container network element.

During the VM deployment, the central VNFM sends the VM deployment requirements to the deployed VIMs of the VMs managing the logical areas. The VIMs for VM deployment are, for example, openstack or VMware. The VIMs are VMs in the area managed by the VIM according to the deployment requirements. After deployment, VIM feeds back the VM's deployment results to the central VNFM. The central VNFM is responsible for the lifecycle management of VM-based VNFs, such as managing the generation of VM-based VNFs.

In the Docker deployment, the central VNFM sends the deployment requirements of the Docker or Docker Over VM of each logical area to each logical area, which can be only the Docker deployment request, the Docker Over VM deployment request, or they The combination. The central VNFM sends the deployment requirements for the Docker or Docker Over VM to the zone edge VNFM. Taking Docker deployment as an example, the central VNFM directly sends the Docker deployment requirements to the edge VNFM. The edge VNFM manages the lifecycle of the Docker-based CNF and passes the deployment requirements to the VIM that manages the deployment of the container. For example, the container management platform such as K8S/Mesos, VIM deploys Docker according to the deployment requirements, and feeds the results back to the edge VNFM. The edge VNFM feeds back the deployment results of the area to the central VNFM. The central VNFM collects the logic from each edge VNFM. The Docker deployment of the region is focused on display and management. Here, the edge VNFM manages the lifecycle of the Docker-based CNF.

The specific deployment method will be described in detail with reference to FIG.

As shown in FIG. 6, the central VNFM manages the deployment of virtualized network elements of logical area 1 and logical area 2. In step S610, the central VNFM obtains an instantiation request from the outside, the instantiation request including a deployment requirement to instantiate the virtualized network element VNF1. The central VNFM determines the deployment requirements of the VM-based VNF and the deployment requirements of the Docker-based CNF based on the received deployment requirements of the VNF1. In the case where the central VNFM determines the deployment requirements of the VM-based VNF and the deployment requirements of the Docker-based CNF, in step S611, the central VNFM sends a deployment request of the VM to the VIM 11 of the logical area 1, the VIM11 follows the secondary VNFM. The received deployment requires VM deployment, where VIM11 deploys and manages the VMs of logical area 1. In step S612, the VIM 11 directly feeds back the deployment result of the VM to the central VNFM.

Next, in step S613, the central VNFM sends the Docker-based network element deployment request in the deployment request of the instantiated VNF1 to the edge VNFM of the area 1, that is, the indication area 1 edge VNFM arranges DC1 according to the Docker manner. The edge VNFM orchestrate the Docker-based CNF according to the allocation requirements, and conduct lifecycle management of the CNF. In step S614, the edge VNFM sends the Docker deployment request to the VIM1, the VIM1 performs the deployment of the Docker in the area 1 according to the deployment requirement, and in step S615, the VIM1 feeds back the Docker deployment result to the edge VNFM, in step S616, The edge VNFM sends the Docker deployment results to the central VNFM. In S617, the central VNFM uniformly displays and manages the deployment results of all VMs and Dockers to complete the instantiation of VNF1.

Similarly, in step S618, the central VNFM obtains an instantiation request from the outside, the instantiation request including a deployment requirement for deploying the virtualized network element VNF2. The central VNFM judges based on the received deployment request of the VNF2, and in the case that the central VNFM determines the deployment of the VM-based VNF and the deployment of the Docker-based CNF, the central VNFM transmits to the VIM 21 of the logical area 2 in step S619. The deployment of the VM requires that the VIM 21 deploy the VM in accordance with the deployment requirements received from the central VNFM, where the VIM 21 deploys and manages the VMs of the logical area 2. In step S620, the VIM 21 directly feeds back the deployment result of the VM to the central VNFM.

Next, in step S621, the central VNFM sends the Docker-based network element deployment request in the deployment request of the instantiated VNF2 to the edge VNFM of the area 2, that is, the edge VNFM indicating the area 2 arranges the DC2 in the Docker manner. The edge VNFM orchestrate the Docker-based CNF according to the allocation requirements, and conduct lifecycle management of the CNF. In step S622, the edge VNFM sends the Docker deployment request to the VIM 21, the VIM 21 performs the deployment of the Docker in the area 2 according to the deployment requirement, and in step S622, the VIM 21 feeds back the Docker deployment result to the edge VNFM, in step S623, The edge VNFM sends the Docker deployment results to the central VNFM. In S624, the central VNFM uniformly displays and manages the deployment results of all VMs and Dockers, thereby completing the instantiation of VNF2.

The embodiment of the present invention is not limited to the order shown in FIG. 6, and the order can be appropriately changed according to the execution time. Depending on the deployment requirements, VM-based VNF deployment, container-based CNF deployment can be performed simultaneously, or container-based CNF deployment can be performed first, followed by VM-based VNF deployment.

Deploying an edge VNFM that manages the lifecycle of Docker-based CNF in each DC/AZ, etc., implements secondary management by service characteristics, that is, central VNFM manages lifecycle management of VM-based VNF in all areas, edge VNFM Manage the lifecycle management of CNFs based on Docker or Docker Over VM in their respective regions. The beneficial effects achieved by the present invention are summarized as follows: Lifecycle management of Docker and Docker Over VM scenarios is solved on the ETSI architecture.

Through the above, MANO-based deployment of virtual machines and containers can be realized. In addition, the VM-based virtual machine network elements of all logical areas are managed by the central VNFM, and the container-based container network elements of the respective logical areas are managed by the edge VNFM outside the central VNFM to implement hierarchical management. Ability to quickly deploy containers and save resources.

In addition, the deployment of the container can be performed quickly, and the life cycle of the container-based container network element can be effectively managed, the delay in generating the container-based container network element is reduced, and the probability of deployment failure is reduced. Thereby, it is possible to effectively utilize a container that is quick to start and consumes less resources.

That is, as shown in FIG. 7, the VNFM secondary separation architecture performs the following deployment method of the VNF.

In step S71, the central VNFM receives an instantiation request, where the instantiation request includes a deployment requirement of the virtualized network element, and the central VNFM performs management of the virtualized network element on the one or more logical areas; in step S72, The central VNFM determines the deployment requirements of the virtual machine network element and the deployment requirements of the container network element based on the deployment requirements of the virtualized network element, where the virtualized network element includes a virtual machine network element and a container network element, and the virtual machine network The component is configured based on the deployment of the VM, and the container network element is configured based on the deployment of the container. In step S73, the central VNFM manages the life cycle of the virtual machine network element based on the deployment requirement of the virtual network element. In step S74, the edge VNFM acquires the deployment requirement of the container network element from the center VNFM; in step S75, the edge VNFM manages the life cycle of the container based on the deployment requirement of the virtual network element.

Optionally, in the foregoing deployment method, the central VNFM manages the life cycle of the virtual machine network element based on the deployment requirement of the virtual network element, at least: the central VNFM sends the deployment requirement of the virtual machine network element Deploying a virtual machine to the virtual machine, the virtual deployment unit performing the deployment of the virtual machine on the logical area managed by the virtual network element; the central VNFM acquiring the deployment of the VM from the virtual machine deployment unit result.

Optionally, in the foregoing deployment method, the edge VNFM manages the life cycle of the container based on the deployment requirement of the container network element, at least: the edge VNFM sends the deployment requirement of the container network element to the container deployment unit, where The container deployment unit performs the deployment of the container on the logical area managed by itself according to the deployment requirement of the container network element; the edge manager obtains the deployment result of the container from the container deployment unit; and the edge The VNFM sends the deployment result of the container to the central VNFM.

Optionally, in the foregoing deployment method, the container network element includes a virtual machine that deploys the container and a physical machine that deploys the container.

Optionally, in the foregoing deployment method, the logical area is one of DC, Region, AZ, and HA.

Optionally, in the above deployment method, the central VNFM is disposed in one of each of the logical regions, or is disposed in an area other than the logical region.

With the embodiments of the present invention, MANO-based deployment of virtual machines and containers can be implemented. In addition, the VM-based virtualized network element of all logical areas is subjected to lifecycle management through the central VNFM, and the container-based container network elements of the respective logical areas are managed by the edge VNFM outside the central VNFM, thereby implementing hierarchical management. Ability to quickly deploy containers and save resources.

Next, a deployment apparatus of a MANO-based VNF corresponding to the above method will be described.

Embodiments of the present invention relate to a device for deploying a virtualized network element, including: a central VNFM for managing virtualized network elements of one or more logical areas; and an edge VNFM at each of the foregoing In the logical area, the central VNFM includes: a first receiving unit, configured to receive an instantiation request, where the instantiation request includes a deployment requirement of the virtualized network element, and a determining unit, configured to deploy based on the virtualized network element Requiring to determine the deployment requirements of the virtual machine network element and the deployment requirements of the container network element, where the virtualized network element includes a virtual machine network element and a container network element, where the virtual machine network element is configured based on VM deployment, The container network element is configured based on the deployment of the container; and the management unit is configured to manage the life cycle of the virtual machine network element based on the deployment requirement of the virtual machine network element, where the edge VNFM includes: a first receiving unit a deployment request for obtaining the container network element from the central VNFM; a management unit, configured to perform a life cycle of the container based on a deployment requirement of the container network element management.

Optionally, the foregoing deployment apparatus further includes: in the deployment apparatus, the central VNFM further includes: a sending unit, configured to send a deployment requirement of the virtual machine network element to a virtual machine deployment unit, where the virtual deployment The unit performs the deployment of the virtual machine on the logical area managed by the virtual network element based on the deployment requirement of the virtual network element. The second receiving unit is configured to obtain the deployment result of the virtual machine from the virtual machine deployment unit.

Optionally, in the deployment device, the edge VNFM further includes: a first sending unit, configured to send a deployment request of the virtual network element to a container deployment unit, where the container deployment unit is based on the container network The deployment of the container requires the deployment of the container for the logical area managed by itself; the second receiving unit is configured to obtain the deployment result of the container from the container deployment unit; and the second sending unit is configured to use the container The deployment results are sent to the central VNFM.

Optionally, in the deploying device, the container network element includes a virtual machine that deploys a container and a physical machine that deploys the container.

Optionally, in the foregoing deployment apparatus, the logical area is one of DC, Region, AZ, and HA.

Optionally, in the foregoing deployment apparatus, the central VNFM is disposed in any one of the logical areas, or may be disposed in an area other than the logical area.

In addition, with this embodiment of the present invention, it is possible to realize the deployment of MANO-based supporting virtual machines and containers. In addition, the virtual machine-based virtual machine network elements of all logical areas are managed by the central VNFM, and the container-based container network elements of the respective logical areas are managed by the edge VNFM outside the central VNFM to implement hierarchical management. It enables rapid deployment of containers and saves resources.

FIG. 8 is a schematic block diagram of a network device deployed by a VNF according to an embodiment of the present invention. As shown in FIG. 8, network device 80 includes an input device 81, an input interface 82, a processor 83, a memory 84, an output interface 85, and an output device 86.

The input interface 82, the processor 83, the memory 84, and the output interface 85 are connected to each other through a bus 87. The input device 81 and the output device 86 are respectively connected to the bus 87 through the input interface 82 and the output interface 85, thereby being connected to the network device 80. Other components are connected.

Specifically, input device 81 receives input information from the outside and transmits the input information to processor 83 via input interface 82; processor 83 processes the input information based on computer executable instructions stored in memory 84 to generate output information, The output information is temporarily or permanently stored in the memory 84, and then the output information is transmitted to the output device 86 through the output interface 85; the output device 86 outputs the output information to the outside of the network device 80 for use by the user.

Network device 80 can perform the steps in embodiments of the present invention.

Processor 83 can be one or more central processing units (CPUs). In the case where the processor 83 is a CPU, the CPU may be a single core CPU or a multi-core CPU.

The memory 84 may be, but not limited to, one of a random access memory (RAM), a read only memory (ROM), an erasable programmable read only memory (EPROM), a compact disk read only memory (CD-ROM), a hard disk, or the like. A variety. Memory 84 is used to store program code.

It can be understood that, in the embodiment of the present invention, the network device 80 of FIG. 8 may be a deployment device of a virtualized network element.

The various parts of the specification are described in a progressive manner, and the same or similar parts between the various embodiments may be referred to each other, and each embodiment focuses on differences from other embodiments. In particular, for device and system embodiments, the description is relatively simple as it is substantially similar to the method embodiment, and the relevant portions can be found in the description of the method embodiments.

Claims

A method for deploying a virtualized network element, comprising:

The central manager receives an instantiation request, the instantiation request includes a deployment requirement of a virtualized network element, and the central manager performs management of the virtualized network element on one or more logical areas;

The central manager determines the deployment requirements of the virtual machine network element and the deployment requirements of the container network element based on the deployment requirements of the virtualized network element, where the virtualized network element includes a virtual machine network element and a container network element, and the virtual machine The network element is constructed based on the deployment of the virtual machine, and the container network element is constructed based on the deployment of the container;

The central manager manages a life cycle of the virtual machine network element based on a deployment requirement of the virtual machine network element;

An edge manager obtains a deployment requirement of the container network element from the central manager, the edge manager being in each logical area managed by the central manager;

The edge manager manages the lifecycle of the container based on deployment requirements of the container network element.
The deployment method of claim 1 wherein

The management of the virtual machine network element life cycle based on the deployment requirements of the virtual machine network element includes:

The central manager sends the deployment request of the virtual machine network element to the virtual machine deployment unit, and the virtual deployment unit performs the virtual machine deployment on the logical area managed by the virtual network element based on the deployment requirement of the virtual network element. ;

The central manager obtains a deployment result of the virtual machine from the virtual machine deployment unit.
The deployment method according to claim 1 or 2, characterized in that

The edge manager manages the life cycle of the container based on the deployment requirements of the container network element at least:

The edge manager sends the deployment requirement of the container network element to the container deployment unit, and the container deployment unit performs the container deployment on the logical area managed by itself according to the deployment requirement of the container network element;

The edge manager obtains a deployment result of the container from the container deployment unit;

The edge manager sends the deployment result of the container to the central manager.
The deployment method according to any one of claims 1 to 3, characterized in that

The container network element includes a virtual machine that deploys the container and a physical machine that deploys the container.
The deployment method according to any one of claims 1 to 4, characterized in that

The logical area is one of a data center, a region, an available area, and a host group.
The deployment method according to any one of claims 1 to 5, characterized in that

The center manager is disposed in any one of the logical regions or is disposed in an area other than the logical region.
A device for deploying a virtualized network element, comprising:

a central manager that manages virtualized network elements for one or more logical areas;

An edge manager, in each of the logical regions,

The central manager includes:

a first receiving unit, configured to receive an instantiation request, where the instantiation request includes a deployment requirement of the virtualized network element;

a determining unit, configured to determine, according to a deployment requirement of the virtualized network element, a deployment requirement of a virtual machine network element and a deployment requirement of a container network element, where the virtualized network element includes a virtual machine network element and a container network element, The virtual machine network element is constructed based on the deployment of the virtual machine, and the container network element is constructed based on the deployment of the container;

a management unit, configured to manage a life cycle of the virtual machine network element based on a deployment requirement of the virtual machine network element,

The edge manager includes:

a first receiving unit, configured to acquire, from the central manager, a deployment requirement of the container network element;

a management unit, configured to manage a life cycle of the container based on a deployment requirement of the container network element.
The deployment device of claim 7 wherein:

The central manager also includes:

a sending unit, configured to send the deployment requirement of the virtual machine network element to the virtual machine deployment unit, where the virtual deployment unit performs the virtual machine deployment on the logical area managed by the virtual network element based on the deployment requirement of the virtual network element ;

And a second receiving unit, configured to acquire a deployment result of the virtual machine from the virtual machine deployment unit.
A deployment device according to claim 7 or 8, wherein

The edge manager further includes:

a first sending unit, configured to send, to the container deployment unit, the deployment requirement of the virtual network element, where the container deployment unit performs the container deployment on the logical area managed by the container network element according to the deployment requirement of the container network element;

a second receiving unit, configured to acquire a deployment result of the container from the container deployment unit;

a second sending unit, configured to send the deployment result of the container to the central manager.
A deployment device according to any one of claims 7 to 9, wherein

The container network element includes a virtual machine that deploys the container and a physical machine that deploys the container.
A deployment device according to any one of claims 7 to 10, wherein

The logical area is one of a data center, a region, an available area, and a host group.
A deployment apparatus according to any one of claims 7 to 11, wherein

The center manager is disposed in any one of the logical regions or is disposed in an area other than the logical region.