WO2021120968A1

WO2021120968A1 - Server capacity expansion method and capacity expansion system

Info

Publication number: WO2021120968A1
Application number: PCT/CN2020/129869
Authority: WO
Inventors: 赵贝; 矫恒浩; 刘云冲
Original assignee: 聚好看科技股份有限公司
Priority date: 2020-03-24
Filing date: 2020-11-18
Publication date: 2021-06-24
Also published as: CN111464603B; CN111464603A

Abstract

Embodiments of the present application provide a server capacity expansion method and a capacity expansion system. According to an embodiment, embedding in advance a virtual cloud host mirror in a first sub-database of a physical machine, and embedding a service container mirror in a second sub-database; when a virtual server needs capacity expansion, directly using the embedded virtual cloud host mirror to build a cloud host container, and loading the configuration file of a target service container mirror to the configuration directory of the cloud host container so as to complete the building of the virtual cloud server. The whole building process does not involve pulling files from a mirror library at a cloud end, but instead uses a virtual cloud host mirror and a service container mirror embedded locally to build a virtual server. During server capacity expansion, the process can prevent network congestion caused by a large number of physical machines making requests to a mirror repository, thereby conserving virtual server build time and achieving rapid capacity expansion.

Description

Server capacity expansion method and capacity expansion system

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office, the application number is 202010214207.4, and the invention title is "a server expansion method and expansion system" on March 24, 2020, the entire content of which is incorporated into this application by reference in.

Technical field

The present disclosure relates to the technical field of smart TVs, and in particular to a server expansion method and expansion system.

Background technique

Virtual server (English name: Linux Virtual Server) is widely used because of its good scalability, reliability and manageability. At present, the virtual server used in the industry mostly adopts the master-standby mode, that is, only one master virtual server provides external services at any time. However, this active-standby mode will cause a large amount of data processing pressure on the main virtual server (also called a cloud server) when the number of requests processed by the main virtual server is large, and it will prolong the time for the main virtual server to respond to requests. , Which greatly reduces the efficiency of the main virtual server to process requests.

Summary of the invention

Based on the above technical problems, the purpose of the invention of this application is to provide a server expansion method and a server expansion system.

The first aspect of the embodiments of the present application shows a server expansion system, including:

The management platform is configured to send creation requests;

A physical machine configured to create a virtual server cluster, the virtual server cluster including at least one virtual server; a virtual cloud host database is configured, and the virtual cloud host database is independently provided with a first sub-database and a second sub-database, the The first sub-database is used to embed the virtual cloud host image, and the second sub-database is used to embed the service container image;

It is further configured to: in response to receiving the creation request sent by the management platform, use the embedded virtual cloud host image to create the cloud host container;

Traverse the second sub-database based on the service container image identifier to obtain a target service container image, where the target service container image is a service container image corresponding to the service container image identifier;

The configuration file of the target service container image is loaded into the configuration directory of the cloud host container to complete the creation of the virtual cloud host, so as to realize the communication with the processing server.

The second aspect of the embodiments of the present application shows a server expansion method, the method is applied to a physical machine, the physical machine is configured with a virtual cloud host database, the virtual cloud host database is independently provided with a first sub-database and a second sub-database A sub-database, the first sub-database is used to embed virtual cloud host images, and the second sub-database is used to embed service container images;

It can be seen from the above technical solutions that the embodiment of the present application shows a server expansion method and a server expansion system. The system includes a management platform configured to send a creation request; a physical machine is configured to create a virtual server cluster and is configured with a virtual server cluster. A cloud host database, the virtual cloud host database is independently provided with a first sub-database and a second sub-database, the first sub-database is used to embed virtual cloud host images, and the second sub-database is used to embed service containers Mirror; is further configured to: in response to receiving a creation request sent by the management platform, use the embedded virtual cloud host image to create a cloud host container; traverse the second sub-database to obtain a target service container based on the service container image identifier Image, the target service container image is a service container image corresponding to the service container image identifier; the configuration file of the target service container image is loaded into the configuration directory of the cloud host container to complete the virtual cloud host Created to achieve communication with the processing server. It can be seen that this embodiment shows that the virtual cloud host image is embedded in the first sub-database of the physical machine in advance, while the service container image is embedded in the second sub-database; when the virtual server needs to be expanded, the embedded virtual server is directly used. The virtual cloud host image creates a cloud host container, and loads the configuration file of the target service container image into the configuration directory of the cloud host container to complete the creation of the virtual cloud server. The entire creation process does not go to the cloud image library. Instead of fetching files, use the embedded virtual cloud host image and service container image to create a virtual server. The above process can avoid network congestion caused by a large number of physical machines requesting a mirror warehouse during server expansion, which can save the creation of virtual servers. Time to achieve the purpose of rapid expansion.

Description of the drawings

In order to explain the technical solutions of the present application more clearly, the following will briefly introduce the drawings needed in the embodiments. Obviously, for those of ordinary skill in the art, without paying creative labor, Other drawings can also be obtained from these drawings.

Fig. 1 is a schematic diagram of a virtual server capacity expansion system according to an embodiment;

Fig. 2 is a structural block diagram of a physical machine according to an embodiment;

Fig. 3 is an interaction diagram of a physical machine, a management platform, and a cloud server according to an embodiment;

Fig. 4 is an interaction diagram of a physical machine and a management platform according to an embodiment;

Fig. 5 is a flowchart showing a method for server expansion according to an embodiment.

Detailed ways

The technical solutions in the embodiments of the present application will be described clearly and completely in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of them. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application.

It should be understood that when used in this specification and appended claims, the terms "including" and "including" indicate the existence of the described features, wholes, steps, operations, elements and/or components, but do not exclude one or The existence or addition of multiple other features, wholes, steps, operations, elements, components, and/or collections thereof.

It should also be understood that the terms used in the specification of this application are only for the purpose of describing specific embodiments and are not intended to limit the application. As used in the specification of this application and the appended claims, unless the context clearly indicates other circumstances, the singular forms "a", "an" and "the" are intended to include plural forms.

Please refer to FIG. 1 and FIG. 2. FIG. 1 is a virtual server expansion system provided by an embodiment of the present application, and FIG. 2 is a structural block diagram of a physical machine in an embodiment of the present application. The expansion system is used for the expansion of the virtual server 21.

Please refer to FIG. 1. The capacity expansion system shown in the embodiment of the present application includes: a management platform 10, a physical machine 20 and a cloud server 30.

The management platform 10, the service container image or cloud host image developed by the developer can be uploaded to the cloud server 30 through the management platform 10. Specifically applied to the solution shown in the embodiment of the present application, the developer can synchronize the developed service container image or cloud host image to the virtual cloud host database 22 of the physical machine 20 through the management platform 10.

Please refer to FIG. 2, where the physical machine 20 is used to create a virtual server cluster. The virtual server cluster includes multiple virtual servers 21. The multiple virtual servers 21 can be deployed on the same physical machine 20 or on multiple servers. On the physical machine 20, no specific restrictions are made here. Specifically applied to this application, the physical machine 20 is provided with a virtual cloud host database 22. The virtual cloud host database is independently provided with a first sub-database 221 and a second sub-database 222, and the first sub-database 221 is used to embed a virtual cloud host database. Cloud host mirroring, and the second sub-database 222 is used to embed service container mirroring.

The cloud server 30 is provided with an image library, and the image library is used to store service container images or cloud host images developed by developers.

FIG. 3 is an interaction diagram of a physical machine, a management platform, and a cloud server in the process of creating a virtual server shown in an embodiment of the application. As shown in FIG. 3, the process of creating a virtual server includes steps S101 to S104.

The S101 management platform 10 is configured to send a creation request;

In this embodiment, when a new virtual server 21 needs to be created in the virtual server cluster, a user such as a developer or a maintainer can send a request for adding a virtual server to the management platform 10. When the management platform 10 receives a request for adding a virtual server, it sends a creation request to the physical machine 20, where the creation request includes at least a service container image identifier, and the service container image identifier is an identifier corresponding to the service container image in the second sub-database. The service container image identifier may be an identifier used to uniquely identify the service container image, such as the name and number of the service container image, and there is no restriction on the specific content of the service container image identifier.

S102, in response to receiving the creation request sent by the management platform, creates a cloud host container using the embedded virtual cloud host image;

It is worth noting that each physical machine 20 is provided with a first sub-database 221 and multiple second sub-databases 222. Therefore, in some embodiments, the creation request sent by the management platform 10 may include the cloud host image identifier. In some embodiments, the creation request sent by the management platform 10 may not include the cloud host image identifier.

The file of the virtual cloud host image in this application is the code of the application program, and the application program code is used to record the construction rules preset by the user. A virtual cloud host image refers to a pre-installed software and configured operating system. This image can be used to quickly create a cloud host. The operating system includes the windows version or the linux version, and the image contains all the things that the server runs normally. When the cloud host is created again after the cloud host image is created, use the image as a benchmark to quickly create a cloud host container.

The physical machine 20 uses the embedded virtual cloud host image to create a container corresponding to the virtual server 21, that is, the cloud host container. After the container is created, the virtual server 21 can run in the container.

In an embodiment, the physical machine 20 may execute the Docker run command to create a corresponding container according to the virtual cloud host image. For example, the physical machine 20 can complete the creation of the cloud host container by executing the following command: docker run LVS-Qugga.

In a feasible embodiment, in response to the inability to create the cloud host container, the physical machine 20 sends a load request for loading the virtual cloud host image to the cloud server 30 to retrieve the virtual cloud host image stored by the cloud server 30. Wherein, the loading request includes a cloud host image identifier, and the cloud host image identifier may be an identifier for uniquely identifying the cloud host image, such as the name and number of the cloud host image, and the specific content of the cloud host image identifier is not restricted here.

Generally, a mirror library is provided in the cloud server 30, and the mirror library stores cloud host images. Usually the number and types of cloud host images are large, and each cloud host image has its corresponding code, so the image library needs to store the code of multiple cloud host images, in order to facilitate the code of the stored cloud host image For management, the image library includes at least one cloud host code warehouse, and each cloud host code warehouse is used to store a kind of cloud host image code. The cloud server 30 can establish the corresponding relationship between the code of the cloud host code warehouse and the cloud host image identifier by detecting the setting operation of the user. Based on this correspondence, when receiving the cloud host image identifier uploaded by the physical machine, the cloud server 30 may retrieve the code corresponding to the cloud host image identifier, and send the code to the physical machine 20 that issued the loading request.

In response to the cloud host image sent by the cloud server 30, the physical machine 20 loads the cloud host image issued by the cloud server 30, and creates a corresponding container according to the cloud host image.

After the creation of the virtual cloud host image is completed, the physical machine 20 is configured to perform step S103 to obtain a target service container image by traversing the second sub-database based on the service container image identifier, and the target service container image is the same as the The service container image ID corresponds to the service container image.

Generally, the virtual cloud host database 22 of the physical machine 20 is stored with a variety of service container images. In order to facilitate the management of the code of the stored service container images, the virtual cloud host database includes a plurality of second sub-databases 222, each The second sub-database 222 is used to store a code of a service container image. The physical machine 20 can establish the corresponding relationship between the code of the second sub-database and the service container image identifier by detecting the setting operation of the user. Based on this correspondence, when the physical machine 20 receives the service container image identifier issued by the management platform 10, the physical machine 20 can determine that the code corresponding to the service container image is the target service container image.

In a feasible embodiment, in response to the configuration file being unable to be loaded into the configuration directory of the cloud host container, a load request for loading the target service container image is sent to the cloud server to retrieve the cloud server storage The target service container image. Wherein, the aforementioned loading request includes the service container image identifier.

