CN112052067A - Virtualized container starting and information maintenance method, electronic device and storage medium - Google Patents
Virtualized container starting and information maintenance method, electronic device and storage medium Download PDFInfo
- Publication number
- CN112052067A CN112052067A CN202010727944.4A CN202010727944A CN112052067A CN 112052067 A CN112052067 A CN 112052067A CN 202010727944 A CN202010727944 A CN 202010727944A CN 112052067 A CN112052067 A CN 112052067A
- Authority
- CN
- China
- Prior art keywords
- container
- starting
- identifier
- dependent
- storage space
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 103
- 238000012423 maintenance Methods 0.000 title claims description 19
- 230000001419 dependent effect Effects 0.000 claims abstract description 213
- 238000013507 mapping Methods 0.000 claims description 32
- 230000004044 response Effects 0.000 claims description 16
- 238000004590 computer program Methods 0.000 claims description 11
- 230000002452 interceptive effect Effects 0.000 claims description 11
- 230000008569 process Effects 0.000 abstract description 31
- 238000013515 script Methods 0.000 abstract description 14
- 238000010586 diagram Methods 0.000 description 9
- 238000004891 communication Methods 0.000 description 7
- 230000000977 initiatory effect Effects 0.000 description 4
- 230000003993 interaction Effects 0.000 description 4
- 230000004913 activation Effects 0.000 description 3
- 238000013459 approach Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 239000002131 composite material Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000012858 packaging process Methods 0.000 description 1
- 230000037361 pathway Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 239000000523 sample Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45575—Starting, stopping, suspending or resuming virtual machine instances
-
- 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/45591—Monitoring or debugging support
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the invention provides a method for starting a virtualized container and maintaining information, electronic equipment and a storage medium. After the start tool acquires the identifier of the dependent container of any container where the start tool is located, or after the identifier of the dependent container of any container is inquired from the dependent container relation stored in the shared storage space through the call-back interface before starting, if the identifier of the dependent container is inquired from the shared storage space through the call-back interface before starting and is mapped to complete the start identifier, the start tool starts any container through executing the call-back interface. By the shared storage space shared by the container set to which any container belongs, the starting tool can realize the inquiry of the dependent container, the inquiry of the starting state of the dependent container and the writing of the starting state of the dependent container through a uniform interface, so that different scripts do not need to be packaged for the containers, the standardization of the starting process of the containers is realized, and the realization process of the sequential starting of the containers is simplified.
Description
Technical Field
The invention relates to the technical field of virtualized containers, in particular to a virtualized container starting and information maintaining method, electronic equipment and a storage medium.
Background
There are two ways to start up a virtualized container. The first mode is as follows: in Docker composite, a tool such as a script is used to encapsulate a start command of a container. However, since the script has no versatility, the script for packaging needs to be rewritten for each container, and the packaging process is complicated. The second approach is only applicable during initialization of the container. In the process of initializing the container, it is necessary to ensure that the former container can be initialized and started after the former container is initialized and started and then quit. However, in the actual service operation process, multiple containers are usually required to be operated simultaneously, so the second method is not suitable for controlling the starting process of the containers in the service operation process.
Therefore, in the prior art, the starting of the container needs to depend on the script packaged for each container, and the implementation process is complex due to different scripts packaged for each container.
Disclosure of Invention
Embodiments of the present invention provide a virtualized container starting and information maintaining method, an electronic device, and a storage medium, so as to solve a problem in the prior art that starting of a container needs to depend on a script packaged for each container, and an implementation process is complicated due to different scripts packaged for each container.
To solve the foregoing technical problem, in a first aspect, an embodiment of the present invention provides a method for starting a virtualized container, including:
a starting tool configured in any container acquires the identifier of the dependent container of any container from the configuration file of any container, or inquires the identifier of the dependent container of any container from the dependent container relation stored in the shared storage space through a call-back interface before starting according to the identifier of any container; wherein the dependent container is a container with a starting sequence before any container and a starting sequence adjacent to any container; the shared storage space is shared by a container set to which the any container belongs; the container set comprises at least two containers with starting sequences; the dependency container relationship records the identifier of the container in the container set and the corresponding starting sequence;
and inquiring whether the identifier of the dependent container is mapped to the start-up completion identifier or not through the callback interface before starting according to the identifier of the dependent container and the mapping relation between the start-up completion identifier written into the shared storage space by the container which completes starting and the identifier of the container which completes starting in the container set, sending a start command to any container through executing the callback interface until the identifier of the dependent container is inquired to map the start-up completion identifier, and otherwise, not sending the start command to any container.
Optionally, after the container to be activated is activated, the method further includes:
after the completion of the starting of any container is detected, writing a file in a preset format into a folder where any container is located in the shared storage space through a notification callback interface, and taking the file in the preset format as a completion starting identifier of any container mapping.
Optionally, the querying, by the pre-startup callback interface, whether the identifier of the dependent container is mapped to the completion startup identifier until the identifier of the dependent container is mapped to the completion startup identifier is queried, includes:
and inquiring whether the identifier of the dependent container is mapped to a starting identifier or not through the callback interface before starting every preset time interval until the identifier of the dependent container is inquired to be mapped to the starting identifier.
Optionally, before the start tool configured in the any container acquires the identifier of the dependent container of the any container from the configuration file of the any container, the method includes:
and generating the configuration file according to the identification of the dependent container which is configured when the any container is created and is depended by the any container.
In a second aspect, an embodiment of the present invention provides a method for maintaining virtualized container information, where the method is applied to a shared storage space, and includes:
acquiring a starting sequence corresponding to any container when each container in the container set is started, configured for any container in the container set through an interactive interface, and storing an identifier of any container and the starting sequence corresponding to any container into a dependent container relation in a shared storage space;
the starting sequence corresponding to any container is determined according to the container configured for each container and depended on for starting each container when each container in the container set is created; wherein the shared storage space is shared by a container set to which the any container belongs; the container set comprises at least two containers with starting sequences.
Optionally, the method further comprises:
receiving a first query request sent by a starting tool configured in any container through a call-back interface before starting; the first query request is used for requesting to query the identification of a dependent container of any container according to the identification of the any container;
querying an identification of a container which is started before the container from a dependent container relation stored in the shared storage space and has a starting sequence adjacent to the starting sequence of the container, and taking the identification of the queried container as the identification of the dependent container of the container;
and returning the identification of the dependent container of any container to the starting tool through the call-back interface before starting.
Optionally, the method further comprises:
receiving a second query request sent by a starting tool configured in any container through the pre-starting callback interface, wherein the second query request is used for requesting to query whether the identifier of the dependent container of any container is mapped to finish starting the identifier;
inquiring whether the identifier of the dependent container of any container is mapped to the completion starting identifier or not according to the mapping relation between the completion starting identifier written into the shared storage space by the container which completes the starting in the container set and the identifier of the container which completes the starting, if so, sending an inquiry response to the starting tool through the call-back interface before starting, and if not, not sending the inquiry response to the starting tool; the query response is used for indicating the query to the identification mapping completion starting identification of the dependent container.
Optionally, the method further comprises:
receiving a write-in instruction sent by a starting tool configured in any container through a notification callback interface; the write instruction is used for indicating that the start identifier is written into any container;
and writing a file in a preset format in a folder where any container is located in the shared storage space, wherein the file in the preset format is used as a completion starting identifier of any container mapping.
In a third aspect, an embodiment of the present invention provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the virtualized container starting method or the virtualized container information maintenance method described above when executing the program.
In a fourth aspect, an embodiment of the present invention provides a non-transitory readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps of the virtualized container starting method or the virtualized container information maintaining method described in any one of the above.
The embodiment of the invention provides a virtualized container starting and information maintaining method, electronic equipment and a storage medium. After the start tool acquires the identifier of the dependent container of any container where the start tool is located, or after the identifier of the dependent container of any container is inquired from the dependent container relation stored in the shared storage space through the call-back interface before starting, if the identifier of the dependent container is inquired from the shared storage space through the call-back interface before starting and is mapped to complete the start identifier, the start tool starts any container through executing the call-back interface. By the shared storage space shared by the container set to which any container belongs, the starting tool can realize the inquiry of the dependent container, the inquiry of the starting state of the dependent container and the writing of the starting state of the dependent container through a uniform interface, so that different scripts do not need to be packaged for the containers, the standardization of the starting process of the containers is realized, and the realization process of the sequential starting of the containers is simplified.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.
Fig. 1 is a schematic flowchart of a virtualized container starting method according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of an activation tool controlling the activation of a container according to another embodiment of the present invention;
fig. 3 is a flowchart illustrating a virtualized container information maintenance method according to another embodiment of the present invention;
FIG. 4 is a schematic flow chart of an implementation of ordered container startup according to another embodiment of the present invention;
FIG. 5 is a block diagram illustrating a virtualized container starting apparatus according to another embodiment of the present invention;
fig. 6 is a block diagram showing a configuration of a virtualized container information maintenance apparatus according to another embodiment of the present invention;
fig. 7 is a schematic physical structure diagram of an electronic device according to another embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. 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 invention.
In some scenarios, control over the start-up sequence of virtualized containers is required. To this end, the present application provides a virtualized container startup method that is performed by any startup tool that manages the startup of a virtualized container. Wherein, an actuating tool is arranged in each container and used for controlling the actuation of the container.
The virtual container starting method provided by the application can be applied to at least one of the following application scenarios:
scene 1: the start-up of a container needs to rely on the services provided by the last container. If the service provided by the last container is required to be relied on: the system comprises a Web Server and/or a database, wherein the Web Server must wait for the database to be available after the database is started.
Scene 2: the container needs to complete the initial configuration for the next container or service. If necessary, cluster information, node information, network service information and the like necessary for collecting the next container are preset in a configuration file, or the required configuration file or data file and the like are downloaded from a remote Git warehouse and a file system.
Scene 3: the container needs to send self-registration information of the Pod or service to the remote service, and after the registration is completed, other containers in the Pod or service can be started.
Fig. 1 is a schematic flow chart of a virtualized container starting method provided in this embodiment, and referring to fig. 1, the virtualized container starting method includes the following steps:
step 101: a starting tool configured in any container acquires the identifier of the dependent container of any container from the configuration file of any container, or inquires the identifier of the dependent container of any container from the dependent container relation stored in the shared storage space through a call-back interface before starting according to the identifier of any container; wherein the dependent container is a container with a starting sequence before any container and a starting sequence adjacent to any container; the shared storage space is shared by a container set to which the any container belongs; the container set comprises at least two containers with starting sequences; the dependency container relationship records the identifier of the container in the container set and the corresponding starting sequence;
step 102: and inquiring whether the identifier of the dependent container is mapped to the start-up completion identifier or not through the callback interface before starting according to the identifier of the dependent container and the mapping relation between the start-up completion identifier written into the shared storage space by the container which completes starting and the identifier of the container which completes starting in the container set, sending a start command to any container through executing the callback interface until the identifier of the dependent container is inquired to map the start-up completion identifier, and otherwise, not sending the start command to any container.
Fig. 2 is a schematic diagram illustrating the starting tool controlling the starting of the containers according to the embodiment, and referring to fig. 2, a starting tool is configured in each container in the container set, and the starting tool cyclically executes the above steps 101 and 102 to start the container in which the starting tool is located. Dependent containers of any container refer to containers that must have completed activation when any container is activated.
For an initiating tool configured in any container, the identification of the dependent container of any container is first determined in step 101. There are two acquisition pathways:
route 1: from the configuration file of any container. When the any container is created, the start sequence of the configuration is before the any container, and the start sequence is the identification of the container adjacent to the any container (i.e. the dependent container of the any container). And the starting tool configured in any container acquires the identification of the dependent container of any container from the configuration file of any container through a get command.
Route 2: the start tool obtains the identifier of the dependent container of any container by inquiring the dependency container relationship stored in the shared storage space through a callback interface before start provided externally according to the identifier of any container where the start tool is located (the identifier of any container can be written into the start tool when the start tool is configured into any container).
For the above approach 2, specifically, the start tool sends the identifier of any container and the first query instruction to the shared storage space through the pre-start callback interface, so that the shared storage space queries the dependency container identifier of any container from the stored dependency container relationship according to the identifier of any container, and returns the identifier of the dependency container of any container to the start tool through the pre-start callback interface. Wherein the first query request is for requesting a query for an identification of a dependent container of the any container based on the identification of the any container.
After the identification of the dependent container of any container is determined, whether the dependent container of any container is started is inquired through step 102, if yes, a starting command is sent to any container through the execution callback interface, so that the starting of any container is realized, otherwise, the starting command is not sent to any container, so that any container is in a state of waiting for starting.
It should be noted that, any container in the container set that completes starting stores, in the shared storage space, a mapping relationship between an identifier of the container that completes starting and a complete starting identifier. Therefore, each starting tool can inquire whether the dependent container of any container completes starting or not from the shared storage space through the mapping relation.
Specifically, in step 102, the start tool sends the identifier of the dependent container of any container and the second query request to the shared storage space through the pre-start callback interface, so that the shared storage space queries whether the dependent container of any container is mapped with the start identifier according to the identifier of the dependent container of any container, if so, it indicates that the dependent container of any container is started completely, otherwise, the dependent container of any container is not started completely. And the second query request is used for requesting to query whether the identifier of the dependent container of any container is mapped to the completion starting identifier.
In this embodiment, a start tool is configured for each container, the start tool queries a dependent container of the container through a shared storage space by using a pre-start callback interface, and the start state of the dependent container, and sends a start command to the container where the start tool is located by executing the callback interface, thereby completing the start of the container. The starting tool can inquire the related information of the dependent container from the shared storage space through the unified call-back interface before starting and the notification call-back interface which writes the start completion identifier after the container is started, and finish the control of starting by executing the interaction of the call-back interface and the container. Therefore, the container is started in a unified flow through the interaction between the starting tool and the shared storage volume and the interaction between the starting tool and the container where the starting tool is located. In the embodiment, the flow of container starting is standardized, and compared with the prior art, different scripts are not required to be packaged in different containers, and the container starting can be realized only by the starting tool installed in the container through interaction between the starting tool and the shared storage space. The standardization of the container starting process is beneficial to simplifying the implementation process of container sequential starting.
The embodiment provides a virtualized container starting method, and a starting tool is configured for each container. After the start tool acquires the identifier of the dependent container of any container where the start tool is located, or after the identifier of the dependent container of any container is inquired from the dependent container relation stored in the shared storage space through the call-back interface before starting, if the identifier of the dependent container is inquired from the shared storage space through the call-back interface before starting and is mapped to complete the start identifier, the start tool starts any container through executing the call-back interface. By the shared storage space shared by the container set to which any container belongs, the starting tool can realize the inquiry of the dependent container, the inquiry of the starting state of the dependent container and the writing of the starting state of the dependent container through a uniform interface, so that different scripts do not need to be packaged for the containers, the standardization of the starting process of the containers is realized, and the realization process of the sequential starting of the containers is simplified.
Further, on the basis of the above embodiment, the method further includes:
after the completion of the starting of any container is detected, writing a file in a preset format into a folder where any container is located in the shared storage space through a notification callback interface, and taking the file in the preset format as a completion starting identifier of any container mapping.
The starting tool configured in any container can judge whether the starting of any container is finished or not through the parameter change before the container is started and after the container is started.
After detecting that any container is started completely, the starting tool calls a notification callback interface to write a completion starting identifier mapped with the identifier of any container in the shared storage volume. It should be noted that, in this embodiment, the start completion flag refers to a file in a preset format. For example, the file of the preset format is finish. For example, after the container with the container name "container name 1" is started, the start tool configured in the container sends a notification callback interface to the shared storage space, the file of finish.ok is stored under the file of the container, and the following files exist in the file directory where the stored file of finish.ok is located: "/service name 1/container name 1/finish.ok".
Specifically, after detecting that any container is started completely, the starting tool sends a write-in instruction to the shared storage space through the notification callback interface, so as to store a file in a preset format in a folder of any container in the shared storage space according to the write-in instruction, and the file in the preset format is used as a start-up completion identifier of any container. Wherein the writing instruction includes an identifier of the any container.
In this embodiment, after the container is started, the start tool of the container stores a file in a preset format in a folder of the container in the shared storage space by notifying the callback interface, and the file in the preset format is used as a start completion identifier. The method for writing the start completion identifier is simple, the identifier of the container after the start is completed is realized, and a judgment basis for judging whether the container is started completely is provided.
Further, on the basis of the foregoing embodiments, the querying, by using the pre-startup callback interface, whether the identifier of the dependent container is mapped to the completion startup identifier until the identifier of the dependent container is mapped to the completion startup identifier includes:
and inquiring whether the identifier of the dependent container is mapped to a starting identifier or not through the callback interface before starting every preset time interval until the identifier of the dependent container is inquired to be mapped to the starting identifier.
In the process of querying whether the identifier of the dependent container of any container is mapped to complete the start identifier by the start tool, if the identifier of the dependent container is not queried for the first time to map to complete the start identifier, the query process is continuously repeated at preset time intervals until the identifier of the dependent container is queried to map to complete the start identifier. The preset time period may be preset, for example, 5 seconds.
According to the embodiment, repeated query of the starting identifier is completed by mapping the identifier of the dependent container, so that the timeliness of the query result can be ensured, any container is started after the starting identifier of the dependent container is queried, and the control efficiency of starting the containers in sequence is improved.
Further, on the basis of the foregoing embodiments, before the initiating tool configured in any container acquires the identifier of the dependent container of any container from the configuration file of any container, the method includes:
and generating the configuration file according to the identification of the dependent container which is configured when the any container is created and is depended by the any container.
The process of any container creation configures the dependent container on which any container is started, and the identification of the dependent container on which any container is started and configured at the time of any container creation is written in the configuration file. The start-up tool for any container may determine the identity of the dependent container for that container by accessing the configuration file.
In this embodiment, the start tool determines the identifier of the dependent container of any container through the configuration file in any container, so as to query the start state of the dependent container according to the identifier of the dependent container of any container, thereby implementing a control process for starting the containers according to the start sequence.
Based on the above control of the Container starting process by the starting tool, referring to fig. 2, in the virtualized Container starting method provided in this embodiment, (1) the service containers having a starting dependency relationship with each other are grouped into a set (e.g., Container1, Container2 … … Container), where each Container is mounted and shares the same shared storage volume (i.e., shared storage space). (2) A unified container command initiation tool is provided that provides three callback interfaces:
the pre-starting callback interface is a callback interface which depends before starting, and the interface returns a list of other service containers which depend on the starting of the current container and is used for prejudging and waiting for the completion of the starting of the dependent container.
The execution callback interface is a callback interface for executing the start command, and the interface returns the start command of the current container for starting the container.
The notification callback interface is a notification callback interface for the completion of the starting of the current container to be started, and is used for registering and registering the current notification callback interface to the specified directory and file when the container is started.
For the shared storage space, fig. 2 also provides (3) a set of operation and maintenance WEB interfaces, and the background displays the start dependency relationship between the containers by reading the directories and files of the shared storage volume. Specifically, fig. 3 is a schematic flowchart of a method for maintaining virtualized container information provided in this embodiment, where the method for maintaining virtualized container information is applied to a shared storage space, and referring to fig. 3, the method for maintaining virtualized container information includes:
step 301: acquiring a starting sequence corresponding to any container when each container in the container set is started, configured for any container in the container set through an interactive interface, and storing an identifier of any container and the starting sequence corresponding to any container into a dependent container relation in a shared storage space;
the starting sequence corresponding to any container is determined according to the container configured for each container and depended on for starting each container when each container in the container set is created; wherein the shared storage space is shared by a container set to which the any container belongs; the container set comprises at least two containers with starting sequences.
The interactive interface refers to a human-computer interactive interface (e.g., a WEB interface), and a user can write a starting sequence of the containers through the interactive interface, and the starting sequence is stored in the dependency container relationship by the shared storage space. It will be appreciated that the user follows the container-dependent write initiation sequence for the container configuration when the container is created. If the start-up sequence written by the user is different from the start-up sequence determined according to the dependent containers configured for each container, an error may occur in the start-up process, resulting in termination of the sequential start-up.
In the embodiment, the dependency container relationship in the shared storage space is stored and edited through the interactive interface, a way for a user to uniformly manage the shared storage space is provided, and the management of the dependency container relationship in the shared storage space is realized.
The embodiment provides a virtualized container information maintenance method, and a starting tool is configured for each container. After the start tool acquires the identifier of the dependent container of any container where the start tool is located, or after the identifier of the dependent container of any container is inquired from the dependent container relation stored in the shared storage space through the call-back interface before starting, if the identifier of the dependent container is inquired from the shared storage space through the call-back interface before starting and is mapped to complete the start identifier, the start tool starts any container through executing the call-back interface. By the shared storage space shared by the container set to which any container belongs, the starting tool can realize the inquiry of the dependent container, the inquiry of the starting state of the dependent container and the writing of the starting state of the dependent container through a uniform interface, so that different scripts do not need to be packaged for the containers, the standardization of the starting process of the containers is realized, and the realization process of the sequential starting of the containers is simplified.
Further, on the basis of the above embodiment, the method further includes:
receiving a first query request sent by a starting tool configured in any container through a call-back interface before starting; the first query request is used for requesting to query the identification of a dependent container of any container according to the identification of the any container;
querying an identification of a container which is started before the container from a dependent container relation stored in the shared storage space and has a starting sequence adjacent to the starting sequence of the container, and taking the identification of the queried container as the identification of the dependent container of the container;
and returning the identification of the dependent container of any container to the starting tool through the call-back interface before starting.
In the process of realizing the sequential starting of the containers, the starting tool interacts with the shared storage space through the callback interface before starting, so as to realize the identification of the dependent containers and the query of the starting state of the dependent containers. After receiving the first query request, the shared storage space queries the identifier of the dependent container of any container from the dependent container relationship according to the identifier of the dependent container, and returns the queried identifier of the dependent container to the starting tool through the call-back interface before starting, so that the starting tool queries the starting state of the dependent container according to the identifier of the dependent container, and then starts the dependent container after the dependent container is started, thereby realizing the control of starting the containers according to the starting sequence.
Further, on the basis of the above embodiments, the method further includes:
receiving a second query request sent by a starting tool configured in any container through the pre-starting callback interface, wherein the second query request is used for requesting to query whether the identifier of the dependent container of any container is mapped to finish starting the identifier;
inquiring whether the identifier of the dependent container of any container is mapped to the completion starting identifier or not according to the mapping relation between the completion starting identifier written into the shared storage space by the container which completes the starting in the container set and the identifier of the container which completes the starting, if so, sending an inquiry response to the starting tool through the call-back interface before starting, and if not, not sending the inquiry response to the starting tool; the query response is used for indicating the query to the identification mapping completion starting identification of the dependent container.
And after determining the identification of the dependent container of any container, the starting tool of any container sends a second query request to the shared storage space according to the identification of the dependent container. After receiving the second query request, the shared storage space queries whether the dependent container is started or not by storing the start-up completion identifier for each started container in advance according to the identifier of the dependent container. And after the shared storage space determines that the identifier of the dependent container of any container maps the completion starting identifier, returning a query response to the starting tool, so that the starting tool of any container performs starting control on any container after receiving the query response.
It should be noted that, when there are multiple dependent containers in any container, the any container is started only after receiving the query response corresponding to each dependent container.
In this embodiment, the start tool of any container controls start of any container after receiving a query response corresponding to each dependent container of any container through query of the callback interface to the start state of the dependent container before starting, so that sequential start of the containers is realized.
Further, on the basis of the above embodiments, the method further includes:
receiving a write-in instruction sent by a starting tool configured in any container through a notification callback interface; the write instruction is used for indicating that the start identifier is written into any container;
and writing a file in a preset format in a folder where any container is located in the shared storage space, wherein the file in the preset format is used as a completion starting identifier of any container mapping.
The starting tool also provides a notification callback interface, and after the starting tool detects that any container is started completely, a starting completion identifier is written into any container through the notification callback interface, so that the starting state of any container can be inquired through the shared storage volume after any container is started completely, and therefore when any container is used as a dependent container of other containers, the correct starting state updated in time can be inquired, and sequential starting of subsequent containers is guaranteed.
In the embodiment, the starting state of any container is updated in time after the container is started through the notification callback interface, so that the shared storage space can provide the container state updated in time, delay of the starting process due to untimely updating of the starting state is avoided, and the starting efficiency of the container starting in sequence is ensured.
In general, the virtualized container starting and information maintenance method comprises the following information:
when the container is started and called back, the start tool needs to write an empty file finish.ok into the specified directory of the shared storage volume, and the corresponding directory path is as follows: ok, service name/container name/finish.ok; and updates its own container information (state information of the container) in the container.meta file of the root directory of the shared storage volume, such as including: container and state of dependent containers, flag file path, etc. Here, the storage of the markup file and the container information is used for determining whether the container is started up or not, and for visually displaying and configuring the interface.
When the container is reset before being started, the starting tool needs to read whether a finish.ok file exists in a specified container directory under specified service according to a dependent service container list returned by the interface, if yes, returning true, and executing a starting command; otherwise, return to false and continue to wait.
Fig. 4 is a schematic diagram of a flow for implementing ordered container starting provided in this embodiment, and referring to fig. 4, the flow includes the following processes:
1. a user presets a container set through a visual interface and configures a starting dependency list of each container.
2. The visual interface interacts with the shared storage area. And analyzing preset information of a user to obtain a starting dependency list of each container in the set, and then storing the information into a container.
3. Before the container is started, the starting tool obtains the current container identifier, such as a name, by reading the environment variable or the specified configuration file in the container.
4. And (4) starting a tool to a container.meta file of the shared storage area to inquire a dependent container list of the current container, if the current container is started without depending on other containers, directly entering the step 6, and if not, continuing the following steps.
5. And the starting tool searches whether the completion flag files finish.
6. If the completion flag files of the dependent containers are all present, the start command of the container is invoked to start the container.
7. And after the container is started, the starting tool is informed. The notification mode comprises
a. The container provides a probe service, and the starting tool detects whether the service is started and completed;
b. and after the container is started, calling back a notification interface of the starting tool and the like.
8. After receiving the instruction of completing the container starting, the starting tool writes a starting completion flag file of the container, such as "/service name 1/container name 1/finish.ok", into the shared storage area, and updates self information of the container, such as the state of the container and the container depended on, a flag file path and the like, in a container.
In summary, the method provided in this embodiment standardizes the container start process through a unified start tool and a start command of the package container, and on the other hand, realizes the judgment waiting and notification recording of the container start dependency relationship through a shared storage communication manner.
It is understood that the methods provided by the above embodiments are applicable to both Docker complex and K8S, and are not even limited to Docker, as long as the container provides a launch command callback interface implementation and a shared storage mount.
Compared with the manner of implementing sequential starting of containers in the existing Docker complex, on one hand, the method provided in this embodiment standardizes the starting process of the containers through a unified starting tool (specifically, the starting tool in the embodiments of the present application exposes three interface callbacks to the outside, and can perform unified callback processing on dependency judgment and waiting before starting of the containers, starting command execution, starting completion notification and recording). On the other hand, containers which depend on each other share the same storage volume, and the starting dependency relationship is managed in a mode of storing a volume directory file and combining WEB display, so that the method is simpler and more intuitive and is easy to maintain.
Compared with the existing Init container scheme of kubernets, firstly, the method provided by the embodiment does not require the container to be started and finished to quit the service. Namely, after the container finishes the starting completion notification, the continuous online operation can be entered and the service can be provided. Secondly, the method provided by the embodiment can be directly used in the Pod to realize the starting sequence of the multiple containers in the Pod, and can also realize the control of the starting sequence of the containers in different services and different pods, so that the control granularity is finer. Finally, the method provided by the embodiment does not need to rely on an initial-container (init-container) concept adopted in Kubernets, is small in limitation, and can be applied in a cross-platform mode.
Fig. 5 is a block diagram of a virtualized container starting apparatus applied to a starting tool according to this embodiment, and referring to fig. 5, the virtualized container starting apparatus includes an obtaining module 501 and a starting module 502, wherein,
an obtaining module 501, configured to obtain an identifier of a dependent container of any container from a configuration file of the any container, or query, according to the identifier of the any container, the identifier of the dependent container of the any container from a dependent container relationship stored in a shared storage space through a callback interface before starting; wherein the dependent container is a container with a starting sequence before any container and a starting sequence adjacent to any container; the shared storage space is shared by a container set to which the any container belongs; the container set comprises at least two containers with starting sequences; the dependency container relationship records the identifier of the container in the container set and the corresponding starting sequence;
a starting module 502, configured to query, through the pre-start callback interface, whether the identifier of the dependent container is mapped to the start-up completion identifier in the shared storage space according to the identifier of the dependent container and a mapping relationship between the start-up completion identifier written by the container that completes start-up in the container set and the identifier of the container that completes start-up, until the identifier of the dependent container is queried to map to the start-up completion identifier, send a start command to any container through the execution callback interface, and otherwise, not send the start command to any container.
The virtualized container starting apparatus provided in this embodiment is suitable for the virtualized container starting method provided in each of the above embodiments, and details are not described here again.
The embodiment of the invention provides a virtualized container starting and information maintaining device, and a starting tool is configured for each container. After the start tool acquires the identifier of the dependent container of any container where the start tool is located, or after the identifier of the dependent container of any container is inquired from the dependent container relation stored in the shared storage space through the call-back interface before starting, if the identifier of the dependent container is inquired from the shared storage space through the call-back interface before starting and is mapped to complete the start identifier, the start tool starts any container through executing the call-back interface. By the shared storage space shared by the container set to which any container belongs, the starting tool can realize the inquiry of the dependent container, the inquiry of the starting state of the dependent container and the writing of the starting state of the dependent container through a uniform interface, so that different scripts do not need to be packaged for the containers, the standardization of the starting process of the containers is realized, and the realization process of the sequential starting of the containers is simplified.
Optionally, the method further comprises:
after the completion of the starting of any container is detected, writing a file in a preset format into a folder where any container is located in the shared storage space through a notification callback interface, and taking the file in the preset format as a completion starting identifier of any container mapping.
Optionally, the querying, by the pre-startup callback interface, whether the identifier of the dependent container is mapped to the completion startup identifier until the identifier of the dependent container is mapped to the completion startup identifier is queried, includes:
and inquiring whether the identifier of the dependent container is mapped to a starting identifier or not through the callback interface before starting every preset time interval until the identifier of the dependent container is inquired to be mapped to the starting identifier.
Optionally, before the start tool configured in the any container acquires the identifier of the dependent container of the any container from the configuration file of the any container, the method includes:
and generating the configuration file according to the identification of the dependent container which is configured when the any container is created and is depended by the any container.
Fig. 6 is a block diagram of a structure of a virtualized container information maintenance apparatus provided in this embodiment, where the virtualized container information maintenance apparatus is applied to a shared storage space, and referring to fig. 6, the virtualized container information maintenance apparatus includes a storage module 601, where,
a storage module 601, configured to obtain a starting sequence corresponding to any container configured for any container in a container set through an interactive interface when each container in the container set is started, and store an identifier of the any container and the starting sequence corresponding to the any container in a dependent container relationship in a shared storage space;
the starting sequence corresponding to any container is determined according to the container configured for each container and depended on for starting each container when each container in the container set is created; wherein the shared storage space is shared by a container set to which the any container belongs; the container set comprises at least two containers with starting sequences.
The virtualized container information maintenance method provided in this embodiment is suitable for the virtualized container information maintenance methods provided in the foregoing embodiments, and details are not described here.
The embodiment of the invention provides a virtualized container starting and information maintaining device, and a starting tool is configured for each container. After the start tool acquires the identifier of the dependent container of any container where the start tool is located, or after the identifier of the dependent container of any container is inquired from the dependent container relation stored in the shared storage space through the call-back interface before starting, if the identifier of the dependent container is inquired from the shared storage space through the call-back interface before starting and is mapped to complete the start identifier, the start tool starts any container through executing the call-back interface. By the shared storage space shared by the container set to which any container belongs, the starting tool can realize the inquiry of the dependent container, the inquiry of the starting state of the dependent container and the writing of the starting state of the dependent container through a uniform interface, so that different scripts do not need to be packaged for the containers, the standardization of the starting process of the containers is realized, and the realization process of the sequential starting of the containers is simplified.
Optionally, the method further comprises:
receiving a first query request sent by a starting tool configured in any container through a call-back interface before starting; the first query request is used for requesting to query the identification of a dependent container of any container according to the identification of the any container;
querying an identification of a container which is started before the container from a dependent container relation stored in the shared storage space and has a starting sequence adjacent to the starting sequence of the container, and taking the identification of the queried container as the identification of the dependent container of the container;
and returning the identification of the dependent container of any container to the starting tool through the call-back interface before starting.
Optionally, the method further comprises:
receiving a second query request sent by a starting tool configured in any container through the pre-starting callback interface, wherein the second query request is used for requesting to query whether the identifier of the dependent container of any container is mapped to finish starting the identifier;
inquiring whether the identifier of the dependent container of any container is mapped to the completion starting identifier or not according to the mapping relation between the completion starting identifier written into the shared storage space by the container which completes the starting in the container set and the identifier of the container which completes the starting, if so, sending an inquiry response to the starting tool through the call-back interface before starting, and if not, not sending the inquiry response to the starting tool; the query response is used for indicating the query to the identification mapping completion starting identification of the dependent container.
Optionally, the method further comprises:
receiving a write-in instruction sent by a starting tool configured in any container through a notification callback interface; the write instruction is used for indicating that the start identifier is written into any container;
and writing a file in a preset format in a folder where any container is located in the shared storage space, wherein the file in the preset format is used as a completion starting identifier of any container mapping.
Fig. 7 illustrates a physical structure diagram of an electronic device, and as shown in fig. 7, the electronic device may include: a processor (processor)701, a communication Interface (Communications Interface)702, a memory (memory)703 and a communication bus 704, wherein the processor 701, the communication Interface 702 and the memory 703 complete communication with each other through the communication bus 704. The processor 701 may call logic instructions in the memory 703 to perform the following method:
a starting tool configured in any container acquires the identifier of the dependent container of any container from the configuration file of any container, or inquires the identifier of the dependent container of any container from the dependent container relation stored in the shared storage space through a call-back interface before starting according to the identifier of any container; wherein the dependent container is a container with a starting sequence before any container and a starting sequence adjacent to any container; the shared storage space is shared by a container set to which the any container belongs; the container set comprises at least two containers with starting sequences; the dependency container relationship records the identifier of the container in the container set and the corresponding starting sequence; according to the identifier of the dependent container and the mapping relation between the identifier of the container which is written into the shared storage space by the container which finishes the start and the identifier of the container which finishes the start, inquiring whether the identifier of the dependent container finishes the mapping of the identifier of the dependent container through the callback interface before the start until the identifier of the dependent container finishes the mapping of the identifier of the dependent container, and sending a start command to any one container through the callback interface, otherwise, not sending the start command to any one container;
or acquiring a starting sequence corresponding to any container when each container in the container set is started, configured for any container in the container set through an interactive interface, and storing the identifier of any container and the starting sequence corresponding to any container into a dependent container relation in a shared storage space; the starting sequence corresponding to any container is determined according to the container configured for each container and depended on for starting each container when each container in the container set is created; wherein the shared storage space is shared by a container set to which the any container belongs; the container set comprises at least two containers with starting sequences.
In addition, the logic instructions in the memory 703 can be implemented in the form of software functional units and stored in a computer readable storage medium when the software functional units are sold or used as independent products. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
Further, embodiments of the present invention disclose a computer program, the computer program comprising a computer program stored on a non-transitory readable storage medium, the computer program comprising program instructions, which when executed by a computer, the computer is capable of performing the methods provided by the above-mentioned method embodiments, for example, comprising:
a starting tool configured in any container acquires the identifier of the dependent container of any container from the configuration file of any container, or inquires the identifier of the dependent container of any container from the dependent container relation stored in the shared storage space through a call-back interface before starting according to the identifier of any container; wherein the dependent container is a container with a starting sequence before any container and a starting sequence adjacent to any container; the shared storage space is shared by a container set to which the any container belongs; the container set comprises at least two containers with starting sequences; the dependency container relationship records the identifier of the container in the container set and the corresponding starting sequence; according to the identifier of the dependent container and the mapping relation between the identifier of the container which is written into the shared storage space by the container which finishes the start and the identifier of the container which finishes the start, inquiring whether the identifier of the dependent container finishes the mapping of the identifier of the dependent container through the callback interface before the start until the identifier of the dependent container finishes the mapping of the identifier of the dependent container, and sending a start command to any one container through the callback interface, otherwise, not sending the start command to any one container;
or acquiring a starting sequence corresponding to any container when each container in the container set is started, configured for any container in the container set through an interactive interface, and storing the identifier of any container and the starting sequence corresponding to any container into a dependent container relation in a shared storage space; the starting sequence corresponding to any container is determined according to the container configured for each container and depended on for starting each container when each container in the container set is created; wherein the shared storage space is shared by a container set to which the any container belongs; the container set comprises at least two containers with starting sequences.
In another aspect, an embodiment of the present invention further provides a non-transitory readable storage medium, on which a computer program is stored, where the computer program is implemented to perform the transmission method provided in the foregoing embodiments when executed by a processor, for example, the method includes:
a starting tool configured in any container acquires the identifier of the dependent container of any container from the configuration file of any container, or inquires the identifier of the dependent container of any container from the dependent container relation stored in the shared storage space through a call-back interface before starting according to the identifier of any container; wherein the dependent container is a container with a starting sequence before any container and a starting sequence adjacent to any container; the shared storage space is shared by a container set to which the any container belongs; the container set comprises at least two containers with starting sequences; the dependency container relationship records the identifier of the container in the container set and the corresponding starting sequence; according to the identifier of the dependent container and the mapping relation between the identifier of the container which is written into the shared storage space by the container which finishes the start and the identifier of the container which finishes the start, inquiring whether the identifier of the dependent container finishes the mapping of the identifier of the dependent container through the callback interface before the start until the identifier of the dependent container finishes the mapping of the identifier of the dependent container, and sending a start command to any one container through the callback interface, otherwise, not sending the start command to any one container;
or acquiring a starting sequence corresponding to any container when each container in the container set is started, configured for any container in the container set through an interactive interface, and storing the identifier of any container and the starting sequence corresponding to any container into a dependent container relation in a shared storage space; the starting sequence corresponding to any container is determined according to the container configured for each container and depended on for starting each container when each container in the container set is created; wherein the shared storage space is shared by a container set to which the any container belongs; the container set comprises at least two containers with starting sequences.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding, the above technical solutions may be embodied in the form of a software product, which may be stored in a readable storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the embodiments or some parts of the embodiments.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (10)
1. A virtualized container starting method is applied to a starting tool and comprises the following steps:
a starting tool configured in any container acquires the identifier of the dependent container of any container from the configuration file of any container, or inquires the identifier of the dependent container of any container from the dependent container relation stored in the shared storage space through a call-back interface before starting according to the identifier of any container; wherein the dependent container is a container with a starting sequence before any container and a starting sequence adjacent to any container; the shared storage space is shared by a container set to which the any container belongs; the container set comprises at least two containers with starting sequences; the dependency container relationship records the identifier of the container in the container set and the corresponding starting sequence;
and inquiring whether the identifier of the dependent container is mapped to the start-up completion identifier or not through the callback interface before starting according to the identifier of the dependent container and the mapping relation between the start-up completion identifier written into the shared storage space by the container which completes starting and the identifier of the container which completes starting in the container set, sending a start command to any container through executing the callback interface until the identifier of the dependent container is inquired to map the start-up completion identifier, and otherwise, not sending the start command to any container.
2. The virtualized container startup method according to claim 1, further comprising:
after the completion of the starting of any container is detected, writing a file in a preset format into a folder where any container is located in the shared storage space through a notification callback interface, and taking the file in the preset format as a completion starting identifier of any container mapping.
3. The virtualization container starting method according to claim 1, wherein the querying, through the pre-start callback interface, whether the identifier of the dependent container is mapped to the start identifier until the identifier of the dependent container is queried to be mapped to the start identifier of the dependent container, includes:
and inquiring whether the identifier of the dependent container is mapped to a starting identifier or not through the callback interface before starting every preset time interval until the identifier of the dependent container is inquired to be mapped to the starting identifier.
4. The virtualization container starting method according to claim 1, before the starting tool configured in the any container obtains the identifier of the dependent container of the any container from the configuration file of the any container, comprising:
and generating the configuration file according to the identification of the dependent container which is configured when the any container is created and is depended by the any container.
5. A virtualized container information maintenance method is applied to a shared storage space, and comprises the following steps:
acquiring a starting sequence corresponding to any container when each container in the container set is started, configured for any container in the container set through an interactive interface, and storing an identifier of any container and the starting sequence corresponding to any container into a dependent container relation in a shared storage space;
the starting sequence corresponding to any container is determined according to the container configured for each container and depended on for starting each container when each container in the container set is created; wherein the shared storage space is shared by a container set to which the any container belongs; the container set comprises at least two containers with starting sequences.
6. The virtualized container information maintenance method according to claim 5, further comprising:
receiving a first query request sent by a starting tool configured in any container through a call-back interface before starting; the first query request is used for requesting to query the identification of a dependent container of any container according to the identification of the any container;
querying an identification of a container which is started before the container from a dependent container relation stored in the shared storage space and has a starting sequence adjacent to the starting sequence of the container, and taking the identification of the queried container as the identification of the dependent container of the container;
and returning the identification of the dependent container of any container to the starting tool through the call-back interface before starting.
7. The virtualized container information maintenance method according to claim 6, further comprising:
receiving a second query request sent by a starting tool configured in any container through the pre-starting callback interface, wherein the second query request is used for requesting to query whether the identifier of the dependent container of any container is mapped to finish starting the identifier;
inquiring whether the identifier of the dependent container of any container is mapped to the completion starting identifier or not according to the mapping relation between the completion starting identifier written into the shared storage space by the container which completes the starting in the container set and the identifier of the container which completes the starting, if so, sending an inquiry response to the starting tool through the call-back interface before starting, and if not, not sending the inquiry response to the starting tool; the query response is used for indicating the query to the identification mapping completion starting identification of the dependent container.
8. The virtualized container information maintenance method according to claim 6, further comprising:
receiving a write-in instruction sent by a starting tool configured in any container through a notification callback interface; the write instruction is used for indicating that the start identifier is written into any container;
and writing a file in a preset format in a folder where any container is located in the shared storage space, wherein the file in the preset format is used as a completion starting identifier of any container mapping.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the steps of the virtualized container startup method according to any one of claims 1 to 4 when executing the program or implements the steps of the virtualized container information maintenance method according to any one of claims 5 to 8 when executing the program.
10. A non-transitory readable storage medium having stored thereon a computer program, which when executed by a processor, performs the steps of the virtualized container startup method according to any one of claims 1 to 4 or the steps of the virtualized container information maintenance method according to any one of claims 5 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010727944.4A CN112052067A (en) | 2020-07-23 | 2020-07-23 | Virtualized container starting and information maintenance method, electronic device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010727944.4A CN112052067A (en) | 2020-07-23 | 2020-07-23 | Virtualized container starting and information maintenance method, electronic device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112052067A true CN112052067A (en) | 2020-12-08 |
Family
ID=73601211
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010727944.4A Pending CN112052067A (en) | 2020-07-23 | 2020-07-23 | Virtualized container starting and information maintenance method, electronic device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112052067A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114237626A (en) * | 2021-12-22 | 2022-03-25 | 四川新网银行股份有限公司 | Method, system and equipment for non-invasive dynamic editing of JVM (Java virtual machine) parameters |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107368339A (en) * | 2017-07-25 | 2017-11-21 | 上海携程商务有限公司 | Container entrance program operating method, system, equipment and storage medium |
| US20180246729A1 (en) * | 2017-02-24 | 2018-08-30 | International Business Machines Corporation | Techniques for managing software container dependencies |
| US20190065096A1 (en) * | 2017-08-25 | 2019-02-28 | Vmware, Inc. | Distributed file storage system supporting accesses from multiple container hosts |
| CN110134496A (en) * | 2019-05-22 | 2019-08-16 | 中国联合网络通信集团有限公司 | Container monitors method, apparatus, equipment and computer readable storage medium |
-
2020
- 2020-07-23 CN CN202010727944.4A patent/CN112052067A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180246729A1 (en) * | 2017-02-24 | 2018-08-30 | International Business Machines Corporation | Techniques for managing software container dependencies |
| CN107368339A (en) * | 2017-07-25 | 2017-11-21 | 上海携程商务有限公司 | Container entrance program operating method, system, equipment and storage medium |
| US20190065096A1 (en) * | 2017-08-25 | 2019-02-28 | Vmware, Inc. | Distributed file storage system supporting accesses from multiple container hosts |
| CN110134496A (en) * | 2019-05-22 | 2019-08-16 | 中国联合网络通信集团有限公司 | Container monitors method, apparatus, equipment and computer readable storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114237626A (en) * | 2021-12-22 | 2022-03-25 | 四川新网银行股份有限公司 | Method, system and equipment for non-invasive dynamic editing of JVM (Java virtual machine) parameters |
| CN114237626B (en) * | 2021-12-22 | 2024-06-21 | 四川新网银行股份有限公司 | Method, system and equipment for non-invasively dynamically editing JVM parameters |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109542529B (en) | Function name-based point burying method and device, computer equipment and storage medium | |
| CN109634718B (en) | Method and system for creating mirror image by cloud platform | |
| CN112199197B (en) | Server management method and system | |
| CN105335187B (en) | Application processing method and device | |
| CN112445579B (en) | Zero terminal data processing system and file copying method and device thereof | |
| US9009737B2 (en) | Apparatus and method of terminal for providing file system function | |
| CN113296805A (en) | Method and device for realizing hot upgrade of auxiliary container | |
| CN111641676A (en) | Method and device for constructing third-party cloud monitoring service | |
| CN111582824B (en) | Cloud resource synchronization method, device, equipment and storage medium | |
| CN115168061A (en) | Calculation storage separation method and system, electronic equipment and storage medium | |
| CN109992956A (en) | The processing method and relevant apparatus of the security strategy of container | |
| CN110798462B (en) | Smart home system and equipment access method | |
| CN111124540B (en) | Dynamic configuration method of service control system and service request forwarding method | |
| CN116339756A (en) | Application program mounting method, device, equipment and storage medium | |
| CN112052067A (en) | Virtualized container starting and information maintenance method, electronic device and storage medium | |
| CN110688201A (en) | Log management method and related equipment | |
| CN113254045A (en) | Software initialization method, system and computer readable storage medium | |
| CN109495298B (en) | Method and device for managing nodes in OpenStack system | |
| CN113568603B (en) | Component object creating and interface method calling method, terminal and storage device | |
| CN114721784B (en) | Application running method and device, electronic equipment and readable medium | |
| CN115562590A (en) | Method, system, equipment and storage medium for using cloud hard disk by cloud host | |
| CN113419760A (en) | Method, apparatus, computer device and medium for opening/saving project file | |
| CN112130900A (en) | User information management method, system, equipment and medium for BMC | |
| CN114090083A (en) | Visual component configuration method, device, equipment and storage medium | |
| CN111858234A (en) | Task execution method, device, equipment and medium |
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 |