CN117724740A - Automatic application deployment method, device, equipment and storage medium - Google Patents
Automatic application deployment method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN117724740A CN117724740A CN202311733673.3A CN202311733673A CN117724740A CN 117724740 A CN117724740 A CN 117724740A CN 202311733673 A CN202311733673 A CN 202311733673A CN 117724740 A CN117724740 A CN 117724740A
- Authority
- CN
- China
- Prior art keywords
- application
- application component
- upgrading
- deployment
- time
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 96
- 230000008569 process Effects 0.000 claims description 35
- 238000012545 processing Methods 0.000 claims description 26
- 230000002159 abnormal effect Effects 0.000 claims description 14
- 238000012163 sequencing technique Methods 0.000 claims description 5
- 230000000694 effects Effects 0.000 abstract description 5
- 238000004519 manufacturing process Methods 0.000 abstract description 5
- 238000010586 diagram Methods 0.000 description 6
- 230000004044 response Effects 0.000 description 6
- 230000000007 visual effect Effects 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 238000004590 computer program Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 125000004122 cyclic group Chemical group 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Stored Programmes (AREA)
Abstract
The application provides an automatic application deployment method, device, equipment and storage medium, wherein the method comprises the following steps: scanning a deployment plan according to a preset period, wherein the deployment plan comprises a version upgrading plan of a plurality of different application components, and the version upgrading plan of each application component comprises a version number and upgrading time, wherein the upgrading time of the different application components is different; judging whether the current time meets the upgrading time of any application component, if so, controlling the application component to be upgraded according to the version number of the application component; if the version of the application component does not meet the requirement, continuing to scan the deployment plan according to the preset period until the version upgrading of the application component in the deployment plan is completed. The method realizes the automatic execution of the deployment plan application, avoids the intervention of production deployment personnel, and improves the technical effect of the high efficiency of the automatic deployment of the application.
Description
Technical Field
The present disclosure relates to communication technologies, and in particular, to an automatic application deployment method, apparatus, device, and storage medium.
Background
As multiple upgrades of enterprise systems and industry application components evolve, the need for frequent deployment of heterogeneous systems becomes more pronounced.
This situation places higher demands on production deployments who need to continually upgrade versions of different applications, especially in the context of large-scale application upgrades, frequent human intervention becomes a tedious and time-consuming task. To solve this problem, implementing the automatic deployment capability of applications is urgent and significant.
Disclosure of Invention
The application provides an automatic application deployment method, device, equipment and storage medium, which are used for solving the problem that manual intervention is required continuously and automatic application deployment cannot be realized when large-scale application upgrading is handled in the prior art.
In a first aspect, the present application provides an automatic application deployment method, including:
scanning a deployment plan according to a preset period, wherein the deployment plan comprises a version upgrading plan of a plurality of different application components, and the version upgrading plan of each application component comprises a version number and upgrading time, wherein the upgrading time of the different application components is different;
judging whether the current time meets the upgrading time of any application component or not;
if yes, controlling the application component to be upgraded according to the version number of the application component;
if not, continuing to scan the deployment plan according to a preset period until all the application components in the deployment plan finish version upgrading.
Optionally, before the scanning the deployment plan according to the preset period, the method further includes:
responding to the operation of a user on a deployment plan page, displaying the deployment plan page, wherein a plurality of configuration fields and attribute frames corresponding to each configuration field are arranged in the deployment plan page, the attribute frames are used for configuring the attributes corresponding to the configuration fields, and the plurality of configuration fields comprise application component identifiers, version numbers and upgrading time;
and after the configuration of the attribute frame is completed, responding to the configuration completion operation of a user, and generating the deployment plan.
Optionally, the generating the deployment plan includes:
judging whether the plurality of application components can be upgraded sequentially according to the upgrading time of each application component;
if yes, generating the deployment plan;
if not, prompting the user to rearrange the upgrading time of each application component until the plurality of application components can be upgraded in sequence, and generating the deployment plan.
Optionally, the determining whether the current time meets the upgrade time of any application component includes:
sequencing upgrading time of a plurality of different application components according to time sequence;
judging whether the current time meets the upgrading time of the current first order or not;
if yes, controlling the application component to be upgraded according to the version number of the application component;
if not, continuing to scan the deployment plan according to a preset period.
Optionally, after the controlling the application component to upgrade, the method further includes:
after the application component is upgraded, continuously judging whether the new current time meets the new first-ordered upgrading time or not;
if yes, continuing to upgrade the new application component until the current time does not meet the upgrade time of the current first order;
if not, continuing to scan the deployment plan according to a preset period.
Optionally, before controlling the application component to upgrade according to the version number of the application component, the method further includes:
judging whether the application component is currently in a service processing state or not;
if yes, generating log information after the current business processing of the application component is completed, wherein the log information is used for indicating the application component to start upgrading;
if not, generating log information, wherein the log information is used for indicating the application component to start upgrading.
Optionally, after controlling the application component to upgrade according to the version number of the application component, the method further includes:
acquiring an execution log and judging the state of the log, wherein the execution log is generated in the upgrading process of the application component;
if the execution log is abnormal, recording the upgrading state of the application component as an abnormal state, and ending the upgrading process;
if the execution log is normal, recording the upgrading state of the application component as a normal state, and continuing the upgrading process.
In a second aspect, the present application provides an application automatic deployment apparatus, including:
the system comprises a scanning module, a deployment module and a control module, wherein the scanning module is used for scanning a deployment plan according to a preset period, the deployment plan comprises a version upgrading plan of a plurality of different application components, the version upgrading plan of each application component comprises a version number and upgrading time, and the upgrading time of the different application components is different;
the judging module is used for judging whether the current time meets the upgrading time of any application component or not;
the control module is used for controlling the application component to be upgraded according to the version number of the application component if the version number is met;
and the scanning module is specifically used for continuously scanning the deployment plan according to a preset period if the version of the application component in the deployment plan is not satisfied, until the version upgrading of the application component in the deployment plan is completed.
Optionally, the scanning module is specifically configured to:
responding to the operation of a user on a deployment plan page, displaying the deployment plan page, wherein a plurality of configuration fields and attribute frames corresponding to each configuration field are arranged in the deployment plan page, the attribute frames are used for configuring the attributes corresponding to the configuration fields, and the plurality of configuration fields comprise application component identifiers, version numbers and upgrading time;
and after the configuration of the attribute frame is completed, responding to the configuration completion operation of a user, and generating the deployment plan.
Optionally, the scanning module is further configured to:
judging whether the plurality of application components can be upgraded sequentially according to the upgrading time of each application component;
if yes, generating the deployment plan;
if not, prompting the user to rearrange the upgrading time of each application component until the plurality of application components can be upgraded in sequence, and generating the deployment plan.
Optionally, the judging module is specifically configured to:
sequencing upgrading time of a plurality of different application components according to time sequence;
judging whether the current time meets the upgrading time of the current first order or not;
if yes, controlling the application component to be upgraded according to the version number of the application component;
if not, continuing to scan the deployment plan according to a preset period.
Optionally, the control module is specifically configured to:
after the application component is upgraded, continuously judging whether the new current time meets the new first-ordered upgrading time or not;
if yes, continuing to upgrade the new application component until the current time does not meet the upgrade time of the current first order;
if not, continuing to scan the deployment plan according to a preset period.
Optionally, the control module is further configured to:
judging whether the application component is currently in a service processing state or not;
if yes, generating log information after the current business processing of the application component is completed, wherein the log information is used for indicating the application component to start upgrading;
if not, generating log information, wherein the log information is used for indicating the application component to start upgrading.
Optionally, the control module is further configured to:
acquiring an execution log and judging the state of the log, wherein the execution log is generated in the upgrading process of the application component;
if the execution log is abnormal, recording the upgrading state of the application component as an abnormal state, and ending the upgrading process;
if the execution log is normal, recording the upgrading state of the application component as a normal state, and continuing the upgrading process.
In a third aspect, the present application provides an electronic device, comprising: a processor, a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored in the memory to implement the various alternative methods of automatic application deployment as in the first aspect.
In a fourth aspect, the present application provides a computer-readable storage medium comprising computer-executable instructions that, when executed by a processor, perform the various alternative methods of automatic application deployment as in the first aspect.
In a fifth aspect, the present application provides a program product comprising a computer program for execution by a processor to implement the various alternative automatic application deployment methods of the first aspect.
According to the automatic application deployment method, device, equipment and storage medium, whether the current time meets the upgrading time of any application component in the deployment plan is judged by scanning the deployment plan according to the preset period, and if the upgrading time is met, the application component is controlled to be upgraded according to the version number of the application component; if the version upgrading is not satisfied, the version upgrading of all the application components is circularly scanned until the version upgrading of the timed application components is completed, the version upgrading is ensured to be completed within a specified time, the safety and the stability of a maintenance system are facilitated, the upgrading time of the application components is judged in real time, the need of manual intervention is avoided, the timeliness and the accuracy of the upgrading are improved, and the effect of high-efficiency and controllable automatic application deployment is realized.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.
Fig. 1 is a block diagram of an automatic application deployment method according to an embodiment of the present application;
FIG. 2 is a flowchart of an automatic application deployment method according to an embodiment of the present application;
FIG. 3 is a second flowchart of an automatic application deployment method according to an embodiment of the present disclosure;
fig. 4 is a flowchart III of an automatic application deployment method provided in an embodiment of the present application;
fig. 5 is a flowchart of an automatic application deployment method provided in an embodiment of the present application;
fig. 6 is a schematic diagram of an application automatic deployment device provided in an embodiment of the present application;
fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Specific embodiments thereof have been shown by way of example in the drawings and will herein be described in more detail. These drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.
Enterprise systems and industry application components, after multiple upgrades evolve, have features that heterogeneous systems are frequently deployed. Version upgrades of different applications are required, and a scene facing large-scale application upgrades generally consumes larger manpower and time, so that the realization of the automatic deployment capability of the applications becomes urgent and has important significance, the deployment efficiency can be improved, errors can be reduced, and the production environment can be more rapidly adapted to system upgrades and industry changes.
In the prior art, frequent manual intervention is needed to realize large-scale application upgrading, but the manual intervention not only makes the deployment process complex and easy to make mistakes, but also can cause longer downtime of the production environment and influence the continuity of the service.
Based on the above, the application automatic deployment method, device, equipment and storage medium are provided, by automatically scanning a deployment plan, carrying out matching judgment on the current time according to the upgrading time of each application component in the deployment plan, upgrading the application components meeting the upgrading time according to the time sequence, carrying out cyclic scanning on the deployment plan not meeting the upgrading time until the deployment plan is completed, generating log information for different execution processes, upgrading each application component according to the deployment plan, reducing human intervention, improving the stability of a system, and helping a user to know the process of planning execution by generating the log information, and helping the user to track and diagnose problems when errors occur in the automatic deployment process.
The following describes the technical solutions of the present application and how the technical solutions of the present application solve the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
Fig. 1 is a block diagram of an automatic application deployment method according to an embodiment of the present application. As shown in fig. 1, includes:
a visual interface layer, a logic processing layer and an application response layer.
In this embodiment, the visual interface layer graphically displays information and functions of the system to a user to provide an intuitive user interaction interface, which is a key component in the automatic deployment method, and simplifies configuration and management deployment plans by providing an intuitive interface for the user. The user sets the application component identification, version number and upgrading time in the deployment plan according to the attribute frames corresponding to the different configuration fields in the interface to generate the deployment plan, provides a basis for the execution of the automatic deployment of the subsequent application,
the logic processing layer is used for processing logic, business rules and flow control in the application program, is responsible for explaining configuration performed by a user of the visual interface layer in automatic application deployment, converts parameters and a plan set by the user through the visual interface into instructions which can be understood and executed by a system, coordinates the execution flow of the deployment plan, processes abnormal conditions possibly occurring in the upgrading process, and judges whether an application component is in a business processing state.
The application response layer refers to a module responsible for executing actual business logic in automatic application deployment and generates corresponding response. After the application receives the deployment signal, the service processing state is judged, and the user is informed by generating log information according to the processing state, so that the automatic deployment of the application is ensured, and the operator is ensured to obtain log feedback.
According to the application automatic deployment method, visual deployment plan pages are provided for users through the visual interface layer, learning cost of the users is reduced, operation understandability is improved, manual intervention requirements are reduced by the logic processing layer, deployment accuracy and reliability are improved, version upgrading of the application is automatically executed by the application response layer according to instructions of the logic processing layer, correct deployment of the application is ensured, the whole application automatic deployment is modularized due to the arrangement of three layers, flexible modification and expansion are achieved due to independence among layers, maintenance and upgrading are facilitated, and high efficiency of the application automatic deployment is improved.
Fig. 2 is a flowchart one of an automatic application deployment method according to an embodiment of the present application. As shown in fig. 2, the method includes:
s101, scanning a deployment plan according to a preset period, wherein the deployment plan comprises version upgrade plans of a plurality of different application components, and the version upgrade plan of each application component comprises a version number and upgrade time, wherein the upgrade time of the different application components is different;
deployment plans refer to detailed plans and policies formulated for effectively facilitating deployment of applications or systems in application management, including, but not limited to, application component identification, version number, and upgrade time.
The upgrade time refers to the time for executing upgrade operation on the corresponding plan in the automatic deployment process of the application.
In this embodiment, the system scans the deployment plan according to a scanning period set in advance, and obtains different attribute settings in the deployment plan.
S102, judging whether the current time meets the upgrading time of any application component;
in this embodiment, the system determines, according to matching between the upgrade time of different application components in the scanned deployment plan and the current time, whether the current time meets the upgrade time of any application component in the deployment plan.
S103, if the version number of the application component is met, the application component is controlled to be upgraded;
in this embodiment, when the current time is matched with the upgrade time of an application component in the deployment plan, the application component is automatically controlled to be upgraded according to the scanned version number corresponding to the application component, so as to complete automatic deployment of the application component.
And S104, if the version of the application component does not meet the requirement, continuing to scan the deployment plan according to the preset period until the version of the application component in the deployment plan is upgraded.
In this embodiment, if the current time is not matched with the upgrade time of any application component in the deployment plan, the system continues to scan the deployment plan according to the preset period until the current time is matched with the upgrade time of all application components in the deployment plan, and the version upgrade of all application components in the deployment plan is completed.
According to the application automatic deployment method, device, equipment and storage medium, whether the current time meets the upgrading time of any application component is judged by scanning a deployment plan according to a preset period, and if yes, the application component is controlled to be upgraded according to the version number of the application component; if the version of the application component does not meet the requirement, continuing to scan the deployment plan according to the preset period until the version upgrading of the application component in the deployment plan is completed. The method realizes the automatic execution of the deployment plan application, avoids the intervention of production deployment personnel, and improves the technical effect of the high efficiency of the automatic deployment of the application.
Fig. 3 is a second flowchart of an automatic application deployment method according to an embodiment of the present application. As shown in fig. 3, the present embodiment describes in detail a deployment plan generation process, and the method includes:
s201, responding to operation of a user on a deployment plan page, displaying the deployment plan page, and setting a plurality of configuration fields and attribute frames corresponding to each configuration field in the deployment plan page, wherein the attribute frames are used for configuring attributes corresponding to the configuration fields, and the plurality of configuration fields comprise application component identifiers, version numbers and upgrading time;
in this embodiment, the deployment plan page is used for setting different attributes of the deployment plan, where the deployment plan page has a plurality of configuration fields and corresponding attribute frames, where the configuration fields correspond to the deployment plan attributes, the attribute frames are used for inputting contents of specific configuration fields, for example, "upgrade time" corresponds to the configuration fields, and contents input in the attribute frames may be "2023.12.13.10:00:00", etc.
In this embodiment, after a user clicks a deployment plan setting operation on a page, the system displays a deployment plan page, where the page includes an application component identifier, a version number, an upgrade time field, and a corresponding attribute frame, and the user may perform attribute configuration of the deployment plan by using attribute frames corresponding to different configuration fields according to service requirements.
S202, after the configuration of the attribute frame is completed, generating a deployment plan in response to the configuration completion operation of the user.
Judging whether the plurality of application components can be upgraded sequentially according to the upgrading time of each application component;
if yes, generating a deployment plan;
if not, prompting the user to rearrange the upgrading time of each application component until a plurality of application components can be upgraded in sequence, and generating a deployment plan.
In this embodiment, after the user completes the configuration of the attribute frame, the system sequentially determines according to the upgrade time of each application component, so that each application component can be upgraded in a planned manner, and simultaneous upgrade is avoided, and mutual influence is avoided. If the upgrade can be sequentially performed in sequence, generating a deployment plan; otherwise, prompting the user to rearrange the upgrade time until the plurality of application components can be upgraded in sequence, and finally generating a deployment plan by the system through the configuration of the user and the judgment of the system.
According to the automatic application deployment method, device, equipment and storage medium, a user configures upgrading information of application components through a plurality of attribute frames of a deployment plan page, and a system responds to the configuration of the user and judges whether the plurality of application components can be sequentially upgraded according to upgrading time; if the upgrade schedule of the application components is reasonable, the system generates a deployment plan on the fly. Otherwise, if time conflict or unreasonable arrangement exists, the system prompts the user to rearrange the upgrade time, flexibly adjusts the upgrade plan according to actual conditions, adapts to different business requirements and constraint conditions, improves the flexibility of the system, is beneficial to maintaining the stability of the system, prevents problems caused by dependency relationship among components, and finally generates a deployment plan through the configuration of the user and the judgment of the system, thereby simplifying the generation flow of the deployment plan, reducing manual intervention and improving the efficiency and accuracy.
Fig. 4 is a flowchart III of an automatic deployment method for applications according to an embodiment of the present application. As shown in fig. 4, the present embodiment describes in detail a process of determining an upgrade time of an application component in a deployment plan, where the method includes:
s301, scanning a deployment plan according to a preset period;
s302, sorting upgrading time of a plurality of different application components according to time sequence;
in this embodiment, the system sorts the upgrade times of the plurality of application components according to the scanned upgrade times of all application components in the deployment plan, so as to ensure that the application components are upgraded according to the sequence of the upgrade times. For example, before the upgrade time of the application component 1 is 12.13.12:05:00, before the upgrade time of the application component 2 is 12.13.12:08:00, and before the upgrade time of the application component 3 is 12.13.11:05:00, the upgrade orders of the three application components are: an application component 3, an application component 1, an application component 2.
S303, judging whether the current time meets the upgrading time of the current first order;
in this embodiment, the system determines, according to the upgrade order obtained by ordering the plurality of application components, whether the current time matches with the upgrade time of the first order in the upgrade order.
S304, if not, continuing to scan the deployment plan according to a preset period;
in this embodiment, the system determines, according to the upgrade order obtained by sorting the plurality of application components, that the current time does not match with the upgrade time of the first sort in the upgrade order, and then continues scanning the deployment plan according to the set period. Continuing with the example of S302, if the current time is 12.13.12:06:00, the system will scan the deployment plan again according to the preset period, without matching the upgrade time of the first ranked application component 3.
S305, if yes, controlling the application component to upgrade according to the version number of the application component;
in this embodiment, the system determines, according to the upgrade order obtained by ordering the plurality of application components, that the current time matches with the upgrade time of the first order in the upgrade order, and then automatically controls the application components to upgrade according to the version numbers corresponding to the application components. Continuing with the example of S302, if the current time is 12.13.11:04:00, the system controls the application components to upgrade according to the version numbers of the application components, and the current time matches the upgrade time of the application components 3 ordered first.
S306, after the application component is upgraded, continuously judging whether the new current time meets the new first-order upgrading time;
in this embodiment, after finishing upgrading an application component, whether the upgrading time of the application component is matched with the upgrading time of the application component in the first order is continuously determined according to the current time.
S307, if yes, continuing to upgrade the new application component until the current time does not meet the upgrade time of the current first order;
in this embodiment, if the system determines that the current time matches the upgrade time of the first order in the current upgrade order, the system continues to automatically control the application component to upgrade according to the version number corresponding to the application component until the current time does not meet the upgrade time of the current first order. Continuing with the example of S302, if the current time is 12.13.12:04:00, the system controls the application component to upgrade according to the version number of the application component, and the current time is matched with the upgrade time of the application component 1 with the first order.
And S308, if the deployment plan is not satisfied, continuing to scan the deployment plan according to a preset period.
In this embodiment, if the system determines that the current time does not match the upgrade time of the first order in the current upgrade order, the system continues to scan the deployment plan according to the set period. Continuing with the example of S302, if the current time is 12.13.12:09:00, the system will scan the deployment plan again according to the preset period, if the current time is not matched with the upgrade time of the first application component 1.
According to the application automatic deployment method, device, equipment and storage medium, the upgrade time of a plurality of application components is sequenced according to the preset period scanning deployment plan, whether upgrade conditions are met or not is judged according to the time sequence, so that automatic upgrade is achieved, component application upgrade is guaranteed to be carried out within set time, timeliness of upgrade is improved, the application components are guaranteed to be upgraded according to the set time sequence through sequencing and real-time judgment of the upgrade time, possible conflict and error in the upgrade process are prevented, and the system can flexibly adapt to different upgrade requirements through continuous upgrade and periodic scanning, and continuity and stability of the system are guaranteed.
Fig. 5 is a flowchart of an automatic application deployment method according to an embodiment of the present application. As shown in fig. 5, the present embodiment describes in detail a process of controlling the log generation before and after the upgrade of the application component according to the version number of the application component, and the method includes:
s401, the current time meets the upgrading time of the application component;
in this embodiment, the current time matches the upgrade time of a certain application component in the deployment plan.
S402, judging whether an application component is currently in a service processing state;
in this embodiment, the system checks whether the application component is executing business processes.
S403, if yes, generating log information after the current business processing of the application component is completed, wherein the log information is used for starting upgrading of the application component;
the log information refers to records generated by the system in the process of upgrading the application and is used for tracking and monitoring the activity of the system. These records contain various events of the system, upgrade information, state changes and the like,
in this embodiment, the system checks that the application component is in a service processing state, and the system needs to wait for the service processing to be completed and then upgrade, and generates corresponding log information to mark that the application component can start to upgrade.
S404, if not, generating log information, wherein the log information is used for indicating the application component to start upgrading;
in this embodiment, if the system determines that the application component is not in the service processing state, log information is directly generated, and the application component is marked for starting upgrading.
S405, controlling the application component to upgrade according to the version number of the application component;
s406, acquiring an execution log, and judging the state of the log, wherein the execution log is generated in the upgrading process of the application component;
the execution log refers to records generated during an application upgrade process for recording various operations, state changes, and possible errors or anomalies of the system.
In this embodiment, after the application component is upgraded, the system acquires an execution log, and determines whether the execution log has a state abnormality.
S407, if the execution log is abnormal, recording the upgrading state of the application component as an abnormal state, and ending the upgrading process;
in this embodiment, when it is checked that an abnormal situation occurs in the application component during the upgrade process in the execution log acquired by the system, the upgrade state of the application component is recorded as an abnormal state, and the subsequent upgrade procedure of the deployment plan is ended
S408, if the execution log is normal, recording the upgrading state of the application component as a normal state, and continuing the upgrading process.
In this embodiment, when it is checked in the execution log obtained by the system that no abnormal condition occurs in the upgrading process of the application component, the upgrading state of the application component is recorded as a normal state, and the next application component with the first order is continuously upgraded until all application components complete the upgrading process.
According to the application automatic deployment method, device, equipment and storage medium, log information is correspondingly generated by whether the application component is in a service processing state or not before upgrading; after the application component is upgraded, an execution log is obtained, and the upgrading state of the application component is judged, so that the upgrade is performed after the business processing is finished, and the business interference is avoided; by generating and acquiring the execution log, detailed records of the upgrading process are provided, so that problems can be detected, the upgrading state can be tracked, and maintainability and stability of the system are improved.
Fig. 6 is a schematic diagram of an application automatic deployment device provided in an embodiment of the present application; as shown in fig. 6, the apparatus includes:
the scanning module 501 is configured to scan a deployment plan according to a preset period, where the deployment plan includes version upgrade plans of a plurality of different application components, and each version upgrade plan of an application component includes a version number and upgrade time, where the upgrade times of the different application components are different;
a judging module 502, configured to judge whether the current time meets an upgrade time of any application component;
a control module 503, configured to control the application component to upgrade according to the version number of the application component if the version number is satisfied;
the scanning module 501 is specifically configured to, if the version update is not satisfied, continue to scan the deployment plan according to the preset period until all the application components in the deployment plan complete the version update.
In one possible implementation, the scanning module 501 is specifically configured to:
responding to the operation of a user on a deployment plan page, displaying the deployment plan page, and setting a plurality of configuration fields and attribute frames corresponding to each configuration field in the deployment plan page, wherein the attribute frames are used for configuring attributes corresponding to different configuration fields, and the plurality of configuration fields comprise application component identifiers, version numbers and upgrading time;
after the configuration of the attribute frame is completed, generating a deployment plan in response to the configuration completion operation of the user.
In a possible implementation, the scanning module 501 is further configured to:
judging whether the plurality of application components can be upgraded sequentially according to the upgrading time of each application component;
if yes, generating a deployment plan;
if not, prompting the user to rearrange the upgrading time of each application component until a plurality of application components can be upgraded in sequence, and generating a deployment plan.
In one possible implementation manner, the judging module 502 is specifically configured to:
sequencing upgrading time of a plurality of different application components according to time sequence;
judging whether the current time meets the upgrading time of the current first order or not;
if yes, the application component is controlled to be upgraded according to the version number of the application component;
if not, continuing to scan the deployment plan according to the preset period.
In a possible implementation manner, the control module 503 is specifically configured to:
after the application component is upgraded, continuously judging whether the new current time meets the new first-ordered upgrading time;
if yes, continuing to upgrade the new application component until the current time does not meet the upgrade time of the current first order;
if not, continuing to scan the deployment plan according to the preset period.
In a possible implementation, the control module 503 is further configured to:
judging whether the application component is in a service processing state currently or not;
if yes, generating log information after the current business processing of the application component is completed, wherein the log information is used for indicating the application component to start upgrading;
if not, generating log information, wherein the log information is used for indicating the application component to start upgrading.
In a possible implementation, the control module 503 is further configured to:
acquiring an execution log, and judging the state of the log, wherein the execution log is generated by an application component in the upgrading process;
if the execution log is abnormal, recording the upgrading state of the application component as an abnormal state, and ending the upgrading process;
if the execution log is normal, recording the upgrading state of the application component as a normal state, and continuing the upgrading process.
Fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present invention. As shown in fig. 7, the electronic device 60 provided in this embodiment includes: at least one processor 601 and a memory 602. The device 60 further comprises a communication component 603. The processor 601, the memory 602, and the communication section 603 are connected via a bus 604.
In a specific implementation, the at least one processor 601 executes computer-executable instructions stored in the memory 602, so that the at least one processor 601 executes the application automatic deployment method described above.
The specific implementation process of the processor 601 may refer to the above-mentioned method embodiment, and its implementation principle and technical effects are similar, and this embodiment will not be described herein again.
In the embodiment shown in fig. 7, it should be understood that the processor may be a central processing unit (english: central Processing Unit, abbreviated as CPU), or may be other general purpose processors, digital signal processors (english: digital Signal Processor, abbreviated as DSP), application specific integrated circuits (english: application Specific Integrated Circuit, abbreviated as ASIC), or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present invention may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in a processor for execution.
The Memory may comprise high-speed Memory (Random Access Memory, RAM) or may further comprise Non-volatile Memory (NVM), such as at least one disk Memory.
The bus may be an industry standard architecture (Industry Standard Architecture, ISA) bus, an external device interconnect (Peripheral Component, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, the buses in the drawings of the present application are not limited to only one bus or one type of bus.
The present application also provides a computer program product comprising a computer program which, when executed by a processor, implements the above-described method of automatic application deployment.
The application also provides a computer readable storage medium, wherein the computer readable storage medium stores computer execution instructions, and when a processor executes the computer execution instructions, the automatic application deployment method is realized.
The above-described readable storage medium may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk. A readable storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.
An exemplary readable storage medium is coupled to the processor such the processor can read information from, and write information to, the readable storage medium. In the alternative, the readable storage medium may be integral to the processor. The processor and the readable storage medium may reside in an application specific integrated circuit (Application Specific Integrated Circuits, ASIC for short). The processor and the readable storage medium may reside as discrete components in a device.
The division of units is merely a logical function division, and there may be another division manner in actual implementation, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method of the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the method embodiments described above may be performed by hardware associated with program instructions. The foregoing program may be stored in a computer readable storage medium. The program, when executed, performs steps including the method embodiments described above; and the aforementioned storage medium includes: various media that can store program code, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any adaptations, uses, or adaptations of the invention following, in general, the principles of the invention and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains and as may be applied to the precise construction hereinbefore set forth and shown in the drawings and as follows in the scope of the appended claims. The scope of the invention is limited only by the appended claims.
Claims (10)
1. An application automatic deployment method, comprising:
scanning a deployment plan according to a preset period, wherein the deployment plan comprises a version upgrading plan of a plurality of different application components, and the version upgrading plan of each application component comprises a version number and upgrading time, wherein the upgrading time of the different application components is different;
judging whether the current time meets the upgrading time of any application component or not;
if yes, controlling the application component to be upgraded according to the version number of the application component;
if not, continuing to scan the deployment plan according to a preset period until all the application components in the deployment plan finish version upgrading.
2. The method of claim 1, wherein prior to scanning the deployment plan in accordance with the preset period, the method further comprises:
responding to the operation of a user on a deployment plan page, displaying the deployment plan page, wherein a plurality of configuration fields and attribute frames corresponding to each configuration field are arranged in the deployment plan page, the attribute frames are used for configuring the attributes corresponding to the configuration fields, and the plurality of configuration fields comprise application component identifiers, version numbers and upgrading time;
and after the configuration of the attribute frame is completed, responding to the configuration completion operation of a user, and generating the deployment plan.
3. The method of claim 2, wherein the generating the deployment plan comprises:
judging whether the plurality of application components can be upgraded sequentially according to the upgrading time of each application component;
if yes, generating the deployment plan;
if not, prompting the user to rearrange the upgrading time of each application component until the plurality of application components can be upgraded in sequence, and generating the deployment plan.
4. The method of claim 1, wherein the determining whether the current time satisfies an upgrade time of any application component comprises:
sequencing upgrading time of a plurality of different application components according to time sequence;
judging whether the current time meets the upgrading time of the current first order or not;
if yes, controlling the application component to be upgraded according to the version number of the application component;
if not, continuing to scan the deployment plan according to a preset period.
5. The method of claim 4, wherein after said controlling the application component to upgrade, the method further comprises:
after the application component is upgraded, continuously judging whether the new current time meets the new first-ordered upgrading time or not;
if yes, continuing to upgrade the new application component until the current time does not meet the upgrade time of the current first order;
if not, continuing to scan the deployment plan according to a preset period.
6. The method of claim 1, wherein the method further comprises, prior to controlling the application component for upgrade based on the version number of the application component:
judging whether the application component is currently in a service processing state or not;
if yes, generating log information after the current business processing of the application component is completed, wherein the log information is used for indicating the application component to start upgrading;
if not, generating log information, wherein the log information is used for indicating the application component to start upgrading.
7. The method of claim 1, wherein after controlling the application component for upgrading according to the version number of the application component, the method further comprises:
acquiring an execution log and judging the state of the log, wherein the execution log is generated in the upgrading process of the application component;
if the execution log is abnormal, recording the upgrading state of the application component as an abnormal state, and ending the upgrading process;
if the execution log is normal, recording the upgrading state of the application component as a normal state, and continuing the upgrading process.
8. An application automatic deployment apparatus comprising:
the system comprises a scanning module, a deployment module and a control module, wherein the scanning module is used for scanning a deployment plan according to a preset period, the deployment plan comprises a version upgrading plan of a plurality of different application components, the version upgrading plan of each application component comprises a version number and upgrading time, and the upgrading time of the different application components is different;
the judging module is used for judging whether the current time meets the upgrading time of any application component or not;
the control module is used for controlling the application component to be upgraded according to the version number of the application component if the version number is met;
and the scanning module is specifically used for continuously scanning the deployment plan according to a preset period if the version of the application component in the deployment plan is not satisfied, until the version upgrading of the application component in the deployment plan is completed.
9. An electronic device, comprising: a processor, and a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored in the memory to implement the automatic application deployment method of any one of claims 1 to 7.
10. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are for implementing the application automatic deployment method according to any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311733673.3A CN117724740A (en) | 2023-12-15 | 2023-12-15 | Automatic application deployment method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311733673.3A CN117724740A (en) | 2023-12-15 | 2023-12-15 | Automatic application deployment method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117724740A true CN117724740A (en) | 2024-03-19 |
Family
ID=90201019
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311733673.3A Pending CN117724740A (en) | 2023-12-15 | 2023-12-15 | Automatic application deployment method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117724740A (en) |
-
2023
- 2023-12-15 CN CN202311733673.3A patent/CN117724740A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10338550B2 (en) | Multisite version and upgrade management system | |
| US10756974B2 (en) | Launch multiple devices firmware update operation from another application with device list context | |
| US9152413B2 (en) | Bi-directional communication between change management tool and implementation tools | |
| CN105373428B (en) | Task scheduling method and system | |
| CN102622247B (en) | The BIOS information configuration-system of server and method | |
| EP1351108B1 (en) | Method and apparatus for programming | |
| CN106502226A (en) | Software deployment manager integration in Process Control System | |
| CN103365262A (en) | Apparatus and method for determining operation compatibility between field devices | |
| JP2008282363A (en) | Programmable controller, program creation support device, computer program and programmable logic controller (plc) system | |
| US20080255872A1 (en) | Powertag: Manufacturing And Support System Method And Apparatus For Multi-Computer Solutions | |
| CN111815099A (en) | Assembly line production management method and system | |
| CN111930354B (en) | Framework component system for software development and construction method thereof | |
| CN109558191A (en) | A kind of method, apparatus, storage medium and computer equipment configuring the page | |
| CN113706022A (en) | Business process execution method and device, storage medium and electronic equipment | |
| CN115860451A (en) | Flow operation method and device, electronic equipment and storage medium | |
| CN113176996A (en) | Fault processing method, engine, plug-in probe, device and readable storage medium | |
| US8151189B2 (en) | Computer-implemented systems and methods for an automated application interface | |
| CN117724740A (en) | Automatic application deployment method, device, equipment and storage medium | |
| JPH10301799A (en) | System for applying test program | |
| CN116431277A (en) | Multi-place operation and maintenance containerization method and device, computer equipment and storage medium | |
| CN115454472A (en) | Remote upgrading problem solving method, device, equipment and readable storage medium | |
| CN114237634A (en) | Application release risk identification method, device, equipment, medium and program product | |
| Cisco | Software Management | |
| Cisco | Software Management | |
| CN113656088A (en) | Self-service management method and device for Internet data center server 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 |