Generally, a mirror library is provided in the cloud server 30, and the mirror library stores service container images. Generally, the number and types of service container images are relatively large. In order to facilitate the management of the stored service container image codes, the image library includes at least one service code repository, and each service code repository is used to store the code of a service container image. . The cloud server 30 can establish a corresponding relationship between the code of the service code warehouse and the service container image identifier by detecting the setting operation of the user. Based on this correspondence, when receiving the service container image identifier uploaded by the physical machine, the cloud server 30 may call the code corresponding to the service container image identifier (ie the configuration file of the target service container image), and send the code to The physical machine 20 that issued the load request.

Step S104: Load the configuration file of the target service container image into the configuration directory of the cloud host container to complete the creation of the virtual cloud host, so as to realize the communication with the processing server.

Wherein, a configuration file of the service is recorded in the service container image, and the configuration file includes network address information and port numbers of multiple processing servers managed by the virtual server 21. Then load the configuration file into the configuration directory of the cloud host container. In this way, when the virtual server 21 needs to send the received request to the processing server for processing, it can forward the request to the corresponding processing server according to the network address information and port number of the processing server in the configuration directory, so that the processing server can Process the request.

For the following application scenarios, the service container image stored in the second sub-database needs to be updated.

A scenario. For a published service container image, if the service container image has some defects in the actual use process, which affects the performance of the service container image, the developer of the service container image can use the source code of the service container image Make modifications to overcome the problems in the running process of the service container image, thereby improving the performance of the service container image. After the developer of the service container image has modified the source code of the service container image, the developer of the service container image uploads the modified code of the service container image to the management platform 10. In response to obtaining the update service container image released by the developer, the management platform 10 synchronizes the update container image to the second sub-database. This ensures that the second sub-database always stores the latest version of the service container image.

In another scenario, in order to meet the needs of users, the service container image developer can develop a service container image with new functions, and then upload the developed service container image code to the code warehouse server through the terminal. After the developer of the service container image has modified the source code of the service container image, the developer of the service container image uploads the modified code of the service container image to the management platform 10. In response to obtaining the update service container image released by the developer, the management platform 10 synchronizes the update container image to the second sub-database. This ensures that the second sub-database always stores the latest version of the service container image.

It should be noted that FIG. 3 only illustrates the interaction between one physical machine 20 and the management platform 10, and the interaction between other physical machines 20 and the management platform 10 is similar to the situation in FIG. Out. In addition, it can be understood that the management platform 10 may be installed in a hardware server.

In a feasible embodiment, when the physical machine cannot create the cloud host container, or the physical machine can also interact with other physical machines, the other physical machines are different from the physical machines that are creating the virtual cloud host. Other physical machines use the same cloud host image code as the physical machine that creates the virtual cloud host.

Refer to Figure 4 for the specific interaction process. FIG. 4 is an interaction diagram of a physical machine, a management platform, and other physical machines. As shown in FIG. 4, the method for creating a virtual server includes steps S201 to S204.

S201 The management platform 10 is configured to send a creation request;

Wherein, the method for sending the creation request is similar to the foregoing embodiment, and will not be repeated here.

In S202, in response to receiving the creation request sent by the management platform, create a cloud host container using the embedded virtual cloud host image;

Wherein, the method for creating the cloud host container is similar to the foregoing embodiment, and will not be repeated here.

In a feasible embodiment, in response to the inability to create the cloud host container, the physical machine 20 sends a load request for loading the virtual cloud host image to other physical machines to retrieve the virtual cloud host image stored by the other physical machine. Generally, a virtual cloud host database is provided in other physical machines. The virtual cloud host database is independently provided with a first sub-database and a second sub-database. The first sub-database is used to embed the virtual cloud host image, and the second The sub-database is used to embed the service container image.

When receiving the cloud host image loading request sent by the physical machine 20, other physical machines retrieve the cloud host image pre-buried in the first sub-database, and then send the cloud host image to the corresponding physical machine 20.

The physical machine 20 responds to the cloud host image sent by other physical machines, loads the cloud host image issued by the other physical machine, and creates a corresponding container according to the cloud host image.

After the creation of the virtual cloud host image is completed, the physical machine 20 is configured to perform step S203 to obtain a target service container image by traversing the second sub-database based on the service container image identifier, and the target service container image is the same as the The service container image ID corresponds to the service container image.

Generally, the virtual cloud host database of other physical machines stores multiple service container images. In order to facilitate the management of the code of the stored service container images, the virtual cloud host database includes multiple second sub-databases. The sub-database is used to store the code of a service container image. The other physical machine 20 can establish the correspondence between the code of the second sub-database and the service container image identifier by detecting the setting operation of the user. Based on this correspondence, when the physical machine 20 receives the service container image identifier issued by the management platform 10, the other physical machines 20 can determine that the code corresponding to the service container image is the target service container image.

In a feasible embodiment, in response to the configuration file being unable to be loaded into the configuration directory of the cloud host container, a load request for loading the target service container image is sent to another physical machine to retrieve the other physical machine. The target service container image stored on the machine. Wherein, the aforementioned loading request includes the service container image identifier.

Generally, multiple second sub-databases are set in other physical machines, each second sub-database is used to record a code of a service container image, and each second sub-database corresponds to a service container image identifier. Based on this correspondence, when receiving the service container image identifier uploaded by the physical machine, other physical machines can call the code corresponding to the service container image identifier (ie the configuration file of the target service container image), and send the code to The physical machine that issued the load request.

The physical machine executes step S204 to load the configuration file of the target service container image into the configuration directory of the cloud host container to complete the creation of the virtual cloud host to achieve communication with the processing server.

An embodiment of the present application also provides a server expansion method, the method is applied to a physical machine, the physical machine is configured with a virtual cloud host database, the virtual cloud host database is independently provided with a first sub-database and a second sub-database A database, the first sub-database is used to embed virtual cloud host images, and the second sub-database is used to embed service container images;

The physical machine is configured to perform step S301 in response to receiving a creation request sent by the management platform, and use the embedded virtual cloud host image to create a cloud host container;

Step S302 traverses the second sub-database based on the service container image identifier to obtain a target service container image, where the target service container image is a service container image corresponding to the service container image identifier;

In step S303, the configuration file of the target service container image is loaded into the configuration directory of the cloud host container to complete the creation of the virtual cloud host, so as to realize the communication with the processing server.

Optionally, in response to that the configuration file cannot be loaded into the configuration directory of the cloud host container, send a load request for loading the target service container image to the cloud server to retrieve the target service container stored by the cloud server Mirror.

Optionally, in response to that the configuration file cannot be loaded into the configuration directory of the cloud host container, a load request for loading the target service container image is sent to another physical machine, so as to retrieve the embedded data of the other physical machine. The target service container image.

Optionally, in response to the inability to create the cloud host container, a loading request for loading the virtual cloud host image is sent to the cloud server to retrieve the virtual cloud host image stored by the cloud server.

Optionally, in response to the inability to create the cloud host container, a loading request for loading the virtual cloud host image is sent to other physical machines to retrieve the virtual cloud host image embedded in the other physical machine.

It can be seen from the above technical solutions that the embodiment of the present application shows a server expansion method and a server expansion system. The system includes a management platform configured to send a creation request; a physical machine is configured to create a virtual server cluster and is configured with a virtual server cluster. A cloud host database, the virtual cloud host database is independently provided with a first sub-database and a second sub-database, the first sub-database is used to embed virtual cloud host images, and the second sub-database is used to embed service containers Mirror; is further configured to: in response to receiving a creation request sent by the management platform, use the embedded virtual cloud host image to create a cloud host container; traverse the second sub-database to obtain a target service container based on the service container image identifier Image, the target service container image is a service container image corresponding to the service container image identifier; the configuration file of the target service container image is loaded into the configuration directory of the cloud host container to complete the virtual cloud host Created to achieve communication with the processing server. It can be seen that this embodiment shows that the virtual cloud host image is embedded in the first sub-database of the physical machine in advance, while the service container image is embedded in the second sub-database; when the virtual server needs to be expanded, the embedded virtual server is directly used. The virtual cloud host image creates a cloud host container, and loads the configuration file of the target service container image into the configuration directory of the cloud host container to complete the creation of the virtual cloud server. The entire creation process does not go to the cloud image library Instead of pulling files, it uses the embedded virtual cloud host image and service container image to create a virtual server. The above process can avoid network congestion caused by a large number of physical machines requesting the mirror warehouse during server expansion, which can save the creation of virtual servers. The time of the server achieves the purpose of rapid expansion.

It should be understood that the same or similar parts in the various embodiments in this specification can be referred to each other, and the above-mentioned embodiments do not constitute a limitation on the protection scope of this application. For those skilled in the art, this application can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this application shall be included in the protection scope of this application.

Claims

A server expansion system, which is characterized in that it includes:

The management platform is configured to send creation requests;

A physical machine configured to create a virtual server cluster, the virtual server cluster including at least one virtual server; a virtual cloud host database is configured, and the virtual cloud host database is independently provided with a first sub-database and a second sub-database, the The first sub-database is used to embed the virtual cloud host image, and the second sub-database is used to embed the service container image;

It is further configured to: in response to receiving the creation request sent by the management platform, use the embedded virtual cloud host image to create the cloud host container;

Traverse the second sub-database based on the service container image identifier to obtain a target service container image, where the target service container image is a service container image corresponding to the service container image identifier;

Load the configuration file of the target service container image into the configuration directory of the cloud host container to complete the creation of the virtual cloud host.
The system according to claim 1, wherein the physical machine is further configured to:

In response to the configuration file being unable to be loaded into the configuration directory of the cloud host container, a load request for loading the target service container image is sent to the cloud server to retrieve the target service container image stored by the cloud server.
The system according to claim 1, wherein the physical machine is further configured to:

In response to that the configuration file cannot be loaded into the configuration directory of the cloud host container, send a load request for loading the target service container image to another physical machine to retrieve the target service container image embedded in the other physical machine .
The system according to claim 1, wherein the physical machine is further configured to:

In response to the inability to create the cloud host container, a load request for loading the virtual cloud host image is sent to the cloud server to retrieve the virtual cloud host image stored by the cloud server.
The system according to claim 1, wherein the physical machine is further configured to:

In response to the inability to create the cloud host container, a load request for loading the virtual cloud host image is sent to other physical machines to retrieve the virtual cloud host image embedded in the other physical machines.
The system according to claim 1, wherein the physical machine is further configured to:

In response to obtaining the update service container image released by the developer, the update container image is synchronized into the second sub-database.
A server expansion method, characterized in that the method is applied to a physical machine, the physical machine is configured with a virtual cloud host database, the virtual cloud host database is independently provided with a first sub-database and a second sub-database, The first sub-database is used to embed the virtual cloud host image, and the second sub-database is used to embed the service container image;

In response to receiving the creation request sent by the management platform, use the embedded virtual cloud host image to create a cloud host container;

Traverse the second sub-database based on the service container image identifier to obtain a target service container image, where the target service container image is a service container image corresponding to the service container image identifier;

The configuration file of the target service container image is loaded into the configuration directory of the cloud host container to complete the creation of the virtual cloud host, so as to realize the communication with the processing server.
The method according to claim 7, wherein:

In response to that the configuration file cannot be loaded into the configuration directory of the cloud host container, a load request for loading the target service container image is sent to the cloud server to retrieve the target service container image stored by the cloud server.
The method according to claim 7, wherein:

In response to that the configuration file cannot be loaded into the configuration directory of the cloud host container, send a load request for loading the target service container image to another physical machine to retrieve the target service container image embedded in the other physical machine .
The method according to claim 7, wherein:

In response to the inability to create the cloud host container, a load request for loading the virtual cloud host image is sent to the cloud server to retrieve the virtual cloud host image stored by the cloud server.