CN113076248B - Application processing method, device and equipment and readable storage medium - Google Patents
Application processing method, device and equipment and readable storage medium Download PDFInfo
- Publication number
- CN113076248B CN113076248B CN202110378514.0A CN202110378514A CN113076248B CN 113076248 B CN113076248 B CN 113076248B CN 202110378514 A CN202110378514 A CN 202110378514A CN 113076248 B CN113076248 B CN 113076248B
- Authority
- CN
- China
- Prior art keywords
- instance
- verification
- published
- issued
- target 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.)
- Active
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 19
- 238000012795 verification Methods 0.000 claims abstract description 142
- 238000000034 method Methods 0.000 claims abstract description 42
- 238000012545 processing Methods 0.000 claims abstract description 19
- 230000008569 process Effects 0.000 claims description 24
- 238000007726 management method Methods 0.000 description 16
- 238000010586 diagram Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 230000000694 effects Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 238000013500 data storage Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000005096 rolling process Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3604—Software analysis for verifying properties of programs
- G06F11/3612—Software analysis for verifying properties of programs by runtime analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- 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
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses an application processing method, an application processing device, application processing equipment and a readable storage medium, and relates to the technical field of computers, so that issued applications can meet business requirements. The method comprises the following steps: receiving an update request for a target application; generating a verification instance according to the updating request; verifying the verification instance; when the verification of the verification instance passes, generating an instance to be issued, wherein the instance to be issued is generated according to the verification instance; and issuing the instance to be issued. The embodiment of the application can ensure that the issued application can meet the requirements of the service.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to an application processing method, an application processing apparatus, an application processing device, and a readable storage medium.
Background
In the financial field, as businesses are deployed in large-scale containerization, containerization applications are increased. Containerized applications are used primarily to enable orchestration and lifecycle control of applications. In the existing kubernets resource management mode, the update mode adopted by the stateful controller is a scheme of rolling update. That is, the controller updates the instances of the applications in order of the start time from late to early after receiving the update request.
In practical applications, it is possible to find that a problem occurs in an application during the process of releasing the application. In such a situation, the existing method cannot handle such a situation, so that the published application cannot meet normal business requirements.
Disclosure of Invention
The embodiment of the application provides an application processing method, an application processing device, application processing equipment and a readable storage medium, so as to ensure that issued applications can meet business requirements.
In a first aspect, an embodiment of the present application provides an application processing method, including:
receiving an update request for a target application;
generating a verification instance according to the updating request;
verifying the verification instance;
when the verification of the verification instance passes, generating an instance to be issued, wherein the instance to be issued is generated according to the verification instance;
and issuing the instance to be issued.
In a second aspect, an embodiment of the present application further provides an application processing apparatus, including:
the first receiving module is used for receiving an update request of a target application;
the first generation module is used for generating a verification example according to the updating request;
the first verification module is used for verifying the verification example;
the second generation module is used for generating an instance to be issued when the verification of the verification instance passes, wherein the instance to be issued is generated according to the verification instance;
and the issuing module is used for issuing the example to be issued.
In a third aspect, an embodiment of the present application further provides an electronic device, including: a memory, a processor and a program stored on the memory and executable on the processor, the processor implementing the steps in the application processing method as described above when executing the program.
In a fourth aspect, an embodiment of the present application further provides an application processing method, including:
receiving an update request for a target application;
modifying the metadata information of the target application according to the updating request;
generating a verification example according to the modified metadata information of the target application;
verifying the verification instance;
when the verification of the verification instance passes, generating an instance to be issued, wherein the instance to be issued is generated according to the verification instance;
and issuing the instance to be issued.
In a fifth aspect, an embodiment of the present application further provides an application processing system, including: a cloud management and control system and a controller;
the cloud management and control system is used for receiving an update request of a target application; modifying the metadata information of the target application according to the updating request; the controller is used for generating a verification example according to the modified metadata information of the target application; verifying the verification instance; when the verification of the verification instance passes, generating an instance to be issued, wherein the instance to be issued is generated according to the verification instance; and issuing the instance to be issued.
In a sixth aspect, the present application further provides a readable storage medium, where a program is stored, and when the program is executed by a processor, the program implements the steps in the application processing method as described above.
In the embodiment of the application, after an update request for a target application is received, a verification instance is generated, and after the verification of the verification instance is passed, an instance to be issued is generated and verified according to the verification instance. Therefore, by using the scheme of the embodiment of the application, the generated to-be-issued instance can better meet the business requirement because the verification is carried out by using the verification instance before the issuance.
Drawings
Fig. 1 is a flowchart of an application processing method provided in an embodiment of the present application;
FIG. 2 is a schematic diagram of an application processing system provided by an embodiment of the present application;
FIG. 3 is a process diagram of an application processing method provided by an embodiment of the present application;
fig. 4 is a block diagram of an application processing apparatus according to an embodiment of the present application.
Detailed Description
In the embodiment of the present application, the term "and/or" describes an association relationship of associated objects, and means that there may be three relationships, for example, a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
In the embodiments of the present application, the term "plurality" means two or more, and other terms are similar thereto.
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a flowchart of an application processing method provided in an embodiment of the present application, and as shown in fig. 1, the method includes the following steps:
Wherein the target application may refer to an arbitrary application. When a certain application needs to be updated, a user can trigger the update of the application through the cloud management and control system. After receiving the update request, the cloud management and control system modifies the metadata information of the application and sends the modified metadata information to the controller. Correspondingly, the controller receives an update request for the target application and acquires the metadata information modified by the target application from the cloud management and control system.
And 102, generating a verification example according to the updating request.
In the embodiment of the present application, the generated verification instance corresponds to the update request, that is, the verification instance needs to satisfy the requirement of the update request. Kubernets is a cross-host cluster, open-source container scheduling platform that automates the deployment, expansion, and operation of application containers, providing a container-centric infrastructure. Therefore, in the embodiment of the present Application, specifically, an API (Application Programming Interface) of Kubernetes may be called to generate the verification instance according to the update request. The method for generating the verification instance can be implemented by referring to the prior art.
And 103, verifying the verification example.
Specifically, in this step, the verification instance may be run to obtain a running result. Since the purpose of the update is to enable the instance to meet the new requirements of the service, in the embodiment of the present application, whether the operation result of the instance meets the service requirement may be determined to pass the verification. If the requirement of the target service is met, the verification of the verification example is passed; and when the operation result does not meet the requirement of the target service, the verification of the verification example is not passed. In this way, the published instances can be made to better conform to the needs of the business.
In addition, other authentication methods are possible. For example, the verification of whether the instance is normal or not is performed by directly accessing the instance IP, i.e. the port, or directly checking whether the start log of the verification instance is normal or not.
Because only the verification example is started, the function verification can be carried out under the condition of minimum influence on the online service, thereby reducing the influence on the application and ensuring that the application is more stable.
And 104, generating an instance to be issued when the verification of the verification instance passes, wherein the instance to be issued is generated according to the verification instance.
And the number of the instances to be issued is the same as the number of the instances which the target application has when receiving the updating request.
The number of instances that the target application has when receiving the update request may also be understood as the number of instances that the target application has before the update. For example, assuming that the target application has 3 instances before this time is not updated, the number of instances to be published generated here is 3.
The number of the to-be-issued instances is generated in the same way as the verification instances. Since the verification instance is in accordance with the requirements of the business, the to-be-published instance generated here is also in accordance with the requirements of the business. The generated to-be-released example can be used for carrying out gray scale testing. At this time, the instance to be issued does not need to process the service request.
And 105, releasing the to-be-released example.
In the process of releasing the new version instance, the new version instance and the old version instance run simultaneously. When there are service requests, these service requests are distributed to these instances. In the embodiment of the application, in the process of publishing the instance, one-by-one instance can be selected according to a preset configuration, or a plurality of instances can be published in batch. In the case of batch distribution, the number of instances distributed at a time and the like can also be controlled according to the selection of the user.
Specifically, when the instances are issued one by one, if the instances to be issued are multiple, each first instance to be issued in the instances to be issued may be issued respectively, and each second instance to be issued may be closed respectively, where the second instance to be issued is an instance corresponding to the first instance to be issued in an existing instance before the target application is updated. That is, the first to-be-published instance is the updated second to-be-published instance. In this way, the impact on the service can be avoided, the service is smoothly migrated to the instance of the newly released version, and the user is subjected to zero perception. Moreover, in the mode, in the process of issuing, because the data are issued one by one, if a problem occurs in a certain instance, rollback can be quickly realized.
For example, it is assumed that existing examples before the update of the target application are dp1, dp2, and dp3, and after the update, dp11, dp21, and dp31 are respectively corresponding. Then, in the process of publishing, dp11 may be published first and dp1 may be closed. Here, the effect of turning off dp1 is not to have it process traffic requests. Then the request originally assigned to dp1 will be assigned to dp 11. The dp21 may then be issued and dp2 closed, dp31 issued and dp3 closed.
Specifically, when the instances are published in batch, if the instances to be published are multiple, then when the instances to be published are published, the multiple instances to be published can be published simultaneously, and then the multiple instances of the old version are closed simultaneously. Specifically, at least two first instances to be published in the instances to be published are published simultaneously, and a second instance to be published is closed, wherein the second instance to be published is an instance corresponding to the first instance to be published in an existing instance before the target application is updated. By the method, the plurality of instances can be updated simultaneously, time consumption in the issuing process can be reduced in the issuing process, and the influence of the number of the instances on the issuing process is reduced.
For example, it is assumed that existing examples before the update of the target application are dp1, dp2, and dp3, and after the update, dp11, dp21, and dp31 are respectively corresponding. Then, in the issuing process, dp11, dp21, dp31 may be issued simultaneously, and dp1, dp2, dp3 may be turned off simultaneously; alternatively, dp11 and dp21 may be issued simultaneously, dp1 and dp2 may be closed simultaneously, and then dp31 may be issued, and dp3 may be closed.
In addition, in order to save system space, the second to-be-published instance and/or the verification instance may also be deleted. That is, after the instance of the new version is released, the instance of the old version may be deleted, as well as the verification instance.
Optionally, on the basis of the foregoing embodiment, after step 101, current operation information of the target application may also be obtained, and then, according to the update request, information to be updated of the target application is obtained. And then, comparing the current operation information with the information to be updated, and determining whether to update the target application according to a comparison result. The operation information may include version information of the instance, operation result information, and the like. Then, in step 102, specifically, when the comparison result indicates that the current operation information and the information to be updated are different, a verification instance is generated according to the update request. In this way, useless updates to the target application can be avoided, thereby saving resources.
In the embodiment of the application, after an update request for a target application is received, a verification instance is generated, and after the verification of the verification instance is passed, an instance to be issued is generated and verified according to the verification instance. Therefore, by using the scheme of the embodiment of the application, the generated to-be-issued instance can better meet the business requirement because the verification is carried out by using the verification instance before the issuance.
On the basis of the above embodiment, when the verification of the verification instance fails, the existing instance of the target application may be reused to process the service request. In this way, rollback of instances may be implemented prior to publication, thereby improving the success rate of publication.
Referring to fig. 2, fig. 2 is a schematic diagram of an application processing system provided in an embodiment of the present application. The system may include: cloud management and control system 201 and controller 202.
The cloud management and control system 201 is configured to receive an update request for a target application; modifying the metadata information of the target application according to the updating request; the controller 202 is configured to generate a verification instance according to the modified metadata information of the target application; verifying the verification instance; when the verification of the verification instance passes, generating an instance to be issued, wherein the instance to be issued is generated according to the verification instance; and issuing the instance to be issued.
In practical application, when an application needs to be updated, a user can trigger the update of the application through the cloud management and control system. After receiving the update request, the cloud management and control system modifies the metadata information of the application, and sends the modified metadata information to the controller in a manner of calling an API server of Kubernetes. Correspondingly, the controller acquires the metadata information modified by the target application from the cloud management and control system.
In the embodiment of the present application, the controller 202 implements a Custom Resource manager in the form of kubernets CRD (Custom Resource Definition), and specifically, in the embodiment of the present application, a Custom Resource manager is defined by a Resource type apitextensions of kubernets. The controller 202 may acquire the metadata modified by the application and the metadata before modification from the cloud management and control system through a Kubernetes message notification mechanism. The controller 202 may determine whether the application needs an updated version or modify the resource size by comparing the metadata before and after the modification. If the update is needed, the controller 202 updates the version or resource of each instance by calling the interface of the kubernets instance lifecycle, so as to achieve the purpose of controlling the instance lifecycle.
In connection with fig. 3, it is assumed that an application has three instances dp1, dp2, dp 3. The flow of the three examples is in an open state, and service requests can be received. When an update is required, the controller will generate a verification instance with a suffix name dp0, for example. Thereafter, the verification instance is run. The controller accesses instance IP directly: and determining whether the starting of the verification instance is normal and the function is expected by a port mode or a mode of checking whether the instance starting log is normal. At this time, the authentication instance does not process the service request, i.e. the traffic of the authentication instance is closed.
After the verification of the verification example passes, at this time, the user may send an issue instruction through the cloud management and control system. According to the issuing instruction, a plurality of new version examples can be generated at the same time, wherein the number of the new version examples is the same as that of the old version examples. In this embodiment, assume that corresponding to dp1, dp2, dp3, examples of new versions generated are dp4, dp5, dp 6. The generated new version of the example can be used for performing gray scale test to ensure the reliability of the operation result of the example. After the new version of the instance is generated, dp4, dp5, dp6 are issued in response to the issue command, respectively, and the old version of the instance is closed at the same time. For example, after publishing dp4, dp1 may be closed; after the dp5 is issued, the dp2 may be closed; after the dp6 is issued, the dp3 may be closed. In this way, the service can be smoothly transited to the instance of the new version, thereby reducing the influence on the user. Afterwards, dp0, dp1, dp2, dp3 may also be deleted.
Of course, dp4, dp5, dp6 may be issued simultaneously with the issuing process, and dp1, dp2, dp3 may be closed. At this time, the process of publication may be made unaffected by the number of instances.
If the authentication of the authentication instance fails, then rollback onto the old version of the instance may also be controlled so that the business request is still processed by the old version of the instance.
In the embodiment of the application, after an update request for a target application is received, a verification instance is generated, and after the verification of the verification instance is passed, an instance to be issued is generated and verified according to the verification instance. Therefore, by using the scheme of the embodiment of the application, the generated to-be-issued instance can better meet the business requirement because the verification is carried out by using the verification instance before the issuance. Since the verification example is only verified in the verification process, the function verification can be performed under the condition of minimum influence on the online service, so that the application is more stable.
In addition, an embodiment of the present application further provides an application processing method, including:
step 301, receiving an update request for a target application.
Step 302, according to the update request, modifying the metadata information of the target application.
Wherein the target application may refer to an arbitrary application. When a certain application needs to be updated, a user can trigger the update of the application through the cloud management and control system. After receiving the update request, the cloud management and control system modifies the metadata information of the application and sends the modified metadata information to the controller.
And 303, generating a verification instance according to the modified metadata information of the target application.
And the controller acquires the metadata information modified by the target application from the cloud management and control system, and generates a verification example.
And step 304, verifying the verification example.
Step 305, generating an instance to be issued when the verification of the verification instance passes, wherein the instance to be issued is generated according to the verification instance;
and step 306, releasing the to-be-released example.
The specific process of steps 303 to 306 can refer to the description of steps 102 to 105.
In the embodiment of the application, after an update request for a target application is received, a verification instance is generated, and after the verification of the verification instance is passed, an instance to be issued is generated and verified according to the verification instance. Therefore, by using the scheme of the embodiment of the application, the generated to-be-issued instance can better meet the business requirement because the verification is carried out by using the verification instance before the issuance. Since the verification example is only verified in the verification process, the function verification can be performed under the condition of minimum influence on the online service, so that the application is more stable.
The embodiment of the application also provides an application processing device. Referring to fig. 4, fig. 4 is a structural diagram of an application processing apparatus according to an embodiment of the present application. As shown in fig. 4, the application processing apparatus 400 includes:
a first receiving module 401, configured to receive an update request for a target application; a first generating module 402, configured to generate a verification instance according to the update request; a first verification module 403, configured to verify the verification instance; a second generating module 404, configured to generate an instance to be published when the verification of the verification instance passes, where the instance to be published is generated according to the verification instance; and the publishing module 405 is configured to publish the to-be-published instance.
Optionally, the first generating module 402 is configured to invoke an API of kubernets to generate the verification instance according to the update request.
Optionally, the first verification module 403 includes: the operation sub-module is used for operating the verification example to obtain an operation result; the verification submodule is used for passing the verification of the verification example when the operation result meets the requirement of the target service; and when the operation result does not meet the requirement of the target service, the verification of the verification example is not passed.
Optionally, the number of the instances to be published is the same as the number of the instances that the target application has when receiving the update request.
Optionally, the publishing module 405 is configured to publish each first to-be-published instance in the to-be-published instances respectively, and close each second to-be-published instance respectively, where the second to-be-published instance is an instance, in an existing instance before the target application is updated, corresponding to the first to-be-published instance.
Optionally, the publishing module 405 is configured to publish at least two first instances to be published in the instances to be published simultaneously, and close a second instance to be published, where the second instance to be published is an instance, in an existing instance before the target application is updated, corresponding to the first instance to be published.
Optionally, the apparatus may further include: and deleting the second to-be-issued instance and/or the verification instance.
Optionally, the apparatus may further include: the first acquisition module is used for acquiring the current running information of the target application; the second obtaining module is used for obtaining the information to be updated of the target application according to the updating request; and the first determining module is used for comparing the current operation information with the information to be updated and determining whether to update the target application according to a comparison result. At this time, the first generating module is configured to generate a verification instance according to the update request when the comparison result indicates that the current operation information is different from the information to be updated.
Optionally, the apparatus may further include: and the first processing module is used for processing the service request by reusing the existing instance of the target application when the verification of the verification instance fails.
The apparatus provided in the embodiment of the present application may implement the method embodiment, and the implementation principle and the technical effect are similar, which are not described herein again.
It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented as a software functional unit and sold or used as a stand-alone product, may be stored in a processor readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
An embodiment of the present application further provides an electronic device, including: a memory, a processor and a program stored on the memory and executable on the processor, the processor implementing the steps in the application processing method as described above when executing the program.
The embodiment of the present application further provides a readable storage medium, where a program is stored on the readable storage medium, and when the program is executed by a processor, the program implements the processes of the embodiment of the application processing method, and can achieve the same technical effects, and in order to avoid repetition, the detailed description is omitted here. The readable storage medium may be any available medium or data storage device that can be accessed by a processor, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.), optical memory (e.g., CD, DVD, BD, HVD, etc.), and semiconductor memory (e.g., ROM, EPROM, EEPROM, nonvolatile memory (NAND FLASH), Solid State Disk (SSD)), etc.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. With such an understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the methods according to the embodiments of the present application.
While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (10)
1. An application processing method, comprising:
receiving an update request for a target application;
generating a verification instance according to the updating request;
verifying the verification instance;
when the verification of the verification instance passes, generating an instance to be issued, wherein the instance to be issued is generated according to the verification instance;
publishing the instance to be published;
the number of the instances to be issued is multiple; the publishing the to-be-published instance includes:
and simultaneously publishing at least two first instances to be published in the instances to be published, and closing a second instance to be published, wherein the second instance to be published is an instance corresponding to the first instance to be published in an existing instance before the target application is updated.
2. The method of claim 1, wherein the number of instances to be published is the same as the number of instances the target application has when receiving the update request.
3. The method of claim 1, further comprising:
and deleting the second to-be-issued instance and/or the verification instance.
4. The method of claim 1, wherein after said receiving an update request for a target application, the method further comprises:
acquiring current running information of the target application;
acquiring information to be updated of the target application according to the updating request;
comparing the current operation information with the information to be updated, and determining whether to update the target application according to a comparison result;
generating a verification instance according to the update request, including:
and when the comparison result shows that the current operation information is different from the information to be updated, generating a verification example according to the updating request.
5. The method of claim 1, further comprising:
and when the verification of the verification example fails, reusing the existing example of the target application to process the service request.
6. An application processing method, comprising:
receiving an update request for a target application;
modifying the metadata information of the target application according to the updating request;
generating a verification example according to the modified metadata information of the target application;
verifying the verification instance;
when the verification of the verification instance passes, generating an instance to be issued, wherein the instance to be issued is generated according to the verification instance;
publishing the instance to be published;
the number of the instances to be issued is multiple; the publishing the to-be-published instance includes:
and simultaneously publishing at least two first instances to be published in the instances to be published, and closing a second instance to be published, wherein the second instance to be published is an instance corresponding to the first instance to be published in an existing instance before the target application is updated.
7. An application processing apparatus, comprising:
the first receiving module is used for receiving an update request of a target application;
the first generation module is used for generating a verification example according to the updating request;
the first verification module is used for verifying the verification example;
the second generation module is used for generating an instance to be issued when the verification of the verification instance passes, wherein the instance to be issued is generated according to the verification instance;
the issuing module is used for issuing the example to be issued;
the number of the instances to be issued is multiple; the publishing module is configured to publish at least two first instances to be published in the instances to be published simultaneously, and close a second instance to be published, where the second instance to be published is an instance corresponding to the first instance to be published in an existing instance before the target application is updated.
8. An application processing system, comprising: a cloud management and control system and a controller;
the cloud management and control system is used for receiving an update request of a target application; modifying the metadata information of the target application according to the updating request;
the controller is used for generating a verification example according to the modified metadata information of the target application; verifying the verification instance; when the verification of the verification instance passes, generating an instance to be issued, wherein the instance to be issued is generated according to the verification instance; publishing the instance to be published;
the number of the instances to be issued is multiple; when the controller issues the instance to be issued, the controller is configured to:
and simultaneously publishing at least two first instances to be published in the instances to be published, and closing a second instance to be published, wherein the second instance to be published is an instance corresponding to the first instance to be published in an existing instance before the target application is updated.
9. An electronic device, comprising: a memory, a processor, and a program stored on the memory and executable on the processor; characterized in that the processor, configured to read a program implementation in a memory, comprises the steps of the application processing method according to any one of claims 1 to 6.
10. A readable storage medium storing a program, wherein the program, when executed by a processor, comprises the steps in the application processing method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110378514.0A CN113076248B (en) | 2021-04-08 | 2021-04-08 | Application processing method, device and equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110378514.0A CN113076248B (en) | 2021-04-08 | 2021-04-08 | Application processing method, device and equipment and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113076248A CN113076248A (en) | 2021-07-06 |
| CN113076248B true CN113076248B (en) | 2021-11-30 |
Family
ID=76615552
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110378514.0A Active CN113076248B (en) | 2021-04-08 | 2021-04-08 | Application processing method, device and equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113076248B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114265618A (en) * | 2021-11-30 | 2022-04-01 | 重庆富民银行股份有限公司 | Method for publishing and rolling back by applying one key |
| CN117453665A (en) * | 2023-10-09 | 2024-01-26 | 行吟信息科技（上海）有限公司 | Data processing method, device, equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014020773A1 (en) * | 2012-07-31 | 2014-02-06 | Nec Corporation | A modification management apparatus, a modification management method and a modification management program |
| CN105765539A (en) * | 2013-11-14 | 2016-07-13 | 微软技术许可有限责任公司 | User support experience with automatically generated virtual environment |
| CN108921551A (en) * | 2018-06-11 | 2018-11-30 | 西安纸贵互联网科技有限公司 | Alliance's block catenary system based on Kubernetes platform |
| CN110825399A (en) * | 2019-11-07 | 2020-02-21 | 郑州悉知信息科技股份有限公司 | Deployment method and device of application program |
| CN111258609A (en) * | 2020-01-19 | 2020-06-09 | 北京百度网讯科技有限公司 | Upgrading method and device of Kubernetes cluster, electronic equipment and medium |
| CN111290768A (en) * | 2020-01-22 | 2020-06-16 | 北京百度网讯科技有限公司 | Updating method, device, equipment and medium for containerization application system |
| CN112130880A (en) * | 2020-09-27 | 2020-12-25 | 平安医疗健康管理股份有限公司 | Micro-service publishing method and device, computer equipment and storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108376118B (en) * | 2018-02-09 | 2021-07-13 | 腾讯科技（深圳）有限公司 | Service distribution system, method, device 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 |
-
2021
- 2021-04-08 CN CN202110378514.0A patent/CN113076248B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014020773A1 (en) * | 2012-07-31 | 2014-02-06 | Nec Corporation | A modification management apparatus, a modification management method and a modification management program |
| CN105765539A (en) * | 2013-11-14 | 2016-07-13 | 微软技术许可有限责任公司 | User support experience with automatically generated virtual environment |
| CN108921551A (en) * | 2018-06-11 | 2018-11-30 | 西安纸贵互联网科技有限公司 | Alliance's block catenary system based on Kubernetes platform |
| CN110825399A (en) * | 2019-11-07 | 2020-02-21 | 郑州悉知信息科技股份有限公司 | Deployment method and device of application program |
| CN111258609A (en) * | 2020-01-19 | 2020-06-09 | 北京百度网讯科技有限公司 | Upgrading method and device of Kubernetes cluster, electronic equipment and medium |
| CN111290768A (en) * | 2020-01-22 | 2020-06-16 | 北京百度网讯科技有限公司 | Updating method, device, equipment and medium for containerization application system |
| CN112130880A (en) * | 2020-09-27 | 2020-12-25 | 平安医疗健康管理股份有限公司 | Micro-service publishing method and device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113076248A (en) | 2021-07-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11221838B2 (en) | Hot update method, operating system, terminal device, system, and computer-readable storage medium for a system process | |
| CN113076248B (en) | Application processing method, device and equipment and readable storage medium | |
| CN110995473A (en) | Service node control method and related equipment | |
| CN110532025B (en) | Data processing method, device and equipment based on micro-service architecture and storage medium | |
| CN111143023A (en) | Resource changing method and device, equipment and storage medium | |
| CN112947945B (en) | Multi-type application release method and device, computer equipment and storage medium | |
| US11489844B2 (en) | On-the-fly creation of transient least privileged roles for serverless functions | |
| CN111581077A (en) | Intelligent contract testing method and device | |
| CN114006815B (en) | Automatic deployment method and device for cloud platform nodes, nodes and storage medium | |
| CN113946854A (en) | File access control method and device and computer readable storage medium | |
| WO2021013185A1 (en) | Virtual machine migration processing and strategy generation method, apparatus and device, and storage medium | |
| CN111447178B (en) | Access control method, system and computing device | |
| CN110716730B (en) | Gray release method, device, equipment and computer readable storage medium | |
| CN111712795A (en) | Method, apparatus, computer program product and readable medium for evaluating application deployment | |
| CN112650689A (en) | Test method, test device, electronic equipment and storage medium | |
| CN113741924A (en) | Application deployment method, system and server | |
| CN115174158B (en) | Cloud product configuration checking method based on multi-cloud management platform | |
| CN115576626A (en) | Method, device and storage medium for safe mounting and dismounting of USB (Universal Serial bus) device | |
| CN114443102A (en) | Gray level switching method and device for transaction upgrading | |
| US20220376992A1 (en) | Network Function Management | |
| JP2008090485A (en) | Job management device, system and program | |
| CN113391921A (en) | Resource quota checking method for application example | |
| CN114968505A (en) | Task processing system, method, device, apparatus, storage medium, and program product | |
| CN110874238A (en) | Online service updating method and device | |
| CN110738515A (en) | Resource delivery data monitoring method and device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| OL01 | Intention to license declared |