CN111324385A - Starting method of application module, container, control device and readable storage medium - Google Patents

Starting method of application module, container, control device and readable storage medium Download PDF

Info

Publication number
CN111324385A
CN111324385A CN201811518762.5A CN201811518762A CN111324385A CN 111324385 A CN111324385 A CN 111324385A CN 201811518762 A CN201811518762 A CN 201811518762A CN 111324385 A CN111324385 A CN 111324385A
Authority
CN
China
Prior art keywords
container
application module
starting
indication information
application
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
Application number
CN201811518762.5A
Other languages
Chinese (zh)
Inventor
吴兵
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to CN201811518762.5A priority Critical patent/CN111324385A/en
Priority to PCT/CN2019/118594 priority patent/WO2020119377A1/en
Publication of CN111324385A publication Critical patent/CN111324385A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • G06F9/44505Configuring for program initiating, e.g. using registry, configuration files
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/45575Starting, stopping, suspending or resuming virtual machine instances

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

The embodiment of the invention relates to the technical field of communication, and discloses a starting method of an application module, a container, control equipment and a readable storage medium. In the invention, the starting method of the application module is applied to the container and comprises the following steps: receiving indication information sent by a control center, wherein the indication information is determined by the control center according to a preset starting condition; judging whether the application module in the container meets the starting condition or not according to the indication information; and determining whether to start the application module in the container according to the judgment result. In the implementation, the container judges whether the application module in the container meets the preset starting condition or not according to the indication information sent by the control center, compared with the prior manual intervention and high requirements on the familiarity requirements of implementers on the application, the operation is more convenient, and the difficulty of operation and maintenance is reduced.

Description

Starting method of application module, container, control device and readable storage medium
Technical Field
The embodiment of the invention relates to the technical field of communication, in particular to a starting method, a container, control equipment and a readable storage medium of an application module.
Background
Because the container can remove cross-service dependence and conflict, the productivity of developers is improved, the operation and maintenance complexity is reduced to a certain extent, the utilization rate of resources is improved, the total investment of a system is reduced, and the container technology is rapidly developed. However, when the container is used, the problems of complex application system, complex installation and deployment, frequent development and update and the like are encountered. With the continuous development and improvement of container technology, the value of a container cloud platform is gradually discovered, and the container cloud platform can substantially better solve the problems. Application containerization is a key point of attention for building a container cloud platform.
However, the inventors found that at least the following problems exist in the related art: when the traditional application system uses a container cloud platform, containerization transformation is needed, and a problem is encountered in the containerization transformation. Therefore, in order to reduce the workload of containerization modification of the conventional application, a method for controlling the start sequence of the application modules of the application more easily and conveniently is needed.
It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
The embodiment of the invention aims to provide a starting method, a container, a control device and a readable storage medium of an application module, so that the operation of an implementer is more convenient, and the difficulty of operation and maintenance is reduced.
In order to solve the above technical problem, an embodiment of the present invention provides a method for starting an application module, which is applied to a container, and includes the following steps: receiving indication information sent by a control center, wherein the container is one of N containers corresponding to the application in the container cloud platform, and the indication information is determined by the control center according to a preset starting condition; judging whether the application module in the container meets the starting condition or not according to the indication information; and determining whether to start the application module in the container according to the judgment result, wherein N is a positive integer.
The embodiment of the invention also provides a starting method of the application module, which is applied to the control center and comprises the following steps: determining indication information according to preset starting conditions; sending indication information to the container; the system comprises a control center, a container cloud platform and a control center, wherein the container is one of N containers corresponding to an application in the container cloud platform, and the container receives indication information sent by the control center; judging whether the application module in the container meets the starting condition or not according to the indication information; and determining whether to start the application module in the container according to the judgment result, wherein N is a positive integer.
Embodiments of the present invention also provide a container comprising: at least one processor; and a memory communicatively coupled to the at least one processor; and a communication component in communication connection with the control device, the communication component receiving and transmitting data under control of the processor; the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the method for starting the application module according to the embodiment.
An embodiment of the present invention also provides a control apparatus including: at least one processor; and a memory communicatively coupled to the at least one processor; and a communication component in communicative connection with the container, the communication component receiving and transmitting data under control of the processor; the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the method for starting the application module according to the embodiment.
The embodiment of the invention also provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to realize the starting method of the application module mentioned in the above embodiment.
The embodiment of the invention also provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to realize the starting method of the application module mentioned in the above embodiment.
Compared with the prior art, the method and the device have the advantages that the control center controls the starting process of the application modules in each container according to the starting conditions of the application modules in each container, so that the application modules can be started according to the preset starting sequence, and the problem of dependence of the application modules in the containers in the traditional application containerization process is solved. Furthermore, the implementation personnel can change the dependency relationship of the application modules in the container by modifying the starting conditions in the control center, thereby reducing the workload of containerization transformation of the application. The control center controls the starting sequence of the application modules in each container, the original manual control is changed into automatic control, the requirement on the familiarity of implementers to the application is lowered, the starting sequence of the application modules of the application can be controlled more simply and conveniently, and the difficulty of operation and maintenance is lowered.
Drawings
One or more embodiments are illustrated by way of example in the accompanying drawings, which correspond to the figures in which like reference numerals refer to similar elements and which are not to scale unless otherwise specified.
Fig. 1 is a flowchart of a starting method of an application module of a first embodiment of the present invention;
FIG. 2 is a flow chart of a method for launching an application module according to a second embodiment of the present invention;
FIG. 3 is a flowchart of a method for launching an application module according to a third embodiment of the present invention;
FIG. 4 is a flowchart of a method for launching an application module according to a fourth embodiment of the present invention;
FIG. 5 is a schematic diagram of the location of a control center of a fourth embodiment of the present invention in a vessel cloud platform configuration;
FIG. 6 is a schematic diagram of the interaction of the system of the fourth embodiment of the present invention with the outside world;
fig. 7 is a schematic flow chart of the control logic of the SDDD entity of the fourth embodiment of the present invention;
fig. 8 is an overall flowchart illustrating a starting process of an application module according to a fourth embodiment of the present invention;
FIG. 9 is a schematic diagram of a process for implementing the start-up sequence of the application module in the container according to the fourth embodiment of the present invention;
FIG. 10 is a schematic structural view of a container according to a fifth embodiment of the present invention;
fig. 11 is a schematic configuration diagram of a control apparatus of a sixth embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. However, it will be appreciated by those of ordinary skill in the art that numerous technical details are set forth in order to provide a better understanding of the present application in various embodiments of the present invention. However, the technical solution claimed in the present application can be implemented without these technical details and various changes and modifications based on the following embodiments.
The first embodiment of the invention relates to a starting method of an application module, which is applied to a container. The starting method of the application module is shown in fig. 1, and comprises the following steps:
step 101: and receiving indication information sent by the control center.
Specifically, the instruction information is determined by the control center according to the preset starting condition. The start-up conditions include at least conditions determined according to a preset start-up order of the application modules in the container. The control center is loaded with a configuration file storing the starting sequence of the application modules in the containers, and determines the starting conditions of the application modules in each container according to the starting sequence of the application modules in each container set in the configuration file.
It should be noted that, as will be understood by those skilled in the art, in practical applications, other conditions may be included in the start-up conditions, for example, the configuration of the container needs to satisfy the conditions, and in order to highlight the innovative part of the present application, conditions that are not so closely related to solving the technical problem proposed by the present application are not listed in the present embodiment, but this does not indicate that other conditions are not included in the start-up conditions.
For example, the container corresponding to the application a includes a container a, a container b, and a container c, and the start sequence of the application modules in each container configured in the configuration file is as follows: starting an application module in the container a; after the application module in the container a is started, starting the application module in the container b; and after the application module in the container b is started, starting the application module in the container c. The control module determines that the starting condition of the container a indicates that the application module in the container a is independent of other containers, the starting condition of the container b indicates that the application module in the container b is dependent on the application module in the container a, and the starting condition of the container c indicates that the application module in the container c is dependent on the application module in the container b.
In a specific implementation, the indication information may be a control instruction determined by the control center according to the start condition, or may be the start condition and state information of other containers, or may be the state information of a container that is dependent on an application module in the container determined by the control center according to the start condition.
It should be noted that the control center may return the instruction information after the container sends the query instruction information, where the query instruction is used to instruct the control center to return the instruction information, and the control center may also actively send the instruction information to the container, and this embodiment does not limit the specific condition for the control center to send the instruction information.
Step 102: and judging whether the application module in the container meets the starting condition or not according to the indication information.
Hereinafter, a method of judging the container based on the instruction information in different cases will be described as an example.
Case 1: the indication information is a control instruction determined by the control center according to the starting condition. And the control center sends a control instruction to the container after determining that the application module in the container meets the starting condition according to the starting condition. The container receives a control instruction and judges whether the control instruction is a starting instruction, wherein the starting instruction is used for indicating that an application module in the container meets a starting condition; if the judgment result is yes, the application module in the container is determined to be in accordance with the starting condition, and if the judgment result is not, the application module in the container is determined to be in accordance with the starting condition.
It is worth mentioning that, under the condition, the control center judges whether the application module in the container meets the starting condition, so that the workload of the container is reduced.
Case 2: the indication information is determined by the control center based on the start-up conditions and the status information of the other containers. The other containers are containers other than the container in the N containers, and the state information of the other containers is used for indicating whether the application modules in the other containers are started or not. In a specific implementation, the control center takes the starting condition and the state information of other containers as indication information. The container judges whether the application module in the container depends on other containers or not according to the starting condition; if the application module in the container is determined to depend on other containers, determining a judgment result according to the state information of the container on which the application module in the container depends; and if the application modules in the container are determined not to depend on other containers, determining that the application modules in the container meet the starting conditions according to the judgment result. And under the condition that the application modules in the container depend on other containers, if the container determines that the state information of the dependent container indicates that the application modules in the dependent container are started, determining that the application modules in the container meet the starting conditions as a judgment result.
Case 3: the indication information is the state information of the container which is depended by the application module in the container, wherein the state information of the depended container is determined by the control center according to the starting condition, and the state information of the depended container is used for indicating whether the application module in the depended container is started or not. And if the container determines that the state information of the container depended by the application module in the container indicates that the application module depended by the application module in the container is started, determining that the judgment result is that the application module in the container meets the starting condition.
It is worth mentioning that the container automatically judges whether the application module in the container meets the starting condition according to the data returned by the control center, so that the pressure of the control center is reduced.
Step 103: and determining whether to start the application module in the container according to the judgment result.
Specifically, if it is determined that the application modules in the container meet the start condition as a result of the determination, it indicates that the application modules of the container that should be started before the application modules of the container have already been started according to the preset start sequence, and therefore, the application modules in the container are started, otherwise, it indicates that the application modules of the container that should be started before the application modules of the container have not yet been started according to the preset start sequence, and the container needs to wait for further instructions, or re-request the indication information after a period of time.
The following description will exemplify the starting method of the application module in combination with the actual scenario.
For example, for the above-mentioned application a, after the container b in the application a is started and before the application module in the container b is started, the query instruction is sent to the control center every 10 ms. At the first moment, the container b sends a query instruction to the control center, and the control center determines that the application module in the current container a is not started, so that the determination indication information indicates that the container b does not meet the starting condition. After the container b receives the indication information sent by the control center, the container b does not start the internal application module because the indication information indicates that the starting condition is not met. And after the distance from the container b to the first moment is 10ms, the container b sends the query instruction to the control center again, the control center determines that the application module in the current container a is started, and the indication information indicates that the container b meets the starting condition. After the container b receives the indication information sent by the control center, the application modules in the container b are started in turn at present according to the preset starting sequence as the indication information indicates that the starting conditions are met, and the application modules in the container b are started by the container.
According to the above, when the application modules in the container meet the starting conditions, it is described that the application modules in the container are started in turn according to the preset starting sequence, so that the container can start the application modules in the container according to the preset starting sequence.
In specific implementation, after the application module in the container is started, the container sends a state change instruction to the control center. The state change instruction is used for indicating the success or failure of starting the application module in the container. And after receiving the state change instruction, the control center changes the state information of the container according to the state change instruction. For example, if the container determines that the application module in the container has not finished starting within the starting time, it is determined that the state change instruction indicates a failed start. Wherein the starting time can be set according to the requirement.
The above description is only for illustrative purposes and does not limit the technical aspects of the present invention.
Compared with the prior art, in the starting method of the application modules provided in the embodiment, the control center controls the starting process of the application modules in each container according to the starting conditions of the application modules in each container, so that each application module can be started according to the preset starting sequence, and the problem of dependence of the application modules in the containers in the traditional application containerization process is solved. Furthermore, the implementation personnel can change the dependency relationship of the application modules in the container by modifying the starting conditions in the control center, thereby reducing the workload of containerization transformation of the application. The control center controls the starting sequence of the application modules in each container, the original manual control is changed into automatic control, the requirement on the familiarity of implementers to the application is lowered, the starting sequence of the application modules of the application can be controlled more simply and conveniently, and the difficulty of operation and maintenance is lowered.
The second embodiment of the present invention relates to a method for starting an application module, and the embodiment is further improved on the basis of the first embodiment, and the specific improvements are as follows: before step 101 and after step 103, other relevant steps are added.
Specifically, as shown in fig. 2, the present embodiment includes steps 201 to 207, wherein steps 202 to 204 are substantially the same as steps 101 to 103 in the first embodiment, and are not repeated herein. The following mainly introduces the differences:
step 201: and sending a query instruction to the control center.
Specifically, the query instruction is used to instruct the control center to return instruction information. In one specific implementation, the container periodically sends the query instruction to the control center when the application module in the container is not started until the indication information indicates that the application module in the container meets the starting condition.
Step 202: and receiving indication information sent by the control center.
Step 203: and judging whether the application module in the container meets the starting condition or not according to the indication information.
Step 204: and determining whether to start the application module in the container according to the judgment result.
Step 205: and receiving a restart signal sent by the control center.
Specifically, after step 204 is executed, there may be a case where the container is failed to be started, or a case where the control center has not received the state change instruction after the application module in the container has been started, in which case, the control center sends a restart signal, so that the container can determine whether to be restarted according to the restart signal.
Step 206: and judging whether the application module in the container is started successfully or not.
Specifically, if it is determined that the application modules in the container are successfully started, no response is made to the restart signal, and if it is determined that the application modules in the container are failed to be started, step 207 is executed.
Step 207: and restarting the application module in the container.
Specifically, the container re-executes the program modules within the container, and the application modules within the container have been started.
It is worth mentioning that after the last start of the container fails, the application modules in the container can be restarted according to the restart signal, so that the overall stability of the application subjected to containerization processing is improved.
The above description is only for illustrative purposes and does not limit the technical aspects of the present invention.
Compared with the prior art, in the starting method of the application modules provided in the embodiment, the control center controls the starting process of the application modules in each container according to the starting conditions of the application modules in each container, so that each application module can be started according to the preset starting sequence, and the problem of dependence of the application modules in the containers in the traditional application containerization process is solved. Furthermore, the implementation personnel can change the dependency relationship of the application modules in the container by modifying the starting conditions in the control center, thereby reducing the workload of containerization transformation of the application. The control center controls the starting sequence of the application modules in each container, the original manual control is changed into automatic control, the requirement on the familiarity of implementers to the application is lowered, the starting sequence of the application modules of the application can be controlled more simply and conveniently, and the difficulty of operation and maintenance is lowered. In addition, under the condition that the container is failed to start, the application modules in the container can be restarted after the restart signal is received, and the overall stability of the application containerization is improved.
The third embodiment of the invention relates to a starting method of an application module, which is applied to a control center. The starting method of the application module is shown in fig. 3, and comprises the following steps:
step 301: and determining the indication information according to the preset starting condition.
Specifically, the start-up conditions include at least conditions determined according to a preset start-up order of the application modules in the container.
The following illustrates a process in which the control center determines the indication information according to the start condition.
In a first implementation, the indication information is a control instruction determined according to the start condition. The control center judges whether the application module in the container depends on other containers or not according to the starting condition; if so, determining whether the control instruction is a starting instruction according to the state information of the container depended by the application module in the container. The container is one of N containers corresponding to the application in the container cloud platform, and the other containers are containers except the containers in the N containers. Specifically, if the control center determines that the state information of the container on which the application module in the container depends indicates that the application module in the container on which the application module in the container depends is started, the control center determines that the control instruction is a start instruction. For example, the container corresponding to the application B includes a container a, a container B, and a container c, and the start sequence of the application modules in each container configured in the configuration file is as follows: starting an application module in the container a and starting an application module in the container b; and after the application modules in the container a and the container b are started, starting the application module in the container c. That is, the application module in the container a and the application module in the container b are independent of other containers, and the application module in the container c is dependent on the container a and the container b, that is, the container c can be started after the container a and the container b are started. At the first moment, the control center determines that the containers a and b are independent of other containers and sends starting instructions to the containers a and b. And after receiving the starting instruction, the container a and the container b run internal program modules and start the respective internal application modules. After determining that the container a and the container b complete the starting of the application modules in the containers a and b respectively, the control center determines that the container c meets the starting condition, and sends a starting instruction to the container c, so that the starting of all the application modules of the application A is completed.
In a specific implementation, when determining that the application module in the container, on which the application module in the container depends, is not started, the control center may continue to detect the state of the application module in the container, on which the application module in the container depends, until the state of the application module in the container, on which the application module in the container depends, is started, and then send a control instruction to the container.
It should be noted that, in order to avoid that the control center always detects the state of the application module in the container that the application module in the container depends on, and gets into the dead loop, the detection time may be set, and when the time for the control center to detect the state of the application module in the container that the application module in the container depends on exceeds the detection time, it is determined that the application module in the container does not meet the start condition, and the start fails.
In a second implementation, the indication information is determined based on the start-up conditions and the status information of the other containers. The other containers are containers except the container in the N containers, and the state information of the other containers is used for indicating whether the application modules in the other containers are started or not. In a specific implementation, the control center takes the starting condition and the state information of other containers as indication information.
In a third implementation manner, the indication information is state information of a container, which is determined according to the starting condition and on which the application module in the container depends. The state information of the container depended on by the application module in the container is determined by the control center according to the starting condition, and the state information of the container depended on by the application module in the container is used for indicating whether the application module in the container depended on by the application module in the container is started or not. Specifically, the control center determines a container on which an application module in the container depends according to a starting condition; and taking the state information of the container depended by the application module in the container as indication information.
It should be noted that, as will be understood by those skilled in the art, in practical applications, the specific content of the indication information may be determined as needed, for example, the starting time of the container is added to the indication information, so that the container or the control center determines whether the container is started successfully according to the starting time, and the specific content of the indication information is not limited in this embodiment.
Step 302: and sending indication information to the container.
Specifically, the container receives indication information sent by the control center; judging whether the application module in the container meets the starting condition or not according to the indication information; and determining whether to start the application module in the container according to the judgment result. For the container to determine whether the application module in the container meets the start condition according to the indication information, reference may be made to the related description of the first embodiment and the second embodiment, which is not described herein again.
The following illustrates an example of a manner of triggering the control center to transmit the instruction information.
In a specific implementation, before sending the indication information to the container, the control center receives an inquiry instruction sent by the container, and the inquiry instruction is used for indicating the control center to return the indication information.
In another specific implementation, the control center intermittently transmits the indication information. For example, when the state information of the container indicates that the container is not activated, the control center transmits the indication information every 1 s.
In another specific implementation, the control center sends the indication information after determining that the application module in the container satisfies the starting condition.
It should be noted that, as can be understood by those skilled in the art, in practical application, the trigger condition for the control center to send the indication information may be set as needed, for example, the embodiment does not limit the trigger condition for the control center to send the indication information.
It is worth mentioning that the control center actively sends the indication information to the container after determining that the application module in the container meets the starting condition, so as to avoid the situation that the control container cannot obtain the indication information due to the packet loss of the query instruction of the container, and further the application module in the container fails to start.
Compared with the prior art, in the starting method of the application modules provided in the embodiment, the control center controls the starting process of the application modules in each container according to the starting conditions of the application modules in each container, so that each application module can be started according to the preset starting sequence, and the problem of dependence of the application modules in the containers in the traditional application containerization process is solved. Furthermore, the implementation personnel can change the dependency relationship of the application modules in the container by modifying the starting conditions in the control center, thereby reducing the workload of containerization transformation of the application. The control center controls the starting sequence of the application modules in each container, the original manual control is changed into automatic control, the requirement on the familiarity of implementers to the application is lowered, the starting sequence of the application modules of the application can be controlled more simply and conveniently, and the difficulty of operation and maintenance is lowered.
The fourth embodiment of the present invention relates to a method for starting an application module, and the embodiment is further improved based on the third embodiment, and the specific improvements are as follows: after step 302, other related steps are added.
Specifically, as shown in fig. 4, the present embodiment includes steps 401 to 404, where steps 401 and 402 are substantially the same as steps 301 and 302 in the third embodiment, and are not repeated here. The following mainly introduces the differences:
steps 401 to 402 are performed.
Step 403: and receiving a state change instruction sent by the container, and updating the state information of the container according to the state change instruction.
Specifically, the state change instruction is used for indicating the success or failure of starting the application module in the container;
in the specific implementation, before updating the state information of the container according to the state change instruction, the control center needs to detect the state of the application module in the container, determine the first detection result, determine whether the state change instruction is correct according to the first detection result, update the state information of the container if it is determined that the first detection result indicates that the state change instruction is correct, and not update the state information of the container if it is determined that the first detection result indicates that the state change instruction is wrong. For example, the state change instruction indicates that the application module in the container is successfully started, and if the first detection result obtained by the detection of the control center indicates that the application module in the container is not started, the state change instruction is incorrect, and the control center does not change the state information of the container. On the contrary, if the first detection result obtained by the detection of the control center indicates that the application module in the container is started, the state change instruction is correct, and the control center changes the state information of the container.
It is worth mentioning that the control center verifies the state change instruction before changing the state information of the containers according to the state change instruction, so that the accuracy of the state information of the containers in the control center is ensured, and further, the containers can be started according to a correct sequence.
It should be noted that, as can be understood by those skilled in the art, the control center may detect the state of the application module in the container after sending the indication information to the container, and determine a second detection result; and updating the state information of the container according to the second detection result. For example, if the control center determines that the second detection result indicates that the application module in the container is started, the control center changes the state information of the container to the state information of the application module in the container.
In specific implementation, the control center detects the state of the application module in the container, and the specific process of determining the second detection result is as follows: and the control center detects the state of the application module in the container discontinuously, and if the state of the application module is still not started after the preset starting time is exceeded, the second detection result is determined to be that the application module in the container fails to start.
It is worth mentioning that the control center automatically detects the state of the application module in the container, so as to avoid the situation that the state information of the container is not updated timely due to the loss of the data packet carrying the state change instruction.
It should be noted that, as can be understood by those skilled in the art, in practical applications, the starting time of different application modules is different, and therefore, the starting detection interval time and the number of times in the SDDD entity can be configured according to practical situations.
The method for the control center to detect the state of the application module in the container includes but is not limited to the following 4 methods:
the method comprises the following steps: and (6) judging the port. The control center uses Telnet to connect the port of the target container, if the connection is successful, the port is started, the application module in the container is started successfully, otherwise, the connection fails.
The method 2 comprises the following steps: the Application Programming Interface (API) of rest. And the control center acquires a result according to the access type and the path configured by the SDDD entity, compares the result with the configured success value, if the returned result contains the configured success returned value, the API is available, and if the application module in the container is successfully started, otherwise, the API fails.
The method 3 comprises the following steps: uniform Resource Locator (URL) determination. The principle of the method is basically similar to that of the method 2, and whether the URL is available or not is judged according to the returned result, so that whether the application module in the container is started successfully or not is determined.
The method 4 comprises the following steps: and detecting a custom script. When the method is used, the detection script needs to be put into the container in advance, and whether the application module in the container is successfully started or not is judged by returning a success result and the like according to the path configured in the SDDD entity.
Step 404: and determining that the updated state information of the container indicates that the application module in the container fails to start, and sending a restart signal to the container.
Specifically, after determining that the application modules in the container are failed to start, the control center sends a restart signal to the container, and the container receives the restart signal and restarts the application modules in the container.
It is worth mentioning that after the last start of the container fails, the application modules in the container can be restarted according to the restart signal, so that the overall stability of the application subjected to containerization processing is improved.
Compared with the prior art, in the starting method of the application modules provided in the embodiment, the control center controls the starting process of the application modules in each container according to the starting conditions of the application modules in each container, so that each application module can be started according to the preset starting sequence, and the problem of dependence of the application modules in the containers in the traditional application containerization process is solved. Furthermore, the implementation personnel can change the dependency relationship of the application modules in the container by modifying the starting conditions in the control center, thereby reducing the workload of containerization transformation of the application. The control center controls the starting sequence of the application modules in each container, the original manual control is changed into automatic control, the requirement on the familiarity of implementers to the application is lowered, the starting sequence of the application modules of the application can be controlled more simply and conveniently, and the difficulty of operation and maintenance is lowered. In addition, the control center verifies the state change instruction before changing the state information of the containers according to the state change instruction, so that the accuracy of the state information of the containers in the control center is ensured, and further, the containers can be started in a correct sequence. After the container is failed to be started last time, the application modules in the container can be restarted according to the restarting signal, and the overall stability of the application subjected to containerization treatment is improved.
The following describes an overall process of application containerization, taking a container cloud platform based on an open source container engine (docker) as an example.
First, the entire application containerization system includes three major parts, a container application, a container cloud platform, and an infrastructure. The system comprises a container cloud platform, a Service registration Center, a resource monitoring management module, a mirror image management module, an application release module, a tenant management module and a Control Center, wherein a plurality Of containers are arranged in The container application, and functional blocks such as The Service registration Center, The resource monitoring management module, The persistent integration module, The data volume management module, The Service management module, The log management module, The mirror image management module, The application release module and The tenant management module are arranged in The container cloud platform. After the application is containerized, the application is released on a container cloud platform, at the moment, preset starting conditions are loaded to a control center, and the control on the starting sequence of the application modules can be realized in the starting process of the container. An application arrangement and a container engine are also deployed on the container cloud platform, so that a user can conveniently perform service arrangement of the application. The Infrastructure may be physical machines, virtual machines, and Infrastructure As A Service (IAAS). Fig. 6 shows a schematic diagram of interaction between the system and the outside, and as can be seen from fig. 6, when a user uses the system to containerize an application, the user logs in an interface first, enters a container cloud platform, and executes the following operations in the container cloud platform:
the method comprises the following steps of firstly, determining a file (dockerfile) and a dependent file of an engine of an open source container of each container. The mirror image management module of the container cloud platform can perform mirror image construction according to the dockerfile and the dependent file. When the mirror image management module makes the mirror image of the container of the application, the agent program which is communicated with the control center is packaged into the starting process, so that the agent program can exchange information with the control center at the first time when the container is started.
And secondly, arranging the container by arranging service, and defining a System Deployment Definition Descriptor (SDDD) entity.
Specifically, the SDDD entity is the aforementioned configuration file. The SDDD entity may be another markup language (yaml) file. The SDDD entity supports entities such as a database, a file, a Representational State transfer (rest) interface and the like, and is mainly used for defining the starting sequence, the detection condition and the like of application modules in each container.
In a specific implementation, defining the SDDD entity includes the following operations: allocating a starting sequence of application modules in the container; the start-up detection condition of the application module within the blending container is set, for example, to: connecting a port of the container by using a remote terminal protocol (Telnet), and if the connection is successful, indicating that the application module in the container is successfully started; deploying a start-up dependency of an application module within a container; fault tolerance mechanisms, such as deployment of detection times and detection times, for application modules within the container are deployed to prevent trapping in a constantly detected endless loop situation. For example, the detection time is set to be 2s, and if the application module in the container still does not meet the starting condition after the detection is continued for 2s, it is determined that the application module fails to start.
It should be noted that, in this embodiment, the starting condition is loaded to the control center in a manner that the SDDD entity bears the starting condition, and in practical application, the starting condition may be loaded to the control center in other manners.
In a specific implementation, a schematic control logic flow diagram of the SDDD entity is shown in fig. 7, and includes the following steps:
step 601: the start-up conditions are read.
Step 602: and judging whether the detection time is exceeded.
Specifically, if the determination is not yes, step 603 is executed, otherwise, step 605 is executed. Wherein, the detection time can be set according to the requirement.
Step 603: and judging whether the application module in the container meets the starting condition or not.
If yes, go to step 604, otherwise, go to step 602.
Step 604: the application module is started.
Step 605: a startup failure is determined.
And thirdly, service deployment and application release, wherein the arranged services and applications are released, so that each container is in an operating state.
After the above operations are completed, the application is already released, and the application modules in the containers are sequentially started according to the configured starting sequence. Fig. 8 shows an overall flowchart of the starting process of the application module, which includes the following steps:
step 701: the user defines the SDDD entity.
Step 702: the control center loads the SDDD entity.
Specifically, the information related to the defined starting sequence of the application modules in each container is loaded into the control center, so that the control center can determine the starting condition of each application module according to the preset starting sequence, and control each container to start the application module according to the preset starting sequence according to the starting condition of the application modules in each container.
Step 703: the container of the application is started.
Specifically, a Process Identification (PID) of the container is set to 1 so that the container can be immediately started when the user enters. Because the agent program of the control center is encapsulated into the starting process, the agent program is started in the container starting process.
Step 704: the control center is started.
Specifically, the control center starts fault-tolerant judgment according to the information in the SDDD entity, determines a method for detecting the state of the application modules in the container, and sequentially starts programs of the application modules according to the starting conditions in the SDDD entity.
Step 705: the application module is started.
Specifically, a schematic diagram of the process of implementing the starting sequence of the application modules in the container is shown in fig. 9, and in fig. 9, ①, ②, ③ and ④ represent the sequence of each step in the starting process of the application modules in the container.
① container start-up procedure before the application module starts, the start-up of the container needs to be completed.
② during the start-up of the container, the agent in the container is started.
③ the agent program communicates with the control center to get the instruction information the agent program in the container is connected with the control center through the rest interface to send the query instruction to get the instruction information.
④, the container determines whether to start the application module according to the indication information, if the indication information indicates that the application module in the container meets the start condition, the application module is started, if not, the application module continues to wait until the indication information indicating that the application module in the container meets the start condition is received or a start failure signal is received.
And after receiving the query instruction sent by the agent program in the container, the control center according to the information in the SDDD entity. And if the application module in the container corresponding to the agent program is not dependent, returning indication information indicating that the application module in the container meets the starting condition. If the application modules in the container have dependency relationship, determining whether the application modules on which the application modules in the container depend are started, and if the application modules in the container are determined to be started, returning indication information indicating that the application modules in the container meet the starting conditions; otherwise, returning indication information that the application module in the container is not in accordance with the starting condition, or repeatedly detecting until the re-detection result is that the dependent application module is started or exceeds the preset detection time. And when the detection time is exceeded, returning indication information indicating that the application modules in the container are not in accordance with the starting conditions. Optionally, when the startup fails, the failure condition is recorded and stored in the database.
Preferably, when the application modules of the containers are sequentially started according to the starting sequence, the specific starting condition of the application modules is recorded, and the result is returned to the user interface. And the user interface displays each state of the container and the state of the application module according to the acquired result.
The steps of the above methods are divided for clarity, and the implementation may be combined into one step or split some steps, and the steps are divided into multiple steps, so long as the same logical relationship is included, which are all within the protection scope of the present patent; it is within the scope of the patent to add insignificant modifications to the algorithms or processes or to introduce insignificant design changes to the core design without changing the algorithms or processes.
A fifth embodiment of the present invention relates to a container, as shown in fig. 10, including: at least one processor 801; and a memory 802 communicatively coupled to the at least one processor 801; and a communication component 803 communicatively coupled to the control device, the communication component 803 receiving and transmitting data under control of the processor 801; the memory 802 stores instructions executable by the at least one processor 801, and the instructions are executed by the at least one processor 801, so that the at least one processor 801 can execute the method for starting the application module according to the above embodiment.
A sixth embodiment of the present invention is directed to a control apparatus, as shown in fig. 11, including: at least one processor 901; and, memory 902 communicatively connected to at least one processor 901; and a communication component 903 communicatively coupled to the container, the communication component 903 receiving and transmitting data under the control of the processor 901; the memory 902 stores instructions executable by the at least one processor 901, and the instructions are executed by the at least one processor 901, so that the at least one processor 901 can execute the method for starting the application module according to the above embodiments.
In the fifth embodiment and the sixth embodiment, one or more processors and memories are exemplified by one processor in fig. 10 and 11. The processor and the memory may be connected by a bus or other means, and fig. 10 and 11 illustrate the connection by a bus. The memory, which is a non-volatile computer-readable storage medium, may be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. The processor executes various functional applications and data processing of the device by running the nonvolatile software programs, instructions and modules stored in the memory, that is, the starting method of the application modules is realized.
The memory may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store a list of options, etc. Further, the memory may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some embodiments, the memory optionally includes memory located remotely from the processor, and these remote memories may be connected to the external device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
One or more modules are stored in the memory and, when executed by the one or more processors, perform the method for launching an application module in any of the method embodiments described above.
The product can execute the method provided by the embodiment of the application, has corresponding functional modules and beneficial effects of the execution method, and can refer to the method provided by the embodiment of the application without detailed technical details in the embodiment.
A seventh embodiment of the present invention relates to a computer-readable storage medium storing a computer program. The computer program, when executed by a processor, implements the method for launching the application module mentioned in the first and second embodiments.
An eighth embodiment of the present invention relates to a computer-readable storage medium storing a computer program. The computer program, when executed by a processor, implements the method for launching the application module mentioned in the third and fourth embodiments.
That is, as can be understood by those skilled in the art, all or part of the steps in the method for implementing the embodiments described above may be implemented by a program instructing related hardware, where the program is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the method described in the embodiments of the present application. 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.
It will be understood by those of ordinary skill in the art that the foregoing embodiments are specific examples for carrying out the invention, and that various changes in form and details may be made therein without departing from the spirit and scope of the invention in practice.

