CN111290768A - Updating method, device, equipment and medium for containerization application system - Google Patents
Updating method, device, equipment and medium for containerization application system Download PDFInfo
- Publication number
- CN111290768A CN111290768A CN202010074813.0A CN202010074813A CN111290768A CN 111290768 A CN111290768 A CN 111290768A CN 202010074813 A CN202010074813 A CN 202010074813A CN 111290768 A CN111290768 A CN 111290768A
- Authority
- CN
- China
- Prior art keywords
- resource change
- change request
- release
- admission control
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- 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/4555—Para-virtualisation, i.e. guest operating system has to be modified
Abstract
The application discloses an updating method, device, equipment and medium of a containerized application system, and relates to an updating technology of a computer program architecture. The specific implementation scheme is as follows: acquiring an initial resource change request; calling an admission control management program of resource change to acquire a release strategy configured for an initial resource change request; calling a modification program in an admission control management program, and modifying the initial resource change request according to the release strategy to form a target resource change request; and changing the resources of the application instance including the containerization management in the containerization application system according to the target resource change request. According to the technical scheme of the embodiment of the application, the initial resource change request is modified by introducing the release strategy, so that the resource is changed according to the modified initial resource change request, the effective control on the resource change process is realized, the function influence on the service execution process in the change process is reduced, and the intrusiveness of the resource change is reduced.
Description
Technical Field
The embodiment of the application relates to the technical field of computers, in particular to an updating technology of a computer program architecture.
Background
The Kubernetes system is a container orchestration system widely used in the industry for automated deployment, scaling, and management of containerized applications. The kubernets system includes a variety of resource types, typically including Deployment, repliaset, and Pod. The Deployment may manage one or more Pod through one or more replicasets. The Pod is a stateless application instance, and is specifically used to provide a business service for a user. The Deployment and the repliaset may manage the Pod according to a configured desired control objective.
In a system such as the kubernets system that manages application instances in containers, where software upgrade updates may be involved, old versions of Pod need to be reissued as new versions of Pod before providing business services.
In the existing Kubernetes system, two Update modes, namely, create Update and Rolling Update, are provided, and can be used for releasing a new version of Pod. However, the release process of the new version Pod is difficult to control, so that the release control requirement in the alternation process of the new version Pod and the old version Pod cannot be met.
Disclosure of Invention
The embodiment of the application provides an updating method, device, equipment and medium of a containerized application system, so that the updating process of the system is controllable, and different service requirements of updating and releasing are met.
In a first aspect, an embodiment of the present application provides an updating method for a containerized application system, including:
acquiring an initial resource change request;
calling an admission control management program of resource change to acquire a release strategy configured for the initial resource change request;
calling a modifying program in the admission control management program, and modifying the initial resource change request according to the issuing strategy to form a target resource change request;
and changing the resources in the containerized application system according to the target resource change request, wherein the resources at least comprise application instances managed in a containerization mode.
The method comprises the steps of obtaining an initial resource change request; calling an admission control management program of resource change to acquire a release strategy configured for an initial resource change request; calling a modification program in an admission control management program, and modifying the initial resource change request according to the release strategy to form a target resource change request; according to the target resource change request, the resources in the containerization application system are changed in a best effort manner; wherein the resources comprise at least application instances of containerization management. According to the technical scheme, the issuing strategy configured for the initial resource change request is introduced in the admission control link, and the initial resource change request is modified, so that the resource change is performed according to the modified initial resource change request, the effective control on the resource change process is realized, the functional influence on the service execution process in the change process is reduced, and the intrusiveness of the resource change is reduced.
Optionally, the publication policy includes a publication rule and a current publication state.
In an optional implementation manner in the foregoing application, the publishing policy is refined to include the publishing rule and the current publishing state, so that a basis is provided for publishing control in the resource changing process.
Optionally, the publication rule includes at least one of the following:
the number of release batches of the newly released application instance;
the number of newly published application instances per batch;
and the release condition of the subsequent batch is used for allowing the release of the subsequent batch when the release condition is met.
In an alternative embodiment of the above application, a basis is provided for batch control of the publication process by refining the publication rule to include the number of publication batches of new publication use cases.
In another alternative embodiment of the above application, by refining the publishing rule to include the number of newly published application instances per batch, a basis is provided for controlling the number of published application instances per batch.
In yet another alternative embodiment in the above application, the distribution rule is refined to include the distribution condition of the subsequent batch, so as to provide a basis for the connection mode between two adjacent batches and the sending time of the subsequent batch.
Optionally, the release condition of the subsequent batch includes at least one of the following:
receiving a subsequent batch release instruction input by a user;
meeting the release time interval of adjacent batches;
published batches run normally.
In an optional implementation manner of the foregoing application, by refining the publishing condition of the subsequent batch to include the subsequent batch publishing instruction received by the user, the publishing of the subsequent batch is triggered in an artificial control manner, and meanwhile, artificial suspension control after the publishing of the previous batch is realized.
In another optional embodiment of the foregoing application, the issuance of the subsequent batch is triggered by the pause duration by refining the issuance condition of the subsequent batch to include the issuance time interval satisfying the adjacent batch, and the duration pause control after the issuance of the previous batch is realized at the same time.
In yet another optional implementation manner in the above application, the issuance condition of the subsequent batch is refined to include normal operation of the issued batch, so that in the case of normal operation of the previous batch, issuance of the subsequent batch is performed, and meanwhile, abnormal suspension control after issuance of the previous batch is realized.
Optionally, the current publishing state includes publishing, suspended, cancelled, and completed of the application instance.
In an optional implementation manner of the foregoing application, the current publishing state is refined to include in-publishing, suspended, cancelled, and completed of the application instance, so that the reference basis for modifying the initial resource change request according to the publishing policy is perfected.
Optionally, the obtaining the initial resource change request includes:
acquiring an update request input by a user, wherein the update request is used for indicating to reissue an application instance managed in the containerized application system;
determining an updating mode and updating parameters according to the updating request;
and generating the initial resource change request according to the update mode and the update parameters.
In an optional implementation manner of the foregoing application, by refining the operation of obtaining the initial resource change request into obtaining an update request input by a user, determining an update mode and an update parameter according to the update request, and generating the initial resource change request according to the update mode and the update parameter, the method can adapt to an operation mechanism of the current kubernets system, and improve a generation manner of generating the initial resource change request in the current kubernets system.
Optionally, the update mode includes a rebuild update or a rolling update, and the update parameters corresponding to the rolling update mode include a maximum value of the application instance exceeding the expected control target and a maximum value of the application instance falling below the expected control target.
In an optional implementation manner in the foregoing application, the update mode is refined, and when the update mode includes a rolling update mode, the update parameter is further refined, so that a generation manner of the initial resource change request in the application is ensured, two update modes, namely a reconstruction update mode and a rolling update mode, can be adapted, and the generation manner of the initial resource change request is further enriched.
Optionally, the invoking a modification program in the admission control management program, and modifying the initial resource change request according to the issue policy to form a target resource change request includes:
calling a modifying program in the admission control management program, and determining whether the number of the released new version application instances meets the number requirement of the current release batch according to the release rule in the release strategy;
and if the number requirement of the current release batch is not met, modifying the number of the new version application instances released in the current release batch according to the release rule to form the target resource change request.
In an optional implementation manner of the foregoing application, the modification mechanism of the initial resource change request is refined to modify the number of new version application instances that do not meet the number requirement of the current release batch by calling a modification program in the admission control management program, so that the modification mechanism of the initial resource change request is perfected.
Optionally, the new version application instance is released in the newly built repliaset, and the original old version application instance is retained in the original repliaset.
In an optional implementation manner in the above application, the management object of the application instance is refined into repliaset, so that the architecture composition of the Kubernetes system to which the application is applied is further improved.
Optionally, invoking an admission control management program for resource change, and acquiring the release policy configured for the initial resource change request includes:
and calling an admission control management program for resource change, and searching a release strategy bound with the resource to be changed in an admission control configuration description file to be used as the release strategy configured by the initial resource change request.
In an optional implementation manner of the foregoing application, an acquisition mechanism of a release policy is refined into an admission control management program for invoking resource change, and a release policy bound to a resource to be changed is searched in an admission control configuration description file, so that a mechanism for determining the release policy is perfected, and by establishing a correspondence between the release policy and the resource to be changed in advance, pertinence, specificity, and controllability of the release policy are ensured.
Optionally, the method further includes:
and newly adding, changing or deleting the content of the release strategy according to the user input, and changing the binding relationship between the release strategy and the resource according to the user input.
In an optional implementation manner in the above application, through adding new adding, changing, deleting, and relationship binding operations to the release policy, a relationship binding mechanism between the release policy and the resource is perfected, and support is provided for pertinence, specificity, and feasibility of the release policy.
In a second aspect, an embodiment of the present application further provides an updating apparatus for a containerized application system, including:
the deployment control module is used for acquiring an initial resource change request;
the admission control module is used for calling an admission control management program of resource change and acquiring a release strategy configured for the initial resource change request;
the admission control module is used for calling a modification program in the admission control management program and modifying the initial resource change request according to the release strategy to form a target resource change request;
and the admission control module is used for changing the resources in the containerized application system according to the target resource change request, wherein the resources at least comprise application instances managed in a containerization mode.
In a third aspect, an embodiment of the present application further provides an electronic device, including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
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 update method of the containerized application system provided by the embodiment of the first aspect.
In a fourth aspect, the present application further provides a non-transitory computer-readable storage medium storing computer instructions for causing a computer to execute the update method of the containerized application system provided in the first aspect.
Other effects of the above-described alternative will be described below with reference to specific embodiments.
Drawings
The drawings are included to provide a better understanding of the present solution and are not intended to limit the present application. Wherein:
fig. 1A is a schematic diagram of a basic structure of a containerization application system according to an embodiment of the present application;
fig. 1B is a schematic diagram of a software architecture of a native delivery model according to an embodiment of the present application;
fig. 1C is a flowchart of an update method of a containerized application system according to an embodiment of the present application;
fig. 2 is a flowchart of an update method of a containerized application system according to a second embodiment of the present application;
fig. 3 is a block diagram of an update apparatus of a containerized application system according to a third embodiment of the present application;
fig. 4 is a block diagram of an electronic device for implementing an update method of a containerized application system according to a fourth embodiment of the present application.
Detailed Description
The following description of the exemplary embodiments of the present application, taken in conjunction with the accompanying drawings, includes various details of the embodiments of the application for the understanding of the same, which are to be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
In order to clearly introduce the technical solutions of the embodiments of the present application, first, a system architecture related to the embodiments of the present application is described.
Referring to fig. 1A, a basic structure diagram of a containerization application system is shown. The system comprises: deployment, repliaset, and Pod. Wherein, the Deployment, the replicase and the Pod are all resource types of the resource object. One Deployment can manage one or more replicase, and one replicase can manage one or more Pod. The Pod is a stateless application instance, specifically providing a business service for the user.
See fig. 1B for a schematic diagram of a software architecture of a native delivery model. The model comprises: a Deployment control module (Deployment Controller)10, a resource change service module (API Server)20, and an issuing policy management module 30.
The deployment control module 10 is configured to receive a resource change request sent by a user through a deployment control visual interface;
and a resource change service module 20 serving as a unified resource change management entry for providing a resource change service based on the resource change request.
The resource change service module 20 includes: an interface listener module (API Handler)21, an Admission control module (Admission Controller)22, and a database (etcd) 23.
The interface monitoring module 21 is configured to monitor a generation situation of the resource change request;
the admission control module 22 is configured to intercept the generated resource change request when it is monitored that the resource change request is generated, execute at least one of relevant logics such as resource modification and resource verification on the intercepted resource change request, and persist the modified resource in the database 23.
The release policy management module 30 is configured to store a binding relationship between each resource and a release policy;
the admission control module 22 is further configured to search, in the release policy management module 30, a release policy bound to the resource to be changed according to the resource change request, and modify the resource change request according to the searched release policy, so as to change the resource according to the modified resource change request.
Example one
Fig. 1C is a flowchart of an update method of a containerized application system according to a first embodiment of the present application, and the present application is applied to a case where a resource object in the containerized application system shown in fig. 1A is changed in the native delivery model shown in fig. 1B. The method is executed by an updating device of the containerized application system, which is realized by software and/or hardware and is specifically configured in the electronic equipment.
A method for updating a containerized application system shown in fig. 1C includes:
s101, acquiring an initial resource change request.
Illustratively, the initial resource change request may be understood as a resource change request initiated by a user operating the deployment control visualization interface according to an actual change requirement, and used for instructing a change operation on a resource object in the containerized application system.
The resource object is mainly a change to a Deployment. The resource object to be changed may be another resource object directly or indirectly managed by the Deployment after the Deployment is changed, such as a replicase or Pod.
Generally, the Deployment control module does not initiate the change of the replicase and Pod actively, but changes the Deployment control module, and after the change of the Deployment control module, the Deployment control module changes the controlled replicase, and further, the replicase changes the controlled Pod.
Wherein the changed resources at least comprise application instances of containerization management, namely the Pod. The specific changed content may include at least one of an image version, an environment variable, and a mount of a configuration file.
Illustratively, an initial resource change request generated by a user operating a Deployment control visual interface is acquired by a Deployment control module to realize the change of the Deployment control visual interface; or the deployment control module acquires an initial resource change request initiated by the deployment control module to change the replicase or Pod.
Specifically, the request for changing resources such as the Deployment is initiated by the user through operating the Deployment control visualization interface or through invoking and operating specific interactive contents through the interface. The request for changing resources such as the replicase is initiated by the Deployment control module, and the specific changed content is related to the change of the Deployment element (the description file of the replicase can be created according to the description file of the Deployment element, so that part of the content of the Deployment element description file is changed, and a new description file of the replicase can be automatically generated). The change request for the resource such as Pod is also initiated by the Deployment control module, and the specific change content is related to the change of the Deployment element (the description file of Pod can be created based on a description file of a new ReplicaSet automatically generated by changing part of the content of the Deployment element description file).
S102, calling an admission control management program of resource change, and acquiring a release strategy configured for the initial resource change request.
The release policy includes a release rule and a current release state.
The release rule is used for representing release conditions required to be met when the resource is released again. For example, the rules for Pod are reissued.
Optionally, the publishing rule may include the number of publishing batches for newly publishing the application instance, and is used to control the number of batches when the application instance is published, so as to reduce the influence on the stability of the system caused by frequently publishing the application instance; or alternatively, the publication rule may include: the number of the application examples newly released in each batch is used for controlling the number of the application examples released in each batch so as to reduce the influence on the stability and the safety of the system caused by the release of a large number of application examples in a single batch; or alternatively, the publication rule may include: and the issuing conditions of the subsequent batches are used for realizing the suspension control of the sending process of each batch, so that the performance of the application examples of the issued batches can be monitored conveniently, and the application examples with poor performance can be interfered in time.
The release condition of the subsequent batch is used for allowing the subsequent batch to be released when the release condition is met, so that release control among batches is realized, and user operation during batch release is simplified.
Optionally, the release condition of the subsequent batch may include: receiving a subsequent batch release instruction input by a user, so that the user can conveniently perform abnormity monitoring on the performance indexes of the application examples of the released batch, and triggering the release of the next batch under the condition that abnormity is not found, thereby realizing manual control on the release process; optionally, the release condition of the subsequent batch may include: the release time interval of adjacent batches is met, so that the performance of the released application examples of the previous batch is monitored in the release time interval, the application examples under abnormal conditions are interfered in the time interval, and the automatic control of the release process is realized; optionally, the release condition of the subsequent batch may include: published batches run normally in order to guarantee the performance of the published batch's application instance.
Illustratively, when the release of the subsequent batch is controlled manually, after the release of the previous batch is finished and suspended, a user is required to manually determine that there is no problem with the application instance released by the previous batch, and then trigger the release operation of the subsequent batch. Specifically, the update of the previous batch is prompted to be completed on a human-computer interaction interface, such as the aforementioned deployment control visualization interface, and the next batch is started again on the human-computer interaction interface triggered by the user, for example, through command line input or key control.
Illustratively, when the release of the subsequent batch is controlled automatically, after the release of the previous batch is finished and suspended, the release is carried out at intervals, and if the application example finds an abnormality, an abnormality alarm is carried out at intervals, and the release of the next batch is cancelled.
And the current release state is used for representing the current state of the application instance in the release process. Optionally, the current publishing state may include: in-release, suspended, cancelled, and completed of the application instance.
Specifically, when an interface monitoring module deployed in the resource change service module monitors that the deployment control module obtains the initial resource change request, the admission control module intercepts the initial resource change request and calls an admission control management program for resource change to obtain an issuing policy configured for the initial resource change request, so that corresponding logic is subsequently executed on the intercepted initial resource change request according to the issuing policy.
In an optional implementation manner of the embodiment of the application, a binding relationship between each release policy and a resource is pre-established, and the binding relationship is pre-stored in the local electronic device, other devices associated with the electronic device, or a cloud. Correspondingly, the step of calling an admission control management program for resource change to obtain the issue policy configured for the initial resource change request may be: and calling an admission control management program for resource change to search the release strategy bound with the resource to be changed according to the preset binding relationship, wherein the release strategy is used as the release strategy configured by the initial resource change request.
Typically, the binding relationship between the release policy and the resource exists in the release policy management module in the form of an admission control configuration description file, and the release policy bound to the resource to be changed is searched in the admission control configuration description file by calling an admission control management program for resource change, and is used as the release policy configured by the initial resource change request.
Optionally, the content of the release policy is newly added, changed or deleted according to the user input, and the binding relationship between the release policy and the resource is changed according to the user input.
Specifically, a user inputs the content of newly adding, changing or deleting the publishing strategy through a deployment control visual interface or an interface; after receiving the content to be newly added, the content to be changed or the content to be deleted, the deployment control module sends the content to the resource change service module; and the admission control module in the resource change service module transmits the contents to the release policy management module so that the release policy management module updates the release policy in the admission control configuration description file according to the contents to be added, the contents to be changed or the contents to be deleted.
S103, calling a modifying program in the admission control management program, and modifying the initial resource changing request according to the issuing strategy to form a target resource changing request.
Illustratively, the initial number of new published application instances in the initial resource change request and/or the initial number of new published application instances per batch are included.
When the initial number of the issuing batches in the initial resource change request or the initial number of the newly issued application instances in each batch is inconsistent with the corresponding content contained in the issuing rule, the inconsistent content in the initial resource change request is modified according to the content contained in the issuing policy to form a target resource change request meeting the issuing policy.
Specifically, the admission control module calls a modification program in the admission control management program, takes the obtained initial resource change request and the release strategy corresponding to the initial resource change request as input parameters, and modifies the initial resource change request to obtain a target resource change request.
S104, changing the resources in the containerization application system according to the target resource change request, wherein the resources at least comprise application instances subjected to containerization management.
Specifically, the admission control module changes the resource in the containerized application system according to the target resource change request, for example, at least one of a mirror version, an environment variable, a mount of a configuration file, and the like corresponding to the resource may be changed.
The method comprises the steps of obtaining an initial resource change request; calling an admission control management program of resource change to acquire a release strategy configured for an initial resource change request; calling a modification program in an admission control management program, and modifying the initial resource change request according to the release strategy to form a target resource change request; according to the target resource change request, the resources in the containerization application system are changed in a best effort manner; wherein the resources comprise at least application instances of containerization management. According to the technical scheme, the issuing strategy configured for the initial resource change request is introduced in the admission control link, and the initial resource change request is modified, so that the resource is changed according to the modified initial resource change request, the effective control on the resource change process is realized, the functional influence on the service execution process in the change process is reduced, the intrusiveness of the resource change on program codes is reduced, and the controllability of the resource change is completed by utilizing the modification mechanism in the existing admission control link.
Example two
Fig. 2 is a flowchart of an updating method of a containerized application system in the second embodiment of the present application, and the second embodiment of the present application performs optimization and improvement on the basis of the technical solutions of the foregoing embodiments.
Further, the operation of obtaining an initial resource change request is refined into obtaining an update request input by a user, wherein the update request is used for indicating to reissue the application instance managed in the containerized application system; determining an updating mode and updating parameters according to the updating request; and generating the initial resource change request' according to the update mode and the update parameters so as to perfect a generation mechanism of the initial resource change request.
The updating method of the containerized application system shown in fig. 2 includes:
s201, obtaining an updating request input by a user, wherein the updating request is used for indicating to reissue the application instance managed in the containerized application system.
S202, determining an updating mode and updating parameters according to the updating request.
Wherein the Update mode comprises a rebuild Update (regeneration Update) mode or a rolling Update (rolling Update) mode, and the Update parameters corresponding to the rolling Update mode comprise a maximum value of the application instance above an expected control target and a maximum value of the application instance below the expected control target.
Where the application instance exceeds the maximum value of the desired control objective (maxsource), is an optional configuration item that specifies the maximum number that can exceed the desired number of Pod. The value may be an absolute value (e.g., 5) or a percentage of the desired number of Pod (e.g., 10%). The absolute value, which can be calculated by a percentage, is rounded up. The default value is 1.
Where the application instance is below a maximum value of the desired control target (maxUnavailable), is an optional configuration item to specify a maximum number of unavailable Pod during the upgrade process. The value may be an absolute value (e.g., 5) or may be a percentage (e.g., 10%) of the desired number of Pod. Rounding down can be done by calculating the absolute value of the percentage. The default value is 1.
It should be noted that, in order to ensure the smooth implementation of the update operation, both maxUnavailable and maxSurge cannot be 0 at the same time.
S203, generating the initial resource change request according to the update mode and the update parameter.
After the user configures the update mode and the update parameters, the configuration control module may generate an initial resource change request according to the update mode and/or the update parameters.
In an optional implementation manner of the embodiment of the present application, when the update mode is the rolling update mode, the initial resource change request is generated according to the update mode and the update parameter.
For example, assuming that the number of Pod copies controlled by the Deployment is 9, if maxsource is 30%, the number of Pod copies controlled by the Deployment does not exceed the number of Pod copies controlled by the Deployment
(wherein,
to round up). If maxUnavailable is 30%, the number of Pod copies controlled by the Deployment does not exceed
(wherein,
to round down). Therefore, in the initial resource change request generated according to the update mode and the update parameters at the time of the first change, the number of pod copies of the new version of the replicase is 3, and the number of pod copies of the old version of the replicase is 7. And repeating the expansion and contraction processes during the second change, expanding 2 volumes and contracting 5 volumes when no abnormality is found in the pod of the new version released in the first batch, and determining that the quantity of pod copies of the new version of the replicase in the generated initial resource change request is 5 and the quantity of pod copies of the old version of the replicase is 5.
In another optional implementation manner of the embodiment of the present application, when the update mode is the rebuild update mode, since all the old version of the Pod controlled by the repliaset needs to be deleted in the rebuild update mode, an initial resource change request may be directly generated according to the update mode, in which the old version Pod is controlled to be 0 and the new version Pod is controlled to be 9.
S204, calling an admission control management program of resource change, and acquiring a release strategy configured for the initial resource change request.
Illustratively, the publishing policy includes the number of newly published application instances per batch.
S205, calling a modifying program in the admission control management program, and modifying the initial resource change request according to the issuing strategy to form a target resource change request.
For example, invoking a modification program in the admission control management program, and modifying the initial resource change request according to the issue policy to form a target resource change request may be: calling a modifying program in the admission control management program, and determining whether the number of the released new version application instances meets the number requirement of the current release batch according to the release rule in the release strategy; and if the number requirement of the current release batch is not met, modifying the number of the new version application instances released in the current release batch according to the release rule to form the target resource change request.
Take the example that the number of newly released application instances per batch does not exceed 2.
Continuing the previous example, when the number of Pod copies of the new version replicase is 3 and the number of Pod copies of the old version replicase is 7 in the initial resource change request generated by adopting the rolling update mode, it is obvious that the number of Pod copies of the new version replicase does not satisfy the distribution policy (3>2), and the number of Pod copies of the new version replicase and the old version replicase needs to be modified respectively according to the number (2) of each batch of newly released application instances to obtain the target resource change request. In the target resource change request, the number of pod copies of the new version of replicase is 2, and the number of pod copies of the old version of replicase is 7.
Continuing the previous example, when the number of Pod copies of the new version of replicase is 9 and the number of Pod copies of the old version of replicase is 0 in the initial resource change request generated by adopting the reestablishment update mode, it is obvious that the number of Pod copies of the new version of replicase does not satisfy the distribution policy (9>2), and the number of Pod copies of the new version of replicase needs to be modified respectively according to the number (2) of each batch of newly released application instances to obtain the target resource change request. In the target resource change request, the number of pod copies of the new version of replicase is 2, and the number of pod copies of the old version of replicase is 8.
Optionally, the new version application instance is released in the newly built repliaset, and the original old version application instance is retained in the original repliaset.
S206, changing the resources in the containerization application system according to the target resource change request, wherein the resources at least comprise application instances of containerization management.
According to the method and the device, the acquisition operation of the initial resource change request is refined into the acquisition of the update request input by the user, the update mode and the update parameter are determined according to the update request, the generation of the initial resource change request is carried out according to the update mode and the update parameter, the operation mechanism of the current Kubernets system can be adapted, and the generation mode of the initial resource change request in the current Kubernets system is improved.
EXAMPLE III
Fig. 3 is a block diagram of an update apparatus of a containerized application system according to a third embodiment of the present application. The present embodiment is applied to a case where a resource object in the containerization application system shown in fig. 1A is changed in the native delivery model shown in fig. 1B. The apparatus is implemented by software and/or hardware, and is specifically configured in an electronic device.
An updating apparatus 300 of a containerized application system shown in fig. 3 includes: a deployment control module 301 and an admission control module 302.
A deployment control module 301, configured to obtain an initial resource change request;
an admission control module 302, configured to invoke an admission control management program for resource change, and obtain a release policy configured for the initial resource change request;
an admission control module 302, configured to invoke a modification program in the admission control management program, and modify the initial resource change request according to the issue policy to form a target resource change request;
an admission control module 302, configured to change resources in the containerized application system according to the target resource change request, where the resources at least include application instances managed in a containerization manner.
According to the embodiment of the application, an initial resource change request is obtained through a deployment control module; calling an admission control management program of resource change through an admission control module to obtain a release strategy configured for an initial resource change request; calling a modification program in an admission control management program through an admission control module, and modifying the initial resource change request according to a release strategy to form a target resource change request; the admission control module is used for carrying out complete resource change on the containerized application system according to the target resource change request; wherein the resources comprise at least application instances of containerization management. According to the technical scheme, the initial resource change request is modified by introducing the release strategy configured for the initial resource change request, so that the resource change is performed according to the modified initial resource change request, the effective control on the resource change process is realized, the functional influence on the service execution process in the change process is reduced, and the intrusiveness of the resource change is reduced.
Further, the publication policy includes a publication rule and a current publication state.
Further, the publication rule includes at least one of:
the number of release batches of the newly released application instance;
the number of newly published application instances per batch;
and the release condition of the subsequent batch is used for allowing the release of the subsequent batch when the release condition is met.
Further, the release condition of the subsequent batch includes at least one of:
receiving a subsequent batch release instruction input by a user;
meeting the release time interval of adjacent batches;
published batches run normally.
Further, the current publication state includes in publication, suspended, cancelled, and completed for the application instance.
Further, the deployment control module 301 is configured to:
acquiring an update request input by a user, wherein the update request is used for indicating to reissue an application instance managed in the containerized application system;
determining an updating mode and updating parameters according to the updating request;
and generating the initial resource change request according to the update mode and the update parameters.
Further, the update mode includes a rebuild update or a rolling update, and the update parameters corresponding to the rolling update mode include a maximum value of the application instance above an expected control objective and a maximum value of the application instance below the expected control objective.
Further, the admission control module 302, when executing a modification program in the admission control management program and modifying the initial resource change request according to the issue policy to form a target resource change request, is specifically configured to:
calling a modifying program in the admission control management program, and determining whether the number of the released new version application instances meets the number requirement of the current release batch according to the release rule in the release strategy;
and if the number requirement of the current release batch is not met, modifying the number of the new version application instances released in the current release batch according to the release rule to form the target resource change request.
Further, the new version application instance is released in the newly built replicase, and the original old version application instance is retained in the original replicase.
Further, the admission control module 302, when executing the admission control management program for invoking resource change and acquiring the issue policy configured for the initial resource change request, is specifically configured to:
and calling an admission control management program for resource change, and searching a release strategy bound with the resource to be changed in an admission control configuration description file to be used as the release strategy configured by the initial resource change request.
Further, the deployment control module 301 is further configured to obtain user input to add, change, or delete the content of the publishing policy;
correspondingly, the admission control module 302 is further configured to add, change or delete the content of the distribution policy according to the user input, and change the binding relationship between the distribution policy and the resource according to the user input.
The updating device of the containerized application system can execute the updating method of the containerized application system provided by any embodiment of the application, and has the corresponding functional modules and beneficial effects of executing the updating method of the containerized application system.
Example four
According to an embodiment of the present application, an electronic device and a readable storage medium are also provided.
Fig. 4 is a block diagram of an electronic device that implements the update method of the containerized application system according to the embodiment of the present application. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the present application that are described and/or claimed herein.
As shown in fig. 4, the electronic apparatus includes: one or more processors 401, memory 402, and interfaces for connecting the various components, including high-speed interfaces and low-speed interfaces. The various components are interconnected using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions for execution within the electronic device, including instructions stored in or on the memory to display graphical information of a GUI on an external input/output apparatus (such as a display device coupled to the interface). In other embodiments, multiple processors and/or multiple buses may be used, along with multiple memories and multiple memories, as desired. Also, multiple electronic devices may be connected, with each device providing portions of the necessary operations (e.g., as a server array, a group of blade servers, or a multi-processor system). In fig. 4, one processor 401 is taken as an example.
The memory 402, which is a non-transitory computer readable storage medium, may be used to store non-transitory software programs, non-transitory computer executable programs, and modules, such as program instructions/modules (e.g., the deployment control module 301 and the admission control module 302 shown in fig. 3) corresponding to the update method of the containerized application system in the embodiments of the present application. The processor 401 executes various functional applications of the server and data processing by running non-transitory software programs, instructions and modules stored in the memory 402, that is, implements the update method of the containerized application system in the above method embodiment.
The memory 402 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 data created by use of the electronic device of the update method of the containerized application system, and the like. Further, the memory 402 may include high speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory 402 may optionally include memory located remotely from the processor 401, and these remote memories may be connected over a network to an electronic device that implements the update method of the containerized application system. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The electronic device implementing the update method of the containerized application system may further include: an input device 403 and an output device 404. The processor 401, the memory 402, the input device 403 and the output device 404 may be connected by a bus or other means, and fig. 4 illustrates an example of a connection by a bus.
The input device 403 may receive input numeric or character information and generate key signal inputs related to user settings and function control of the electronic device implementing the update method of the containerized application system, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, a pointing stick, one or more mouse buttons, a track ball, a joystick, or the like. The output devices 404 may include a display device, auxiliary lighting devices (e.g., LEDs), and haptic feedback devices (e.g., vibrating motors), among others. The display device may include, but is not limited to, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, and a plasma display. In some implementations, the display device can be a touch screen.
Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, application specific ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
These computer programs (also known as programs, software applications, or code) include machine instructions for a programmable processor, and may be implemented using high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.
The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
The method comprises the steps of obtaining an initial resource change request; calling an admission control management program of resource change to acquire a release strategy configured for an initial resource change request; calling a modification program in an admission control management program, and modifying the initial resource change request according to the release strategy to form a target resource change request; according to the target resource change request, the resources in the containerization application system are changed in a best effort manner; wherein the resources comprise at least application instances of containerization management. According to the technical scheme, the initial resource change request is modified by introducing the release strategy configured for the initial resource change request, so that the resource change is performed according to the modified initial resource change request, the effective control on the resource change process is realized, the functional influence on the service execution process in the change process is reduced, and the intrusiveness of the resource change is reduced.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present application may be executed in parallel, sequentially, or in different orders, and the present invention is not limited thereto as long as the desired results of the technical solutions disclosed in the present application can be achieved.
The above-described embodiments should not be construed as limiting the scope of the present application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (14)
1. An updating method of a containerized application system, comprising:
acquiring an initial resource change request;
calling an admission control management program of resource change to acquire a release strategy configured for the initial resource change request;
calling a modifying program in the admission control management program, and modifying the initial resource change request according to the issuing strategy to form a target resource change request;
and changing the resources in the containerized application system according to the target resource change request, wherein the resources at least comprise application instances managed in a containerization mode.
2. The method of claim 1, wherein the publication policy includes publication rules and a current publication status.
3. The method of claim 2, wherein the publication rule comprises at least one of:
the number of release batches of the newly released application instance;
the number of newly published application instances per batch;
and the release condition of the subsequent batch is used for allowing the release of the subsequent batch when the release condition is met.
4. The method according to claim 3, wherein the release condition of the subsequent batch comprises at least one of:
receiving a subsequent batch release instruction input by a user;
meeting the release time interval of adjacent batches;
published batches run normally.
5. The method of claim 2, wherein the current publication state comprises in publication, suspended, cancelled, and completed for an application instance.
6. The method of any of claims 1-5, wherein obtaining the initial resource change request comprises:
acquiring an update request input by a user, wherein the update request is used for indicating to reissue an application instance managed in the containerized application system;
determining an updating mode and updating parameters according to the updating request;
and generating the initial resource change request according to the update mode and the update parameters.
7. The method of claim 6, wherein the update mode comprises a rebuild update mode or a rolling update mode, wherein the update parameters corresponding to the rolling update mode comprise a maximum value of the application instance above an expected control objective, and wherein the maximum value of the application instance below the expected control objective.
8. The method of claim 7, wherein invoking a modification procedure in the admission control management procedure to modify the initial resource change request according to the issuance policy to form a target resource change request comprises:
calling a modifying program in the admission control management program, and determining whether the number of the released new version application instances meets the number requirement of the current release batch according to the release rule in the release strategy;
and if the number requirement of the current release batch is not met, modifying the number of the new version application instances released in the current release batch according to the release rule to form the target resource change request.
9. The method of claim 8, wherein the new version application instance is published in a newly created replicase, and the old version application instance is retained in the original replicase.
10. The method of claim 1, wherein invoking an admission control manager for resource change, and obtaining the configured release policy for the initial resource change request comprises:
and calling an admission control management program for resource change, and searching a release strategy bound with the resource to be changed in an admission control configuration description file to be used as the release strategy configured by the initial resource change request.
11. The method of claim 1, further comprising:
and newly adding, changing or deleting the content of the release strategy according to the input of the user, and changing the binding relationship between the release strategy and the resource according to the input of the user.
12. An updating apparatus of a containerized application system, comprising:
the deployment control module is used for acquiring an initial resource change request;
the admission control module is used for calling an admission control management program of resource change and acquiring a release strategy configured for the initial resource change request;
the admission control module is used for calling a modification program in the admission control management program and modifying the initial resource change request according to the release strategy to form a target resource change request;
and the admission control module is used for changing the resources in the containerized application system according to the target resource change request, wherein the resources at least comprise application instances managed in a containerization mode.
13. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of updating a containerized application system of any of claims 1-11.
14. A non-transitory computer readable storage medium storing computer instructions for causing a computer to execute the update method of a containerized application system of any one of claims 1-11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010074813.0A CN111290768B (en) | 2020-01-22 | 2020-01-22 | Updating method, device, equipment and medium of containerized application system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010074813.0A CN111290768B (en) | 2020-01-22 | 2020-01-22 | Updating method, device, equipment and medium of containerized application system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111290768A true CN111290768A (en) | 2020-06-16 |
| CN111290768B CN111290768B (en) | 2023-10-20 |
Family
ID=71030719
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010074813.0A Active CN111290768B (en) | 2020-01-22 | 2020-01-22 | Updating method, device, equipment and medium of containerized application system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111290768B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112860343A (en) * | 2021-02-10 | 2021-05-28 | 北京百度网讯科技有限公司 | Configuration changing method, system, device, electronic equipment and storage medium |
| CN113076248A (en) * | 2021-04-08 | 2021-07-06 | 马上消费金融股份有限公司 | Application processing method, device and equipment and readable storage medium |
| CN113726871A (en) * | 2021-08-27 | 2021-11-30 | 猪八戒股份有限公司 | Dispatching method and system for automatic code release |
| CN114531443A (en) * | 2022-02-18 | 2022-05-24 | 京东科技信息技术有限公司 | Cluster-based container control method and system |
| CN117369946A (en) * | 2023-10-18 | 2024-01-09 | 中科驭数（北京）科技有限公司 | Container deployment method and device based on DPU, electronic equipment and medium |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070288526A1 (en) * | 2006-06-08 | 2007-12-13 | Emc Corporation | Method and apparatus for processing a database replica |
| CN103176790A (en) * | 2011-12-26 | 2013-06-26 | 阿里巴巴集团控股有限公司 | Application releasing method and application releasing system |
| CN105100051A (en) * | 2015-05-29 | 2015-11-25 | 北京京东尚科信息技术有限公司 | Method and system for realizing data resource access right control |
| US20180091583A1 (en) * | 2016-09-26 | 2018-03-29 | Amazon Technologies, Inc. | Multi-party updates to distributed systems |
| CN108509253A (en) * | 2018-04-03 | 2018-09-07 | 南京中兴软创软件技术有限公司 | A kind of method of a large amount of container mirror images of release quickly |
| CN108536524A (en) * | 2018-03-13 | 2018-09-14 | Oppo广东移动通信有限公司 | Resource regeneration method, device, terminal and storage medium |
| US10079832B1 (en) * | 2017-10-18 | 2018-09-18 | Palantir Technologies Inc. | Controlling user creation of data resources on a data processing platform |
| CN108874403A (en) * | 2018-05-30 | 2018-11-23 | 深圳市分期乐网络科技有限公司 | Dissemination method, device, equipment and the storage medium of rule file |
| CN109814910A (en) * | 2018-12-14 | 2019-05-28 | 深圳壹账通智能科技有限公司 | Automate gray scale dissemination method, device, computer system and storage medium |
| CN110287029A (en) * | 2019-06-27 | 2019-09-27 | 中国—东盟信息港股份有限公司 | A method of it is adjusted based on kubernetes container resource dynamic |
| CN110427204A (en) * | 2019-08-08 | 2019-11-08 | 浪潮云信息技术有限公司 | A kind of automation gray scale dissemination method based on container and service grid |
-
2020
- 2020-01-22 CN CN202010074813.0A patent/CN111290768B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070288526A1 (en) * | 2006-06-08 | 2007-12-13 | Emc Corporation | Method and apparatus for processing a database replica |
| CN103176790A (en) * | 2011-12-26 | 2013-06-26 | 阿里巴巴集团控股有限公司 | Application releasing method and application releasing system |
| CN105100051A (en) * | 2015-05-29 | 2015-11-25 | 北京京东尚科信息技术有限公司 | Method and system for realizing data resource access right control |
| US20180091583A1 (en) * | 2016-09-26 | 2018-03-29 | Amazon Technologies, Inc. | Multi-party updates to distributed systems |
| US10079832B1 (en) * | 2017-10-18 | 2018-09-18 | Palantir Technologies Inc. | Controlling user creation of data resources on a data processing platform |
| CN108536524A (en) * | 2018-03-13 | 2018-09-14 | Oppo广东移动通信有限公司 | Resource regeneration method, device, terminal and storage medium |
| CN108509253A (en) * | 2018-04-03 | 2018-09-07 | 南京中兴软创软件技术有限公司 | A kind of method of a large amount of container mirror images of release quickly |
| CN108874403A (en) * | 2018-05-30 | 2018-11-23 | 深圳市分期乐网络科技有限公司 | Dissemination method, device, equipment and the storage medium of rule file |
| CN109814910A (en) * | 2018-12-14 | 2019-05-28 | 深圳壹账通智能科技有限公司 | Automate gray scale dissemination method, device, computer system and storage medium |
| CN110287029A (en) * | 2019-06-27 | 2019-09-27 | 中国—东盟信息港股份有限公司 | A method of it is adjusted based on kubernetes container resource dynamic |
| CN110427204A (en) * | 2019-08-08 | 2019-11-08 | 浪潮云信息技术有限公司 | A kind of automation gray scale dissemination method based on container and service grid |
Non-Patent Citations (4)
| Title |
|---|
| EDDY TRUYEN 等: "A Comprehensive Feature Comparison Study of Open-Source Container Orchestration Frameworks", 《APPLIED SCIENCES》, vol. 9, no. 5, pages 1 - 76 * |
| SHAWN-LI: "Pod控制器Deployment使用详解（更新策略、回滚策略、暂停策略）以及金丝雀发布详解", pages 1 - 3 * |
| 何思玫: "面向容器云平台的集群资源调度管理器的设计与实现", 《中国优秀硕士学位论文全文数据库 信息科技辑》, no. 12, pages 139 - 177 * |
| 阿里云: "Kubernetes分批发布", pages 1 - 3, Retrieved from the Internet <URL:《https://help.aliyun.com/document_detail/96666.html》> * |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112860343A (en) * | 2021-02-10 | 2021-05-28 | 北京百度网讯科技有限公司 | Configuration changing method, system, device, electronic equipment and storage medium |
| CN112860343B (en) * | 2021-02-10 | 2024-04-23 | 北京百度网讯科技有限公司 | Configuration changing method, system, device, electronic equipment and storage medium |
| CN113076248A (en) * | 2021-04-08 | 2021-07-06 | 马上消费金融股份有限公司 | Application processing method, device and equipment and readable storage medium |
| CN113076248B (en) * | 2021-04-08 | 2021-11-30 | 马上消费金融股份有限公司 | Application processing method, device and equipment and readable storage medium |
| CN113726871A (en) * | 2021-08-27 | 2021-11-30 | 猪八戒股份有限公司 | Dispatching method and system for automatic code release |
| CN113726871B (en) * | 2021-08-27 | 2024-02-02 | 猪八戒股份有限公司 | Scheduling method and system for automatic code release |
| CN114531443A (en) * | 2022-02-18 | 2022-05-24 | 京东科技信息技术有限公司 | Cluster-based container control method and system |
| CN117369946A (en) * | 2023-10-18 | 2024-01-09 | 中科驭数（北京）科技有限公司 | Container deployment method and device based on DPU, electronic equipment and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111290768B (en) | 2023-10-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111290768B (en) | Updating method, device, equipment and medium of containerized application system | |
| CN111258609B (en) | Upgrading method and device of Kubernetes cluster, electronic equipment and medium | |
| CN111475259B (en) | Applet loading method and device and electronic equipment | |
| US11824714B2 (en) | Method and apparatus for updating an edge node, device, medium and program product | |
| CN110651256B (en) | System and method for preventing service interruption during software update | |
| CN112527474B (en) | Task processing method and device, equipment, readable medium and computer program product | |
| CN110704162B (en) | Method, device and equipment for sharing container mirror image by physical machine and storage medium | |
| CN110995480A (en) | Block chain network deployment method, device, electronic equipment and medium | |
| EP3869336A1 (en) | Method and apparatus for processing development machine operation task, device and storage medium | |
| CN112073994A (en) | Method and device for over-the-air upgrading, electronic equipment and readable storage medium | |
| CN111562969B (en) | Intelligent contract implementation method, device, equipment and medium for block chain | |
| CN112925651A (en) | Application resource deployment method, device, electronic equipment and medium | |
| CN111324417A (en) | Kubernetes cluster component control method and device, electronic equipment and medium | |
| CN110727557A (en) | Log collector control method, platform, electronic device and storage medium | |
| CN111782254A (en) | Method, device, equipment and storage medium for upgrading object | |
| CN111930539A (en) | Task management method, device and equipment based on label engine and storage medium | |
| CN111625195A (en) | Method and device for server capacity expansion | |
| CN112084395A (en) | Search method, search device, electronic device, and storage medium | |
| US20200133709A1 (en) | System and method for content - application split | |
| CN111767149A (en) | Scheduling method, device, equipment and storage equipment | |
| CN111770176A (en) | Traffic scheduling method and device | |
| CN113051122B (en) | Performance data acquisition method, device, electronic equipment and medium | |
| CN112148447B (en) | Task processing method and system based on risk control and electronic equipment | |
| CN115576565A (en) | Application program deployment method and device, electronic equipment and storage medium | |
| CN111510480B (en) | Request sending method and device and first server |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |