WO2018036103A1 - 虚拟机创建方法、系统以及主机 - Google Patents
虚拟机创建方法、系统以及主机 Download PDFInfo
- Publication number
- WO2018036103A1 WO2018036103A1 PCT/CN2017/072987 CN2017072987W WO2018036103A1 WO 2018036103 A1 WO2018036103 A1 WO 2018036103A1 CN 2017072987 W CN2017072987 W CN 2017072987W WO 2018036103 A1 WO2018036103 A1 WO 2018036103A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- host
- tenant
- identifier
- virtual machine
- machine creation
- Prior art date
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
-
- 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/45562—Creating, deleting, cloning virtual machine instances
Definitions
- the embodiments of the present invention relate to the field of computer technologies, and in particular, to a virtual machine creation method, system, and host.
- the common IaaS Intelligent as a Service
- the common IaaS Infrastructure as a Service
- Virtual machines this isolation is essentially a logical isolation, and different tenants do not monopolize their own physical resources. For example, different virtual machines on one physical machine may be subordinate to different tenants.
- the virtual machines of different tenants share the same server's memory and CPU resources, and one tenant's virtual machine can steal another resource from the shared resources.
- the data stored by a tenant's virtual machine has low data confidentiality between different tenants' virtual machines.
- embodiments of the present invention provide a virtual machine creation method, system, and host.
- a virtual machine creation method is provided, which is applied to a virtual machine creation system including a plurality of hosts, the method comprising: the virtual machine creation system first receiving a virtual machine creation request of a tenant, The virtual machine creation request carries the tenant identifier of the tenant; when the tenant is a preset tenant, the virtual machine creation system determines the tenant identifier in the virtual machine creation request according to the binding relationship between the tenant identifier and the host identifier.
- the bound host identifier, the host having the host identifier bound to the tenant ID in the virtual machine creation request is the target host; wherein the host having the host identifier in the binding relationship is only created and has the The host in the binding relationship identifies the virtual machine of the tenant of the tenant ID bound to the host, and the plurality of hosts include the host having the host identifier in the binding relationship; the virtual machine creation system then creates a request according to the virtual machine. Creating a virtual machine of the tenant on the target host.
- each host identifier in the binding relationship between the tenant identifier and the host identifier uniquely corresponds to one tenant identifier; for any tenant who has physical isolation requirements for the host, the virtual machine creation system only has The virtual machine of the tenant is created in the host of the host ID corresponding to the tenant's tenant ID, and the virtual machine of the tenant is not created in the host having the host ID corresponding to the tenant ID of the other tenant, that is, having the tenant Only the virtual machine of the tenant exists in the host of the host ID corresponding to the tenant ID, and there is no virtual machine of other users; thus, physical isolation between virtual machines of different tenants is realized, thereby improving the virtuality of different tenants. Data confidentiality between machines.
- the method further includes: the virtual machine creation system may determine, according to the tenant identifier in the virtual machine creation request, whether the tenant is the preset tenant, and the preset tenant refers to A tenant who has physical isolation requirements for the host.
- the virtual machine creation system when the tenant is not the preset tenant, the virtual machine creation system does not need to separately allocate one host to the tenant, so in order to save the host, the virtual machine creation system may be from the multiple Determining, by the host other than the host of the host identity included in the binding relationship, any one of the hosts to create the virtual machine of the tenant, or the virtual machine creation system may also use the virtual machine resource scheduling policy from the plurality of Among the hosts other than the host of the host identity included in the binding relationship, a host is determined to create the virtual machine of the tenant.
- the virtual machine creation system determines, according to the binding relationship between the tenant identifier and the host identifier, a host identifier that is bound to the tenant identifier in the virtual machine creation request, including: if the virtual machine creation system is based on the tenant identifier and the host If the identifier of the identified binding is determined to be one of the host IDs bound to the tenant ID in the virtual machine creation request, the host identifier is the host ID of the target host; if the virtual machine creation system is based on the tenant ID and the host If the identified binding relationship determines that the host identifier is bound to the tenant identifier in the virtual machine creation request, the virtual machine creation system may select any one of the determined multiple host identifiers as the target.
- the host identifier of the host; or the virtual machine creation system may select one of the determined host identifiers as the host identifier of the target host according to the virtual machine resource scheduling policy.
- the resource scheduling policy can be a load balancing policy or the like.
- the virtual machine creation system may select the remaining storage space and/or The host with the largest computing resources remaining and serves as the target host.
- the virtual machine creation request carries a resource requirement parameter; the virtual machine creation system determines, according to a binding relationship between the tenant identifier and the host identifier, a host identifier that is bound to the tenant identifier in the virtual machine creation request,
- the host identifier is a host of the target host, if the host identifier that is bound to the tenant identifier in the virtual machine creation request is determined by the virtual machine creation system according to the binding relationship between the tenant identifier and the host identifier.
- the virtual machine creation system may have a certain number of determinations if the number of host IDs bound to the tenant ID in the virtual machine creation request determined by the virtual machine creation system is determined by the binding relationship between the tenant ID and the host ID.
- the host that meets the resource requirement parameter is selected as the target host, and the host identifier of the target host is determined.
- the virtual machine creation system selects, as the target host, the host that meets the resource requirement parameter among the multiple hosts that have the determined multiple host identifiers, including: if the virtual machine creation system is in the determined multiple hosts If the host that meets the resource requirement parameter is one of the identified multiple hosts, the host is the target host; if the virtual machine creation system meets the resource requirement in multiple hosts having the determined multiple host identifiers The main parameter If there are multiple machines, the virtual machine creation system may select any one of the plurality of hosts that meet the resource requirement parameter as the target host, or the virtual machine creation system may also use multiple parameters that satisfy the resource requirement parameter.
- a host is determined as a target host according to a resource scheduling policy.
- the resource scheduling policy can be a load balancing policy or the like.
- the virtual machine is created.
- the system can select the hosts with the largest remaining storage space and/or the largest remaining computing resources among these hosts and serve as the target host.
- a virtual machine creation system includes: a receiving unit and a processing unit, wherein the receiving unit is configured to receive a virtual machine creation request of a tenant, and the virtual machine creation request And the processing unit is configured to: determine, when the tenant is a preset tenant, the host identifier that is bound to the tenant identifier in the virtual machine creation request according to the binding relationship between the tenant identifier and the host identifier.
- the host having the host identifier bound to the tenant ID in the virtual machine creation request is the target host, and the virtual machine of the tenant is created on the target host according to the virtual machine creation request.
- the host having the host identifier in the binding relationship is only for creating a virtual machine of a tenant having a tenant identifier bound to the host identifier in the binding relationship, and the multiple hosts include the binding.
- the host of the host ID in the relationship is only for creating a virtual machine of a tenant having a tenant identifier bound to the host identifier in the binding relationship.
- each host identifier in the binding relationship between the tenant identifier and the host identifier uniquely corresponds to one tenant identifier; for any tenant who has physical isolation requirements for the host, the virtual machine creation system only has The virtual machine of the tenant is created in the host of the host ID corresponding to the tenant's tenant ID, and the virtual machine of the tenant is not created in the host having the host ID corresponding to the tenant ID of the other tenant, that is, having the tenant Only the virtual machine of the tenant exists in the host of the host ID corresponding to the tenant ID, and there is no virtual machine of other users; thus, physical isolation between virtual machines of different tenants is realized, thereby improving the virtuality of different tenants. Data confidentiality between machines.
- the processing unit is further configured to determine, according to the tenant identifier in the virtual machine creation request, whether the tenant is the preset tenant, where the preset tenant refers to a physical isolation requirement for the host. Tenant.
- the processing unit does not need to separately allocate one host to the tenant. Therefore, in order to save the host, the processing unit is further used to Determining any one of the hosts other than the host of the host identity included in the binding relationship to create a virtual machine of the tenant, or removing from the plurality of hosts according to a virtual machine resource scheduling policy A host other than the host whose host identity is included in the binding relationship determines a host to create the virtual machine of the tenant.
- the processing unit is further configured to: if the host identifier bound to the tenant identifier in the virtual machine creation request is determined according to the binding relationship between the tenant identifier and the host identifier, the host identifier is The host identifier of the target host; if the host identifier bound to the tenant identifier in the virtual machine creation request is determined according to the binding relationship between the tenant identifier and the host identifier, the plurality of host identifiers are determined from the plurality of host identifiers. Selecting any host identifier as the host identifier of the target host; or selecting one of the determined multiple host identifiers according to the virtual machine resource scheduling policy Any host ID is the host ID of the target host.
- the resource scheduling policy can be a load balancing policy or the like.
- the processing unit may select the largest storage space and/or among the hosts. The host with the largest computing resources remaining and serves as the target host.
- the virtual machine creation request carries a resource requirement parameter
- the processing unit is further configured to: if the tenant identifier in the virtual machine creation request is determined according to the binding relationship between the tenant identifier and the host identifier, If the host ID is one, the host identifier is the host ID of the target host; and the host identifier bound to the tenant ID in the VM creation request is determined according to the binding relationship between the tenant ID and the host identifier. If there are multiple, the host that meets the resource requirement parameter is selected as the target host among the multiple hosts having the determined multiple host identifiers, and the host identifier of the target host is determined.
- the processing unit is further configured to: if the host that meets the resource requirement parameter is one of the plurality of hosts having the determined plurality of host identifiers, the host is the target host; If there are multiple hosts satisfying the resource requirement parameter among the plurality of hosts having the determined plurality of host identifiers, selecting any one of the plurality of hosts that meet the resource requirement parameter as the target host, or satisfying One of the plurality of hosts of the resource requirement parameter determines a host as the target host according to the resource scheduling policy.
- the resource scheduling policy can be a load balancing policy or the like.
- the processing is performed.
- the unit can be selected from these hosts as the target host with the largest remaining storage space and/or the largest remaining computing resources.
- the embodiment of the present application further provides a host, including at least one processor, a memory, and a communication interface; the at least one processor, the memory, and the communication interface are all connected by a bus;
- the memory is configured to store a computer execution instruction
- the at least one processor configured to execute the computer-executed instructions of the memory storage, such that the host performs data interaction with other hosts in the virtual machine creation system through the communication interface to perform the first aspect or the first aspect described above
- Each of the possible designs provides a virtual machine creation method that includes the host.
- a computer readable storage medium where computer execution instructions are stored, and when the at least one processor of the host executes the computer to execute an instruction, the host performs the first aspect or the first aspect.
- a computer program product comprising computer executed instructions stored in a computer readable storage medium.
- At least one processor of the host computer can read the computer executable instructions from the computer readable storage medium, and the at least one processor executes the computer to execute the instructions such that the host implements the virtual machine creation provided by the first aspect or the various possible designs of the first aspect method.
- FIG. 1 is a schematic diagram of a cloud computing platform according to an exemplary embodiment
- FIG. 2 is a flowchart of a virtual machine creation method according to an exemplary embodiment
- FIG. 3 is a block diagram of a virtual machine creation system according to an exemplary embodiment
- FIG. 4 is a block diagram of a virtual machine creation system, according to an exemplary embodiment.
- a cloud computing platform includes a virtual machine creation system 1 and a plurality of hosts 2, and the virtual machine creation system 1 and each host 2 respectively communicate with each other.
- the virtual machine creation system 1 can control each host 2.
- the virtual machine creation system 1 can create a virtual machine or the like in any one of the hosts 2, and the virtual machine creation system can be integrated on a certain host 2.
- Host 2 can be a server or a personal computer, or can be other computing devices with computing power.
- FIG. 2 is a flowchart of a method for creating a virtual machine according to an exemplary embodiment.
- the execution body of the method is a virtual machine creation system, and the method includes the steps shown in FIG. 2.
- step S101 a virtual machine creation request of a tenant is received, where the virtual machine creation request carries the tenant identifier;
- the virtual machine creation request may be sent to the virtual machine creation system, and the virtual machine creation request carries at least the tenant identifier of the tenant.
- the tenant may be a preset user or may not be a preset user.
- a preset tenant can be a tenant who has physical isolation requirements for the host.
- a tenant When a tenant is a tenant with physical isolation requirements for the host, the tenant often has a higher requirement for the running environment of the virtual machine. Therefore, when creating a virtual machine, one host needs to be exclusive, and the virtual machine of the other tenant is not used. Share a host. That is, if the tenant needs to create a virtual machine on a host, then the virtual machine of the other tenant cannot exist in the host, and after the tenant creates the virtual machine of the tenant in the host, only the virtual machine in the host can be The virtual machine of the tenant continues to be created, and the virtual machines of other tenants cannot be created.
- the tenant When the tenant is not a tenant with physical isolation requirements for the host, the tenant often has lower requirements for the running environment of the virtual machine; the tenant can create a virtual machine of the tenant without a single host, and can be virtualized with other tenants.
- the machine shares a host. That is, if the tenant needs to create a virtual machine on one host, then the host can There are virtual machines of other tenants; after the tenant creates the tenant's virtual machine in the host, the virtual machines of other tenants can continue to be created in the host.
- the virtual machine creation system needs to determine whether the tenant is a tenant with physical isolation requirements for the host.
- the tenant needs to add the tenant's tenant to the virtual creation request message before sending the virtual machine creation request to the virtual machine creation system.
- the identity is such that the virtual machine creation system can determine, based on the tenant identity, whether the tenant is a tenant with physical isolation requirements for the host.
- each tenant is not a tenant having physical isolation requirements for the host, and each tenant has a tenant identifier; the tenant identifier is used to uniquely identify the tenant, for example, the tenant identifier may be the name of the tenant or Numbering.
- the tenant can create a system to apply for the exclusive host to the virtual machine.
- the tenant is the tenant who has physical isolation requirements for the host.
- the virtual machine creation system adds a preset feature identifier to the tenant's tenant ID to identify the tenant as a tenant who has physical isolation requirements for the host.
- each tenant ID consists of 4 digits. Assuming that the tenant's tenant ID is "1234" and the preset feature identifier is "#”, the preset feature identifier "#" is added to the tenant ID "1234" to obtain "1234#”.
- the virtual machine creation system can determine whether the tenant identifier carries the preset feature identifier.
- the tenant is determined to be a tenant with physical isolation requirements for the host, and then the tenant is determined to be pre-determined. If the tenant ID does not carry the preset feature identifier, it is determined that the tenant is not a tenant who has physical isolation requirements for the host, and then determines that the tenant is not the default tenant.
- the host identifier bound to the tenant ID in the virtual machine creation request is determined according to the binding relationship between the tenant identifier and the host identifier, and is associated with the virtual machine creation request.
- the host identified by the tenant ID of the host ID is the target host;
- the host that has the host ID in the binding relationship is only used to create a virtual machine that has a tenant ID that is bound to the host ID in the binding relationship.
- the multiple hosts include the binding relationship. Host identified by the host; each host ID in the binding relationship uniquely corresponds to a tenant ID.
- the binding relationship may have a plurality of different host identifiers corresponding to one tenant identifier, for example, when a tenant is a tenant having physical isolation requirements for the host, and the tenant needs to create a virtual machine.
- the virtual machine creation system can assign at least two hosts to the tenant from multiple hosts, so that there are at least two host identifiers bound to the tenant ID in the binding relationship.
- the step may be: if the host identifier bound to the tenant ID in the virtual machine creation request is determined according to the binding relationship between the tenant identifier and the host identifier, the host identifier is the host identifier of the target host. If the host identifier bound to the tenant ID in the virtual machine creation request is determined according to the binding relationship between the tenant ID and the host identifier, selecting one of the determined multiple host identifiers is The host ID of the target host.
- creating a virtual machine in a host requires occupying resources of the host, for example, a computing resource of the host, a storage resource of the host, and a network resource of the host, etc., and the remaining resources of the host are sufficient.
- Create a virtual machine in the host For example, the storage space in each host in the virtual machine creation system is limited, and the computing resources in each host are also limited.
- a virtual machine creation system creates a virtual machine in a host, it needs to occupy a part of the storage space in the host, and needs to occupy a part of the computing resources of the host, such as the computing resources of the CPU of the host and the computing resources of the memory.
- the host with the host ID may have not yet created a virtual machine, or one or more virtual machines may have been created for each other host ID in the binding relationship. The same is true.
- the remaining storage space in the host with the host ID is greater than or equal to the occupied space of the virtual machine to be created, but the national virtual machine is created before the host with the host identifier, and the virtual machine is running, because the host runs
- the virtual machine needs to occupy the computing resources of the host, for example, CPU resources and memory resources.
- the computing resources of the host are occupied.
- the process of creating a VM locally depends on the computing resources of the host. Therefore, when the CPU usage or memory usage of a host is too high, if you create a VM in the host, the system may be affected.
- the host runs the stability of other created virtual machines.
- the virtual machine creation request also needs to carry resource requirement parameters, and the resource requirement parameters include the virtual to be created. At least one of the occupied space of the machine, the occupied resources of the host required to create the virtual machine, and the network resources of the host to be occupied.
- the host identifier bound to the tenant ID in the virtual machine creation request is one according to the binding relationship between the tenant ID and the host identifier
- the host identifier is the host of the target host. If the number of hosts bound to the tenant ID in the virtual machine creation request determined by the binding relationship between the tenant ID and the host identifier is multiple, in multiple hosts having multiple host identifiers determined Select the host that meets the resource requirement parameter as the target host and determine the host ID of the target host.
- the host that meets the resource requirement parameter is selected as the target host among the multiple hosts that have the determined multiple host identifiers, including:
- the host that meets the resource requirement parameter is one of the plurality of hosts having the determined plurality of host identifiers
- the host that meets the resource requirement parameter is the target host; if there are multiple hosts having the determined multiple host identifiers If there are multiple hosts in the host that meet the resource requirement parameter, select one of the multiple hosts that meet the resource requirement parameter as the target host, or determine from the multiple hosts that meet the resource requirement parameter according to the resource scheduling policy.
- a host acts as the target host.
- the resource scheduling policy can be a load balancing policy or the like.
- load balancing when the remaining storage space is greater than or equal to the occupied space of the virtual machine to be created, and the remaining computing resources are larger than the number of hosts that need to occupy the computing resources to be created, the virtual machine is created.
- the system can select the hosts with the largest remaining storage space and/or the largest remaining computing resources among these hosts and serve as the target host.
- step S103 the virtual machine of the tenant is created on the target host according to the virtual machine creation request
- the tenant needs to create a virtual machine in the virtual machine creation system to create a virtual machine.
- the virtual machine creation system selects one from the virtual machine creation system.
- the host of the virtual machine is not created and assigned to the tenant. After that, the selected host is no longer a host that can be created by other tenants at the same time. That is, only the tenant can create a virtual machine in the selected host. Other tenants cannot create virtual machines in the selected host.
- step S104 is performed. If there are multiple shared hosts in the virtual machine creation system, the control device may select one shared host from the plurality of shared hosts, and then perform step S104. For the specific selection process of selecting a shared host from the multiple shared hosts, refer to the selection process in step S103, which is not described in detail herein.
- step S104 when the tenant is not the preset tenant, determining, by the host other than the host of the host identifier included in the binding relationship, the virtual machine of the tenant is created, or according to The virtual machine resource scheduling policy determines a host from among hosts of the plurality of hosts other than the host identifier included in the binding relationship to create the virtual machine of the tenant.
- each host identifier in the binding relationship between the tenant identifier and the host identifier uniquely corresponds to one tenant identifier; for any tenant that has physical isolation requirements for the host, the virtual machine creation system only has The virtual machine of the tenant is created in the host with the host ID corresponding to the tenant's tenant ID, and the virtual machine of the tenant is not created in the host having the host identifier corresponding to the tenant ID of the other tenant, that is, having Only the virtual machine of the tenant exists in the host of the host ID corresponding to the tenant ID of the tenant, and there is no virtual machine of other users; thus, physical isolation between virtual machines of different tenants is realized, thereby improving different tenants. Data confidentiality between virtual machines.
- FIG. 3 is a block diagram of a virtual machine creation system, according to an exemplary embodiment.
- the system includes:
- the receiving unit 11 is configured to receive a virtual machine creation request of the tenant, where the virtual machine creation request carries the tenant identifier of the tenant;
- the processing unit 12 is configured to determine, according to the binding relationship between the tenant identifier and the host identifier, a host identifier bound to the tenant identifier in the virtual machine creation request, where the tenant is the default tenant, and the virtual machine
- the host that creates the host ID bound to the tenant ID in the request is the target host.
- the host with the host ID in the binding relationship is only created with the tenant ID that is bound to the host ID in the binding relationship.
- the tenant's virtual machine, The plurality of hosts includes a host having a host identifier in the binding relationship;
- the processing unit 12 is further configured to create a virtual machine of the tenant on the target host according to the virtual machine creation request.
- each host identifier in the binding relationship between the tenant identifier and the host identifier uniquely corresponds to one tenant identifier; for any tenant who has physical isolation requirements for the host, the virtual machine creation system only has The virtual machine of the tenant is created in the host of the host ID corresponding to the tenant's tenant ID, and the virtual machine of the tenant is not created in the host having the host ID corresponding to the tenant ID of the other tenant, that is, having the tenant Only the virtual machine of the tenant exists in the host of the host ID corresponding to the tenant ID, and there is no virtual machine of other users; thus, physical isolation between virtual machines of different tenants is realized, thereby improving the virtuality of different tenants. Data confidentiality between machines.
- processing unit 12 is further configured to:
- processing unit 12 is further configured to:
- the tenant is not the preset tenant, determining, by using any one of the plurality of hosts, other than the host of the host identifier included in the binding relationship, to create the virtual machine of the tenant, Or determining, according to the virtual machine resource scheduling policy, a host from the hosts other than the host identifier of the binding relationship included in the multiple hosts to create the virtual machine of the tenant.
- the processing unit 12 is further configured to:
- the host identifier bound to the tenant identifier in the virtual machine creation request is determined according to the binding relationship between the tenant identifier and the host identifier, the host identifier is the host identifier of the target host.
- a host identifier that is bound to the tenant identifier in the virtual machine creation request and selecting any one of the determined multiple host identifiers as the The host identifier of the target host; or the host identifier of the target host is selected from the determined plurality of host identifiers according to the virtual machine resource scheduling policy.
- the virtual machine creation request carries resource requirement parameters in order to avoid losing other data and to avoid the stability of running other created virtual machines when creating a virtual machine in the host;
- the processing unit 12 is further configured to:
- the host identifier bound to the tenant identifier in the virtual machine creation request is determined according to the binding relationship between the tenant identifier and the host identifier, the host identifier is the host identifier of the target host.
- the host identifier bound to the tenant ID in the virtual machine creation request is determined according to the binding relationship between the tenant ID and the host identifier, the plurality of hosts having the determined plurality of host identifiers are selected to be satisfied.
- the host that describes the resource requirement parameter serves as the target host, and determines the host identifier of the target host.
- the processing unit 12 is further configured to:
- the host that meets the resource requirement parameter is one of the plurality of hosts having the determined plurality of host identifiers, Then the host is the target host;
- the virtual machine creation system is deployed on multiple hosts. Therefore, the hardware body of the virtual machine creation method is the host, and the hardware body of the virtual machine creation system is also the host; the host is illustrated in FIG. 4 as the host 400. That is, the host of the above method embodiment is the host 400 shown in FIG.
- the host 400 includes at least one processor 401, a memory 402, and a communication interface 403; the at least one processor 401, the memory 402, and the communication interface 403 are all connected by a bus 404;
- the memory 402 is configured to store a computer execution instruction
- the at least one processor 401 is configured to execute a computer execution instruction stored by the memory 402, so that the host 400 performs data interaction with other hosts in the virtual machine creation system through the communication interface 403 to perform the foregoing embodiment.
- the virtual machine creation method or the host 400 performs data interaction with other hosts in the virtual machine creation system through the communication interface 403 to implement some or all of the functions of the virtual machine creation system.
- the at least one processor 401 may include different types of processors 401 or include the same type of processor 401; the processor 401 may be any one of the following: a central processing unit (CPU), an ARM processor. , Field Programmable Gate Array (FPGA), dedicated processor and other devices with computational processing capabilities. In an optional implementation manner, the at least one processor 401 may also be integrated into a many-core processor.
- processors 401 may be any one of the following: a central processing unit (CPU), an ARM processor. , Field Programmable Gate Array (FPGA), dedicated processor and other devices with computational processing capabilities.
- the at least one processor 401 may also be integrated into a many-core processor.
- the memory 402 may be any one or any combination of the following: a random access memory (RAM), a read only memory (ROM), a non-volatile memory (non-volatile memory). , referred to as NVM), Solid State Drives (SSD), mechanical hard disks, disks, disk arrays and other storage media.
- RAM random access memory
- ROM read only memory
- NVM non-volatile memory
- SSD Solid State Drives
- Communication interface 403 is used by host 400 to perform data interaction with other devices, such as other hosts in the virtual machine creation system.
- the communication interface 403 may be any one or any combination of the following: a network interface (such as an Ethernet interface), a wireless network card, or the like having a network access function.
- the bus 404 can include an address bus, a data bus, a control bus, etc., for ease of representation, Figure 4 shows the bus with a thick line.
- the bus 404 can be any one or any combination of the following: an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, and an extended industry standard structure ( Extended Industry Standard Architecture (EISA) bus and other devices for wired data transmission.
- ISA Industry Standard Architecture
- PCI Peripheral Component Interconnect
- EISA Extended Industry Standard Architecture
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
一种虚拟机创建方法、系统以及主机。租户标识与主机标识之间的绑定关系中的每个主机标识唯一对应一个租户标识；对于对主机有物理隔离需求的任意一个租户，虚拟机创建系统只会在具有与该租户的租户标识对应的主机标识的主机中创建该租户的虚拟机，而不会在具有与其他租户的租户标识对应的主机标识的主机中创建该租户的虚拟机，也即，具有与该租户的租户标识对应的主机标识的主机中只会存在该租户的虚拟机，而不会存在其他用户的虚拟机；从而实现了不同租户的虚拟机之间的物理隔离，进而提高了不同租户的虚拟机之间的数据保密性。
Description
本发明实施例涉及计算机技术领域，尤其涉及一种虚拟机创建方法、系统以及主机。
当前，在公有云领域，普通IaaS(Infrastructure as a Service，基础设施即服务)以虚拟化方式实现多个租户的计算资源之间的隔离，这种方式是实现在同一个服务器上创建不同租户的虚拟机，这种隔离本质上是一种逻辑隔离，不同的租户并不会独占专属于自己的物理资源。例如，一个物理机上的不同虚拟机可能分别从属于不同的租户。
然而，当一个服务器上的多个不同的虚拟机分别从属于不同的租户时，不同租户的虚拟机是共享同一个服务器的内存和CPU等硬件资源，一个租户的虚拟机可以从共享资源窃取另一租户的虚拟机存储的数据，不同租户的虚拟机之间数据保密性低。
发明内容
为克服相关技术中存在的不同租户的虚拟机之间数据保密性低的问题，本发明实施例提供一种虚拟机创建方法、系统以及主机。
根据本发明实施例的第一方面，提供一种虚拟机创建方法，应用于包括多个主机的虚拟机创建系统，所述方法包括：虚拟机创建系统首先接收租户的虚拟机创建请求，所述虚拟机创建请求携带所述租户的租户标识；在所述租户为预设租户时，然后虚拟机创建系统再根据租户标识与主机标识的绑定关系确定与所述虚拟机创建请求中的租户标识绑定的主机标识，具有与所述虚拟机创建请求中的租户标识绑定的主机标识的主机为目标主机；其中，具有所述绑定关系中的主机标识的主机仅供创建具有与所述绑定关系中的主机标识绑定的租户标识的租户的虚拟机，所述多个主机包括具有所述绑定关系中的主机标识的主机；之后虚拟机创建系统再根据所述虚拟机创建请求，在所述目标主机上创建所述租户的虚拟机。
在本发明中，租户标识与主机标识之间的绑定关系中的每个主机标识唯一对应一个租户标识；对于对主机有物理隔离需求的任意一个租户，虚拟机创建系统只会在具有与该租户的租户标识对应的主机标识的主机中创建该租户的虚拟机，而不会在具有与其他租户的租户标识对应的主机标识的主机中创建该租户的虚拟机，也即，具有与该租户的租户标识对应的主机标识的主机中只会存在该租户的虚拟机，而不会存在其他用户的虚拟机；从而实现了不同租户的虚拟机之间的物理隔离，进而提高了不同租户的虚拟机之间的数据保密性。
在第一方面，还有如下可选设计；
可选地，根据租户标识与主机标识的绑定关系确定与所述虚拟机创建请求中的租户
标识绑定的主机标识之前，所述方法还包括：虚拟机创建系统可以根据所述虚拟机创建请求中的租户标识，判断所述租户是否为所述预设租户，所述预设租户是指对主机有物理隔离需求的租户。
在第一方面，还有如下可选设计；
可选地，在所述租户不为所述预设租户时，此时虚拟机创建系统就无需单独为所述租户分配一个主机，因此，为了节省主机，虚拟机创建系统可以从所述多个主机中的除所述绑定关系包括的主机标识的主机以外的主机中确定任一个主机来创建所述租户的虚拟机，或者，虚拟机创建系统也可以根据虚拟机资源调度策略从所述多个主机中的除所述绑定关系包括的主机标识的主机以外的主机中确定一个主机来创建所述租户的虚拟机。
在第一方面，还有如下可选设计；
可选地，所述虚拟机创建系统根据租户标识与主机标识的绑定关系确定与所述虚拟机创建请求中的租户标识绑定的主机标识，包括：若虚拟机创建系统根据租户标识与主机标识的绑定关系确定的与所述虚拟机创建请求中的租户标识绑定的主机标识为一个，则该个主机标识为所述目标主机的主机标识；若虚拟机创建系统根据租户标识与主机标识的绑定关系确定的与所述虚拟机创建请求中的租户标识绑定的主机标识为多个，则虚拟机创建系统可以从确定的多个主机标识中选择任一个主机标识为所述目标主机的主机标识；或者虚拟机创建系统也可以根据虚拟机资源调度策略从确定的多个主机标识中选择任一个主机标识为所述目标主机的主机标识。例如，资源调度策略可以为负载均衡策略等等。例如，为了实现负载均衡，当确定的与所述虚拟机创建请求中的租户标识绑定的主机标识为多个时，虚拟机创建系统可以这些主机中，可以挑选剩余存储空间最大的和/或剩余计算资源最大的主机，并作为目标主机。
在第一方面，为了避免丢失其他数据，以及避免在主机中创建虚拟机时影响运行其他已创建的虚拟机的稳定性，还有如下可选设计；
可选地，所述虚拟机创建请求携带有资源需求参数；所述虚拟机创建系统根据租户标识与主机标识的绑定关系确定与所述虚拟机创建请求中的租户标识绑定的主机标识，包括：若虚拟机创建系统根据租户标识与主机标识的绑定关系确定的与所述虚拟机创建请求中的租户标识绑定的主机标识为一个，则该个主机标识为所述目标主机的主机标识；若虚拟机创建系统根据租户标识与主机标识的绑定关系确定的与所述虚拟机创建请求中的租户标识绑定的主机标识为多个，则虚拟机创建系统可以在具有确定的多个主机标识的多个主机中选择满足所述资源需求参数的主机作为目标主机，并确定所述目标主机的主机标识。
在第一方面，还有如下可选设计；
可选地，所述虚拟机创建系统在具有确定的多个主机标识的多个主机中选择满足所述资源需求参数的主机作为目标主机，包括：若虚拟机创建系统在具有确定的多个主机标识的多个主机中满足所述资源需求参数的主机为一个，则该个主机为所述目标主机；若虚拟机创建系统在具有确定的多个主机标识的多个主机中满足所述资源需求参数的主
机为多个，则虚拟机创建系统可以从满足所述资源需求参数的多个主机中选择任一个主机作为所述目标主机，或者虚拟机创建系统也可以从满足所述资源需求参数的多个主机中根据资源调度策略确定一个主机作为所述目标主机。例如，资源调度策略可以为负载均衡策略等等。例如，为了实现负载均衡，当剩余存储空间大于或等于待创建的虚拟机的占用空间、且剩余计算资源大于创建待创建的虚拟机所需占用的计算资源的主机为多个时，虚拟机创建系统可以这些主机中，可以挑选剩余存储空间最大的和/或剩余计算资源最大的主机，并作为目标主机。
根据本发明实施例的第二方面，提供一种虚拟机创建系统，所述系统包括：接收单元和处理单元，其中，接收单元，用于接收租户的虚拟机创建请求，所述虚拟机创建请求携带所述租户的租户标识；处理单元，用于在所述租户为预设租户时，根据租户标识与主机标识的绑定关系确定与所述虚拟机创建请求中的租户标识绑定的主机标识，具有与所述虚拟机创建请求中的租户标识绑定的主机标识的主机为目标主机，以及根据所述虚拟机创建请求，在所述目标主机上创建所述租户的虚拟机。其中，具有所述绑定关系中的主机标识的主机仅供创建具有与所述绑定关系中的主机标识绑定的租户标识的租户的虚拟机，所述多个主机包括具有所述绑定关系中的主机标识的主机。
在本发明中，租户标识与主机标识之间的绑定关系中的每个主机标识唯一对应一个租户标识；对于对主机有物理隔离需求的任意一个租户，虚拟机创建系统只会在具有与该租户的租户标识对应的主机标识的主机中创建该租户的虚拟机，而不会在具有与其他租户的租户标识对应的主机标识的主机中创建该租户的虚拟机，也即，具有与该租户的租户标识对应的主机标识的主机中只会存在该租户的虚拟机，而不会存在其他用户的虚拟机；从而实现了不同租户的虚拟机之间的物理隔离，进而提高了不同租户的虚拟机之间的数据保密性。
在第二方面，还有如下可选设计；
可选地，所述处理单元，还用于根据所述虚拟机创建请求中的租户标识，判断所述租户是否为所述预设租户，所述预设租户是指对主机有物理隔离需求的租户。
在第二方面，还有如下可选设计；
可选地，在所述租户不为所述预设租户时，处理单元就无需单独为所述租户分配一个主机，因此，为了节省主机，此时所述处理单元，还用于从所述多个主机中的除所述绑定关系包括的主机标识的主机以外的主机中确定任一个主机来创建所述租户的虚拟机，或者根据虚拟机资源调度策略从所述多个主机中的除所述绑定关系包括的主机标识的主机以外的主机中确定一个主机来创建所述租户的虚拟机。
在第二方面，为了实现负载均衡，还有如下可选设计；
可选地，所述处理单元，还用于若根据租户标识与主机标识的绑定关系确定的与所述虚拟机创建请求中的租户标识绑定的主机标识为一个，则该个主机标识为所述目标主机的主机标识；若根据租户标识与主机标识的绑定关系确定的与所述虚拟机创建请求中的租户标识绑定的主机标识为多个，则从确定的多个主机标识中选择任一个主机标识为所述目标主机的主机标识；或者根据虚拟机资源调度策略从确定的多个主机标识中选择
任一个主机标识为所述目标主机的主机标识。例如，资源调度策略可以为负载均衡策略等等。例如，为了实现负载均衡，当确定的与所述虚拟机创建请求中的租户标识绑定的主机标识为多个时，所述处理单元可以这些主机中，可以挑选剩余存储空间最大的和/或剩余计算资源最大的主机，并作为目标主机。
在第二方面，为了避免丢失其他数据，以及避免在主机中创建虚拟机时影响运行其他已创建的虚拟机的稳定性，还有如下可选设计；
可选地，所述虚拟机创建请求携带有资源需求参数；所述处理单元，还用于：若根据租户标识与主机标识的绑定关系确定的与所述虚拟机创建请求中的租户标识绑定的主机标识为一个，则该个主机标识为所述目标主机的主机标识；若根据租户标识与主机标识的绑定关系确定的与所述虚拟机创建请求中的租户标识绑定的主机标识为多个，则在具有确定的多个主机标识的多个主机中选择满足所述资源需求参数的主机作为目标主机，并确定所述目标主机的主机标识。
在第二方面，为了实现负载均衡，还有如下可选设计；
可选地，所述处理单元，还用于：若在具有确定的多个主机标识的多个主机中满足所述资源需求参数的主机为一个，则该个主机为所述目标主机；若在具有确定的多个主机标识的多个主机中满足所述资源需求参数的主机为多个，则从满足所述资源需求参数的多个主机中选择任一个主机作为所述目标主机，或者从满足所述资源需求参数的多个主机中根据资源调度策略确定一个主机作为所述目标主机。例如，资源调度策略可以为负载均衡策略等等。例如，为了实现负载均衡，当剩余存储空间大于或等于待创建的虚拟机的占用空间、且剩余计算资源大于创建待创建的虚拟机所需占用的计算资源的主机为多个时，所述处理单元可以这些主机中，可以挑选剩余存储空间最大的和/或剩余计算资源最大的主机，并作为目标主机。
第三方面，本申请实施例还提供了一种主机，包括至少一个处理器、存储器和通信接口；所述至少一个处理器、所述存储器和所述通信接口均通过总线连接；
所述存储器，用于存储计算机执行指令；
所述至少一个处理器，用于执行所述存储器存储的计算机执行指令，使得所述主机通过所述通信接口与虚拟机创建系统中的其它主机进行数据交互来执行上述第一方面或第一方面的各可能设计提供的虚拟机创建方法，所述虚拟机创建系统包括所述主机。
第四方面，提供一种计算机可读存储介质，计算机可读存储介质中存储有计算机执行指令，当主机的至少一个处理器执行该计算机执行指令时，主机执行上述第一方面或者第一方面的各种可能设计提供的虚拟机创建方法。
第五方面，提供一种计算机程序产品，该计算机程序产品包括计算机执行指令，该计算机执行指令存储在计算机可读存储介质中。主机的至少一个处理器可以从计算机可读存储介质读取该计算机执行指令，至少一个处理器执行该计算机执行指令使得主机实施上述第一方面或者第一方面的各种可能设计提供的虚拟机创建方法。
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本发明的实施例，并与说明书一起用于解释本发明实施例的原理。
图1是根据一示例性实施例示出的一种云计算平台的示意图；
图2是根据一示例性实施例示出的一种虚拟机创建方法的流程图；
图3是根据一示例性实施例示出的一种虚拟机创建系统的框图；
图4是根据一示例性实施例示出的一种虚拟机创建系统的框图。
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本发明实施例相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本发明实施例的一些方面相一致的系统和方法的例子。
图1是本发明实施例提供的一种云计算平台的示意图，参见图1，云计算平台中包括虚拟机创建系统1和多个主机2，虚拟机创建系统1与每一个主机2分别通信连接，虚拟机创建系统1可以控制每一个主机2，例如，虚拟机创建系统1可以在任意一个主机2中创建虚拟机等，虚拟机创建系统可以集成在某一个主机2上。主机2可以是服务器或者个人计算机，或者可以是其他具有计算能力的计算设备。
图2是根据一示例性实施例示出的一种虚拟机创建方法的流程图，该方法的执行主体为虚拟机创建系统，该方法包括如图2所示的步骤。
在步骤S101中，接收租户的虚拟机创建请求，该虚拟机创建请求携带该的租户标识；
在本发明实施例中，当某一租户需要在创建虚拟机时，可以向虚拟机创建系统发送虚拟机创建请求，该虚拟机创建请求中至少携带该租户的租户标识。
在本发明实施例中，该租户可能为预设用户，也可能不为预设用户。预设租户可以是指对主机有物理隔离需求的租户。
其中，当某一租户为对主机有物理隔离需求的租户时，该租户往往对虚拟机的运行环境的要求较高，因此在创建虚拟机时需要独占一个主机，而不与其他租户的虚拟机共享一个主机。也即，如果该租户需要一个主机上创建虚拟机，则此时该主机中不能存在其他租户的虚拟机，且待该租户在该主机中创建该租户的虚拟机之后，在该主机中只能继续创建该租户的虚拟机，而无法创建其他租户的虚拟机。
当该租户不为对主机有物理隔离需求的租户时，该租户往往对虚拟机的运行环境的要求较低；该租户可以不独占一个主机来创建该租户的虚拟机，可以与其他租户的虚拟机共享一个主机。也即，如果该租户需要在一个主机上创建虚拟机，此时该主机中可以
存在其他租户的虚拟机；待该租户在该主机中创建该租户的虚拟机之后，在该主机中还可以继续创建其他租户的虚拟机。
因此，如果该租户需要创建虚拟机，虚拟机创建系统需要确定出该租户是否为对主机有物理隔离需求的租户。为了使得虚拟机创建系统能够确定出该租户是否为对主机有物理隔离需求的租户，该租户在向虚拟机创建系统发送虚拟机创建请求之前，租户需要在虚拟创建请求消息中添加该租户的租户标识，这样虚拟机创建系统就可以根据租户标识确定该租户是否为对主机有物理隔离需求的租户。
在本发明一个实施例中，起初每一个租户都不为对主机有物理隔离需求的租户，每一个租户都有租户标识；租户标识用于唯一标识租户，例如租户标识可以为该租户的名称或编号。
对于任意一个租户而言，当该租户需要独占一个主机创建虚拟机时，该租户可以向虚拟机创建系统申请独占主机的资格，申请通过之后，该租户即为对主机有物理隔离需求的租户，虚拟机创建系统就会在该租户的租户标识中添加预设特征标识，用于标识该租户为为对主机有物理隔离需求的租户。
例如，假设每一个租户标识均由4个数字组成。假设该租户的租户标识为“1234”以及预设特征标识为“#”，则在租户标识“1234”中添加预设特征标识“#”得到“1234#”。
因此，虚拟机创建系统可以判断该租户标识中是否携带预设特征标识；当该租户标识中携带预设特征标识时，确定该租户为对主机有物理隔离需求的租户，进而确定该租户为预设租户；当该租户标识中未携带预设特征标识时，确定该租户不为对主机有物理隔离需求的租户，进而确定该租户不为预设租户。
在步骤S102中，在该租户为预设租户时，根据租户标识与主机标识的绑定关系确定与该虚拟机创建请求中的该租户标识绑定的主机标识，具有与该虚拟机创建请求中的该租户标识绑定的该主机标识的主机为目标主机；
其中，具有该绑定关系中的该主机标识的主机仅供创建具有与该绑定关系中的该主机标识绑定的租户标识的租户的虚拟机，多个主机包括具有该绑定关系中的主机标识的主机；该绑定关系中每个主机标识唯一对应一个租户标识。
在本发明实施例中，该绑定关系中可能有一个租户标识同时对应的多个不同的主机标识，例如，当一个租户为对主机有物理隔离需求的租户且该租户需要创建虚拟机的数量很大时，虚拟机创建系统可以从多个主机中给该租户分配至少两个主机，这样，该绑定关系中就存在至少两个与该租户标识绑定的主机标识。
因此，本步骤可以为：若根据租户标识与主机标识的绑定关系确定的与该虚拟机创建请求中的该租户标识绑定的主机标识为一个，则该个主机标识为目标主机的主机标识；若根据租户标识与主机标识的该绑定关系确定的与该虚拟机创建请求中的该租户标识绑定的主机标识为多个，则从确定的多个主机标识中选择任一个主机标识为目标主机的主机标识。
在本发明实施例中，在主机中创建虚拟机需要占用主机的资源，例如，主机的计算资源、主机的存储资源以及主机的网络资源等等，在主机的剩余的资源足够的情况下才能在主机中创建虚拟机。例如，虚拟机创建系统中的每一个主机中的存储空间都是有限的，以及，每一个主机中的计算资源也是有限的。然而，虚拟机创建系统在一个主机中创建虚拟机时需要占用主机中的一部分存储空间，且需要占用主机的一部分计算资源，例如主机的CPU的计算资源和内存的计算资源。
对于该绑定关系中的任意一个主机标识，具有该主机标识的主机中可能还未创建虚拟机，也可能已经创建了一个或多个虚拟机，对于该绑定关系中的其他每一个主机标识，同样如此。
因此，当需要在具有该主机标识的主机中创建虚拟机时，需要满足一个条件：具有该主机标识的主机中的剩余存储空间大于或等于待创建的虚拟机的占用空间，否则，为了能够在具有该主机标识的主机中成功创建待创建虚拟机，则需要删除具有该主机标识的主机中的一部分其他数据，以预留出足够的存储空间来创建待创建的虚拟机，但是这样会丢失该一部分数据。
其次，假设具有该主机标识的主机中的剩余存储空间大于或等于待创建的虚拟机的占用空间，但是在具有该主机标识的主机中之前创建国虚拟机，且正在运行虚拟机，由于主机运行虚拟机需要占用主机的计算资源，例如，CPU资源和内存资源等，当一个主机中运行的虚拟机越多时，则主机的计算资源的占用率就较高。由于主机在本地创建虚拟机的过程也需要占用主机的计算资源，因此，当一个主机的CPU占用率或者内存占用率过高时，如果还要在该主机中创建虚拟机，则就可能会影响主机运行其他已创建的虚拟机的稳定性。
所以，为了避免丢失其他数据，以及避免在主机中创建虚拟机时影响运行其他已创建的虚拟机的稳定性，该虚拟机创建请求还需要携带有资源需求参数，资源需求参数包括待创建的虚拟机的占用空间、创建虚拟机所需占用的主机的占用资源以及所需占用的主机的网络资源等中的至少一个。
这样，本步骤可以为：若根据租户标识与主机标识的该绑定关系确定的与该虚拟机创建请求中的该租户标识绑定的主机标识为一个，则该个主机标识为目标主机的主机标识；若根据租户标识与主机标识的该绑定关系确定的与该虚拟机创建请求中的该租户标识绑定的主机标识为多个，则在具有确定的多个主机标识的多个主机中选择满足该资源需求参数的主机作为目标主机，并确定该目标主机的主机标识。
其中，在具有确定的多个主机标识的多个主机中选择满足该资源需求参数的主机作为目标主机，包括：
若在具有确定的多个主机标识的多个主机中满足该资源需求参数的主机为一个，则满足该资源需求参数的该个主机为目标主机；若在具有确定的多个主机标识的多个主机中满足该资源需求参数的主机为多个，则从满足该资源需求参数的多个主机中选择任一个主机作为目标主机，或者从满足该资源需求参数的多个主机中根据资源调度策略确定一个主机作为目标主机。
例如，资源调度策略可以为负载均衡策略等等。例如，为了实现负载均衡，当剩余存储空间大于或等于待创建的虚拟机的占用空间、且剩余计算资源大于创建待创建的虚拟机所需占用的计算资源的主机为多个时，虚拟机创建系统可以这些主机中，可以挑选剩余存储空间最大的和/或剩余计算资源最大的主机，并作为目标主机。
在步骤S103中，根据该虚拟机创建请求，在目标主机上创建该租户的虚拟机；
在本发明实施例中，在技术人员建立虚拟机创建系统时，虚拟机创建系统中设置多个主机，此时多个租户可以在同一个主机中分别创建自己的虚拟机。
然而，当一个租户为对主机有物理隔离需求的租户时，该租户在虚拟机创建系统中创建虚拟机时需要独占一个主机创建虚拟机，虚拟机创建系统就会从虚拟机创建系统中选择一个未创建虚拟机的主机，并分配给该租户，之后，选择的该主机即不再是可以被其他租户同时创建虚拟机的主机，也即，只有该租户能够在选择的该主机中创建虚拟机，其他租户不能在选择的该主机中创建虚拟机。
因此，在该租户不为预设租户时，如果虚拟机创建系统中还存在一个共享主机，则虚拟机创建系统可以获取该共享主机，然后执行步骤S104。如果虚拟机创建系统中还存在多个共享主机，控制设备可以从该多个共享主机中选择一个共享主机，然后执行步骤S104。其中，从该多个共享主机中选择一个共享主机的具体选择过程可以参见步骤S103中的选择过程，在此不做详述。
在步骤S104中，在该租户不为预设租户时，从多个主机中的除该绑定关系包括的主机标识的主机以外的主机中确定任一个主机来创建该租户的虚拟机，或者根据虚拟机资源调度策略从该多个主机中的除该绑定关系包括的主机标识的主机以外的主机中确定一个主机来创建该租户的虚拟机。
在本发明实施例中，租户标识与主机标识之间的绑定关系中的每个主机标识唯一对应一个租户标识；对于对主机有物理隔离需求的任意一个租户，虚拟机创建系统只会在具有与该租户的租户标识对应的主机标识的主机中创建该租户的虚拟机，而不会在具有与其他租户的租户标识对应的主机标识的主机中创建该租户的虚拟机，也即，具有与该租户的租户标识对应的主机标识的主机中只会存在该租户的虚拟机，而不会存在其他用户的虚拟机；从而实现了不同租户的虚拟机之间的物理隔离，进而提高了不同租户的虚拟机之间的数据保密性。
图3是根据一示例性实施例示出的一种虚拟机创建系统的框图。参照图3，该系统包括：
接收单元11，用于接收租户的虚拟机创建请求，所述虚拟机创建请求携带所述租户的租户标识；
处理单元12，用于在所述租户为预设租户时，根据租户标识与主机标识的绑定关系确定与所述虚拟机创建请求中的租户标识绑定的主机标识，具有与所述虚拟机创建请求中的租户标识绑定的主机标识的主机为目标主机；其中，具有所述绑定关系中的主机标识的主机仅供创建具有与所述绑定关系中的主机标识绑定的租户标识的租户的虚拟机，
所述多个主机包括具有所述绑定关系中的主机标识的主机；
所述处理单元12，还用于根据所述虚拟机创建请求，在所述目标主机上创建所述租户的虚拟机。
在本发明中，租户标识与主机标识之间的绑定关系中的每个主机标识唯一对应一个租户标识；对于对主机有物理隔离需求的任意一个租户，虚拟机创建系统只会在具有与该租户的租户标识对应的主机标识的主机中创建该租户的虚拟机，而不会在具有与其他租户的租户标识对应的主机标识的主机中创建该租户的虚拟机，也即，具有与该租户的租户标识对应的主机标识的主机中只会存在该租户的虚拟机，而不会存在其他用户的虚拟机；从而实现了不同租户的虚拟机之间的物理隔离，进而提高了不同租户的虚拟机之间的数据保密性。
在一种可选的设计中，所述处理单元12，还用于：
根据所述虚拟机创建请求中的租户标识，判断所述租户是否为所述预设租户，所述预设租户是指对主机有物理隔离需求的租户。
在一种可选的设计中，所述处理单元12，还用于：
在所述租户不为所述预设租户时，从所述多个主机中的除所述绑定关系包括的主机标识的主机以外的主机中确定任一个主机来创建所述租户的虚拟机，或者根据虚拟机资源调度策略从所述多个主机中的除所述绑定关系包括的主机标识的主机以外的主机中确定一个主机来创建所述租户的虚拟机。
在一种可选的设计中，为了实现负载均衡，所述处理单元12，还用于：
若根据租户标识与主机标识的绑定关系确定的与所述虚拟机创建请求中的租户标识绑定的主机标识为一个，则该个主机标识为所述目标主机的主机标识；
若根据租户标识与主机标识的绑定关系确定的与所述虚拟机创建请求中的租户标识绑定的主机标识为多个，则从确定的多个主机标识中选择任一个主机标识为所述目标主机的主机标识；或者根据虚拟机资源调度策略从确定的多个主机标识中选择任一个主机标识为所述目标主机的主机标识。
在一种可选的设计中，为了避免丢失其他数据，以及避免在主机中创建虚拟机时影响运行其他已创建的虚拟机的稳定性，所述虚拟机创建请求携带有资源需求参数；所述处理单元12，还用于：
若根据租户标识与主机标识的绑定关系确定的与所述虚拟机创建请求中的租户标识绑定的主机标识为一个，则该个主机标识为所述目标主机的主机标识；
若根据租户标识与主机标识的绑定关系确定的与所述虚拟机创建请求中的租户标识绑定的主机标识为多个，则在具有确定的多个主机标识的多个主机中选择满足所述资源需求参数的主机作为目标主机，并确定所述目标主机的主机标识。
在一种可选的设计中，为了实现负载均衡，所述处理单元12，还用于：
若在具有确定的多个主机标识的多个主机中满足所述资源需求参数的主机为一个，
则该个主机为所述目标主机；
若在具有确定的多个主机标识的多个主机中满足所述资源需求参数的主机为多个，则从满足所述资源需求参数的多个主机中选择任一个主机作为所述目标主机，或者从满足所述资源需求参数的多个主机中根据资源调度策略确定一个主机作为所述目标主机。
关于上述实施例中的系统，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
其中，虚拟机创建系统是部署在多个主机上的，因此具体执行上述虚拟机创建方法的硬件主体为主机，实现上述虚拟机创建系统的硬件主体也是主机；主机在图4中示意为主机400，即上述方法实施例的主机为图4所示的主机400。
参见图4，主机400包括至少一个处理器401、存储器402和通信接口403；所述至少一个处理器401、所述存储器402和所述通信接口403均通过总线404连接；
所述存储器402，用于存储计算机执行指令；
所述至少一个处理器401，用于执行所述存储器402存储的计算机执行指令，使得所述主机400通过所述通信接口403与虚拟机创建系统中的其它主机进行数据交互来执行上述实施例提供的虚拟机创建方法，或者使得所述主机400通过所述通信接口403与虚拟机创建系统中的其它主机进行数据交互来实现虚拟机创建系统的部分或者全部功能。
至少一个处理器401，可以包括不同类型的处理器401，或者包括相同类型的处理器401；处理器401可以是以下的任一种：中央处理器(Central Processing Unit，简称CPU)、ARM处理器、现场可编程门阵列(Field Programmable Gate Array，简称FPGA)、专用处理器等具有计算处理能力的器件。一种可选实施方式，所述至少一个处理器401还可以集成为众核处理器。
存储器402可以是以下的任一种或任一种组合：随机存取存储器(Random Access Memory，简称RAM)、只读存储器(read only memory，简称ROM)、非易失性存储器(non-volatile memory，简称NVM)、固态硬盘(Solid State Drives，简称SSD)、机械硬盘、磁盘、磁盘整列等存储介质。
通信接口403用于主机400与其他设备(例如虚拟机创建系统中的其他主机)进行数据交互。通信接口403可以是以下的任一种或任一种组合：网络接口(例如以太网接口)、无线网卡等具有网络接入功能的器件。
该总线404可以包括地址总线、数据总线、控制总线等，为便于表示，图4用一条粗线表示该总线。总线404可以是以下的任一种或任一种组合：工业标准体系结构(Industry Standard Architecture，简称ISA)总线、外设组件互连标准(Peripheral Component Interconnect，简称PCI)总线、扩展工业标准结构(Extended Industry Standard Architecture，简称EISA)总线等有线数据传输的器件。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本发明的其它
实施方案。本申请旨在涵盖本发明实施例的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本发明实施例的一般性原理并包括本发明实施例未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本发明实施例的真正范围和精神由所附的权利要求指出。
应当理解的是，本发明实施例并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本发明实施例的范围仅由所附的权利要求来限制。
Claims (13)
- 一种虚拟机创建方法，其特征在于，应用于包括多个主机的虚拟机创建系统，所述方法包括：接收租户的虚拟机创建请求，所述虚拟机创建请求携带所述租户的租户标识；在所述租户为预设租户时，根据租户标识与主机标识的绑定关系确定与所述虚拟机创建请求中的租户标识绑定的主机标识，具有与所述虚拟机创建请求中的租户标识绑定的主机标识的主机为目标主机；其中，具有所述绑定关系中的主机标识的主机仅供创建具有与所述绑定关系中的主机标识绑定的租户标识的租户的虚拟机，所述多个主机包括具有所述绑定关系中的主机标识的主机；根据所述虚拟机创建请求，在所述目标主机上创建所述租户的虚拟机。
- 根据权利要求1所述的方法，其特征在于，根据租户标识与主机标识的绑定关系确定与所述虚拟机创建请求中的租户标识绑定的主机标识之前，所述方法还包括：根据所述虚拟机创建请求中的租户标识，判断所述租户是否为所述预设租户，所述预设租户是指对主机有物理隔离需求的租户。
- 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：在所述租户不为所述预设租户时，从所述多个主机中的除所述绑定关系包括的主机标识的主机以外的主机中确定任一个主机来创建所述租户的虚拟机，或者根据虚拟机资源调度策略从所述多个主机中的除所述绑定关系包括的主机标识的主机以外的主机中确定一个主机来创建所述租户的虚拟机。
- 根据权利要求1至3任一项所述的方法，其特征在于，所述根据租户标识与主机标识的绑定关系确定与所述虚拟机创建请求中的租户标识绑定的主机标识，包括：若根据租户标识与主机标识的绑定关系确定的与所述虚拟机创建请求中的租户标识绑定的主机标识为一个，则该个主机标识为所述目标主机的主机标识；若根据租户标识与主机标识的绑定关系确定的与所述虚拟机创建请求中的租户标识绑定的主机标识为多个，则从确定的多个主机标识中选择任一个主机标识为所述目标主机的主机标识；或者根据虚拟机资源调度策略从确定的多个主机标识中选择任一个主机标识为所述目标主机的主机标识。
- 根据权利要求1至3任一项所述的方法，其特征在于，所述虚拟机创建请求携带有资源需求参数；所述根据租户标识与主机标识的绑定关系确定与所述虚拟机创建请求中的租户标识绑定的主机标识，包括：若根据租户标识与主机标识的绑定关系确定的与所述虚拟机创建请求中的租户标识绑定的主机标识为一个，则该个主机标识为所述目标主机的主机标识；若根据租户标识与主机标识的绑定关系确定的与所述虚拟机创建请求中的租户标识绑定的主机标识为多个，则在具有确定的多个主机标识的多个主机中选择满足所述资源需求参数的主机作为目标主机，并确定所述目标主机的主机标识。
- 根据权利要求5所述的方法，其特征在于，所述在具有确定的多个主机标识的多个主机中选择满足所述资源需求参数的主机作为目标主机，包括：若在具有确定的多个主机标识的多个主机中满足所述资源需求参数的主机为一个，则该个主机为所述目标主机；若在具有确定的多个主机标识的多个主机中满足所述资源需求参数的主机为多个，则从满足所述资源需求参数的多个主机中选择任一个主机作为所述目标主机，或者从满足所述资源需求参数的多个主机中根据资源调度策略确定一个主机作为所述目标主机。
- 一种虚拟机创建系统，其特征在于，所述系统包括：接收单元，用于接收租户的虚拟机创建请求，所述虚拟机创建请求携带所述租户的租户标识；处理单元，用于在所述租户为预设租户时，根据租户标识与主机标识的绑定关系确定与所述虚拟机创建请求中的租户标识绑定的主机标识，具有与所述虚拟机创建请求中的租户标识绑定的主机标识的主机为目标主机；其中，具有所述绑定关系中的主机标识的主机仅供创建具有与所述绑定关系中的主机标识绑定的租户标识的租户的虚拟机，所述多个主机包括具有所述绑定关系中的主机标识的主机；所述处理单元，还用于根据所述虚拟机创建请求，在所述目标主机上创建所述租户的虚拟机。
- 根据权利要求7所述的系统，其特征在于，所述处理单元，还用于：根据所述虚拟机创建请求中的租户标识，判断所述租户是否为所述预设租户，所述预设租户是指对主机有物理隔离需求的租户。
- 根据权利要求7或8所述的系统，其特征在于，所述处理单元，还用于：在所述租户不为所述预设租户时，从所述多个主机中的除所述绑定关系包括的主机标识的主机以外的主机中确定任一个主机来创建所述租户的虚拟机，或者根据虚拟机资源调度策略从所述多个主机中的除所述绑定关系包括的主机标识的主机以外的主机中确定一个主机来创建所述租户的虚拟机。
- 根据权利要求7至9任一项所述的系统，其特征在于，所述处理单元，还用于：若根据租户标识与主机标识的绑定关系确定的与所述虚拟机创建请求中的租户标识绑定的主机标识为一个，则该个主机标识为所述目标主机的主机标识；若根据租户标识与主机标识的绑定关系确定的与所述虚拟机创建请求中的租户标识绑定的主机标识为多个，则从确定的多个主机标识中选择任一个主机标识为所述目标主机的主机标识；或者根据虚拟机资源调度策略从确定的多个主机标识中选择任一个主机标识为所述目标主机的主机标识。
- 根据权利要求7至9任一项所述的系统，其特征在于，所述虚拟机创建请求携带有资源需求参数；所述处理单元，还用于：若根据租户标识与主机标识的绑定关系确定的与所述虚拟机创建请求中的租户标识绑定的主机标识为一个，则该个主机标识为所述目标主机的主机标识；若根据租户标识与主机标识的绑定关系确定的与所述虚拟机创建请求中的租户标识绑定的主机标识为多个，则在具有确定的多个主机标识的多个主机中选择满足所述资源需求参数的主机作为目标主机，并确定所述目标主机的主机标识。
- 根据权利要求11所述的系统，其特征在于，所述处理单元，还用于：若在具有确定的多个主机标识的多个主机中满足所述资源需求参数的主机为一个，则该个主机为所述目标主机；若在具有确定的多个主机标识的多个主机中满足所述资源需求参数的主机为多个，则从满足所述资源需求参数的多个主机中选择任一个主机作为所述目标主机，或者从满足所述资源需求参数的多个主机中根据资源调度策略确定一个主机作为所述目标主机。
- 一种主机，其特征在于，包括至少一个处理器、存储器和通信接口；所述至少一个处理器、所述存储器和所述通信接口均通过总线连接；所述存储器，用于存储计算机执行指令；所述至少一个处理器，用于执行所述存储器存储的计算机执行指令，使得所述主机通过所述通信接口与虚拟机创建系统中的其它主机进行数据交互来执行权利要求1至6任一项所述的虚拟机创建方法，所述虚拟机创建系统包括所述主机。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610717758.6 | 2016-08-24 | ||
| CN201610717758.6A CN106354544A (zh) | 2016-08-24 | 2016-08-24 | 虚拟机创建方法、系统以及主机 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2018036103A1 true WO2018036103A1 (zh) | 2018-03-01 |
Family
ID=57844815
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2017/072987 WO2018036103A1 (zh) | 2016-08-24 | 2017-02-06 | 虚拟机创建方法、系统以及主机 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN106354544A (zh) |
| WO (1) | WO2018036103A1 (zh) |
Families Citing this family (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106354544A (zh) * | 2016-08-24 | 2017-01-25 | 华为技术有限公司 | 虚拟机创建方法、系统以及主机 |
| CN108667886B (zh) * | 2017-04-01 | 2020-07-28 | 华为技术有限公司 | 提供PaaS服务的方法、管理系统和云计算服务架构 |
| CN108574718B (zh) * | 2017-04-19 | 2021-03-26 | 北京金山云网络技术有限公司 | 一种云主机创建方法及装置 |
| CN108574719B (zh) * | 2017-04-19 | 2021-04-20 | 北京金山云网络技术有限公司 | 一种云主机创建方法及装置 |
| CN107343008A (zh) * | 2017-07-17 | 2017-11-10 | 山东超越数控电子有限公司 | 一种抗访问模式泄露的数据安全隔离与共享实现方法 |
| CN109542580A (zh) * | 2017-09-22 | 2019-03-29 | 中兴通讯股份有限公司 | 一种资源管理方法、装置、设备及计算机可读存储介质 |
| CN107864131A (zh) * | 2017-11-03 | 2018-03-30 | 郑州云海信息技术有限公司 | 一种实现Kubernetes集群多租户网络隔离的方法及系统 |
| CN112214293A (zh) * | 2017-11-08 | 2021-01-12 | 华为技术有限公司 | 一种无服务器架构下业务部署的方法和函数管理平台 |
| CN107959689B (zh) * | 2018-01-10 | 2020-09-25 | 北京工业大学 | 一种云平台租户网络隔离测试方法 |
| CN108170520A (zh) * | 2018-01-29 | 2018-06-15 | 北京搜狐新媒体信息技术有限公司 | 一种云计算资源管理方法及装置 |
| CN108399106A (zh) * | 2018-02-28 | 2018-08-14 | 华为技术有限公司 | 管理物理主机的方法和装置 |
| CN108614727B (zh) * | 2018-03-23 | 2021-04-20 | 华为技术有限公司 | 一种虚拟机创建方法及装置 |
| CN108551399B (zh) * | 2018-03-29 | 2021-08-13 | 深信服科技股份有限公司 | 一种云环境下服务的部署方法、系统及相关装置 |
| CN108874490A (zh) * | 2018-06-14 | 2018-11-23 | 上海掌门科技有限公司 | 界面显示方法和装置 |
| CN109739612B (zh) * | 2018-11-22 | 2021-10-26 | 海光信息技术股份有限公司 | 虚拟机进程的调度方法、装置、设备和存储介质 |
| CN109634720B (zh) | 2018-12-13 | 2021-11-19 | 郑州云海信息技术有限公司 | 一种多虚拟机共享fpga板卡的方法、系统及装置 |
| CN112019366B (zh) * | 2019-05-31 | 2022-02-01 | 北京金山云网络技术有限公司 | 物理主机的租赁方法、装置、云平台及可读存储介质 |
| CN112702252B (zh) * | 2019-10-23 | 2024-02-02 | 华为云计算技术有限公司 | 一种报文处理方法、系统及相关设备 |
| CN111736960B (zh) * | 2020-08-10 | 2020-12-22 | 北京信安世纪科技股份有限公司 | 基于软件隔离的服务提供方法、设备及存储介质 |
| CN113032107B (zh) * | 2021-05-24 | 2022-05-10 | 北京金山云网络技术有限公司 | 一种云数据库的资源管理方法、装置及系统 |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103797462A (zh) * | 2013-10-23 | 2014-05-14 | 华为技术有限公司 | 一种创建虚拟机的方法和装置 |
| CN103810015A (zh) * | 2012-11-09 | 2014-05-21 | 华为技术有限公司 | 虚拟机创建方法和设备 |
| CN104753852A (zh) * | 2013-12-25 | 2015-07-01 | 中国移动通信集团公司 | 一种虚拟化平台、安全防护方法及装置 |
| CN105446792A (zh) * | 2014-08-27 | 2016-03-30 | 联想(北京)有限公司 | 一种虚拟机的部署方法、部署装置和管理节点 |
| CN106354544A (zh) * | 2016-08-24 | 2017-01-25 | 华为技术有限公司 | 虚拟机创建方法、系统以及主机 |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103139159B (zh) * | 2011-11-28 | 2015-11-25 | 上海贝尔股份有限公司 | 云计算架构中的虚拟机之间的安全通信 |
| CN104348881B (zh) * | 2013-08-08 | 2018-11-30 | 中国电信股份有限公司 | 云管理平台中的用户资源划分方法与装置 |
| WO2015149253A1 (zh) * | 2014-03-31 | 2015-10-08 | 华为技术有限公司 | 数据中心的虚拟网络管理方法及数据中心系统 |
| CN104468574B (zh) * | 2014-12-05 | 2018-03-23 | 中国联合网络通信集团有限公司 | 一种虚拟机动态获取ip地址的方法、系统及装置 |
| CN105631316A (zh) * | 2015-12-25 | 2016-06-01 | 曙光信息产业(北京)有限公司 | 一种虚拟化资源的管理方法和装置 |
| CN105577675A (zh) * | 2015-12-31 | 2016-05-11 | 深圳前海微众银行股份有限公司 | 多租户资源管理的方法及装置 |
-
2016
- 2016-08-24 CN CN201610717758.6A patent/CN106354544A/zh active Pending
-
2017
- 2017-02-06 WO PCT/CN2017/072987 patent/WO2018036103A1/zh active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103810015A (zh) * | 2012-11-09 | 2014-05-21 | 华为技术有限公司 | 虚拟机创建方法和设备 |
| CN103797462A (zh) * | 2013-10-23 | 2014-05-14 | 华为技术有限公司 | 一种创建虚拟机的方法和装置 |
| CN104753852A (zh) * | 2013-12-25 | 2015-07-01 | 中国移动通信集团公司 | 一种虚拟化平台、安全防护方法及装置 |
| CN105446792A (zh) * | 2014-08-27 | 2016-03-30 | 联想(北京)有限公司 | 一种虚拟机的部署方法、部署装置和管理节点 |
| CN106354544A (zh) * | 2016-08-24 | 2017-01-25 | 华为技术有限公司 | 虚拟机创建方法、系统以及主机 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106354544A (zh) | 2017-01-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2018036103A1 (zh) | 虚拟机创建方法、系统以及主机 | |
| US10778521B2 (en) | Reconfiguring a server including a reconfigurable adapter device | |
| US11061712B2 (en) | Hot-plugging of virtual functions in a virtualized environment | |
| US11855904B2 (en) | Automated migration of compute instances to isolated virtual networks | |
| JP5510556B2 (ja) | 仮想マシンのストレージスペースおよび物理ホストを管理するための方法およびシステム | |
| JP5837206B2 (ja) | 分離された仮想空間を提供するための方法および装置 | |
| WO2017133203A1 (zh) | 一种执行环境的虚拟化、虚拟执行环境的访问方法及装置 | |
| US9639402B2 (en) | Systems and methods for automatic hardware provisioning based on application characteristics | |
| US20140214922A1 (en) | Method of providing virtual machine and service gateway for real-time virtual desktop service | |
| US8930507B2 (en) | Physical memory shared among logical partitions in a VLAN | |
| US8635318B1 (en) | Message broadcast protocol which handles configuration changes in a cluster of virtual servers | |
| WO2016138638A1 (zh) | 虚拟机的资源分配方法及装置 | |
| CN112099941A (zh) | 实现硬件加速处理的方法、设备和系统 | |
| WO2015043147A1 (zh) | 一种虚拟机内存数据的迁移方法及相关装置和集群系统 | |
| US11924117B2 (en) | Automated local scaling of compute instances | |
| TW200925878A (en) | System and method for management of an IOV adapter through a virtual intermediary in an IOV management partition | |
| WO2019148854A1 (zh) | 虚拟化网元设备的部署方法以及装置 | |
| US20150370582A1 (en) | At least one user space resident interface between at least one user space resident virtual appliance and at least one virtual data plane | |
| JP2014517419A (ja) | ネットワークのセグメント化によるネイティブクラウドコンピューティング | |
| US20200219225A1 (en) | Session coordination for auto-scaled virtualized graphics processing | |
| WO2018107945A1 (zh) | 一种实现硬件资源分配的方法、装置及存储介质 | |
| US11861406B2 (en) | Dynamic microservices allocation mechanism | |
| US20180246772A1 (en) | Method and apparatus for allocating a virtual resource in network functions virtualization network | |
| US20110246600A1 (en) | Memory sharing apparatus | |
| US10652094B2 (en) | Network traffic management for virtualized graphics devices |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 17842529 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 17842529 Country of ref document: EP Kind code of ref document: A1 |