CN115033250B - Application deployment method, computing device and readable storage medium - Google Patents
Application deployment method, computing device and readable storage medium Download PDFInfo
- Publication number
- CN115033250B CN115033250B CN202210532268.4A CN202210532268A CN115033250B CN 115033250 B CN115033250 B CN 115033250B CN 202210532268 A CN202210532268 A CN 202210532268A CN 115033250 B CN115033250 B CN 115033250B
- Authority
- CN
- China
- Prior art keywords
- deployment
- deployment information
- service
- information
- application
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
本发明公开了一种应用部署方法、计算设备及可读存储介质。本发明的应用部署方法在计算设备中执行，计算设备与服务部署服务器通信连接，该方法包括：当监听到第一事件时，获取应用当前所有服务的第一部署信息。接着，获取应用前一次有效部署时所有服务的第二部署信息，并将第一部署信息与第二部署信息的差异信息，在第一部署信息或第二部署信息中进行标注。然后，将标注后的第三部署信息发送至审核端。最后，当接收到审核端发送的审核成功消息后，将第三部署信息发送至服务部署服务器，以便服务部署服务器依据第三部署信息对应用中所修改的服务进行重新部署。本发明的应用部署方法支持按照服务更新，实现了小粒度的更新，方便快捷。
The present invention discloses an application deployment method, a computing device and a readable storage medium. The application deployment method of the present invention is executed in a computing device, and the computing device is connected to a service deployment server in communication. The method includes: when a first event is monitored, the first deployment information of all current services of the application is obtained. Then, the second deployment information of all services of the application during the last effective deployment is obtained, and the difference information between the first deployment information and the second deployment information is marked in the first deployment information or the second deployment information. Then, the marked third deployment information is sent to the audit end. Finally, after receiving the audit success message sent by the audit end, the third deployment information is sent to the service deployment server, so that the service deployment server redeploys the modified services in the application according to the third deployment information. The application deployment method of the present invention supports updating according to services, realizes small-grained updates, and is convenient and fast.
Description
The application is a divisional application of patent application 2022100772961 filed 24/01/2022.
Technical Field
The present invention relates to the field of computers, and in particular, to an application deployment method, a computing device, and a readable storage medium.
Background
Currently, application deployment is mainly implemented based on Helm. Specifically, first, an application package to be deployed is uploaded, generally in jar and war format. Then, java Api is called to render Dockerfile files according to the visibility syntax, and a Docker image which can be used by Kubernetes is generated according to the Docker API. Then, the Docker image and the generated HELM CHART deployment file are uploaded to a server through a Java API. Finally, kubernetes components such as Pod and Deployment are created by HELM INSTALL commands.
Obviously, the implementation of the application deployment method relies on the deployment personnel to write Dockerfile and HELM CHART files, which has high requirements on the deployment personnel, and is not supported to update according to the service, and the efficiency is low.
For this reason, a new application deployment method is needed to solve the above-mentioned problems.
Disclosure of Invention
To this end, the present invention provides an application deployment method, computing device, and readable storage medium in an effort to solve or at least alleviate the above-identified problems.
According to one aspect of the invention, an application deployment method is provided, the application deployment method is executed in a computing device, the computing device is in communication connection with a service deployment server, when a first event is monitored, first deployment information of all services of an application at present is obtained, second deployment information of all services of the application at the time of effective deployment of the application at the previous time is obtained, difference information of the first deployment information and the second deployment information is marked in the first deployment information or the second deployment information, third deployment information after marking is sent to an auditing end so that the auditing end can audit the deployment information of the modified services according to the third deployment information, and after an auditing success message sent by the auditing end is received, the third deployment information is sent to the service deployment server so that the service deployment server can redeploy the modified services in the application according to the third deployment information.
Optionally, in the application deployment method according to the invention, before the step of acquiring the first deployment information of all the services of the application currently when the first event is monitored, the method further comprises the step of displaying a service deployment information interface when the second event is monitored, so that a user creates or modifies the deployment information of the services of the application through the service deployment information interface and triggers the first event.
Optionally, in the application deployment method according to the invention, the step of labeling the difference information of the first deployment information and the second deployment information in the first deployment information or the second deployment information comprises the steps of labeling the newly added part of the first deployment information compared with the second deployment information in the first deployment information or the second deployment information by a first identifier and labeling the deleted part of the first deployment information compared with the second deployment information by a second identifier.
Optionally, in the application deployment method according to the invention, the method for the service deployment server to redeploy the modified services in the application according to the third deployment information comprises the steps of acquiring the marked deployment information of each modified service in the application after receiving the third deployment information sent by the computing device, and redeploying each modified service according to the marked deployment information of each modified service.
Optionally, the method for deploying the application comprises the steps of, for each modified service, acquiring marked deployment information of each modified resource in the service based on the marked deployment information of each modified service, and redeploying each modified resource according to the marked deployment information of each modified resource.
Optionally, in the application deployment method according to the invention, the service deployment server is built with a container cluster, and the step of redeploying each modified resource comprises the steps of rendering a description file template generated based on interface parameters of the container cluster by using the noted deployment information of each modified resource to generate a description file identifiable to the container cluster, and creating, updating or deleting the resource based on the description file.
Optionally, the application deployment method further comprises the steps of detecting the state of the service to which the resource belongs after the steps of creating, updating or deleting the resource, continuing to redeploy the modified next resource in the service if the service state is normal, and executing rollback on the redeployed target service if the service state is abnormal.
Optionally, in the application deployment method according to the invention, the step of performing rollback on the redeployed target service comprises the steps of sending a message for performing rollback on the target service to the computing device, so that the computing device marks the difference information of the current deployment information of the target service and the deployment information of the last valid deployment of the target service in the current deployment information of the target service or the deployment information of the last valid deployment of the target service, receiving the marked fourth deployment information sent by the computing device, and performing rollback on the target service based on the fourth deployment message.
Optionally, in the application deployment method according to the invention, the step of marking the difference information of the current deployment information of the target service and the deployment information of the last valid deployment of the target service in the current deployment information of the target service or the deployment information of the last valid deployment of the target service by the computing device comprises the steps of marking the part of the deployment information of the last valid deployment of the target service, which is newly added compared with the current deployment information, by a first identifier and marking the part of the deployment information of the last valid deployment of the target service, which is deleted compared with the current deployment information, by a second identifier in the current deployment information of the target service or the deployment information of the last valid deployment of the target service.
Optionally, in the application deployment method according to the present invention, after the step of acquiring the first deployment information of all services of the application, the method further includes storing the acquired first deployment information.
According to yet another aspect of the present invention there is provided a computing device comprising at least one processor, and a memory storing program instructions, wherein the program instructions are configured to be executed by the at least one processor, the program instructions comprising instructions for performing an application deployment method according to the present invention.
According to yet another aspect of the present invention, there is provided a readable storage medium storing program instructions that, when read and executed by a computing device, cause the computing device to perform an application deployment method according to the present invention.
According to the application deployment method, when the application is deployed, the current deployment information of the application and the difference information of the deployment information of the previous effective deployment of the application are firstly acquired. The modified service is then redeployed based on the difference information. It can be seen that the present invention can achieve the redeployment of the application by only redeploying the modified service. Therefore, the invention supports updating according to the service, realizes small-granularity updating, and is convenient and quick.
Further, after the difference information of the current deployment information of the application and the deployment information of the previous effective deployment is obtained, the current deployment information of the application and the deployment information of the previous effective deployment are sent to an auditing end for auditing, and the application is redeployed based on the difference information only after the auditing end passes. Therefore, the invention can ensure the accuracy of the application deployment information, thereby reducing the error rate of application release.
Drawings
To the accomplishment of the foregoing and related ends, certain illustrative aspects are described herein in connection with the following description and the annexed drawings, which set forth the various ways in which the principles disclosed herein may be practiced, and all aspects and equivalents thereof are intended to fall within the scope of the claimed subject matter. The above, as well as additional objects, features, and advantages of the present disclosure will become more apparent from the following detailed description when read in conjunction with the accompanying drawings. Like reference numerals generally refer to like parts or elements throughout the present disclosure.
FIG. 1 illustrates a block diagram of a computing device 100, according to one embodiment of the invention;
FIG. 2 illustrates a flow chart of an application deployment method 200 according to one embodiment of the invention;
FIG. 3 shows a schematic diagram of a service deployment information interface, according to one embodiment of the invention;
FIG. 4 illustrates a comparison of two deployments of a resource under a certain service of an application according to an embodiment of the invention;
FIG. 5 shows a schematic diagram of an application deployment method according to another embodiment of the invention;
fig. 6 shows a schematic diagram of an application deployment method according to a further embodiment of the invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
FIG. 1 illustrates a block diagram of a computing device 100, according to one embodiment of the invention. It should be noted that the computing device 100 shown in fig. 1 is only an example, and in practice, the computing device for implementing the application deployment method of the present invention may be any type of device, and the hardware configuration of the computing device may be the same as the computing device 100 shown in fig. 1 or may be different from the computing device 100 shown in fig. 1. In practice, the computing device for implementing the application deployment method of the present invention may add or delete hardware components of the computing device 100 shown in fig. 1, and the present invention is not limited to the specific hardware configuration of the computing device.
As shown in FIG. 1, in a basic configuration 102, a computing device 100 typically includes a system memory 106 and one or more processors 104. The memory bus 108 may be used for communication between the processor 104 and the system memory 106.
Depending on the desired configuration, the processor 104 may be any type of processing including, but not limited to, a microprocessor (μP), a microcontroller (μC), a digital information processor (DSP), or any combination thereof. The processor 104 may include one or more levels of caches, such as a first level cache 110 and a second level cache 112, a processor core 114, and registers 116. The example processor core 114 may include an Arithmetic Logic Unit (ALU), a Floating Point Unit (FPU), a digital signal processing core (DSP core), or any combination thereof. The example memory controller 118 may be used with the processor 104, or in some implementations, the memory controller 118 may be an internal part of the processor 104.
Depending on the desired configuration, system memory 106 may be any type of memory including, but not limited to, volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.), or any combination thereof. Physical memory in a computing device is often referred to as volatile memory, RAM, and data in disk needs to be loaded into physical memory in order to be read by processor 104. The system memory 106 may include an operating system 120, one or more applications 122, and program data 124. In some implementations, the application 122 may be arranged to execute instructions on an operating system by the one or more processors 104 using the program data 124. Operating system 120 may be, for example, linux, windows or the like, which includes program instructions for handling basic system services and performing hardware-dependent tasks. The application 122 includes program instructions for implementing various functions desired by the user, and the application 122 may be, for example, a browser, instant messaging software, a software development tool (e.g., integrated development environment IDE, compiler, etc.), or the like, but is not limited thereto. When an application 122 is installed into computing device 100, a driver module may be added to operating system 120.
When the computing device 100 starts up running, the processor 104 reads and executes program instructions of the operating system 120 from the system memory 106. Applications 122 run on top of operating system 120, utilizing interfaces provided by operating system 120 and underlying hardware to implement various user-desired functions. When a user launches the application 122, the application 122 is loaded into the system memory 106, and the processor 104 reads and executes the program instructions of the application 122 from the system memory 106.
Computing device 100 also includes storage device 132, storage device 132 including removable storage 136 and non-removable storage 138, both removable storage 136 and non-removable storage 138 being connected to storage interface bus 134.
Computing device 100 may also include an interface bus 140 that facilitates communication from various interface devices (e.g., output devices 142, peripheral interfaces 144, and communication devices 146) to basic configuration 102 via bus/interface controller 130. The example output device 142 includes a graphics processing unit 148 and an audio processing unit 150. They may be configured to facilitate communication with various external devices such as a display or speakers via one or more a/V ports 152. Example peripheral interfaces 144 may include a serial interface controller 154 and a parallel interface controller 156, which may be configured to facilitate communication with external devices such as input devices (e.g., keyboard, mouse, pen, voice input device, touch input device) or other peripherals (e.g., printer, scanner, etc.) via one or more I/O ports 158. An example communication device 146 may include a network controller 160, which may be arranged to facilitate communication with one or more other computing devices 162 via one or more communication ports 164 over a network communication link.
The network communication link may be one example of a communication medium. Communication media may typically be embodied by computer readable instructions, data structures, program modules, and may include any information delivery media in a modulated data signal, such as a carrier wave or other transport mechanism. A "modulated data signal" may be a signal that has one or more of its data set or changed in such a manner as to encode information in the signal. By way of non-limiting example, communication media may include wired media such as a wired network or special purpose network, and wireless media such as acoustic, radio Frequency (RF), microwave, infrared (IR) or other wireless media. The term computer readable media as used herein may include both storage media and communication media.
In a computing device 100 according to the present invention, an application 122 includes instructions for performing the application deployment method 200 of the present invention, which may instruct the processor 104 to perform the application deployment method of the present invention. Those skilled in the art will appreciate that the application 122 may include other applications 126 for implementing other functions in addition to the instructions for performing the application deployment method 200.
FIG. 2 illustrates a flowchart of an application deployment method 200 according to one embodiment of the invention, the method 200 being adapted for execution in a computing device (e.g., the computing device 100 shown in FIG. 1). The computing device is communicatively coupled to a service deployment server.
To improve the efficiency of deployment, applications may be deployed based on the pattern of the micro-services. Micro-services are an architectural style that partitions a single application into multiple smaller service units. Therefore, when the application is deployed in the micro-service mode, one application is divided into a plurality of services. That is, the application in the present invention is composed of several services.
As shown in fig. 2, the application deployment method 200 of the present invention begins at step S210. Wherein prior to step S210, the method further comprises displaying a service deployment information interface when the second event is monitored, so that the user creates or modifies the deployment information of the service of the application through the service deployment information interface, and triggers the first event.
Specifically, the second event may be a pressing event of a predetermined key. Thus, when the user presses the preset key, a service deployment information interface is displayed on the current desktop. The service deployment information interface may include a service name, a mirror address, a start command, a service port, a configuration map, an environment variable, a key name, and the like. Thus, the user can modify the deployment information such as the service image address, the configuration file and the like in the application through the interface. Further, the service deployment information interface may take the form of a form, such as that of FIG. 3. Of course, the service deployment information interface may also take other forms, which are not limiting on the invention. In a specific embodiment, the person skilled in the art may set the settings according to the actual needs.
Additionally, the first event can be a click event that deploys the control. Based on this, a deployment control may be further included in the service deployment information interface, so that when the user modifies the deployment information such as the service image address, the configuration file, etc. in the application, the first event (i.e., the deployment event) may be triggered by clicking the deployment control. Of course, the above is only an example regarding the setting of the first event and the second event, and in a specific embodiment, a person skilled in the art may set the setting according to actual needs, which is not limited to the present invention.
Subsequently, when the first event is monitored, step S210 is performed to acquire first deployment information of all services currently applied. After the first deployment information of all the services of the application currently is acquired, the first deployment information can be stored. Specifically, the first deployment information for all services currently applied may be snapshot and then the generated snapshot of the first deployment information may be stored in a storage device that is locally or communicatively connected to the computing device. The storage device may be a database, for example, mySQL, mariaDB, oracle database, which is not limited to the present invention.
After the first deployment information of all the services of the application is obtained, step S220 is entered, the second deployment information of all the services when the application is effectively deployed for the previous time is obtained, and the difference information of the first deployment information and the second deployment information is marked in the first deployment information or the second deployment information.
Based on the above description, for each application, the present invention stores the deployment information of each service that it issues each time in a storage device that is locally or communicatively connected to the computing device, so that the second deployment information of all services when the application was effectively deployed last time can be obtained from the storage device that is locally or communicatively connected to the computing device. The validity here means that the release is successful, that is, the second deployment information of all the services of which the application was last released successfully is obtained.
Next, by comparing the first deployment information of all the services currently applied with the second deployment information of all the services successfully released last time, the difference information (i.e. the modification difference) between the first deployment information and the second deployment information can be obtained, as shown in fig. 4, the left side shows the deployment information of a resource under a service when the application successfully released last time, and the right side shows the deployment information of the resource under the current version of the application. It is obvious that, the two lines marked in fig. 4 are just difference information of the twice deployment information of the resource, and the two lines corresponding to each other may also be called as a change set of the twice deployment information of the resource.
After the difference information of the first deployment information and the second deployment information is obtained, the first deployment information of all the services at present is used as a target, and the second deployment information of all the services successfully released last time is used as a source, so that the difference information is marked in the first deployment information or the second deployment information. Specifically, when the difference information is marked in the second deployment information, the part of the first deployment information, which is newly added compared with the second deployment information, is marked by a first identifier, and the part of the first deployment information, which is deleted compared with the second deployment information, is marked by a second identifier. Further, the first deployment information is marked at the corresponding position of the second deployment information compared with the newly added part in the second deployment information by using the first identifier, and the first deployment information is marked at the original position of the second deployment information compared with the deleted part of the second deployment information by using the second identifier. Wherein the first indicia may be set as underlined and the second indicia as middle-underlined. Of course, the first mark may be set to be red, and the second mark may be set to be blue, which is not limited to the present invention, and in a specific embodiment, those skilled in the art may set the first mark according to actual needs.
In addition, the method for labeling the difference information in the first deployment information by using the first deployment information as a target and the second deployment information as a source is similar to the method for labeling the difference information in the second deployment information by using the first deployment information as a target and the second deployment information as a source, and the description of labeling the difference information in the second deployment information can be referred to for relevant points, and is not repeated here.
To better illustrate this step, a specific example is given below by taking AppConfig resources under a service of an application as an example. The first deployment information of AppConfig resources when the last release of the application is successful is 'Host: 0.0.0.0port: 18822', the user modifies the first deployment information of AppConfig resources to be 'Host: 127.0.1 port: 18822', the second deployment information of the modified AppConfig resources is taken as a target, the first deployment information of AppConfig resources when the last release of the application is successful is 'Host: 0.0.0.0port: 18822', and the first deployment information is marked as 'Host: 127.0.0.1', when the first deployment information is markedPort:18822”。
The difference information between the first deployment information and the second deployment information is marked in the first deployment information or the second deployment information to obtain marked third deployment information, and then step S230 is performed, and the marked third deployment information is sent to an auditing end so that the auditing end can audit the deployment information of the modified service (i.e. the service with changed deployment information) according to the third deployment information. Specifically, at the auditing end, the auditor can audit the modified service deployment information based on the noted third deployment information, and send an audit success message to the computing device after the audit is passed.
For the computing device, after receiving the audit success message sent by the audit terminal, step S240 is entered, and the third deployment information is sent to the service deployment server, so that the service deployment server redeploys the modified service in the application according to the third deployment information. Therefore, the invention can send the deployment information to the service deployment server only after the verification is successful, so that the accuracy of the application deployment information can be ensured, and the error rate of application release can be reduced.
Specifically, for the service deployment server, after receiving the third deployment information sent by the computing device, the service deployment server first obtains the modified deployment information of each service after labeling in the application. And then, redeploying the modified services according to the modified deployment information of the marked services.
Wherein for any modified service, it can be redeployed by the following steps. Firstly, based on the labeled deployment information of the service, the labeled deployment information of each resource modified in the service is obtained. And then, redeploying the modified resources according to the modified deployment information of the marked resources, thereby completing redeployment of the service.
According to one embodiment of the invention, any modified resource may be deployed through a cluster of containers when deployed. Thus, a container cluster environment may first be built in a service deployment server. Specifically, the container cluster environment may be a Kubernetes (open source container cluster management system for deploying, expanding and managing containerized applications), a tool for defining and running multi-container Docker applications by Docker-Compose, or a Docker-SWARM (cluster management tool specified by Docker official), which is not limited to this embodiment, and in a specific embodiment, those skilled in the art may choose according to actual needs.
After the container cluster environment is built in the service deployment server, any modified resource can be deployed by utilizing the container cluster. Specifically:
Firstly, rendering a description file template generated based on interface parameters of a container cluster by using the deployment information after the resource labeling, and generating a description file identifiable by the container cluster. Wherein the description file template may be generated based on a template engine when the description file template is generated based on interface parameters of the container cluster environment. The Template engine may employ Pongo, mustache, hero, GO-Template, etc., and the invention is not limited thereto. In addition, as an example herein, in the Kubernetes container cluster environment, the generated description file is a YAML file. The YAML file is used to declare Kubernetes Objects, kubernetes Objects as persistent entries that Kubernetes uses to represent the state of the entire cluster, such as Pod, configMap, service. The description of the other container clusters is not described in detail herein.
Then, the resource is created, updated, or deleted based on the generated description file. Specifically, the creation, update, or deletion of the resource may be implemented by executing the generated description file through an API (Application Programming Interface, application program interface) of the container cluster, thereby completing the deployment of the resource.
In addition, according to one embodiment of the present invention, after any resource is created, updated or deleted, detecting the state of the service to which the resource belongs is further included. The state of the service to which the resource belongs may be detected by WebSocket. Further, the state of the service to which the resource belongs can be detected by calling a detection interface of the container cluster based on WebSocket.
If the service state of the resource is normal, continuing to redeploy the modified next resource in the service. After each resource modified in the service is deployed, the next modified service is continued to be deployed until each modified service is deployed. At this time, deployment of the application is completed, i.e., release is completed.
If the service state of the resource is abnormal, rollback is performed on the redeployed target service. Specifically, first, a message to perform rollback on a redeployed target service is sent to a computing device.
When the computing device receives the rollback message for the target service, the computing device compares the current deployment information of the target service obtained based on the first deployment information with the deployment information of the last effective deployment of the target service obtained based on the second deployment information to obtain the difference information between the current deployment information of the target service and the deployment information of the last effective deployment of the target service, and marks the obtained difference information in the current deployment information of the target service or the deployment information of the last effective deployment of the target service.
When the obtained difference information is marked in the current deployment information of the target service or the deployment information of the previous effective deployment of the target service, the obtained difference information should be marked in the current deployment information of the target service or the deployment information of the previous effective deployment of the target service by taking the deployment information of the previous effective deployment of the target service as a target and the current deployment information of the target service as a source.
Specifically, when the obtained difference information is marked in the current deployment information of the target service, the part of the deployment information of the previous effective deployment of the target service, which is compared with the current deployment information of the target service, is marked by a first identifier, and the part of the deployment information of the previous effective deployment of the target service, which is compared with the current deployment information of the target service, is marked by a second identifier. In addition, the method for marking the obtained difference information in the deployment information of the previous effective deployment of the target service is similar to the method for marking the obtained difference information in the current deployment information of the target service, and will not be described in detail herein.
A specific example will be given below taking AppConfig resources under a service of an application as an example. The deployment information of AppConfig resources when the application is successfully released last time is 'Host: 0.0.0.0Port: 18822', and the user modifies the deployment information of AppConfig resources to 'Host: 127.0.0.1Port: 18822'. When the computing device receives the rollback message, the deployment information of last effective deployment of AppConfig resources, "Host:0.0.0 Port:18822" is taken as a target, the current deployment information of AppConfig resources, "Host: 127.0.1 Port:18822" is taken as a source, and the deployment information is marked as "Host: 0.0.0.0.0.0 after the current deployment information is markedPort:18822”。
After the obtained difference information is marked in the current deployment information of the target service or the deployment information of the previous effective deployment, marked fourth deployment information is obtained, and then the computing equipment sends the marked fourth deployment information to the service deployment server.
And after the service deployment server receives the marked fourth deployment information sent by the computing equipment, executing rollback on the target service based on the received fourth deployment information. Wherein, when the rollback is executed on the target service, the auditing end is not required to audit. Specifically:
and aiming at any target service, acquiring the marked deployment information of each resource modified in the target service based on the marked deployment information of the target service. Then, according to the modified deployment information of each resource after marking, rollback is performed on each modified resource, so that rollback of the target service is completed.
When any modified resource is rolled back, firstly, the deployment information marked by the resource is utilized to render a description file template generated based on interface parameters of the container cluster, and a description file identifiable by the container cluster is generated. Then, based on the generated description file, the resource is created, updated or deleted, thereby completing rollback of the resource.
It should be noted that, the method for performing rollback on the target service is similar to the method for deploying the service, and specifically, the method for redeploying the modified service in the application can be referred to as the above method, which is not described herein.
Thus, the method and the device are used for redeploying the modified resources based on the difference information of the two deployments (taking the current deployment information of the application as a target and the deployment information of the last effective deployment as a source) which are positively acquired, so that the corresponding redeployment is realized. If an abnormality is detected in the middle of deployment, rollback is performed on the redeployed resources based on the difference information of two deployments of the redeployed service (taking the current deployment information of the redeployed service as a source and the deployment information of the last effective deployment as a target), which is acquired in a reverse direction, so that rollback on the application is realized. Obviously, the invention can realize the redeployment and rollback of the application by only small amount of updating based on the difference information of the adjacent two deployments, and is convenient and quick.
In order to better explain the complete implementation of the present invention, the entire process of the application deployment method of the present invention will be described by way of a specific example with reference to fig. 5. Wherein the user modifies the deployment information of the services a, B and C of the application through the service deployment information form in this example. Specifically, for application service A, the user has modified both its ConfigMap Objects and Pod Objects resources. In addition, in this example, the container cluster built in the service deployment server is Kubernetes, which is an open-source application for managing containerization on multiple hosts in the cloud platform. The description file template generated based on the interface parameters of Kubernetes is Kubernetes Objects, which is a persisted entry that Kubernetes uses to represent the state of the entire cluster, such as Pod, configMap and Service. Next, a deployment method of the application will be described.
And the first step is to acquire the deployment information of all the services currently applied when the deployment event is monitored, and generate a snapshot thereof.
And the second step is to acquire the snapshot of the deployment information of all the services when the application is effectively deployed last time, and forward acquire the modification difference of the deployment information of the two times by taking the snapshot of the deployment information of all the services when the application is effectively deployed last time as a target and taking the snapshot of the deployment information of all the services when the application is effectively deployed last time as a source.
And thirdly, marking the obtained modification difference in the snapshot of the deployment information when the application is effectively deployed last time, and sending the marked deployment information to an auditing end for auditing.
And fourthly, if the audit is not passed, notifying the user to revise the deployment information of the service through the form. If the audit passes, stage Kubernetes Objects is entered, first, a YAML file is generated using the annotated deployment information rendering Kubernetes Objects template of ConfigMap Objects resources in service A. Among them, the YAML file is used to claim Kubernetes Objects in Kubernetes 8.
And fifthly, executing the YAML file through the Kubernetes API SERVER to update ConfigMap Objects resources.
And sixthly, checking the state of the service A through the WebSocket. If not, performing rollback and recording the rollback message. If so, the next Pod Objects resource in service A is continued to be updated (similar to the update method for ConfigMap Objects resources).
And seventhly, continuing to check the state of the service A through the WebSocket. If not, performing rollback and recording the rollback message. If the service B and the service C are normally deployed (similar to the method for deploying the service A), when the service B and the service C are deployed, the release is completed, and release information is recorded.
For specific details regarding the application deployment method of the present embodiment, reference may be made to the descriptions based on fig. 1 to 4, and details are not repeated here.
For a better understanding of the application deployment method of the present invention, the present invention further provides four embodiments in conjunction with fig. 6. It should be noted that, the four examples are all described by taking one resource as an example.
Creation of configuration at first publication
The first step is that the user creates a configuration (as follows) through the service deployment information form and applies for deployment.
When monitoring a deployment event, creating a new deployment snapshot new, and caching the deployment snapshot old of the last effective deployment, wherein the deployment snapshot old is as follows:
Thirdly, taking the deployment snapshot in the last effective deployment as a source, taking the deployment snapshot at this time as a target, acquiring difference information of the two deployments (namely calculating a change set), and marking the difference information, wherein an underline represents the new addition, and a middle underline represents the deletion, as follows. In addition, the marked deployment information is sent to auditors.
Fourthly, entering a Kubernetes Objects template stage after receiving an examination passing message sent by an auditor, rendering Kubernetes Objects templates by using the marked deployment information, and generating a YAML file, wherein the steps are as follows:
fifth, YAML file is executed through Kubernetes API SERVER, and Kubernetes Objects is created.
And sixthly, checking the service state through the WebSocket, wherein the service state is Running (namely normal), and completing the creation of the configuration, namely completing the release.
And seventhly, recording the release state.
(II) modification of configuration
The first step is that the user modifies the configuration (as follows) through the service deployment information form and applies for deployment.
When monitoring a deployment event, creating a new deployment snapshot new, and caching the deployment snapshot old of the last effective deployment, wherein the deployment snapshot old is as follows:
Thirdly, taking the deployment snapshot in the last effective deployment as a source, taking the deployment snapshot at this time as a target, acquiring difference information of the two deployments (namely calculating a change set), and marking the difference information, wherein an underline represents the new addition, and a middle underline represents the deletion, as follows. In addition, the marked deployment information is sent to auditors.
Fourthly, entering a Kubernetes Objects template stage after receiving an examination passing message sent by an auditor, rendering Kubernetes Objects templates by using the marked deployment information, and generating a YAML file, wherein the steps are as follows:
Fifth, the YAML file is executed through the Kubernetes API SERVER to update Kubernetes Objects.
And sixthly, checking the service state through the WebSocket, wherein the service state is Running (namely normal), and finishing updating the configuration, namely finishing release.
And seventhly, recording the release state.
(III) delete configuration
The first step is that the user modifies the configuration (as follows) through the deployment information form and applies for deployment.
When monitoring a deployment event, creating a new deployment snapshot new, and caching the deployment snapshot old of the last effective deployment, wherein the deployment snapshot old is as follows:
Thirdly, taking the deployment snapshot in the last effective deployment as a source, taking the deployment snapshot at this time as a target, acquiring difference information of the two deployments (namely calculating a change set), and marking the difference information, wherein an underline represents the new addition, and a middle underline represents the deletion, as follows. In addition, the marked deployment information is sent to auditors.
Fourthly, entering a Kubernetes Objects template stage after receiving an examination passing message sent by an auditor, rendering Kubernetes Objects templates by using the marked deployment information, and generating a YAML file, wherein the steps are as follows:
And fifthly, deleting Kubernetes Objects by executing YAML file through Kubernetes API SERVER.
And sixthly, checking the service state through the WebSocket, wherein the service state is Running (namely normal), and deleting the configuration is completed, namely the release is completed.
And seventhly, recording the release state.
(IV) Modify configuration failure, rollback
The first step is that the user modifies the configuration (as follows) through the deployment information form and applies for deployment.
When monitoring a deployment event, creating a new deployment snapshot new, and caching the deployment snapshot old of the last effective deployment, wherein the deployment snapshot old is as follows:
Thirdly, taking the deployment snapshot in the last effective deployment as a source, taking the deployment snapshot at this time as a target, acquiring difference information of the two deployments (namely calculating a change set), and marking the difference information, wherein an underline represents the new addition, and a middle underline represents the deletion, as follows. In addition, the marked deployment information is sent to auditors.
Fourthly, entering a Kubernetes Objects template stage after receiving an examination passing message sent by an auditor, rendering Kubernetes Objects templates by using the marked deployment information, and generating a YAML file, wherein the steps are as follows:
Fifth, the YAML file is executed through the Kubernetes API SERVER to update Kubernetes Objects.
And sixthly, checking the service state through the WebSocket, and executing the rollback operation if the service state is Fail (i.e. abnormal).
And seventhly, exchanging the source and the target of the difference information of the two deployments obtained in the deployment process, namely taking the deployment snapshot of the executed part in the current deployment snapshot as the source and taking the deployment snapshot of the part in the last effective deployment as the target, obtaining the difference information of the two deployments, and marking the difference information, wherein the underline represents the new addition, the middle-underline represents the deletion, and the method is as follows. When the rollback is executed, the marked deployment information is not required to be sent to an auditor for audit.
Step eight, entering Kubernetes Objects a template stage, and rendering Kubernetes Objects the template by using the marked deployment information to generate a YAML file, wherein the steps are as follows:
ninth, the YAML file is executed through the Kubernetes API SERVER, and Kubernetes Objects is updated, so that rollback is completed.
And tenth, recording the rollback state.
According to the application deployment method, when the application is deployed, the current deployment information of the application and the difference information of the deployment information of the previous effective deployment of the application are firstly acquired. The modified resources under the modified service are then redeployed based on the difference information. That is, the invention can realize the redeployment of the application by only redeploying the modified resource. And when the application is deployed, if the abnormality occurs in the middle of the deployment, the invention can acquire the difference information between the current deployment information of the redeployed service and the deployment information of the previous effective deployment based on the current deployment information of the application and the deployment information of the previous effective deployment, and based on the difference information, the invention can realize rollback of the application only by executing rollback on the redeployed resource. Therefore, when the application is deployed and rolled back, the invention realizes the update of the minimum granularity, and is convenient and quick.
Further, after the difference information of the current deployment information of the application and the deployment information of the previous effective deployment is obtained, the current deployment information of the application and the deployment information of the previous effective deployment are sent to an auditing end for auditing, and the application is redeployed based on the difference information only after the auditing end passes. Therefore, the invention can ensure the accuracy of the application deployment information, thereby reducing the error rate of application release.
In addition, the invention provides a visual service deployment information interface, and a user can deploy the application by filling a small amount of deployment data such as application names and the like on the interface, so that the requirement on deployment personnel is reduced.
The various techniques described herein may be implemented in connection with hardware or software or, alternatively, with a combination of both. Thus, the methods and apparatus of the present invention, or certain aspects or portions of the methods and apparatus of the present invention, may take the form of program code (i.e., instructions) embodied in tangible media, such as removable hard drives, U-drives, floppy diskettes, CD-ROMs, or any other machine-readable storage medium, wherein, when the program is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the invention.
In the case of program code execution on programmable computers, the computing device will generally include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. The processor is configured to execute the application deployment method of the present invention according to instructions in the program code stored in the memory.
By way of example, and not limitation, readable media comprise readable storage media and communication media. The readable storage medium stores information such as computer readable instructions, data structures, program modules, or other data. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. Combinations of any of the above are also included within the scope of readable media.
In the description provided herein, algorithms and displays are not inherently related to any particular computer, virtual system, or other apparatus. Various general-purpose systems may also be used with examples of the invention. The required structure for a construction of such a system is apparent from the description above. In addition, the present invention is not directed to any particular programming language. It will be appreciated that the teachings of the present invention described herein may be implemented in a variety of programming languages, and the above description of specific languages is provided for disclosure of enablement and best mode of the present invention.
In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
It should be appreciated that in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim.
Those skilled in the art will appreciate that the modules or units or components of the devices in the examples disclosed herein may be arranged in a device as described in this embodiment, or alternatively may be located in one or more devices different from the devices in this example. The modules in the foregoing examples may be combined into one module or may be further divided into a plurality of sub-modules.
Those skilled in the art will appreciate that the modules in the apparatus of the embodiments may be adaptively changed and disposed in one or more apparatuses different from the embodiments. The modules or units or components of the embodiments may be combined into one module or unit or component and, furthermore, they may be divided into a plurality of sub-modules or sub-units or sub-components. Any combination of all features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or units of any method or apparatus so disclosed, may be used in combination, except insofar as at least some of such features and/or processes or units are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings), may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features but not others included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments.
Furthermore, some of the embodiments are described herein as methods or combinations of method elements that may be implemented by a processor of a computer system or by other means of performing the functions. Thus, a processor with the necessary instructions for implementing the described method or method element forms a means for implementing the method or method element. Furthermore, the elements of the apparatus embodiments described herein are examples of apparatus for performing the functions performed by the elements for the purpose of practicing the invention.
As used herein, unless otherwise specified the use of the ordinal terms "first," "second," "third," etc., to describe a general object merely denote different instances of like objects, and are not intended to imply that the objects so described must have a given order, either temporally, spatially, in ranking, or in any other manner.
While the invention has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of the above description, will appreciate that other embodiments are contemplated within the scope of the invention as described herein. Furthermore, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter. Accordingly, many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the appended claims. The disclosure of the present invention is intended to be illustrative, but not limiting, of the scope of the invention, which is defined by the appended claims.
Claims (5)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210532268.4A CN115033250B (en) | 2022-01-24 | 2022-01-24 | Application deployment method, computing device and readable storage medium |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210077296.1A CN114138285B (en) | 2022-01-24 | 2022-01-24 | Application deployment method, computing device and readable storage medium |
| CN202210532268.4A CN115033250B (en) | 2022-01-24 | 2022-01-24 | Application deployment method, computing device and readable storage medium |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210077296.1A Division CN114138285B (en) | 2022-01-24 | 2022-01-24 | Application deployment method, computing device and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115033250A CN115033250A (en) | 2022-09-09 |
| CN115033250B true CN115033250B (en) | 2025-07-01 |
Family
ID=80381574
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210077296.1A Active CN114138285B (en) | 2022-01-24 | 2022-01-24 | Application deployment method, computing device and readable storage medium |
| CN202210532268.4A Active CN115033250B (en) | 2022-01-24 | 2022-01-24 | Application deployment method, computing device and readable storage medium |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210077296.1A Active CN114138285B (en) | 2022-01-24 | 2022-01-24 | Application deployment method, computing device and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN114138285B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN120029640A (en) * | 2023-11-21 | 2025-05-23 | 华为云计算技术有限公司 | Application update method and container management platform |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109814918A (en) * | 2019-01-24 | 2019-05-28 | 深圳市多元世纪信息技术股份有限公司 | Software deployment method and system, computer readable storage medium |
| CN112394961A (en) * | 2020-11-24 | 2021-02-23 | 平安普惠企业管理有限公司 | Data updating system, method, device, equipment and storage medium |
Family Cites Families (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9250866B2 (en) * | 2011-06-20 | 2016-02-02 | Ebay Inc. | Systems and methods for incremental software deployment |
| US9804835B2 (en) * | 2014-06-11 | 2017-10-31 | Microsoft Technology Licensing, Llc | Dynamic pacing for service upgrades |
| CN109814901A (en) * | 2018-12-29 | 2019-05-28 | 中兴智能交通股份有限公司 | A kind of O&M method that automatically dispose application may be implemented |
| CN110096284B (en) * | 2019-04-19 | 2023-06-02 | 北京金山云网络技术有限公司 | A method, device, electronic device and storage medium for visually publishing software |
| CN110336695A (en) * | 2019-06-21 | 2019-10-15 | 威富通科技有限公司 | A kind of method and server of deployment and maintenance application |
| US11288055B2 (en) * | 2020-02-18 | 2022-03-29 | International Business Machines Corporation | Model-based differencing to selectively generate and deploy images in a target computing environment |
| CN111666080B (en) * | 2020-04-28 | 2024-05-03 | 平安科技（深圳）有限公司 | Micro service cluster deployment method and device, computer equipment and storage medium |
| CN111694750B (en) * | 2020-06-29 | 2024-10-15 | 深圳前海微众银行股份有限公司 | A method and device for constructing a software testing environment |
| CN112328295B (en) * | 2020-11-25 | 2024-09-24 | 昆山丘钛光电科技有限公司 | Software updating method and device |
| CN112882738A (en) * | 2021-03-22 | 2021-06-01 | 亿企赢网络科技有限公司 | Configuration information updating method and device under micro-service architecture and electronic equipment |
-
2022
- 2022-01-24 CN CN202210077296.1A patent/CN114138285B/en active Active
- 2022-01-24 CN CN202210532268.4A patent/CN115033250B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109814918A (en) * | 2019-01-24 | 2019-05-28 | 深圳市多元世纪信息技术股份有限公司 | Software deployment method and system, computer readable storage medium |
| CN112394961A (en) * | 2020-11-24 | 2021-02-23 | 平安普惠企业管理有限公司 | Data updating system, method, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114138285A (en) | 2022-03-04 |
| CN115033250A (en) | 2022-09-09 |
| CN114138285B (en) | 2022-07-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9354987B2 (en) | Systems and methods for out-of-band backup and restore of hardware profile information | |
| CN109445861B (en) | System starting method, device, computer device and storage medium | |
| US11030047B2 (en) | Information handling system and method to restore system firmware to a selected restore point | |
| WO2019148722A1 (en) | Electronic device, data migrating and calling method and storage medium | |
| CN113032032B (en) | System management method and device, computing equipment and readable storage medium | |
| KR20110086732A (en) | Application Recovery Points | |
| CN114610337B (en) | A multi-system installation method, computing device and storage medium | |
| CN113076170B (en) | Remote assistance method, system, device, computing equipment and storage medium | |
| JP2016058006A (en) | Information processing device and program | |
| CN116566811A (en) | Cluster deployment method, computing device and readable storage medium | |
| CN110209420A (en) | A kind of method and device updating bootstrap loader | |
| CN113157347A (en) | Automatic probe deployment method, electronic device and storage medium | |
| CN115033250B (en) | Application deployment method, computing device and readable storage medium | |
| CN112416379B (en) | Application program installation method and device, computing equipment and readable storage medium | |
| CN109766084B (en) | Custom development method, apparatus, computer equipment and storage medium for payment application | |
| CN103106086B (en) | Operating system disposal route and system | |
| CN105426272B (en) | Application program backup method and device | |
| CN114490294B (en) | A system performance testing method, device and computing equipment for application software | |
| CN114064361A (en) | Data writing method executed in backup related operation and backup gateway system | |
| CN110968569A (en) | Database management method, database management device, and storage medium | |
| CN109828752B (en) | Project code automatic generation method, device, computer equipment and storage medium | |
| CN113505026B (en) | Method, device and equipment for verifying backup data and storage medium | |
| CN115145644A (en) | Hardware self-adaption method and device | |
| CN113434370A (en) | Server cluster deployment method and device, computing equipment and storage medium | |
| CN113867825B (en) | Multi-system operation method, computing equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |