CN108076078A - A kind of cloud host creation method, device and cloud service system - Google Patents

Abstract

The embodiment of the invention discloses a cloud host creation method, device and cloud service system. The method is applied to the target computing node in the cloud service system, including: receiving the creation instruction for the target cloud host; judging whether the target image file required to create the target cloud host is saved locally; if not saved, determining the target from the cache node Cache node; send the first request to obtain the target image file to the target cache node; receive the target information fed back by the target cache node according to the first request; judge whether the target information is the target image file; if yes, create the target cloud according to the target image file Host; if not, send a second request to the mirror node for obtaining the target mirror file; receive the target mirror file fed back by the mirror node according to the second request; create a target cloud host according to the target mirror file. The embodiment of the present invention can reduce the pulling time of the image file and shorten the creation time of the cloud host.

Description

A cloud host creation method, device and cloud service system

technical field

The present invention relates to the technical field of virtualization, in particular to a cloud host creation method, device and cloud service system.

Background technique

In cloud computing technology, a cloud host is a plurality of parts similar to independent hosts simulated on a physical machine through virtualization technology, and they share the hardware resources of a physical machine. The physical machine can also be called a host. With the popularization and commercialization of virtualization technology, more and more users need to create cloud hosts on host machines to improve the utilization rate of host machines.

For example, in the OpenStack (cloud computing management platform) architecture, when creating a cloud host on a host machine, you first need to obtain the system disk image file of the cloud host. After obtaining the above system disk image file, the host machine can Create a cloud host based on the image file.

Specifically, when the above-mentioned system disk image file is obtained, if the image file corresponding to the cloud host is stored in the host machine, the image file stored in the host machine is directly copied as the system disk image file of the cloud host machine; if the host machine If the image file corresponding to the cloud host is not saved in the cloud host, you need to pull the above system disk image file through the Glance server in the OpenStack architecture. Among them, the Glance server is used to provide the image service of OpenStack, and is used to register, log in and retrieve the virtual machine image.

Normally, cloud hosts can be successfully created by applying the above methods, but when a large number of cloud hosts are created concurrently and there is no system disk image file corresponding to the cloud host on the host machine, the host machine will access the Glance server in large numbers to pull the corresponding Image files lead to high pressure on the Glance server, and the pull time of image files is longer, which makes the creation time of a large number of cloud hosts longer or even uncontrollable.

Contents of the invention

The purpose of the embodiments of the present invention is to provide a cloud host creation method, device and cloud service system, so as to realize high concurrent downloading of image files, reduce the pull time of image files, and shorten the creation time of cloud hosts. The specific technical scheme is as follows:

In order to achieve the above purpose, the embodiment of the present invention discloses a method for creating a cloud host, which is applied to a target computing node in a cloud service system, wherein the cloud service system includes: a computing node, a cache node providing data caching services, providing A mirror node of cloud host mirror service, the method includes:

Receive creation instructions for the target cloud host;

Judging whether there is a target image file stored locally, wherein the target image file is an image file required for creating the target cloud host;

If not saved, determine the target cache node from the cache nodes;

sending a first request for obtaining the target image file to the target cache node;

receiving target information fed back by the target cache node according to the first request;

judging whether the target information is the target image file;

If yes, create the target cloud host according to the target image file;

If not, send a second request for obtaining the target image file to the mirror node; receive the target mirror file fed back by the mirror node according to the second request; create the target according to the target mirror file cloud host.

Optionally, the cache node includes: a primary cache node and a secondary cache node corresponding to the primary cache node, where the image file cached by the secondary cache node is the same as the image file cached by the primary cache node;

The step of determining the target cache node from the cache nodes includes:

According to the preset association relationship between computing nodes and cache nodes, the target cache node is determined from the cache nodes.

Optionally, the preset association relationship between computing nodes and cache nodes is generated in the following manner:

According to the number N of cache nodes, determine the sequence number of each cache node, wherein the sequence number is an integer in the interval [0, N-1], and the sequence numbers of any two cache nodes are different;

Calculate the target hash value H of the identification information of each computing node;

Calculate the target modulo value M corresponding to each computing node according to the following expression:

M=mod(H,N);

For each computing node, determine the cache node whose sequence number is the same as the target modulo value of the computing node, and establish an association relationship between the computing node and the determined cache node.

To achieve the above purpose, the embodiment of the present invention also discloses a cloud host creation device, which is applied to a target computing node in a cloud service system, wherein the cloud service system includes: a computing node, a cache node providing data caching services, A mirror node that provides cloud host mirror service, the device includes:

The first receiving module is used to receive the creation instruction for the target cloud host;

The first judging module is used to judge whether there is a target image file stored locally, wherein the target image file is an image file required for creating the target cloud host;

A determination module, configured to determine the target cache node from the cache nodes when the first determination module determines that the target image file is not saved locally;

A sending module, configured to send a first request for acquiring the target image file to the target cache node;

A second receiving module, configured to receive target information fed back by the target cache node according to the first request;

A second judging module, configured to judge whether the target information is the target image file;

A first creation module, configured to create the target cloud host according to the target image file when the second judgment module determines that the target information is the target image file;

A second creating module, configured to send a second request for acquiring the target image file to the image node when the second judging module determines that the target information is not the target image file; and receive the image node According to the target image file fed back by the second request; creating the target cloud host according to the target image file.

Optionally, the cache node includes: a primary cache node and a secondary cache node corresponding to the primary cache node, where the image file cached by the secondary cache node is the same as the image file cached by the primary cache node;

The determining module is used for:

According to the preset association relationship between computing nodes and cache nodes, the target cache node is determined from the cache nodes.

Optionally, the preset association relationship between computing nodes and cache nodes is:

Generated as follows:

According to the number N of cache nodes, determine the sequence number of each cache node, wherein the sequence number is an integer in the interval [0, N-1], and the sequence numbers of any two cache nodes are different;

Calculate the target hash value H of the identification information of each computing node;

Calculate the target modulo value M corresponding to each computing node according to the following expression:

M=mod(H,N);

For each computing node, determine the cache node whose sequence number is the same as the target modulo value of the computing node, and establish an association relationship between the computing node and the determined cache node.

In order to achieve the above purpose, the embodiment of the present invention also discloses a cloud service system, the system includes: a computing node, a cache node providing data caching service, and a mirroring node providing cloud host mirroring service, wherein,

The computing node is used to: receive a creation instruction for the target cloud host; determine whether a target image file is stored locally, wherein the target image file is the image file required for creating the target cloud host; if not saved, Determining a target cache node from the cache nodes; sending a first request for acquiring the target image file to the target cache node;

The cache node is configured to: receive a first request for acquiring the target image file sent by the computing node; and feed back target information to the computing node according to the first request;

The computing node is further configured to: receive the target information fed back by the target cache node according to the first request; determine whether the target information is the target image file; if yes, create a target image file based on the target image file The target cloud host; if not, send a second request for obtaining the target mirror file to the mirror node;

The image node is configured to: receive a second request for acquiring the target image file sent by the computing node; feed back the target image file to the computing node according to the second request;

The computing node is further configured to: receive the target image file fed back by the image node according to the second request; create the target cloud host according to the target image file.

Optionally, the cache node includes: a primary cache node and a secondary cache node corresponding to the primary cache node, where the image file cached by the secondary cache node is the same as the image file cached by the primary cache node;

The computing node is specifically configured to: determine a target caching node from among the caching nodes according to a preset association relationship between computing nodes and caching nodes.

Optionally, the computing node is specifically configured to: determine the sequence number of each cache node according to the number N of cache nodes, where the sequence number is an integer in the interval [0, N-1], and any two cache nodes The sequence numbers are all different; calculate the target hash value H of the identification information of the computing node; calculate the target modulo value M corresponding to the computing node according to the following expression: M=mod (H, N); determine the sequence number and the computing node The target cache node with the same modulus value is established, and an association relationship between the computing node and the determined cache node is established.

Optionally, the image node is further configured to: feed back the target image file to the cache node;

The cache node is further configured to: receive the target image file fed back by the mirror node, and cache the target image file.

Optionally, the cache node is specifically used to: determine whether the amount of data cached locally reaches a preset threshold, if not, cache the target image file, if yes, determine the image file to be deleted locally, and delete the desired image file. For the deleted image file, the target image file is cached.

Optionally, the cache node includes: a master cache node and a slave cache node corresponding to the master cache node;

The image node is specifically used to: feed back the target image file to the primary cache node;

The primary cache node is configured to: receive the target image file fed back by the mirror node, cache the target image file, and then feed back the target image file to the slave cache node;

The slave cache node is configured to: receive the target image file fed back by the master cache node, and cache the target image file.

Optionally, the system further includes: a storage node for providing data storage services;

The mirroring node is further configured to: receive the mirroring file uploaded by the user, and store the mirroring file uploaded by the user in the storage node by using object storage technology;

The storage node is configured to: store the image file uploaded by the user.

It can be seen from the above that in the solution provided by the embodiment of the present invention, after the computing node receives the creation instruction for the target cloud host, it first judges whether the corresponding target image file is cached locally, and if not, requests the target image file from the cache node file, and only when the cache node does not cache the target image file, it requests the target image file from the mirror node.

It can be seen that applying the solutions provided by the embodiments of the present invention can reduce the access pressure of mirror nodes, realize high concurrent download of mirror files, reduce the time for pulling mirror files, and shorten the creation time of cloud hosts.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. Those skilled in the art can also obtain other drawings based on these drawings without creative work.

FIG. 1 is a schematic flow diagram of a method for creating a cloud host provided by an embodiment of the present invention;

Fig. 2 is a schematic diagram of a specific embodiment provided by the embodiment of the present invention;

FIG. 3 is a schematic structural diagram of a cloud host creation device provided by an embodiment of the present invention;

FIG. 4 is a first structural schematic diagram of a cloud master service system provided by an embodiment of the present invention;

FIG. 5 is a second structural schematic diagram of the cloud master service system provided by the embodiment of the present invention;

FIG. 6 is a schematic diagram of the third structure of the cloud host service system provided by the embodiment of the present invention;

FIG. 7 is a schematic diagram of a fourth structure of a cloud host service system provided by an embodiment of the present invention;

8 is a schematic diagram of a fifth structure of the cloud master service system provided by the embodiment of the present invention;

FIG. 9 is a schematic diagram of a sixth structure of a cloud master service system provided by an embodiment of the present invention.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.

A brief introduction to the technical terms involved in this application document is given first.

Redis cache is a high-performance log type and key-value storage system that can be based on memory and can be persisted. It supports stored value types including string (string), list (linked list), set (collection) and zset (with order collection), in order to ensure efficiency, data is usually cached in memory, and at the same time, the data in memory can also be saved in the local disk, and can be loaded again for use when restarting. On this basis, Redis caching technology can also realize master-slave (master-slave) synchronization, that is, a master (master node) can have multiple slaves (slave nodes), and a slave can have multiple slaves. The data is synchronized to the slave corresponding to the master, and then each slave synchronizes the data to the slave corresponding to the slave.

Glance is the image service component of OpenStack, which provides virtual machine image discovery, registration, and acquisition services. The API (application program interface) provided by Glance can query the metadata of the virtual machine image and obtain the image. With Glance, virtual machine images can be stored on a variety of storage, such as file storage or object storage.

In order to solve the problems in the prior art, the embodiment of the present invention provides a cloud host creation method, device and cloud service system. A method for creating a cloud host provided by an embodiment of the present invention will firstly be described in detail below.

It should be noted that the cloud host creation method provided by the embodiment of the present invention can be applied to any target computing node in the cloud service system, wherein the cloud service system can include: computing nodes, caching nodes providing data caching services, A mirror node that provides cloud host mirroring services.

Wherein, the cloud service system may be a cloud service system based on the Openstack framework, or other types of cloud service systems, and the cache nodes providing data cache services may be cache nodes based on Redis cache technology, or other types of caches The node is not limited in this embodiment of the present invention.

Fig. 1 is a schematic flow chart of the first method for creating a cloud host provided by an embodiment of the present invention, the method may include:

S101. Receive a creation instruction for a target cloud host.

Wherein, the creation instruction needs to carry at least the identification information of the target cloud host. Of course, the instruction can also carry other information, such as: the identification information of the image file required to create the target cloud host. This embodiment of the present invention does not To limit.

S102. Determine whether a target image file is saved locally, wherein the target image file is an image file required for creating a target cloud host; if not saved, execute S103.

For example, the target image file may be a system disk image file of the target cloud host, or other types of image files, which is not limited in this embodiment of the present invention.

It can be understood that multiple cloud hosts can be created in one host computer, and if the target computing node has already created the target cloud host, the target computing node has already stored the target image file locally. Or, the target computing node has not created the target cloud host before, but the target image file is saved to the target computing node by the image node in advance, then the target computing node also saves the target image file locally.

Therefore, when receiving the creation instruction for the target cloud host, it can be judged whether the target image file corresponding to the target cloud host is stored locally, and if so, the target cloud host can be created directly according to the target image file stored locally. In this way, there is no need to obtain the target image file from the image node, which speeds up the speed of obtaining the target image file, thereby reducing the access pressure of the image node and shortening the creation time of the cloud host.

Wherein, the specific process of creating the cloud host according to the image file is an existing technology, and will not be repeated here.

S103. Determine a target cache node from cache nodes.

Since the image files corresponding to different cloud hosts are cached in the cache nodes that provide the data cache service, when the target computing node does not store the target image file locally, the target image file can be obtained from the cache node in the cloud service system.

It can be understood that a cache node can be set in the cloud service system, and all computing nodes can obtain required image files from this cache node. However, this will cause excessive reading pressure on this cache node. Therefore, multiple cache nodes can be set in the cloud service system to reduce the reading pressure of each cache node.

It can be understood that when the cloud service system contains multiple cache nodes, one of the cache nodes can be set as the master cache node, and the other cache nodes can be set as slave cache nodes corresponding to the master cache node, and the slave cache nodes cache The image file of the cache node is the same as the image file cached by the main cache node, that is to say, the image files cached in all cache nodes are exactly the same.

In practical applications, the data synchronization mechanism of the Redis cache technology can be used to realize that the mirror file cached by the slave cache node is the same as the mirror file cached by the master cache node. Specifically, the data synchronization mechanism of the Redis cache technology is an existing technology, and details are not described here.

In this case, since the image files cached in all the cache nodes are exactly the same, the target computing node can obtain the target image file from any cache node. In this way, the performance of concurrent downloading of image files by computing nodes in the cloud service system can be further improved, and the ability of concurrent downloading of image files can increase linearly with the increase in the number of secondary cache nodes.

For example, the target computing node may randomly select a cache node from all cache nodes as the target cache node. However, this method may cause more computing nodes to request image files from the same cache node at a certain point in time, resulting in greater reading pressure on the cache node.

Therefore, in order to balance the reading pressure of each cache node, in a preferred embodiment, the step of determining the target cache node from the cache nodes may include:

The target cache node is determined from the cache nodes according to the preset association relationship between the computing node and the cache node.

It can be understood that if each computing node is associated with a cache node, then a cache node only has an association relationship with a fixed number of computing nodes, and each cache node only needs to provide a fixed number of computing nodes with image files. Read service, there will be no phenomenon that a cache node needs to provide services to more computing nodes at the same time, so the reading pressure of each cache node can be reduced.

Among them, the above preset relationship between computing nodes and cache nodes can be generated in the following manner:

According to the number N of cache nodes, determine the sequence number of each cache node, wherein the sequence number is an integer in the interval [0, N-1], and the sequence numbers of any two cache nodes are different;

Calculate the target hash value H of the identification information of each computing node;

Calculate the target modulo value M corresponding to each computing node according to the following expression:

M=mod(H,N);

For each computing node, determine the cache node whose sequence number is the same as the target modulo value of the computing node, and establish an association relationship between the computing node and the determined cache node.

Wherein, the identification information of each computing node may be the computing node's IP address (Internet Protocol Address, Internet Protocol Address), MAC address (MAC Address, physical address), etc., and may also be other information that can uniquely identify the computing node , are all reasonable, and are not limited in this embodiment of the present invention.

The calculation of the target hash value of the identification information of each computing node can be realized by using a preset hash algorithm, where the input value of the hash algorithm can be pure numbers, or a string containing numbers, letters and symbols, and the hash The output of the Greek algorithm is a positive integer. Since the calculation of the hash value using the hash algorithm is an existing technology, details are not described here.

It is known to those skilled in the art that mod(a, b) is a MOD function, which is used for modulo calculation, where a is the dividend and b is the divisor. When a and b are both positive integers, the result of the modulo operation is the remainder of dividing a by b.

It can be understood that, for the expression of the above calculation target modulo value M, when N is determined, for any positive integer H, the modulo operation is performed according to the above expression, and the obtained target modulo value must be [0, N-1 ] an integer value in the interval.

It can be seen from the above that the serial number of each cache node is an integer in the interval [0, N-1], and the serial numbers of any two cache nodes are different, and the target modulo value is also the integer in the interval [0, N-1] A certain integer; therefore, for each computing node, when the corresponding target modulo value is determined, there must be a cache node with the serial number of the target modulo value, and then the cache node is associated with the computing node at this time .

Exemplarily, the number of cache nodes in the cloud service system is 10, the sequence number of the master cache node is determined as 0, and the sequence numbers of other slave cache nodes are determined as 1-9 in turn, and the hash algorithm is performed on the IP addresses of each computing node The corresponding target hash value H is obtained, and the target hash value H is a positive integer value. Based on the target hash value H and the number N of cache nodes, the target modulo value corresponding to each computing node can be calculated.

For example, the hash values H obtained by performing the hash algorithm on the IP addresses of computing nodes A and B are 54 and 100 respectively, and then the hash values 54 and 100 are calculated by performing a modulo operation on the number of cache nodes 10 according to the above expression. The modulo values of are 4 and 0 respectively, then the computing node A is associated with the slave cache node whose serial number is 4, and the computing node B is associated with the primary cache node whose serial number is 0.

Of course, other methods may also be used to establish the association relationship between the computing node and the cache node, which is not limited in this embodiment of the present invention.

In addition, it should be noted that in this embodiment, the serial number of the cache node is used to determine the corresponding relationship between the cache node and different target modulo values. This embodiment may not limit the determination method of the serial number, or may not limit the cache node The specific sequence number, but the corresponding relationship between each cache node and the target modulo value must be specified.

For example: there are currently 8 cache nodes, and the target modulo value must be an integer in the interval [0, 7]. The serial numbers of each cache node are determined to be 7, 12, 52, 9, 18, 35, 29, and 77, and the Correspondence: Cache nodes 7, 12, 52, 9, 18, 35, 29, and 77 points correspond to target modulo values 0, 1, 2, 3, 4, 5, 6, and 7. Therefore, for each computing node, when the target modulus value corresponding to the computing node is calculated, the association relationship between the computing node and the cache node corresponding to the target modulus value can be established, assuming that the target modulus value is 6 , an association relationship between the computing node and the cache node with the serial number 29 is established.

For another example, there are currently 5 cache nodes, and the target modulo value must be an integer in the interval [0, 4]. Mark each cache node as cache node a, b, c, d, and e respectively, and establish a corresponding relationship at the same time: mark as The cache nodes of a, b, c, d, and e correspond to the target modulo values 0, 1, 2, 3, and 4. Therefore, for each computing node, when the target modulus value corresponding to the computing node is calculated, the association relationship between the computing node and the cache node corresponding to the target modulus value can be established, assuming that the target modulus value is 3, Then establish an association relationship between the computing node and the cache node with the serial number d.

It should be noted that it is relatively simple to establish an association relationship between each computing node and only one cache node, which can achieve the purpose of balancing the reading pressure of each cache node. However, in another implementation, it is also possible to associate a computing node with multiple cache nodes, so that when a cache node fails, the computing node can obtain images from other cache nodes that have established an association relationship. document.

S104. Send a first request for acquiring the target image file to the target cache node.

Wherein, the first request needs to carry at least the identification information of the target image file. Of course, the request can also carry other information, which is not limited in this embodiment of the present invention.

S105. Receive target information fed back by the target cache node according to the first request.

It can be understood that the first request carries the identification information of the target image file, so the target cache node can judge whether it has cached the target image file according to the identification information in the first request.

When the target image file is cached in the target cache node, the target information fed back by the target cache node to the target computing node can be the target image file itself; when the target image file is not cached in the target cache node, the target cache node feeds back to the target computing node The target information of may be: a message that the target cache node does not cache the target image file.

S106, judging whether the target information is the target image file; if yes, execute S107; if not, execute S108.

Understandably, when the target computing node receives the target information fed back by the target cache node, it can first determine whether the target information is an image file, and if the target information is not an image file, it can directly determine that the target information is not a target image file.

Further, if the target information is an image file, it can continue to judge whether the identification information in the target information matches the identification information of the target image file, if it does not match, it can be determined that the target information is not a target image file, and if it matches, it can be It is determined that the target information is the target image file.

In addition, since the image file is a specific type of file, its file format can be: ISO, BIN, IMG, GHO, etc. Therefore, whether the target information is a mirror file can be determined by judging whether the target information is a specific type of file.

S107. Create a target cloud host according to the target image file.

S108, sending a second request for acquiring a target image file to the image node; receiving the target image file fed back by the image node according to the second request; creating a target cloud host according to the target image file.

Wherein, the second request needs to carry at least the identification information of the target image file, and of course, the request can also carry other information, which is not limited in this embodiment of the present invention.

It can be understood that when the target cache node feeds back the target image file, the target computing node can create the target cloud host according to the target image file, and if the target cache node does not feed back the target image file, the target computing node also needs to request the target image from the mirror node document.

It should be noted that, in practical applications, the mirroring node itself may store the mirroring file, or may not store the mirroring file, but only record the storage location information of the mirroring file as a database.

When the image node does not store the image file, the image node can feed back the storage location of the target image file to the target computing node, and the target computing node pulls the target image file from the storage location, or the image node pulls the target image file from the storage location It is reasonable to pull to the target computing node, etc., which is not limited in this embodiment of the present invention.

It can be seen from the above that in the solution provided by this embodiment, after receiving the creation instruction for the target cloud host, the computing node first judges whether there is a corresponding target image file in the local cache, and if not, requests the target image file from the cache node , only when the cache node does not cache the target image file, the target image file is requested from the mirror node. It can be seen that applying the solution provided by this embodiment can reduce the access pressure of mirror nodes, realize high concurrent download of mirror files, reduce the time for pulling mirror files, and shorten the creation time of cloud hosts.

A method for creating a cloud host provided by an embodiment of the present invention will be described below with a specific embodiment.

A schematic structural diagram of a cloud service system in a specific embodiment as shown in Figure 2, wherein the Redis node is a cache node based on Redis cache technology, which is divided into a Redis master node and a plurality of Redis slave nodes, and the Glance server provides cloud The mirror node of the host mirror service, the Glance server does not store mirror files, but only records the storage location information of each mirror file, and the storage node is used to store mirror files.

Moreover, the association relationship between each computing node and the Redis node is established in advance, for example, the computing node is associated with the Redis master node whose serial number is 0, and the computing nodes 2 and 3 are both associated with the Redis slave node whose serial number is 1. Wherein, the association relationship is generated according to a modulo value obtained by performing a hash algorithm on the IP addresses of each computing node and moduloing the obtained hash value on the number of Redis nodes.

Exemplarily, if computing node 2 receives an instruction to create a cloud host, then computing node 2 first determines whether the target image file required to create the cloud host is stored locally, and if so, directly according to the target image file stored locally Create a cloud host; otherwise, request the target image file from the Redis slave node with the serial number 1 associated with computing node 2. If the Redis slave node caches the target image file, the computing node can use the target image fed back by the Redis slave node File creation cloud host, if the Redis slave node does not cache the target image file, you need to request the target image file from the Glance server, and the Glance server will pull the target image file from the corresponding storage node to the computing node according to the storage location of the target image file 2.

It can be seen from the above description that after the computing node receives the creation command for the target cloud host, it first judges whether the corresponding target image file is cached locally. If not, it requests the target image file from the cache node, and there is no cache in the cache node. In the case of the target image file, the target image file is requested from the mirror node. It can be seen that the application of this specific embodiment can reduce the access pressure of mirror nodes, realize high concurrent download of mirror files, reduce the pull time of mirror files, and shorten the creation time of cloud hosts.

Corresponding to the above method for creating a cloud host, an embodiment of the present invention also provides a device for creating a cloud host.

The device can be applied to a target computing node in a cloud service system, wherein the cloud service system can include: a computing node, a cache node providing data caching services, and a mirroring node providing cloud host mirroring services.

Corresponding to the method embodiment shown in FIG. 1, FIG. 3 is a first structural schematic diagram of a cloud host creation device provided by an embodiment of the present invention, and the device may include:

The first receiving module 301 is configured to receive a creation instruction for a target cloud host;

The first judging module 302 is used to judge whether the target image file is saved locally, wherein the target image file is an image file required for creating the target cloud host;

A determination module 303, configured to determine the target cache node from the cache nodes when the first determination module 302 determines that the target image file is not saved locally;

A sending module 304, configured to send a first request for acquiring the target image file to the target cache node;

The second receiving module 305 is configured to receive target information fed back by the target cache node according to the first request;

A second judging module 306, configured to judge whether the target information is the target image file;

The first creation module 307 is configured to create the target cloud host according to the target image file when the second judgment module 306 determines that the target information is the target image file;

The second creation module 308 is configured to send a second request for acquiring the target image file to the image node when the second judging module 306 determines that the target information is not the target image file; receive the The image node feeds back the target image file according to the second request; and creates the target cloud host according to the target image file.

In practical applications, the cache node may include: a master cache node and a slave cache node corresponding to the master cache node, where the image file cached by the slave cache node is the same as the mirror file cached by the master cache node;

The determining module 303 may be used for:

According to the preset association relationship between computing nodes and cache nodes, the target cache node is determined from the cache nodes.

In practical applications, the preset relationship between computing nodes and cache nodes may be:

Generated as follows:

According to the number N of cache nodes, determine the sequence number of each cache node, wherein the sequence number is an integer in the interval [0, N-1], and the sequence numbers of any two cache nodes are different;

Calculate the target hash value H of the identification information of each computing node;

Calculate the target modulo value M corresponding to each computing node according to the following expression:

M=mod(H,N);

For each computing node, determine the cache node whose sequence number is the same as the target modulo value of the computing node, and establish an association relationship between the computing node and the determined cache node.

It can be seen from the above that in the solution provided by this embodiment, after receiving the creation instruction for the target cloud host, the computing node first judges whether there is a corresponding target image file in the local cache, and if not, requests the target image file from the cache node , only when the cache node does not cache the target image file, the target image file is requested from the mirror node. It can be seen that applying the solution provided by this embodiment can reduce the access pressure of mirror nodes, realize high concurrent download of mirror files, reduce the time for pulling mirror files, and shorten the creation time of cloud hosts.

Corresponding to the above-mentioned method and device for creating a cloud host, an embodiment of the present invention also provides a cloud service system.

FIG. 4 is a schematic diagram of the first structure of a cloud service system provided by an embodiment of the present invention. The system may include: a computing node 401, a cache node 402 providing data caching services, and a mirroring node 403 providing cloud host mirroring services, wherein ,

The computing node 401 may be configured to: receive a creation instruction for the target cloud host; determine whether the target image file is stored locally, wherein the target image file is an image file required for creating the target cloud host; If it is not saved, determine the target cache node from the cache node 402; send a first request for obtaining the target image file to the target cache node;

The cache node 402 may be configured to: receive a first request for acquiring the target image file sent by the computing node 401; feed back target information to the computing node 401 according to the first request;

The computing node 401 may also be configured to: receive the target information fed back by the target cache node according to the first request; determine whether the target information is the target image file; if yes, according to the target image file The file creates the target cloud host; if not, send a second request for obtaining the target mirror file to the mirror node 403;

The image node 403 may be configured to: receive a second request for acquiring the target image file sent by the computing node 401; feed back the target image file to the computing node 401 according to the second request;

The computing node 401 may also be configured to: receive the target image file fed back by the image node 403 according to the second request; and create the target cloud host according to the target image file.

As shown in FIG. 5, it is a second structural schematic diagram of the cloud service system provided by the embodiment of the present invention. On the basis of the embodiment shown in FIG. 4,

The cache node 402 may include: a master cache node 4021 and a slave cache node 4022 corresponding to the master cache node 4021, the image file cached by the slave cache node 4022 is the same as the mirror file cached by the master cache node 4021;

The computing node 401 may specifically be configured to: determine a target caching node from the caching nodes 402 according to a preset association relationship between computing nodes and caching nodes.

In an implementation manner of the present invention, the computing node 401 may be specifically configured to: determine the sequence number of each cache node 402 according to the number N of cache nodes 402, wherein the sequence number is [0, N-1] An integer in the interval, the sequence numbers of any two cache nodes 402 are different; calculate the target hash value H of the identification information of the computing node 401; calculate the target modulo value M corresponding to the computing node 401 according to the following expression: M= mod(H, N); determine the cache node 402 whose serial number is the same as the target modulo value of the computing node 401 , and establish an association relationship between the computing node 401 and the determined cache node 402 .

It can be seen from the above that in the solution provided by this embodiment, after receiving the creation instruction for the target cloud host, the computing node first judges whether there is a corresponding target image file in the local cache, and if not, requests the target image file from the cache node , only when the cache node does not cache the target image file, the target image file is requested from the mirror node. It can be seen that applying the solution provided by this embodiment can reduce the access pressure of mirror nodes, realize high concurrent download of mirror files, reduce the time for pulling mirror files, and shorten the creation time of cloud hosts.

As shown in FIG. 6, it is a schematic diagram of the third structure of the cloud service system provided by the embodiment of the present invention. On the basis of the embodiment shown in FIG. 4,

The image node 403 may also be configured to: feed back the target image file to the cache node 402;

The cache node 402 may also be configured to: receive the target image file fed back by the mirror node 403, and cache the target image file.

It can be understood that the cache node 402 may be used for caching the image file, and the image node 403 may be used for storing the image file or storing location information of the image file. The image node 403 can feed back the image file to the cache node 402 before the computing node 401 sends the request for obtaining the image file to the cache node 402, so that the computing node 401 can obtain the image file from the cache node 401; After the image node 403 sends the request for obtaining the image file, it feeds back the image file to the cache node 402, so that the computing node 401 can obtain the image file from the cache node 402 when it needs to obtain the image file next time.

It can be understood that the cache resources that the cache node 402 can provide are limited. In order not to affect the normal operation of the cache node 402, the amount of data cached in the cache node 402 cannot be too large. Therefore, the maximum amount of data that can be cached by the cache node 402 can be preset.

In this case, the cache node 402 may specifically be used to: determine whether the amount of data cached locally reaches a preset threshold, if not, cache the target image file, and if so, determine the image file to be deleted locally, The image file to be deleted is deleted, and the target image file is cached.

Specifically, since the probability that the image file with the earliest cache time is acquired again in the cache node 402 is relatively small, the image file with the earliest cache time can be determined as the image file to be deleted;

It is also possible to determine the image file with the least access frequency as the image file to be deleted according to the access frequency of the cached image file;

Alternatively, according to the importance of the cached image files, the image file with the least importance may be determined as the image file to be deleted.

Of course, this application only uses the above as an example for illustration. In practical applications, the image file to be deleted can also be determined according to other principles, and this application does not limit this.

In another implementation manner, if the amount of data cached in the cache node 402 reaches a preset threshold, the cache image file may not be processed.

FIG. 7 is a schematic diagram of the fourth structure of the cloud service system provided by the embodiment of the present invention. On the basis of the embodiment shown in FIG. 6, the cache node 402 may include: a primary cache node 4021 and the primary cache The slave cache node 4022 corresponding to the node 4021;

The mirroring node 402 may be specifically configured to: feed back the target mirroring file to the primary cache node 4021;

The primary cache node 4021 may be configured to: receive the target image file fed back by the mirror node 402, cache the target image file, and then feed back the target image file to the slave cache node 4022;

The slave cache node 4022 may be configured to: receive the target image file fed back by the master cache node 4021, and cache the target image file.

It can be understood that the master cache node 4021 feeds back the image file fed back by the mirror node to the corresponding slave cache node 4022, which can realize data synchronization between the master cache node 4021 and the slave cache node 4022, that is, the mirror image cached in the master cache node 4021 The file is the same as the image file cached from the cache node 4022.

In this way, as long as the target image file is cached in the cache node 402, the computing node can obtain the target image file from any cache node 402, and this method can further improve the performance of concurrently downloading the image file by the computing node 401 in the cloud service system.

Specifically, for the method for caching the target image file by the primary cache node 4021, reference may be made to the relevant description of the embodiment shown in FIG. 6 above, and details are not repeated here.

Exemplary, in the specific embodiment shown in Figure 2, mirror node is Glance server, cache node is Redis node, includes a Redis master node and a plurality of Redis slave nodes, and Redis master node can synchronize the data cached by itself to On each Redis slave node, master-slave synchronization of Redis nodes is realized. Wherein, the Glance server is used to store the storage location information of the image file, and an image-management (image-management) module can be set in the Glance server to pull the image file from the corresponding storage node to the Redis master node.

In this specific embodiment, the image file is cached using the Redis cache technology, and the Redis master-slave synchronization mechanism is used to ensure the consistency of data on different Redis nodes, and the mode of multiple Redis cache nodes is adopted to make the image file download concurrently. Capacity can scale linearly with the number of Redis slave nodes.

FIG. 8 is a schematic diagram of a fifth structure of the cloud service system provided by the embodiment of the present invention. On the basis of the embodiment shown in FIG. 4, the system may further include: a storage node 404 for providing data storage services;

The image node 403 can also be used to: receive the image file uploaded by the user, and store the image file uploaded by the user to the storage node 404 by using object storage technology;

The storage node 404 may be configured to: store the image file uploaded by the user.

Understandably, when a user needs to create a new cloud host on a computing node, the image file corresponding to the new cloud host needs to be uploaded to the cloud service system in advance, wherein the image file corresponding to the new cloud host It can be understood as: a user-defined image file.

It should be noted that object storage technology is a network storage architecture, the core of which is to separate the data path (data read or write) from the control path (metadata), and based on the object storage device (Object-based Storage Dexice, OSD) construction In the storage system, each object storage device has certain intelligence and can automatically manage the distribution of data on it. For the specific introduction of the object storage technology, reference may be made to the prior art, and details are not repeated here.

As can be seen from the description of the above embodiments, the mirroring node 403 may not store the mirroring file, but only saves the storage location information of the mirroring file. Therefore, the mirroring node may utilize the object storage technology to store the mirroring file uploaded by the user in the storage node 404, Record and save the storage location information of the image file.

In order to prevent the image file uploaded by the user from being lost or unavailable due to failure of the storage node 404 , the image node may also save the image file uploaded by the user to a computing node 401 . Specifically, based on the amount of data stored in all computing nodes 401, a computing node 401 may be selected to save the image file according to a capacity balancing policy.

After storing the image file uploaded by the user, the image node 403 can also send the image file to the cache node 402 for caching, so that the computing node 401 can obtain the image file from the cache node 402 .

In practical applications, when the cache node 402 caches the image file uploaded by the user, it may first determine whether the amount of data cached locally reaches a preset threshold, if not, cache the image file, and if so, determine the image file to be deleted locally. file, delete the image file to be deleted, and then cache the image file. In another implementation manner, if the amount of data cached in the cache node 402 reaches a preset threshold, the image file may not be cached.

Specifically, for the method for caching the image file uploaded by the user by the caching node 402, reference may be made to the relevant description of the embodiment shown in FIG. 6 above, and details are not repeated here.

In a preferred embodiment, FIG. 9 is a schematic diagram of the sixth structure of the cloud service system provided by the embodiment of the present invention. On the basis of the embodiment shown in FIG. 8 , the cache node 402 may include: primary cache The node 4021 and the slave cache node 4022 corresponding to the master cache node 4021.

The image node 403 can feed back the image file uploaded by the user to the master cache node 4021, the master cache node 4021 caches the image file, and feeds the image file back to the slave cache node 4022, and the mirror file is also stored in the slave cache node 4022. for caching.

Specifically, for the method of caching the image file uploaded by the user by the master cache node 4021 and the slave cache node 4022, reference may be made to the relevant description of the above embodiment shown in FIG. 7 , which will not be repeated here.

In this way, each cache node 402 has cached the image file uploaded by the user, and the computing node 401 can obtain the image file from any cache node 402. This method can further improve the concurrent downloading of images by computing nodes in the cloud service system. file performance.

Exemplarily, in the specific embodiment shown in Figure 2, using the object storage technology, the Glance server first stores the image file uploaded by the user in a storage node, and then selects a computing node according to the capacity balancing strategy, and the image-management module Pull the image file to the selected computing node for storage. The Glance server can also trigger the image-management module to pull the image file to the Redis master node. If the amount of data cached in the Redis master node has reached the preset threshold, the image file will not be cached. When the computing node is created When the image file corresponds to the cloud host, the _Redis master node adopts the LRU (least recently used) strategy to delete the image file with the least access frequency in the latest preset period of time among the cached image files, and then Uploaded image files are cached.

Each embodiment in this specification is described in a related manner, the same and similar parts of each embodiment can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and for relevant parts, please refer to part of the description of the method embodiments.

It should be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is a relationship between these entities or operations. There is no such actual relationship or order between them. Furthermore, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also includes elements not expressly listed. other elements of or also include elements inherent in such a process, method, article, or device. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present invention are included in the protection scope of the present invention.

Claims (13)

1. a kind of cloud host creation method, which is characterized in that applied to the target computing nodes in cloud service system, wherein, institute Stating cloud service system includes：Calculate node, the cache node that data buffer service is provided, the mirror image that cloud mirrored host computer service is provided Node, the described method includes：

The establishment received for target cloud host instructs；

Judge locally whether preserve target image file, wherein, the target image file is the establishment target cloud host Required image file；

If not preserving, target cache node is determined from the cache node；

The first request for obtaining the target image file is sent to the target cache node；

Receive target information of the target cache node according to the described first request feedback；

Judge whether the target information is the target image file；

If it is, according to the target mirror as described in document creation target cloud host；

If it has not, the second request for obtaining the target image file is sent to the mirror nodes；Receive the mirror nodes According to the target image file of the described second request feedback；According to the target mirror as described in document creation target cloud master Machine.

2. according to the method described in claim 1, it is characterized in that, the cache node includes：Master cache node and the master Cache node is corresponding from cache node, the mirror of the image file and the master cache nodal cache from caching nodal cache As file is identical；

Described the step of target cache node is determined from the cache node, including：

According to default calculate node and the incidence relation of cache node, target cache node is determined from the cache node.

3. according to the method described in claim 2, it is characterized in that, the default calculate node and cache node associate System, generates in the following way：

According to the quantity N of cache node, determine the sequence number of each cache node, wherein, serial number [0, the N-1] section it is whole Number, the sequence number of any two cache node differ；

Calculate the target cryptographic Hash H of the identification information of each calculate node；

The corresponding target Modulus of access M of each calculate node is calculated according to following formula：

M=mod (H, N)；

For each calculate node, determine the sequence number cache node identical with the target Modulus of access of the calculate node, establish the meter Operator node and incidence relation between definite cache node.

4. a kind of cloud host creating device, which is characterized in that applied to the target computing nodes in cloud service system, wherein, institute Stating cloud service system includes：Calculate node, the cache node that data buffer service is provided, the mirror image that cloud mirrored host computer service is provided Node, described device include：

First receiving module, the establishment for receiving for target cloud host instruct；

First judgment module, for judging locally whether preserve target image file, wherein, the target image file is wound Build the image file needed for the target cloud host；

Determining module, for first judgment module judge it is local do not preserve the target image file when, from described Target cache node is determined in cache node；

Sending module, for sending the first request for obtaining the target image file to the target cache node；

Second receiving module, for receiving target information of the target cache node according to the described first request feedback；

Second judgment module, for judging whether the target information is the target image file；

First creation module, for judging that the target information is the target image file in second judgment module When, according to the target mirror as described in document creation target cloud host；

Second creation module, for judging that the target information is not the target image file in second judgment module When, the second request for obtaining the target image file is sent to the mirror nodes；The mirror nodes are received according to The target image file of second request feedback；According to the target mirror as described in document creation target cloud host.

5. device according to claim 4, which is characterized in that the cache node includes：Master cache node and the master Cache node is corresponding from cache node, the mirror of the image file and the master cache nodal cache from caching nodal cache As file is identical；

The determining module, is used for：

According to default calculate node and the incidence relation of cache node, target cache node is determined from the cache node.

6. device according to claim 5, which is characterized in that the default calculate node is associated with cache node It is to be：

It generates in the following way：

According to the quantity N of cache node, determine the sequence number of each cache node, wherein, serial number [0, the N-1] section it is whole Number, the sequence number of any two cache node differ；

Calculate the target cryptographic Hash H of the identification information of each calculate node；

The corresponding target Modulus of access M of each calculate node is calculated according to following formula：

M=mod (H, N)；

For each calculate node, determine the sequence number cache node identical with the target Modulus of access of the calculate node, establish the meter Operator node and incidence relation between definite cache node.

7. a kind of cloud service system, which is characterized in that the system comprises：Calculate node, the caching that data buffer service is provided Node, the mirror nodes that cloud mirrored host computer service is provided, wherein,

The calculate node, is used for：The establishment received for target cloud host instructs；Judge locally whether preserve target mirror picture File, wherein, the target image file is the image file needed for the establishment target cloud host；If not preserving, from described Target cache node is determined in cache node；Send the acquisition target image file to the target cache node first please It asks；

The cache node, is used for：Receive the first request of the acquisition target image file that the calculate node is sent；Root According to the described first request, to the calculate node feedback target information；

The calculate node, is additionally operable to：Receive target information of the target cache node according to the described first request feedback；Sentence Whether the target information of breaking is the target image file；If it is, according to the target mirror as described in document creation target Cloud host；If it has not, the second request for obtaining the target image file is sent to the mirror nodes；

The mirror nodes, are used for：Receive the second request of the acquisition target image file that the calculate node is sent；Root According to the described second request, the target image file is fed back to the calculate node；

The calculate node, is additionally operable to：Receive target mirror picture text of the mirror nodes according to the described second request feedback Part；According to the target mirror as described in document creation target cloud host.

8. system according to claim 7, which is characterized in that the cache node includes：Master cache node and the master Cache node is corresponding from cache node, the mirror of the image file and the master cache nodal cache from caching nodal cache As file is identical；

The calculate node, is specifically used for：According to default calculate node and the incidence relation of cache node, from the caching section Target cache node is determined in point.

9. system according to claim 8, which is characterized in that

The calculate node, is specifically used for：According to the quantity N of cache node, the sequence number of each cache node is determined, wherein, institute The integer in serial number [0, N-1] section is stated, the sequence number of any two cache node differs；Calculate the mark of the calculate node The target cryptographic Hash H of information；The corresponding target Modulus of access M of the calculate node is calculated according to following formula：M=M=mod (H, N)；It determines the sequence number cache node identical with the target Modulus of access of the calculate node, establish the calculate node and determines caching Incidence relation between node.

10. system according to claim 7, which is characterized in that

The mirror nodes, are additionally operable to：The target image file is fed back to the cache node；

The cache node, is additionally operable to：The target image file of the mirror nodes feedback is received, and caches the target Image file.

11. system according to claim 10, which is characterized in that

The cache node, is specifically used for：Judge whether the data volume of local cache reaches predetermined threshold value, if not, caching institute Target image file is stated, if so, determining the local image file to be deleted, the image file to be deleted described in deletion, caching The target image file.

12. system according to claim 10, which is characterized in that the cache node includes：Master cache node and described Master cache node is corresponding from cache node；

The mirror nodes, are specifically used for：To target image file described in the master cache node feeding back；

The master cache node, is used for：The target image file of the mirror nodes feedback is received, and caches the target Image file, then to described from target image file described in caching node feeding back；

It is described from cache node, be used for：The target image file of the master cache node feeding back is received, and caches the target mirror As file.

13. system according to claim 7, which is characterized in that the system also includes：For providing data storage service Memory node；

The mirror nodes, are additionally operable to：The image file that user uploads is received, and using object storage technology, by the user The image file of upload is stored to the memory node；

The memory node, is used for：Store the image file that the user uploads.