Claims (22)

1. A starting method of an application module is applied to a container, and comprises the following steps:
receiving indication information sent by a control center, wherein the container is one of N containers corresponding to an application in a container cloud platform, the indication information is determined by the control center according to a preset starting condition, and N is a positive integer;
judging whether the application module in the container meets the starting condition or not according to the indication information;
and determining whether to start the application module in the container or not according to the judgment result.
2. The method for starting an application module according to claim 1, wherein the starting conditions include at least conditions determined according to a preset starting order of the application modules in the container.
3. The method for starting the application module according to claim 1, wherein the indication information is a control instruction determined by the control center according to the starting condition; alternatively, the first and second electrodes may be,
the indication information is determined by the control center according to the starting condition and the state information of other containers; the other containers are containers other than the container in the N containers, and the state information of the other containers is used for indicating whether application modules in the other containers are started or not; alternatively, the first and second electrodes may be,
the indication information is state information of a container which is depended by the application module in the container, wherein the state information of the depended container is determined by the control center according to the starting condition, and the state information of the depended container is used for indicating whether the application module in the depended container is started or not.
4. The method for starting an application module according to claim 3, wherein if the indication information is a control instruction determined by the control center according to a starting condition, the determining whether the application module in the container meets the starting condition according to the indication information includes: judging whether the control instruction is a starting instruction or not, wherein the starting instruction is used for indicating that an application module in the container meets the starting condition; if yes, determining that the judgment result is that the application module in the container meets the starting condition;
if the indication information is the starting condition and the state information of other containers, the determining whether the application module in the container meets the starting condition according to the indication information includes: judging whether the application module in the container depends on other containers or not according to the starting condition; if so, determining the judgment result according to the state information of the container on which the application module in the container depends; if not, determining that the judgment result is that the application module in the container meets the starting condition;
if the indication information is the state information of the container on which the application module in the container depends, the determining whether the application module in the container meets the starting condition according to the indication information includes: and if the state information of the dependent container is determined to indicate that the application module in the dependent container is started, determining that the judgment result is that the application module in the container meets the starting condition.
5. The method for starting an application module according to claim 4, wherein the determining the determination result according to the state information of the container on which the application module in the container depends specifically includes:
and if the state information of the dependent container is determined to indicate that the application module in the dependent container is started, determining that the judgment result is that the application module in the container meets the starting condition.
6. The method for starting an application module according to any one of claims 1 to 5, wherein before the receiving the indication information sent by the control center, the method for starting an application module further comprises:
sending a query instruction to the control center; the query instruction is used for instructing the control center to return the indication information.
7. The method for starting an application module according to any one of claims 1 to 5, wherein after determining whether to start the application module in the container according to the determination result, the method for starting an application module further comprises:
and sending a state change instruction to the control center, wherein the state change instruction is used for indicating that the application modules in the container are started successfully or unsuccessfully.
8. The method for starting an application module according to any one of claims 1 to 5, wherein after determining whether to start the application module in the container according to the determination result, the method for starting an application module further comprises:
receiving a restarting signal sent by the control center;
judging whether the application module in the container is started successfully or not;
and if not, restarting the application module in the container.
9. A starting method of an application module is applied to a control center, and comprises the following steps:
determining indication information according to preset starting conditions;
sending indication information to the container; the container is one of N containers corresponding to the application in the container cloud platform, and the container receives indication information sent by the control center; judging whether the application module in the container meets the starting condition or not according to the indication information; and determining whether to start the application module in the container or not according to the judgment result, wherein N is a positive integer.
10. The method for starting an application module according to claim 9, wherein the starting conditions include at least conditions determined according to a preset starting order of the application modules in the container.
11. The method for starting an application module according to claim 9, wherein the indication information is a control command determined according to the starting condition; alternatively, the first and second electrodes may be,
the indication information is determined according to the starting condition and state information of other containers, wherein the other containers are containers other than the container in the N containers, and the state information of the other containers is used for indicating whether application modules in the other containers are started; alternatively, the first and second electrodes may be,
the indication information is state information of a container which is depended by the application module in the container, wherein the state information of the depended container is determined by the control center according to the starting condition, and the state information of the depended container is used for indicating whether the application module in the depended container is started or not.
12. The method for starting an application module according to claim 11, wherein if the indication information is the control instruction, the determining the indication information according to a preset starting condition specifically includes: judging whether the application module in the container depends on other containers or not according to the starting condition; if so, determining whether the control instruction is a starting instruction according to the state information of the container on which the application module in the container depends; if not, determining the control instruction as the starting instruction; wherein the starting instruction is used for indicating that the application module in the container meets the starting condition;
if the indication information is the starting condition and the state information of other containers, determining the indication information according to a preset starting condition specifically includes: taking the starting condition and the state information of the container as the indication information;
if the indication information is the state information of the container, which is depended by the application module in the container, determining the indication information according to a preset starting condition, which specifically includes: determining a container on which an application module in the container depends according to the starting condition; and using the state information of the dependent container as the indication information.
13. The method for starting an application module according to claim 12, wherein the determining whether the control instruction is a start instruction according to the state information of the container on which the application module in the container depends includes:
and if the state information of the dependent container is determined to indicate that the application module in the dependent container is started, determining that the control instruction is the starting instruction.
14. The method for starting an application module according to any one of claims 9 to 13, wherein before the sending the indication information to the container, the method for starting an application module further comprises:
receiving a query instruction sent by the container; the query instruction is used for instructing the control center to return the indication information.
15. The method for starting an application module according to claim 9, wherein after the sending the indication information to the container, the method for starting an application module further comprises:
receiving a state change instruction sent by the container; wherein the state change instruction is used for indicating the success or failure of the starting of the application module in the container;
and updating the state information of the container according to the state change instruction.
16. The method for starting an application module according to claim 15, wherein after the receiving the state change instruction sent by the container, and before the updating the state information of the container according to the state change instruction, the method for starting an application module further comprises:
detecting the state of an application module in the container, and determining a first detection result;
determining that the first detection result indicates that the state change instruction is correct.
17. The method for starting an application module according to claim 9, wherein after the sending the indication information to the container, the method for starting an application module further comprises:
detecting the state of an application module in the container and determining a second detection result;
and updating the state information of the container according to the second detection result.
18. The method for starting an application module according to any one of claims 15 to 17, wherein after the updating the state information of the container, the method for starting an application module further comprises:
if the updated state information of the container indicates that the application module in the container fails to start, sending a restart signal to the container; and the container receives the restart signal and restarts the application module in the container.
19. A container, comprising: at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; and the number of the first and second groups,
a communication component in communicative connection with a control device, the communication component receiving and transmitting data under control of the processor;
wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of launching an application module according to any of claims 1 to 8.
20. A control apparatus, characterized by comprising: at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; and the number of the first and second groups,
a communication component in communicative connection with the container, the communication component receiving and transmitting data under control of the processor;
wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of launching an application module according to any of claims 9 to 18.
21. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out a method for starting an application module according to any one of claims 1 to 8.
22. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method for starting an application module according to any one of claims 9 to 18.
CN201811518762.5A 2018-12-12 2018-12-12 Starting method of application module, container, control device and readable storage medium Pending CN111324385A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201811518762.5A CN111324385A (en) 2018-12-12 2018-12-12 Starting method of application module, container, control device and readable storage medium
PCT/CN2019/118594 WO2020119377A1 (en) 2018-12-12 2019-11-14 Start method for application module, container, control device and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201811518762.5A CN111324385A (en) 2018-12-12 2018-12-12 Starting method of application module, container, control device and readable storage medium

Publications (1)

Publication Number Publication Date
CN111324385A true CN111324385A (en) 2020-06-23

Family

ID=71075412

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811518762.5A Pending CN111324385A (en) 2018-12-12 2018-12-12 Starting method of application module, container, control device and readable storage medium

Country Status (2)

Country Link
CN (1) CN111324385A (en)
WO (1) WO2020119377A1 (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112596776A (en) * 2020-12-10 2021-04-02 平安普惠企业管理有限公司 Software publishing method, device, equipment and medium based on remote control
CN113296888A (en) * 2021-04-27 2021-08-24 优刻得科技股份有限公司 Mirror image processing method and system
CN113867145A (en) * 2021-09-29 2021-12-31 中国第一汽车股份有限公司 Application control method and device, electronic equipment and storage medium
CN114650318A (en) * 2022-02-24 2022-06-21 阿里巴巴(中国)有限公司 Switch pushing method

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140229951A1 (en) * 2011-10-24 2014-08-14 Huawei Technologies Co., Ltd. Method and System for Starting Application Program in Linux Container
US20150186129A1 (en) * 2014-01-02 2015-07-02 International Business Machines Corporation Method and system for deploying a program module
WO2018004403A1 (en) * 2016-06-28 2018-01-04 Telefonaktiebolaget Lm Ericsson (Publ) Managing a lifecycle of a software container
US20180024889A1 (en) * 2016-07-21 2018-01-25 International Business Machines Corporation Automatic restarting of containers
CN107870771A (en) * 2016-09-26 2018-04-03 平安科技(深圳)有限公司 Application builds and upgrade method and system
CN108132832A (en) * 2016-12-01 2018-06-08 腾讯科技(深圳)有限公司 Application program launching method and device
CN108664291A (en) * 2017-03-30 2018-10-16 中国移动通信集团山西有限公司 The construction method and device of container group
CN108762769A (en) * 2018-06-04 2018-11-06 万惠投资管理有限公司 Micro services application layout and dispositions method, device and terminal

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108718253A (en) * 2018-05-11 2018-10-30 新华三技术有限公司 A kind of positioning problems method and device

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140229951A1 (en) * 2011-10-24 2014-08-14 Huawei Technologies Co., Ltd. Method and System for Starting Application Program in Linux Container
US20150186129A1 (en) * 2014-01-02 2015-07-02 International Business Machines Corporation Method and system for deploying a program module
WO2018004403A1 (en) * 2016-06-28 2018-01-04 Telefonaktiebolaget Lm Ericsson (Publ) Managing a lifecycle of a software container
US20180024889A1 (en) * 2016-07-21 2018-01-25 International Business Machines Corporation Automatic restarting of containers
CN107870771A (en) * 2016-09-26 2018-04-03 平安科技(深圳)有限公司 Application builds and upgrade method and system
CN108132832A (en) * 2016-12-01 2018-06-08 腾讯科技(深圳)有限公司 Application program launching method and device
CN108664291A (en) * 2017-03-30 2018-10-16 中国移动通信集团山西有限公司 The construction method and device of container group
CN108762769A (en) * 2018-06-04 2018-11-06 万惠投资管理有限公司 Micro services application layout and dispositions method, device and terminal

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112596776A (en) * 2020-12-10 2021-04-02 平安普惠企业管理有限公司 Software publishing method, device, equipment and medium based on remote control
CN113296888A (en) * 2021-04-27 2021-08-24 优刻得科技股份有限公司 Mirror image processing method and system
CN113867145A (en) * 2021-09-29 2021-12-31 中国第一汽车股份有限公司 Application control method and device, electronic equipment and storage medium
WO2023051315A1 (en) * 2021-09-29 2023-04-06 中国第一汽车股份有限公司 Application control method and apparatus, electronic device, and storage medium
CN114650318A (en) * 2022-02-24 2022-06-21 阿里巴巴(中国)有限公司 Switch pushing method
CN114650318B (en) * 2022-02-24 2024-04-19 阿里巴巴(中国)有限公司 Switch pushing method

Also Published As

Publication number Publication date
WO2020119377A1 (en) 2020-06-18

Similar Documents

Publication Publication Date Title
CN111324385A (en) Starting method of application module, container, control device and readable storage medium
WO2017148268A1 (en) Task processing method, apparatus and system based on distributed system
CN107315656B (en) Multi-kernel embedded PLC software recovery method and PLC
CN109039779B (en) Equipment upgrading method, data transmission unit, controller local area network equipment and network
CN101980171B (en) Failure self-recovery method for software system and software watchdog system used by same
JP2001101033A (en) Fault monitoring method for operating system and application program
CN110768873B (en) Distributed heartbeat detection method, system and device and computer equipment
WO2018019242A1 (en) Self-recovery method and self-recovery system for web server
US11089454B2 (en) Systems and methods for upgrading firmware in multiple devices of a wireless fire detection system
JP7345921B2 (en) OTA differential update method and system for master-slave architecture
KR20130108613A (en) Method and device for interprocess communication and computer storage medium
CN101593119A (en) A kind of aerial firmware upgrade method of flash memory unit equipment and device monopolized
EP3879875A1 (en) Resource change method and device, apparatus, and storage medium
CN112953983A (en) SFTP transmission method and device
CN110691120A (en) Timing task state detection method, server and detection system
CN108228789B (en) Synchronous abnormity recovery method and device triggered by slave node
CN110275793B (en) Detection method and equipment for MongoDB data fragment cluster
CN114416293A (en) Fault recovery method and device for virtualization equipment
CN109450757B (en) Method for starting CANopen master station and overall management device thereof
CN109245979B (en) CANopen master-slave station reliability control method and overall management device thereof
CN111506388B (en) Container performance detection method, container management platform and computer storage medium
CN109905459B (en) Data transmission method and device
CN115335803A (en) Equipment upgrading method, intelligent equipment and computer readable storage medium
CN114691299A (en) Serverless-based edge computing resource management system
CN102752365A (en) Method and device for processing information

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
RJ01 Rejection of invention patent application after publication

Application publication date: 20200623

RJ01 Rejection of invention patent application after publication