CN105677441A - Migration method of virtual machines, manager of virtual facility and coordinator - Google Patents

Migration method of virtual machines, manager of virtual facility and coordinator Download PDF

Info

Publication number
CN105677441A
CN105677441A CN201410673544.4A CN201410673544A CN105677441A CN 105677441 A CN105677441 A CN 105677441A CN 201410673544 A CN201410673544 A CN 201410673544A CN 105677441 A CN105677441 A CN 105677441A
Authority
CN
China
Prior art keywords
vim
migrated
virtual machine
resource
source
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN201410673544.4A
Other languages
Chinese (zh)
Other versions
CN105677441B (en
Inventor
倪伟渊
张园园
周皓隽
石腾
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201410673544.4A priority Critical patent/CN105677441B/en
Priority to PCT/CN2015/080670 priority patent/WO2016078391A1/en
Publication of CN105677441A publication Critical patent/CN105677441A/en
Application granted granted Critical
Publication of CN105677441B publication Critical patent/CN105677441B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The embodiment of the invention provides a migration method of virtual machines, a manager of a virtual facility and a coordinator. The migration method of virtual machines comprises following steps: obtaining resources usage information of all physics machines managed by a source VIM; determining the physics machines in idle states based on resources usage information of all the physics machines and resources threshold values of the pre-set physics machines and determining the virtual machines of the physics machine in idle states as the virtual machines to be migrated; sending migration request information to the coordinator for managing the source VIM, wherein migration request information comprises IDs of the virtual machines to be migrated and an ID of the source VIM; receiving migration indication information sent by the coordinator, wherein migration indication information comprises an ID of the target VIM of the virtual machines to be migrated; and migrating the virtual machines to be migrated to the physics machines managed by the target VIM. The embodiment of the migration method of virtual machines, the manager of the virtual facility and the coordinator help to optimize resources of a data center room and reduce energy consumption of the data center.

Description

Virtual machine migration method, virtual facility manager and coordinator
Technical Field
The embodiment of the invention relates to virtualization technologies, in particular to a virtual machine migration method, a virtual facility manager and a coordinator.
Background
A large number of dedicated hardware devices are included in a communication network to implement a large number of network services. If a new network service is brought online, new hardware devices are generally required to be added to the communication network, and due to the increasing diversification of network services, it becomes increasingly difficult to find suitable deployment space and power supply for the new hardware devices. The network element virtualization (NFV for short) technology can implement and operate network element devices in a software manner on a high-performance physical machine by using a virtualization technology, thereby avoiding troubles caused by adding new devices, device migration, and the like. The main architecture of the existing NFV technology may include a virtual network element (VNF) group, an infrastructure and management coordination (MANO) system. The VNF group includes at least one VNF, each VNF may include at least one virtual network element component (VNFC), and each VNFC may run on a physical machine of the infrastructure through a virtual machine. The at least one VNF may implement a Network Service (NS). The MANO system comprises a coordinator, a virtual network element manager (VNFM for short) and a virtual facility manager (VIM for short). Wherein the coordinator can perform resource orchestration for at least one VNF and network services based on virtual resources in the infrastructure.
The virtual machine migration can be performed under the conditions that the data center needs maintenance, the load is unbalanced and the like, and the virtual machine cross-data center migration is performed. The coordinator in the MANO can only determine a part of virtual machines in the data center meeting the migration condition as virtual machines to be migrated according to the virtual resource information of each data center recorded in the infrastructure resource directory, and determine a target data center for further migration.
However, due to the difference in running virtual machines, the resource utilization of the data centers of these non-migrated virtual machines is also different. In the existing scheme, a coordinator determines the overall migration of virtual resources of a data center according to the use condition of the virtual resources of the data center. However, at least one physical machine may be in an idle state in a data center that does not satisfy the migration condition, and if the existing scheme is adopted, the situation that the idle state physical machine exists in the data center cannot be handled, so that resource optimization among the data centers cannot be actually achieved, and energy consumption of the data center cannot be reduced.
Disclosure of Invention
The embodiment of the invention provides a virtual machine migration method, a virtual facility manager and a coordinator, and aims to solve the problem that in the prior art, energy consumption of a data center cannot be reduced only by migrating a virtual machine according to virtual resource information.
In a first aspect, an embodiment of the present invention provides a virtual machine migration method, including:
a source virtual facility manager VIM acquires resource use information of each physical machine managed by the source VIM;
the source VIM determines a physical machine in an idle state according to the resource use information of each physical machine and a preset resource threshold of the physical machine, and determines a virtual machine on the physical machine in the idle state as a virtual machine to be migrated;
the source VIM sends a migration request message to a coordinator managing the source VIM, wherein the migration request message comprises: the identification ID of the virtual machine to be migrated and the ID of the source VIM;
the source VIM receives a migration indication message sent by the coordinator, wherein the migration indication message comprises: the ID of the target VIM of the virtual machine to be migrated;
and the source VIM migrates the virtual machine to be migrated to a physical machine managed by the destination VIM of the virtual machine to be migrated according to the ID of the virtual machine to be migrated and the ID of the destination VIM of the virtual machine to be migrated.
According to the first aspect, in a first possible implementation manner of the first aspect, the determining, by the source VIM, that a physical machine in an idle state is ahead of the physical machine according to the resource usage information of each physical machine and a preset resource threshold of the physical machine, further includes:
and the source VIM acquires a preset resource threshold value of the physical machine.
According to a first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the resource threshold of the physical machine includes: a resource usage threshold or a resource idleness threshold;
the source VIM determines the physical machine in an idle state according to the resource usage information of each physical machine and a preset resource threshold of the physical machine, and the method comprises the following steps:
the source VIM determines the physical machine with the resource use information smaller than the resource use threshold value as the idle physical machine according to the resource use information of each physical machine and the resource use threshold value; or,
and the source VIM determines the resource idle information of each physical machine according to the resource use information of each physical machine, and determines the physical machine with the resource idle information being greater than or equal to the resource idle threshold value as the idle-state physical machine according to the resource idle information of each physical machine and the resource idle threshold value.
In a third possible implementation manner, according to any one of the first aspect to the second possible implementation manner of the first aspect, the sending, by the source VIM, the migration request message to the coordinator includes:
and the source VIM sends the migration request message to the coordinator through a virtual network element manager (VNFM).
According to any one of the first aspect to the third possible implementation manner of the first aspect, in a fourth possible implementation manner, the IDs of the virtual machines to be migrated included in the migration request message include IDs of at least two virtual machines to be migrated;
the migration indication message includes: the IDs of the at least two virtual machines to be migrated and the ID of the destination VIM of each virtual machine to be migrated;
the migrating the virtual machine to be migrated to the physical machine managed by the destination VIM of the virtual machine to be migrated by the source VIM according to the ID of the virtual machine to be migrated and the ID of the destination VIM of the virtual machine to be migrated, and the migrating comprises the following steps:
and the source VIM migrates each virtual machine to be migrated to a physical machine managed by the destination VIM of each virtual machine to be migrated according to the IDs of the at least two virtual machines to be migrated and the ID of the destination VIM of each virtual machine to be migrated.
In a second aspect, an embodiment of the present invention provides a virtual machine migration method, including:
the coordinator receives a migration request message sent by a source VIM; the migration request message includes: the ID of the virtual machine to be migrated and the ID of the source VIM are obtained;
the coordinator determines a target VIM for the virtual machine to be migrated according to the ID of the virtual machine to be migrated and the ID of the source VIM;
the coordinator sends a migration indication message to the source VIM, wherein the migration indication message comprises: the ID of the target VIM of the virtual machine to be migrated; the migration indication message is used for indicating the source VIM to migrate the virtual machine to be migrated to the physical machine managed by the destination VIM of the virtual machine to be migrated.
According to the second aspect, in a first possible implementation manner of the second aspect, before the receiving, by the coordinator, the migration request message sent by the source VIM, the method further includes:
the coordinator sends the resource threshold of the physical machine to the source VIM.
In a second possible implementation manner, the receiving, by the coordinator, the migration request message sent by the source VIM includes:
the coordinator receives the migration request message sent by the source VIM through the VNFM.
In a third possible implementation manner, according to any one of the second to third possible implementation manners of the second aspect, the determining, by the coordinator, a destination VIM for the virtual machine to be migrated according to the ID of the virtual machine to be migrated and the ID of the source VIM includes:
the coordinator determines the resource requirement of the virtual machine to be migrated and the virtual resource information of each VIM except the source VIM managed by the coordinator according to the ID of the virtual machine to be migrated and the ID of the source VIM;
the coordinator determines at least one candidate VIM for the virtual machine to be migrated according to the resource requirement of the virtual machine to be migrated and the virtual resource information of each other VIM except the source VIM;
the coordinator determines the VIM with the maximum receiving weight as the target VIM of the virtual machine to be migrated according to the receiving weight of each candidate VIM of the at least one candidate VIM; and the receiving weight of each candidate VIM represents the receiving requirement of the physical machine managed by each candidate VIM on the virtual machine to be migrated.
According to a third possible implementation manner of the second aspect, in a fourth possible implementation manner, before the determining, by the coordinator, that the VIM with the largest reception weight is the destination VIM of the virtual machine to be migrated according to the reception weight of each candidate VIM of the at least one candidate VIM, the method further includes:
the coordinator sends a weight request message to each candidate VIM respectively; the weight request message includes: the resource requirement of the virtual machine to be migrated;
the coordinator receives a weight request response message sent by each candidate VIM, wherein the weight request response message comprises: a receive weight for each of the candidate VIMs; the receive weight for each candidate VIM comprises: and each candidate VIM is obtained according to the resource requirement of the virtual machine to be migrated and the resource information of the physical machine managed by each candidate VIM.
According to a fourth possible implementation manner of the second aspect to the fourth possible implementation manner of the second aspect, in a fifth possible implementation manner, the IDs of the virtual machines to be migrated, which are included in the migration request message, include IDs of at least two virtual machines to be migrated;
the determining, by the coordinator, a destination VIM for the virtual machine to be migrated according to the ID of the virtual machine to be migrated and the ID of the source VIM includes:
the coordinator determines a destination VIM for each virtual machine to be migrated according to the IDs of the at least two virtual machines to be migrated and the ID of the source VIM; the migration indication message includes: the IDs of the at least two virtual machines to be migrated and the ID of the destination VIM of each virtual machine to be migrated.
In a third aspect, an embodiment of the present invention provides a VIM, where the VIM is a source VIM, and includes:
the acquisition module is used for acquiring resource use information of each physical machine managed by the source VIM;
the determining module is used for determining the physical machine in an idle state according to the resource use information of each physical machine and a preset resource threshold of the physical machine, and determining the virtual machine on the physical machine in the idle state as a virtual machine to be migrated;
a sending module, configured to send a migration request message to a coordinator managing the source VIM, where the migration request message includes: the ID of the virtual machine to be migrated and the ID of the source VIM;
a receiving module, configured to receive a migration indication message sent by the coordinator, where the migration indication message includes: the ID of the target VIM of the virtual machine to be migrated;
and the migration module is used for migrating the virtual machine to be migrated to a physical machine managed by the destination VIM of the virtual machine to be migrated according to the ID of the virtual machine to be migrated and the ID of the destination VIM of the virtual machine to be migrated.
According to a third aspect, in a first possible implementation manner of the third aspect, the obtaining module is further configured to obtain the resource threshold of the physical machine before the determining module determines, according to the resource usage information of each physical machine and a preset resource threshold of the physical machine, that the virtual machine is to be migrated.
According to a first possible implementation manner of the third aspect, in a second possible implementation manner, the resource threshold of the physical machine includes: a resource usage threshold or a resource idleness threshold;
the determining module is further configured to determine, according to the resource usage information of each physical machine and the resource usage threshold, that the physical machine with the resource usage information smaller than the resource usage threshold is the idle physical machine; or, the resource idle information of each physical machine is determined according to the resource usage information of each physical machine, and the physical machine with the resource idle information greater than or equal to the resource idle threshold is determined to be the physical machine in the idle state according to the resource idle information of each physical machine and the resource idle threshold.
In a third possible implementation manner, the sending module is further configured to send the migration request message to the coordinator through the VNFM.
According to any one of the third aspect to the third possible implementation manner of the third aspect, in a fourth possible implementation manner, the IDs of the virtual machines to be migrated, which are included in the migration request message, include IDs of at least two virtual machines to be migrated;
the migration indication message includes: the IDs of the at least two virtual machines to be migrated and the ID of the destination VIM of each virtual machine to be migrated;
the migration module is further configured to migrate each virtual machine to be migrated to a physical machine managed by the destination VIM of each virtual machine to be migrated according to the IDs of the at least two virtual machines to be migrated and the ID of the destination VIM of each virtual machine to be migrated.
In a fourth aspect, an embodiment of the present invention provides a coordinator, including:
the receiving module is used for receiving a migration request message sent by a source VIM; the migration request message includes: the ID of the virtual machine to be migrated and the ID of the source VIM are obtained;
the determining module is used for determining a destination VIM for the virtual machine to be migrated according to the ID of the virtual machine to be migrated and the ID of the source VIM;
a sending module, configured to send a migration indication message to the source VIM, where the migration indication message includes: the ID of the target VIM of the virtual machine to be migrated; the migration indication message is used for indicating the source VIM to migrate the virtual machine to be migrated to the physical machine managed by the destination VIM of the virtual machine to be migrated.
In a first possible implementation manner of the fourth aspect, the sending module is further configured to send a resource threshold of a physical machine to the source VIM before the receiving module receives the migration request message sent by the source VIM.
In a second possible implementation manner, the receiving module is further configured to receive the migration request message sent by the source VIM through the VNFM.
According to any one of the fourth to the fourth aspects of the second possible implementation manners, in a third possible implementation manner of the fourth aspect, the determining module is further configured to determine, according to the ID of the virtual machine to be migrated and the ID of the source VIM, the resource requirement of the virtual machine to be migrated and the virtual resource information of each VIM, which is managed by the coordinator and is other than the source VIM, determine at least one candidate VIM for the virtual machine to be migrated according to the resource requirement of the virtual machine to be migrated and the virtual resource information of each VIM other than the source VIM, and determine, according to the receiving weight of each candidate VIM of the at least one candidate VIM, the VIM with the largest receiving weight as the target VIM of the virtual machine to be migrated; the receiving weight of each candidate VIM is used for representing the receiving requirement of the physical machine managed by each candidate VIM on the virtual machine to be migrated.
According to a third possible implementation manner of the fourth aspect, in a fourth possible implementation manner, the sending module is further configured to send a weight request message to each candidate VIM before the determining module determines, according to the receiving weight of each candidate VIM of the at least one candidate VIM, that the VIM with the largest receiving weight is the destination VIM of the virtual machine to be migrated; the weight request message includes: the resource requirement of the virtual machine to be migrated;
the receiving module is further configured to receive a weight request response message sent by each candidate VIM, where the weight request response message includes: a receive weight for each of the candidate VIMs; the receive weight for each candidate VIM comprises: and each candidate VIM is obtained according to the resource requirement of the virtual machine to be migrated and the resource information of the physical machine managed by each candidate VIM.
In a fifth possible implementation manner, the IDs of the virtual machines to be migrated that are included in the migration request message include IDs of at least two virtual machines to be migrated;
the determining module is further configured to determine a destination VIM for each virtual machine to be migrated according to the IDs of the at least two virtual machines to be migrated and the ID of the source VIM; the migration indication message includes: the IDs of the at least two virtual machines to be migrated and the ID of the destination VIM of each virtual machine to be migrated.
According to the virtual machine migration method, the virtual facility manager and the coordinator provided by the embodiments of the present invention, a physical machine in an idle state may be determined by a source VIM according to acquired resource usage information of each physical machine managed by the source VIM and a preset resource threshold of the physical machine, then a virtual machine on the physical machine in the idle state is determined as a virtual machine to be migrated, a migration request message including an ID of the virtual machine to be migrated is sent to the coordinator, so that the coordinator determines a destination VIM for the virtual machine to be migrated, receives a migration indication message including the ID of the destination VIM of the virtual machine to be migrated and migrates the virtual machine to be migrated to the physical machine managed by the destination VIM of the virtual machine to be migrated, where the migration indication message includes the ID of the destination VIM of the virtual machine to be migrated and is sent by the coordinator. Therefore, according to the virtual machine migration method provided by the embodiment of the present invention, since the virtual machine of the physical machine in the idle state in the data center corresponding to the source VIM can be migrated to the physical machine managed by the destination VIM, even if the virtual resource information of the data center corresponding to the different VIMs managed by the coordinator does not satisfy the migration condition, the virtual machine on the physical machine in the idle state in the data center can be migrated, so that resource optimization of the physical machine managed by the VIM is achieved, and energy consumption of the physical machine managed by the VIM is reduced.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a schematic structural diagram of a management coordination system according to an embodiment of the present invention;
fig. 2 is a flowchart of a virtual machine migration method according to an embodiment of the present invention;
fig. 3 is a flowchart of another virtual machine migration method according to an embodiment of the present invention;
fig. 4 is a flowchart of another virtual machine migration method according to an embodiment of the present invention;
fig. 5 is a flowchart of a virtual machine migration method according to another embodiment of the present invention;
FIG. 6 is a schematic diagram of a VIM according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a coordinator according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The virtual machine migration method provided by the embodiments of the invention can be applied to a management coordination system. Fig. 1 is a schematic structural diagram of a management coordination system applied in the embodiment of the present invention. As shown in FIG. 1, MANO system 100 includes a coordinator 101, a VNFM102, and at least two VIMs 103. Each VIM103 may manage one data center 104. At least one physical machine 105 is included within each data center 104, wherein at least one virtual machine 106 runs on each physical machine 105. Where the coordinator 101 is connected to at least two VIMs 103, the coordinator 101 can manage the at least two VIMs 103 by performing resource orchestration on at least one virtual machine 106 running on a physical machine 105 of a data center 104 managed by the at least two VIMs 103. The at least one virtual machine 106 may be operated on a physical machine of the corresponding data center in a software manner according to a preset resource deployment policy. Each virtual machine 106 may be a virtual machine corresponding to any VNFC included in any VNF. Different VNFs may implement different network element functions. Each VNF includes at least one VNFC, different VNFCs can implement different module functions of the same network element function, and the at least one VNFC, when combined, can implement a complete network element function.
Fig. 2 is a flowchart of a virtual machine migration method according to an embodiment of the present invention. The method is suitable for performing cross-data center migration on the virtual machine, so that resource balance and resource optimization are performed on the data center. The method can be executed by any VIM of the MANO system, and the VIM can be specifically executed by a VIM for managing a physical machine operated by a virtual machine to be migrated, namely a source VIM. As shown in fig. 2, the method of the present embodiment includes the following steps:
step 201, the source VIM obtains the resource usage information of each physical machine managed by the source VIM.
Specifically, in a MANO system, a VIM may manage hardware resources corresponding to a data center in the infrastructure. The hardware resources corresponding to one data center in the infrastructure may include the physical machines managed by the one VIM. The infrastructure may be a network element virtualization infrastructure (NFVI) in the MANO system. Since each VIM may manage one data center, and one data center includes at least one physical machine, there is a connection between the source VIM and each physical machine managed by the source VIM, and there is a transmission interface. In this embodiment of the present invention, the source VIM may send a resource query message to each physical machine managed by the source VIM through a transmission interface between the source VIM and each physical machine managed by the source VIM, so as to obtain resource usage information of each physical machine managed by the source VIM.
Optionally, each physical machine managed by the source VIM may report respective resource usage information to the VIM managing each physical machine according to a preset period, that is, the source VIM reports the respective resource usage information, and the source VIM stores the reported resource usage information. The source VIM may be, for example, a data center resource table storing resource usage information reported by each physical machine managed by the source VIM, and the resource usage information of each physical machine is obtained. It should be noted that the source VIM may also obtain the resource usage information in other manners, and the embodiment of the present invention is described by way of example only and is not limited in sequence.
The resource usage information of each physical machine managed by the source VIM may include resource usage information of a Central Processing Unit (CPU) of each physical machine and/or resource usage information of a memory.
Step 202, the source VIM determines a physical machine in an idle state according to the resource usage information of each physical machine and a preset resource threshold of the physical machine, and determines a virtual machine on the physical machine in the idle state as a virtual machine to be migrated.
In particular, the resource threshold for the physical machine may include a resource usage threshold, or a resource idleness threshold. The resource threshold of the physical machine may be configured by an upper management device of the source VIM, such as a coordinator, a VNFM, or other management devices, or may be determined according to a preset resource threshold configuration rule. The coordinator may be a network virtualization coordinator (NFVO). The other management device may be, for example, an integrated management device that manages at least one VIM. The integrated management device may be, for example, a super virtual facility manager (SVIM). The source VIM may determine, according to the resource usage information of each physical machine and the resource threshold of the physical machine, that the physical machine whose resource usage information satisfies the resource threshold of the physical machine is in an idle state. The source VIM may determine that any virtual machine on the idle-state physical machine is the virtual machine to be migrated, or determine that all virtual machines on the idle-state physical machine are the virtual machine to be migrated. Thus, the virtual machine to be migrated may include at least one virtual machine.
Due to the virtual machine migration method provided by the embodiment of the invention, the virtual machines on the idle physical machines in the data center corresponding to the source VIM can be migrated, so that resource optimization among the data centers is realized, and the energy consumption of the data centers is reduced.
Step 203, the source VIM sends a migration request message to the coordinator managing the source VIM, where the migration request message includes: the identification ID of the virtual machine to be migrated and the ID of the source VIM.
Specifically, the coordinator may be the NFVO described above. The Identity (Identity, abbreviated as ID) of the virtual machine to be migrated may be represented by an ID of a physical machine where the virtual machine to be migrated is located and/or a specific location of the physical machine where the virtual machine to be migrated is located. Further, the ID of the virtual machine to be migrated may also be represented by identification information of a corresponding module function in the entire network service implemented by the virtual machine to be migrated.
The coordinator may determine the resource requirement of the virtual machine to be migrated according to the ID of the virtual machine to be migrated and the ID of the source VIM, and determine resource information of the data center corresponding to the VIM managed by the coordinator except for the source VIM according to the ID of the source VIM. And then, determining a target VIM for the virtual machine to be migrated according to the resource requirement of the virtual machine to be migrated and the resource information of the data center corresponding to the other VIMs. The data center corresponding to the target VIM of the virtual machine to be migrated can at least meet the resource requirement of the virtual machine to be migrated. Since the data center corresponding to the VIM that meets the resource requirement of the virtual machine to be migrated may include at least one VIM, the destination VIM of the virtual machine to be migrated may be any VIM selected by the coordinator from the at least one VIM, and the destination VIM may also be a VIM selected by the coordinator from the at least one VIM according to a preset selection rule.
It should be noted that, the coordinator can only obtain the virtual resource information of the VIM of the data center managed by the coordinator after virtualization by the virtual machine layer through the NFVI resource (NFVIResource) table. The resource information of the data center corresponding to the other VIMs determined by the coordinator may be virtual resource information of the data center corresponding to the other VIMs. The resource information of the data center corresponding to the other VIMs may be represented by resource usage information and/or free resource information of the data center corresponding to the other VIMs.
If the virtual machine to be migrated comprises at least two virtual machines, the coordinator determines a destination VIM for each virtual machine in the virtual machine to be migrated. In the at least one virtual machine, the destination VIMs of different virtual machines may be the same or different.
Step 204, the source VIM receives a migration indication message sent by the coordinator, where the migration indication message includes: and the ID of the destination VIM of the virtual machine to be migrated.
Step 205, the source VIM migrates the virtual machine to be migrated to the physical machine managed by the destination VIM of the virtual machine to be migrated according to the ID of the virtual machine to be migrated and the ID of the destination VIM of the virtual machine to be migrated.
Specifically, the source VIM may determine a virtual machine to be migrated according to the ID of the virtual machine to be migrated, determine a migration destination of the virtual machine to be migrated, that is, a destination VIM, according to the ID of the destination VIM of the virtual machine to be migrated, then migrate the virtual machine to be migrated, and migrate the virtual machine to be migrated to a physical machine managed by the destination VIM of the virtual machine to be migrated. The specific physical machine managed by the destination VIM for migrating the virtual machine to be migrated to the virtual machine to be migrated may be determined by the destination VIM according to the resource requirement of the virtual machine to be migrated and the resource condition of each physical machine managed by the destination VIM.
In the virtual machine migration method provided by the embodiment of the present invention, a physical machine in an idle state may be determined by a source VIM according to acquired resource usage information of each physical machine managed by the source VIM and a preset resource threshold of the physical machine, then a virtual machine on the physical machine in the idle state is determined as a virtual machine to be migrated, a migration request message including an ID of the virtual machine to be migrated is sent to a coordinator, so that the coordinator determines a destination VIM for the virtual machine to be migrated, receives a migration indication message including the ID of the destination VIM of the virtual machine to be migrated and sends the virtual machine to be migrated to the physical machine managed by the destination VIM of the virtual machine to be migrated according to the ID of the source VIM and the ID of the destination VIM of the virtual machine to be migrated. Because the virtual machine to be migrated is determined by the source VIM according to the resource usage information of each physical machine and the preset resource threshold of the physical machine, and the virtual machine on the physical machine in the idle state in each physical machine managed by the source VIM, the virtual machine migration method provided by the embodiment of the invention can migrate the virtual machine of the physical machine in the idle state in each physical machine managed by the source VIM to the physical machine managed by the destination VIM, so that the virtual machine on the physical machine in the idle state in the data centers can be migrated even if the virtual resource information of the data centers corresponding to different VIMs managed by the coordinator does not meet the migration condition, thereby optimizing the resources among the data centers and reducing the energy consumption of the data centers.
It should be noted that, in the virtual machine migration method provided in the embodiment of the present invention, after the source VIM migrates the to-be-migrated machine to the destination VIM of the to-be-migrated virtual machine, the source VIM further sends a migration result to the coordinator through a migration notification message, where the migration result may be represented by a predefined operation indication value. For example, the success of the migration result can be represented by a binary number of 1, and the failure of the migration result can be represented by a binary number of 0. The migration notification message may further include information of virtual resources after the source VIM has migrated out of the virtual machine to be migrated, and information of virtual resources after the destination VIM has migrated into the virtual machine to be migrated. After receiving the migration notification message sent by the source VIM, the coordinator may further perform resource update on the infrastructure resource directory according to the virtual resource information after the source VIM migrates the virtual machine to be migrated and the virtual resource information after the destination VIM moves into the virtual machine to be migrated, and also update the location information of the VNFC corresponding to the virtual machine to be migrated in the NFV instance (Instances) record table.
The embodiment of the invention also provides a virtual machine migration method. Optionally, on the basis of the method in the foregoing embodiment, before the determining, by the source VIM in step 202, the physical machine in an idle state according to the resource information of each physical machine and a preset resource threshold of the physical machine, the method further includes:
and the source VIM acquires a preset resource threshold value of the physical machine.
Specifically, the source VIM may be a resource threshold of the physical machine that was pre-configured in the source VIM during the construction initialization of the MANO system. The source VIM may also be a resource threshold for the physical machine as determined by a configuration message sent by a receiving coordinator or other management device. In the MANO system, the physical resources used by the at least one VNF may include hardware resources of the at least one data center. That is, in the MANO system, the coordinator may manage at least one VIM, where one VIM may manage hardware resources on at least one physical machine in one data center. Then the coordinator may also send resource thresholds including the physical machine for other VIMs when sending the resource threshold of the physical machine for the source VIM. Thus, the source VIM may be the resource threshold of the physical machine that the coordinator sent over the broadcast or multicast.
Optionally, in the method described in the foregoing embodiment, the resource threshold of the physical machine includes: a resource usage threshold or a resource idleness threshold.
The resource usage information may be represented by, for example, the resources and/or the resource usage rates used by all virtual machines in the physical machine.
In the step 202, the determining, by the source VIM, the physical machine in the idle state according to the resource usage information of each physical machine and the preset resource threshold of the physical machine includes:
and the source VIM determines the physical machine with the resource use information smaller than the resource use threshold as the idle physical machine according to the resource use information of each physical machine and the resource use threshold.
For example, if the resource usage threshold of the physical machine is 10% of the average CPU and memory usage. If the CPU utilization of one physical machine in the resource information of each physical machine acquired by the source VIM is 8%, the memory utilization of the physical machine is 6%, that is, the average resource utilization of the physical machine is 7%. The average resource utilization rate of the physical machine is 7% which is less than the resource utilization threshold value of the physical machine is 10%. Thus. The source VIM may determine that the physical machine is an idle physical machine according to the resource information of each physical machine and a preset resource threshold of the physical machine, and then set all virtual machines on the physical machine as the virtual machine to be migrated.
Alternatively, the determining, by the source VIM in step 202, that the virtual machine in the idle state is in the idle state according to the resource usage information of each physical machine and a preset resource threshold of the physical machine may further include:
and the source VIM determines the resource idle information of each physical machine according to the resource use information of each physical machine, and determines the physical machine with the resource idle information being greater than or equal to the resource idle threshold value as the idle-state physical machine according to the resource idle information of each physical machine and the resource idle threshold value.
Specifically, the resource vacancy information may be represented by, for example, remaining resources and/or a resource vacancy rate in the physical machine. The specific implementation process of determining the physical machine in the idle state according to the resource idle information of each physical machine and the resource idle threshold may be similar to the process of determining according to the resource usage information of each physical machine and the resource usage threshold, except that the physical machine whose resource idle information is greater than or equal to the resource idle threshold is determined according to the resource idle information of each physical machine and the resource idle threshold. For similar parts, the embodiments of the present invention are not described in detail herein.
And the physical machine with the resource use information smaller than the resource use threshold value, or the physical machine with the resource idle information larger than or equal to the resource idle threshold value is the physical machine in the idle state. And determining the virtual machines on the physical machines as virtual machines to be migrated, and then migrating the virtual machines, so that the energy consumption of the idle physical machine can be avoided.
The virtual machine migration method provided by the embodiment of the invention specifically explains the scheme of the embodiment through various schemes of determining the physical machine in the idle state, and better ensures the resource optimization among the data centers managed by the coordinator, thereby reducing the energy consumption of the data centers.
Further, the sending, by the source VIM, the migration request message to the coordinator in step 203 may include:
the source VIM sends the migration request message to the coordinator via the VNFM.
Optionally, the IDs of the virtual machines to be migrated included in the migration request message include IDs of at least two virtual machines to be migrated.
The migration indication message includes: the IDs of the at least two virtual machines to be migrated and the ID of the destination VIM of each virtual machine to be migrated.
In the foregoing embodiment, in step 205, migrating, by the source VIM, the virtual machine to be migrated to the physical machine managed by the destination VIM of the virtual machine to be migrated according to the ID of the virtual machine to be migrated and the ID of the destination VIM of the virtual machine to be migrated, includes:
and the source VIM migrates each virtual machine to be migrated to a physical machine managed by the destination VIM of each virtual machine to be migrated according to the ID of the at least two virtual machines to be migrated and the ID of the destination VIM of each virtual machine to be migrated.
Specifically, if the to-be-migrated virtual machine includes at least two virtual machines, and the destination VIMs of each to-be-migrated virtual machine are the same, that is, the migration indication message includes the same ID of the destination VIM of each to-be-migrated virtual machine, the virtual machine migration method may be executed to migrate the different virtual machines to the physical machine managed by the same destination VIM. If the destination VIMs of different virtual machines are different, that is, the migration indication message includes the ID of the destination VIM of each virtual machine to be migrated that is different, the virtual machine migration method may be executed to migrate the different virtual machines to physical machines managed by the different destination VIMs.
The virtual machine migration method provided by the embodiment of the invention provides a plurality of implementation methods for the source VIM to acquire the resource threshold of the physical machine and determine the physical machine in the idle state, namely determine the virtual machine to be migrated, thereby better ensuring the resource optimization among different data centers managed by the coordinator and reducing the energy consumption of the data centers.
Fig. 3 is a flowchart of a virtual machine migration method according to another embodiment of the present invention, which may be executed by a coordinator. As shown in fig. 3, the method includes the following:
step 301, the coordinator receives a migration request message sent by a source VIM; the migration request message includes: and the ID of the virtual machine to be migrated and the ID of the source VIM.
The virtual machine to be migrated is the source VIM, and determines a physical machine in an idle state according to the acquired resource use information of each physical machine in the data center corresponding to the source VIM and a preset resource threshold of the physical machine, and then determines the virtual machine on the physical machine in the idle state. The virtual machine to be migrated at least comprises at least one virtual machine.
Step 302, the coordinator determines a destination VIM for the virtual machine to be migrated according to the ID of the virtual machine to be migrated and the ID of the source VIM.
Step 303, the coordinator sends a migration indication message to the source VIM, where the migration indication message includes: the ID of the target VIM of the virtual machine to be migrated; the migration indication message is used for indicating the source VIM to migrate the virtual machine to be migrated to the physical machine managed by the destination VIM of the virtual machine to be migrated.
In the virtual machine migration method provided by the embodiment of the present invention, the coordinator may send the ID of the virtual machine to be migrated to the source VIM according to the received ID of the virtual machine to be migrated sent by the source VIM and the ID of the source VIM, which is a destination VIM determined by the virtual machine to be migrated, and send the ID of the destination VIM of the virtual machine to be migrated to the source VIM, so that the source VIM may migrate the virtual machine to be migrated to a physical machine managed by the destination VIM of the virtual machine to be migrated. Therefore, by adopting the virtual machine migration method provided by the embodiment of the invention, even if the virtual resource information of the data centers corresponding to different VIMs managed by the coordinator does not meet the migration condition, the data centers can realize resource optimization and reduce the energy consumption of the data centers.
Optionally, before the coordinator receives the migration request message sent by the source VIM in step 301 in the embodiment, the method further includes:
the coordinator sends the resource thresholds of the physical machines to the source VIM.
The resource threshold of the physical machine is used to instruct the source VIM to determine, in combination with the acquired resource information of each physical machine in the data center corresponding to the source VIM, a physical machine in an idle state and determine the virtual machine on the physical machine in the idle state as the virtual machine to be migrated.
Alternatively, in step 301 of the above scheme, the receiving, by the coordinator, the migration request message sent by the source VIM may include:
the coordinator receives the migration request message sent by the source VIM through the VNFM.
According to the virtual machine migration method provided by the embodiment of the invention, the coordinator can also better ensure resource optimization among data centers managed by the coordinator by sending the resource threshold value of the physical machine to the source VIM.
Another embodiment of the present invention further provides a virtual machine migration method, as shown in fig. 4. Fig. 4 is a flowchart of another virtual machine migration method according to an embodiment of the present invention. Optionally, in step 302, the method may include that the coordinator determines a specific description of a destination VIM for the virtual machine to be migrated according to the ID of the virtual machine to be migrated and the ID of the source VIM, and the method includes:
step 401, the coordinator determines the resource requirement of the virtual machine to be migrated and the virtual resource information of each VIM managed by the coordinator except the source VIM according to the ID of the virtual machine to be migrated and the ID of the source VIM.
Step 402, the coordinator determines at least one candidate VIM for the virtual machine to be migrated according to the resource requirement of the virtual machine to be migrated and the virtual resource information of each VIM other than the source VIM.
In step 403, the coordinator determines, according to the receiving weight of each candidate VIM of the at least one candidate VIM, the VIM with the largest receiving weight as the destination VIM of the virtual machine to be migrated.
The receiving weight of each candidate VIM represents the receiving requirement of the physical machine managed by each candidate VIM on the virtual machine to be migrated.
Specifically, the larger the receiving weight is, the larger the receiving requirement of the physical machine managed by the corresponding candidate VIM on the virtual machine to be migrated is. The receiving requirement of the physical machine managed by the candidate VIM on the virtual machine to be migrated may be that the physical machine managed by the candidate VIM determines resource information of the physical machine managed by the candidate VIM after determining that the virtual machine to be migrated is migrated by pre-receiving the virtual machine to be migrated.
The receiving weight of each candidate VIM may be a receiving weight determined by each candidate VIM received by the coordinator according to resource information of the physical machine managed by the coordinator and resource requirements of the virtual machine. Among the receiving weights of the at least one candidate VIM, different receiving weights may have different assignments, such as any value between 0 and 1. The larger the receiving weight is, the stronger the willingness of the physical machine managed by the candidate VIM corresponding to the receiving weight to receive the virtual machine to be migrated is, so that in the embodiment, the coordinator may determine the VIM with the largest receiving weight as the destination VIM of the virtual machine to be migrated, and notify the ID of the destination VIM of the virtual machine to be migrated to the source VIM through the migration indication message. Because the coordinator determines the destination VIM of the virtual machine to be migrated according to the receiving weight of each candidate VIM, after the source VIM migrates the virtual machine to be migrated to the destination VIM of the virtual machine to be migrated, the physical resource allocation of the data centers managed by the source VIM and the destination VIM respectively is more reasonable, the resources among the data centers managed by the coordinator are optimized, and the energy consumption of the data centers is reduced.
Optionally, before the step 403 in the foregoing scheme, the method determines, according to the receiving weight of each candidate VIM of the at least one candidate VIM, that the VIM with the largest receiving weight is the destination VIM of the virtual machine to be migrated, further includes:
in step 403a, the coordinator sends a weight request message to each candidate VIM, where the weight request message may include the resource requirement of the virtual machine to be migrated.
In step 403b, the coordinator receives a weight request response message sent by each candidate VIM, where the weight request response message includes: a receive weight for each candidate VIM; the receive weight for each candidate VIM includes: and each candidate VIM is obtained according to the resource requirement of the virtual machine to be migrated and the resource information of the physical machine managed by each candidate VIM.
Specifically, the resource requirement of the virtual machine to be migrated may be a physical resource on the physical machine required for installing the virtual machine to be migrated. The resource requirements of the virtual machine to be migrated include: and the CPU processing resource and/or the memory storage resource of the physical machine required to be occupied by the virtual machine to be migrated. The CPU processing resource may be represented by a resource usage value of the CPU processing resource, and the memory storage resource may also be represented by a resource usage value of the memory storage resource.
The receiving weight of each candidate VIM obtained by each candidate VIM may be obtained by using a resource allocation algorithm of each candidate VIM according to the resource requirement of the virtual machine to be migrated and the resource information of the physical machine managed by each candidate VIM.
The resource allocation algorithm may be an average resource allocation algorithm. In the at least one candidate VIM, each candidate VIM may be, for example, resource information of a different physical machine managed by each candidate VIM after the virtual machine to be migrated is migrated to the physical machine managed by each candidate VIM is calculated according to a resource requirement of the virtual machine to be migrated, so that a receiving weight of the corresponding VIM is determined according to the resource information of the different physical machine managed by each candidate VIM.
The receive weight for each candidate VIM may be represented by the inverse of the standard deviation of resource usage for each candidate VIM. The each candidate VIM may be configured to calculate an inverse of a standard deviation of resource usage of different physical machines managed by the each candidate VIM after migrating the virtual machine to be migrated to the physical machine managed by the each candidate VIM, and use the inverse of the standard deviation of resource usage as a receiving weight of the each candidate VIM. If the resource requirement of the virtual machine to be migrated includes: and the CPU processing resource utilization value and the memory storage resource utilization value of the physical machine required by the virtual machine to be migrated. Then, the standard deviation may be, for example, an average of the CPU processing resource usage and the memory storage resource usage, that is, an average usage, as a standard value, and the standard value and the CPU processing resource usage and the memory storage resource usage variance are respectively calculated as square of the standard value and the CPU processing resource usage. The utilization rate of the CPU processing resource may be obtained by calculation according to, for example, a utilization value of the CPU processing resource of the physical machine required by the virtual machine to be migrated, a current CPU processing resource utilization condition of each physical machine, and a total CPU processing resource of each physical machine. The usage rate of the memory storage resource may be obtained by calculation according to the usage value of the memory storage resource of the physical machine required by the virtual machine to be migrated, the current usage condition of the memory storage resource of each physical machine, and the total memory storage resource of each physical machine, for example. In the embodiment of the present invention, the larger the value of the receiving weight of the candidate VIM is, the better the corresponding resource allocation effect is, so that the larger the receiving demand of the physical machine managed by the candidate VIM on the virtual machine to be migrated is, the larger the coordinator may select, according to the receiving weight of each VIM in the at least one candidate VIM, the VIM with the largest receiving weight as the target VIM of the virtual machine to be migrated.
For example, suppose that the ith virtual machine to be migrated is migrated to the physical machine managed by the kth VIM, which may be denoted as VIMK. Then the VIMKThe CPU processing resource utilization rate of the physical machine to be managed is 60%, the memory storage resource utilization rate of the physical machine is 40%, and the average utilization rate, that is, the average 50% of the 60% and 40%, is taken as a standard value. The VIMKThe standard deviation of resource usage of (2) may be obtained by summing the squares of the 60% to 50% difference and the squares of the 40% to 50% difference and then squaring the result of the summation. The VIMKThe receive weight of (a) may be the inverse of the standard deviation, i.e., the inverse of the result after the square of the square. The VIMKThe resource usage standard deviation is the receiving weight of the ith virtual machine to be migrated received by the data center corresponding to the kth VIM.
It should be noted that, the obtaining of the receiving weight is only described as an example, and the resource allocation algorithm used for calculating the receiving weight and the resource requirement of the virtual machine to be migrated may further include other resource parameters, so that the obtaining of the receiving weight may also be obtained according to other similar manners, and is not described herein again.
Optionally, the IDs of the virtual machines to be migrated included in the migration request message include IDs of at least two virtual machines to be migrated.
In step 302, the determining, by the coordinator, the destination VIM for the virtual machine to be migrated according to the ID of the virtual machine to be migrated and the ID of the source VIM may include:
the coordinator respectively determines a destination VIM for each virtual machine to be migrated according to the IDs of the at least two virtual machines to be migrated and the ID of the source VIM; the migration indication message includes: the IDs of the at least two virtual machines to be migrated and the ID of the destination VIM of each virtual machine to be migrated.
Because the receiving weight of each candidate VIM is obtained by each candidate VIM according to the resource requirement of the virtual machine to be migrated and the resource information of the physical machine managed by each candidate VIM, the coordinator can select the target VIM according to the receiving weight of at least one candidate VIM, and the resource requirement of the virtual machine to be migrated can be met. And performing virtual machine migration based on the target VIM determined by the coordinator, so that resource allocation among data centers corresponding to different VIMs managed by the coordinator is more reasonable, and resource optimization among the data centers managed by the coordinator is better realized.
According to the virtual machine migration method provided by the embodiment of the invention, at least one candidate VIM can be determined for the virtual machine to be migrated through the coordinator according to the ID of the virtual machine to be migrated and the ID of the source VIM, and the VIM with the largest receiving weight is determined as the target VIM of the virtual machine to be migrated according to the receiving weight of each candidate VIM in the at least one candidate VIM.
The embodiment of the invention also provides a virtual machine migration method. The embodiment of the present invention specifically describes the virtual machine migration method according to any one of the above embodiments by way of an example. Fig. 5 is a flowchart of another virtual machine migration method according to an embodiment of the present invention. As shown in fig. 5, the method may include:
step 501, the coordinator sends a configuration message to the source VIM, where the configuration message includes: a resource usage threshold of the physical machine.
The configuration message may be, for example, that the average resource utilization of one physical machine managed by the source VIM is less than the resource usage threshold of the physical machine, and that other physical machines managed by the source VIM cannot accommodate the virtual machine on the physical machine. The average resource utilization of the physical machine may be, for example, an average utilization of CPU processing resources and memory storage resources of the physical machine. For example, the configuration message may be that, in each physical machine managed by the source VIM, an average resource utilization rate of CPU processing resources and memory storage resources of an i-th physical machine is less than 10%, and in each physical machine managed by the source VIM, other physical machines cannot accommodate a virtual machine on the physical machine.
It should be noted that the coordinator also sends a configuration message to other VIMs to send the resource usage threshold of the physical machine for the other VIMs.
Step 502, the source VIM obtains resource usage information of each physical machine managed by the source VIM.
Step 503, the source VIM determines the physical machine in the idle state according to the resource usage information of each physical machine and the resource threshold of the physical machine, and takes all the virtual machines on the physical machine in the idle state as the virtual machines to be migrated.
If, in the resource information, the CPU processing resource utilization rate of the nth physical machine in the data center corresponding to the source VIM is 8%, and the memory storage resource utilization rate is 6%, then the average resource utilization rate of the nth physical machine is 7%. If the resource threshold in the migration condition is 10%, the source VIM may determine that all virtual machines on the nth physical machine are to-be-migrated virtual machines.
Step 504, the source VIM sends a migration request message to the coordinator, where the migration request message includes the ID of the virtual machine to be migrated and the ID of the source VIM.
The source VIM may generate the migration request message including the ID of the virtual machine to be migrated and the ID of the source VIM according to the ID of the virtual machine to be migrated and the ID of the source VIM through a transmission interface between the source VIM and the coordinator, which is configured in advance, and send the migration request message to the coordinator.
Step 505, the coordinator determines at least one candidate VIM for the virtual machine to be migrated according to the ID of the virtual machine to be migrated and the ID of the source VIM.
The coordinator may obtain, according to the ID of the virtual machine to be migrated, a VNF-level resource deployment policy of the VNFC corresponding to the virtual machine to be migrated and an NS-level resource deployment policy of the VNF to which the VNFC corresponding to the virtual machine to be migrated belongs, and then determine whether migration of the virtual machine to be migrated conforms to the VNF-level resource deployment policy and the NS-level deployment policy. If the migration of the virtual machine to be migrated conforms to the VNF-level resource deployment policy and the NS-level resource deployment policy, the virtual machine to be migrated may be migrated. If not, the coordinator rejects the migration of the virtual machine to be migrated, that is, returns a migration rejection message to the source VIM, where the migration rejection message includes a rejection cause value, such as virtual machine 01, and rejects the migration.
And the coordinator also divides the virtual machines which need to be migrated to the data center corresponding to the same VIM and the data center corresponding to different VIMs according to the VNF-level resource deployment strategy and the NS-level resource deployment strategy.
It should be noted that the coordinator may query a virtual network element directory (VNFR for short) in the NFV instance directory according to the ID of the virtual machine to be migrated, respectively, to obtain the ID of the VNFC corresponding to the virtual machine to be migrated, the resource requirement of the VNFC, the ID of the VNF to which the VNFC belongs, and a resource deployment policy of the VNF to which the VNFC belongs, that is, the VNF-level resource deployment policy. Wherein, the resource requirement of the VNFC, that is, the resource requirement of the virtual machine to be migrated. The VNF-level resource deployment policy includes: the VNFC is deployed in the same physical machine as other VNFCs in the VNF to which the VNFC belongs, or is deployed in corresponding information of different physical machines.
The coordinator may query a network service directory (VSR) in the NFV instance directory according to the ID of the source VIM and the ID of the VNF, and obtain a resource deployment policy of the NS to which the VNF belongs, that is, a resource deployment policy of the NS level, and IDs of VIMs corresponding to data centers where other VNFs of the NS are located and having a constraint relationship with the VNF. The resource deployment strategy of the NS level comprises the following steps: the VNF is deployed in the same data center as other VNFs in the NS to which the VNF belongs, or is deployed in corresponding information of a different data center.
The coordinator also queries the infrastructure resource directory according to the ID of the source VIM to obtain resource information, such as available resource information, of the data center corresponding to other VIMs except the source VIM.
And the coordinator further determines that the resource requirements of the virtual machines to be migrated can be met respectively according to the resource information of the data centers corresponding to the other VIMs and the resource requirements of the virtual machines to be migrated, and at least one VIM which meets the VNF-level resource deployment strategy and the NS-level resource deployment strategy is at least one candidate VIM of the virtual machine to be migrated. If there is no VIM that can meet the virtual resource requirement of the virtual machine to be migrated, the coordinator needs to return a migration rejection message including a rejection reason value to the source VIM.
Step 506, the source VIM sends a weight request message to at least one candidate VIM, where the weight request message includes the resource requirement of the virtual machine to be migrated.
The source VIM may generate, through a pre-configured transmission interface between the source VIM and another VIM, a weight request message including the resource requirement of the virtual machine to be migrated and the resource deployment policy corresponding to the virtual machine to be migrated according to the resource requirement of the virtual machine to be migrated and the resource deployment policy corresponding to the virtual machine to be migrated, and send the weight request message to the at least one candidate VIM.
In step 507, the at least one candidate VIM obtains a corresponding receiving weight according to the resource requirement of the virtual machine to be migrated and the physical resource information of the at least one candidate VIM, respectively.
Step 508, the at least one candidate VIM sends a weight request response message to the coordinator, respectively, where the weight request response message includes: a receive weight for each candidate VIM.
In step 509, the coordinator determines the VIM with the largest receiving weight as the destination VIM of the virtual machine to be migrated according to the receiving weight of each candidate VIM.
Step 510, the coordinator sends a migration indication message to the source VIM, where the migration indication message includes the ID of the virtual machine to be migrated and the ID of the destination VIM of the virtual machine to be migrated.
Step 511, the source VIM migrates the virtual machine to be migrated to the physical machine managed by the destination VIM of the virtual machine to be migrated.
It should be noted that, in the embodiment of the present invention, after the migration of the virtual machine to be migrated is completed, the source VIM further sends a migration notification message to the coordinator, where the migration notification message may include information of virtual resources after the source VIM migrates out of the virtual machine to be migrated, and information of virtual resources after the destination VIM migrates into the virtual machine to be migrated. After receiving the migration notification message, the coordinator may further perform resource update on the infrastructure resource directory according to the virtual resource information after the source VIM is migrated out of the virtual machine to be migrated and the virtual resource information after the destination VIM is migrated into the virtual machine to be migrated, and also update the location information of the VNFC corresponding to the virtual machine to be migrated in the NFV instance (Instances) record table.
In the virtual machine migration method provided by the embodiment of the present invention, because the source VIM may determine the virtual machine to be migrated according to the acquired resource usage information of each physical machine and the resource threshold of the physical machine, and then send a migration request message to the coordinator to trigger migration of the virtual machine to be migrated, and the coordinator may also determine the destination VIM according to the receiving weight determined by the at least one candidate VIM, resource allocation between data centers corresponding to different VIMs managed by the coordinator may be more reasonable, resource optimization between data centers managed by the coordinator may be better achieved, and energy consumption of the data centers may be reduced.
The embodiment of the invention also provides the VIM. The VIM provided by the embodiment of the present invention can be used to implement any of the virtual machine migration methods described in the above embodiments. Fig. 6 is a schematic structural diagram of a VIM according to an embodiment of the present invention. VIM600 is the source VIM.
As shown in fig. 6, VIM600 includes: an acquisition module 601, a determination module 602, a sending module 603, a receiving module 604, and a migration module 605.
The obtaining module 601 is configured to obtain resource usage information of each physical machine managed by the source VIM.
A determining module 602, configured to determine, according to the resource usage information of each physical machine and a preset resource threshold of the physical machine, a physical machine in an idle state, and determine a virtual machine on the physical machine in the idle state as a virtual machine to be migrated.
A sending module 603, configured to send a migration request message to a coordinator managing the source VIM, where the migration request message includes: the ID of the virtual machine to be migrated and the ID of the source VIM.
A receiving module 604, configured to receive a migration indication message sent by the coordinator, where the migration indication message includes: and the ID of the destination VIM of the virtual machine to be migrated.
The migration module 605 is configured to migrate the virtual machine to be migrated to the physical machine managed by the destination VIM of the virtual machine to be migrated according to the ID of the virtual machine to be migrated and the ID of the destination VIM of the virtual machine to be migrated.
Optionally, the obtaining module 604 is further configured to obtain the resource threshold of the physical machine before the determining module 602 determines the virtual machine to be migrated according to the resource usage information of each physical machine and the preset resource threshold of the physical machine.
Optionally, the resource threshold of the physical machine may include: a resource usage threshold, or a resource idle threshold.
A determining module 602, configured to determine, according to the resource usage information of each physical machine and the resource usage threshold, that the physical machine whose resource usage information is smaller than the resource usage threshold is the idle physical machine; or, the resource idle information determining unit is configured to determine the resource idle information of each physical machine according to the resource usage information of each physical machine, and determine, according to the resource idle information of each physical machine and the resource idle threshold, that the physical machine whose resource idle information is greater than or equal to the resource idle threshold is the physical machine in the idle state.
Optionally, the sending module 603 is further configured to send the migration request message to the coordinator through the VNFM.
Optionally, the ID of the virtual machine to be migrated included in the migration request message includes IDs of at least two virtual machines to be migrated.
The migration indication message includes: the IDs of the at least two virtual machines to be migrated and the ID of the destination VIM of each virtual machine to be migrated.
The migration module is further configured to migrate each virtual machine to be migrated to a physical machine managed by the destination VIM of each virtual machine to be migrated according to the IDs of the at least two virtual machines to be migrated and the ID of the destination VIM of each virtual machine to be migrated.
The VIM provided by the embodiment of the present invention can be used to implement the virtual machine migration method described in the above embodiment, and the specific implementation process and beneficial effects thereof are similar to those of the above embodiment, and are not described herein again.
The embodiment of the invention also provides a coordinator. The coordinator provided in the embodiment of the present invention may be used to implement any virtual machine migration method described in the above embodiments. Fig. 7 is a schematic structural diagram of a coordinator according to an embodiment of the present invention. As shown in fig. 7, the coordinator 700 may be an NFVO. The coordinator 700 includes: a receiving module 701, a determining module 702 and a sending module 703.
The receiving module 701 is configured to receive a migration request message sent by a source VIM; the migration request message includes: and the ID of the virtual machine to be migrated and the ID of the source VIM.
The at least one virtual machine to be migrated is determined by the source VIM according to the acquired resource use information of each physical machine managed by the source VIM and a preset physical machine resource threshold.
A determining module 702, configured to determine a destination VIM for the virtual machine to be migrated according to the ID of the virtual machine to be migrated and the ID of the source VIM.
A sending module 703, configured to send a migration indication message to the source VIM, where the migration indication message includes: and the ID of the destination VIM of the virtual machine to be migrated.
The migration indication message is used to indicate the source VIM to migrate the virtual machine to be migrated to the physical machine managed by the destination VIM of the virtual machine to be migrated.
Optionally, the sending module 703 is further configured to send the resource threshold of the physical machine to the source VIM before the receiving module 701 receives the migration request message sent by the source VIM.
Optionally, the receiving module 701 is further configured to receive the migration request message sent by the source VIM through the VNFM.
Optionally, the determining module 702 is further configured to determine, according to the ID of the virtual machine to be migrated and the ID of the source VIM, the resource requirement of the virtual machine to be migrated and the virtual resource information of each VIM, other than the source VIM, managed by the coordinator, determine, according to the resource requirement of the virtual machine to be migrated and the virtual resource information of each VIM, other than the source VIM, at least one candidate VIM for the virtual machine to be migrated, and determine, according to the receiving weight of the at least one candidate VIM, the VIM with the largest receiving weight as the destination VIM of the virtual machine to be migrated. And the receiving weight of the at least one candidate VIM is respectively used for representing the receiving requirement of the physical machine managed by the at least one VIM on the virtual machine to be migrated.
Optionally, the sending module 703 is further configured to send a weight request message to each candidate VIM before the determining module 702 determines, according to the receiving weight of each candidate VIM of the at least one candidate VIM, that the VIM with the largest receiving weight is the destination VIM of the virtual machine to be migrated; the weight request message includes: the resource requirement of the virtual machine to be migrated.
The receiving module 701 is further configured to receive a weight request response message sent by each candidate VIM, where the weight request response message includes: a receive weight for each candidate VIM; the receive weight for each candidate VIM includes: and each candidate VIM is obtained according to the resource requirement of the virtual machine to be migrated and the resource information of the physical machine managed by each candidate VIM.
Optionally, the IDs of the virtual machines to be migrated included in the migration request message include IDs of at least two virtual machines to be migrated.
A determining module 702, further configured to determine a destination VIM for each virtual machine to be migrated according to the IDs of the at least two virtual machines to be migrated and the ID of the source VIM, respectively; the migration indication message includes: the IDs of the at least two virtual machines to be migrated and the ID of the destination VIM of each virtual machine to be migrated.
The coordinator provided in the embodiment of the present invention may be used to implement any virtual machine migration method described in the above embodiments, and the specific implementation process and beneficial effects thereof are similar to those in the above embodiments, and are not described herein again.
Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.

Claims (22)

1. A virtual machine migration method is characterized by comprising the following steps:
a source virtual facility manager VIM acquires resource use information of each physical machine managed by the source VIM;
the source VIM determines a physical machine in an idle state according to the resource use information of each physical machine and a preset resource threshold of the physical machine, and determines a virtual machine on the physical machine in the idle state as a virtual machine to be migrated;
the source VIM sends a migration request message to a coordinator managing the source VIM, wherein the migration request message comprises: the identification ID of the virtual machine to be migrated and the ID of the source VIM;
the source VIM receives a migration indication message sent by the coordinator, wherein the migration indication message comprises: the ID of the target VIM of the virtual machine to be migrated;
and the source VIM migrates the virtual machine to be migrated to a physical machine managed by the destination VIM of the virtual machine to be migrated according to the ID of the virtual machine to be migrated and the ID of the destination VIM of the virtual machine to be migrated.
2. The method of claim 1, wherein the source VIM determines that the physical machine in the idle state is ahead of the physical machine according to the resource usage information of the physical machines and a preset resource threshold of the physical machine, and further comprising:
and the source VIM acquires a preset resource threshold value of the physical machine.
3. The method of claim 2, wherein the resource threshold of the physical machine comprises: a resource usage threshold or a resource idleness threshold;
the source VIM determines the physical machine in an idle state according to the resource usage information of each physical machine and a preset resource threshold of the physical machine, and the method comprises the following steps:
the source VIM determines the physical machine with the resource use information smaller than the resource use threshold value as the idle physical machine according to the resource use information of each physical machine and the resource use threshold value; or,
and the source VIM determines the resource idle information of each physical machine according to the resource use information of each physical machine, and determines the physical machine with the resource idle information being greater than or equal to the resource idle threshold value as the idle-state physical machine according to the resource idle information of each physical machine and the resource idle threshold value.
4. The method of any of claims 1-3, wherein sending a migration request message from the source VIM to a coordinator comprises:
and the source VIM sends the migration request message to the coordinator through a virtual network element manager (VNFM).
5. The method according to any one of claims 1 to 4, wherein the ID of the virtual machine to be migrated included in the migration request message includes IDs of at least two virtual machines to be migrated;
the migration indication message includes: the IDs of the at least two virtual machines to be migrated and the ID of the destination VIM of each virtual machine to be migrated;
the migrating the virtual machine to be migrated to the physical machine managed by the destination VIM of the virtual machine to be migrated by the source VIM according to the ID of the virtual machine to be migrated and the ID of the destination VIM of the virtual machine to be migrated, and the migrating comprises the following steps:
and the source VIM migrates each virtual machine to be migrated to a physical machine managed by the destination VIM of each virtual machine to be migrated according to the IDs of the at least two virtual machines to be migrated and the ID of the destination VIM of each virtual machine to be migrated.
6. A virtual machine migration method is characterized by comprising the following steps:
the coordinator receives a migration request message sent by a source VIM; the migration request message includes: the ID of the virtual machine to be migrated and the ID of the source VIM are obtained;
the coordinator determines a target VIM for the virtual machine to be migrated according to the ID of the virtual machine to be migrated and the ID of the source VIM;
the coordinator sends a migration indication message to the source VIM, wherein the migration indication message comprises: the ID of the target VIM of the virtual machine to be migrated; the migration indication message is used for indicating the source VIM to migrate the virtual machine to be migrated to the physical machine managed by the destination VIM of the virtual machine to be migrated.
7. The method of claim 6, wherein before the coordinator receives the migration request message sent by the source VIM, the method further comprises:
the coordinator sends the resource threshold of the physical machine to the source VIM.
8. The method of claim 6 or 7, wherein the coordinator receiving the migration request message sent by the source VIM comprises:
the coordinator receives the migration request message sent by the source VIM through the VNFM.
9. The method according to any of claims 6-8, wherein the coordinator determines a destination VIM for the virtual machine to be migrated according to the ID of the virtual machine to be migrated and the ID of the source VIM, and comprises:
the coordinator determines the resource requirement of the virtual machine to be migrated and the virtual resource information of each VIM except the source VIM managed by the coordinator according to the ID of the virtual machine to be migrated and the ID of the source VIM;
the coordinator determines at least one candidate VIM for the virtual machine to be migrated according to the resource requirement of the virtual machine to be migrated and the virtual resource information of each other VIM except the source VIM;
the coordinator determines the VIM with the maximum receiving weight as the target VIM of the virtual machine to be migrated according to the receiving weight of each candidate VIM of the at least one candidate VIM; and the receiving weight of each candidate VIM represents the receiving requirement of the physical machine managed by each candidate VIM on the virtual machine to be migrated.
10. The method of claim 9, wherein the coordinator determines, according to the reception weight of each candidate VIM of the at least one candidate VIM, that the VIM with the largest reception weight is the destination VIM of the virtual machine to be migrated, and further comprising:
the coordinator sends a weight request message to each candidate VIM respectively; the weight request message includes: the resource requirement of the virtual machine to be migrated;
the coordinator receives a weight request response message sent by each candidate VIM, wherein the weight request response message comprises: a receive weight for each of the candidate VIMs; the receive weight for each candidate VIM comprises: and each candidate VIM is obtained according to the resource requirement of the virtual machine to be migrated and the resource information of the physical machine managed by each candidate VIM.
11. The method according to any one of claims 6 to 10, wherein the IDs of the virtual machines to be migrated included in the migration request message include IDs of at least two virtual machines to be migrated;
the determining, by the coordinator, a destination VIM for the virtual machine to be migrated according to the ID of the virtual machine to be migrated and the ID of the source VIM includes:
the coordinator determines a destination VIM for each virtual machine to be migrated according to the IDs of the at least two virtual machines to be migrated and the ID of the source VIM; the migration indication message includes: the IDs of the at least two virtual machines to be migrated and the ID of the destination VIM of each virtual machine to be migrated.
12. A VIM that is a source VIM, comprising:
the acquisition module is used for acquiring resource use information of each physical machine managed by the source VIM;
the determining module is used for determining the physical machine in an idle state according to the resource use information of each physical machine and a preset resource threshold of the physical machine, and determining the virtual machine on the physical machine in the idle state as a virtual machine to be migrated;
a sending module, configured to send a migration request message to a coordinator managing the source VIM, where the migration request message includes: the ID of the virtual machine to be migrated and the ID of the source VIM;
a receiving module, configured to receive a migration indication message sent by the coordinator, where the migration indication message includes: the ID of the target VIM of the virtual machine to be migrated;
and the migration module is used for migrating the virtual machine to be migrated to a physical machine managed by the destination VIM of the virtual machine to be migrated according to the ID of the virtual machine to be migrated and the ID of the destination VIM of the virtual machine to be migrated.
13. The VIM of claim 12,
the obtaining module is further configured to obtain the resource threshold of the physical machine before the determining module determines the virtual machine to be migrated according to the resource usage information of each physical machine and a preset resource threshold of the physical machine.
14. The VIM of claim 13, wherein the resource thresholds for the physical machines comprise: a resource usage threshold or a resource idleness threshold;
the determining module is further configured to determine, according to the resource usage information of each physical machine and the resource usage threshold, that the physical machine with the resource usage information smaller than the resource usage threshold is the idle physical machine; or, the resource idle information of each physical machine is determined according to the resource usage information of each physical machine, and the physical machine with the resource idle information greater than or equal to the resource idle threshold is determined to be the physical machine in the idle state according to the resource idle information of each physical machine and the resource idle threshold.
15. The VIM of any one of claims 12-14,
the sending module is further configured to send the migration request message to the coordinator through the VNFM.
16. The VIM of any of claims 12-15, wherein the IDs of the virtual machines to be migrated that the migration request message includes IDs of at least two virtual machines to be migrated;
the migration indication message includes: the IDs of the at least two virtual machines to be migrated and the ID of the destination VIM of each virtual machine to be migrated;
the migration module is further configured to migrate each virtual machine to be migrated to a physical machine managed by the destination VIM of each virtual machine to be migrated according to the IDs of the at least two virtual machines to be migrated and the ID of the destination VIM of each virtual machine to be migrated.
17. A coordinator, comprising:
the receiving module is used for receiving a migration request message sent by a source VIM; the migration request message includes: the ID of the virtual machine to be migrated and the ID of the source VIM are obtained;
the determining module is used for determining a destination VIM for the virtual machine to be migrated according to the ID of the virtual machine to be migrated and the ID of the source VIM;
a sending module, configured to send a migration indication message to the source VIM, where the migration indication message includes: the ID of the target VIM of the virtual machine to be migrated; the migration indication message is used for indicating the source VIM to migrate the virtual machine to be migrated to the physical machine managed by the destination VIM of the virtual machine to be migrated.
18. The coordinator according to claim 17,
the sending module is further configured to send a resource threshold of a physical machine to the source VIM before the receiving module receives the migration request message sent by the source VIM.
19. Coordinator according to claim 17 or 18,
the receiving module is further configured to receive the migration request message sent by the source VIM through the VNFM.
20. Coordinator according to any one of claims 17-19,
the determining module is further configured to determine, according to the ID of the virtual machine to be migrated and the ID of the source VIM, the resource requirement of the virtual machine to be migrated and the virtual resource information of each VIM, other than the source VIM, managed by the coordinator, determine, according to the resource requirement of the virtual machine to be migrated and the virtual resource information of each VIM, other than the source VIM, at least one candidate VIM for the virtual machine to be migrated, and determine, according to the receiving weight of each candidate VIM of the at least one candidate VIM, the VIM with the largest receiving weight as the destination VIM of the virtual machine to be migrated; the receiving weight of each candidate VIM is used for representing the receiving requirement of the physical machine managed by each candidate VIM on the virtual machine to be migrated.
21. The coordinator according to claim 20,
the sending module is further configured to send a weight request message to each candidate VIM before the determining module determines, according to the receiving weight of each candidate VIM of the at least one candidate VIM, that the VIM with the largest receiving weight is the target VIM of the virtual machine to be migrated; the weight request message includes: the resource requirement of the virtual machine to be migrated;
the receiving module is further configured to receive a weight request response message sent by each candidate VIM, where the weight request response message includes: a receive weight for each of the candidate VIMs; the receive weight for each candidate VIM comprises: and each candidate VIM is obtained according to the resource requirement of the virtual machine to be migrated and the resource information of the physical machine managed by each candidate VIM.
22. The coordinator according to any one of claims 17 to 21, wherein the IDs of the virtual machines to be migrated included in the migration request message include IDs of at least two virtual machines to be migrated;
the determining module is further configured to determine a destination VIM for each virtual machine to be migrated according to the IDs of the at least two virtual machines to be migrated and the ID of the source VIM; the migration indication message includes: the IDs of the at least two virtual machines to be migrated and the ID of the destination VIM of each virtual machine to be migrated.
CN201410673544.4A 2014-11-21 2014-11-21 Virtual machine migration method, virtual facility manager and coordinator Active CN105677441B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201410673544.4A CN105677441B (en) 2014-11-21 2014-11-21 Virtual machine migration method, virtual facility manager and coordinator
PCT/CN2015/080670 WO2016078391A1 (en) 2014-11-21 2015-06-03 Virtual machine migration method, virtualized infrastructure manger and coordinator

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201410673544.4A CN105677441B (en) 2014-11-21 2014-11-21 Virtual machine migration method, virtual facility manager and coordinator

Publications (2)

Publication Number Publication Date
CN105677441A true CN105677441A (en) 2016-06-15
CN105677441B CN105677441B (en) 2019-07-09

Family

ID=56013224

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201410673544.4A Active CN105677441B (en) 2014-11-21 2014-11-21 Virtual machine migration method, virtual facility manager and coordinator

Country Status (2)

Country Link
CN (1) CN105677441B (en)
WO (1) WO2016078391A1 (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106230623A (en) * 2016-07-22 2016-12-14 中国联合网络通信集团有限公司 A kind of VIM site selection method and device
CN108804210A (en) * 2018-04-23 2018-11-13 北京奇艺世纪科技有限公司 A kind of resource allocation method and device of cloud platform
WO2018205079A1 (en) * 2017-05-08 2018-11-15 华为技术有限公司 Method and device for use in transferring control right of network device
CN108958889A (en) * 2018-07-12 2018-12-07 郑州云海信息技术有限公司 The management method and device of virtual machine in cloud data system
CN109189553A (en) * 2018-08-17 2019-01-11 烽火通信科技股份有限公司 Network service and virtual resource multiple target matching process and system
CN109960564A (en) * 2017-12-22 2019-07-02 上海盛霄云计算技术有限公司 A kind of method of virtual machine (vm) migration

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109408230B (en) * 2018-10-10 2021-07-20 中国科学院计算技术研究所 Docker container deployment method and system based on energy consumption optimization
CN113645078B (en) * 2021-08-16 2023-10-27 烽火通信科技股份有限公司 Method and system for automatically extending network management service

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104010028A (en) * 2014-05-04 2014-08-27 华南理工大学 Dynamic virtual resource management strategy method for performance weighting under cloud platform
CN104102523A (en) * 2013-04-03 2014-10-15 华为技术有限公司 Method for migrating virtual machine and resource scheduling platform
US20140317621A1 (en) * 2006-02-28 2014-10-23 Microsoft Corporation Migrating a virtual machine that owns a resource such as a hardware device

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140317621A1 (en) * 2006-02-28 2014-10-23 Microsoft Corporation Migrating a virtual machine that owns a resource such as a hardware device
CN104102523A (en) * 2013-04-03 2014-10-15 华为技术有限公司 Method for migrating virtual machine and resource scheduling platform
CN104010028A (en) * 2014-05-04 2014-08-27 华南理工大学 Dynamic virtual resource management strategy method for performance weighting under cloud platform

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106230623A (en) * 2016-07-22 2016-12-14 中国联合网络通信集团有限公司 A kind of VIM site selection method and device
CN106230623B (en) * 2016-07-22 2019-03-15 中国联合网络通信集团有限公司 A kind of VIM site selection method and device
WO2018205079A1 (en) * 2017-05-08 2018-11-15 华为技术有限公司 Method and device for use in transferring control right of network device
CN109219941A (en) * 2017-05-08 2019-01-15 华为技术有限公司 Network equipment control right transfer method and apparatus
CN109960564A (en) * 2017-12-22 2019-07-02 上海盛霄云计算技术有限公司 A kind of method of virtual machine (vm) migration
CN108804210A (en) * 2018-04-23 2018-11-13 北京奇艺世纪科技有限公司 A kind of resource allocation method and device of cloud platform
CN108958889A (en) * 2018-07-12 2018-12-07 郑州云海信息技术有限公司 The management method and device of virtual machine in cloud data system
CN109189553A (en) * 2018-08-17 2019-01-11 烽火通信科技股份有限公司 Network service and virtual resource multiple target matching process and system

Also Published As

Publication number Publication date
CN105677441B (en) 2019-07-09
WO2016078391A1 (en) 2016-05-26

Similar Documents

Publication Publication Date Title
CN105677441B (en) Virtual machine migration method, virtual facility manager and coordinator
EP3606008B1 (en) Method and device for realizing resource scheduling
CN105376083B (en) Energy-saving control method, management server and the network equipment
US10133606B2 (en) Application scaling management method and apparatus that uses distances between data centers and network resources of data centers to select a data center for expansion
US10764132B2 (en) Scale-out association method and apparatus, and system
CN106161076B (en) Virtual network function extended method and device
CN105429776B (en) Method and system for managing functions of virtual network
CN106462450A (en) Notification about virtual machine live migration to VNF manager
CN106302074B (en) Migration method and device of virtual network function VNF
CN103227838B (en) A kind of multi-load equilibrium treatment apparatus and method
EP3289456A1 (en) Balancing resources in distributed computing environments
CN107005452B (en) Network function virtualization resource processing method and virtual network function manager
CN106663012B (en) Hardware acceleration method and related equipment
CN108132827B (en) Network slice resource mapping method, related equipment and system
US20160164828A1 (en) Adjusting virtual machine resources
US10761869B2 (en) Cloud platform construction method and cloud platform storing image files in storage backend cluster according to image file type
CN106685784A (en) Virtualized network function VNF instance scaling method and VNF instance scaling device
JP2018531549A6 (en) Network function virtualization resource processing method and virtualized network function manager
US9960961B2 (en) Methods and apparatus for radio access network resource management
CN106790354B (en) Communication method and device for preventing data congestion
WO2018192475A1 (en) Method and apparatus for adjusting virtual machine specifications
WO2018196651A1 (en) Resource management method and device
CN103973811A (en) High-availability cluster management method capable of conducting dynamic migration
CN106685683A (en) Management indication transmitting and VNF automatic telescoping function management method and device
CN107615872A (en) A kind of method, apparatus and system for discharging connection

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant