WO2017113895A1 - Method and device for creating virtual machine - Google Patents

Abstract

Disclosed are a method and device for creating a virtual machine, belonging to the field of communications. The method comprises: negotiating with a volume creation entity a compute node where a processing module and a volume comprised by a virtual machine to be created are located; creating the processing module on the compute node (304); receiving volume identification information about the volume sent by the volume creation entity, wherein the volume is created by the volume creation entity on the compute node (306); and according to the volume identification information, mounting the volume on the processing module, so as to form the virtual machine to be created (308). The device comprises a processing unit and a receiving unit. The method and device can satisfy the performance requirement of reading and writing a volume at a high speed.

Description

Method and device for creating virtual machine Technical field

The present invention relates to the field of communications, and in particular, to a method and an apparatus for creating a virtual machine.

Background technique

Openstack (open source cloud management platform) is an open source cloud platform for creating virtual machines. The virtual machine includes processing modules and volumes for processing modules for read and write access. Openstack provides Nova (computing resource management) components and Cinder (block storage resource management) component, which is used to create processing modules and volumes.

When a virtual machine is created, the Nova component obtains the virtual machine specification information of the virtual machine to be created, selects a computing node, and creates a processing module of the virtual machine on the computing node according to the virtual machine specification information; the Cinder component acquires the virtual machine to be created. Volume specification information, selecting a computing node, creating a volume on the computing node according to the volume specification information, and sending volume identification information of the volume to the Nova component; the Nova component mounts the volume according to the volume identification information On the processing module, get the virtual machine to be created.

In the process of implementing the present invention, the inventors have found that the prior art has at least the following problems:

The compute node where the created processing module resides and the compute node where the created volume resides may be different, so that the processing module can only read and write volumes remotely through the network, which cannot meet the performance requirements of high-speed read-write volumes.

Summary of the invention

In order to meet the performance requirements of high speed read and write volumes, the present invention provides a method and apparatus for creating a virtual machine. The technical solution is as follows:

In a first aspect, a method of creating a virtual machine is provided, the method comprising:

Negotiating, with the volume creation entity, a processing module to be created by the virtual machine and a computing node where the volume is located;

Creating the processing module on the computing node;

Receiving volume identification information of the volume sent by the volume creation entity, where the volume is created by the volume creation entity on the computing node;

And mounting the volume on the processing module to form the virtual machine to be created according to the volume identifier information.

In the first aspect, the processing module included in the virtual machine to be created is negotiated with the volume creation entity and The compute node where the volume resides ensures that the processing module and the volume are created on the same compute node, so that the processing module reads and writes the access volume to read and write access to the local storage resources to meet the performance requirements of high-speed read and write volumes.

With reference to the first aspect, in a first possible implementation of the first aspect, the processing, by the volume creation entity, the processing module and the computing node where the volume is to be created, including:

Obtaining, according to virtual machine specification information of the virtual machine to be created, a computing node that meets the virtual machine specification information;

Sending node identification information of the computing node to the volume creation entity.

In the first possible implementation manner of the first aspect, since the node identification information of the selected computing node is directly sent to the volume creation entity, it is ensured that the computing node that creates the volume and the computing node that creates the processing module are the same computing node.

With reference to the first aspect, in a second possible implementation manner of the first aspect, the determining, by the volume creation entity, the processing module and the computing node where the volume is to be created, including:

Obtaining, according to virtual machine specification information of the virtual machine to be created, a node list, where the node list includes one computing node that satisfies the virtual machine specification information;

Sending the node list to a volume creation entity, the node list being used by the volume creation entity to select a computing node from the node list;

Receiving node identification information of the selected one of the computing nodes sent by the volume creation entity.

In a second possible implementation of the first aspect, since the node list is sent to the volume creation entity, it is guaranteed that the volume creation entity can select a compute node that satisfies the volume specification information.

With reference to the first aspect, in a third possible implementation manner of the first aspect, the determining, by the volume creation entity, the processing module and the computing node where the volume is to be created by the virtual machine to be created includes:

Receiving the node identification information of the computing node sent by the volume creation entity, where the computing node is the volume specification information acquired by the volume creation entity and satisfying the volume corresponding to the virtual machine to be created.

In a third possible implementation manner of the first aspect, the computing node that creates the volume and the computing node that creates the processing module are the same computing node because the node identification information of the computing node sent by the volume creation entity is received.

With reference to the first aspect, in a fourth possible implementation manner of the first aspect, the determining, by the volume creation entity, the processing module and the computing node where the volume is to be created by the virtual machine to be created includes:

Receiving, by the volume creation entity, a node list, where the node list includes at least one computing node that meets volume specification information of a volume corresponding to the virtual machine to be created;

Selecting a computing node from the list of nodes;

Sending node identification information of the selected computing node to the volume creation entity.

In a fourth possible implementation of the first aspect, since the node list sent by the volume creation entity is received, it is guaranteed that the computing node that can satisfy the virtual machine specification information can be selected.

In a second aspect, a method of creating a virtual machine is provided, the method comprising:

Negotiating, with the processing module creation entity, a processing module and a computing node where the volume is to be created by the virtual machine to be created;

Creating the volume on the compute node;

Transmitting, to the processing module creation entity, volume identification information of the volume, the volume identification information being used by the processing module creation entity to mount the volume in the processing module after creating the processing module on the computing node Processing the module to form the virtual machine to be created.

In the second aspect, since the processing module included in the virtual machine to be created and the computing node where the volume is located are negotiated with the processing module creation entity, it is ensured that the processing module is created and the volume is created on the same computing node, so that the processing module reads and writes the access volume. The essence is read and write access to local storage resources to meet the performance requirements of high-speed read and write volumes.

With reference to the second aspect, in a first possible implementation manner of the second aspect, the processing module that is to be created by the processing module and the computing node that is included in the virtual machine includes:

Obtaining, by the volume specification information of the volume corresponding to the virtual machine to be created, a computing node that meets the volume specification information;

Sending node identification information of the computing node to the processing module creation entity.

In a first possible implementation manner of the second aspect, since the node identification information of the selected computing node is directly sent to the processing module creation entity, it is ensured that the computing node that creates the volume and the computing node that creates the processing module are the same computing node.

With reference to the second aspect, in a second possible implementation manner of the second aspect, the processing module that is to be created by the processing module and the computing node that is included in the virtual machine to be created includes:

Obtaining, according to volume specification information of a volume corresponding to the virtual machine to be created, a node list, where the node list includes one to a computing node that satisfies the volume specification information;

Sending, to the processing module creation entity, the node list, where the node list is used by the processing module creation entity to select a computing node from the node list;

Receiving node identification information of the selected one of the computing nodes sent by the processing module creation entity.

In a second possible implementation of the second aspect, since the node list is sent to the processing module creation entity, it is ensured that the processing module creation entity can select a computing node that satisfies the virtual machine specification information.

With reference to the second aspect, in a third possible implementation manner of the second aspect, the processing module, the processing module, and the computing node, where the volume is to be created, are:

The receiving processing module creates the node identification information of the computing node sent by the entity, where the computing node is the virtual machine specification information acquired by the processing module creation entity and meets the virtual machine to be created.

In a third possible implementation manner of the second aspect, the receiving processing module creates the node identification information of the computing node sent by the entity, and ensures that the computing node that creates the volume and the computing node that creates the processing module are the same computing node.

With reference to the second aspect, in a fourth possible implementation manner of the second aspect, the processing module, the processing module, and the computing node, where the volume is to be created, are:

Receiving, by the processing module creation entity, a node list, where the node list includes at least one computing node that meets virtual machine specification information of the virtual machine to be created;

Selecting a computing node from the list of nodes;

Sending node identification information of the selected computing node to the processing module creation entity.

In a fourth possible implementation manner of the first aspect, since the receiving processing module creates a node list sent by the entity, it is ensured that the computing node that can satisfy the virtual machine specification information can be selected.

A third aspect provides an apparatus for creating a virtual machine, the apparatus comprising: a processing unit and a receiving unit;

The processing unit is configured to negotiate, with the volume creation entity, a processing module that is to be created by the virtual machine and a computing node where the volume is located; and create the processing module on the computing node;

The receiving unit is configured to receive volume identification information of the volume sent by the volume creation entity, where the volume is created by the volume creation entity on the computing node;

The processing unit is further configured to mount the volume on the processing module to form the virtual machine to be created according to the volume identifier information.

In the third aspect, the processing module included in the virtual machine to be created is negotiated with the volume creation entity and The compute node where the volume resides ensures that the processing module and the volume are created on the same compute node, so that the processing module reads and writes the access volume to read and write access to the local storage resources to meet the performance requirements of high-speed read and write volumes.

With reference to the third aspect, in a first possible implementation manner of the third aspect, the processing unit is configured to negotiate, in a manner with the volume creation entity, a processing module and a computing node where the volume is included in the virtual machine to be created, include:

Obtaining, according to virtual machine specification information of the virtual machine to be created, a computing node that meets the virtual machine specification information;

Sending node identification information of the computing node to the volume creation entity.

In a first possible implementation manner of the third aspect, since the node identification information of the selected computing node is directly sent to the volume creation entity, it is ensured that the computing node that creates the volume and the computing node that creates the processing module are the same computing node.

With reference to the third aspect, in a second possible implementation manner of the third aspect, the processing unit is specifically configured to negotiate, by using a volume creation entity, a processing module and a computing node where the volume is included in the virtual machine to be created, include:

Obtaining, according to virtual machine specification information of the virtual machine to be created, a node list, where the node list includes one computing node that satisfies the virtual machine specification information;

Sending the node list to a volume creation entity, the node list being used by the volume creation entity to select a computing node from the node list;

Receiving node identification information of the selected one of the computing nodes sent by the volume creation entity.

In a second possible implementation of the third aspect, since the node list is sent to the volume creation entity, it is guaranteed that the volume creation entity can select a compute node that satisfies the volume specification information.

With reference to the third aspect, in a third possible implementation manner of the third aspect, the processing unit is configured to negotiate, by using a volume creation entity, a processing module that is to be created by the virtual machine and a computing node where the volume is located, include:

Receiving the node identification information of the computing node sent by the volume creation entity, where the computing node is the volume specification information acquired by the volume creation entity and satisfying the volume corresponding to the virtual machine to be created.

In a third possible implementation manner of the third aspect, the computing node that creates the volume and the computing node that creates the processing module are the same computing node because the node identification information of the computing node sent by the volume creation entity is received.

With reference to the third aspect, in a fourth possible implementation manner of the third aspect, the processing unit, Specifically, the method for negotiating with the volume creation entity is as follows: the processing module included in the virtual machine to be created and the computing node where the volume is located, including:

Receiving, by the volume creation entity, a node list, where the node list includes at least one computing node that meets volume specification information of a volume corresponding to the virtual machine to be created;

Selecting a computing node from the list of nodes;

Sending node identification information of the selected computing node to the volume creation entity.

In a fourth possible implementation manner of the third aspect, since the node list sent by the volume creation entity is received, it is ensured that the computing node that can satisfy the virtual machine specification information can be selected.

A fourth aspect provides an apparatus for creating a virtual machine, where the apparatus includes: a processing unit and a sending unit;

The processing unit is configured to negotiate, with the processing module creation entity, a processing module and a computing node where the volume is included in the virtual machine to be created; and create the volume on the computing node;

The sending unit is configured to send volume identifier information of the volume to the processing module creation entity, where the volume identifier information is used by the processing module creation entity to create the processing module on the computing node The volume is mounted on the processing module to form the virtual machine to be created.

In the fourth aspect, since the processing module included in the virtual machine to be created and the computing node where the volume is located are negotiated with the processing module creation entity, it is ensured that the processing module is created and the volume is created on the same computing node, so that the processing module reads and writes the access volume. The essence is read and write access to local storage resources to meet the performance requirements of high-speed read and write volumes.

With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the processing unit is configured to: negotiate, with the processing module creation entity, a processing module that is to be created by the virtual machine and a computing node where the volume is located, ,include:

Obtaining, by the volume specification information of the volume corresponding to the virtual machine to be created, a computing node that meets the volume specification information;

Sending node identification information of the computing node to the processing module creation entity.

In a first possible implementation manner of the fourth aspect, since the node identification information of the selected computing node is directly sent to the processing module creation entity, the computing node that creates the volume and the computing node that creates the processing module are the same computing node.

With reference to the fourth aspect, in a second possible implementation manner of the fourth aspect, the processing unit is specifically configured to: negotiate with the processing module creation entity to perform processing included in the virtual machine to be created. The compute nodes where the modules and volumes are located, including:

Obtaining, according to volume specification information of a volume corresponding to the virtual machine to be created, a node list, where the node list includes one to a computing node that satisfies the volume specification information;

Sending, to the processing module creation entity, the node list, where the node list is used by the processing module creation entity to select a computing node from the node list;

Receiving node identification information of the selected one of the computing nodes sent by the processing module creation entity.

In a second possible implementation of the fourth aspect, since the node list is sent to the processing module creation entity, it is ensured that the processing module creation entity can select a computing node that satisfies the virtual machine specification information.

With reference to the fourth aspect, in a third possible implementation manner of the fourth aspect, the processing unit is specifically configured to negotiate, by using the following manner, with the processing module creation entity, a processing module that is to be created by the virtual machine, and a computing node where the volume is located ,include:

The receiving processing module creates the node identification information of the computing node sent by the entity, where the computing node is the virtual machine specification information acquired by the processing module creation entity and meets the virtual machine to be created.

In a third possible implementation manner of the fourth aspect, the receiving processing module creates the node identification information of the computing node sent by the entity, and ensures that the computing node that creates the volume and the computing node that creates the processing module are the same computing node.

With reference to the fourth aspect, in a fourth possible implementation manner of the fourth aspect, the processing unit is specifically configured to negotiate, in a manner with the processing module creation entity, a processing module and a computing node where the volume is to be created by the virtual machine to be created. ,include:

Receiving, by the processing module creation entity, a node list, where the node list includes at least one computing node that meets virtual machine specification information of the virtual machine to be created;

Selecting a computing node from the list of nodes;

Sending node identification information of the selected computing node to the processing module creation entity.

In a fourth possible implementation manner of the fourth aspect, since the receiving processing module creates a node list sent by the entity, it is ensured that the computing node that can satisfy the virtual machine specification information can be selected.

DRAWINGS

1 is a network architecture diagram of an application of an embodiment of the present invention;

2-1 is a structural block diagram of a processing module creation entity according to an embodiment of the present invention;

2-2 is a structural block diagram of a volume creation entity according to an embodiment of the present invention;

3-1 is a flowchart of a method for creating a virtual machine according to an embodiment of the present invention;

3-2 is a flowchart of another method for creating a virtual machine according to an embodiment of the present invention;

4-1 is a flowchart of another method for creating a virtual machine according to an embodiment of the present invention;

4-2 is a flowchart of another method for creating a virtual machine according to an embodiment of the present invention;

5-1 is a flowchart of another method for creating a virtual machine according to an embodiment of the present invention;

FIG. 5-2 is a flowchart of another method for creating a virtual machine according to an embodiment of the present invention;

6-1 is a flowchart of another method for creating a virtual machine according to an embodiment of the present invention;

FIG. 6-2 is a flowchart of another method for creating a virtual machine according to an embodiment of the present invention;

7-1 is a flowchart of another method for creating a virtual machine according to an embodiment of the present invention;

7-2 is a flowchart of another method for creating a virtual machine according to an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of an apparatus for creating a virtual machine according to an embodiment of the present invention;

FIG. 9 is a schematic structural diagram of another apparatus for creating a virtual machine according to an embodiment of the present invention.

detailed description

The embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.

This embodiment is applied to the Openstack platform, which is an open source cloud platform for creating virtual machines. The user can submit a virtual machine creation request to the Openstack platform and request the Openstack platform to create a virtual machine for it. The virtual machine includes a processing module and a volume, the processing module is an operation logic part of the virtual machine, and the volume is a storage module for the processing module to perform read and write access.

Referring to FIG. 1 , the Openstack platform includes a processing module creation entity, a volume creation entity, and a computing node. The computing node includes a CPU (Central Processing Unit), a memory, a hard disk, and the like, and may be a storage server located in the network. . The processing module creation entity is used to create a processing module of the virtual machine, the volume creation entity is used to create a volume of the virtual machine, the processing module creation entity may be a Nova component, the volume creation entity may be a Cinder component, and the Nova component may have a calculation in the network. A functional server or a module in the server; the Cinder component can also be a server with computing functions in the network or a module in the server. When both are modules, the Nova component and the Cinder component can be on the same server or on different servers. In In the present invention, an entity is created by using a Nova component as a processing module, and a Cinder component is used as a volume creation entity. However, this is not intended to limit the scope of the present invention.

When a user needs to create a virtual machine, the user simultaneously sends a virtual machine creation request to the Nova component and the Cinder; the Nova component receives the user's virtual machine creation request, schedules a computing node in the computing node included in the Openstack platform, and creates on the scheduled computing node. The processing module of the virtual machine to be created; the Cinder component receives the virtual machine creation request of the user, schedules a computing node in the computing node included in the Openstack platform, creates a volume corresponding to the virtual machine to be created on the scheduled computing node, and sends the volume corresponding to the virtual machine to the Nova component. Volume identification information of the volume; the Nova component receives the volume identification information of the volume, and mounts the volume on the processing module according to the volume identification information of the volume to form a virtual machine to be created.

It should be noted that, in this embodiment, the computing node scheduled by the Nova component and the computing node scheduled by the Cinder component are the same computing node, so that the processing module and the volume of the virtual machine are located in the same computing node, and the processing module reads and writes the access volume essence. Read and write access to local storage resources to meet the performance requirements of high-speed read and write of virtual machines.

Currently, the Nova component includes a Nova API module, a Nova scheduling module, a Nova computing module, and a KVM (Kernel-based Virtual Machine) layer. The KVM layer includes an interface for creating a processing module; the Cinder component includes a Cinder API module. The Cinder scheduling module, the Cinder computing module, and the vdevice (virtual device) layer, the vdevice layer includes an interface for creating a volume. The Nova component creates a processing module of the virtual machine through each module it includes. The Cinder component creates a volume of the virtual machine through each module included therein, and the specific creation process of the Nova component and the Cinder component is described in detail later.

Referring to FIG. 2-1, FIG. 2-1 is a structural block diagram of a processing module creation entity 100 according to an embodiment of the present invention. The processing module creation entity 100 may be a server having a computing function in the network or a module in the server. The processing module creation entity 100 may vary considerably depending on configuration or performance, and may include one or more processors 101, receivers 102, and transmitters 103, one or more storage media storing applications 204 or data 105. 106 (for example, one or one storage device in Shanghai). The storage medium 206 can be short-lived or persistent. The program stored on storage medium 106 may include one or more modules (not shown), each of which may include a series of instruction operations in processing module creation entity 100. Still further, the processor 101 can be arranged to communicate with the storage medium 106 to perform a series of instruction operations in the storage medium 106 on the Nova component 100.

The processing module creation entity 100 may also include one or more power sources 107, one or more wired or wireless network interfaces 108, one or more input and output interfaces 109, and/or one or more operating systems 110, such as Windows ServerTM. , Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM and more.

The processor 101 and the receiver 102 of the processing module creation entity 100 in the present invention have the following functions:

The processor 101 is configured to negotiate, with the volume creation entity, a processing module that is to be created by the virtual machine and a computing node where the volume is located; and create the processing module on the computing node;

The receiver 102 is configured to receive volume identification information of the volume sent by the volume creation entity, where the volume is created by the volume creation entity on the computing node;

The processor 101 is further configured to mount the volume on the processing module to form the virtual machine to be created according to the volume identifier information.

Optionally, the processor 101 is specifically configured to negotiate, with the volume creation entity, the processing module and the computing node where the volume is to be created, including:

Obtaining, according to virtual machine specification information of the virtual machine to be created, a computing node that meets the virtual machine specification information;

Sending node identification information of the computing node to the volume creation entity.

Optionally, the processor 101 is specifically configured to negotiate, with the volume creation entity, the processing module and the computing node where the volume is to be created, including:

Obtaining, according to virtual machine specification information of the virtual machine to be created, a node list, where the node list includes one computing node that satisfies the virtual machine specification information;

Sending the node list to a volume creation entity, the node list being used by the volume creation entity to select a computing node from the node list;

Receiving node identification information of the selected one of the computing nodes sent by the volume creation entity.

Optionally, the processor 101 is specifically configured to negotiate, with the volume creation entity, the processing module and the computing node where the volume is to be created, including:

Receiving the node identification information of the computing node sent by the volume creation entity, where the computing node is the volume specification information acquired by the volume creation entity and satisfying the volume corresponding to the virtual machine to be created.

Optionally, the processor 101 is specifically configured to negotiate, with the volume creation entity, the processing module and the computing node where the volume is to be created, including:

Receiving a list of nodes sent by the volume creation entity, the node list including satisfying the to-be-created Constructing at least one computing node of volume specification information of a volume corresponding to the virtual machine;

Selecting a computing node from the list of nodes;

Sending node identification information of the selected computing node to the volume creation entity.

In the embodiment of the present invention, since the processing module included in the virtual machine to be created and the computing node where the volume is located are negotiated with the volume creation entity, it is ensured that the processing module and the volume are created on the same computing node, so that the processing module reads and writes the access volume. The essence is read and write access to local storage resources to meet the performance requirements of high-speed read and write volumes.

Referring to FIG. 2-2, FIG. 2-2 is a structural block diagram of a volume creation entity 200 according to an embodiment of the present invention. The volume creation entity 200 can be a server having computing functionality in the network or a module in the server. The volume creation entity 200 can vary considerably depending on configuration or performance, and can include one or more processors 201, a transmitter 202, and a receiver 203, one or more storage media 206 that store application 204 or data 205. (eg one or one storage device in Shanghai). The storage medium 206 can be short-lived or persistent. The program stored on storage medium 206 may include one or more modules (not shown), each of which may include a series of instruction operations in volume creation entity 200. Still further, the processor 201 can be arranged to communicate with the storage medium 206 to perform a series of instruction operations in the storage medium 206 on the Nova appliance 200.

Volume creation entity 200 may also include one or more power sources 207, one or more wired or wireless network interfaces 208, one or more input and output interfaces 209, and/or one or more operating systems 210, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM and more.

The processor 201 and transmitter 202 of the volume creation entity 200 in the present invention have the following functions:

The processor 201 is configured to negotiate, with the computing processing module creating entity, a processing module and a computing node where the volume is included in the virtual machine to be created; and create the volume on the computing node;

The transmitter 202 is configured to send, to the processing module creation entity, volume identifier information of the volume, where the volume identifier information is used by the processing module creation entity to create the processing module on the computing node The volume is mounted on the processing module to form the virtual machine to be created.

Optionally, the processor 201 is configured to negotiate with the processing module creation entity that the processing module and the computing node that are included in the virtual machine to be created are in the following manner, including:

Obtaining the volume specification information that meets the volume specification information according to the volume specification information of the volume corresponding to the virtual machine to be created a computing node;

Sending node identification information of the computing node to the processing module creation entity.

Optionally, the processor 201 is configured to negotiate with the processing module creation entity that the processing module and the computing node that are included in the virtual machine to be created are in the following manner, including:

Obtaining, according to volume specification information of a volume corresponding to the virtual machine to be created, a node list, where the node list includes one to a computing node that satisfies the volume specification information;

Sending, to the processing module creation entity, the node list, where the node list is used by the processing module creation entity to select a computing node from the node list;

Receiving node identification information of the selected one of the computing nodes sent by the processing module creation entity.

Optionally, the processor 201 is configured to negotiate with the processing module creation entity that the processing module and the computing node that are included in the virtual machine to be created are in the following manner, including:

The receiving processing module creates the node identification information of the computing node sent by the entity, where the computing node is the virtual machine specification information acquired by the processing module creation entity and meets the virtual machine to be created.

Optionally, the processor 201 is configured to negotiate with the processing module creation entity that the processing module and the computing node that are included in the virtual machine to be created are in the following manner, including:

Receiving, by the processing module creation entity, a node list, where the node list includes at least one computing node that meets virtual machine specification information of the virtual machine to be created;

Selecting a computing node from the list of nodes;

Sending node identification information of the selected computing node to the processing module creation entity.

In the embodiment of the present invention, since the processing module included in the virtual machine to be created and the computing node where the volume is located are negotiated with the computing processing module creation entity, it is ensured that the processing module and the volume are created on the same computing node, so that the processing module reads and writes. The access volume is essentially a read-write access to local storage resources to meet the performance requirements of high-speed read and write volumes.

Embodiments of the present invention provide a method for creating a virtual machine. In this embodiment, the Nova component schedules the compute node where the processing module is located, and sends the node identifier information of the compute node to the Cinder component, so that the Nova component and the Cinder component respectively create the processing module and volume of the virtual machine on the compute node. . Referring to Figure 3-1, the method includes:

Step 301: The Nova component receives a virtual machine creation request, and the virtual machine creation request carries a to-be-created ID and volume specification information of virtual machine specification information of the virtual machine.

The virtual machine creation request is sent by the user through its corresponding terminal. The user can configure the virtual machine specification information of the virtual machine to be created and the volume specification information of the volume corresponding to the virtual machine to be created on the corresponding terminal, and then send the identifier carrying the virtual machine specification information and the volume specification information through the terminal. The virtual machine creates a request. The terminal sends the virtual machine creation request to the Nova component and the Cinder component at the same time.

Optionally, the configuration process may be: the user corresponding terminal may display a configuration interface to the user, where the configuration interface includes multiple virtual machine specification information; the user may select a virtual machine specification information in the configuration interface, and Setting the volume specification information; the terminal obtains the identifier of the virtual machine specification information and the volume specification information from the configuration interface, and sends a virtual machine creation request that carries the identifier of the virtual machine specification information and the volume specification information to the Nova component and the Cinder component. .

Optionally, referring to Figure 3-2, the Nova component receives the virtual machine creation request through the NovaAPI module it includes.

The virtual machine specification information of the virtual machine to be created includes at least one of a virtual machine memory size, a vCPU (virtual central processing unit), a system disk size, a swap (distributed partition) disk size, and a temporary disk size. . The volume specification information of the virtual machine to be created may be the SLA attribute of the volume, such as SSD (Solid State Drives) or HDD (Hard Disk Drive), and volume IOPS ((Input/Output Operations Per Second). The number of times the read/write (I/O) operation is performed in seconds = 100, etc.

Step 302: The Nova component obtains the virtual machine specification information according to the identifier of the virtual machine specification information, and schedules a computing node that meets the virtual machine specification information according to the virtual machine specification information.

The Nova component includes the resource size of each of the current resources of each computing node in the Openstack platform, and each computing node sends the resource size of the various resources it includes to the Nova component in real time.

In this step, the Nova component obtains corresponding virtual machine specification information from the corresponding relationship between the stored identifier and the virtual machine specification information according to the identifier of the virtual machine specification information, and according to the virtual machine specification information and each saved computing node. For the current resource size of various resources, select a computing node whose resource size satisfies the virtual machine specification information. For example, if the virtual machine specification information includes the virtual machine memory size and the number of vCPUs, the Nova component can select a computing node whose current memory size is larger than the virtual machine memory size and the current vCPU number is greater than the vCPU number.

Optionally, refer to Figure 3-2. The Nova API module in the Nova component will specify the virtual machine specification. The identifier of the information is sent to the Nova scheduling module of the Nova component. The Nova scheduling module obtains the corresponding virtual machine specification information from the corresponding relationship between the stored identifier and the virtual machine specification information according to the identifier, and the scheduling meets the requirement according to the virtual machine specification information. A compute node for virtual machine specification information.

Step 303: The Nova component sends the node identification information of the computing node to the Cinder component.

Step 304: The Nova component creates a processing module of the virtual machine to be created on the computing node according to the virtual machine specification information.

Optionally, referring to Figure 3-2, the Nova scheduling module in the Nova component sends the node identification information of the selected computing node to the Nova computing module of the Nova component, and the Nova computing module identifies the node identification information according to the virtual machine specification information. A processing module of the virtual machine to be created is created on the corresponding computing node.

The Nova component includes a KVM layer, and the KVM layer includes an interface for creating a processing module. The Nova computing module invokes the interface from the virtual layer, and schedules resources on the computing node through the interface according to the virtual machine specification information. Create a processing module. For example, if the virtual machine specification information includes the virtual machine memory size and the number of vCPUs, the corresponding size memory and vCPU are scheduled on the computing node according to the virtual machine memory size and the number of the vCPU.

In this embodiment, step 303 may be performed first, and then step 304 may be performed. Step 304 may be performed first, then step 303 may be performed, or two steps may be performed simultaneously. Steps 303 and 304 have no strict timing relationship.

Step 305: The Cinder component receives a virtual machine creation request, where the virtual machine creation request carries the identifier and volume specification information of the virtual machine specification information of the virtual machine to be created.

The virtual machine creation request is sent by the user through its corresponding terminal.

Optionally, referring to FIG. 3-2, the Cinder component receives the virtual machine creation request through the CinderAPI module included therein.

In this embodiment, the steps 301 and 305 have no strict timing relationship. Step 301 may be performed first, and then step 305 may be performed. Step 305 may be performed first, then step 301 may be performed, or two steps may be performed simultaneously.

Step 306: The Cinder component receives the node identification information, and creates a volume of the virtual machine to be created on the computing node corresponding to the node identification information according to the volume specification information.

Optionally, referring to Figure 3-2, the Cinder component receives the node identification information through the CinderAPI module included therein, and sends the node identification information and the volume specification information to the Cinder scheduling module of the Cinder component; the Cinder scheduling module identifies the node again. Information and volume specification information is sent to Cinder The Cinder calculation module of the component; the Cinder calculation module creates a volume of the virtual machine to be created on the computing node corresponding to the node identification information according to the volume specification information.

The Cinder component includes a vdevice layer, and the vdevice layer includes an interface for creating a volume. The Cinder computing module invokes the interface from the vdevice layer, and according to the volume specification information, the resource is scheduled to be created on the computing node through the interface. The scheduled resources may be SSDs, HDDs, and non-volatile storage media, etc., and the non-volatile storage medium may be Nvdimm.

Step 307: The Cinder component sends the volume identification information of the created volume to the Nova component.

Step 308: The Nova component receives the volume identification information, and mounts the volume on the processing module according to the volume identification information to form a virtual machine to be created.

It should be noted that if the selected computing node does not satisfy the volume specification information, the Cinder component sends a notification message to the Nova component, and then the Nova component reselects a computing node that satisfies the virtual machine specification information, and then sends a reselection to the Cinder component. The node identification information of the compute node allows the Cinder component to create the volume.

In the embodiment of the present invention, the Nova component dispatches a computing node, and sends the node identification information of the computing node to the Cinder component, so that the computing node where the Nova component creation processing module is located and the computing node where the Cinder component creation volume is located are The same computing node enables the processing module to read and write access volumes to read and write access to local storage resources to meet the performance requirements of high-speed read and write volumes.

Embodiments of the present invention provide a method for creating a virtual machine. In this embodiment, the Nova component obtains a node list, the node list includes at least one computing node, and sends the node list to the Cinder component, and the Cinder selects a computing node from the node list, and sends the node of the computing node to the Nova component. Identify information such that the Nova component and the Cinder component create processing modules and volumes for the virtual machine on the compute node, respectively. Referring to Figure 4-1, the method includes:

Step 401: The same as step 301, and will not be described in detail herein.

Step 402: The Nova component obtains the virtual machine specification information according to the identifier of the virtual machine specification information, and obtains a node list according to the virtual machine specification information, where the node list includes at least one computing node that satisfies the virtual machine specification information.

The Nova component includes the resource size of each of the current resources of each computing node in the Openstack platform, and each computing node sends the resource size of the various resources it includes to the Nova component in real time.

In this step, the Nova component obtains corresponding virtual machine specification information according to the identifier of the virtual machine specification information, and selects at least one computing node according to the virtual machine specification information and the saved resource size of each resource of each computing node. . For example, if the virtual machine specification information includes the virtual machine memory size and the number of vCPUs, the Nova component may select at least one computing node whose current memory size is greater than the virtual machine memory size and the current vCPU number is greater than the number of vCPUs.

Optionally, referring to Figure 3-2, the Nova API module in the Nova component sends the identifier of the virtual machine specification information to the Nova scheduling module of the Nova component, and the Nova scheduling module obtains the corresponding virtual machine according to the identifier of the virtual machine specification information. The specification information is to schedule at least one computing node that satisfies the virtual machine specification information according to the virtual machine specification information.

Step 403: The Nova component sends the node list to the Cinder component.

Step 404: The Cinder component receives a virtual machine creation request, where the virtual machine creation request carries the identifier and volume specification information of the virtual machine specification information of the virtual machine to be created.

The virtual machine creation request is sent by the user through its corresponding terminal.

Optionally, referring to FIG. 4-2, the Cinder component receives the virtual machine creation request through the CinderAPI module included therein.

Step 405: The Cinder component receives the node list, and selects a computing node from the node list according to the volume specification information.

Optionally, referring to Figure 4-2, the CinderAPI module receives the node list, and sends the node list and the volume specification information to the Cinder scheduling module. The Cinder scheduling module selects a computing node that satisfies the volume specification information from the node list according to the volume specification information.

Step 406: The Cinder component creates a volume of the virtual machine to be created on the computing node, and sends the node identification information of the selected computing node and the volume identification information of the volume to the Nova component.

Optionally, referring to Figure 4-2, the Cinder scheduling module in the Cinder component sends the node identification information of the selected computing node to the Cinder computing module of the Cinder component, and the Cinder computing module identifies the node identification information according to the virtual machine specification information. Create a volume for the virtual machine to be created on the corresponding compute node.

The Cinder component includes a virtual layer, and the virtual layer includes an interface for creating a processing module. The Cinder computing module invokes the interface from the virtual layer, and according to the virtual machine specification information, the resource is created by scheduling resources on the computing node. volume.

Step 407: The Nova component receives the node identification information and the volume identification information, and creates a virtual machine to be created on the computing node corresponding to the node identification information according to the virtual machine specification information. Module.

Optionally, referring to Figure 4-2, the Nova scheduling module in the Nova component sends the node identification information to the Nova computing module of the Nova component, and the Nova computing module determines the computing node corresponding to the node identification information according to the virtual machine specification information. Create a processing module for the virtual machine to be created.

The Nova component includes a KVM (Kernel-based Virtual Machine) layer, the KVM layer includes an interface for creating a processing module, and the Nova computing module calls the interface from the virtual layer, according to the virtual machine specification information, A processing module is created by scheduling resources on the computing node through the interface. For example, if the virtual machine specification information includes the virtual machine memory size and the number of vCPUs, the corresponding size memory and vCPU are scheduled on the computing node according to the virtual machine memory size and the number of the vCPU.

Step 408: The Nova component mounts the volume on the processing module according to the volume identification information to form a virtual machine to be created.

In the embodiment of the present invention, the Nova component schedules at least one computing node to form a node list, and sends the node list to the Cinder component, the Cinder component selects a computing node from the node list, and selects the node identification information of the computing node. It is sent to the Nova component, which ensures that the compute node where the Nova component creation processing module is located and the compute node where the Cinder component creates the volume are the same compute node, so that the processing module reads and writes the access volume to read and write access to the local storage resource, satisfying the high speed. The performance requirements of read and write volumes.

Embodiments of the present invention provide a method for creating a virtual machine. In this embodiment, the Cinder component schedules the compute node where the volume is created, and sends the node identifier information of the compute node to the Nova component, such that the Nova component and the Cinder component respectively create a processing module and volume of the virtual machine on the compute node. Referring to Figure 5-1, the method includes:

Step 501: The Cinder component receives a virtual machine creation request, where the virtual machine creation request carries the identifier and volume specification information of the virtual machine specification information of the virtual machine to be created.

The virtual machine creation request is configured by the user on the corresponding terminal and is sent by the corresponding terminal. For details, refer to the related content in step 301, and details are not described herein.

Optionally, referring to FIG. 5-2, the Cinder component receives the virtual machine creation request through the Cinder API module included therein.

Step 502: The Cinder component schedules a computing node that meets the volume specification information according to the volume specification information.

The Cinder component includes resource sizes of various resources of each computing node in the Openstack platform, and each computing node sends the resource size of various resources included in the Cinder component in real time.

This step may be: the Cinder component selects a computing node according to the volume specification information and the saved resource size of each resource of each computing node.

Optionally, referring to Figure 5-2, the Cinder API module in the Cinder component sends the volume specification information to the Cinder scheduling module of the Cinder component, and the Cinder scheduling module schedules a computing node that meets the volume specification information according to the volume specification information. .

Step 503: The Cinder component sends the node identification information of the computing node to the Nova component.

Step 504: The Cinder component creates a volume of the virtual machine to be created on the computing node according to the volume specification information, and sends the volume identification information of the volume to the Nova component.

Optionally, referring to Figure 5-2, the Cinder scheduling module in the Cinder component sends the node identification information of the selected computing node to the Cinder computing module of the Cinder component, and the Cinder computing module corresponds to the node identification information according to the volume specification information. Create a volume on the compute node where the virtual machine is to be created.

The Cinder component includes a vdevice layer, and the vdevice layer includes an interface for creating a volume. The Cinder computing module invokes the interface from the vdevice layer, and according to the volume specification information, the resource is scheduled to be created on the computing node through the interface.

Step 505: The Nova component receives a virtual machine creation request, and the virtual machine creation request carries the identifier and volume specification information of the virtual machine specification information of the virtual machine to be created.

The virtual machine creation request is sent by the user through its corresponding terminal.

Optionally, referring to Figure 5-2, the Nova component receives the virtual machine creation request through the NovaAPI module it includes.

Step 506: The Nova component receives the node identification information, obtains the corresponding virtual machine specification information according to the identifier of the virtual machine specification information, and creates a virtual machine to be created on the computing node corresponding to the node identification information according to the virtual machine specification information. Processing module.

Optionally, referring to Figure 5-2, the Nova component receives the virtual machine creation request through the NovaAPI module included therein, and sends the identifier of the virtual machine specification information to the Nova scheduling module of the Nova component; the Nova scheduling module according to the virtual machine specification The identifier of the information obtains the corresponding virtual machine specification information, and sends the virtual machine specification information to the Nova computing module of the Nova component; the Nova computing module receives the node identification information, and corresponding to the node identification information according to the virtual machine specification information. Create a processing module for the virtual machine to be created on the compute node.

The Nova component includes a KVM layer, the KVM layer includes an interface for creating a processing module, and the Nova computing module invokes the interface from the KVM layer, and according to the virtual machine specification information, the resource is created by scheduling resources on the computing node through the interface. Processing module.

Step 507: The Nova component receives the volume identification information, and mounts the volume on the processing module according to the volume identification information to form a virtual machine to be created.

It should be noted that if the selected computing node does not satisfy the virtual machine specification information, the Nova component sends a notification message to the Cinder component, and then the Cinder component reselects a computing node that satisfies the volume specification information, and then sends a reselection to the Nova component. The node identification information of the compute node allows the Nova component to create the processing module.

In the embodiment of the present invention, the Cinder component schedules a computing node, and sends the node identification information of the computing node to the Nova component, so that the computing node where the Nova component creation processing module is located and the computing node where the Cinder component creation volume is located are The same computing node enables the processing module to read and write access volumes to read and write access to local storage resources to meet the performance requirements of high-speed read and write volumes.

Embodiments of the present invention provide a method for creating a virtual machine. In this embodiment, the Cinder component acquires a node list, the node list includes at least one computing node, and sends a node list to the Nova component, the Nova component selects a computing node from the node list, and sends the node of the computing node to the Cinder component. Identify information so that the Nova component and the Cinder component create the processing modules and volumes of the virtual machine on the compute nodes, respectively. Referring to Figure 6-1, the method includes:

Step 601: The same as step 501, and will not be described in detail herein.

Step 602: The Cinder component acquires a node list according to the volume specification information, where the node list includes at least one computing node that satisfies the volume specification information.

The Cinder component includes resource sizes of various resources of each computing node in the Openstack platform, and each computing node sends the resource size of various resources included in the Cinder component in real time.

The step may be: the Cinder component selects at least one computing node according to the volume specification information and the saved resource size of each resource of each computing node.

Optionally, referring to Figure 6-2, the Cinder API module in the Cinder component sends the volume specification information to the Cinder scheduling module of the Cinder component, and the Cinder scheduling module according to the volume specification information. At least one compute node that satisfies the volume specification information is scheduled.

Step 603: The Cinder component sends the node list to the Nova component.

Step 604: The Nova component receives a virtual machine creation request, and the virtual machine creation request carries the identifier and volume specification information of the virtual machine specification information of the virtual machine to be created.

The virtual machine creation request is sent by the user through its corresponding terminal.

Optionally, referring to Figure 6-2, the Nova component receives the virtual machine creation request through the NovaAPI module included therein, and sends the identifier of the virtual machine specification information to the Nova scheduling module.

Step 605: The Nova component receives the node list, obtains the virtual machine specification information according to the identifier of the virtual machine specification information, and selects a computing node from the node list according to the virtual machine specification information.

Optionally, the Nova scheduling module of the Nova component obtains the virtual machine specification information according to the identifier of the virtual machine specification information, and selects a computing node that meets the virtual machine specification information from the node list according to the virtual machine specification information, and then The node identification information of the selected computing node is sent to the Nova computing module.

Step 606: The Nova component creates a processing module of the virtual machine to be created on the computing node, and sends the node identification information of the selected computing node to the Cinder component.

Optionally, referring to FIG. 6-2, the Nova computing module receives the node identifier information of the computing node, and creates a processing module of the virtual machine to be created on the computing node corresponding to the node identifier information according to the virtual machine specification information.

The Nova component includes a KVM layer, the KVM layer includes an interface for creating a processing module, and the Nova computing module invokes the interface from the KVM layer, and according to the virtual machine specification information, the resource is created by scheduling resources on the computing node through the interface. volume.

Step 607: The Cinder component receives the node identification information, and creates a volume of the virtual machine to be created on the computing node corresponding to the node identification information according to the volume specification information, and sends the volume identification information of the volume to the Nova component.

Optionally, referring to Figure 6-2, the Cinder calculation module in the Cinder component receives the node identification information, and creates a volume of the virtual machine to be created on the computing node corresponding to the node identification information according to the volume specification information.

The Cinder component includes a vdevice layer, and the vdevice layer includes an interface for creating a volume. The Cinder computing module invokes the interface from the vdevice layer, and according to the volume specification information, the resource is scheduled to be created on the computing node through the interface.

Step 608: The Nova component receives the volume identification information, and mounts the volume on the processing module according to the volume identification information to form a virtual machine to be created.

In the embodiment of the present invention, the Cinder component schedules at least one computing node to form a node list, and sends the node list to the Nova component, and the Nova component selects a computing node from the node list, and selects the node identification information of the computing node. The Cinder component is sent to the Cinder component, so that the computing node where the Nova component creation processing module is located and the computing node where the Cinder component creation volume is located are the same computing node, so that the processing module reads and writes the access volume to read and write access to the local storage resource, which satisfies the high speed. The performance requirements of read and write volumes.

Embodiments of the present invention provide a method for creating a virtual machine. In this embodiment, the Nova component schedules a processing module and a computing node where the volume is located, and creates a processing module and a volume of the virtual machine on the computing node. Referring to Figure 7-1, the method includes:

Step 701: The same as step 301, and will not be described in detail herein.

Step 702: The Nova component obtains the virtual machine specification information according to the identifier of the virtual machine specification information, and schedules a computing node that meets the virtual machine specification information according to the virtual machine specification information.

The Nova component includes the resource size of each of the current resources of each computing node in the Openstack platform, and each computing node sends the resource size of the various resources it includes to the Nova component in real time.

In this step, the Nova component obtains corresponding virtual machine specification information from the corresponding relationship between the stored identifier and the virtual machine specification information according to the identifier of the virtual machine specification information, and according to the virtual machine specification information and each saved computing node. For the current resource size of various resources, select a compute node. For example, if the virtual machine specification information includes the virtual machine memory size and the number of vCPUs, the Nova component can select a computing node whose current memory size is larger than the virtual machine memory size and the current vCPU number is greater than the vCPU number.

Optionally, referring to Figure 7-2, the Nova API module in the Nova component sends the identifier of the virtual machine specification information and the volume specification information to the Nova scheduling module of the Nova component, and the Nova scheduling module identifies the virtual machine specification information according to the virtual machine specification information. And acquiring corresponding virtual machine specification information from the correspondence between the stored identifier and the virtual machine specification information, and scheduling one computing node that meets the virtual machine specification information according to the virtual machine specification information.

Step 703: The Nova component creates a processing module of the virtual machine to be created on the computing node according to the virtual machine specification information.

Optionally, referring to Figure 7-2, the Nova scheduling module in the Nova component sends the node identification information of the selected computing node, the virtual machine specification information, and the volume specification information to the Nova computing module of the Nova component, and the Nova computing module is configured according to The virtual machine specification information is used to create a processing module of the virtual machine to be created on the computing node corresponding to the node identifier information.

The Nova component includes a module KVM layer, the KVM layer includes an interface for creating a processing module, the Nova computing module invokes the interface from the KVM layer, and schedules resources on the computing node through the interface according to the virtual machine specification information. To create a processing module. For example, if the virtual machine specification information includes the virtual machine memory size and the number of vCPUs, the corresponding size memory and vCPU are scheduled on the computing node according to the virtual machine memory size and the number of the vCPU.

Step 704: The Nova component creates a volume of the virtual machine to be created on the computing node according to the volume specification information.

Optionally, referring to FIG. 7-2, the Nova component further includes a vdevice layer, where the vdevice layer includes an interface for creating a volume, and the Nova computing module invokes the interface from the vdevice layer, according to the volume specification information, through the interface. A resource is scheduled on the compute node to create a volume.

Step 705: The Nova component mounts the volume on the processing module to form a virtual machine to be created.

In the embodiment of the present invention, the Nova component schedules a computing node, and creates a processing module and a volume of the virtual machine to be created on the computing node, so that the created processing module and the volume are all located in the same computing node, so that the processing module reads The write access volume is essentially a read-write access to local storage resources to meet the performance requirements of high-speed read and write volumes.

Referring to Figure 8, an embodiment of the present invention provides an apparatus 800 for creating a virtual machine, the apparatus 800 comprising: a processing unit 801 and a receiving unit 802;

The processing unit 801 is configured to negotiate, with the volume creation entity, a processing module that is to be created by the virtual machine and a computing node where the volume is located; and create the processing module on the computing node;

The receiving unit 802 is configured to receive volume identification information of the volume sent by the volume creation entity, where the volume is created by the volume creation entity on the computing node;

The processing unit 801 is further configured to mount the volume on the processing module to form the virtual machine to be created according to the volume identifier information.

Optionally, the processing unit 801 is specifically configured to negotiate, with the volume creation entity, the processing module and the computing node where the volume is to be created, including:

Obtaining the virtual machine specification information that meets the virtual machine according to the virtual machine specification information of the virtual machine to be created. a computing node;

Sending node identification information of the computing node to the volume creation entity.

Optionally, the processing unit 801 is specifically configured to negotiate, with the volume creation entity, the processing module and the computing node where the volume is to be created, including:

Obtaining, according to virtual machine specification information of the virtual machine to be created, a node list, where the node list includes one computing node that satisfies the virtual machine specification information;

Sending the node list to a volume creation entity, the node list being used by the volume creation entity to select a computing node from the node list;

Receiving node identification information of the selected one of the computing nodes sent by the volume creation entity.

Optionally, the processing unit 801 is specifically configured to negotiate, with the volume creation entity, the processing module and the computing node where the volume is to be created, including:

Receiving the node identification information of the computing node sent by the volume creation entity, where the computing node is the volume specification information acquired by the volume creation entity and satisfying the volume corresponding to the virtual machine to be created.

Optionally, the processing unit 801 is specifically configured to negotiate, with the volume creation entity, the processing module and the computing node where the volume is to be created, including:

Receiving, by the volume creation entity, a node list, where the node list includes at least one computing node that meets volume specification information of a volume corresponding to the virtual machine to be created;

Selecting a computing node from the list of nodes;

Sending node identification information of the selected computing node to the volume creation entity.

In the embodiment of the present invention, since the processing module included in the virtual machine to be created and the computing node where the volume is located are negotiated with the volume creation entity, it is ensured that the processing module and the volume are created on the same computing node, so that the processing module reads and writes the access volume. The essence is read and write access to local storage resources to meet the performance requirements of high-speed read and write volumes.

Referring to FIG. 9, an embodiment of the present invention provides an apparatus 900 for creating a virtual machine, where the apparatus 900 includes: a processing unit 901 and a sending unit 902;

The processing unit 901 is configured to negotiate, with the processing module creation entity, a processing module included in the virtual machine to be created and a computing node where the volume is located; and create the volume on the computing node;

The sending unit 902 is configured to send volume identifier information of the volume to the processing module creation entity, where the volume identifier information is used by the processing module creation entity to create the processing module on the computing node The volume is mounted on the processing module to form the virtual machine to be created.

Optionally, the processing unit 901 is specifically configured to negotiate with the processing module creation entity that the processing module and the computing node that are included in the virtual machine to be created are in the following manner, including:

Obtaining, by the volume specification information of the volume corresponding to the virtual machine to be created, a computing node that meets the volume specification information;

Sending node identification information of the computing node to the processing module creation entity.

Optionally, the processing unit 901 is specifically configured to negotiate with the processing module creation entity that the processing module and the computing node that are included in the virtual machine to be created are in the following manner, including:

Obtaining, according to volume specification information of a volume corresponding to the virtual machine to be created, a node list, where the node list includes one to a computing node that satisfies the volume specification information;

Sending, to the processing module creation entity, the node list, where the node list is used by the processing module creation entity to select a computing node from the node list;

Receiving node identification information of the selected one of the computing nodes sent by the processing module creation entity.

Optionally, the processing unit 901 is specifically configured to negotiate with the processing module creation entity that the processing module and the computing node that are included in the virtual machine to be created are in the following manner, including:

The receiving processing module creates the node identification information of the computing node sent by the entity, where the computing node is the virtual machine specification information acquired by the processing module creation entity and meets the virtual machine to be created.

Optionally, the processing unit 901 is specifically configured to negotiate with the processing module creation entity that the processing module and the computing node that are included in the virtual machine to be created are in the following manner, including:

Receiving, by the processing module creation entity, a node list, where the node list includes at least one computing node that meets virtual machine specification information of the virtual machine to be created;

Selecting a computing node from the list of nodes;

Sending node identification information of the selected computing node to the processing module creation entity.

In the embodiment of the present invention, since the processing module included in the virtual machine to be created and the computing node where the volume is located are negotiated with the computing processing module creation entity, it is ensured that the processing module and the volume are created on the same computing node, so that the processing module reads and writes. The access volume is essentially a read-write access to local storage resources to meet the performance requirements of high-speed read and write volumes.

A person of ordinary skill in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to complete related hardware, and the program may be Stored in a computer readable storage medium, the storage medium mentioned above may be a read only memory, a magnetic disk or an optical disk or the like.

The above are only the preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalents, improvements, etc., which are within the spirit and scope of the present invention, should be included in the protection of the present invention. Within the scope.

Claims (20)

1. A method for creating a virtual machine, the method comprising:

   Negotiating, with the volume creation entity, a processing module to be created by the virtual machine and a computing node where the volume is located;

   Creating the processing module on the computing node;

   Receiving volume identification information of the volume sent by the volume creation entity, where the volume is created by the volume creation entity on the computing node;

   And mounting the volume on the processing module to form the virtual machine to be created according to the volume identifier information.
2. The method of claim 1, wherein the negotiating with the volume creation entity, the processing module included in the virtual machine to be created, and the computing node where the volume is located, includes:

   Obtaining, according to virtual machine specification information of the virtual machine to be created, a computing node that meets the virtual machine specification information;

   Sending node identification information of the computing node to the volume creation entity.
3. The method of claim 1, wherein the negotiating with the volume creation entity, the processing module included in the virtual machine to be created, and the computing node where the volume is located, includes:

   Obtaining, according to virtual machine specification information of the virtual machine to be created, a node list, where the node list includes one computing node that satisfies the virtual machine specification information;

   Sending the node list to a volume creation entity, the node list being used by the volume creation entity to select a computing node from the node list;

   Receiving node identification information of the selected one of the computing nodes sent by the volume creation entity.
4. The method of claim 1, wherein the negotiating with the volume creation entity, the processing module included in the virtual machine to be created, and the computing node where the volume is located, includes:

   Receiving the node identification information of the computing node sent by the volume creation entity, where the computing node is the volume specification information acquired by the volume creation entity and satisfying the volume corresponding to the virtual machine to be created.
5. The method of claim 1, wherein the negotiating with the volume creation entity, the processing module included in the virtual machine to be created, and the computing node where the volume is located, includes:

   Receiving a list of nodes sent by the volume creation entity, the node list including satisfying the to-be-created Constructing at least one computing node of volume specification information of a volume corresponding to the virtual machine;

   Selecting a computing node from the list of nodes;

   Sending node identification information of the selected computing node to the volume creation entity.
6. A method for creating a virtual machine, the method comprising:

   Negotiating, with the processing module creation entity, a processing module and a computing node where the volume is to be created by the virtual machine to be created;

   Creating the volume on the compute node;

   Transmitting, to the processing module creation entity, volume identification information of the volume, the volume identification information being used by the processing module creation entity to mount the volume in the processing module after creating the processing module on the computing node Processing the module to form the virtual machine to be created.
7. The method according to claim 6, wherein the processing module and the computing node where the volume is included in the virtual machine to be created are negotiated with the processing module creation entity, and the method includes:

   Obtaining, by the volume specification information of the volume corresponding to the virtual machine to be created, a computing node that meets the volume specification information;

   Sending node identification information of the computing node to the processing module creation entity.
8. The method according to claim 6, wherein the processing module and the computing node where the volume is included in the virtual machine to be created are negotiated with the processing module creation entity, and the method includes:

   Obtaining, according to volume specification information of a volume corresponding to the virtual machine to be created, a node list, where the node list includes one to a computing node that satisfies the volume specification information;

   Sending, to the processing module creation entity, the node list, where the node list is used by the processing module creation entity to select a computing node from the node list;

   Receiving node identification information of the selected one of the computing nodes sent by the processing module creation entity.
9. The method according to claim 6, wherein the processing module and the computing node where the volume is included in the virtual machine to be created are negotiated with the processing module creation entity, and the method includes:

   The receiving processing module creates node identification information of the computing node sent by the entity, where the computing node is a virtual machine specification letter that is obtained by the processing module creation entity and meets the virtual machine to be created. interest.
10. The method according to claim 6, wherein the processing module and the computing node where the volume is included in the virtual machine to be created are negotiated with the processing module creation entity, and the method includes:

    Receiving, by the processing module creation entity, a node list, where the node list includes at least one computing node that meets virtual machine specification information of the virtual machine to be created;

    Selecting a computing node from the list of nodes;

    Sending node identification information of the selected computing node to the processing module creation entity.
11. An apparatus for creating a virtual machine, the apparatus comprising: a processing unit and a receiving unit;

    The processing unit is configured to negotiate, with the volume creation entity, a processing module that is to be created by the virtual machine and a computing node where the volume is located; and create the processing module on the computing node;

    The receiving unit is configured to receive volume identification information of the volume sent by the volume creation entity, where the volume is created by the volume creation entity on the computing node;

    The processing unit is further configured to mount the volume on the processing module to form the virtual machine to be created according to the volume identifier information.
12. The device according to claim 11, wherein the processing unit is configured to negotiate with the volume creation entity that the processing module and the volume of the volume to be created by the virtual machine are located in the following manner, including:

    Obtaining, according to virtual machine specification information of the virtual machine to be created, a computing node that meets the virtual machine specification information;

    Sending node identification information of the computing node to the volume creation entity.
13. The device according to claim 11, wherein the processing unit is configured to negotiate with the volume creation entity that the processing module and the volume of the volume to be created by the virtual machine are located in the following manner, including:

    Obtaining, according to virtual machine specification information of the virtual machine to be created, a node list, where the node list includes one computing node that satisfies the virtual machine specification information;

    Sending the list of nodes to a volume creation entity, the node list being used for the volume creation entity Selecting a computing node in the node list;

    Receiving node identification information of the selected one of the computing nodes sent by the volume creation entity.
14. The device according to claim 11, wherein the processing unit is configured to negotiate with the volume creation entity that the processing module and the volume of the volume to be created by the virtual machine are located in the following manner, including:

    Receiving the node identification information of the computing node sent by the volume creation entity, where the computing node is the volume specification information acquired by the volume creation entity and satisfying the volume corresponding to the virtual machine to be created.
15. The device according to claim 11, wherein the processing unit is configured to negotiate with the volume creation entity that the processing module and the volume of the volume to be created by the virtual machine are located in the following manner, including:

    Receiving, by the volume creation entity, a node list, where the node list includes at least one computing node that meets volume specification information of a volume corresponding to the virtual machine to be created;

    Selecting a computing node from the list of nodes;

    Sending node identification information of the selected computing node to the volume creation entity.
16. An apparatus for creating a virtual machine, the apparatus comprising: a processing unit and a sending unit;

    The processing unit is configured to negotiate, with the processing module creation entity, a processing module and a computing node where the volume is included in the virtual machine to be created; and create the volume on the computing node;

    The sending unit is configured to send volume identifier information of the volume to the processing module creation entity, where the volume identifier information is used by the processing module creation entity to create the processing module on the computing node The volume is mounted on the processing module to form the virtual machine to be created.
17. The device according to claim 16, wherein the processing unit is configured to negotiate with the processing module creation entity that the processing module and the volume of the volume to be created by the virtual machine include:

    Obtaining, by the volume specification information of the volume corresponding to the virtual machine to be created, a computing node that meets the volume specification information;

    Sending node identification information of the computing node to the processing module creation entity.
18. The device according to claim 16, wherein the processing unit is configured to negotiate with the processing module creation entity that the processing module and the volume of the volume to be created by the virtual machine include:

    Obtaining, according to volume specification information of a volume corresponding to the virtual machine to be created, a node list, where the node list includes one to a computing node that satisfies the volume specification information;

    Sending, to the processing module creation entity, the node list, where the node list is used by the processing module creation entity to select a computing node from the node list;

    Receiving node identification information of the selected one of the computing nodes sent by the processing module creation entity.
19. The device according to claim 16, wherein the processing unit is configured to negotiate with the processing module creation entity that the processing module and the volume of the volume to be created by the virtual machine include:

    The receiving processing module creates the node identification information of the computing node sent by the entity, where the computing node is the virtual machine specification information acquired by the processing module creation entity and meets the virtual machine to be created.
20. The device according to claim 16, wherein the processing unit is configured to negotiate with the processing module creation entity that the processing module and the volume of the volume to be created by the virtual machine include:

    Receiving, by the processing module creation entity, a node list, where the node list includes at least one computing node that meets virtual machine specification information of the virtual machine to be created;

    Selecting a computing node from the list of nodes;

    Sending node identification information of the selected computing node to the processing module creation entity.

Images