CN113849206A - Application service publishing method and device, electronic equipment and storage medium - Google Patents
Application service publishing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN113849206A CN113849206A CN202110975304.XA CN202110975304A CN113849206A CN 113849206 A CN113849206 A CN 113849206A CN 202110975304 A CN202110975304 A CN 202110975304A CN 113849206 A CN113849206 A CN 113849206A
- Authority
- CN
- China
- Prior art keywords
- application service
- target
- target application
- server
- service
- 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 61
- 238000003860 storage Methods 0.000 title claims abstract description 15
- 238000004806 packaging method and process Methods 0.000 claims abstract description 5
- 238000012544 monitoring process Methods 0.000 claims description 27
- 230000008569 process Effects 0.000 claims description 16
- 238000004590 computer program Methods 0.000 claims description 4
- 238000009826 distribution Methods 0.000 description 10
- 238000010586 diagram Methods 0.000 description 8
- 230000009471 action Effects 0.000 description 6
- 230000004044 response Effects 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000007792 addition Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 238000005096 rolling process Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5083—Techniques for rebalancing the load in a distributed system
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a method and a device for issuing application services, electronic equipment and a storage medium, wherein the method for issuing the application services comprises the following steps: acquiring a release parameter of a target application service; wherein the publishing parameter comprises at least an up-to-date code ID of the target application service; pulling a code program corresponding to the latest code ID of the target application service and packaging to obtain a current program package of the target application service; sequentially aiming at each target server, replacing the current program package of the target application service with the old program package of the target application service in the target server according to the IP of the target server in a configuration file, and starting the target application service; and the target server is the server where the target application is located.
Description
Technical Field
The present application relates to the field of application publishing technologies, and in particular, to a method and an apparatus for publishing an application service, an electronic device, and a storage medium.
Background
With the continuous change of products and requirements, the application service also needs to continuously perform corresponding update iteration, and the update iteration frequency of the current application service is faster and faster.
The existing application service updating and releasing mode is mainly manually updated by operation and maintenance personnel, and the updating process is roughly as follows: and uploading a new program package by the operation and maintenance personnel, and restarting the application service after backing up and replacing the program package so as to completely correspond to the update and the release of the service.
However, since there are many commands to be executed in the update distribution process, it is relatively cumbersome to manually update the application service, and thus the update efficiency is relatively slow.
Disclosure of Invention
Based on the defects of the prior art, the application provides a method and device for issuing application services, electronic equipment and a storage medium, so as to solve the problems that the existing issuing mode is too excessive in sending and the issuing efficiency is low.
In order to achieve the above object, the present application provides the following technical solutions:
a first aspect of the present application provides a method for publishing an application service, including:
acquiring a release parameter of a target application service; wherein the publishing parameter comprises at least an up-to-date code ID of the target application service;
pulling a code program corresponding to the latest code ID of the target application service and packaging to obtain a current program package of the target application service;
sequentially aiming at each target server, replacing the current program package of the target application service with the old program package of the target application service in the target server according to the IP of the target server in a configuration file, and starting the target application service; and the target server is the server where the target application is located.
Optionally, in the method for issuing an application service provided above, the sequentially aiming at each target server, replacing an old package of the target application service in the target server with a current package of the target application service according to the IP of the target server in a configuration file, and starting the target application service includes:
sequentially aiming at each target server, uploading a current program package of the target application service to a fixed directory of the target server according to the IP of the target server in a configuration file;
and copying the current program of the target application service from the fixed directory of the target server, replacing the current program of the target application service with the old program package of the target application service in the target server, and starting the target application service.
Optionally, in the method for issuing an application service, after uploading the current package of the target application service to the fixed directory of the target server according to the IP of the target server, the method further includes:
judging whether the target application service belongs to a Web service or not;
if the target application service is judged to belong to the Web service, the IP of the target server is removed from the load balancer;
closing the zabbix monitoring alarm of the target application service.
Optionally, in the method for issuing an application service provided above, after replacing the current program of the target application service with the old program package of the target application service in the target server and starting the target application service, the method further includes:
starting a zabbix monitoring alarm of the target application service;
and adding the IP of the target server into the load of the load balancer again, and reloading the load balancer.
Optionally, in the method for publishing the application service, the method further includes:
monitoring the execution information and the execution result of the issuing operation command executed on each target server in the issuing process in real time;
responding to a user's implementation checking request, and displaying the monitored execution information of the issuing operation command and the execution result;
and feeding back the release completion prompt information when monitoring that all the target servers finish the update release of the target application service.
Optionally, in the method for publishing the application service, obtaining a publishing parameter of a target application service includes:
determining the application service selected by the user in the application service pull-down option of the release interface as a target service;
determining various configuration information corresponding to the target application service from the configuration file;
respectively displaying each item of configuration information in corresponding parameter pull-down options;
and responding to the selection operation of the user in the parameter pull-down option, and determining the configuration information selected by the user as the release parameter of the target application service.
Optionally, in the method for issuing an application service provided above, after replacing the current package of the target application service with the old package of the target application service in the target server and starting the target application service, the method further includes:
and responding to the rollback operation of the user, replacing the old program package of the target application service with the current program package of the target application service in the target server, and starting the target application service.
A second aspect of the present application provides an apparatus for issuing an application service, including:
the parameter acquisition unit is used for acquiring the release parameters of the target application service; wherein the publishing parameter comprises at least an up-to-date code ID of the target application service;
a program pulling unit, configured to pull and package a code program corresponding to the latest code ID of the target application service, to obtain a current program package of the target application service;
the update release unit is used for sequentially aiming at each target server, replacing the current program package of the target application service with the old program package of the target application service in the target server according to the IP of the target server in the configuration file, and starting the target application service; and the target server is the server where the target application is located.
Optionally, in the above-mentioned distribution apparatus for an application service, the update distribution unit includes:
the uploading unit is used for sequentially uploading the current program package of the target application service to a fixed directory of the target server according to the IP of the target server in a configuration file aiming at each target server;
and the updating and issuing subunit is used for copying the current program of the target application service from the fixed directory of the target server, replacing the current program of the target application service with the old program package of the target application service in the target server, and starting the target application service.
Optionally, in the above-mentioned application service issuing apparatus, the apparatus further includes:
a judging unit configured to judge whether the target application service belongs to a Web service;
the eliminating unit is used for eliminating the IP of the target server from the load balancer when the judging unit judges that the target application service belongs to the Web service;
and the closing unit is used for closing the zabbix monitoring alarm of the target application service.
Optionally, in the above-mentioned application service issuing apparatus, the apparatus further includes:
the starting unit is used for starting a zabbix monitoring alarm of the target application service;
and the reloading unit is used for adding the IP of the target server into the load of the load balancer again and reloading the load balancer.
Optionally, in the above-mentioned application service issuing apparatus, the apparatus further includes:
the monitoring unit is used for monitoring the execution information and the execution result of the issuing operation command executed on each target server in the issuing process in real time;
the first response unit is used for responding to an implementation checking request of a user and displaying the monitored execution information of the issuing operation command and the execution result;
and the feedback unit is used for feeding back the prompt information of the completion of the release when the target servers are monitored to finish the update release of the target application service.
Optionally, in the above-mentioned application service publishing device, the parameter obtaining unit includes:
the first determining unit is used for determining the application service selected by the user in the application service pull-down option of the release interface as the target service;
a second determining unit, configured to determine, from the configuration file, configuration information items corresponding to the target application service;
the display unit is used for respectively displaying each item of configuration information in the corresponding parameter pull-down options;
and the second response unit is used for responding to the selection operation of the user in the parameter pull-down option and determining the configuration information selected by the user as the release parameter of the target application service.
Optionally, in the above-mentioned application service issuing apparatus, the apparatus further includes:
and the third response unit is used for responding to the rollback operation of the user, replacing the old program package of the target application service with the current program package of the target application service in the target server, and starting the target application service.
A third aspect of the present application provides an electronic device comprising:
a memory and a processor;
wherein the memory is used for storing programs;
the processor is configured to execute the program, and when the program is executed, the program is specifically configured to implement the method for issuing an application service according to any one of the above.
A fourth aspect of the present application provides a computer storage medium storing a computer program for implementing the method of publishing an application service as claimed in any one of the preceding claims when executed.
The embodiment of the application service publishing method comprises the steps of obtaining publishing parameters of a target application service, wherein the publishing parameters at least comprise the latest code ID of the target application service, so that a code program corresponding to the latest code ID of the target application service can be pulled and packaged to obtain a current program package of the target application service. And then sequentially aiming at each target server where the target application is positioned, replacing the current program package of the target application service with the old program package of the target application service in the target server according to the IP of the target server in the configuration file, starting the target application service, and finishing the automatic updating and releasing of the target application service.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a method for issuing an application service according to an embodiment of the present application;
fig. 2 is a flowchart of a method for obtaining a publishing parameter of a target application service according to an embodiment of the present application;
fig. 3 is a flowchart of a method for issuing a target application service update to a target server according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an application service publishing device according to another embodiment of the present application;
fig. 5 is a schematic structural diagram of an update issue unit according to another embodiment of the present application;
fig. 6 is a schematic structural diagram of a parameter obtaining unit according to another embodiment of the present application;
fig. 7 is a schematic structural diagram of an electronic device according to another embodiment of the present application.
Detailed Description
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.
In this application, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, 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 identical elements in a process, method, article, or apparatus that comprises the element.
The application provides a method for issuing an application service, as shown in fig. 1, specifically including the following steps:
s101, obtaining the release parameters of the target application service.
Wherein the release parameter comprises at least the latest code ID of the target application service. Of course, the publishing parameters may also include the service name, service type, publishing action, etc. of the target application service. Wherein, the publishing action can be pre-publishing, complete publishing, or rolling back the last version, etc.
Optionally, the publishing parameters may include parameters selected by the user and fixed parameters, which include parameters that the user can select according to the user's needs, such as a server that needs to be updated at this time. However, considering that there may be some parameters that cannot be changed arbitrarily, the release parameters may be fixed parameters, that is, the default release parameters may be fixed after the target application service to be released is selected.
Optionally, in another embodiment of the present application, an implementation manner of step S101, as shown in fig. 2, includes:
s201, determining the application service selected by the user in the application service pull-down option of the release interface as the target service.
S202, determining various pieces of configuration information corresponding to the target application service from the configuration files.
In the present application, the name of each application service, the corresponding code repository, the service type, and the like are previously described.
And S203, respectively displaying each item of configuration information in the corresponding parameter pull-down option.
That is to say, in the embodiment of the present application, after the user selects the target application service that needs to be updated and published, the corresponding configuration information such as the IP, git, etc. of the server is also automatically brought out for the user to select.
It should be noted that, in addition to the parameter drop-down items corresponding to the respective configuration information, other drop-down items that need to be selected by the user but do not have parameters in the configuration file may be displayed on the publishing interface. For example, a drop down option for a publish action, etc.
And S204, responding to the selection operation of the user in the parameter pull-down option, and determining the configuration information selected by the user as the release parameter of the target application service.
By adopting the pull-down option mode, the problem that the application service cannot be normally issued due to the fact that the user inputs information by mistake can be effectively avoided.
Similarly, in the embodiment of the present application, in addition to determining the configuration information selected by the user as the publishing parameter of the target application service, if there is a fixed parameter corresponding to the target application service, the fixed parameter needs to be directly determined as the publishing parameter of the target application service.
S102, pulling and packaging the code program corresponding to the latest code ID of the target application service to obtain a current program package of the target application service.
Specifically, the corresponding code program may be pulled from the remote code repository according to the latest code ID of the target application service, and then packaged according to a preset packaging command to obtain the current package of the target application service.
S103, sequentially aiming at each target server, replacing the current program package of the target application service with the old program package of the target application service in the target server according to the IP of the target server in the configuration file, and starting the target application service, wherein the target server is the server where the target application is located.
It should be noted that, in order to ensure that the target application service can be continuously used when the service is updated, the update of the target application service needs to be sequentially issued to each target server.
Alternatively, the update distribution may be performed on each target server in turn according to the IP of each target server where the target application service is located in the configuration file. Of course, the target application service may also be updated only on a part of the target servers selected by the user, that is, in the embodiment of the present application, a part of the update publishing or all the update canvas may be selected, and the user may first select the IP of the server to be published according to the requirement.
Specifically, in the updating process, the current program package of the target application service is replaced by the old program package of the target application service in the target server, the target application service is started, so that the target application service in one target server is updated, and then the next target server is updated until all the target servers are updated.
Optionally, in another embodiment of the present application, a specific implementation manner of step S103, as shown in fig. 3, includes:
s301, sequentially aiming at each target server, uploading the current program package of the target application service to a fixed directory of the target server according to the IP of the target server in the configuration file.
It should be noted that, in the embodiment of the present application, when the target server is updated, the current package of the target application service is remotely uploaded to the fixed directory of the target server, instead of being directly updated, so that the required preparation work is performed before replacing the package, and the current package of the target application service can also be backed up.
In another embodiment of the present application, after step S301 is executed, before step S302 is executed, further steps of:
it is determined whether the target application service belongs to a Web service,
if the target application service is judged to belong to the Web service, the IP of the target server is removed from a load balancer (Nginx), and then the zabbix monitoring alarm of the target application service is closed. If the target application service is judged not to belong to the Web service, the zabbix monitoring alarm of the target application service can be directly sent out.
It should be noted that, because the Web service generally provides an http service, the monitored disconnection is 8080, and when the Web service is restarted, the 8080 port is turned off and then turned on, and a request for invoking the target application service, which is allocated to the target server when the Web service is turned off, is invalid access, so that the request of the user cannot be responded. Therefore, in the embodiment of the application, when it is determined that the target application service belongs to the Web service, the IP of the target server is removed from the load balancer, so that the request of the user is smoothly migrated to other target servers during load balancing, the target server which is currently updated and published is prevented from receiving the request, and the response to the user request is ensured.
Since the zabbix monitoring alarm of the target application service is prone to false alarm when the target application service is updated, in the embodiment of the present application, before step S302 is executed, the zabbix monitoring alarm of the target application service is first closed.
Accordingly, in the embodiment of the present application, after step S302 is executed, that is, after the target server completes the update distribution, it is further required to execute: and starting a zabbix monitoring alarm of the target application service, adding the IP of the target server into the load of the load balancer again, and reloading the load balancer.
Because the zabbix monitoring alarm of the target application service is closed before updating, the zabbix monitoring alarm of the target application service needs to be opened after updating and releasing are completed, so that the normal operation of the zabbix monitoring alarm is ensured. Also, for the Web service, since the IP of the target server is removed from the load balancer (Nginx) before the update, the IP of the target server needs to be added to the load of the load balancer again after the update, and the load balancer needs to be reloaded, so that the target server can normally receive the request of the user.
S302, copying the current program of the target application service from the fixed directory of the target server, replacing the current program of the target application service with the old program package of the target application service in the target server, and starting the target application service.
Optionally, in another embodiment of the present application, after performing step S103, that is, after completing the update issue of the target application service, the method may further include: and responding to the rollback operation of the user, replacing the old program package of the target application service with the current program package of the target application service in the target server, and starting the target application service.
That is to say, in the embodiment of the present application, a one-key rollback may also be performed, and when it is found that the target application service has a problem after release and an urgent rollback version is required, the previous version may be directly rolled back through a one-key rollback operation. It should be noted that the rollback operation mainly aims at normal update distribution completion, but when some functions find that there is a service logic problem, the rollback operation is performed according to service requirements. If a problem occurs in the release process, operation and maintenance personnel should be required to determine and repair the fault by checking the process log.
Optionally, in another embodiment of the present application, during the issuing process, the method may further include:
and monitoring the execution information and the execution result of the issuing operation command executed on each target server in the issuing process in real time.
And responding to a request for implementing and checking by a user, and displaying the monitored execution information of the issuing operation command and the execution result.
And feeding back the release completion prompt information when monitoring that all the target servers finish the update release of the target application service.
The implementation monitoring and display of the publishing process enable the user to know the publishing condition, so that problems can be found conveniently.
Optionally, in another embodiment of the present application, an update publishing tool is further provided, which is used for implementing the publishing method of the application service provided in the foregoing embodiment. Also, the facility may perform publishing tasks for nodes added to the facility, i.e., for adding application services to new application servers. The update distribution tool can make additions to the nodes and, of course, deletes them accordingly.
Specifically, when the node is added or deleted, the application service configuration information of the node to be added or deleted is modified. It should be noted that, for an application providing a web service, after adding an IP of a node, a corresponding IP is also added to a load balancer. And after the node is deleted, the load balancer also deletes the corresponding IP, otherwise, the ring section of the load balancer operated by the update publishing tool stops operating due to error report caused by that the corresponding IP cannot be found. Of course, the update distribution tool may also include functions such as online and offline of the application service.
The embodiment of the application service publishing method comprises the steps of obtaining publishing parameters of a target application service, wherein the publishing parameters at least comprise the latest code ID of the target application service, so that a code program corresponding to the latest code ID of the target application service can be pulled and packaged to obtain a current program package of the target application service. And then sequentially aiming at each target server where the target application is positioned, replacing the current program package of the target application service with the old program package of the target application service in the target server according to the IP of the target server in the configuration file, starting the target application service, and finishing the automatic updating and releasing of the target application service.
It is to be noted that the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Although the operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous.
Another embodiment of the present application provides an apparatus for issuing an application service, as shown in fig. 4, including the following units:
a parameter obtaining unit 401, configured to obtain a publishing parameter of the target application service.
Wherein the release parameter comprises at least the latest code ID of the target application service.
A program pulling unit 402, configured to pull and package a code program corresponding to the latest code ID of the target application service, so as to obtain a current package of the target application service.
And an update issuing unit 403, configured to sequentially replace, for each target server, an old package of the target application service in the target server with a current package of the target application service according to the IP of the target server in the configuration file, and start the target application service.
The target server is a server where the target application is located.
Optionally, in another embodiment of the present application, there is provided an update distribution unit in a distribution apparatus for an application service, as shown in fig. 5, including:
and an uploading unit 501, configured to sequentially upload, for each target server, a current program package of the target application service to a fixed directory of the target server according to the IP of the target server in the configuration file.
An update issuing subunit 502 is configured to copy the current program of the target application service from the fixed directory of the target server, replace the current program of the target application service with the old package of the target application service in the target server, and start the target application service.
Optionally, another embodiment of the present application provides an apparatus for issuing an application service, further including:
and the judging unit is used for judging whether the target application service belongs to the Web service.
And the eliminating unit is used for eliminating the IP of the target server from the load balancer when the judging unit judges that the target application service belongs to the Web service.
And the closing unit is used for closing the zabbix monitoring alarm of the target application service.
Optionally, another embodiment of the present application provides an apparatus for issuing an application service, further including:
and the starting unit is used for starting the zabbix monitoring alarm of the target application service.
And the overloading unit is used for adding the IP of the target server into the load of the load balancer again and reloading the load balancer.
Optionally, another embodiment of the present application provides an apparatus for issuing an application service, further including:
the monitoring unit is used for monitoring the execution information and the execution result of the issuing operation command executed on each target server in the issuing process in real time;
the first response unit is used for responding to the implementation checking request of the user and displaying the monitored execution information and execution result of the issuing operation command;
and the feedback unit is used for feeding back the prompt information of the completion of the release when the situation that all the target servers finish the update release of the target application service is monitored.
Optionally, in another embodiment of the present application, there is provided an application service publishing device, where the parameter obtaining unit, as shown in fig. 6, includes:
the first determining unit 601 is configured to determine an application service selected by a user in an application service pull-down option of a publishing interface as a target service.
A second determining unit 602, configured to determine, from the configuration file, configuration information corresponding to the target application service.
The display unit 603 is configured to display each item of configuration information in the corresponding parameter pull-down option.
A second responding unit 604, configured to respond to a selection operation of the user in the parameter pull-down option, and determine the configuration information selected by the user as a publishing parameter of the target application service.
Optionally, another embodiment of the present application provides an apparatus for issuing an application service, further including:
and the third response unit is used for responding to the rollback operation of the user, replacing the old program package of the target application service with the current program package of the target application service in the target server, and starting the target application service.
It should be noted that, for the specific working processes of each unit provided in the foregoing embodiments of the present application, corresponding steps in the foregoing method embodiments may be referred to accordingly, and are not described herein again.
Another embodiment of the present application provides an electronic device, as shown in fig. 7, including:
a memory 701 and a processor 702.
The memory 701 is used for storing programs.
The processor 702 is configured to execute the program stored in the storage 701, and when the program is executed, the processor is specifically configured to implement the publishing method of the application service provided in any one of the above embodiments.
Another embodiment of the present application provides a computer storage medium for storing a computer program, which when executed, is used for implementing the method for issuing an application service provided in any one of the above embodiments.
Computer storage media, including permanent and non-permanent, removable and non-removable media, may implement the information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A method for publishing an application service, comprising:
acquiring a release parameter of a target application service; wherein the publishing parameter comprises at least an up-to-date code ID of the target application service;
pulling a code program corresponding to the latest code ID of the target application service and packaging to obtain a current program package of the target application service;
sequentially aiming at each target server, replacing the current program package of the target application service with the old program package of the target application service in the target server according to the IP of the target server in a configuration file, and starting the target application service; and the target server is the server where the target application is located.
2. The method according to claim 1, wherein said sequentially aiming at each of the target servers, replacing the current package of the target application service with the old package of the target application service in the target server according to the IP of the target server in the configuration file, and starting the target application service, comprises:
sequentially aiming at each target server, uploading a current program package of the target application service to a fixed directory of the target server according to the IP of the target server in a configuration file;
and copying the current program of the target application service from the fixed directory of the target server, replacing the current program of the target application service with the old program package of the target application service in the target server, and starting the target application service.
3. The method of claim 2, wherein after uploading the current package of the target application service into the fixed directory of the target server according to the IP of the target server, further comprising:
judging whether the target application service belongs to a Web service or not;
if the target application service is judged to belong to the Web service, the IP of the target server is removed from the load balancer;
closing the zabbix monitoring alarm of the target application service.
4. The method of claim 3, wherein after replacing the current program of the target application service with the old package of the target application service in the target server and starting the target application service, further comprising:
starting a zabbix monitoring alarm of the target application service;
and adding the IP of the target server into the load of the load balancer again, and reloading the load balancer.
5. The method of claim 1, further comprising:
monitoring the execution information and the execution result of the issuing operation command executed on each target server in the issuing process in real time;
responding to a user's implementation checking request, and displaying the monitored execution information of the issuing operation command and the execution result;
and feeding back the release completion prompt information when monitoring that all the target servers finish the update release of the target application service.
6. The method of claim 1, wherein obtaining publishing parameters of a target application service comprises:
determining the application service selected by the user in the application service pull-down option of the release interface as a target service;
determining various configuration information corresponding to the target application service from the configuration file;
respectively displaying each item of configuration information in corresponding parameter pull-down options;
and responding to the selection operation of the user in the parameter pull-down option, and determining the configuration information selected by the user as the release parameter of the target application service.
7. The method of claim 1, wherein after replacing the current package of the target application service with the old package of the target application service in the target server and starting the target application service, further comprising:
and responding to the rollback operation of the user, replacing the old program package of the target application service with the current program package of the target application service in the target server, and starting the target application service.
8. An apparatus for publishing an application service, comprising:
the parameter acquisition unit is used for acquiring the release parameters of the target application service; wherein the publishing parameter comprises at least an up-to-date code ID of the target application service;
a program pulling unit, configured to pull and package a code program corresponding to the latest code ID of the target application service, to obtain a current program package of the target application service;
the update release unit is used for sequentially aiming at each target server, replacing the current program package of the target application service with the old program package of the target application service in the target server according to the IP of the target server in the configuration file, and starting the target application service; and the target server is the server where the target application is located.
9. An electronic device, comprising:
a memory and a processor;
wherein the memory is used for storing programs;
the processor is configured to execute the program, which when executed is specifically configured to implement the method of publishing an application service as claimed in any of claims 1 to 7.
10. A computer storage medium storing a computer program which, when executed, implements the method of publishing application services as claimed in any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110975304.XA CN113849206A (en) | 2021-08-24 | 2021-08-24 | Application service publishing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110975304.XA CN113849206A (en) | 2021-08-24 | 2021-08-24 | Application service publishing method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113849206A true CN113849206A (en) | 2021-12-28 |
Family
ID=78976118
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110975304.XA Pending CN113849206A (en) | 2021-08-24 | 2021-08-24 | Application service publishing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113849206A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160026452A1 (en) * | 2014-07-23 | 2016-01-28 | Verizon Patent And Licensing Inc. | Efficient deployment of application revisions and implementation of application rollbacks across multiple application servers |
| CN107147711A (en) * | 2017-05-04 | 2017-09-08 | 浙江路港互通信息技术有限公司 | Application service update method and device |
| CN107729066A (en) * | 2017-11-08 | 2018-02-23 | 重庆扬讯软件技术股份有限公司 | One kind is based on SVN resources banks automation structure dissemination method and device |
| CN108376118A (en) * | 2018-02-09 | 2018-08-07 | 腾讯科技（深圳）有限公司 | Service delivery system, method, equipment and storage medium |
| CN108388440A (en) * | 2018-04-28 | 2018-08-10 | 北京辰森世纪科技股份有限公司 | A kind of method that web application systems automatically update |
| CN110519088A (en) * | 2019-08-15 | 2019-11-29 | 上海易点时空网络有限公司 | Configure service disaster and system |
| CN110825420A (en) * | 2019-11-26 | 2020-02-21 | 中国银行股份有限公司 | Configuration parameter updating method, device, equipment and storage medium for distributed cluster |
-
2021
- 2021-08-24 CN CN202110975304.XA patent/CN113849206A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160026452A1 (en) * | 2014-07-23 | 2016-01-28 | Verizon Patent And Licensing Inc. | Efficient deployment of application revisions and implementation of application rollbacks across multiple application servers |
| CN107147711A (en) * | 2017-05-04 | 2017-09-08 | 浙江路港互通信息技术有限公司 | Application service update method and device |
| CN107729066A (en) * | 2017-11-08 | 2018-02-23 | 重庆扬讯软件技术股份有限公司 | One kind is based on SVN resources banks automation structure dissemination method and device |
| CN108376118A (en) * | 2018-02-09 | 2018-08-07 | 腾讯科技（深圳）有限公司 | Service delivery system, method, equipment and storage medium |
| CN108388440A (en) * | 2018-04-28 | 2018-08-10 | 北京辰森世纪科技股份有限公司 | A kind of method that web application systems automatically update |
| CN110519088A (en) * | 2019-08-15 | 2019-11-29 | 上海易点时空网络有限公司 | Configure service disaster and system |
| CN110825420A (en) * | 2019-11-26 | 2020-02-21 | 中国银行股份有限公司 | Configuration parameter updating method, device, equipment and storage medium for distributed cluster |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107844386B (en) | Data backup and recovery method and device | |
| CN111610989B (en) | Application publishing/updating method and system for offline container cloud environment | |
| US10585656B1 (en) | Event manager for software deployment | |
| US8640098B2 (en) | Offline configuration and download approach | |
| EP2474910A1 (en) | Setting program, workflow creating method, and work flow creating apparatus | |
| CN113434180B (en) | Data processing method and device for application, server and storage medium | |
| CN115562911B (en) | Virtual machine data backup method, device, system, electronic equipment and storage medium | |
| CN112579101A (en) | Task script control method and device, electronic equipment and storage medium | |
| EP2940540B1 (en) | Power system monitoring and control system | |
| CN108388440A (en) | A kind of method that web application systems automatically update | |
| CN113849206A (en) | Application service publishing method and device, electronic equipment and storage medium | |
| CN114338363A (en) | Continuous integration method, device, equipment and storage medium | |
| CN110764785B (en) | Cloud platform tool chain and cloud platform operation and maintenance method for power industry based on open source assembly | |
| FR3003365A1 (en) | METHOD AND DEVICE FOR MANAGING SOFTWARE UPDATES OF A SET OF EQUIPMENT OF A SYSTEM SUCH AS A SYSTEM OF AN AIRCRAFT | |
| CN117055930A (en) | System upgrading deployment method and system | |
| CN115080309A (en) | Data backup system, method, storage medium, and electronic device | |
| CN108958827B (en) | Method and system for processing program upgrading fault | |
| CN107797915B (en) | Fault repairing method, device and system | |
| CN115529228B (en) | Fault positioning method, device and medium based on browser end | |
| CN116578380B (en) | Cluster task scheduling method, device and medium of data acquisition tool | |
| CN114296357B (en) | Processing method and device of functional data, electronic equipment and storage medium | |
| CN117205574A (en) | Real-time operation data processing method, device, equipment and storage medium | |
| CN116881365A (en) | Method, device, equipment and storage medium for field synchronization | |
| CN114840526A (en) | Data sampling inspection processing method and device | |
| CN116737464A (en) | Backup failure handling method, apparatus, device, medium and program product |
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 |