CN111464603B - Server capacity expansion method and system - Google Patents
Server capacity expansion method and system Download PDFInfo
- Publication number
- CN111464603B CN111464603B CN202010214207.4A CN202010214207A CN111464603B CN 111464603 B CN111464603 B CN 111464603B CN 202010214207 A CN202010214207 A CN 202010214207A CN 111464603 B CN111464603 B CN 111464603B
- Authority
- CN
- China
- Prior art keywords
- cloud host
- mirror image
- database
- sub
- service container
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Abstract
The embodiment of the application shows a server capacity expansion method and a capacity expansion system, in this embodiment, a virtual cloud host mirror image is pre-embedded in a first sub-database of a physical machine, and a service container mirror image is pre-embedded in a second sub-database; when the virtual server needs to be expanded, a cloud host container is created directly by using the pre-embedded virtual cloud host mirror image, the configuration file of the target service container mirror image is loaded into the configuration directory of the cloud host container to complete the creation of the virtual cloud server, the file is not pulled by the cloud mirror library in the whole creation process, but the virtual server is created by using the pre-embedded virtual cloud host mirror image and the service container mirror image, and the process can avoid network congestion caused by a large number of physical machines requesting the mirror image warehouse during the expansion of the server, so that the time for creating the virtual server can be saved, and the purpose of rapid expansion is achieved.
Description
Technical Field
The disclosure relates to the technical field of smart televisions, in particular to a server capacity expansion method and a server capacity expansion system.
Background
The virtual Server (english name: Linux Vi real Server) is widely used due to its excellent scalability, reliability and manageability. Currently, the industry uses virtual servers mostly in a master-standby mode, that is, only one master virtual server provides external services at any time. However, in the active/standby mode, when the number of requests to be processed by the main virtual server is large, a large data processing pressure is applied to the main virtual server (which may also be referred to as a cloud server), and the time for the main virtual server to respond to the requests is prolonged, so that the efficiency of the main virtual server in processing the requests is greatly reduced.
Disclosure of Invention
Based on the above technical problem, an object of the present invention is to provide a server capacity expansion method and a capacity expansion system.
A first aspect of an embodiment of the present application shows a server capacity expansion system, including:
a management platform configured to send a create request;
a physical machine configured to create a virtual server cluster, the virtual server cluster including at least one virtual server; the method comprises the steps that a virtual cloud host database is configured, a first sub-database and a second sub-database are independently arranged in the virtual cloud host database, the first sub-database is used for embedding a virtual cloud host mirror image in advance, and the second sub-database is used for embedding a service container mirror image in advance;
is further configured to: in response to receiving a creation request sent by a management platform, creating a cloud host container by utilizing a pre-embedded virtual cloud host mirror image;
traversing the second sub-database based on the service container mirror image identifier to obtain a target service container mirror image, wherein the target service container mirror image is a service container mirror image corresponding to the service container mirror image identifier;
and loading the configuration file of the target service container mirror image into a 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.
A second aspect of the embodiment of the present application shows a server capacity expansion method, where 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 for embedding a virtual cloud host mirror image, and the second sub-database is used for embedding a service container mirror image;
is further configured to: in response to receiving a creation request sent by a management platform, creating a cloud host container by utilizing a pre-embedded virtual cloud host mirror image;
traversing the second sub-database based on the service container mirror image identifier to obtain a target service container mirror image, wherein the target service container mirror image is a service container mirror image corresponding to the service container mirror image identifier;
and loading the configuration file of the target service container mirror image into a 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.
As can be seen from the foregoing technical solutions, the embodiment of the present application illustrates a server capacity expansion method and a capacity expansion system, where the system includes a management platform configured to send a creation request; the system comprises a physical machine, a service container mirror image pre-embedding device and a service container mirror image pre-embedding device, wherein the physical machine is configured to create a virtual server cluster and 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 for pre-embedding the virtual cloud host mirror image, and the second sub-database is used for pre-embedding the service container mirror image; is further configured to: in response to receiving a creation request sent by a management platform, creating a cloud host container by utilizing a pre-embedded virtual cloud host mirror image; traversing the second sub-database based on the service container mirror image identifier to obtain a target service container mirror image, wherein the target service container mirror image is a service container mirror image corresponding to the service container mirror image identifier; and loading the configuration file of the target service container mirror image into a 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. It can be seen that in the embodiment, a virtual cloud host mirror image is pre-embedded in a first sub-database of a physical machine, and a service container mirror image is pre-embedded in a second sub-database; when the virtual server needs to be expanded, a cloud host container is created directly by using the pre-embedded virtual cloud host mirror image, the configuration file of the target service container mirror image is loaded into the configuration directory of the cloud host container to complete the creation of the virtual cloud server, the file is not pulled by the cloud mirror library in the whole creation process, but the virtual server is created by using the pre-embedded virtual cloud host mirror image and the service container mirror image, and the process can avoid network congestion caused by a large number of physical machines requesting the mirror image warehouse during the expansion of the server, so that the time for creating the virtual server can be saved, and the purpose of rapid expansion is achieved.
Drawings
In order to more clearly explain the technical solution of the present application, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious to those skilled in the art that other drawings can be obtained according to the drawings without any creative effort.
FIG. 1 is a schematic diagram illustrating a virtual server capacity expansion system according to an embodiment;
FIG. 2 is a block diagram illustrating the structure of a physical machine, according to one embodiment;
fig. 3 is an interaction diagram illustrating a physical machine, a management platform, and a cloud server, according to an embodiment;
FIG. 4 is an interaction diagram illustrating a physical machine, management platform, according to one embodiment;
fig. 5 is a flowchart illustrating a server capacity expansion method according to an embodiment.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the present application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification of the present application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
Referring to fig. 1 and fig. 2, fig. 1 is a structural block diagram of a virtual server capacity expansion system according to an embodiment of the present application, and fig. 2 is a structural block diagram of a physical machine according to an embodiment of the present application, where the capacity expansion system is used for capacity expansion of a virtual server 21.
Referring to fig. 1, an expansion system according to an embodiment of the present application includes: management platform 10, physical machine 20 and cloud server 30.
The management platform 10, the service container image or the cloud host image developed by the developer may 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, a developer may synchronize a developed service container image or cloud host image into the virtual cloud host database 22 of the physical machine 20 through the management platform 10.
Referring to fig. 2, the physical machine 20 is used to create a virtual server cluster, where the virtual server cluster includes a plurality of virtual servers 21, and the plurality of virtual servers 21 may be deployed on the same physical machine 20 or on a plurality of physical machines 20, which is not limited herein. Specifically, in the present 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, the first sub-database 221 is used for pre-embedding a virtual cloud host mirror image, and the second sub-database 222 is used for pre-embedding a service container mirror image.
The cloud server 30 is provided with a mirror library, and the mirror library is used for storing service container mirrors or cloud host mirrors developed by developers.
Fig. 3 is an interaction diagram of a physical machine, a management platform, and a cloud server in a virtual server creation process according to an embodiment of the present application, where the virtual server creation process shown in fig. 3 includes steps S101 to S104.
S101 the management platform 10 is configured to send a create 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 maintenance person may send a request for adding a virtual server to the management platform 10. When receiving the request for adding the virtual server, the management platform 10 sends a creation request to the physical machine 20, where the creation request at least includes a service container mirror image identifier, the service container mirror image identifier is an identifier corresponding to a service container mirror image in the second sub-database, and the service container mirror image identifier may be an identifier used for uniquely identifying the service container mirror image, such as a name and a number of the service container mirror image, where specific content of the service container mirror image identifier is not limited.
S102, in response to receiving a creation request sent by a management platform, creating a cloud host container by using a pre-embedded virtual cloud host mirror image;
it should be noted that each physical machine 20 is provided with a first sub-database 221 and a plurality of second sub-databases 222. Thus, in some embodiments, the cloud host image identification may be included in the creation request sent by the management platform 10. In some embodiments, the creation request sent by the management platform 10 may not include the cloud host image identification.
The file of the virtual cloud host image is an application program code, and the application program code is used for recording a construction rule preset by a user. The virtual cloud host image is an operating system which is pre-installed with software and configured, and can be used for quickly creating a cloud host. The operating system includes a windows version or an l i nux version, and the image contains everything that the server normally runs. And when the cloud host is created again after the cloud host mirror image is created, the cloud host container is quickly created by taking the mirror image as a reference.
The physical machine 20 creates a container corresponding to the virtual server 21, i.e. a cloud host container, using the pre-embedded virtual cloud host image. After the container is created, the virtual server 21 may run in the container.
In an embodiment, the physical machine 20 may create a corresponding container from the virtual cloud host image by executing a Docker run command. For example, physical machine 20 may complete the creation of the cloud host container by executing the following commands: docker run LVS-Qugga.
In one feasible embodiment, in response to failing to create the cloud host container, the physical machine 20 sends a loading 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. The loading request comprises a cloud host mirror image identifier, the cloud host mirror image identifier can be an identifier used for uniquely identifying the cloud host mirror image, such as the name and the number of the cloud host mirror image, and specific content of the cloud host mirror image identifier is not limited herein.
Typically, a mirror library is disposed in the cloud server 30, and the mirror library stores cloud host mirrors. Generally, the number and the types of the cloud host mirror images are large, each cloud host mirror image has a corresponding code, so that a plurality of cloud host mirror image codes need to be stored in a mirror image library, in order to manage the stored cloud host mirror image codes, the mirror image library comprises at least one cloud host code warehouse, and each cloud host code warehouse is used for storing one cloud host mirror image code. The cloud server 30 may establish a correspondence between the code of the cloud host code repository and the cloud host mirror identifier by detecting a setting operation of the user. Based on the correspondence, when receiving the cloud host image identifier uploaded by the physical machine, the cloud server 30 may retrieve a code corresponding to the cloud host image identifier and send the code to the physical machine 20 that issued the loading request.
The physical machine 20, in response to the cloud host image sent by the cloud server 30, loads the cloud host image sent by the cloud server 30, and creates a corresponding container according to the cloud host image.
After the virtual cloud host image is created, the physical machine 20 is configured to execute step S103 to 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.
In general, a plurality of service container images are stored in the virtual cloud host database 22 of the physical machine 20, and in order to facilitate management of codes of the stored service container images, the virtual cloud host database includes a plurality of second sub-databases 222, and each second sub-database 222 is configured to store a code of one service container image. The physical machine 20 may establish a correspondence between the code of the second sub-database and the mirror identifier of the service container by detecting a setting operation of the user. Based on the correspondence, when the physical machine 20 receives the service container mirror image identifier issued by the management platform 10, the physical machine 20 may determine that the code corresponding to the service container mirror image is the target service container mirror image.
In a feasible embodiment, in response to that the configuration file cannot be loaded into the configuration directory of the cloud host container, a loading request for loading a target service container image is sent to a cloud server to retrieve the target service container image stored by the cloud server. Wherein, the loading request comprises a service container mirror image identifier.
Typically, a mirror library is provided in the cloud server 30, and the mirror library stores mirror images of service containers. The number and types of the service container images are more, and in order to manage the stored codes of the service container images, the image library comprises at least one service code warehouse, and each service code warehouse is used for storing the codes of one service container image. The cloud server 30 may establish a correspondence between the code of the service code repository and the mirror identifier of the service container by detecting a setting operation of the user. Based on the correspondence, when receiving the service container image identifier uploaded by the physical machine, the cloud server 30 may retrieve a code corresponding to the service container image identifier (i.e., a configuration file of the target service container image), and send the code to the physical machine 20 that issued the load request.
Step S104, loading the configuration file of the target service container mirror image into a configuration directory of the cloud host container to complete the creation of a virtual cloud host, so as to realize the communication with a processing server.
Wherein, the service container image records a configuration file of the service, and the configuration file includes network address information and port numbers of a plurality of processing servers managed by the virtual server 21. The configuration file is then loaded into a configuration directory of the cloud host container. Thus, when the virtual server 21 needs to send the received request to the processing server for processing, the request can be forwarded to the corresponding processing server according to the network address information and the 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.
For a scenario, for a published service container mirror image, if the service container mirror image has some defects in the actual use process, the performance of the service container mirror image is affected, and a developer of the service container mirror image can modify the source code of the service container mirror image, so that the problem of the service container mirror image in the operation process is solved, and the performance of the service container mirror image is improved. When the developer of the service container image completes the modification of 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. The management platform 10 synchronizes the update container mirror image into the second sub-database in response to acquiring the update service container mirror image issued by the developer. Thereby ensuring that the second sub-database always stores the latest version of the service container image.
In another scenario, in order to meet the use requirements of users, developers of the service container mirror image can develop a service container mirror image with new functions, and then upload codes of the developed service container mirror image to a code warehouse server through a terminal. When the developer of the service container image completes the modification of 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. The management platform 10 synchronizes the update container mirror image into the second sub-database in response to acquiring the update service container mirror image issued by the developer. Thereby ensuring that the second sub-database always stores the latest version of the service container image.
It should be noted that fig. 3 only illustrates an interaction between one physical machine (which may be referred to as a first physical machine in this embodiment) 20 and the management platform 10, and the interaction between the other physical machines 20 (which may be referred to as second physical machines in this embodiment) and the management platform 10 is similar to that in fig. 3 and is not necessarily depicted. In addition, it is understood that the management platform 10 may be installed in a server of hardware.
In a feasible embodiment, the physical machine cannot create the cloud host container, or in the case of the physical machine, the physical machine can interact with other physical machines, wherein the other physical machines are different from the physical machine which creates the virtual cloud host. The other physical machines and the physical machine for creating the virtual cloud host adopt the same code of the cloud host image.
The specific interaction process can be seen in fig. 4. Fig. 4 is an interaction diagram of a physical machine, a management platform, and other physical machines, and the creating method of the virtual server shown in fig. 4 includes steps S201 to S204.
S201 the management platform 10 is configured to send a create request;
the sending method of the creation request is similar to the above embodiments, and is not described herein again.
S202, in response to receiving a creation request sent by a management platform, creating a cloud host container by using a pre-embedded virtual cloud host mirror image;
the method for creating the cloud host container is similar to the above embodiments, and is not described herein again.
In a feasible embodiment, in response to failing to create the cloud host container, the physical machine 20 sends a load request for loading the virtual cloud host image to the other physical machine to retrieve the virtual cloud host image stored by the other physical machine. Generally, a virtual cloud host database is arranged in other physical machines, and the virtual cloud host database is independently provided with a first sub-database and a second sub-database, wherein the first sub-database is used for pre-embedding a virtual cloud host mirror image, and the second sub-database is used for pre-embedding a service container mirror image.
And when receiving the cloud host image loading request sent by the physical machine 20, the other physical machines call the cloud host image pre-embedded 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 mirror images sent by other physical machines, loads the cloud host mirror images sent by the other physical machines, and creates a corresponding container according to the cloud host mirror images.
After the virtual cloud host image is created, the physical machine 20 is configured to execute step S203 to 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.
In general, a plurality of service container images are stored in the virtual cloud host database of other physical machines, and in order to facilitate management of codes of the stored service container images, the virtual cloud host database includes at least a plurality of second sub-databases, each of which is used for storing a code of one service container image. The other physical machines 20 may establish a correspondence between the code of the second sub-database and the service container mirror identifier by detecting a setting operation of the user. Based on the corresponding relationship, when the physical machine 20 receives the service container mirror image identifier issued by the management platform 10, the other physical machines 20 may determine that the code corresponding to the service container mirror image is the target service container mirror image.
In a feasible embodiment, in response to that the configuration file cannot be loaded into the configuration directory of the cloud host container, a loading request for loading the target service container image is sent to the other physical machine, so as to retrieve the target service container image stored by the other physical machine. Wherein, the loading request comprises a service container mirror image identifier.
Usually, a plurality of second sub-databases are provided in the other physical machines, each second sub-database is used for recording a code of a service container mirror image, and each second sub-database corresponds to a service container mirror image identifier. Based on the corresponding relationship, when receiving the service container image identifier uploaded by the physical machine, the other physical machines may invoke a code corresponding to the service container image identifier (i.e., a configuration file of the target service container image), and send the code to the physical machine that issued the load request.
And the physical machine executes the step S204, 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 host, so as to implement communication with the processing server.
Wherein, the service container image records a configuration file of the service, and the configuration file includes network address information and port numbers of a plurality of processing servers managed by the virtual server 21. The configuration file is then loaded into a configuration directory of the cloud host container. Thus, when the virtual server 21 needs to send the received request to the processing server for processing, the request can be forwarded to the corresponding processing server according to the network address information and the port number of the processing server in the configuration directory, so that the processing server can process the request.
The method for expanding the capacity of the server is applied to a physical machine, the physical machine is provided 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 for embedding a virtual cloud host mirror image in advance, and the second sub-database is used for embedding a service container mirror image in advance;
the physical machine is configured to execute step S301, in response to receiving a creation request sent by a management platform, creating a cloud host container by using a pre-embedded virtual cloud host image;
step S302, traversing the second sub-database based on the service container mirror image identifier to obtain a target service container mirror image, wherein the target service container mirror image is a service container mirror image corresponding to the service container mirror image identifier;
step S303 loads the configuration file of the target service container image into the configuration directory of the cloud host container to complete creation of the virtual cloud host, so as to implement 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, sending a loading request for loading a target service container image to a cloud server to retrieve the target service container image stored by the cloud server.
Optionally, in response to that the configuration file cannot be loaded into the configuration directory of the cloud host container, sending a loading request for loading the target service container image to another physical machine, so as to retrieve the target service container image pre-embedded by the other physical machine.
Optionally, in response to failing 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 that the cloud host container cannot be created, sending a loading request for loading the virtual cloud host image to the other physical machine to call the virtual cloud host image pre-embedded by the other physical machine.
As can be seen from the foregoing technical solutions, the embodiment of the present application illustrates a server capacity expansion method and a capacity expansion system, where the system includes a management platform configured to send a creation request; the system comprises a physical machine, a service container mirror image pre-embedding device and a service container mirror image pre-embedding device, wherein the physical machine is configured to create a virtual server cluster and 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 for pre-embedding the virtual cloud host mirror image, and the second sub-database is used for pre-embedding the service container mirror image; is further configured to: in response to receiving a creation request sent by a management platform, creating a cloud host container by utilizing a pre-embedded virtual cloud host mirror image; traversing the second sub-database based on the service container mirror image identifier to obtain a target service container mirror image, wherein the target service container mirror image is a service container mirror image corresponding to the service container mirror image identifier; and loading the configuration file of the target service container mirror image into a 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. It can be seen that in the embodiment, a virtual cloud host mirror image is pre-embedded in a first sub-database of a physical machine, and a service container mirror image is pre-embedded in a second sub-database; when the virtual server needs to be expanded, a cloud host container is created directly by using the pre-embedded virtual cloud host mirror image, the configuration file of the target service container mirror image is loaded into the configuration directory of the cloud host container to complete the creation of the virtual cloud server, the whole creation process does not reach the mirror image library at the cloud end to pull the file, but the virtual server is created by using the pre-embedded virtual cloud host mirror image and the service container mirror image, and the process can avoid network congestion caused by a large number of physical machines requesting a mirror image warehouse during the expansion of the server, so that the time for creating the virtual server can be saved, and the purpose of rapid expansion is achieved.
It should be understood that the same and similar parts in the various embodiments of the present specification are referred to each other, and the above embodiments should not be construed as limiting the scope of the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (5)
1. A server capacity expansion system, comprising:
a management platform configured to send a create request;
a first physical machine and a second physical machine configured to create a virtual server cluster, the virtual server cluster including at least one virtual server; the first physical machine and the second physical machine are both provided 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 for pre-embedding a virtual cloud host mirror image, and the second sub-database is used for pre-embedding a service container mirror image;
the first physical machine is configured to: in response to a creation request sent by a management platform, creating a cloud host container by using a virtual cloud host mirror image pre-embedded in a local first sub-database;
if the cloud host container cannot be created, sending a loading request for loading the virtual cloud host image to a second physical machine so as to call the virtual cloud host image pre-embedded in a first sub-database of the second physical machine; if the cloud host container is successfully created, when a service container mirror image identifier issued by the management platform is received, determining that a code corresponding to the service container mirror image is a target service container mirror image according to the corresponding relation between the code of the local second sub database and the service container mirror image identifier;
and loading the configuration file of the target service container mirror image into a configuration directory of the cloud host container to complete the creation of the virtual cloud host.
2. The system of claim 1, wherein the first physical machine is further configured to:
and sending a loading request for loading a target service container mirror image to the second physical machine in response to the fact that the configuration file cannot be loaded into the configuration directory of the cloud host container, so as to call the target service container mirror image pre-buried in a second sub-database of the second physical machine.
3. The system of claim 1, wherein the first physical machine is further configured to:
and synchronizing the updated service container mirror image to the second sub-database of the first physical machine and the second sub-database of the second physical machine in response to acquiring the updated service container mirror image issued by the developer.
4. The server capacity expansion method is applied to a first physical machine, wherein the first physical machine is provided 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 for embedding a virtual cloud host mirror image, and the second sub-database is used for embedding a service container mirror image;
in response to a creation request sent by a management platform, creating a cloud host container by using a virtual cloud host mirror image pre-embedded in a local first sub-database;
if the cloud host container cannot be created, sending a loading request for loading a virtual cloud host image to a second physical machine so as to call a virtual cloud host image pre-embedded in a first sub-database of the second physical machine, wherein the second physical machine is also configured with the virtual cloud host database;
if the cloud host container is successfully created, when a service container mirror image identifier issued by the management platform is received, determining that a code corresponding to the service container mirror image is a target service container mirror image according to the corresponding relation between the code of the local second sub database and the service container mirror image identifier;
and loading the configuration file of the target service container mirror image into a 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.
5. The method of claim 4,
and sending a loading request for loading a target service container mirror image to the second physical machine in response to the fact that the configuration file cannot be loaded into the configuration directory of the cloud host container, so as to call the target service container mirror image pre-embedded in a second sub-database of the second physical machine.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010214207.4A CN111464603B (en) | 2020-03-24 | 2020-03-24 | Server capacity expansion method and system |
| PCT/CN2020/129869 WO2021120968A1 (en) | 2020-03-24 | 2020-11-18 | Server capacity expansion method and capacity expansion system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010214207.4A CN111464603B (en) | 2020-03-24 | 2020-03-24 | Server capacity expansion method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111464603A CN111464603A (en) | 2020-07-28 |
| CN111464603B true CN111464603B (en) | 2022-03-29 |
Family
ID=71680833
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010214207.4A Active CN111464603B (en) | 2020-03-24 | 2020-03-24 | Server capacity expansion method and system |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN111464603B (en) |
| WO (1) | WO2021120968A1 (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111464603B (en) * | 2020-03-24 | 2022-03-29 | 聚好看科技股份有限公司 | Server capacity expansion method and system |
| CN113360250B (en) * | 2021-08-09 | 2021-12-14 | 连连宝(杭州)信息技术有限公司 | Application service resource control method, device, equipment and medium |
| CN114490544B (en) * | 2022-04-18 | 2022-06-28 | 梯度云科技(北京)有限公司 | Method and device for downloading container mirror image by newly adding host |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104468734A (en) * | 2014-11-18 | 2015-03-25 | 国云科技股份有限公司 | Virtual cluster expanding method based on cloning |
| CN106487850A (en) * | 2015-08-29 | 2017-03-08 | 华为技术有限公司 | The methods, devices and systems of mirror image are obtained under a kind of cloud environment |
| CN108205481A (en) * | 2016-12-19 | 2018-06-26 | 华为技术有限公司 | The container instance creation method and device of application |
| CN108833163A (en) * | 2018-06-13 | 2018-11-16 | 平安科技（深圳）有限公司 | Creation method, device, computer equipment and the storage medium of Linux virtual server |
| WO2019024122A1 (en) * | 2017-07-31 | 2019-02-07 | 国云科技股份有限公司 | System for producing cloud platform mirror image, and implementation method therefor |
| CN109739744A (en) * | 2018-12-05 | 2019-05-10 | 北京奇艺世纪科技有限公司 | A kind of test macro and method |
| CN110752947A (en) * | 2019-10-18 | 2020-02-04 | 北京浪潮数据技术有限公司 | K8s cluster deployment method and device, and deployment platform |
Family Cites Families (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8806479B2 (en) * | 2007-06-05 | 2014-08-12 | International Business Machines Corporation | Creating an application virtual machine image by isolating installation artifacts in shadow area |
| CN103067425B (en) * | 2011-10-20 | 2016-04-27 | 中国移动通信集团公司 | Virtual machine creation method, virtual machine management system and relevant device |
| US9462427B2 (en) * | 2015-01-14 | 2016-10-04 | Kodiak Networks, Inc. | System and method for elastic scaling using a container-based platform |
| US10585690B2 (en) * | 2016-09-30 | 2020-03-10 | Vmware, Inc. | Online promote disk using mirror driver |
| US20180285139A1 (en) * | 2017-04-02 | 2018-10-04 | vEyE Security Ltd. | Hypervisor-based containers |
| CN107733704B (en) * | 2017-09-29 | 2021-02-26 | 中国石油化工股份有限公司 | Virtualization and container technology-based cloud exploration and development system and method |
| CN109379235B (en) * | 2018-11-27 | 2019-08-30 | 无锡华云数据技术服务有限公司 | Method based on high concurrent request scene creation cloud host |
| CN110471740A (en) * | 2019-07-31 | 2019-11-19 | 北京百度网讯科技有限公司 | Execute method, apparatus, equipment and the computer storage medium of machine learning task |
| CN110674043B (en) * | 2019-09-24 | 2023-09-12 | 聚好看科技股份有限公司 | Processing method and server for application debugging |
| CN111464603B (en) * | 2020-03-24 | 2022-03-29 | 聚好看科技股份有限公司 | Server capacity expansion method and system |
-
2020
- 2020-03-24 CN CN202010214207.4A patent/CN111464603B/en active Active
- 2020-11-18 WO PCT/CN2020/129869 patent/WO2021120968A1/en active Application Filing
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104468734A (en) * | 2014-11-18 | 2015-03-25 | 国云科技股份有限公司 | Virtual cluster expanding method based on cloning |
| CN106487850A (en) * | 2015-08-29 | 2017-03-08 | 华为技术有限公司 | The methods, devices and systems of mirror image are obtained under a kind of cloud environment |
| CN108205481A (en) * | 2016-12-19 | 2018-06-26 | 华为技术有限公司 | The container instance creation method and device of application |
| WO2019024122A1 (en) * | 2017-07-31 | 2019-02-07 | 国云科技股份有限公司 | System for producing cloud platform mirror image, and implementation method therefor |
| CN108833163A (en) * | 2018-06-13 | 2018-11-16 | 平安科技（深圳）有限公司 | Creation method, device, computer equipment and the storage medium of Linux virtual server |
| CN109739744A (en) * | 2018-12-05 | 2019-05-10 | 北京奇艺世纪科技有限公司 | A kind of test macro and method |
| CN110752947A (en) * | 2019-10-18 | 2020-02-04 | 北京浪潮数据技术有限公司 | K8s cluster deployment method and device, and deployment platform |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2021120968A1 (en) | 2021-06-24 |
| CN111464603A (en) | 2020-07-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107515776B (en) | Method for upgrading service continuously, node to be upgraded and readable storage medium | |
| CN111464603B (en) | Server capacity expansion method and system | |
| CN108683516B (en) | Application instance upgrading method, device and system | |
| CN107005426B (en) | Method and device for managing life cycle of virtual network function | |
| CN111124475B (en) | Method for storage management, electronic device, and computer-readable storage medium | |
| CN111399764B (en) | Data storage method, data reading device, data storage equipment and data storage medium | |
| EP3879875A1 (en) | Resource change method and device, apparatus, and storage medium | |
| CN113315754B (en) | Intelligent linkage method, device, equipment and medium for firewall of container visit | |
| US11740886B2 (en) | Algorithm update method and apparatus | |
| CN112860282B (en) | Cluster plug-in upgrading method, device and server | |
| CN113094430B (en) | Data processing method, device, equipment and storage medium | |
| CN111240892A (en) | Data backup method and device | |
| CN113590169B (en) | Application deployment method, application deployment system, and computer-readable storage medium | |
| CN113190619B (en) | Data read-write method, system, equipment and medium for distributed KV database | |
| CN112667711B (en) | MySQL read-only instance management method, system and computer readable medium | |
| CN110113217B (en) | Micro-service management method, device, management platform and storage medium | |
| CN112000850A (en) | Method, device, system and equipment for data processing | |
| CN113448609B (en) | Container upgrading method, device, equipment and storage medium | |
| JP2017167675A (en) | Information processing system, information processing method, and server | |
| KR20190015817A (en) | Method, Apparatus and System for Monitoring Using Middleware | |
| CN114615263A (en) | Cluster online migration method, device, equipment and storage medium | |
| CN112463304A (en) | Rollback method and apparatus for container mirror image, computer device, and storage medium | |
| CN115905271B (en) | Virus library updating method and device and multi-engine detection system | |
| CN113687915B (en) | Container running method, device, equipment and storage medium | |
| CN111142921A (en) | Software upgrading method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |