CN108268300B - Virtual machine migration method and device - Google Patents
Virtual machine migration method and device Download PDFInfo
- Publication number
- CN108268300B CN108268300B CN201611257196.8A CN201611257196A CN108268300B CN 108268300 B CN108268300 B CN 108268300B CN 201611257196 A CN201611257196 A CN 201611257196A CN 108268300 B CN108268300 B CN 108268300B
- Authority
- CN
- China
- Prior art keywords
- virtual machine
- address
- virtual
- actual
- list
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/4557—Distribution of virtual machine instances; Migration and load balancing
Abstract
The invention discloses a virtual machine migration method, which comprises the following steps: acquiring a first virtual machine list, wherein the first virtual machine list comprises Internet Protocol (IP) addresses of virtual machines in a target subnet; screening a second virtual machine list from the first virtual machine list according to the IP address, wherein the second virtual machine list comprises all virtual machines which are not obtained the actual IP address in the first virtual machine list; allocating a logic IP address to the virtual machine in the second virtual machine list, wherein the logic IP address is an IP address in the target subnet different from the actual IP address in the first virtual machine list; establishing virtual network server resources for the virtual machines in the second virtual machine list according to the distributed logic IP addresses; and when the actual IP address of the virtual machine in the second virtual machine list is analyzed, replacing the logic IP address of the corresponding virtual machine in the virtual network server with the actual IP address. The invention also discloses a virtual machine migration device.
Description
Technical Field
The invention relates to the field of cloud computing, in particular to a virtual machine migration method and device.
Background
Virtualization technology of a virtualization platform VMware enables a user to confidently virtualize any application, redefine availability and simplify a virtual data center, and finally can realize a highly available and high-recovery on-demand infrastructure. The virtual product vCenter Server can provide uniform management for the whole virtual infrastructure, and can realize the functions of a plurality of key virtual platforms vSphere such as real-time migration. Moreover, the vCenter Server can manage thousands of virtual machines distributed in multiple locations, and the management process is simplified by using rapid deployment and automation strategies.
In order to provide flexible and scalable cloud computing for public or private clouds of virtual computing or storage services, a platform for managing the cloud is required, and a virtual network server (OpenStack) provides such a platform. In general, a virtualization technology KVM is used for a computing node of an OpenStack, and in order to implement uniform resource management, other virtualized resources need to be migrated to a management platform of the OpenStack, and if migration is completed, the resources can be uniformly managed through the management platform of the OpenStack. However, migration of a virtual machine is not easy, and a large number of practical experiences show that successful migration needs to satisfy multiple conditions that information of the virtual machine is completely acquired, and the information of the virtual machine meets the requirements of OpenStack. However, when a virtual machine migrates, the problem of incomplete information often exists in acquiring network information of the virtual machine, for example, under a virtualization platform VMware, only if the virtual machine is in a boot state and virtual machine Tools VMware Tools, which have installed programs for providing IP address information of the virtual machine, can acquire the IP address information of the virtual machine through an Application Programming Interface (API).
Due to the difference of design ideas of different designers, under the management platform of OpenStack, network information of a virtual machine follows strict distribution and management use rules. According to the requirements of OpenStack, the IP address, the network mask, the affiliated network and the subnet information of a virtual network card used by a virtual machine are required to be clear; in other virtualization platforms, the network information of the virtual machine can be manually configured by a user, is not limited by the network to which the user belongs, and has no corresponding IP address allocation record, so that the information integrity of the virtual machine cannot be ensured. Therefore, when the virtual machine is migrated, corresponding information of the virtual machine needs to be supplemented manually, which goes against automatic migration, and the migration of the virtual machine is extraordinarily time-consuming and labor-consuming as the number of migrated virtual machines increases continuously without the principle of human intervention. Fig. 1 is a schematic flow diagram of migration of a VMware virtual machine to OpenStack, and referring to fig. 1, the migration flow of the virtual machine includes: data acquisition of the VMware of the virtualization platform, data information completion of the VMware of the virtualization platform and the process of creating OpenStack resources.
A prior patent application No. CN201510589171.7 entitled "a virtual machine migration method and apparatus" describes a virtual machine migration method, which includes: firstly, a computing node configures drive (Driver) information of a host where a virtual machine to be migrated to the computing node is located, and IP (Internet protocol) address or cluster information of the host in a resource configuration file; then, acquiring configuration information of the virtual machine; establishing a network used by the virtual machine and characteristic information of the virtual machine according to the acquired configuration information; and finally, generating an identifier UUID for the virtual machine to be created, and renaming the name of the virtual machine in the virtualization management software by using the identifier UUID, so that the virtual machine is migrated to Openstack for management. Based on the same inventive concept, the prior patent also provides a migration device of a virtual machine, which can migrate the virtual machine to OpenStack for management without changing the existing virtualization environment.
Although the above patent describes a migration method of a virtual machine, the method does not describe the configuration information of the virtual machine obtained in the migration process in detail, but assumes that the network configuration information of the virtual machine can be normally obtained under ideal conditions. In practical application, if a virtual machine tool VMware Tools is not installed on the virtual machine or the virtual machine is in a shutdown state, a Simple Object Access Protocol (SOAP) API of the VMware of the virtualization platform cannot acquire IP address information of the virtual machine, so that the virtual machine cannot be migrated to the management platform of the OpenStack due to the fact that the virtual machine lacks the IP address information in the process of migrating the virtual machine to the OpenStack. Further, each network of the OpenStack provides an available IP address resource, and in the process of migrating a virtual machine from a virtualized platform Vmware environment to an OpenStack, if the IP address information of the virtualized platform Vmware is not obtained, the OpenStack cannot allocate an IP address to the virtual machine, thereby affecting the creation of the virtual machine.
Therefore, in order to solve the problem that the virtual machine cannot be migrated to the management platform of the OpenStack due to the fact that the virtual machine lacks IP address information, a migration scheme of the virtual machine needs to be found urgently.
Disclosure of Invention
In order to solve the existing problems, embodiments of the present invention desirably provide a method and an apparatus for migrating a virtual machine, which can migrate the virtual machine to a management platform of an OpenStack when the virtual machine lacks IP address information, so as to improve a migration success rate.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
the embodiment of the invention provides a virtual machine migration method, which comprises the following steps:
acquiring a first virtual machine list, wherein the first virtual machine list comprises Internet Protocol (IP) addresses of virtual machines in a target subnet;
screening a second virtual machine list from the first virtual machine list according to the IP address, wherein the second virtual machine list comprises all virtual machines which are not obtained the actual IP address in the first virtual machine list;
allocating a logic IP address to the virtual machine in the second virtual machine list, wherein the logic IP address is an IP address in the target subnet different from the actual IP address in the first virtual machine list;
establishing virtual network server resources for the virtual machines in the second virtual machine list according to the distributed logic IP addresses;
and when the actual IP address of the virtual machine in the second virtual machine list is analyzed, replacing the logic IP address of the corresponding virtual machine in the virtual network server with the actual IP address.
In the foregoing solution, after creating a virtual network server resource for a virtual machine in the second virtual machine list according to the allocated logical IP address, the method further includes:
monitoring a first communication message sent by a virtual machine corresponding to an IP address in an IP address pool, wherein the IP address pool is all IP addresses different from an actual IP address in a first virtual machine list in a target subnet;
comparing the MAC address of the virtual machine network card in the first communication message monitored currently with the MAC address of the virtual machine network card in the second virtual machine list;
when the MAC address of the currently monitored virtual machine network card is consistent with the MAC address of the virtual machine network card in the second virtual machine list, determining that the IP address of the virtual machine in the first communication message is the actual IP address of the virtual machine corresponding to the MAC address of the currently monitored virtual machine network card.
In the foregoing solution, before monitoring a first communication packet sent by a virtual machine corresponding to an IP address in the IP address pool, the method further includes:
sending a second communication message to the IP address in the IP address pool;
comparing the MAC address of the virtual machine network card in a currently received third communication message with the MAC address of the virtual machine network card in a second virtual machine list, wherein the third communication message is a message for responding to the second communication message;
when the MAC address of the currently received virtual machine network card is consistent with the MAC address of the virtual machine network card in the second virtual machine list, determining the IP address of the virtual machine in the currently received third communication message as the actual IP address of the virtual machine corresponding to the MAC address of the currently received virtual machine network card;
judging whether the number of virtual machines of which the actual IP addresses are determined in the second virtual machine list is smaller than the number of virtual machines in the second virtual machine list within first preset time;
and when the number of the virtual machines with the actual IP addresses in the second virtual machine list is determined to be smaller than that in the second virtual machine list, monitoring a first communication message sent by the virtual machine corresponding to the IP address in the IP address pool.
In the foregoing solution, before the sending the second communication message to the IP address in the IP address pool, the method further includes:
sending a fourth communication message to the IP address in the IP address pool according to a preset time period;
judging whether the number of the virtual machines responding to the fourth communication message in a second preset time is greater than 0 or not;
if yes, executing a step of sending a second communication message to the IP address in the IP address pool;
and if not, monitoring the first communication message sent by the virtual machine corresponding to the IP address in the IP address pool.
In the foregoing solution, before sending the fourth communication message to the IP address in the IP address pool according to the preset time period, the method further includes:
judging whether the ratio of the number of the virtual machines in the second virtual machine list to the number of the IP addresses in the IP address pool is larger than a preset value or not;
if yes, executing the step of sending a fourth communication message to the IP address in the IP address pool according to a preset time period;
and if not, monitoring the first communication message sent by the virtual machine corresponding to the IP address in the IP address pool.
In the foregoing solution, before replacing the logical IP address of the corresponding virtual machine in the virtual network server with the actual IP address, the method further includes:
judging whether the analyzed actual IP address is consistent with a logic IP address of a first target virtual machine, wherein the first target virtual machine is a virtual machine which is different from the actual IP address and corresponds to the actual IP address in a second virtual machine list;
if so, reallocating a new logic IP address to a second target virtual machine, wherein the second target virtual machine is a virtual machine corresponding to a logic IP address consistent with the actual IP address in the first target virtual machine;
and if not, executing the step of replacing the logic IP address of the corresponding virtual machine in the virtual network server with the actual IP address.
An embodiment of the present invention further provides a migration apparatus for a virtual machine, where the apparatus includes: the system comprises an acquisition module, a screening module, a distribution module, a creation module and an updating module; wherein the content of the first and second substances,
the acquiring module is used for acquiring a first virtual machine list, wherein the first virtual machine list comprises IP addresses of virtual machines in a target subnet;
the screening module is used for screening a second virtual machine list from the first virtual machine list according to the IP address, wherein the second virtual machine list comprises all virtual machines which are not obtained the actual IP address in the first virtual machine list;
the allocating module is configured to allocate a logical IP address to the virtual machine in the second virtual machine list, where the logical IP address is an IP address in the target subnet that is different from the actual IP address in the first virtual machine list;
the creating module is used for creating virtual network server resources for the virtual machines in the second virtual machine list according to the allocated logic IP addresses;
and the updating module is used for replacing the logic IP address of the corresponding virtual machine in the virtual network server with the actual IP address when the actual IP address of the virtual machine in the second virtual machine list is analyzed.
In the above scheme, the apparatus further comprises: an IP address resolution module; wherein the content of the first and second substances,
the IP address resolution module comprises: the device comprises a monitoring unit, a first comparison unit and a first determination unit; wherein the content of the first and second substances,
the monitoring unit is used for monitoring a first communication message sent by a virtual machine corresponding to an IP address in an IP address pool, wherein the IP address pool is all IP addresses different from an actual IP address in the first virtual machine list in a target subnet;
the first comparison unit is used for comparing the MAC address of the virtual machine network card in the first communication message monitored currently with the MAC address of the virtual machine network card in the second virtual machine list;
the first determining unit is configured to determine that the IP address of the virtual machine in the first communication packet is the actual IP address of the virtual machine corresponding to the currently monitored MAC address of the virtual machine network card when the currently monitored MAC address of the virtual machine network card is consistent with the MAC address of the virtual machine network card in the second virtual machine list.
In the foregoing solution, the IP address resolution module further includes: the device comprises a first sending unit, a second comparing unit, a second determining unit and a first judging unit; wherein the content of the first and second substances,
the first sending unit is configured to send a second communication packet to the IP address in the IP address pool;
the second comparison unit is configured to compare an MAC address of the virtual machine network card in a currently received third communication message with an MAC address of the virtual machine network card in a second virtual machine list, where the third communication message is a message that responds to the second communication message;
the second determining unit is configured to determine, when the MAC address of the currently received virtual machine network card is consistent with the MAC address of the virtual machine network card in the second virtual machine list, the IP address of the virtual machine in the currently received third communication message as the actual IP address of the virtual machine corresponding to the MAC address of the currently received virtual machine network card;
the first judging unit is used for judging whether the number of the virtual machines of which the actual IP addresses are determined in the second virtual machine list is smaller than that in the second virtual machine list within a first preset time; and when the number of the virtual machines with the determined actual IP addresses in the second virtual machine list is less than that in the second virtual machine list, triggering the monitoring unit.
In the foregoing solution, the IP address resolution module further includes: a second transmitting unit and a second judging unit; wherein the content of the first and second substances,
the second sending unit is configured to send a fourth communication packet to the IP address in the IP address pool according to a preset time period;
the second judging unit is configured to judge whether the number of virtual machines responding to the fourth communication message within a second preset time is greater than 0; if yes, triggering the first sending unit; if not, triggering the monitoring unit.
In the foregoing solution, the IP address resolution module further includes:
a third judging unit, configured to judge whether a ratio of the number of virtual machines in the second virtual machine list to the number of IP addresses in the IP address pool is greater than a preset value; if yes, triggering the second sending unit; if not, triggering the monitoring unit.
In the above scheme, the apparatus further comprises:
the judging module is used for judging whether the analyzed actual IP address is consistent with a logic IP address of a first target virtual machine, wherein the first target virtual machine is a virtual machine which is different from the virtual machine corresponding to the actual IP address in a second virtual machine list; if so, reallocating a new logic IP address to a second target virtual machine, wherein the second target virtual machine is a virtual machine corresponding to a logic IP address consistent with the actual IP address in the first target virtual machine; if not, the updating module is triggered.
The migration method and device of the virtual machine provided by the embodiment of the invention comprises the steps of firstly obtaining a first virtual machine list, wherein the first virtual machine list comprises an Internet Protocol (IP) address of the virtual machine in a target subnet; screening a second virtual machine list from the first virtual machine list according to the IP address, wherein the second virtual machine list comprises all virtual machines which are not obtained the actual IP address in the first virtual machine list; allocating a logic IP address to the virtual machine in the second virtual machine list, wherein the logic IP address is an IP address in the target subnet different from the actual IP address in the first virtual machine list; establishing virtual network server resources for the virtual machines in the second virtual machine list according to the distributed logic IP addresses; and when the actual IP address of the virtual machine in the second virtual machine list is analyzed, replacing the logic IP address of the corresponding virtual machine in the virtual network server with the actual IP address.
Therefore, the embodiment of the invention allocates an effective logical IP address to the virtual machine which lacks IP address information, and migrates the virtual machine into OpenStack according to the logical IP address; when the actual IP address of the virtual machine is analyzed, the logic IP address of the corresponding virtual machine in the OpenStack is replaced by the actual IP address, so that the virtual machine can be migrated to the management platform of the OpenStack under the condition that the virtual machine lacks IP address information, and the migration success rate is improved.
Drawings
FIG. 1 is a schematic flow chart of migration of a VMware virtual machine to OpenStack;
fig. 2 is a schematic flow chart illustrating an implementation of a first migration method of a virtual machine according to the present invention;
fig. 3 is a schematic flow chart illustrating a process of resolving an actual IP address of a virtual machine in the second virtual machine list;
FIG. 4 is a diagram illustrating the results of an arping scan;
FIG. 5 is a diagram illustrating a result of monitoring an arp request message;
FIG. 6 is a schematic diagram illustrating a first exemplary embodiment of a virtual machine migration apparatus according to the present invention;
FIG. 7 is a schematic diagram of the structure of the IP address resolution module;
fig. 8 is a schematic diagram of a deployment location of an IP address resolution module in OpenStack.
Detailed Description
The virtual machine migration method provided by the embodiment of the invention is mainly applied to a subnet system, an effective logic IP address is allocated to a virtual machine which lacks IP address information, and the virtual machine is migrated to OpenStack according to the logic IP address; when the actual IP address of the virtual machine is analyzed, the logic IP address of the corresponding virtual machine in the OpenStack is replaced by the actual IP address, so that the virtual machine can be migrated to the management platform of the OpenStack under the condition that the virtual machine lacks IP address information, and the migration success rate is improved.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Fig. 2 is a schematic flow chart of an implementation of a first embodiment of a virtual machine migration method according to the present invention, and referring to fig. 2, the virtual machine migration method according to this embodiment includes the following steps:
the migration method of the virtual machine can be suitable for various virtualization platforms, for example, can be suitable for a virtualization platform VMware, and also can be suitable for a virtualization platform vSphere, and in this embodiment, the virtualization platform VMware can be taken as an example for detailed description; further, the migration method of the virtual machine of the present invention may be applied to a single subnet, and may also be applied to multiple subnets.
Specifically, a Vmware SOAP API is called to obtain a first virtual machine list from OpenStack, and the first virtual machine list comprises the name of a virtual machine, the UUID of the virtual machine, the power state of the virtual machine, the number of virtual processors (vCPU) and the memory size, network information of a virtual machine network card and MAC address information of the virtual machine network card besides the Internet protocol IP address of the virtual machine in a target subnet.
102, screening a second virtual machine list from the first virtual machine list according to the IP address, wherein the second virtual machine list comprises all virtual machines which are not obtained the actual IP address in the first virtual machine list;
whether the IP address information of the virtual machine can be acquired depends on the installation state of VMware Tools of the virtual machine and the current running state of the virtual machine, and if the virtual machine is not provided with the VMware Tools or is in a shutdown state, the IP address information of the virtual machine cannot be acquired by calling a VMware SOAP API; in this embodiment, according to the IP addresses of the virtual machines in the first virtual machine list, a second virtual machine list is screened from the first virtual machine list, where the second virtual machine list includes all virtual machines in the first virtual machine list that have not acquired actual IP addresses.
Specifically, table 1 is a first virtual machine list, and referring to table 1, the first virtual machine list includes information of virtual machines vm1, vm2, vm3, vm4, vm5, and vm6, where IP address information of virtual machines vm3, vm4, vm5, and vm6 is 0.0.0.0, which indicates that the virtual machines lack IP address information and actual IP addresses are not successfully obtained; all information of the virtual machines vm3, vm4, vm5 and vm6 is screened to a second virtual machine list, table 2 is the second virtual machine list, and referring to table 2, all information of the virtual machines vm3, vm4, vm5 and vm6 and the virtual machines in the first virtual machine list are included in the second virtual machine list. In addition, since the information of the virtual machines vm1 and vm2 in the first virtual machine list is complete, OpenStack resources can be created directly for the virtual machines vm1 and vm 2.
TABLE 1 first virtual machine List
TABLE 2 second virtual machine List
103, allocating a logical IP address to the virtual machine in the second virtual machine list, wherein the logical IP address is an IP address in the target subnet different from the actual IP address in the first virtual machine list;
in this step, all IP addresses in the target subnet that are different from the actual IP addresses in the first virtual machine list form an IP address pool, and any IP address in the IP address pool can be used as a logical IP address of a virtual machine in the second virtual machine list, but in order to ensure the uniqueness of logical IP address allocation, the same IP address in the IP address pool cannot be allocated to two virtual machines in the second virtual machine list.
and 105, replacing the logic IP address of the corresponding virtual machine in the virtual network server with the actual IP address when the actual IP address of the virtual machine in the second virtual machine list is resolved.
Here, since the logical IP addresses of the virtual machines in the second virtual list are randomly allocated, when the actual IP addresses of the virtual machines in the second virtual machine list are resolved, the actual IP addresses of the virtual machines may conflict with the logical IP addresses of other virtual machines in the second virtual machine list, and therefore, before replacing the logical IP addresses of the corresponding virtual machines in the OpenStack with the actual IP addresses, it is further necessary to determine whether the resolved actual IP addresses are consistent with the logical IP addresses of a first target virtual machine, where the first target virtual machine is a virtual machine different from the actual IP address in the second virtual machine list; if so, reallocating a new logic IP address to a second target virtual machine, wherein the second target virtual machine is a virtual machine corresponding to a logic IP address consistent with the actual IP address in the first target virtual machine; and if not, replacing the logic IP address of the corresponding virtual machine in the OpenStack with an actual IP address.
After replacing the logical IP address of the corresponding virtual machine in the OpenStack with the actual IP address, an update result may be immediately notified to OpenStack, or may be periodically notified to OpenStack, and one notification may include an update result of IP addresses of a plurality of virtual machines.
Specifically, a first virtual machine list is obtained, and referring to table 1, the first virtual machine list includes IP addresses of virtual machines vm1, vm2, vm3, vm4, vm5, and vm6 in a target subnet;
screening a second virtual machine list from the first virtual machine list according to the IP address, and referring to table 2, wherein the second virtual machine list comprises virtual machines vm3, vm4, vm5 and vm6 which do not acquire an actual IP address in the first virtual machine list;
establishing OpenStack resources for the virtual machines vm1 and vm2 with complete information;
allocating a logic IP address to the virtual machine in the second virtual machine list, wherein the logic IP address is an IP address in an IP address pool;
establishing OpenStack resources for the virtual machines in the second virtual machine list according to the distributed logic IP addresses;
when the actual IP address of the virtual machine in the second virtual machine list is analyzed, judging whether the analyzed actual IP address is consistent with the logic IP address of a first target virtual machine, wherein the first target virtual machine is a virtual machine which is different from the virtual IP address and corresponds to the actual IP address in the second virtual machine list; if so, reallocating a new logic IP address to a second target virtual machine to keep the uniqueness of the logic IP address, wherein the second target virtual machine is a virtual machine corresponding to the logic IP address consistent with the actual IP address in the first target virtual machine; if not, replacing the logic IP address of the corresponding virtual machine in the OpenStack with an actual IP address;
replacing the logic IP address of the corresponding virtual machine in the OpenStack with an actual IP address;
and immediately notifying the update result to OpenStack.
It can be understood that an effective logical IP address is allocated to a virtual machine lacking IP address information, and the virtual machine is migrated to OpenStack according to the logical IP address; when the actual IP address of the virtual machine is resolved, the logical IP address of the corresponding virtual machine in the OpenStack is replaced with the actual IP address, so that the problem that the virtual machine cannot be migrated to the management platform of the OpenStack due to the fact that the virtual machine lacks IP address information can be solved, because: all IP addresses in the target subnet, which are different from the actual IP addresses in the first virtual machine list, form an IP address pool, and the IP addresses in the IP address pool are not really used for the virtual machines, but are effective logical IP addresses for OpenStack; by allocating a logical IP address to the virtual machine which lacks IP address information, OpenStack resources can be created for the virtual machine, and subsequently, when the actual IP address of the virtual machine in the second virtual machine list is analyzed, the logical IP address of the virtual machine corresponding to the OpenStack is replaced by the actual IP address, so that the virtual machine can be migrated to the management platform of the OpenStack under the condition that the virtual machine lacks IP address information, and the migration success rate is improved.
Further, in the second embodiment of the virtual machine migration method according to the present invention, a process of resolving an actual IP address of a virtual machine in the second virtual machine list is described, which is described in detail below with reference to table 1 and table 2.
In this embodiment, three ways may be used to resolve the actual IP address of the virtual machine in the second virtual machine list, where the first way is: determining the actual IP address of the virtual machine in the second virtual machine list only by monitoring a first communication message sent by the virtual machine corresponding to the IP address in the IP address pool; the second way is: only sending a second communication message to an IP address in an IP address pool, and determining the actual IP address of the virtual machine according to a third communication message which is responded by the virtual machine in the second virtual machine list to the second communication message; the third mode is that: and analyzing the actual IP address of the virtual machine in the second virtual machine list by combining the first mode and the second mode.
In this embodiment, a third manner is taken as an example to describe in detail, specifically, fig. 3 is a schematic flow chart of resolving an actual IP address of a virtual machine in the second virtual machine list, and referring to fig. 3, a process of resolving an actual IP address of a virtual machine in the second virtual machine list includes the following steps:
The preset value may be set according to actual needs, for example, the value range of the preset value may be a percentage value of 30% to 90%, in this embodiment, the detailed description may be given by taking 30% as an example; the preset time period may be set according to actual needs, and in this embodiment, the detailed description may be given by taking every 50 milliseconds as an example; the first preset time and the second preset time may be set according to actual needs, and in this embodiment, the first preset time and the second preset time may be described in detail by taking 10.2 seconds as an example.
Specifically, the available IP address field in the subnet a is 192.168.1.1-192.168.1.10, and 10 IP addresses are counted, as shown in table 1 and table 2, a virtual machine with complete IP address information occupies 2 IP addresses, the remaining 8 IP addresses form an IP address pool, there are 4 virtual machines missing IP address information, and the number of virtual machines needing to resolve actual IP addresses is 4; on the premise of ensuring the uniqueness of the logic IP address, 4 IP addresses can be randomly allocated to the virtual machine lacking the IP address information from the IP address pool to serve as the logic IP address; calculating the ratio of the number of virtual machines missing IP address information to the number of IP addresses in the IP address pool to be 50%;
the ratio of 50% to 30% is greater than that of the first communication message, and at this time, the fourth communication message is sent to all the IP addresses in the IP address pool every 50ms for 3 times continuously, wherein the fourth communication message can be an arp request message;
the number of virtual machines responding to the fourth communication message within 10.2 seconds is 2;
at this time, performing an arping scan on the IP addresses in the IP address pool, specifically, sending a second communication message to all the IP addresses in the IP address pool, where the second communication message may be an arp request message; fig. 4 is a schematic diagram of a result of the arping scan, and referring to fig. 4, two third communication messages are received within 10.2 seconds, where the third communication messages are messages responding to the second communication messages, and the messages may be arp reply messages, including the MAC address and the IP address of the virtual machine network card;
the received first third communication message is 'arp request for 192.168.1.5has reply from 00:50:56: aa:3b: 12', the MAC address 00:50:56: aa:3b:12 of the virtual machine network card in the third communication message is consistent with the MAC address of the virtual machine vm3 network card in the second virtual machine list, and 192.168.1.5 is the actual IP address of the virtual machine vm 3; the received second third communication message is 'arp request for 192.168.1.9has reply from 00:50:56: aa:3b: 14', and if the MAC address 00:50:56: aa:3b:14 of the virtual machine network card in the third communication message is consistent with the MAC address of the virtual machine vm5 network card in the second virtual machine list, the actual IP address of the virtual machine vm5 is analyzed to be 192.168.1.9;
because the number of the virtual machines with the determined actual IP addresses is 2 in 10.2 seconds and is less than the number of the virtual machines in the second virtual machine list, the first communication message sent by the virtual machine corresponding to the IP address in the IP address pool needs to be monitored, and the first communication message can be an arp request message sent by communicating with the outside when the virtual machine is started to work, and includes the MAC address and the IP address of the network card of the virtual machine; fig. 5 is a schematic diagram illustrating a result of monitoring arp request messages, and referring to fig. 5, two arp request messages are monitored, where a first arp request message is from a virtual machine with a MAC address 00:50:56: aa:3b:13 and an IP address 192.168.1.4 of a network card, and if the MAC address 00:50:56: aa:3b:13 of the virtual machine network card in the arp request message is consistent with the MAC address of the virtual machine vm4 in the second virtual machine list, an actual IP address 192.168.1.4 of the virtual machine vm4 is resolved; the second arp request message is from the virtual machine with the MAC address 00:50:56: aa:3b:15 and the IP address 192.168.1.6 of the network card, and if the MAC address 00:50:56: aa:3b:15 of the virtual machine network card in the arp request message is consistent with the MAC address of the virtual machine vm6 network card in the second virtual machine list, the actual IP address 192.168.1.6 of the virtual machine vm6 is resolved.
When the actual IP address 192.168.1.5 of the vm3 is resolved, since the actual IP address is consistent with the logical IP address 192.168.1.5 of the vm4, at this time, a new logical IP address needs to be reassigned to the vm4, for example, the IP address 192.168.1.10 in the IP address pool can be reassigned to the vm4, so as to ensure the uniqueness of the logical IP address; similarly, when the actual IP addresses of the virtual machines vm4, vm5 and vm6 are resolved, if the resolved actual IP addresses are consistent with the logical IP addresses of the virtual machines corresponding to the virtual addresses in the second virtual machine list, which are different from the actual IP addresses, new logical IP addresses need to be applied again to ensure the uniqueness of the logical IP addresses.
In addition, if the IP address in the IP address pool is scanned for multiple times or an arp request message sent by a virtual machine corresponding to the IP address in the IP address pool is monitored for multiple times, if there is no response to the IP address, it may indicate that the user of the IP address is in a shutdown state, or the IP address is in an idle state, and the virtual machine is not used.
Further, whether only the first manner or the second manner is adopted, or the first manner and the second manner are combined to analyze the actual IP address of the virtual machine in the second virtual machine list, the actual IP address can be selected by flexibly configuring the preset value, the preset time interval, the first preset time and the second preset time. The user can also configure the virtual machine to finish the work only when the actual IP addresses of all the virtual machines missing the IP address information are analyzed; the real IP address of the virtual machine lacking the IP address information may also be limited to be resolved within a certain time, and if the time is out, the real IP address of a part of the virtual machine is still not successfully resolved, for example, an arp request message cannot be responded within a certain time because the virtual machine is always in a shutdown state or in a busy state, at this time, the real IP address of the virtual machine may be resolved by increasing the automatic resolving time or by manual intervention.
The invention also provides a virtual machine migration device, which is used for realizing the specific details of the virtual machine migration method of the invention and achieving the same effect.
Fig. 6 is a schematic structural diagram of a first embodiment of a virtual machine migration apparatus according to the present invention, and referring to fig. 6, the virtual machine migration apparatus of the present embodiment includes: the system comprises an acquisition module 31, a screening module 32, an allocation module 33, a creation module 34, an IP address resolution module 35, a judgment module 36 and an updating module 37; wherein the content of the first and second substances,
the obtaining module 31 is configured to obtain a first virtual machine list, where the first virtual machine list includes an internet protocol IP address of a virtual machine in a target subnet;
the screening module 32 is configured to screen out a second virtual machine list from the first virtual machine list according to the IP address, where the second virtual machine list includes all virtual machines in the first virtual machine list that have not acquired the actual IP address;
the allocating module 33 is configured to allocate a logical IP address to the virtual machine in the second virtual machine list, where the logical IP address is an IP address in the target subnet that is different from the actual IP address in the first virtual machine list;
the creating module 34 is configured to create a virtual network server resource for the virtual machines in the second virtual machine list according to the allocated logical IP address;
the IP address resolution module 35 is configured to resolve an actual IP address of a virtual machine in the second virtual machine list;
the determining module 36 is configured to determine whether the analyzed actual IP address is consistent with a logical IP address of a first target virtual machine, where the first target virtual machine is a virtual machine in a second virtual machine list that is different from the virtual machine corresponding to the actual IP address; if so, reallocating a new logic IP address to a second target virtual machine, wherein the second target virtual machine is a virtual machine corresponding to a logic IP address consistent with the actual IP address in the first target virtual machine; if not, the updating module 37 is triggered;
the updating module 37 is configured to, when the actual IP address of the virtual machine in the second virtual machine list is resolved, replace the logical IP address of the corresponding virtual machine in the virtual network server with the actual IP address.
Further, in the second embodiment of the migration apparatus of the virtual machine of the present invention, the IP address resolution module 35 is introduced in detail; fig. 7 is a schematic structural diagram of the IP address resolution module, and referring to fig. 7, the IP address resolution module 35 includes: a monitoring unit 351, a first comparison unit 352 and a first determination unit 353; wherein the content of the first and second substances,
the monitoring unit 351 is configured to monitor a first communication packet sent by a virtual machine corresponding to an IP address in an IP address pool, where the IP address pool is all IP addresses in a target subnet that are different from actual IP addresses in the first virtual machine list;
the first comparing unit 352 is configured to compare the MAC address of the virtual machine network card in the first communication packet monitored currently with the MAC address of the virtual machine network card in the second virtual machine list;
the first determining unit 353 is configured to determine, when the MAC address of the currently monitored virtual machine network card is consistent with the MAC address of the virtual machine network card in the second virtual machine list, that the IP address of the virtual machine in the first communication packet is the actual IP address of the virtual machine corresponding to the MAC address of the currently monitored virtual machine network card.
The IP address resolution module 35 further includes: a first sending unit 354, a second comparing unit 355, a second determining unit 356 and a first judging unit 357; wherein the content of the first and second substances,
the first sending unit 354 is configured to send a second communication packet to an IP address in the IP address pool;
the second comparing unit 355 is configured to compare an MAC address of the virtual machine network card in a currently received third communication message with an MAC address of the virtual machine network card in a second virtual machine list, where the third communication message is a message that responds to the second communication message;
the second determining unit 356 is configured to determine, when the MAC address of the currently received virtual machine network card is consistent with the MAC address of the virtual machine network card in the second virtual machine list, the IP address of the virtual machine in the currently received third communication message as the actual IP address of the virtual machine corresponding to the MAC address of the currently received virtual machine network card;
the first judging unit 357 is configured to judge whether the number of virtual machines with determined actual IP addresses in the second virtual machine list is smaller than the number of virtual machines in the second virtual machine list within a first preset time; when the number of virtual machines in the second virtual machine list for which the actual IP address has been determined is smaller than the number of virtual machines in the second virtual machine list, the snooping unit 351 is triggered.
The IP address resolution module 35 further includes: a second transmitting unit 358 and a second judging unit 359; wherein the content of the first and second substances,
the second sending unit 358 is configured to send a fourth communication packet to the IP address in the IP address pool according to a preset time period;
the second determining unit 359, configured to determine whether the number of virtual machines responding to the fourth communication message within a second preset time is greater than 0; if yes, triggering the first sending unit 354; if not, the listening unit 351 is triggered.
The IP address resolution module further comprises:
a third determining unit 3510, configured to determine whether a ratio of the number of virtual machines in the second virtual machine list to the number of IP addresses in the IP address pool is greater than a preset value; if yes, triggering the second sending unit 358; if not, the listening unit 351 is triggered.
Further, fig. 8 is a schematic diagram of a deployment position of an IP address resolution module in OpenStack, and referring to fig. 8, in practical application, according to a design principle of OpenStack, the IP address resolution module is deployed and operated on a network node.
In practical applications, the obtaining module 31, the screening module 32, the allocating module 33, the creating module 34, the IP address parsing module 35, the determining module 36, the updating module 37, the monitoring Unit 351, the first comparing Unit 352, the first determining Unit 353, the first sending Unit 354, the second comparing Unit 355, the second determining Unit 356, the first determining Unit 357, the second sending Unit 358, the second determining Unit 359, and the third determining Unit 3510 may all be implemented by a Central Processing Unit (CPU), a Micro Processing Unit (MPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), or the like located in the mobile terminal.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, and improvement made within the spirit and scope of the present invention are included in the protection scope of the present invention.
Claims (12)
1. A migration method of a virtual machine, the method comprising:
acquiring a first virtual machine list, wherein the first virtual machine list comprises Internet Protocol (IP) addresses of virtual machines in a target subnet;
screening a second virtual machine list from the first virtual machine list according to the IP address, wherein the second virtual machine list comprises all virtual machines which are not obtained the actual IP address in the first virtual machine list;
allocating a logic IP address to the virtual machine in the second virtual machine list, wherein the logic IP address is an IP address in the target subnet different from the actual IP address in the first virtual machine list;
establishing virtual network server resources for the virtual machines in the second virtual machine list according to the distributed logic IP addresses;
and when the actual IP address of the virtual machine in the second virtual machine list is analyzed, replacing the logic IP address of the corresponding virtual machine in the virtual network server with the actual IP address.
2. The method of claim 1, wherein after creating virtual network server resources for the virtual machines in the second list of virtual machines according to the assigned logical IP addresses, the method further comprises:
monitoring a first communication message sent by a virtual machine corresponding to an IP address in an IP address pool, wherein the IP address pool is all IP addresses different from an actual IP address in a first virtual machine list in a target subnet;
comparing the MAC address of the virtual machine network card in the first communication message monitored currently with the MAC address of the virtual machine network card in the second virtual machine list;
when the MAC address of the currently monitored virtual machine network card is consistent with the MAC address of the virtual machine network card in the second virtual machine list, determining that the IP address of the virtual machine in the first communication message is the actual IP address of the virtual machine corresponding to the MAC address of the currently monitored virtual machine network card.
3. The method according to claim 2, wherein before monitoring the first communication packet sent by the virtual machine corresponding to the IP address in the IP address pool, the method further comprises:
sending a second communication message to the IP address in the IP address pool;
comparing the MAC address of the virtual machine network card in a currently received third communication message with the MAC address of the virtual machine network card in a second virtual machine list, wherein the third communication message is a message for responding to the second communication message;
when the MAC address of the currently received virtual machine network card is consistent with the MAC address of the virtual machine network card in the second virtual machine list, determining the IP address of the virtual machine in the currently received third communication message as the actual IP address of the virtual machine corresponding to the MAC address of the currently received virtual machine network card;
judging whether the number of virtual machines of which the actual IP addresses are determined in the second virtual machine list is smaller than the number of virtual machines in the second virtual machine list within first preset time;
and when the number of the virtual machines with the actual IP addresses in the second virtual machine list is determined to be smaller than that in the second virtual machine list, monitoring a first communication message sent by the virtual machine corresponding to the IP address in the IP address pool.
4. The method of claim 3, wherein prior to sending the second communication message to the IP address in the IP address pool, the method further comprises:
sending a fourth communication message to the IP address in the IP address pool according to a preset time period;
judging whether the number of the virtual machines responding to the fourth communication message in a second preset time is greater than 0 or not;
if yes, executing a step of sending a second communication message to the IP address in the IP address pool;
and if not, monitoring the first communication message sent by the virtual machine corresponding to the IP address in the IP address pool.
5. The method of claim 4, wherein before sending the fourth communication message to the IP addresses in the IP address pool according to the preset time period, the method further comprises:
judging whether the ratio of the number of the virtual machines in the second virtual machine list to the number of the IP addresses in the IP address pool is larger than a preset value or not;
if yes, executing the step of sending a fourth communication message to the IP address in the IP address pool according to a preset time period;
and if not, monitoring the first communication message sent by the virtual machine corresponding to the IP address in the IP address pool.
6. The method of any of claims 1-5, wherein prior to replacing the logical IP address of the corresponding virtual machine in the virtual network server with an actual IP address, the method further comprises:
judging whether the analyzed actual IP address is consistent with a logic IP address of a first target virtual machine, wherein the first target virtual machine is a virtual machine which is different from the actual IP address and corresponds to the actual IP address in a second virtual machine list;
if so, reallocating a new logic IP address to a second target virtual machine, wherein the second target virtual machine is a virtual machine corresponding to a logic IP address consistent with the actual IP address in the first target virtual machine;
and if not, executing the step of replacing the logic IP address of the corresponding virtual machine in the virtual network server with the actual IP address.
7. An apparatus for migrating a virtual machine, the apparatus comprising: the system comprises an acquisition module, a screening module, a distribution module, a creation module and an updating module; wherein the content of the first and second substances,
the acquiring module is used for acquiring a first virtual machine list, wherein the first virtual machine list comprises IP addresses of virtual machines in a target subnet;
the screening module is used for screening a second virtual machine list from the first virtual machine list according to the IP address, wherein the second virtual machine list comprises all virtual machines which are not obtained the actual IP address in the first virtual machine list;
the allocating module is configured to allocate a logical IP address to the virtual machine in the second virtual machine list, where the logical IP address is an IP address in the target subnet that is different from the actual IP address in the first virtual machine list;
the creating module is used for creating virtual network server resources for the virtual machines in the second virtual machine list according to the allocated logic IP addresses;
and the updating module is used for replacing the logic IP address of the corresponding virtual machine in the virtual network server with the actual IP address when the actual IP address of the virtual machine in the second virtual machine list is analyzed.
8. The apparatus of claim 7, further comprising: an IP address resolution module; wherein the content of the first and second substances,
the IP address resolution module comprises: the device comprises a monitoring unit, a first comparison unit and a first determination unit; wherein the content of the first and second substances,
the monitoring unit is used for monitoring a first communication message sent by a virtual machine corresponding to an IP address in an IP address pool, wherein the IP address pool is all IP addresses different from an actual IP address in the first virtual machine list in a target subnet;
the first comparison unit is used for comparing the MAC address of the virtual machine network card in the first communication message monitored currently with the MAC address of the virtual machine network card in the second virtual machine list;
the first determining unit is configured to determine that the IP address of the virtual machine in the first communication packet is the actual IP address of the virtual machine corresponding to the currently monitored MAC address of the virtual machine network card when the currently monitored MAC address of the virtual machine network card is consistent with the MAC address of the virtual machine network card in the second virtual machine list.
9. The apparatus of claim 8, wherein the IP address resolution module further comprises: the device comprises a first sending unit, a second comparing unit, a second determining unit and a first judging unit; wherein the content of the first and second substances,
the first sending unit is configured to send a second communication packet to the IP address in the IP address pool;
the second comparison unit is configured to compare an MAC address of the virtual machine network card in a currently received third communication message with an MAC address of the virtual machine network card in a second virtual machine list, where the third communication message is a message that responds to the second communication message;
the second determining unit is configured to determine, when the MAC address of the currently received virtual machine network card is consistent with the MAC address of the virtual machine network card in the second virtual machine list, the IP address of the virtual machine in the currently received third communication message as the actual IP address of the virtual machine corresponding to the MAC address of the currently received virtual machine network card;
the first judging unit is used for judging whether the number of the virtual machines of which the actual IP addresses are determined in the second virtual machine list is smaller than that in the second virtual machine list within a first preset time; and when the number of the virtual machines with the determined actual IP addresses in the second virtual machine list is less than that in the second virtual machine list, triggering the monitoring unit.
10. The apparatus of claim 9, wherein the IP address resolution module further comprises: a second transmitting unit and a second judging unit; wherein the content of the first and second substances,
the second sending unit is configured to send a fourth communication packet to the IP address in the IP address pool according to a preset time period;
the second judging unit is configured to judge whether the number of virtual machines responding to the fourth communication message within a second preset time is greater than 0; if yes, triggering the first sending unit; if not, triggering the monitoring unit.
11. The apparatus of claim 10, wherein the IP address resolution module further comprises:
a third judging unit, configured to judge whether a ratio of the number of virtual machines in the second virtual machine list to the number of IP addresses in the IP address pool is greater than a preset value; if yes, triggering the second sending unit; if not, triggering the monitoring unit.
12. The apparatus of any one of claims 7 to 11, further comprising:
the judging module is used for judging whether the analyzed actual IP address is consistent with a logic IP address of a first target virtual machine, wherein the first target virtual machine is a virtual machine which is different from the virtual machine corresponding to the actual IP address in a second virtual machine list; if so, reallocating a new logic IP address to a second target virtual machine, wherein the second target virtual machine is a virtual machine corresponding to a logic IP address consistent with the actual IP address in the first target virtual machine; if not, the updating module is triggered.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611257196.8A CN108268300B (en) | 2016-12-30 | 2016-12-30 | Virtual machine migration method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611257196.8A CN108268300B (en) | 2016-12-30 | 2016-12-30 | Virtual machine migration method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108268300A CN108268300A (en) | 2018-07-10 |
| CN108268300B true CN108268300B (en) | 2022-01-25 |
Family
ID=62754488
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611257196.8A Active CN108268300B (en) | 2016-12-30 | 2016-12-30 | Virtual machine migration method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108268300B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110519406B (en) * | 2019-08-16 | 2022-05-17 | 济南浪潮数据技术有限公司 | Virtual address allocation method and device, CTDB cluster and storage medium |
| CN114760269B (en) * | 2022-03-17 | 2024-04-09 | 深信服科技股份有限公司 | Virtual machine address allocation method, device and storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1571358A (en) * | 2003-07-19 | 2005-01-26 | 华为技术有限公司 | Static user access network control method based on MAC address |
| CN101662808A (en) * | 2009-08-27 | 2010-03-03 | 上海交通大学 | Method for quickly switching network layers of IEEE802.11 wireless local area network |
| CN103078965A (en) * | 2012-12-25 | 2013-05-01 | 曙光云计算技术有限公司 | IP (Internet Protocol) address management method of virtual machines |
| CN103595826A (en) * | 2013-11-01 | 2014-02-19 | 国云科技股份有限公司 | Method for preventing IP and MAC of virtual machine from being faked |
| CN103747115A (en) * | 2013-12-30 | 2014-04-23 | 武汉邮电科学研究院 | Method of discovering IP (Internet Protocol) address of virtual machine based on virtual network interface card |
| CN104081733A (en) * | 2012-01-31 | 2014-10-01 | 国际商业机器公司 | Interconnecting data centers for migration of virtual machines |
| CN104461697A (en) * | 2014-12-25 | 2015-03-25 | 中国科学院信息工程研究所 | Automatic setting system and method for batched online IP addresses of virtual machine |
| CN105589731A (en) * | 2015-09-16 | 2016-05-18 | 杭州华三通信技术有限公司 | Virtual machine migration method and device |
-
2016
- 2016-12-30 CN CN201611257196.8A patent/CN108268300B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1571358A (en) * | 2003-07-19 | 2005-01-26 | 华为技术有限公司 | Static user access network control method based on MAC address |
| CN101662808A (en) * | 2009-08-27 | 2010-03-03 | 上海交通大学 | Method for quickly switching network layers of IEEE802.11 wireless local area network |
| CN104081733A (en) * | 2012-01-31 | 2014-10-01 | 国际商业机器公司 | Interconnecting data centers for migration of virtual machines |
| CN103078965A (en) * | 2012-12-25 | 2013-05-01 | 曙光云计算技术有限公司 | IP (Internet Protocol) address management method of virtual machines |
| CN103595826A (en) * | 2013-11-01 | 2014-02-19 | 国云科技股份有限公司 | Method for preventing IP and MAC of virtual machine from being faked |
| CN103747115A (en) * | 2013-12-30 | 2014-04-23 | 武汉邮电科学研究院 | Method of discovering IP (Internet Protocol) address of virtual machine based on virtual network interface card |
| CN104461697A (en) * | 2014-12-25 | 2015-03-25 | 中国科学院信息工程研究所 | Automatic setting system and method for batched online IP addresses of virtual machine |
| CN105589731A (en) * | 2015-09-16 | 2016-05-18 | 杭州华三通信技术有限公司 | Virtual machine migration method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108268300A (en) | 2018-07-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10635496B2 (en) | Thread pool management | |
| CN107924383B (en) | System and method for network function virtualized resource management | |
| US10701139B2 (en) | Life cycle management method and apparatus | |
| US10819538B2 (en) | Method and apparatus for establishing link between virtualized network functions | |
| US9887959B2 (en) | Methods and system for allocating an IP address for an instance in a network function virtualization (NFV) system | |
| US10686755B2 (en) | Assigning IP addresses and configuration parameters in hyper-converged infrastructure | |
| US9639402B2 (en) | Systems and methods for automatic hardware provisioning based on application characteristics | |
| CN108924268B (en) | Container cloud service system and pod creation method and device | |
| US11301303B2 (en) | Resource pool processing to determine to create new virtual resource pools and storage devices based on currebt pools and devices not meeting SLA requirements | |
| WO2017148249A1 (en) | Resource configuration method and network device thereof | |
| US20190261186A1 (en) | Network Slice Management Method, Management Unit, and System | |
| US20170373931A1 (en) | Method for updating network service descriptor nsd and apparatus | |
| EP3913859A1 (en) | Vnf life cycle management method and apparatus | |
| EP2892181A1 (en) | Method, device and physical host for managing physical network card | |
| CN110741352B (en) | Virtual network function management system, virtual network function management method and computer readable storage device | |
| WO2014169870A1 (en) | Virtual network element automatic loading and virtual machine ip address acquisition method and system, and storage medium | |
| EP3249852B1 (en) | Methods and devices for determining processing policy of a vnf | |
| JP6330923B2 (en) | Orchestrator device, system, virtual machine creation method and program | |
| US20190018710A1 (en) | Managing resource allocation of a managed system | |
| US20180246772A1 (en) | Method and apparatus for allocating a virtual resource in network functions virtualization network | |
| CN108268300B (en) | Virtual machine migration method and device | |
| CN111262771B (en) | Virtual private cloud communication system, system configuration method and controller | |
| JP2017027166A (en) | Operation management unit, operation management program, and information processing system | |
| WO2021121595A1 (en) | Discovering an instance of a virtual network function | |
| TW201518951A (en) | Control center deployment method for cloud-based system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |