WO2017181877A1 - Procédé et dispositif d'attribution de ressource virtuelle - Google Patents

Procédé et dispositif d'attribution de ressource virtuelle Download PDF

Info

Publication number
WO2017181877A1
WO2017181877A1 PCT/CN2017/080112 CN2017080112W WO2017181877A1 WO 2017181877 A1 WO2017181877 A1 WO 2017181877A1 CN 2017080112 W CN2017080112 W CN 2017080112W WO 2017181877 A1 WO2017181877 A1 WO 2017181877A1
Authority
WO
WIPO (PCT)
Prior art keywords
vnf
resource
virtual
vnfm
vim
Prior art date
Application number
PCT/CN2017/080112
Other languages
English (en)
Chinese (zh)
Inventor
王骅
Original Assignee
华为技术有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2017181877A1 publication Critical patent/WO2017181877A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources

Definitions

  • the present application relates to the field of network technologies, and in particular, to a virtual resource configuration method and apparatus.
  • NFV Network Function Virtualization
  • COTS Common Commercial shelf product
  • each network element used in the telecommunication network can be transformed into a stand-alone application, which can be flexibly deployed on a unified infrastructure platform built by standards-based servers, storage, and switches, and through virtualization technology to the infrastructure.
  • Hardware device resource pooling and virtualization providing virtual resources to upper-layer applications, enabling application and hardware decoupling, enabling each application to rapidly increase virtual resources to achieve rapid expansion of system capacity, or to rapidly reduce virtual resources to achieve shrinkage
  • the purpose of system capacity greatly enhances the flexibility of the network.
  • the common COTS server is used to form a shared resource pool. The newly developed services do not need to be separately deployed with hardware devices, which greatly shortens the time for new services to go online.
  • the foundation of NFV technology includes cloud computing technology and virtualization technology.
  • Hardware devices such as general-purpose COTS computing/storage/network can be decomposed into multiple virtual resources through virtualization technology for use by various applications in the upper layers.
  • virtualization technology Through the virtualization technology, the decoupling between the application and the hardware is realized, so that the virtual resource supply speed is greatly increased.
  • cloud computing technology Through the cloud computing technology, the elastic scalability of the application can be realized, and the virtual resource is matched with the service load, which not only improves the virtual resource. Utilize efficiency and improve system response rate.
  • the Data Center (DC) is one of the more mature areas of NFV technology applications.
  • disaster recovery DCs need to be deployed outside the production DC to enable DR DC takeover services during DC faults.
  • the existing disaster recovery DC adopts the cold backup mode, it will take a long time and slow to start because of the need to restore data and network connection when taking over the service.
  • the hot backup mode it needs to be pre-processed. Leave a lot of virtual resources, especially when a disaster tolerant DC corresponds to multiple production DCs, it will take up a lot of storage and computing resources.
  • the application provides a virtual resource configuration method and device, which can not only quickly initiate the takeover service, but also reduce the resource reservation amount of the disaster tolerant DC.
  • the first aspect provides a virtual resource configuration method, where the method includes:
  • the Virtual Network Function Manager reads the virtual machine (VM) of the virtual network function (VNF) in the description file.
  • the resource configuration information when the first VNF of the active state is deployed, the VNFM sends a virtual resource request to the virtual infrastructure manager (VIM) according to the first reserved resource ratio indicated by the resource configuration information, And creating, according to the resource that the VIM responds to the virtual resource request, the VM of the first VNF; when deploying the second VNF in the standby state, the ratio of the second reserved resource indicated by the VNFM according to the resource configuration information Sending a virtual resource request to the VIM, and creating a VM of the second VNF according to the resource that the VIM requests to allocate in response to the virtual resource.
  • the VNF of the active state and the VNF of the standby state allocate different resources. Since the standby VNF is also in the running state, it can be kept backed up when the primary VNF fails. Dynamic session and dynamic data, while maintaining the connection with the surrounding NEs, quickly taking over the service, and reducing the actual resources occupied by the standby VNF, reducing the resource requirements of the DR.
  • the description file is a Virtualized Network Function Descriptor (VNFD), and the VNFM reads a virtual deployment unit about the VNF in the VNFD ( Resource configuration information of the Virtual Deployment Unit (VDU), or the VNFM reads a deployment preference element of the VNF in the VNFD, where the deployment preference element includes resource configuration information of the VNF.
  • VNFD Virtualized Network Function Descriptor
  • VDU Virtual Deployment Unit
  • the VNFM reads a deployment preference element of the VNF in the VNFD, where the deployment preference element includes resource configuration information of the VNF.
  • the description file is a Network Service Descriptor (NSD)
  • the VNFM reads a service deployment preference element in the NSD, and the service deployment preference The element includes resource configuration information of the VNF.
  • the resource configuration information indicates a ratio of reserved resources of the VNF in different states, including: an active state.
  • the actual resources occupied by the standby VNF can be reduced, and the resource requirements of the disaster tolerant DC can be reduced.
  • the VNFM when the first VNF is faulty, the VNFM receives first state notification information sent by the second VNF, where the first state is The notification information is used to indicate that the second VNF is switched from the standby state to the active state; the VNFM sends a virtual resource change request to the VIM according to the first reserved resource ratio, so that the VIM is according to the first A reserved resource ratio allocates resources for the second VNF.
  • the resource allocation ratio of the standby VNF can be dynamically adjusted, thereby facilitating the standby VNF to take over the service and improving the availability of the service provided by the VNF.
  • the VNFM when the first VNF recovers from a fault, the VNFM receives second state notification information sent by the second VNF, where The second state notification information is used to indicate that the second VNF is switched from the active state to the standby state; the VNFM sends a virtual resource change request to the VIM according to the second reserved resource ratio, so that the VIM is based on the VIM
  • the second reserved resource ratio is a resource allocated by the second VNF.
  • a virtual resource configuration apparatus including a virtual network function manager VNFM, a virtual network function VNF, and a virtual infrastructure manager VIM for performing the method in the above first aspect.
  • a virtual resource configuration device including a processor and a memory for performing the method in the first aspect above.
  • a computer storage medium having stored therein program code for performing the method of the first aspect described above.
  • the present application requests different resource allocation ratios for VNFs of different states, so that the VNF of the active state and the VNF of the standby state allocate different resources. Since the standby VNF is also in the running state, it can be maintained when the primary VNF fails. The dynamic session and the dynamic data are backed up, and the connection relationship with the neighboring NEs is maintained. The service is quickly taken over, and the actual resources occupied by the standby VNF are also reduced, and the resource requirements of the disaster tolerant DC are reduced.
  • FIG. 1 is a schematic structural diagram of a network function virtualization network according to an embodiment of the present application.
  • FIG. 2 is a schematic diagram of an implementation environment of a virtual resource configuration method according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of an implementation environment of a virtual resource configuration method according to an embodiment of the present application.
  • FIG. 4 is a flowchart of a first embodiment of a virtual resource configuration method according to an embodiment of the present application.
  • FIG. 5 is a flowchart of a second embodiment of a virtual resource configuration method according to an embodiment of the present application.
  • FIG. 6 is a flowchart of a third embodiment of a virtual resource configuration method according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a first embodiment of a virtual resource configuration apparatus according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a first embodiment of a virtual resource configuration apparatus according to an embodiment of the present application.
  • the technical solution provided by the present application is applied to the NFV network.
  • the VNFM When deploying the VNF, the VNFM requests different resource allocation ratios for the VNFs of different states, so that the VNF of the active state and the VNF of the standby state allocate different resources, because the standby VNF is also It is in the running state. Therefore, when the primary VNF fails, the dynamic session and dynamic data that have been backed up can be maintained. At the same time, the connection relationship with the surrounding network elements is maintained, the service is quickly taken over, and the actual resources occupied by the standby VNF can be reduced. Resource requirements for disaster tolerant DCs.
  • the NFV system 100 can be used in various networks, for example, in a data center network, a carrier network, or a local area network.
  • the NFV system 100 includes an NFV Management and Orchestration (NFV MANO) 101, an NFV Infrastructure (NFV) 130, multiple VNFs 108, and multiple Element Management (EM). 122.
  • Network Service, VNF and Infrastructure Description (Network Service, VNF and Infrastructure Description) 126, and Operation-Support System/Business Support System (OSS/BSS) 124.
  • the NFV management and orchestration system 101 includes an NFV Orchestrator (NFVO) 102, one or more VNFMs 104 and VIMs 106.
  • NFVO NFV Orchestrator
  • NFVI 130 includes computing hardware 112, storage hardware 114, network hardware 116, virtualization layer, virtual computing 110, virtual storage 118, and virtual network 120.
  • Network services, VNF and infrastructure descriptions 126 and OSS/BSS 124 are discussed further in the ETSI GS NFV 002 V1.1.1 standard.
  • the NFV Management and Orchestration System (NFV MANO) 101 is used to perform monitoring and management of the VNF 108 and NFVI 130.
  • the NFVO 102 may implement network services (such as L2 and L3VPN services) on the NFVI 130, may also perform resource related requests from one or more VNFMs 104, send configuration information to the VNFM 104, and collect status information for the VNF 108.
  • NFVO 102 can communicate with VIM 106 to enable resource allocation and/or reservation and to exchange configuration and status information for virtualized hardware resources.
  • the VNFM 104 can manage one or more VNFs 108.
  • the VNFM 104 can perform various management functions such as instantiating, updating, querying, scaling, and/or terminating the VNF 108 and the like.
  • the VIM 106 can perform resource management functions such as managing the allocation of infrastructure resources (eg, adding resources to virtual containers) and operational functions (such as collecting NFVI failure information).
  • the VNFM 104 and VIM 106 can communicate with one another for resource allocation and exchange of configuration and status information for virtualized hardware resources.
  • the NFVI 130 includes hardware resources, software resources, or a combination of both to complete the deployment of the virtualized environment.
  • the hardware resources and virtualization layers are used to provide virtualized resources, such as virtual machines and other forms of virtual containers, for VNF 108.
  • Hardware resources include computing hardware 112, storage hardware 114, and network hardware 116.
  • Computing hardware 112 may be off-the-shelf hardware and/or user-customized hardware used to provide processing and computing resources.
  • Storage hardware 114 may be storage capacity provided within the network or storage capacity resident in storage hardware 114 itself (local storage located within the server). In one implementation, the resources of computing hardware 112 and storage hardware 114 may be grouped together.
  • Network hardware 116 can be a switch, a router, and/or any other network device configured to have switching functionality.
  • Network hardware 116 can span multiple domains and can include multiple networks interconnected by one or more transport networks.
  • the virtualization layer within NFVI 130 can abstract hardware resources from the physical layer and decouple VNF 108 to provide virtualized resources to VNF 108.
  • the virtual resource layer includes virtual computing 110, virtual memory 118, and virtual network 120.
  • Virtual computing 110 and virtual storage 118 may be provided to VNF 108 in the form of virtual machines, and/or other virtual containers.
  • one or more VNFs 108 can be deployed on a single VM.
  • the virtualization layer abstracts network hardware 116 to form a virtual network 120, which may include a virtual switch that is used to provide connectivity between virtual machines and other virtual machines.
  • the transport network in network hardware 116 can be virtualized using a centralized control plane and a separate forwarding plane (eg, software defined network, SDN).
  • VNFM 104 can interact with VNF 108 and EM 122 to manage the lifecycle of the VNF and exchange configuration and status information.
  • the VNF 108 can be configured to virtualize at least one network function performed by one physical network device.
  • the VNF 108 can be configured to provide functionality provided by different network elements in the IMS network, such as P-SCSCF, S-CSCF or HSS network functions, and the like.
  • the EM 122 is configured to manage one or more VNFs 108.
  • FIG. 2 and FIG. 3 are implementation environments of a virtual resource configuration method according to an embodiment of the present application.
  • 2 and 3 are specific applications for applying the NFV network shown in FIG. 1 to DC, as shown in FIG. 2 and FIG. 3, including production DC1, production DC2, and production DC3, in each production DC.
  • the corresponding VNF is deployed on the VM and the corresponding VM is created in the VNF.
  • the disaster-tolerant DC is used to provide disaster recovery and backup for the above three production DCs.
  • Three VNFs are deployed on the disaster-tolerant DC, corresponding to the production of DC1, production of DC2, and production of VNF on DC3.
  • Figure 2 shows the situation in which the production DC is in a normal state.
  • the production DC1, the production DC2, and the VNF on the production DC3 are all in the active state, and the reserved resources of the corresponding VM are 100%.
  • the VNF on the DR is in standby state, and the reserved resources of the corresponding VM are 30%.
  • the VNF on the disaster-tolerant DC is also in the running state, maintaining and surrounding The connection of the network element.
  • FIG 3 shows the situation when the production of DC1 fails.
  • the VNF1A on the DC1 is also faulty.
  • the standby VNF1B corresponding to VNF1A is switched and service taken over.
  • the state of the VNF1B is switched from the standby state to the active state, and the VNFM is notified.
  • the VNFM sends a request to the VIM according to the new resource allocation ratio, and the reserved resource of the VNF1B is modified to 100%. Since VNF1B is always in the running state and has been connected to the surrounding NEs, it can quickly take over the service and ensure that the session and data are not lost.
  • the resource requirement of the disaster tolerant DC can be greatly reduced.
  • FIG. 4 is a flowchart of a first embodiment of a virtual resource configuration method according to an embodiment of the present application. The method is applied to an NFV network, the method comprising steps S101-S103.
  • step S101 the VNFM reads the resource configuration information of the virtual machine VM of the VNF in the description file.
  • the resource configuration information of the VM about the VNF in the description file is first read.
  • the resource allocation information indicates the proportion of the reserved resources of the VNF in different states, including: the ratio of the first reserved resources in the active state and the proportion of the second reserved resources in the standby state.
  • the ratio of the second reserved resource is smaller than the ratio of the first reserved resource, so that the proportion of the reserved resource used by the VNF in the standby state can be reduced, and the resource requirement of the disaster tolerant DC is reduced.
  • the ratio of the first reserved resource in the primary state may be 100%
  • the proportion of the second reserved resource in the standby state may be 30%. It can be understood that the ratio of the reserved resources can also be set to other values, which is not limited by the embodiment of the present invention.
  • the description file may have various implementation manners, which are described in detail below.
  • the description file is a VNFD, and there is a corresponding description field in the VDF in the VNFD for describing a resource allocation situation of the VM.
  • the description field “cpu_core_oversubscription_policy” is used to describe a resource allocation policy of a central processing unit (CPU)
  • the description field “Memory_oversubscription_policy” is used to describe a resource allocation policy of a memory resource.
  • VNFs can be matched to different states by setting resource allocation policies in different states.
  • the VNFM reads the resource configuration information of the VNF of the VNF in the VNFD.
  • the description file is a VNFD.
  • a deployment Flavour element is used in the VNFD to describe a deployment requirement of the VNF in different capacities or different scenarios. Therefore, the deployment preference element includes a The resource configuration information of the VNF.
  • different resource configurations are implemented by deploying preference elements to implement different resource configurations.
  • the VNFM reads the deployment preference element of the VDU in the VNFD to obtain resource configuration information.
  • the description file is an NSD
  • the NSD is used to describe a network service.
  • the Service Deployment Flavour element is used in the NSD to describe the deployment preferences and requirements of the VNF.
  • the basic elements of business deployment preferences are shown in the following table:
  • constituent_vnf is used to describe VNF deployment preferences and requirements. Further, the basic elements of constraint_vnf are shown in the following table:
  • VNF_reference Reference 1 Associated VNFD logo
  • Vnf_flavour_id_ Reference 1 VNF deployment preferences Redundancy_model parameter 0...1 Redundant mode Anance parameter 0...1 Affinity requirements for VNF instance deployment Capability parameter 0...1 VNF instance capacity Number_of_instances parameter 1 Number of VNF instances
  • a plurality of constraint_models can be defined by defining a plurality of constraints_vnf, wherein the redundancy mode corresponding to the redundancy_model can be a primary state or a standby state, so that the resource allocation policy of the VNF in different states can be described.
  • the VNFM reads a service deployment preference element in the NSD, where the service deployment preference element includes resource configuration information of the VNF.
  • step S102 when deploying the first VNF in the active state, the VNFM sends a virtual resource request to the virtual infrastructure manager VIM according to the first reserved resource ratio indicated by the resource configuration information, and according to the VIM The VM of the first VNF is created in response to the resource allocated by the virtual resource request.
  • the VNFM when the first VNF is deployed, the VNFM generates a virtual resource request according to the ratio of the first reserved resource corresponding to the active state in the resource configuration information, and the VNFM generates the virtual resource request according to the ratio of the first reserved resource corresponding to the active state in the resource configuration information.
  • a virtual resource request is sent to VIM.
  • the VIM responds to the virtual resource request and allocates resources according to the first reserved resource ratio.
  • the VNFM then creates a VM of the first VNF based on the resources allocated by the VIM.
  • step S103 when deploying the second VNF in the standby state, the VNFM sends a virtual resource request to the VIM according to the second reserved resource ratio indicated by the resource configuration information, and responds to the virtual resource request according to the VIM.
  • the allocated resource creates a VM of the second VNF.
  • the VNFM when the second VNF is deployed, the VNFM generates a virtual resource request according to the ratio of the second reserved resource corresponding to the standby state in the resource configuration information, and the virtual resource is configured. Request to send to VIM. The VIM responds to the virtual resource request and allocates resources according to the second reserved resource ratio. The VNFM then creates a VM of the second VNF based on the resources allocated by the VIM.
  • the first VNF can be located on the production DC
  • the second VNF can be located on the disaster tolerant DC
  • the second VNF can be used to provide disaster tolerance and backup for the first VNF, and the second VNF can also be used. It is running and remains connected to the surrounding network elements. By setting a lower second reserved resource ratio, the second VNF can be made to occupy less actual resources, thereby reducing DC resource requirements.
  • the present application requests different resource allocation ratios for VNFs of different states, so that the VNF of the active state and the VNF of the standby state allocate different resources. Since the standby VNF is also in the running state, it can be maintained when the primary VNF fails. The dynamic session and the dynamic data are backed up, and the connection relationship with the neighboring NEs is maintained. The service is quickly taken over, and the actual resources occupied by the standby VNF are also reduced, and the resource requirements of the disaster tolerant DC are reduced.
  • FIG. 5 is a flowchart of a second embodiment of a virtual resource configuration method according to an embodiment of the present application.
  • the method is applied to the NFV network.
  • the method further includes the step of performing the switching and the service takeover of the second VNF when the first VNF is faulty, and the method includes the steps S201-S205.
  • step S201 the VNFM reads the resource configuration information of the virtual machine VM of the VNF in the description file.
  • step S202 when deploying the first VNF in the active state, the VNFM sends a virtual resource request to the virtual infrastructure manager VIM according to the first reserved resource ratio indicated by the resource configuration information, and according to the VIM The VM of the first VNF is created in response to the resource allocated by the virtual resource request.
  • step S203 when deploying the second VNF in the standby state, the VNFM sends a virtual resource request to the VIM according to the second reserved resource ratio indicated by the resource configuration information, and responds to the virtual resource request according to the VIM.
  • the allocated resource creates a VM of the second VNF.
  • the VNFM receives the first state notification information sent by the second VNF, where the first state notification information is used to indicate that the second VNF is switched by the standby state. Main state.
  • the second VNF needs to take over the service on the first VNF, and the second VNF will be in its own state.
  • the standby state is switched to the active state, and the first state notification message is used to notify the VNFM, and the first state notification information is used to indicate that the second VNF is switched from the standby state to the active state.
  • the VNFM receives the first status notification message.
  • step S205 the VNFM sends a virtual resource change request to the VIM according to the first reserved resource ratio, so that the VIM allocates resources to the second VNF according to the first reserved resource ratio.
  • the VNFM sends a virtual resource change request to the VIM according to the proportion of the first reserved resource corresponding to the active state, and the VIM allocates resources according to the first reserved resource ratio to the second VNF. .
  • the ratio of the second reserved resource is 30%
  • the ratio of the first reserved resource is 100%.
  • the corresponding resource ratio is also adjusted to the first reserved resource.
  • the ratio is adjusted to 100%.
  • the VM on the second VNF may directly take effect, or may be effective after being restarted.
  • the resources of the second VNF are increased, and when the resources on the existing physical hardware are insufficient, part of the VMs on the second VNF may be migrated to other physical hardware through hot migration or cold migration. The example is not limited to this.
  • the present application requests different resource allocation ratios for VNFs of different states, so that the VNF of the active state and the VNF of the standby state allocate different resources. Since the standby VNF is also in the running state, it can be maintained when the primary VNF fails. The dynamic session and the dynamic data are backed up, and the connection relationship with the neighboring NEs is maintained. The service is quickly taken over, and the actual resources occupied by the standby VNF are also reduced, and the resource requirements of the disaster tolerant DC are reduced. In particular, when the VNF of the primary state is faulty, the resource allocation ratio of the standby VNF can be dynamically adjusted, thereby facilitating the standby VNF to take over the service and improving the availability of the service provided by the VNF.
  • FIG. 6 is a flowchart of a third embodiment of a virtual resource configuration method according to an embodiment of the present application.
  • the method is applied to the NFV network.
  • the method further includes the step of restoring the second VNF to the standby state when the first VNF recovers from the failure, the method comprising the steps S301-S307.
  • step S301 the VNFM reads the resource configuration information of the virtual machine VM of the VNF in the description file.
  • step S302 when deploying the first VNF in the active state, the VNFM sends a virtual resource request to the virtual infrastructure manager VIM according to the first reserved resource ratio indicated by the resource configuration information, and according to the VIM The VM of the first VNF is created in response to the resource allocated by the virtual resource request.
  • step S303 when deploying the second VNF in the standby state, the VNFM sends a virtual resource request to the VIM according to the second reserved resource ratio indicated by the resource configuration information, and responds to the virtual resource request according to the VIM.
  • the allocated resource creates a VM of the second VNF.
  • step S304 when the first VNF is faulty, the VNFM receives the first state notification information sent by the second VNF, where the first state notification information is used to indicate that the second VNF is switched by the standby state. Main state.
  • step S305 the VNFM sends a virtual resource change request to the VIM according to the first reserved resource ratio, so that the VIM allocates resources to the second VNF according to the first reserved resource ratio.
  • step S306 when the first VNF recovers from the failure, the VNFM receives the second state notification information sent by the second VNF, where the second state notification information is used to indicate that the second VNF is The active state is switched to the standby state.
  • the second VNF when the first VNF recovers from the fault, the second VNF is switched from the active state to the standby state, and the second VNF sends the second state notification information to the VNFM, where the second state notification information is used.
  • the second VNF is instructed to switch from the primary state to the standby state.
  • the VNFM receives the second status notification information.
  • step S307 the VNFM sends a virtual resource change request to the VIM according to the second reserved resource ratio, so that the VIM allocates resources to the second VNF according to the second reserved resource ratio.
  • the VNFM sends a virtual resource change request to the VIM according to the second status notification information, and the VIM responds to the request, and recovers some resources on the second VNF according to the second reserved resource ratio.
  • the present application requests different resource allocation ratios for VNFs of different states, so that the VNF of the active state and the VNF of the standby state allocate different resources. Since the standby VNF is also in the running state, it can be maintained when the primary VNF fails. The dynamic session and the dynamic data are backed up, and the connection relationship with the neighboring NEs is maintained. The service is quickly taken over, and the actual resources occupied by the standby VNF are also reduced, and the resource requirements of the disaster tolerant DC are reduced.
  • the resource allocation ratio of the standby VNF can be dynamically adjusted, and when the VNF of the active state recovers from the failure, the resource allocation ratio of the standby VNF is further adjusted, thereby facilitating recovery of the standby VNF. Resources.
  • FIG. 7 is a schematic structural diagram of a first embodiment of a virtual resource configuration apparatus according to an embodiment of the present application.
  • the virtual resource configuration device is applied to the NFV network.
  • the virtual resource configuration device includes a virtual network function manager VNFM 701, a virtual network function VNF 702, and a virtual infrastructure manager VIM 703.
  • the VNFM is configured to read resource configuration information of a virtual machine VM of the VNF in the description file.
  • the VNFM is further configured to: when the first VNF in the active state is deployed, send a virtual resource request to the VIM according to the first reserved resource proportion indicated by the resource configuration information, and request the virtual resource request according to the VIM response.
  • the resource of the first VNF is created; when the second VNF of the standby state is deployed, the virtual resource request is sent to the VIM according to the second reserved resource ratio indicated by the resource configuration information, and according to the VIM response,
  • the virtual resource requests the allocated resources to create the VM of the second VNF.
  • the description file is a virtual network function descriptor VNFD
  • the VNFM reads resource configuration information of a virtual deployment unit VDU of the VNF in the VNFD
  • the VNFM reads the VDU in the VNFD.
  • a preference element is deployed, the deployment preference element including resource configuration information of the VNF.
  • the description file is a network service descriptor NSD
  • the VNFM reads a service deployment preference element in the NSD, where the service deployment preference element includes resource configuration information of the VNF.
  • the resource configuration information indicates a ratio of reserved resources of the VNF in different states, including: a ratio of a first reserved resource in an active state and a proportion of a second reserved resource in a standby state;
  • the second reserved resource ratio is smaller than the first reserved resource ratio.
  • the VNFM is further configured to: when the first VNF is faulty, receive first state notification information sent by the second VNF, where the first state notification information is used to indicate that the second VNF is used by the backup The state is switched to the active state;
  • the VNFM sends a virtual resource change request to the VIM according to the first reserved resource ratio, so that the VIM allocates resources to the second VNF according to the first reserved resource ratio.
  • the VNFM is further configured to: when the first VNF recovers from a fault, receive second state notification information sent by the second VNF, where the second state notification information is used to indicate the second The VNF is switched from the active state to the standby state;
  • the VNFM sends a virtual resource change request to the VIM according to the second reserved resource ratio, so that the VIM allocates resources to the second VNF according to the second reserved resource ratio.
  • the present application requests different resource allocation ratios for VNFs of different states, so that the VNF of the active state and the VNF of the standby state allocate different resources. Since the standby VNF is also in the running state, it can be maintained when the primary VNF fails. The dynamic session and the dynamic data are backed up, and the connection relationship with the neighboring NEs is maintained. The service is quickly taken over, and the actual resources occupied by the standby VNF are also reduced, and the resource requirements of the disaster tolerant DC are reduced.
  • FIG. 8 is a schematic structural diagram of a first embodiment of a virtual resource configuration apparatus according to an embodiment of the present application.
  • the virtual resource configuration device includes a processor 801 and a memory 802.
  • the processor 801 and the memory 802 can communicate over a bus.
  • the bus may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 8, but it does not mean that there is only one bus or one type of bus.
  • the memory 802 may include a volatile memory such as a random-access memory (RAM); the memory 802 may also include a non-volatile memory such as a flash memory. (flash memory), hard disk drive (HDD) or solid-state drive (SSD); the memory 802 may further include a combination of the above types of memories.
  • RAM random-access memory
  • non-volatile memory such as a flash memory.
  • flash memory flash memory
  • HDD hard disk drive
  • SSD solid-state drive
  • the memory 802 may further include a combination of the above types of memories.
  • the processor 801 can be a CPU, a network processor (NP) or a combination of a CPU and an NP.
  • NP network processor
  • the processor 801 may further include a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • the PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or any combination thereof.
  • the processor 801 can include: VNFM, VIM, and the memory 802 is configured to store a description file and an execution instruction.
  • the processor 801 communicates with the memory 802, and the processor 801 calls an execution instruction in the memory 802 to perform the virtual resource configuration method described in any of the embodiments of FIG. 4-6.
  • the embodiment of the present application further provides a computer storage medium, where the computer storage medium can store a program, and the program includes the steps of the method as shown in FIG. 4-6.
  • the computer program is instructed to execute the associated hardware, and the program can be stored in a computer readable storage medium, which, when executed, can include the flow of an embodiment of the methods described above.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Hardware Redundancy (AREA)

Abstract

L'invention concerne un procédé et un dispositif d'attribution d'une ressource virtuelle, qui comprend les étapes suivantes: un gestionnaire de fonction de réseau virtuel (VNFM) lit des informations d'attribution de ressource par rapport à une fonction de réseau virtuel sur une machine virtuelle (S101); pendant le déploiement d'une première VNF dans un état actif, le VNFM transmet une demande de ressource virtuelle à un gestionnaire d'infrastructure virtualisée (VIM) et selon une première ressource réservée indiquée dans les informations d'attribution de ressource, et crée une VM de la première VNF, conformément à une ressource attribuée en réponse à la demande de ressource virtuelle et par le VIM (S102); et pendant le déploiement d'une seconde VNF dans un état de sauvegarde, le VNFM transmet une demande de ressource virtuelle au VIM et selon une seconde ressource réservée indiquée dans les informations d'attribution de ressource, et crée une VM de la seconde VNF, conformément à une ressource attribuée en réponse à la demande de ressource virtuelle et par le VIM (S103). Le procédé est utilisé pour une prise de service rapide lorsqu'une VNF active fonctionne mal, et pour réduire une ressource réelle utilisée par une VNF de réserve, diminuer un besoin en ressource pour une reprise après sinistre dans un centre de données (DC).
PCT/CN2017/080112 2016-04-21 2017-04-11 Procédé et dispositif d'attribution de ressource virtuelle WO2017181877A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610255205.3A CN105955824B (zh) 2016-04-21 2016-04-21 一种虚拟资源配置方法以及装置
CN201610255205.3 2016-04-21

Publications (1)

Publication Number Publication Date
WO2017181877A1 true WO2017181877A1 (fr) 2017-10-26

Family

ID=56914844

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/080112 WO2017181877A1 (fr) 2016-04-21 2017-04-11 Procédé et dispositif d'attribution de ressource virtuelle

Country Status (2)

Country Link
CN (1) CN105955824B (fr)
WO (1) WO2017181877A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111399970A (zh) * 2019-01-02 2020-07-10 中国移动通信有限公司研究院 一种预留资源管理方法、装置和存储介质
CN112839068A (zh) * 2019-11-22 2021-05-25 厦门网宿有限公司 一种采用nfv部件部署的网络节点的管理方法及装置
CN112889247A (zh) * 2018-10-18 2021-06-01 华为技术有限公司 Vnf服务实例化方法及装置

Families Citing this family (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105955824B (zh) * 2016-04-21 2019-07-19 华为技术有限公司 一种虚拟资源配置方法以及装置
CN108471373B (zh) * 2017-02-23 2020-11-06 华为技术有限公司 一种资源申请、vnf实例创建方法及装置
CN108632067B (zh) 2017-03-21 2020-12-08 华为技术有限公司 容灾部署方法、装置及系统
CN108696373B (zh) * 2017-04-06 2019-09-20 华为技术有限公司 虚拟资源分配方法、nfvo和系统
CN109120555B (zh) * 2017-06-26 2022-10-14 中兴通讯股份有限公司 一种资源分配方法及系统
CN107395710B (zh) * 2017-07-17 2020-09-22 苏州浪潮智能科技有限公司 一种云平台网元的配置和高可用ha实现方法和装置
CN107357663A (zh) * 2017-07-24 2017-11-17 中国联合网络通信集团有限公司 资源共享的方法及资源管理器
CN109587024B (zh) * 2017-09-29 2020-12-22 华为技术有限公司 一种资源处理的方法以及相关装置
CN108011846B (zh) * 2017-11-03 2022-07-26 华为技术有限公司 网络功能虚拟化架构中管理业务的方法及装置
CN110365508B (zh) * 2018-04-10 2022-05-31 中国移动通信有限公司研究院 虚拟网络功能实例化的方法和网络功能虚拟化编排器
CN110545193B (zh) * 2018-05-28 2021-04-09 华为技术有限公司 一种虚拟资源的管理方法、虚拟资源管理设备及服务器
CN108880971B (zh) * 2018-05-30 2021-04-27 新华三技术有限公司 虚拟宽带远程接入服务器vBRAS资源池的扩容方法及装置
CN110673981B (zh) * 2018-07-03 2022-06-17 中国电信股份有限公司 故障恢复方法、装置和系统
CN110795202B (zh) * 2018-08-02 2023-11-17 华为技术有限公司 一种虚拟化集群资源管理系统的资源分配方法以及装置
CN111221619B (zh) * 2018-11-27 2023-09-08 中国移动通信集团江西有限公司 一种业务开通和编排的方法、装置及设备
CN114157573A (zh) 2018-12-26 2022-03-08 华为技术有限公司 部署虚拟化网络功能的方法和装置
CN111399967B (zh) * 2019-01-02 2023-03-31 中国移动通信有限公司研究院 一种基于容器的虚拟资源管理方法、装置及系统
CN111399968B (zh) * 2019-01-02 2023-03-31 中国移动通信有限公司研究院 一种基于容器的虚拟资源管理方法、装置及系统
CN111641515B (zh) * 2019-03-01 2021-11-19 华为技术有限公司 Vnf的生命周期管理方法及装置
CN109842526B (zh) * 2019-03-12 2021-12-07 中国联合网络通信集团有限公司 一种容灾方法和装置
CN111726241B (zh) * 2019-03-22 2023-05-19 中兴通讯股份有限公司 网络资源管理方法、系统、网络设备和可读存储介质
CN110120978B (zh) * 2019-05-17 2021-05-14 电子科技大学 一种弹性用户云计算资源的安全保护方法
CN112217654B (zh) * 2019-07-11 2022-06-07 华为技术有限公司 服务资源许可管理方法和相关设备
CN112256382A (zh) * 2019-07-22 2021-01-22 中兴通讯股份有限公司 一种资源数据的恢复方法、存储介质及电子装置
CN112559113B (zh) * 2019-09-10 2023-11-10 中国移动通信集团浙江有限公司 基于cmdb的nfv配置管理方法、系统、服务器和存储介质
CN112749041B (zh) * 2019-10-29 2023-12-26 中国移动通信集团浙江有限公司 虚拟化网络功能备份策略自决策方法、装置及计算设备
CN110958139B (zh) * 2019-11-20 2022-11-15 中移（杭州）信息技术有限公司 网络控制方法、编排器、控制器及计算机可读存储介质
CN112887118B (zh) * 2019-11-29 2024-05-31 中兴通讯股份有限公司 Vnf信息获取及控制方法、装置、nfvo、vnfm及存储介质
CN113495776A (zh) * 2020-03-18 2021-10-12 华为技术有限公司 Vnf实例化方法及装置
CN114095334A (zh) * 2020-07-30 2022-02-25 华为云计算技术有限公司 一种信息同步的方法及其相关设备
CN114765579A (zh) * 2021-01-11 2022-07-19 中国移动通信有限公司研究院 一种数据传输方法、装置、相关设备和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020013802A1 (en) * 2000-07-26 2002-01-31 Toshiaki Mori Resource allocation method and system for virtual computer system
CN104050045A (zh) * 2014-06-27 2014-09-17 华为技术有限公司 基于磁盘io的虚拟资源分配方法及装置
CN104508634A (zh) * 2012-06-29 2015-04-08 博科通迅系统有限公司 虚拟机的动态资源分配
CN105490908A (zh) * 2014-09-16 2016-04-13 中兴通讯股份有限公司 目标资源占用情况的处理方法及装置
CN105955824A (zh) * 2016-04-21 2016-09-21 华为技术有限公司 一种虚拟资源配置方法以及装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102497288A (zh) * 2011-12-13 2012-06-13 华为技术有限公司 一种双机备份方法和双机系统实现装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020013802A1 (en) * 2000-07-26 2002-01-31 Toshiaki Mori Resource allocation method and system for virtual computer system
CN104508634A (zh) * 2012-06-29 2015-04-08 博科通迅系统有限公司 虚拟机的动态资源分配
CN104050045A (zh) * 2014-06-27 2014-09-17 华为技术有限公司 基于磁盘io的虚拟资源分配方法及装置
CN105490908A (zh) * 2014-09-16 2016-04-13 中兴通讯股份有限公司 目标资源占用情况的处理方法及装置
CN105955824A (zh) * 2016-04-21 2016-09-21 华为技术有限公司 一种虚拟资源配置方法以及装置

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112889247A (zh) * 2018-10-18 2021-06-01 华为技术有限公司 Vnf服务实例化方法及装置
CN111399970A (zh) * 2019-01-02 2020-07-10 中国移动通信有限公司研究院 一种预留资源管理方法、装置和存储介质
CN111399970B (zh) * 2019-01-02 2023-04-07 中国移动通信有限公司研究院 一种预留资源管理方法、装置和存储介质
CN112839068A (zh) * 2019-11-22 2021-05-25 厦门网宿有限公司 一种采用nfv部件部署的网络节点的管理方法及装置
CN112839068B (zh) * 2019-11-22 2023-09-12 厦门网宿有限公司 一种采用nfv部件部署的网络节点的管理方法及装置

Also Published As

Publication number Publication date
CN105955824B (zh) 2019-07-19
CN105955824A (zh) 2016-09-21

Similar Documents

Publication Publication Date Title
WO2017181877A1 (fr) Procédé et dispositif d'attribution de ressource virtuelle
KR102059251B1 (ko) 노드 시스템, 서버 장치, 스케일링 제어 방법 및 프로그램
US11307943B2 (en) Disaster recovery deployment method, apparatus, and system
CN107066319B (zh) 一种面向异构资源的多维调度系统
US20230033296A1 (en) Managing composition service entities with complex networks
CN107924383B (zh) 用于网络功能虚拟化资源管理的系统和方法
WO2017071460A1 (fr) Procédé et appareil de surveillance de conteneur
US8639793B2 (en) Disaster recovery and automatic relocation of cloud services
WO2018006676A1 (fr) Procédé et appareil de traitement de ressources d'accélération et système de virtualisation de fonction de réseau
WO2016165304A1 (fr) Procédé de gestion de nœud d'instance et dispositif de gestion
WO2017114325A1 (fr) Procédé, dispositif et système de traitement de défaillance
CN111641515B (zh) Vnf的生命周期管理方法及装置
WO2017080391A1 (fr) Procédé et dispositif de déploiement de service de réseau
WO2020001409A1 (fr) Procédé et appareil de déploiement de fonctions de réseau virtuel (vnf)
CN109428764B (zh) 虚拟网络功能的实例化方法
CN104158707A (zh) 一种检测并处理集群脑裂的方法和装置
CN111935244B (zh) 一种业务请求处理系统及超融合一体机
WO2021043124A1 (fr) Système d'exploitation distribué kbroker, support de stockage et dispositif électronique
CN111221620B (zh) 存储方法、装置及存储介质
WO2018196651A1 (fr) Procédé et dispositif de gestion de ressources
US10001939B1 (en) Method and apparatus for highly available storage management using storage providers
CN108153484B (zh) 一种虚拟化环境下的共享式存储系统及其管理方法
WO2018099301A1 (fr) Procédé et dispositif d'analyse de données
WO2023155838A1 (fr) Procédé et appareil d'instanciation de fonction de réseau virtuelle (vnf)
Xue et al. On automated cloud bursting and hybrid cloud setups using Apache Mesos

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17785362

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17785362

Country of ref document: EP

Kind code of ref document: A1