WO2020125698A1 - Procédé et appareil de gestion d'objet ressource - Google Patents

Procédé et appareil de gestion d'objet ressource Download PDF

Info

Publication number
WO2020125698A1
WO2020125698A1 PCT/CN2019/126428 CN2019126428W WO2020125698A1 WO 2020125698 A1 WO2020125698 A1 WO 2020125698A1 CN 2019126428 W CN2019126428 W CN 2019126428W WO 2020125698 A1 WO2020125698 A1 WO 2020125698A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
resource object
objects
management device
nfv management
Prior art date
Application number
PCT/CN2019/126428
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 WO2020125698A1 publication Critical patent/WO2020125698A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • 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/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • 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]

Definitions

  • This application relates to the field of communication technologies, and in particular, to a method and device for managing resource objects.
  • Network function virtualization is a software process used by telecommunications network operators to carry many functions through the use of general-purpose hardware such as x86 and virtualization technology, and is implemented in general high-performance servers, switches and storage devices. Network function technology, thereby reducing the cost of expensive network equipment.
  • Various types of existing network equipment such as firewalls, routers, broadband remote access servers (BRAS), carrier-grade network address translation (CG-NAT), etc. Virtualization can be achieved through NFV technology.
  • BRAS broadband remote access servers
  • CG-NAT carrier-grade network address translation
  • VNF manager VNF manager
  • VNFM virtualized Infrastructure Manager
  • VNFM uses a unified deployment algorithm to randomly find a deployment location for each VM, after the VM is created, large resource fragments may appear in the physical machine, resulting in low resource utilization efficiency.
  • the present application provides a resource object management method and device to solve the technical problem of large resource fragmentation and low resource utilization efficiency in the Host.
  • an embodiment of the present application provides a resource object management method, including:
  • the NFV management device determines the demand information of multiple resource objects that need to be created
  • the NFV management device obtains physical resource information from the resource allocation device, and pre-arranges the deployment position of each resource object among the multiple resource objects according to the demand information of the multiple resource objects and the physical resource information, The deployment position of each resource object is used to indicate the physical resource occupied by each resource object;
  • the NFV management device sends a creation request of the plurality of resource objects to a resource allocation device, and the creation request of each resource object includes a deployment location of each resource object.
  • the creation request of each resource object may further include demand information of each resource object.
  • the NFV management device pre-arranges the deployment location of each resource object according to the demand information and physical resource information of multiple resource objects, that is, the NFV management device pre-determines the deployment location of each resource object, and then based on the predetermined deployment Location to create each resource object, so that from a global perspective, multiple resource objects can be centrally arranged and optimized for deployment; compared to the way that resource allocation equipment uses a unified algorithm to randomly find the deployment location for each resource object,
  • the embodiments of the present application can pre-determine the deployment positions of multiple resource objects in an optimized manner before creating multiple resource objects, so as to improve resource utilization efficiency.
  • the deployment location of each resource object includes:
  • the identifier of the central processing unit CPU where each resource object is located the identifier of the Host where the CPU is located; or,
  • the identification of the central processing unit CPU where each resource object is located the identification of the Host where the CPU is located, and the identification of the NUMA node where the CPU is located; or,
  • the identifier of the CPU where each resource object is located the identifier of the Host where the CPU is located, the identifier of the NUMA node where the CPU is located, and the memory allocated to each resource object.
  • the method further includes:
  • the NFV management device sends a resource reservation request to the resource allocation device, where the resource reservation request includes one or more first host identifiers; the resource reservation request is used to request the reservation of the one or more First Hosts; the identification of the one or more first Hosts is obtained according to the deployment location of each resource object in the plurality of resource objects.
  • reserving the one or more first hosts includes:
  • one or more first hosts can be prevented from being occupied by other applications, which may result in multiple resource objects not being able to be deployed according to the pre-arranged deployment location; by closing the one or more first hosts
  • the high-availability HA function corresponding to each first host can effectively prevent resource objects deployed on one or more first hosts from arbitrarily migrating when a failure occurs, resulting in resource fragmentation.
  • the method further includes:
  • the NFV management device determines the deployment position of the first resource object to be reconstructed according to the deployment position of the first resource object;
  • the NFV management device sends a reconstruction request of the first resource object to the resource allocation device, where the reconstruction request includes the deployment location of the first resource object to be reconstructed.
  • the NFV management device may determine the deployment location of the second resource object to be rebuilt according to the deployment location of the first resource object, thereby avoiding resource fragmentation caused by random migration after the resource object fails To improve resource utilization.
  • the first resource object is a business resource object
  • the second resource object is a management resource object used to manage the first resource object among the plurality of resource objects
  • the determining by the NFV management device that the first resource object has failed includes:
  • the NFV management device receives a failure notification sent by a second resource object, where the failure notification is used to indicate that the first resource object has a failure.
  • the NFV management device determines the demand information of multiple resource objects that need to be created, including:
  • the NFV management device receives a VNF instantiation request, and the instantiation request includes the virtual network function description file VNFD of the VNF; the NFV management device determines multiple resource objects that need to be created according to the VNFD of the VNF Demand information; or,
  • the NFV management device receives the expansion request of the VNF, and the expansion request includes expansion strategy information; the NFV management device determines, based on the expansion strategy information and the load information of the VNF, the number of resource objects that need to be created demand information.
  • the method further includes:
  • the NFV management device receives a VNF scaling request, and the scaling request includes scaling policy information
  • the NFV management device determines that the number of resource objects to be downsized is M according to the downsizing policy information and the load information of the VNF;
  • the NFV management device determines M resource objects to be reduced from the plurality of resource objects according to the deployment position of each resource object in the plurality of resource objects;
  • the NFV management device sends a deletion request to the resource allocation device, where the deletion request includes the identifiers of the M resource objects to be reduced.
  • the NFV management device determines M resource objects from the plurality of resource objects according to the deployment location of each of the plurality of resource objects, including:
  • the NFV management device divides the plurality of resource objects into N groups of resource objects according to the number of VMs to be reduced, and each group of resource objects in the N groups of resource objects includes M resource objects;
  • the NFV management device determines the number of hosts where each group of resource objects in the N group of resource objects is located according to the deployment location of each resource object in the plurality of resource objects;
  • the NFV management device determines a set of resource objects with the smallest number of Hosts as the M resource objects to be reduced.
  • the determined resource object to be reduced can be located on the same host as much as possible, thereby reducing resource fragmentation caused by the reduction and effectively improving resource utilization.
  • the method further includes:
  • the NFV management device sends a resource release request to the resource allocation device, the resource release request includes identifiers of one or more second hosts, and the resource release request is used to request the release of the one or more second hosts
  • the identifier of the one or more second hosts is obtained according to the deployment position of each resource object in the M resource objects to be reduced.
  • the NFV management device sends a resource release request to the resource allocation device, thereby facilitating physical resources to be used by other applications.
  • the resource object is a virtual machine VM or a virtual container.
  • an embodiment of the present application provides a resource object management method.
  • the method includes:
  • the resource allocation device receives multiple resource object creation requests sent by the NFV management device, and the creation request of each resource object among the multiple resource objects includes the deployment location of each resource object;
  • the resource allocation device creates each resource object according to the deployment location of each resource object.
  • the deployment location of each resource object includes:
  • the identifier of the central processing unit CPU where each resource object is located the identifier of the Host where the CPU is located; or,
  • the identification of the central processing unit CPU where each resource object is located the identification of the Host where the CPU is located, and the identification of the NUMA node where the CPU is located; or,
  • the identifier of the CPU where each resource object is located the identifier of the Host where the CPU is located, the identifier of the NUMA node where the CPU is located, and the memory allocated to each resource object.
  • the method further includes:
  • the resource allocation device receives a resource reservation request sent by the NFV management device, where the resource reservation request includes one or more first host identifiers; the one or more first host identifiers are based on the Obtained from the deployment location of each resource object in multiple resource objects;
  • the resource allocation device reserves the one or more first hosts.
  • the resource allocation device reserves the one or more first hosts, including:
  • the resource allocation device pre-occupies the one or more first hosts, and/or, the resource allocation device disables the HA function corresponding to the one or more first hosts.
  • the method further includes:
  • the resource allocation device receives a reconstruction request of the first resource object sent by the NFV management device, where the reconstruction request includes the deployment location of the first resource object to be reconstructed;
  • the resource allocation device reconstructs the first resource object according to the deployment position of the first resource object to be reconstructed.
  • the method further includes:
  • the resource allocation device receives a resource release request sent by the NFV management device, and the resource release request includes one or more second host identifiers; the one or more second host identifiers are based on Obtained from the deployment location of each of the M resource objects;
  • the resource allocation device releases the one or more second hosts.
  • the resource object is a VM or a virtual container.
  • an embodiment of the present application provides a resource object management method.
  • the method includes:
  • the NFV management device determines the demand information of multiple resource objects that need to be created
  • the NFV management device sends the demand information of the multiple resource objects to the resource allocation device;
  • the NFV management device receives the deployment position of each resource object in the plurality of resource objects sent by the resource allocation device, and the deployment position of each resource object is used to indicate the physical occupation of each resource object Resources
  • the NFV management device sends a creation request of the plurality of resource objects to a resource allocation device, and the creation request of each resource object includes demand information of each resource object.
  • the resource allocation device pre-arranges the deployment position of each resource object according to the demand information and physical resource information of multiple resource objects, that is, the resource allocation device determines the deployment position of each resource object in advance, and then based on the predetermined deployment position To create each resource object, so as to be able to orchestrate and optimize the deployment of multiple resource objects from a global perspective; compared to the way that resource allocation equipment uses a unified algorithm to randomly find the deployment location for each resource object, this
  • the embodiments of the application can determine the deployment positions of the multiple resource objects in advance through optimization before creating multiple resource objects, so as to improve the efficiency of resource utilization.
  • each resource object creation request includes the deployment location of each resource object.
  • the deployment location of each resource object includes:
  • the identifier of the central processing unit CPU where each resource object is located the identifier of the Host where the CPU is located; or,
  • the identification of the central processing unit CPU where each resource object is located the identification of the Host where the CPU is located, and the identification of the NUMA node where the CPU is located; or,
  • the identifier of the CPU where each resource object is located the identifier of the Host where the CPU is located, the identifier of the NUMA node where the CPU is located, and the memory allocated to each resource object.
  • the method further includes:
  • the NFV management device sends a resource reservation request to the resource allocation device, where the resource reservation request includes one or more first host identifiers; the resource reservation request is used to request the reservation of the one or more First Hosts; the identification of the one or more first Hosts is obtained according to the deployment location of each resource object in the plurality of resource objects.
  • the method further includes:
  • the NFV management device After the NFV management device determines that the first resource object is faulty, delete the first resource object; the NFV management device determines the deployment position of the first resource object to be reconstructed according to the deployment position of the first resource object; The NFV management device sends a reconstruction request of the first resource object to the resource allocation device, where the reconstruction request includes the deployment location of the first resource object to be reconstructed; or,
  • the NFV management device After the NFV management device determines that the first resource object is faulty, delete the first resource object; the NFV management device sends a reconstruction request of the first resource object to the resource allocation object, the reconstruction request includes the first resource object's reconstruction demand information.
  • the method further includes:
  • the NFV management device receives a VNF scaling request, and the scaling request includes scaling policy information
  • the NFV management device determines that the number of resource objects to be downsized is M according to the downsizing policy information and the load information of the VNF;
  • the NFV management device determines M resource objects to be reduced from the plurality of resource objects according to the deployment position of each resource object in the plurality of resource objects;
  • the NFV management device sends a deletion request to the resource allocation device, where the deletion request includes the identifiers of the M resource objects to be reduced.
  • the NFV management device determines M resource objects from the plurality of resource objects according to the deployment location of each of the plurality of resource objects, including:
  • the NFV management device divides the plurality of resource objects into N groups of resource objects according to the number of VMs to be reduced, and each group of resource objects in the N groups of resource objects includes M resource objects;
  • the NFV management device determines the number of hosts where each group of resource objects in the N group of resource objects is located according to the deployment location of each resource object in the plurality of resource objects;
  • the NFV management device determines a set of resource objects with the smallest number of Hosts as the M resource objects to be reduced.
  • the method further includes:
  • the NFV management device sends a resource release request to the resource allocation device, the resource release request includes identifiers of one or more second hosts, and the resource release request is used to request the release of the one or more second hosts
  • the identifier of the one or more second hosts is obtained according to the deployment position of each resource object in the M resource objects to be reduced.
  • an embodiment of the present application provides a resource object management method.
  • the method includes:
  • the resource allocation device receives the demand information of multiple resource objects sent by the NFV management device;
  • the resource allocation device obtains physical resource information, and pre-arranges the deployment position of each resource object among the multiple resource objects according to the demand information of the multiple resource objects and the physical resource information, and each The deployment position of the resource object is used to indicate the physical resource occupied by each resource object;
  • the resource allocation device sends the deployment location of each resource object in the plurality of resource objects to the NFV management device;
  • the resource allocation device receives the creation request of the multiple resource objects sent by the NFV management device, and creates each resource object according to the deployment location of each resource object in the multiple resource objects.
  • the method further includes:
  • the resource allocation device obtains the identifier of one or more first hosts according to the deployment location of each resource object among the plurality of resource objects, and reserves one or more first hosts.
  • the method further includes:
  • the resource allocation device receives a resource reservation request sent by an NFV management device, where the resource reservation request includes one or more first host identifiers; the one or more first host identifiers are based on the multiple Obtained from the deployment location of each resource object in the resource object;
  • the resource allocation device reserves the one or more first hosts.
  • the method further includes:
  • the resource allocation device receives the reconstruction request of the first resource object sent by the NFV management device, where the reconstruction request includes the deployment position of the first resource object to be reconstructed; the resource allocation device according to the deployment position of the first resource object to be reconstructed, Rebuild the first resource object; or,
  • the resource allocation device receives a reconstruction request of the first resource object sent by the NFV management device, the reconstruction request includes demand information of the first resource object, and the resource allocation device determines the first resource to be reconstructed according to the deployment position of the first resource object The deployment position of the object, and the first resource object is reconstructed based on the determined deployment position and the demand information of the first resource object.
  • the method further includes:
  • the resource allocation device receives a resource release request sent by the NFV management device, and the resource release request includes one or more second host identifiers; the one or more second host identifiers are based on Obtained from the deployment location of each of the M resource objects;
  • the resource allocation device releases the one or more second hosts.
  • an embodiment of the present application provides an apparatus.
  • the apparatus may be an NFV management device or a resource allocation device, or may be a semiconductor chip provided in the NFV management device or a resource allocation device.
  • the device has functions to realize various possible implementation manners of the first aspect to the fourth aspect described above. This function can be realized by hardware, and can also be realized by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • an embodiment of the present application provides an apparatus, including: a processor and a memory; the memory is used to store computer-executed instructions, and when the apparatus is running, the processor executes the computer-executed instructions stored in the memory, so that The device performs the method as described in the first aspect or any one of the first aspect above, or causes the device to perform the method as described in the second aspect or any one of the second aspect above, or causes the device to perform as The above-mentioned third aspect or the method according to any one of the third aspects, or the apparatus to perform the method according to the above-mentioned fourth aspect or any one of the fourth aspects.
  • an embodiment of the present application further provides a computer-readable storage medium, in which instructions are stored in the computer-readable storage medium, which when executed on a computer, causes the computer to execute the method described in the above aspects.
  • an embodiment of the present application further provides a computer program product including instructions, which when run on a computer, causes the computer to execute the method described in the above aspects.
  • FIG. 1 is a schematic diagram of an NFV architecture provided by an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a NUMA topology provided by an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of a resource object management method provided in Embodiment 1 of the present application.
  • FIG. 4 is a schematic flowchart of a resource object management method provided in Embodiment 2 of the present application.
  • FIG. 5 is a schematic flowchart of a resource object management method provided in Embodiment 3 of the present application.
  • FIG. 6 is a schematic flowchart of a resource object management method according to Embodiment 4 of the present application.
  • FIG. 7 is a schematic flowchart of a resource object management method provided in Embodiment 5 of the present application.
  • FIG. 8 is a schematic flowchart of a resource object management method provided in Embodiment 6 of the present application.
  • FIG. 9 is a schematic flowchart of a resource object management method provided in Embodiment 7 of the present application.
  • FIG. 10 is a possible exemplary block diagram of a device involved in an embodiment of this application.
  • FIG. 11 is a schematic structural diagram of an apparatus provided by an embodiment of the present application.
  • an embodiment of the present invention provides a schematic diagram of an NFV architecture.
  • the NFV architecture can implement multiple networks, such as a local area network (LAN), an Internet protocol (IP) network, or an evolved packet core (EPC) network.
  • the NFV architecture may include an NFV management and orchestration system (NFV-MANO) 110, an NFV infrastructure (NFV) 150, multiple VNFs 140, and multiple network element management systems (element management system, EMS) 130, and one or more operation support system/business support system (operation support system/business support system (OSS/BSS) 120).
  • NFV-MANO NFV management and orchestration system
  • NFV NFV infrastructure
  • EMS network element management systems
  • OSS/BSS operation support system/business support system
  • NFV-MANO 110 may include NFV orchestrator (NFVO) 111, one or more VNFM112, and one or more VIM113;
  • NFVI 150 may include a hardware resource layer consisting of computing hardware 1521, storage hardware 1522, and network hardware 1523 , A virtualization layer, and a virtual resource layer composed of virtual computing 1511 (for example, a virtual machine), virtual storage 1512, and virtual network 1513.
  • the computing hardware 1521 in the hardware resource layer may be a dedicated processor or a general-purpose processor that provides processing and computing functions, such as a central processing unit (CPU); storage hardware 1522 is used to provide storage capabilities, such as , Disk or network attached storage (network attached storage, NAS); network hardware 1523 may be a switch, router, and/or other network equipment.
  • CPU central processing unit
  • storage hardware 1522 is used to provide storage capabilities, such as , Disk or network attached storage (network attached storage, NAS)
  • network hardware 1523 may be a switch, router, and/or other network equipment.
  • the virtualization layer in NFVI 150 is used to abstract the hardware resources of the hardware resource layer, decouple VNF 140 from the physical layer to which the hardware resources belong, and provide virtual resources to VNF.
  • the virtual resource layer may include virtual computing 1511, virtual storage 1512, and virtual network 1513.
  • the virtual computing 1511 and the virtual storage 1512 may be provided to the VNF 140 in the form of virtual machines or other virtual containers.
  • one or more virtual machines form a VNF 140.
  • the virtualization layer forms a virtual network 1513 by abstracting the network hardware 1523.
  • the virtual network 1513 is used to implement communication between multiple virtual machines or between multiple other types of virtual containers carrying VNFs.
  • VLAN virtual local area network
  • VPLS virtual private LAN service
  • VxLAN virtual extensible local area network
  • NVGRE general routing encapsulated network
  • OSS/BSS 120 is mainly for telecom service operators, providing comprehensive network management and business operation functions, including network management (such as fault monitoring, network information collection, etc.), billing management, and customer service management.
  • network management such as fault monitoring, network information collection, etc.
  • billing management billing management
  • customer service management customer service management
  • NFV-MANO 110 can be used to monitor and manage VNF 140 and NFVI 150.
  • NFVO 111 can communicate with one or more VNFM 112 to fulfill resource-related requests, send configuration information to VNFM 112, and collect VNF 140 status information.
  • NFVO 111 can also communicate with VIM 113 to achieve resource allocation, and/or to realize the reservation and exchange of configuration information and status information of virtualized hardware resources.
  • VNFM 112 can be used to manage one or more VNFs 140, perform various management functions, such as initializing, updating, querying, and/or terminating VNF 140.
  • VIM 113 can be used to control and manage the interaction between VNF 140 and computing hardware 1521, storage hardware 1522, network hardware 1523, virtual computing 1511, virtual storage 1512, and virtual network 1513.
  • VIM 113 can be used to perform resource allocation operations to VNF 140.
  • VNFM 112 and VIM 113 can communicate with each other to exchange virtualized hardware resource configuration and status information.
  • NFVI 150 includes hardware and software, which together establish a virtualized environment to deploy, manage, and execute VNF 140. That is to say, the hardware resource layer and the virtual resource layer are used to provide VNF 140 with virtual resources, such as virtual machines and/or other forms of virtual containers.
  • VNFM 112 can communicate with VNF 140 and EMS 130 to perform VNF lifecycle management and exchange configuration/status information.
  • VNF 140 is the virtualization of at least one network function, which was previously provided by a physical network device.
  • VNF 140 may be a virtualized mobility management entity (MME) node, which is used to provide all network functions provided by a typical non-virtualized MME device.
  • MME virtualized mobility management entity
  • VNF 140 may be used to implement the functions of some components among all components provided on the non-virtualized MME device.
  • a VNF 140 may be composed of one or more virtual network function components (VNF) (VNFC), and the VNFC may be a virtual machine or other forms of virtual containers.
  • EMS 130 can be used to manage one or more VNF 140.
  • VNFM 112 is used to perform various management functions on VNF 140, such as initialization, update, query, and termination of VNF 140, while VIM 113 is used to control and Management VNF 140 interacts with other parts. Therefore, if a VNF 140 is implemented, VNFM 112 and VIM 113 must work together. Therefore, VNFM 112 and VIM 113 can communicate with each other to exchange virtualized hardware resource configuration and status information. Among them, VNFM 112 and VIM 113 establish a communication connection through an interface.
  • VIM the deployment position of the VM is determined by VIM, and VIM is usually Determine the deployment location of the VM based on a unified deployment algorithm. Since this deployment algorithm cannot consider the VMs to be created in the future, it can only plan the deployment position of VMs one by one according to the current status, so that resource fragments may appear in the Host, which makes the resource utilization efficiency low .
  • the embodiments of the present application provide a resource object management method for solving the technology that after a unified deployment algorithm is used to determine the deployment location of a VM and create a VM, resource fragmentation may occur in the Host and resource utilization efficiency is low problem.
  • Host It can also be called a physical machine. It is a physical device that can carry resource objects, such as a computer, a server, and other physical devices.
  • Non-uniform memory access architecture divides the processor and memory into different nodes (nodes), within the node will access the internal local memory through its own storage bus, and all nodes Both can access the remote memory of other nodes through the shared bus on the motherboard.
  • Figure 2 is a schematic diagram of the NUMA topology. As shown in Figure 2, it includes four nodes, namely node 1, node 2, node 3 and node 4, each node including two CPUs and a memory.
  • Pod It can be understood as the smallest unit of management or creation.
  • a Pod can be a logical host in a container environment. It may contain one or more closely connected applications. These applications may be on the same physical machine or virtual machine.
  • the NFV management device may receive a VNF instantiation request during VNF instantiation and generate a creation request for each resource object in at least one resource object of the VNF device of.
  • the NFV control device may be NFVO 111 and/or VNFM 112 in the NFV architecture shown in FIG. 1.
  • the resource allocation device may be a device that receives a creation request of a resource object and creates a resource object based on the creation request.
  • the resource allocation device may be VIM 113 in the NFV architecture shown in FIG. 1.
  • Resource object may be a VM or a virtualized container (virtualized container). Understandably, the resource object may also be another possible virtual unit, such as a Pod, which is not specifically limited in this embodiment of the present application.
  • High availability (HA) function an automatic failover mechanism.
  • multiple hosts can be used as a failover cluster.
  • the resources located on the host Objects such as VM
  • VM can be automatically migrated to another available Host in the cluster and restarted.
  • At least one (a, b) of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be a single or can be Multiple.
  • FIG. 3 is a schematic flowchart of a resource object management method provided in Embodiment 1 of the present application. As shown in FIG. 3, the method includes:
  • Step 301 the NFV management device determines the demand information of multiple resource objects that need to be created.
  • the NFV management device may determine that the demand information of multiple resource objects that need to be created can be implemented in multiple ways. Multiple resource objects that need to be created can belong to the same VNF or can belong to different VNFs.
  • the NFV management device may determine the demand information of multiple resource objects that need to be created according to the VNFD of the VNF included in the instantiation request. For example, after receiving the instantiation request of VNF1, the NFV management device determines the demand information of the resource objects (including resource object a0 to resource object a9) that need to be created according to the VNFD of VNF1. At this time, multiple resources (that is, resource object a0 To resource object a9) belongs to the same VNF, namely VNF1.
  • the NFV management device determines the requirement information of the resource objects (including resource object b0 to resource object b9) that need to be created according to VNFD of VNF2, and determines the need to create according to VNFD of VNF3 Resource object (including resource object c0 to resource object c9) demand information, at this time, multiple resources (ie, resource object b0 to resource object b9, resource object c0 to resource object c9) belong to different VNF, where resource object b0 The resource object b9 belongs to VNF2, and the resource object c0 to resource object c9 belongs to VNF3.
  • the VNFD of the VNF may include deployment_flavour, information of multiple VDUs, virtual_link, connection_point, dependency, and affinity/anti-affinity.
  • deployment_flavour specifies the deployment method of the VNF.
  • the deployment method is divided into three types: large, medium, and small:
  • the NFV management device needs to deploy higher specifications Resource objects (such as virtual machines with large hard disks and large memory), or resource objects with a large number of deployments; in the medium deployment method, use resource objects with moderate specifications or resource objects with a moderate number of deployments; use small deployments
  • a resource object with a lower specification or a resource object with a smaller number of deployments is used.
  • the information of a VDU specifies the specifications of a resource object.
  • the specifications of a resource object may include at least one of the number of CPUs, CPU performance, memory size, bandwidth, and storage size of the resource object (such as a virtual machine).
  • virtual_link specifies the virtual links between the different resource objects that make up the VNF and the attributes of the external virtual links of the VNF, including the link type (such as tree type), the link bandwidth, and so on.
  • connection_point specifies the internal port of the VNF and the external connection port. In different application environments, the port type is different.
  • it can be a layer 2 port (using media access control (MAC) address for interaction) or it can be Layer 3 ports (interaction using internet protocol (IP) addresses), these ports are associated with virtual_link and fully describe the network connection of the VNF; dependency specifies the dependency relationship between resource objects and is used to indicate deployment The instantiation order of different resource objects in the process, that is, the dependent resource objects need to be instantiated first, and the other resource objects can only be instantiated after the dependent resource objects are started.
  • Affinity/anti-affinity indicates the affinity attribute of the resource object, where affinity indicates that the indicated resource object needs to be deployed on the same Host, while anti-affinity indicates that the indicated resource object cannot be deployed on the same Host.
  • the demand information of a resource object can include the specifications of the resource object, so the NFV management device can be based on the information of multiple VDUs; for example, the demand information of the resource object can include the specifications and affinity attributes of the resource object, so, the NFV management device According to the information of multiple VDUs and affinity/anti-affinity, the demand information of multiple resource objects can be obtained. Understandably, the demand information of the resource object may also include other possible information, which is not specifically limited.
  • the VNFD of the VNF may also include redundancy specifications, and the NFV management device may also obtain the redundancy specifications from the VNFD.
  • multiple resource objects may have different specifications.
  • the redundancy specification of the resource object may be 5:1. If VNF needs to create a resource object of that specification If the number is 10, in step 303, the NFV management device may pre-arrange 12 deployment positions of resource objects of this type, and the deployment positions of 2 resource objects are redundant positions of resource objects of this type.
  • the NFV management device may determine the demand information of the multiple resource objects that need to be created according to the expansion strategy information included in the expansion request and the VNF load information.
  • the NFV management device may determine the demand information of multiple resource objects that need to be created after receiving one or more VNF expansion requests.
  • the expansion strategy information can be set by the operator, and the specific implementation of determining the demand information of the multiple resource objects that need to be created according to the expansion strategy information and the VNF load information can refer to the existing technology and will not be repeated here.
  • multiple resource objects that need to be created may include management resource objects and business resource objects, or may include only business resource objects; one of them is a management resource Objects can be used to manage one or more business resource objects.
  • management resource objects can be used to manage one or more business resource objects.
  • Step 302 the NFV management device obtains physical resource information from the resource allocation device.
  • the NFV management device may send a request message for acquiring physical resource information to the resource allocation device through a preset interface; accordingly, the resource allocation device may feed back a response message to the NFV management device, and the response message includes physical resource information.
  • the physical resource information may include the identifier of the Host (such as ID), the identifier of the NUMA node, the CPU on the NUMA node, the memory corresponding to the NUMA node, the free CPU in the NUMA node, and the free memory corresponding to the NUMA node. As shown in Table 1, it is an example of physical resource information.
  • Table 1 Examples of physical resource information
  • Step 303 The NFV management device pre-arranges the deployment position of each resource object among the multiple resource objects according to the demand information and physical resource information of multiple resource objects.
  • the deployment position of each resource object is used to indicate the location of each resource object. Physical resources occupied.
  • the NFV management device pre-arranges to obtain the deployment position of each resource object in multiple resource objects, and there may be multiple specific implementation methods.
  • the NFV management device may be based on the demand information and physical resource information of multiple resource objects. Through multiple rounds of iterative optimization algorithms, the deployment location of each resource object in multiple resource objects is obtained.
  • the NFV management device before creating multiple objects, comprehensively considers the demand information and physical resource information of each resource object to pre-arrange the deployment position of each resource object to avoid
  • the resource allocation equipment uses a unified deployment algorithm to randomly find the deployment location for each resource object, which leads to the problem of resource fragmentation.
  • the specific pre-arrangement method may not be limited.
  • the deployment location of each resource object includes any one of the following: (1) the identifier of the Host where each resource object is located; (2) the identifier of the CPU where each resource object is located, and the Host where the CPU is located (3) The ID of the CPU where each resource object is located, the ID of the Host where the CPU is located, the ID of the NUMA node where the CPU is located; (4) The ID of the CPU where each resource object is located, the The identifier of the Host where the CPU is located, the identifier of the NUMA node where the CPU is located, and the memory allocated to each resource object, wherein the memory allocated to each resource object refers to the memory allocated to the NUMA node Memory for each resource object.
  • the deployment location of the resource object 1 may further include other information, which is not specifically limited.
  • the NFV management device After the NFV management device pre-arranges the deployment location of each resource object, it can store the topology relationship table of multiple resource objects. As shown in Table 2, it is an example of the representation of the topological relationship of multiple resource objects.
  • Table 2 Examples of the representation of the topological relationship of multiple resource objects
  • the content indicated in the last four columns of Table 2 is the deployment location of the resource object.
  • the NFV management device may update Table 2 under the trigger of preset conditions, where the preset conditions may change the deployment location of a certain resource object, or delete one or more resource objects, or add one or more Resource objects, etc., no specific restrictions.
  • the NFV management device may also send a resource reservation request to the resource allocation device.
  • the resource reservation request may include one or more identifiers of the first host. Further, it may further include a reservation indication and a reservation indication. It can be a pre-occupancy indication and/or an indication to turn off the HA function.
  • the identifiers of the one or more first hosts are obtained according to the deployment location of each resource object in the plurality of resource objects. In one example, the identifiers of the one or more first hosts are where the plurality of resource objects are located. Host logo. For example, multiple resource objects are resource object 1 to resource object 10 respectively.
  • the host where resource object 1 and resource object 2 are located is Host1, resource object 3 and resource object
  • the host where 4 is located is Host2
  • the host where resource object 5 and resource object 6 are located is Host3
  • the host where resource object 7 and resource object 8 are located is Host4
  • the host where resource object 9 is located is Host5
  • Host6 is Host6 ;
  • one or more first Hosts can be obtained including Host1, Host2, Host3, Host4, Host5 and Host6.
  • the one or more first hosts may be understood as a resource pool (or may also be referred to as a host group).
  • the resource reservation request may further include the identifier of the resource pool.
  • the resource allocation object may reserve one or more first hosts according to the identifiers of the one or more first hosts included in the resource reservation request.
  • reserving one or more first hosts may include pre-occupying one or more first hosts, so that one or more first hosts may be prevented from being occupied by other applications; in yet another example, the reservation The one or more first hosts may include turning off the highly available HA function corresponding to the one or more first hosts. In this way, resource objects deployed on the one or more first hosts may be effectively prevented from arbitrarily migrating when a failure occurs.
  • reserving one or more first hosts may include pre-occupying one or more first hosts and turning off the highly available HA function corresponding to the one or more first hosts.
  • Step 304 The NFV management device sends the resource allocation device a creation request of the plurality of resource objects, where the creation request of each resource object includes the deployment location of each resource object.
  • the resource allocation device receives the creation request of each resource object, and creates each resource object according to the deployment location of each resource object.
  • the creation request of the resource object 1 may include the identifier of the Host where the resource object 1 is located (such as Host1), and further, may also include the demand information of the resource object 1.
  • the resource allocation device can create the resource object 1 on the Host1 according to the demand information of the resource object 1.
  • the NFV management device pre-arranges the deployment position of each resource object according to the demand information and physical resource information of multiple resource objects, that is, the NFV management device determines the deployment position of each resource object in advance, and then based on the predetermined deployment Location to create each resource object, so that from a global perspective, multiple resource objects can be centrally arranged and optimized for deployment; compared to the way that resource allocation equipment uses a unified algorithm to randomly find the deployment location for each resource object,
  • the embodiments of the present application can pre-determine the deployment positions of multiple resource objects in an optimized manner before creating multiple resource objects, so as to improve resource utilization efficiency.
  • the above steps 301 to 305 describe the creation process of multiple resource objects in the VNF instantiation scenario or the VNF expansion scenario.
  • the resource objects may fail, or the VNF may also be required Downsizing, the following describes the resource object failure scenario and VNF downsizing scenario.
  • the NFV management device requests the resource allocation device to turn off the HA function corresponding to one or more first hosts, after creating multiple resource objects, the NFV management device
  • the resource allocation device may be requested to enable the HA function corresponding to the one or more first hosts.
  • the resource objects deployed on the one or more first hosts can self-heal through the HA function.
  • the NFV management device may send a resource release request to the VIM.
  • the resource release request includes one or more first host identifiers and an instruction to enable the HA function.
  • the resource reservation request includes the identifier of the resource pool
  • the resource release request here may also include the identifier of the resource pool and the instruction to enable the HA function without carrying one or more first host identifiers, thereby saving transmission resources.
  • the NFV management device may not enable the HA function corresponding to one or more first hosts.
  • an embodiment of the present application further provides a method for rebuilding a resource object after failure (including step 306 and step 307) In the following, a detailed description will be given in conjunction with step 306 and step 307.
  • Step 306 After determining that the first resource object is faulty, the NFV management device may delete the first resource object, and determine the deployment position of the first resource object to be rebuilt according to the deployment position of the first resource object; NFV management device Sending a reconstruction request of the first resource object to the resource allocation device, where the reconstruction request includes the deployment location of the first resource object to be reconstructed. Accordingly, in step 307, the resource allocation device receives the reconstruction request of the first resource object, and reconstructs the first resource object according to the deployment position of the first resource object to be reconstructed. Understandably, the reconstruction request of the first resource object may further include demand information of the first resource object.
  • the specific implementation manner of the NFV management device deleting the first resource object can be referred to the existing technology, which will not be repeated here.
  • the port and data disk may be unmounted first, and then the first resource object is deleted.
  • the NFV management device can monitor the status of multiple resource objects. For example, the status of multiple resource objects can be monitored through a heartbeat mechanism. If the first resource object fails to feedback the heartbeat response in time, it can be determined that the first resource object occurs malfunction.
  • multiple resource objects include management resource objects and business resource objects; the NFV management device can monitor the status of the management resource objects, for example, the status of the management resource objects can be monitored through a heartbeat mechanism, and the NFV management device can manage the resources through Objects to monitor the status of business resource objects; for example, the first resource object is a business resource object, the second resource object is a management resource object used to manage the first resource object among the plurality of resource objects, and the second resource object is determined After the first resource object fails, a failure notification (used to indicate that the first resource object has failed) may be sent to the NFV management device, so that the NFV management device may determine that the first resource object has failed.
  • a failure notification used to indicate that the first resource object has failed
  • the resource allocation device replaces the first host with the second host, which may cause the resource object (such as the first resource object) deployed on the first host to fail.
  • the resource object such as the first resource object
  • the specifications of the first host and the second host are the same, and the identifiers of the first host and the second host are the same
  • the NFV management device may The deployment location is taken as the deployment location of the first resource object to be reconstructed, and sends the reconstruction request of the first resource object to the resource allocation device; accordingly, after receiving the reconstruction request, the resource allocation device may Where the resource object is deployed, the first resource object is created on the second host.
  • the deployment position of the first resource object after reconstruction is the same as the deployment position of the first resource object before reconstruction.
  • the specifications of the first host and the second host are the same, and the identifiers of the first host and the second host are different, that is, the resource allocation device deletes the original host identifier, and rebuilds to add a new host identifier , Equivalent to newly expanding a Host.
  • the resource allocation device may synchronize the replaced physical resource information (such as the identifier of the second Host) to the NFV management device.
  • the NFV management device After the NFV management device determines that the first resource object is faulty, it can obtain an idle host with the same specifications as the first host (such as the second host), and determine the deployment location of the first resource object to be rebuilt (may include the identifier of the second host) , And then send the reconstruction request of the first resource object to the resource allocation device; accordingly, after receiving the reconstruction request, the resource allocation device may create a second host on the second Host according to the deployment location of the first resource object to be reconstructed A resource object. It should be noted that, in this example, since the identifiers of the first Host and the second Host are different, it can be understood that the deployment position of the first resource object after reconstruction is different from the deployment position of the first resource object before reconstruction. In this situation, the NFV management device may also update the deployment position of the first resource object in the topology relationship table of the resource objects, so as to ensure the accuracy of the topology relationship table.
  • the NFV management device may determine the deployment position of the second resource object to be rebuilt according to the deployment position of the first resource object To complete the reconstruction of the first resource object.
  • the NFV management device may also change the redundant location after determining that the redundant location meets the demand information of the first resource object The remaining position is used as the deployment position of the first resource object to be reconstructed, and then the reconstruction of the first resource object is completed.
  • the above is only an example where the resource allocation device replaces the Host and causes the failure of the first resource object.
  • the method for rebuilding the resource object provided by the embodiment of the present application can also be applied to the situation where the resource object fails due to other reasons. No specific restrictions.
  • Embodiments of the present application also provide a processing method in a VNF downsizing scenario (including step 308 and step 309), which will be described in detail below in conjunction with step 308 and step 309.
  • Step 308 the NFV management device receives the VNF scaling request, and the scaling request includes the scaling policy information; the scaling policy information may be set by the operator, and is not specifically limited.
  • the NFV management device determines that the number of resource objects to be reduced is M, and M is an integer greater than or equal to 1 according to the volume reduction policy information and the VNF load information; the VNF load information can be obtained from the VNF by the NFV management device.
  • the NFV management device determines M resource objects to be downsized from the multiple resource objects according to the deployment position of each resource object among the multiple resource objects, and sends a delete request to the resource allocation device, the delete request includes the to be downsized Of the M resource objects. Accordingly, in step 309, the resource allocation device may delete the M resource objects to be reduced according to the deletion request.
  • the NFV management device determines that the M resource objects to be downsized from multiple resource objects can be implemented in a variety of ways.
  • One possible implementation method is: the NFV management device determines the number of VMs to be downsized, Divide multiple resource objects into N groups of resource objects. Each group of resource objects in the N groups of resource objects includes M resource objects; the NFV management device determines N groups of resource objects according to the deployment location of each resource object in the multiple resource objects The number of Hosts where each group of resource objects is located; the NFV management device determines the group of resource objects with the smallest number of Hosts as M resource objects to be downsized.
  • the number of hosts where two or more resource objects exist is the smallest, you can randomly select one of the resource objects to determine M resource objects to be downsized.
  • the number of Hosts where the first group of resource objects (including resource objects 1, resource objects 2, and resource objects 3) are located is 2 (Host1 and Host2)
  • the number of Hosts where the second group of resource objects (including resource object 1, resource object 3 and resource object 5) are located is 2 (Host1 and Host2)
  • the tenth group of resource objects (including resource object 3, resource object 4 and The number of Hosts where the resource object 5) is located is 1 (Host2).
  • the set of resource objects with the smallest number of Hosts is the tenth set of resource objects.
  • the three resource objects to be reduced are resource object 3 and resource object 4. And resource object 5.
  • VNF virtual network
  • the determined resource object to be reduced can be located on the same Host as much as possible, thereby reducing resource fragmentation caused by the reduction and effectively improving resource utilization.
  • the NFV management device may also send a resource release request to the resource allocation device.
  • the resource release request includes one or more
  • the identifier of the second Host may further include a reservation indication, and the reservation indication may be an indication to release pre-occupancy and/or an indication to turn on the HA function; one or more identifiers of the second Host are based on the M to be downsized Obtained from the deployment location of the resource objects.
  • the identifier of the one or more second hosts is the identifier of the host where the M resource objects to be reduced are located.
  • the resource release request may include the identifier of Host2.
  • the resource allocation device may release one or more second hosts (namely, Host2).
  • releasing one or more second hosts may include releasing pre-occupancy of one or more second hosts; in yet another example, releasing one or more second hosts may include turning on one or more second hosts Host corresponding HA function. In yet another example, releasing one or more second hosts may include releasing pre-occupancy of one or more second hosts and turning on HA functions corresponding to the one or more second hosts.
  • the resource release request may correspond to the resource reservation request described above.
  • the resource here The release request can be used to request to enable the HA function corresponding to one or more second hosts; if the resource reservation request is used to request to pre-occupy one or more first hosts, the resource release request here can be used to request a Or multiple second hosts release pre-occupancy. If the resource reservation request is used to request to pre-occupy one or more first hosts and turn off the HA function corresponding to the one or more first hosts, the resource release request here may be used to request one or more second hosts Release pre-occupancy and enable the HA function corresponding to one or more second hosts.
  • the NFV management device may also arrange the deployment positions of the resource objects deployed on the unreserved Host, for example, the resource object 1b is deployed on Host1a, and the resource is deployed on Host2a
  • the NFV management device determines that the idle resources on Host1a meet the demand information of resource object 2b, it can migrate resource object 2b to Host1a under the premise of acceptable business impact, thereby reducing resource fragmentation on Host1a.
  • the NFV management device proactively orchestrates the deployment positions of the created resource objects and gradually migrates the resource objects, which can more effectively reduce fragmented resources, facilitate the deployment of more resource objects, and improve resource utilization rate.
  • the functions performed by the NFV management device described in the first embodiment above may be performed by VNFM in the NFV architecture alone; or, they may be performed jointly by VNFM and NFVO in the NFV architecture, that is, VNFM and NFVO respectively perform
  • NFVO can perform the above steps 301 to 303.
  • NFVO can send the pre-arranged deployment location of each resource object to VNFM, and then VNFM can perform the above step 304.
  • the resource reservation request may be sent by the VNFM to the resource allocation device, or the resource reservation request may be sent by the NFVO to the resource allocation device. This embodiment of the present application does not specifically limit this.
  • the deployment location of multiple resource objects is pre-arranged by the NFV management device.
  • the deployment location of multiple resource objects may also be pre-arranged by the resource allocation device. The following is combined with the second embodiment The implementation of the resource allocation device pre-arranging the deployment positions of multiple resource objects will be described.
  • FIG. 4 is a schematic flowchart of a resource object management method provided in Embodiment 2 of the present application. As shown in FIG. 4, the method includes:
  • Step 401 The NFV management device determines the demand information of multiple resource objects that need to be created. For specific implementation, refer to step 301 above.
  • Step 402 The NFV management device sends the demand information of the multiple resource objects to the resource allocation device.
  • Step 403 After receiving the demand information of multiple resource objects, the resource allocation device obtains physical resource information, and pre-arranges the multiple resource objects according to the demand information of the multiple resource objects and the physical resource information A deployment position of each resource object, and the deployment position of each resource object is used to indicate a physical resource occupied by each resource object.
  • the resource allocation device pre-arranging the deployment positions of multiple resource objects reference may be made to the description of the NFV management device pre-arrangement of the deployment positions of multiple resource objects in Embodiment 1.
  • Step 404 The resource allocation device sends the deployment location of each resource object in the multiple resource objects to the NFV management device.
  • the resource allocation device may directly reserve one or more first hosts based on the deployment positions of multiple resource objects (one or more first hosts may be Hosts where multiple resource objects are located), such as pre-occupying one or more first hosts and/or turning off the HA function corresponding to one or more first hosts; or, the resource allocation device may also send it after receiving the NFV management device After the resource reservation request, reserve one or more first hosts. No specific restrictions.
  • Step 405 After receiving the deployment location of each resource object in the plurality of resource objects, the NFV management device sends a creation request of the plurality of resource objects to the resource allocation device, where the creation request of each resource object includes the Demand information of a resource object.
  • the creation request of each resource object may also include the deployment location of each resource object.
  • the resource allocation device pre-arranges the deployment location of each resource object in multiple resource objects and stores it locally, the creation request of each resource object sent by the NFV management device may not include each resource The deployment location of the object. This embodiment of the present application does not specifically limit this.
  • Step 406 The resource allocation device receives multiple resource object creation requests sent by the NFV management device, and creates multiple resource objects according to the deployment location of each resource object in the multiple resource objects.
  • Embodiment 2 the difference between Embodiment 2 and Embodiment 1 is that in Embodiment 2, the NFV management device sends the demand information of multiple resource objects to the resource allocation device.
  • the demand information and physical resource information of multiple resource objects pre-arrange the deployment positions of multiple resource objects, and in the first embodiment, the NFV management device obtains physical resource information from the resource allocation device, and according to the demand information of multiple resource objects and The physical resource information pre-arranges the deployment positions of multiple resource objects. That is to say, the execution subject of the pre-arranged deployment position of multiple resource objects is different.
  • step 301 the execution subject of the pre-arranged deployment position of multiple resource objects is different.
  • the above method may further include:
  • Step 407 After determining that the first resource object is faulty, the NFV management device deletes the first resource object and sends a reconstruction request of the first resource object to the resource allocation object, where the reconstruction request includes demand information of the first resource object.
  • Step 408 The resource allocation device receives the reconstruction request of the first resource object sent by the NFV management device, determines the deployment position of the first resource object to be reconstructed according to the deployment position of the first resource object, and based on the determined deployment position and the first The demand information of the resource object reconstructs the first resource object.
  • step 407 and step 408 are a possible processing method in the scenario where the first resource object fails. Understandably, other possible processing methods may also be used in Embodiment 2, for example, Step 306 and Step 307 in Embodiment 1 may also be used, which is not specifically limited.
  • step 407 and step 408 and step 306 and step 307 is that the former is that the NFV management device determines the deployment position of the first resource object to be reconstructed based on the deployment position of the first resource object, while the latter is caused by The resource allocation device determines the deployment position of the first resource object to be reconstructed based on the deployment position of the first resource object. That is to say, the execution subject that determines the deployment position of the first resource object to be reconstructed is different. Except for this difference, other steps can be performed by referring to step 306 and step 307 in the first embodiment.
  • Step 409 the NFV management device receives the VNF scaling request, and the scaling request includes the scaling policy information; the NFV management device determines that the number of resource objects to be scaled is M according to the scaling policy information and the VNF load information; NFV management The device sends the number of resource objects to be reduced to the resource allocation device.
  • Step 410 After receiving the number of resource objects to be reduced, the resource allocation device determines M resource objects to be reduced from the multiple resource objects according to the deployment position of each resource object among the multiple resource objects, And delete the M resource objects to be reduced.
  • step 409 and step 410 are a possible processing method in the VNF downsizing scenario. Understandably, other possible processing methods may also be used in Embodiment 2, for example, Step 308 and Step 309 in Embodiment 1 may also be used, which is not specifically limited.
  • step 409 and step 410 and step 308 and step 309 is that the former is that the NFV management device determines M to be downsized based on the number of resource objects to be downsized and the deployment positions of multiple resource objects The resource object, and the latter is that the resource allocation device determines M resource objects to be reduced based on the number of resource objects to be reduced and the deployment positions of multiple resource objects.
  • the execution subjects of the M resource objects to be reduced are determined to be different.
  • other steps can be performed with reference to step 308 and step 309 in the first embodiment.
  • Embodiment 2 differs from Embodiment 1 in that the main body that performs the related actions may be different, and other contents except this difference can be cross-referenced.
  • the resource allocation device pre-arranges the deployment location of each resource object according to the demand information and physical resource information of multiple resource objects, that is, the resource allocation device determines the deployment location of each resource object in advance , And then create each resource object based on a predetermined deployment location, so that from a global perspective, multiple resource objects can be centrally orchestrated and optimized for deployment; compared to resource allocation equipment, a uniform algorithm is used to randomly find each resource object
  • the embodiments of the present application can pre-determine the deployment location of multiple resource objects in an optimized manner before creating multiple resource objects, thereby improving resource utilization efficiency.
  • FIG. 5 is a schematic flowchart of a resource object management method provided in Embodiment 3 of the present application, which mainly relates to a VNF instantiation scenario, as shown in FIG. 5, including:
  • step 501 the operator calculates the required resource objects based on the system specifications and fills in the VNFD. For example, if the operator determines that a VNF needs to be instantiated, the VNFD configuration information can be filled in to the VNFD.
  • Step 502 upload the VNFD so that the VNFM can obtain the VNFD.
  • the operator may manually upload the VNFD to the VNFM, or the OSF/BSS or other network management entity in the NFV architecture may upload the VNFD to the VNFM through NFVO.
  • Step 503 Upload the VNF installation package so that the VNFM can obtain the VNF installation package.
  • the operator may manually upload the VNF installation package to the VNFM, or the OSF/BSS or other network management entity in the NFV architecture may upload the VNF installation package to the VNFM through NFVO.
  • Step 504 Start the VNF instantiation process.
  • Step 505 The VNFM determines the demand information of multiple resource objects that need to be created according to the VNFD of one or more VNFs.
  • VNFM can determine the number of resource objects to be created and the demand information of each resource object according to the VNFD.
  • the resource objects that need to be created may include management resource objects and business resource objects, which are not specifically limited; the demand information of the resource objects may include the specifications and affinity attributes of the resource objects, and the specifications of the resource objects may include the number of CPUs of the resource objects , CPU performance, memory size, bandwidth, storage size at least one item, not specifically limited.
  • VNFM can determine that 10 resource objects (2 management resource objects and 8 business resource objects) need to be created according to VNFD.
  • Step 506 The VNFM obtains physical resource information from the VIM, and pre-arranges according to the demand information of the multiple resource objects and the physical resource information to obtain the deployment location of each resource object in the multiple resource objects.
  • the deployment location of each resource object may be stored in the form of a topological relationship table (such as Table 2).
  • Step 507 The VNFM sends a resource reservation request to the VIM.
  • the resource reservation request may include an identifier of one or more first hosts (that is, hosts where multiple resource objects are located), and may further include a pre-occupancy indication and Turn off HA function indication.
  • Step 508 After receiving the resource reservation request, the VIM reserves one or more first hosts, that is, pre-occupies one or more first hosts, and disables the HA function corresponding to the one or more first hosts.
  • the VNFM may send a management resource object creation request to the VIM, where the creation request includes the deployment location of the management resource object.
  • the creation request includes the deployment location of the management resource object.
  • Step 510 the VIM deploys the management resource object according to the deployment location of the management resource object.
  • step 511 the VIM returns a creation response to the VNFM, which is used to indicate that the management resource object has been created.
  • Step 512 the VNFM starts the management resource object on the VNF based on the image file of the management resource object.
  • step 513 the VNF determines that the management resource object is started.
  • step 514 the VNF sends a request to download the VNF installation package to the VNFM.
  • step 515 the VNFM instructs the VNF to download the VNF installation package.
  • Step 516 the VNF initiates a request to instantiate a business resource object to the VNFM.
  • step 517 the VNFM sends a creation request of the business resource object to the VIM, where the creation request includes the deployment location of the business resource object.
  • the creation request includes the deployment location of the business resource object.
  • Step 518 VIM creates a business resource object according to the deployment location of the business resource object.
  • Step 519 the VIM returns a creation response of the business resource object to the VNFM, which is used to indicate that the business resource object has been created.
  • step 520 the VNFM returns a creation response of the business resource object to the VNF, which is used to indicate that the business resource object has been created.
  • FIG. 6 is a schematic flowchart of a resource object management method provided in Embodiment 4 of the present application, which mainly relates to a VNF expansion scenario, as shown in FIG. 6, including:
  • Step 601 The operator sets the expansion strategy information and uploads it to VNFM.
  • Step 602 the VNFM sends a request for obtaining load information to the VNF that needs to be expanded according to the expansion strategy.
  • Step 606 The VNF returns the load information of the VNF to the VNFM.
  • the VNFM calculates the number of resource objects to be expanded and the demand information of each resource object based on the expansion strategy and the load information of the VNF.
  • the resource objects that need to be expanded may all be business resource objects.
  • Step 605 The VNFM obtains physical resource information from the VIM, and pre-arranges according to the demand information of the multiple resource objects and the physical resource information to obtain the deployment location of each resource object in the multiple resource objects.
  • the deployment location of each resource object may be stored in the form of a topological relationship table (such as Table 2).
  • Step 606 The VNFM sends a resource reservation request to the VIM.
  • the resource reservation request may include an identifier of one or more first hosts (that is, hosts where multiple resource objects are located), and may further include a pre-occupancy indication and Turn off HA function indication.
  • Step 607 After receiving the resource reservation request, the VIM reserves one or more first hosts, that is, pre-occupies one or more first hosts, and disables the HA function corresponding to the one or more first hosts.
  • the VNFM may send a creation request of the business resource object to the VIM, and the creation request includes the deployment location of the business resource object.
  • the creation request includes the deployment location of the business resource object.
  • step 609 the VIM deploys the business resource object according to the deployment location of the business resource object.
  • step 610 the VIM returns a creation response of the business resource object to the VNFM, which is used to indicate that the business resource object has been created.
  • Step 611 the VNF starts the resource object, implements the service loading, and completes the capacity expansion process.
  • the deployment location of each resource object is pre-arranged by VNFM, so that multiple resource objects to be expanded can be considered in an integrated manner, effectively reducing Resource fragments appear in the Host, improving resource utilization efficiency.
  • FIG. 7 is a schematic flowchart of a resource object management method provided in Embodiment 5 of the present application, which mainly relates to a VNF downsizing scenario, as shown in FIG. 7, including:
  • Step 701 the operator sets the volume reduction strategy information and uploads it to the VNFM.
  • Step 702 the VNFM sends a request for obtaining load information to the VNF that needs to be downsized according to the downsizing policy information.
  • Step 703 The VNF returns the load information of the VNF to the VNFM.
  • step 704 the VNFM calculates the number of resource objects to be reduced based on the reduction policy information and the VNF load information.
  • Step 705 The VNFM determines M resource objects to be downsized according to the deployment positions of multiple resource objects included in the VNF to be downsized.
  • the M resource objects to be reduced can all be business resource objects.
  • Step 706 the VNFM sends a deletion request to the VIM, and the deletion request may include the identifiers of the M resource objects to be reduced.
  • step 707 the VIM returns a deletion response to the VNFM, which is used to indicate that M resource objects to be reduced have been deleted.
  • Step 708 The VNFM sends a resource release request to the VIM.
  • the resource release request may include one or more second host identifiers, and the one or more second hosts are the hosts where the M resource objects to be reduced are located.
  • the VIM releases one or more second hosts, such as releasing pre-occupancy for one or more second hosts, and enabling the HA function corresponding to the one or more second hosts.
  • step 710 the VIM returns a resource release response to the VNFM, which is used to indicate that one or more second hosts have been released.
  • the VNFM can select from multiple resource objects to be downsized according to the deployment positions of the multiple resource objects M resource objects, so that the selected M resource objects to be reduced can be located in the same host as much as possible, reduce resource fragmentation caused by the reduction, and effectively improve resource utilization.
  • FIG. 8 is a schematic flowchart of a resource object management method provided in Embodiment 6 of the present application, which mainly involves a management resource object failure scenario, as shown in FIG. 8, including:
  • Step 801 the VNFM sends a heartbeat request to the management resource object.
  • Step 802 the management resource object feedbacks the heartbeat response over time, or does not feedback the heartbeat response.
  • the VNFM may query the VIM for the status of the management resource object and the status of the Host.
  • Step 804 The VNFM determines that the management resource object is faulty according to the state of the management resource object and the state of the Host where it is located.
  • Step 805 the VNFM deletes the management resource object, for example, the port and data disk can be unmounted first, and then the management resource object is deleted.
  • Step 806 The VNFM determines the deployment location of the management resource object to be rebuilt according to the deployment location of the management resource object.
  • the VNFM sends a reconstruction request of the management resource object to the VIM.
  • the reconstruction request includes the deployment location of the management resource object to be reconstructed.
  • step 808 the VIM rebuilds the management resource object according to the deployment position of the management resource object to be rebuilt.
  • step 809 the VIM returns a reconstruction response to the VNFM, which is used to indicate that the management resource object has been rebuilt.
  • VNFM determines the deployment position of the management resource object to be rebuilt according to the deployment position of the management resource object, and then the VIM determines the deployment position of the management resource object to be rebuilt Reconstruct management resource objects, avoid VIM based on a unified deployment algorithm to randomly find the deployment location of the management resource objects to be rebuilt, which can reduce the occurrence of resource fragments in the Host and improve resource utilization efficiency.
  • FIG. 9 is a schematic flowchart of a resource object management method provided in Embodiment 7 of the present application, which mainly relates to a business resource object failure scenario, as shown in FIG. 9, including:
  • Step 901 The management resource object sends a heartbeat request to the business resource object.
  • Step 902 the service resource object feedbacks the heartbeat response over time, or does not feedback the heartbeat response.
  • Step 903 The management resource object determines that the business resource object is faulty.
  • Step 904 The management resource object sends a fault notification to the VNFM, which is used to indicate that the service resource object has a fault.
  • step 905 the VNFM deletes the business resource object, for example, the port and data disk can be unmounted first, and then the business resource object is deleted.
  • Step 906 The VNFM determines the deployment location of the business resource object to be rebuilt according to the deployment location of the business resource object.
  • the VNFM sends a reconstruction request of the business resource object to the VIM.
  • the reconstruction request includes the deployment location of the business resource object to be reconstructed.
  • step 908 the VIM reconstructs the business resource object according to the deployment location of the business resource object to be reconstructed.
  • step 909 the VIM returns a reconstruction response to the VNFM, which is used to indicate that the business resource object has been rebuilt.
  • VNFM monitors the status of business resource objects by managing resource objects.
  • VNFM determines the deployment position of the business resource object to be reconstructed according to the deployment position of the business resource object, and then by VIM manages resource objects according to the deployment location of the business resource objects to be rebuilt, which can reduce the occurrence of resource fragments in the Host and improve the efficiency of resource utilization.
  • step numbers in the various embodiments of the present application are only one possible example of the execution flow, and do not constitute a limitation on the execution order of each step. In the embodiments of the present application, there is no strict execution sequence between steps that do not have a time-dependent relationship.
  • the NFV management device or the resource allocation device may include a hardware structure and/or a software module corresponding to each function.
  • the present invention can be implemented in the form of hardware or a combination of hardware and computer software in combination with the units and algorithm steps of the examples described in the embodiments disclosed herein. Whether a function is performed by hardware or computer software driven hardware depends on the specific application of the technical solution and design constraints. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present invention.
  • FIG. 10 shows a possible exemplary block diagram of the device involved in the embodiment of the present application.
  • the device 1000 may exist in the form of software.
  • the device 1000 may include a processing unit 1002 and a communication unit 1003.
  • the processing unit 1002 is used to control and manage the operation of the device 1000.
  • the communication unit 1003 is used to support communication between the device 1000 and other devices.
  • the device 1000 may further include a storage unit 1001 for storing program codes and data of the device 1000.
  • the processing unit 1002 may be a processor or a controller, for example, it may be a general-purpose central processing unit (central processing unit, CPU). It can implement or execute various exemplary logical blocks, modules and circuits described in conjunction with the disclosure of the present invention.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of DSP and microprocessor, and so on.
  • the communication unit 1003 may be a communication interface, a transceiver, or a transceiver circuit, etc., where the communication interface is a general term, and in a specific implementation, the communication interface may include multiple interfaces.
  • the storage unit 1001 may be a memory.
  • the apparatus 1000 may be the NFV management device (such as VNFM and/or NFVO) in any of the foregoing embodiments, or may also be a semiconductor chip provided in the NFV management device.
  • the processing unit 1002 may support the apparatus 1000 to perform the actions of the NFV management device in the foregoing method examples. Alternatively, the processing unit 1002 mainly performs the internal actions of the NFV management device in the method example, and the communication unit 1003 may support communication between the apparatus 1000 and the resource allocation device.
  • the processing unit is used to determine the demand information of multiple resource objects that need to be created
  • the communication unit is used to obtain physical resource information from a resource allocation device, and the processing unit is also used to pre-arrange the multiple resources according to the demand information of the multiple resource objects and the physical resource information
  • a deployment position of each resource object in the object, and the deployment position of each resource object is used to indicate the physical resource occupied by each resource object;
  • the communication unit is further configured to send a creation request of the plurality of resource objects to a resource allocation device, and the creation request of each resource object includes a deployment location of each resource object.
  • the deployment location of each resource object includes:
  • the identifier of the central processing unit CPU where each resource object is located the identifier of the Host where the CPU is located; or,
  • the identification of the central processing unit CPU where each resource object is located the identification of the Host where the CPU is located, and the identification of the NUMA node where the CPU is located; or,
  • the identifier of the CPU where each resource object is located the identifier of the Host where the CPU is located, the identifier of the NUMA node where the CPU is located, and the memory allocated to each resource object.
  • the communication unit is further used to:
  • the resource reservation request includes identifiers of one or more first hosts; the resource reservation request is used to request reservation of the one or more first hosts; The identifier of the one or more first hosts is obtained according to the deployment location of each resource object in the plurality of resource objects.
  • reserving the one or more first hosts includes:
  • the processing unit is further configured to: delete the first resource object after determining that the first resource object fails; and determine the first to be reconstructed according to the deployment location of the first resource object A deployment location of resource objects;
  • the communication unit is further configured to send a reconstruction request of the first resource object to the resource allocation device, where the reconstruction request includes the deployment location of the first resource object to be reconstructed.
  • the first resource object is a business resource object
  • the second resource object is a management resource object used to manage the first resource object among the plurality of resource objects
  • the communication unit is further configured to receive a failure notification sent by a second resource object, where the failure notification is used to indicate that the first resource object has a failure.
  • the communication unit is further configured to receive a VNF instantiation request, and the instantiation request includes the VNF virtual network function description file VNFD;
  • the processing unit is specifically configured to Describe the VNFD of VNF and determine the demand information of multiple resource objects that need to be created; or,
  • the communication unit is further configured to receive a capacity expansion request of the VNF, the capacity expansion request includes capacity expansion strategy information; the processing unit is specifically configured to determine, based on the capacity expansion strategy information and the VNF load information, a Demand information for multiple resource objects.
  • the communication unit after the communication unit sends the request for creating the plurality of resource objects to the resource allocation device, the communication unit is further used to receive a VNF scaling request, where the scaling request includes scaling policy information;
  • the processing unit is further configured to determine the number of resource objects to be reduced to M according to the volume reduction policy information and the load information of the VNF; according to the deployment of each resource object in the plurality of resource objects Location, determining M resource objects to be reduced from the plurality of resource objects;
  • the communication unit is further configured to send a deletion request to the resource allocation device, where the deletion request includes the identifiers of the M resource objects to be reduced.
  • the processing unit determines M resource objects from the plurality of resource objects according to the deployment location of each of the plurality of resource objects, specifically:
  • a group of resource objects with the smallest number of Hosts is determined as the M resource objects to be reduced.
  • the communication unit after the communication unit sends a deletion request to the resource allocation device, it is also used to:
  • the resource release request includes identifiers of one or more second hosts, and the resource release request is used to request the release of the one or more second hosts; the one or The identifiers of the multiple second hosts are obtained according to the deployment position of each resource object in the M resource objects to be reduced.
  • the resource object is a virtual machine VM or a virtual container.
  • the apparatus 1000 may also be the resource allocation device in any of the foregoing embodiments, or may also be a semiconductor chip provided in the resource allocation device.
  • the processing unit 1002 may support the apparatus 1000 to perform the actions of the resource allocation device in the above method examples.
  • the processing unit 1002 mainly performs internal actions of the resource allocation device in the method example, and the communication unit 1003 may support communication between the apparatus 1000 and the NFV management device.
  • the communication unit is configured to receive multiple resource object creation requests sent by the NFV management device, and the creation request of each resource object among the multiple resource objects includes each resource The deployment location of the object;
  • the processing unit is configured to create each resource object according to the deployment location of each resource object.
  • the deployment location of each resource object includes:
  • the identifier of the central processing unit CPU where each resource object is located the identifier of the Host where the CPU is located; or,
  • the identification of the central processing unit CPU where each resource object is located the identification of the Host where the CPU is located, and the identification of the NUMA node where the CPU is located; or,
  • the identifier of the CPU where each resource object is located the identifier of the Host where the CPU is located, the identifier of the NUMA node where the CPU is located, and the memory allocated to each resource object.
  • the communication unit is further configured to receive a resource reservation request sent by the NFV management device, where the resource reservation request includes one or more identifiers of the first host; the one or The identifiers of the multiple first hosts are obtained based on the deployment location of each resource object in the multiple resource objects;
  • the processing unit is also used to reserve the one or more first hosts.
  • the processing unit reserves the one or more first hosts, specifically:
  • the processing unit pre-occupies the one or more first hosts, and/or, the processing unit turns off the HA function corresponding to the one or more first hosts.
  • the communication unit is further configured to receive a reconstruction request of the first resource object sent by the NFV management device, where the reconstruction request includes the deployment location of the first resource object to be reconstructed;
  • the processing unit is further configured to reconstruct the first resource object according to the deployment position of the first resource object to be reconstructed.
  • the communication unit is further configured to receive a resource release request sent by the NFV management device, where the resource release request includes one or more second host identifiers; the one or more The identifier of the second Host is obtained according to the deployment position of each of the M resource objects to be reduced;
  • the processing unit is also used to release the one or more second hosts.
  • the resource object is a VM or a virtual container.
  • FIG. 11 provides a schematic structural diagram of an apparatus.
  • the apparatus 1100 may be the NFV management device (such as NFVO and/or VNFM) or resource allocation device described in the foregoing Embodiments 1 to 7. Such as VIM).
  • the device 1100 may be used to implement the content described in the foregoing first embodiment to seventh embodiment. For details, reference may be made to the description in the foregoing first embodiment to seventh embodiment.
  • the device 1100 may include one or more processors 1101, and the processor 1101 may also be referred to as a processing unit, which may implement certain control functions.
  • the processor 1101 may be a general-purpose processor or a dedicated processor, etc., for example, it may be a baseband processor.
  • the processor 1101 may also store instructions and/or data 1103, and the instructions and/or data 1103 may be executed by the processor, so that the apparatus 1100 executes the method described in the foregoing embodiment Methods.
  • the processor 1101 may include a transceiver unit for implementing receiving and transmitting functions.
  • the transceiver unit may be a transceiver circuit or an interface.
  • the circuits or interfaces used to implement the receive and transmit functions can be separate or integrated.
  • the device 1100 may include a circuit that can implement the function of sending or receiving in the foregoing method embodiments.
  • the device 1100 may include one or more memories 1102, on which instructions 1104 may be stored, and the instructions may be executed on the processor, so that the device 1100 executes the description in the foregoing embodiment Methods.
  • the memory may also store data.
  • the processor may also store instructions and/or data. The processor and the memory may be set separately or integrated together.
  • the device 1100 may further include a transceiver 1105 and/or an antenna 1106.
  • the processor 1101 may be referred to as a processing unit to control the device.
  • the transceiver 1105 may be referred to as a transceiver unit, a transceiver, a transceiver circuit, or a transceiver, etc., for implementing the transceiver function of the device.
  • the apparatus 1100 may include a processor 1101 and a transceiver 1105.
  • processors and transceivers described in this application can be implemented in integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (application-specific integrated circuits (ASICs), printed circuit boards ( printed circuit board (PCB), electronic equipment, etc.
  • ICs integrated circuits
  • RFICs radio frequency integrated circuits
  • ASICs application-specific integrated circuits
  • PCB printed circuit board
  • electronic equipment etc.
  • the processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type Metal oxide semiconductors (positive channels, metal oxides, semiconductors (PMOS), bipolar junction transistors (Bipolar Junction Transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • N-type metal oxide semiconductor nMetal-oxide-semiconductor
  • PMOS metal oxides, semiconductors
  • BJT bipolar junction transistors
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, computer, server or data center Transmit to another website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device including a server, a data center, and the like integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)), or the like.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a DVD
  • a semiconductor medium for example, a solid state disk (SSD)
  • These computer program instructions may also be stored in a computer readable memory that can guide a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, the instructions
  • the device implements the functions specified in one block or multiple blocks of the flowchart one flow or multiple flows and/or block diagrams.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operating steps are performed on the computer or other programmable device to produce computer-implemented processing, which is executed on the computer or other programmable device
  • the instructions provide steps for implementing the functions specified in one block or multiple blocks of the flowchart one flow or multiple flows and/or block diagrams.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Stored Programmes (AREA)

Abstract

La présente invention se rapporte au domaine technique des communications. La présente invention concerne un procédé et un appareil de gestion d'objet ressource. Le procédé comprend les étapes suivantes : un dispositif de gestion de virtualisation des fonctions réseau (NFV) détermine des informations de demande d'une pluralité d'objets ressources devant être créés, obtient des informations de ressource physique à partir d'un dispositif d'attribution de ressources, et pré-orchestre, en fonction des informations de demande de la pluralité d'objets ressources et des informations de ressource physique, pour obtenir la position de déploiement de chacun de la pluralité d'objets ressources, la position de déploiement de chaque objet ressource étant utilisée pour indiquer la ressource physique occupée par chaque objet ressource ; ainsi, le dispositif de gestion de NFV envoie des demandes de création de la pluralité d'objets ressources au dispositif d'attribution de ressources, la demande de création de chacun de la pluralité d'objets ressources comprenant la position de déploiement de chaque objet ressource. Selon le procédé, le dispositif de gestion de NFV pré-détermine la position de déploiement de chaque objet ressource et crée un objet ressource sur la base de la position de déploiement prédéterminée de façon à orchestrer de manière centrale et optimiser le déploiement de la pluralité d'objets ressource à partir d'une perspective globale.
PCT/CN2019/126428 2018-12-21 2019-12-18 Procédé et appareil de gestion d'objet ressource WO2020125698A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811590814.X 2018-12-21
CN201811590814.XA CN111355602B (zh) 2018-12-21 2018-12-21 一种资源对象的管理方法及装置

Publications (1)

Publication Number Publication Date
WO2020125698A1 true WO2020125698A1 (fr) 2020-06-25

Family

ID=71100636

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/126428 WO2020125698A1 (fr) 2018-12-21 2019-12-18 Procédé et appareil de gestion d'objet ressource

Country Status (2)

Country Link
CN (1) CN111355602B (fr)
WO (1) WO2020125698A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115314389A (zh) * 2021-05-08 2022-11-08 中国移动通信有限公司研究院 一种网络服务扩容异常处理方法、装置和存储介质
CN115794337A (zh) * 2022-11-14 2023-03-14 北京百度网讯科技有限公司 资源调度方法、装置、云平台、设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102646052A (zh) * 2011-02-16 2012-08-22 中国移动通信集团公司 一种虚拟机部署方法、装置及系统
CN105656646A (zh) * 2014-11-10 2016-06-08 中国移动通信集团公司 一种虚拟网元的部署方法及装置
CN105700961A (zh) * 2016-02-29 2016-06-22 华为技术有限公司 业务容器创建方法及装置
US20170371717A1 (en) * 2014-12-29 2017-12-28 Ntt Docomo, Inc. Resource management in cloud systems
CN108132827A (zh) * 2016-11-30 2018-06-08 华为技术有限公司 一种网络切片资源映射方法、相关设备及系统

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103810023B (zh) * 2014-03-06 2016-09-07 中国科学院信息工程研究所 一种云平台中分布式应用的智能部署方法及系统
CN104301812B (zh) * 2014-09-19 2020-06-30 中国电力科学研究院信息通信研究所 一种光网络系统和网络功能虚拟化方法
CN104484220B (zh) * 2014-11-28 2017-12-22 杭州华为数字技术有限公司 虚拟化集群的动态资源调度的方法及装置
WO2016090608A1 (fr) * 2014-12-11 2016-06-16 华为技术有限公司 Procédé et appareil permettant de déterminer une ressource de machine virtuelle et produit-programme
CN104536803A (zh) * 2014-12-23 2015-04-22 西安电子科技大学 一种基于组合优化的虚拟机调度方法
US20160316011A1 (en) * 2015-04-27 2016-10-27 Telefonaktiebolaget L M Ericsson (Publ) Sdn network element affinity based data partition and flexible migration schemes
CN108241531A (zh) * 2016-12-23 2018-07-03 阿里巴巴集团控股有限公司 一种在集群中为虚拟机分配资源的方法和装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102646052A (zh) * 2011-02-16 2012-08-22 中国移动通信集团公司 一种虚拟机部署方法、装置及系统
CN105656646A (zh) * 2014-11-10 2016-06-08 中国移动通信集团公司 一种虚拟网元的部署方法及装置
US20170371717A1 (en) * 2014-12-29 2017-12-28 Ntt Docomo, Inc. Resource management in cloud systems
CN105700961A (zh) * 2016-02-29 2016-06-22 华为技术有限公司 业务容器创建方法及装置
CN108132827A (zh) * 2016-11-30 2018-06-08 华为技术有限公司 一种网络切片资源映射方法、相关设备及系统

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115314389A (zh) * 2021-05-08 2022-11-08 中国移动通信有限公司研究院 一种网络服务扩容异常处理方法、装置和存储介质
CN115794337A (zh) * 2022-11-14 2023-03-14 北京百度网讯科技有限公司 资源调度方法、装置、云平台、设备及存储介质
CN115794337B (zh) * 2022-11-14 2023-09-26 北京百度网讯科技有限公司 资源调度方法、装置、云平台、设备及存储介质

Also Published As

Publication number Publication date
CN111355602A (zh) 2020-06-30
CN111355602B (zh) 2021-11-30

Similar Documents

Publication Publication Date Title
KR102409142B1 (ko) 네트워크 슬라이스 배치 방법 및 장치
US20210326167A1 (en) Vnf service instantiation method and apparatus
US9999030B2 (en) Resource provisioning method
WO2020186911A1 (fr) Procédé et dispositif de gestion de ressources pour fonction de réseau virtualisé, vnf, conteneurisée
WO2015172362A1 (fr) Système réseau de virtualisation de fonction réseau, et procédé et dispositif de traitement de données
WO2017166136A1 (fr) Procédé et dispositif d'allocation de ressource de fonction de réseau virtuelle (vnf)
WO2017185251A1 (fr) Procédé de détermination de vnfm et orchestrateur de virtualisation de fonction de réseau
WO2019137516A1 (fr) Procédé et appareil de déploiement de tranche de réseau
US10055311B1 (en) Reversion operations for virtual computing environments
WO2019100266A1 (fr) Procédé et appareil de notification de service de machine hôte edge mobile
WO2020125698A1 (fr) Procédé et appareil de gestion d'objet ressource
WO2023016415A1 (fr) Nœud pour le fonctionnement d'un groupe de conteneurs, et système et procédé de gestion du groupe de conteneurs
WO2021185083A1 (fr) Procédé et dispositif d'instanciation de vnf
WO2021143183A1 (fr) Procédé de déploiement de machine virtuelle et appareil associé
WO2019052363A1 (fr) Procédé et appareil de modification d'instance de tranche de réseau
WO2021022947A1 (fr) Procédé de déploiement d'une machine virtuelle et dispositif associé
US20230105269A1 (en) Virtualized network service deployment method and apparatus
WO2023066224A1 (fr) Procédé et appareil de déploiement d'un service de conteneur
US20230259387A1 (en) Data flow mirroring method and apparatus
WO2018120222A1 (fr) Procédé, dispositif et système de gestion de vnffg
WO2023197815A1 (fr) Procédé et dispositif de réception et d'émission de messages
US11716678B2 (en) Distributed ledger directory service for wireless communication networks
US11281451B2 (en) Distributed backup and restoration in virtualized computing environments
WO2021129868A1 (fr) Procédé d'instanciation de service de réseau (ns) et orchestrateur de virtualisation de fonction de réseau (nfvo)
WO2022183796A1 (fr) Procédé de création de service de réseau (ns) et appareil associé

Legal Events

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

Ref document number: 19898330

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19898330

Country of ref document: EP

Kind code of ref document: A1