CN117931218A - Soft load installation method, device, electronic device and storage medium - Google Patents

Abstract

The embodiment of the present application provides a method, device, electronic device and computer-readable storage medium for installing a soft load, and relates to the field of grayscale release technology in software engineering. The method includes: displaying a soft load management interface, the soft load management interface includes a first input box; in response to the first input box, inputting a soft load installation package identifier, installation script parameter information and a host identifier, downloading a soft load installation package corresponding to the soft load installation package identifier from an object storage tool, and sending the soft load installation package to a host corresponding to the host identifier, the soft load installation package including a first installation script for the soft load; modifying the first installation script according to the installation script parameter information to obtain a second installation script for the soft load; instructing the host to execute the second installation script to install the soft load. The embodiment of the present application instructs the host to execute the second installation script and install the soft load through the terminal, thereby realizing the automatic installation of the soft load and improving the efficiency of the soft load installation process.

Description

Soft load installation method, device, electronic device and storage medium

Technical Field

The present application relates to the field of grayscale release technology. Specifically, the present application relates to a method, device, electronic device and computer-readable storage medium for automatic installation of soft loads.

Background technique

When upgrading applications on the server, you need to upload the application source code or package to the server, then stop the old version service and start the new version. However, this simple release method has two problems. On the one hand, the service is temporarily interrupted during the new version upgrade process. On the other hand, if there is a problem with the new version and the upgrade fails, it is very troublesome to roll back, which can easily cause longer service unavailability.

Grayscale release is a release method to solve the above problems. After the grayscale release begins, a new version of the application is started first, but the traffic is not directly switched over. Instead, the tester conducts an online test on the new version. If there is no problem, a small amount of user traffic can be imported to the new version. When it is confirmed that the new version runs well, more traffic is gradually imported to the new version until all traffic is switched to the new version. Finally, the remaining old version services are closed to complete the grayscale release. If a problem is found in the new version during the grayscale release process, the traffic is immediately switched back to the old version. In this way, the negative impact will be controlled to a minimum.

In the prior art, grayscale release is achieved through software-based load balancing (soft load), but the current mainstream technical solutions are all manual installation and deployment of soft load, which is time-consuming, has low installation efficiency, and is prone to installation failures due to operational errors.

Summary of the invention

The embodiments of the present application provide a method, device, electronic device and computer-readable storage medium for installing a soft load, which can solve the above-mentioned problems of the prior art. The technical solution is as follows:

According to a first aspect of an embodiment of the present application, a method for installing a soft load is provided, the method comprising:

Displaying a soft load management interface, wherein the soft load management interface includes a first input box;

In response to inputting a soft load installation package identifier, installation script parameter information, and a host identifier in the first input box, downloading the soft load installation package corresponding to the soft load installation package identifier from the object storage tool, and sending the soft load installation package to the host corresponding to the host identifier, wherein the soft load installation package includes a first installation script of the soft load;

Modify the first installation script according to the installation script parameter information to obtain a second installation script for the soft load;

Instruct the host to execute the second installation script to install the soft load.

According to a second aspect of an embodiment of the present application, a soft load installation device is provided, the device comprising:

A display module, used to display a soft load management interface, wherein the soft load management interface includes a first input box;

a response module, configured to respond to the input of a soft load installation package identifier, installation script parameter information, and a host identifier in the first input box, and download the soft load installation package corresponding to the soft load installation package identifier from the object storage tool to the host corresponding to the host identifier according to the soft load installation package identifier, the installation script parameter information, and the host identifier, wherein the soft load installation package includes a first installation script of the soft load;

An obtaining module, used to modify the first installation script according to the installation script parameter information to obtain a second installation script of the soft load;

An instruction module is used to instruct the host to execute the second installation script to install the soft load.

According to a third aspect of an embodiment of the present application, an electronic device is provided, which includes a memory, a processor, and a computer program stored in the memory, and the processor executes the computer program to implement the steps of the above method.

According to a fourth aspect of an embodiment of the present application, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above method are implemented.

According to a fifth aspect of an embodiment of the present application, a computer program product is provided, including a computer program, which implements the steps of the above method when the computer program is executed by a processor.

The beneficial effects of the technical solution provided by the embodiment of the present application are:

By displaying the soft load management interface, a first input box is provided to the operation and maintenance personnel, so that the operation and maintenance personnel can clearly enter the soft load installation package identifier corresponding to the soft load to be installed, the host identifier of the host on which the soft load needs to be installed, and the installation script parameter information of the soft load in the first input box; by responding to the soft load installation package identifier, the installation script parameter information and the host identifier entered in the first input box, the soft load installation package corresponding to the soft load installation package identifier is downloaded, and the soft load installation package is sent to the host corresponding to the host identifier, so that there is no need to manually operate the host to download the soft load installation package, thereby improving the efficiency of downloading the soft load installation package; modifying the first installation script in the soft load installation package through the installation script parameter information in the first input box to generate a second installation script; by instructing the host to execute the second installation script, the host installs the soft load by executing the second installation script, thereby achieving the installation of the soft load without manually executing the installation command, thereby improving the efficiency of the soft load installation process.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in describing the embodiments of the present application are briefly introduced below.

FIG1 is a schematic diagram of a system architecture for implementing soft load installation provided in an embodiment of the present application;

FIG2 is a schematic diagram of a flow chart of a method for installing a soft load provided in an embodiment of the present application;

FIG3 is a schematic diagram of a file list of a soft load provided in an embodiment of the present application;

FIG4 is a schematic diagram of a flow chart of modifying a configuration file of a load balancing software provided in an embodiment of the present application;

FIG5 is a schematic diagram of a flow chart of another method for installing a soft load provided in an embodiment of the present application;

FIG6 is a schematic diagram of an interactive flow of a method for installing a soft load provided in an embodiment of the present application;

FIG7 is a schematic diagram of an interactive flow chart of another method for installing a soft load provided in an embodiment of the present application;

FIG8 is a schematic structural diagram of a soft load installation device provided in an embodiment of the present application;

FIG. 9 is a schematic diagram of the structure of an electronic device for installing a soft load provided in an embodiment of the present application.

Detailed ways

The embodiments of the present application are described below in conjunction with the drawings in the present application. It should be understood that the implementation methods described below in conjunction with the drawings are exemplary descriptions for explaining the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions of the embodiments of the present application.

It will be understood by those skilled in the art that, unless specifically stated, the singular forms "one", "said", and "the" used herein may also include plural forms. It should be further understood that the terms "including" and "comprising" used in the embodiments of the present application refer to that the corresponding features can be implemented as the presented features, information, data, steps, operations, elements and/or components, but do not exclude the implementation as other features, information, data, steps, operations, elements, components and/or combinations thereof supported by the technical field. It should be understood that when we say that an element is "connected" or "coupled" to another element, the one element may be directly connected or coupled to the other element, or it may refer to that the one element and the other element establish a connection relationship through an intermediate element. In addition, the "connection" or "coupling" used herein may include wireless connection or wireless coupling. The term "and/or" used herein indicates at least one of the items defined by the term, for example, "A and/or B" may be implemented as "A", or as "B", or as "A and B".

In order to make the objectives, technical solutions and advantages of the present application more clear, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

First, several terms involved in this application are introduced and explained:

Grayscale release: In addition to the stable cluster in the production environment, deploy a small-scale grayscale cluster and introduce part of the traffic into the grayscale cluster through traffic control to perform grayscale verification before full production release. If the verification fails, all traffic can be immediately switched back to the existing stable cluster to cancel the grayscale release process. If the verification succeeds, the new version will be fully released and upgraded to the stable cluster in the production environment, that is, all traffic will be introduced into the new version to complete the grayscale release process.

If a product needs to be developed and launched quickly and the quality needs to be guaranteed, and the newly launched system needs to be able to quickly control the impact of any problems, then a grayscale release system needs to be designed. The grayscale release system can direct user traffic to the newly launched system according to its own configuration to quickly verify new functional modifications, and can also be restored immediately if problems occur.

Grayscale release refers to a release method that can smoothly transition during the software version release process. Assuming that the current software version is A and the new software version is B, when the software development company upgrades and releases a certain software version, the server controls some users to continue using version A, while other users start using version B; if there are no abnormalities when users use version B, all users will be gradually migrated to version B. This gradual transition release method can ensure the stability of the overall system.

Grayscale routing rules are a strategy for gradually pushing new versions to a subset of users during the software release process. Grayscale routing rules can determine which users can receive the new version based on different conditions to ensure the stability and reliability of the new version.

Load Balance: It means to balance the load (work tasks) and distribute them to multiple operation units, such as FTP servers, Web servers, enterprise core application servers and other major task servers, so as to complete the work tasks in a coordinated manner. Load balancing is built on the original network structure. It provides a transparent, cheap and effective method to expand the bandwidth of servers and network devices, enhance network data processing capabilities, increase throughput, and improve network availability and flexibility.

Soft load: refers to software load balancing. Install the corresponding load balancing software on the system server and make relevant configurations to achieve the purpose of load balancing. It is based on a specific usage environment, has simple configuration, flexible use, and low cost. It can solve most demand problems. Commonly used software includes: Nginx.

Hard load: refers to hardware load balancing, which is to install a load balancing device directly between the server and the external network. Commonly used hardware devices include: F5.

Nginx: It is a high-performance Hypertext Transfer Protocol (HTTP) and reverse proxy server, as well as an IMAP/POP3/SMTP proxy server. It is the most widely used HTTP soft load balancer, with high performance, stability, rich feature set, sample configuration files and low system resource consumption. It uses reverse proxy technology. The proxy server accepts connection requests from the Internet, then forwards the requests to the server on the internal network, and returns the results obtained from the server to the client requesting the connection on the Internet. At this time, the proxy server appears to the outside as a server. Reverse proxy load balancing technology is to dynamically forward connection requests from the Internet to multiple servers on the internal network in a reverse proxy manner for processing, thereby achieving the purpose of load balancing.

OpenResty (also known as ngx_openresty) is a full-featured web application server based on Nginx that integrates Nginx with a set of additional modules and the Lua scripting language to provide high-performance web application development and scalability.

Lua: It is a lightweight scripting language written in standard C language and open in source code form. It is designed to be embedded in applications to provide flexible expansion and customization capabilities for applications.

Java Secure Channel (JSch) is a pure Java SSH2 client for connecting to SSH servers. It provides functions for communicating with SSH servers, including file transfer, remote command execution, and remote server information acquisition. Using JSch, you can interact with SSH servers in Java applications to implement remote command execution, file transfer, and other functions. It supports multiple SSH protocol versions and provides a rich API, making communication with SSH servers simple and powerful.

The soft load installation method, device, electronic device, computer-readable storage medium and computer program product provided in the present application are intended to solve the above technical problems in the prior art.

The following describes several exemplary embodiments to illustrate the technical solutions of the embodiments of the present application and the technical effects produced by the technical solutions of the present application. It should be noted that the following embodiments can refer to, draw on or combine with each other, and the same terms, similar features and similar implementation steps in different embodiments will not be described repeatedly.

1 is a schematic diagram of a system architecture for implementing the installation of a soft load provided in an embodiment of the present application, wherein the implementation environment includes a terminal 101 and a host 102. The terminal 101 and the host 102 can be directly or indirectly connected via wired or wireless communication, which is not limited in the embodiment of the present application.

In some embodiments, the terminal 101 is a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, an intelligent voice interaction device, a smart home appliance, a vehicle-mounted terminal, etc., but is not limited thereto. The host 102 can be a Linux host or a virtual machine, but is not limited thereto. The terminal 101 is installed with a soft load management program, and the visual interface of the soft load management program is a soft load management interface. The soft load management interface includes a first input box for inputting a soft load installation package identifier, installation script parameter information, and a host identifier of the host 102. The terminal 101 downloads the soft load installation package corresponding to the soft load installation package identifier in the first input box to the local computer, and then sends the soft load installation package to the host 102. The terminal 101 can modify the first installation script in the soft load installation package in the host 102 according to the installation script parameter information in the first input box, generate a second installation script, and send a command to execute the second installation script to the host 102, so that the host 102 installs the soft load.

Those skilled in the art will appreciate that the number of the above terminals may be more or less. For example, the above terminal may be only one, or the above terminals may be dozens or hundreds, or more. The embodiment of the present application does not limit the number of terminals and device types.

In some embodiments, the host 102 is an independent physical host, or a host cluster or distributed system composed of multiple physical hosts, or a cloud host that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. The host 102 is used to provide background services for applications that support image acquisition. In some embodiments, the host 102 undertakes the main computing work and the terminal 101 undertakes the secondary computing work; or, the host 102 undertakes the secondary computing work and the terminal 101 undertakes the main computing work; or, the host 102 and the terminal 101 use a distributed computing architecture for collaborative computing.

For example, the installation method of the soft load in the embodiment of the present application can be completed by the terminal. The following describes the solution in the embodiment of the present application with the terminal as the execution subject.

An embodiment of the present application provides a content recommendation method, as shown in FIG. 2 , the method includes S101 , S102 , S103 and S104 .

S101. Display a soft load management interface, where the soft load management interface includes a first input box.

In an embodiment of the present application, the soft load management interface displayed by the terminal includes a first input box. When the operation and maintenance personnel want to install the soft load on the host, the soft load installation package identifier corresponding to the soft load and the host identifier of the host are entered in the first input box of the soft load management interface. The soft load installation package identifier can be the version number of the soft load installation package, and the host identifier can be the IP address of the host. In order to enable the host to automatically install the soft load, the installation script parameter information is entered in the first input box, so that the host can install the soft load according to the installation script parameter information. In some embodiments, if the host requires a user name and password to log in, the host identifier also includes the user name and password of the host.

S102, in response to inputting a soft load installation package identifier, installation script parameter information and a host identifier in the first input box, downloading the soft load installation package corresponding to the soft load installation package identifier from the object storage tool, and sending the soft load installation package to the host corresponding to the host identifier, wherein the soft load installation package includes a first installation script for the soft load.

In an embodiment of the present application, after the terminal obtains the soft load installation package identifier, installation script parameter information, and host identifier information input by the operation and maintenance personnel in the first input box, the terminal downloads the soft load installation package corresponding to the soft load installation package identifier from the object storage tool, and sends the soft load installation package to the host corresponding to the host identifier. In an embodiment of the present application, the object storage tool may be MonIo, and the terminal downloads the soft load installation package by calling the HTTP interface of the object storage tool, and the terminal downloads the downloaded soft load installation package to the host by calling the JSch interface.

In an embodiment of the present application, the soft load management interface includes a host identification selection button, a soft load installation package identification selection button, and an installation script parameter information selection button. The operation and maintenance personnel can enter information in the first input box by editing input or clicking input, or by a combination of the two input methods.

As an optional embodiment, after the terminal downloads the soft load installation package, the soft load installation package can be stored in the terminal. When the soft load needs to be installed on other hosts, the terminal does not need to download it again from the object storage tool, thereby improving the efficiency of installing soft loads on multiple hosts.

S103: Modify the first installation script according to the installation script parameter information to obtain a second installation script of the soft load.

Considering that the prior art requires manual execution of installation commands when installing soft loads, the cumbersome process causes the problem of low efficiency in installing soft loads. In an embodiment of the present application, the soft load installation package includes a first installation script, and the first installation script is modified by the installation script parameter information in the first input box. By calling the JSch interface, the first installation script is modified according to the installation script parameter information, and the modified first installation script is used as the second installation script. The second installation script enables the host to automatically execute the installation process without manually executing the installation command.

S104: Instruct the host to execute a second installation script to install the soft load.

In the embodiment of the present application, the terminal sends a startup instruction to the host by calling the Jhch interface, instructing the host to execute the second installation script to install the soft load on the host. The second installation script is generated by the installation script parameter information in the first input box to achieve automatic installation of the soft load. At the same time, according to the soft load installation method in the embodiment of the present application, it can also be used to update the soft load to be updated in the host and to install the soft load on multiple hosts.

By displaying the soft load management interface, a first input box is provided to the operation and maintenance personnel, so that the operation and maintenance personnel can clearly enter the soft load installation package identifier corresponding to the soft load to be installed, the host identifier of the host on which the soft load needs to be installed, and the installation script parameter information of the soft load in the first input box; by responding to the soft load installation package identifier, the installation script parameter information and the host identifier entered in the first input box, the soft load installation package corresponding to the soft load installation package identifier is downloaded, and the soft load installation package is sent to the host corresponding to the host identifier, so that there is no need to manually operate the host to download the soft load installation package, thereby improving the efficiency of downloading the soft load installation package; modifying the first installation script in the soft load installation package through the installation script parameter information in the first input box to generate a second installation script; by instructing the host to execute the second installation script, the host installs the soft load by executing the second installation script, thereby achieving the installation of the soft load without manually executing the installation command, thereby improving the efficiency of the soft load installation process.

Based on the above embodiment, as an optional embodiment, the soft load installation package in the embodiment of the present application includes load balancing software and a configuration management program, the load balancing software is used for load balancing, and the configuration management program is used to register the soft load;

Instructing the host to execute the second installation script to install the soft load, including instructing the host to execute a startup command of the second installation script and start a configuration management program and a load balancing software;

Start with configuration management program and load balancing software, followed by:

S201, receiving registration information of a soft load sent by a host through a configuration management program, where the registration information includes a host identifier;

S202, registering the soft load according to the registration information;

S203: Display the registration information on the soft load management interface.

In an embodiment of the present application, after the terminal sends an execution instruction to execute the second installation script to the host, the host responds to the execution instruction and executes the second installation script. The second installation script includes a startup command. Through the startup command, the host can start the configuration management program and load balancing software in the soft load installation package. In an embodiment of the present application, the load balancing software is OpenResty, and the configuration management program is a program written in the Golong language, which can obtain the registration information of the soft load and modify the configuration file of the soft load.

In the embodiment of the present application, after starting the configuration management program, a configuration file and a script file of the configuration management program are created, wherein the script file can be a script file written in Lua language, and the terminal identifier is written into the script file, and the terminal identifier can be the IP of the terminal, so that the configuration management program can call the HTTP interface of the terminal according to the IP of the terminal. In the embodiment of the present application, the configuration management program can be started first, and then the load balancing software can be started. After the load balancing software is started, all the configuration information required by the soft load is set, that is, the installation of the soft load is realized.

In the embodiment of the present application, after the host starts the load balancing software, the configuration management program calls the HTTP interface of the terminal through the identification information of the terminal and sends the registration information of the soft load to the terminal. The terminal receives the registration information sent by the host through the configuration management program, and the registration information includes the host identification. The soft load is registered through the registration information. The registration can be the registration information of the soft load created in the terminal, and the registration content includes the host identification of the host where the soft load is located.

In an embodiment of the present application, after the terminal registers the soft load, the registration information is displayed through the soft load management interface so that the operation and maintenance personnel can view the registration information.

In an embodiment of the present application, the configuration management program sends registration information to the terminal in real time, that is, the host continuously sends registration information to the terminal through the configuration management program at a preset time period, and the terminal updates the registration information of the soft load management interface according to the registration information received in real time. Therefore, the terminal in the embodiment of the present application can synchronize the registration information of the soft load, so that the operation and maintenance personnel can manage the soft load according to the registration information.

At the same time, the terminal in the embodiment of the present application can receive the registration information of the soft loads on multiple hosts, and can display the registration information of the soft loads on multiple hosts, which is convenient for operation and maintenance personnel to manage the soft loads on multiple hosts through the terminal.

In the embodiment of the present application, by instructing the host to start the configuration management program and the load balancing software in sequence, all script files and configuration files required for installing the soft load are generated, thereby realizing the installation of the soft load; at the same time, considering the problem that the operation and maintenance personnel can only view the registration information of the soft load by entering a query command to the host, the registration information of the soft load sent by the configuration management program is received, the soft load is registered, and the registration information is displayed on the soft load management interface, so that the operation and maintenance personnel can intuitively obtain the registration information of the soft load without manually entering a query command.

Based on the above embodiments, as an optional embodiment, the soft load management interface further includes a second input box, the second input box is used to input the grayscale routing rule, the input grayscale routing rule is used to instruct the host to execute the grayscale release task, the grayscale release task is stored in the terminal, and the configuration management program is also used to modify the configuration file of the load balancing software;

The registration information is displayed on the soft load management interface, followed by:

S301. In response to inputting grayscale routing rules in the second input box, the grayscale routing rules in the second input box are sent to the configuration management program of the host, so that the host can modify the configuration file of the load balancing software through the configuration management program, and execute the grayscale publishing task according to the grayscale routing rules through the load balancing software.

In an embodiment of the present application, the soft load management interface also includes a second input box, through which the grayscale routing rules written by the operation and maintenance personnel are received. It should be understood that the soft load in the embodiment of the present application can realize the task of grayscale release based on the load balancing function, and the specific grayscale release method is determined according to the grayscale routing rules.

In the prior art, the operation and maintenance personnel need to manually write the grayscale routing rules into the configuration file of the soft load, and the manual modification is inefficient and prone to errors. In the embodiment of the present application, the configuration management program has the function of modifying the soft load configuration file, that is, the configuration management program can also modify the configuration file of the load balancing software.

In an embodiment of the present application, the terminal registers the soft load and displays the registration information on the soft load management interface. In order for the soft load to perform the grayscale release task, the operation and maintenance personnel enter the corresponding grayscale routing rules in the second input box of the soft load management interface. The terminal responds to the grayscale routing rules in the second input box and sends the grayscale routing rules to the configuration management program on the host. The configuration management program modifies the configuration file of the load balancing software according to the received grayscale routing rules. In an embodiment of the present application, the terminal sends the grayscale routing rules to the configuration management program by calling the HTTP interface. The load balancing software can be OpenResty, and the configuration file of OpenResty is the nginx.conf file. The configuration management program modifies the configuration file of the soft load nginx through the lua script file in the soft load.

Based on the above embodiments, as an optional embodiment, the configuration management program for sending the grayscale routing rule in the second input box to the host in the embodiment of the present application also includes:

S401. Instruct the host to modify the configuration file of the load balancing software through the configuration management program according to the grayscale publishing task, and establish a corresponding relationship between the grayscale publishing task and the soft load in the host.

In the embodiment of the present application, by establishing a corresponding relationship between the publishing task and the soft load in the host, the terminal can send the grayscale routing rules to the configuration management program in the corresponding soft load. According to the grayscale publishing task, the host is instructed to modify the configuration file of the load balancing software through the configuration management program, for example,

As shown in Figure 3, it exemplarily shows the file list of the soft load provided in the embodiment of the present application, wherein main.go is the configuration management program, openresty is the load balancing software in the embodiment of the present application, nginx.conf is the configuration file of openresty, start.sh is the second installation script in the embodiment of the present application, and the remaining files are configuration modification templates of the lua script of the configuration management program and the configuration file of the load balancing software in the embodiment of the present application.

As shown in Figure 4, it exemplarily shows a flow chart of the configuration management program provided in an embodiment of the present application to modify the configuration file of the load balancing software. It can be seen from Figure 4 that the configuration management program modifies the servername attribute in the configuration file of the load balancing software according to the system application information in the grayscale release task, modifies the location module in the configuration file of the load balancing software according to the application context configuration information in the grayscale release task, and modifies the upstream module in the configuration file of the load balancing software according to the rule configuration in the route routing configuration in the grayscale release task, the upstream configuration and the application domain name domain information.

It should be understood that multiple grayscale release tasks can be stored in the terminal, and there can be multiple hosts with soft loads installed. Therefore, a correspondence between the grayscale release tasks and the soft loads is established. The terminal can determine the configuration management program sent to the corresponding soft load when sending the grayscale routing rules corresponding to the grayscale release tasks.

Based on the above embodiments, as an optional embodiment, the registration information also includes a soft load identifier corresponding to the soft load, an architecture type of the soft load, a node type of the host, and a status of the soft load. The architecture type of the soft load includes a cluster architecture, an active-standby architecture, and a stand-alone architecture. The node type of the host includes a cluster node, a master node, a standby node, and a stand-alone node.

The soft load identifier, soft load architecture type and host node type in the registration information are obtained by the host from the installation script parameter information.

In an embodiment of the present application, the terminal receives registration information sent by the configuration management program, and the registration information includes a soft load identifier of the soft load, an architecture type of the soft load, a node type of the host, and a status of the soft load. The soft load identifier of the soft load is a unique code of the soft load used to identify the soft load during the interaction between the terminal and the host. The code can be a string type. The architecture type of the soft load includes a cluster architecture, a master-slave architecture, and a stand-alone architecture. The node type of the host includes a cluster node, a master node, a standby node, and a stand-alone node. The status of the soft load is divided into an available state and an unavailable state. It should be understood that the node type of the host depends on the architecture type of the soft load. If the architecture type of the soft load is a cluster architecture, the node type of the host is a cluster node. If the architecture type of the soft load is a master-slave architecture, the node type of the host is a master node or a standby node. If the architecture type of the soft load is a single-click architecture, the node type of the host is a single-click node.

In the embodiment of the present application, the installation script parameter information input by the operation and maintenance personnel into the first input box includes the soft load identifier of the soft load, the architecture type of the soft load, the identifier of the terminal, the host identifier of the host, and the node type of the host. The input method of the operation and maintenance personnel can be at least one of edit input and click input, and the soft load management interface has a selection button for the relevant installation script parameter information.

It should be understood that the configuration management program obtains registration information through a preset script file. The host executes the script file so that the configuration management program can obtain the soft load identifier, the architecture type of the soft load, the node type of the host and other information from the installation script parameter information. The configuration management program includes a query command for viewing the status of the soft load, so the status information of the soft load can also be obtained. Therefore, by obtaining the second installation script through the installation script parameter information, the shared parameter information between the terminal and the host can be unified.

The embodiment of the present application receives the installation script parameter information and generates the second installation script according to the installation script parameter information, so that the configuration management program on the host can obtain the soft load identification, the architecture type host identification of the soft load and the node type of the host, and the registration information is displayed on the soft load management interface, so that the operation and maintenance personnel can correspond the gray release task with the soft load according to the registration information, that is, for a certain gray release task, the operation and maintenance personnel can determine a soft load according to the registration information of multiple soft loads on the soft load management interface, and establish a corresponding relationship between the gray release task and the soft load. At the same time, considering that the prior art requires the operation and maintenance personnel to enter a query command in the host to obtain the status of the soft load, the efficiency of obtaining the status of the soft load is low. Therefore, the registration information in the embodiment of the present application includes the status of the soft load, and the status information of the soft load is obtained by the configuration management program, and the status information of the soft load is displayed on the soft load management interface. If the status of the soft load is unavailable, the operation and maintenance personnel can check whether the soft load has a fault. If it is determined that a fault occurs, timely processing is performed, such as reinstalling the soft load to the host.

Based on the above embodiments, as an optional embodiment, the soft load management interface in the embodiment of the present application includes a third input box, and the third input box is used to input a pre-made soft load installation package and a corresponding soft load installation package identifier;

Download the soft load installation package corresponding to the soft load installation package identifier from the object storage tool, which also includes:

S601. In response to the soft load installation package and the corresponding soft load installation package identifier input in the third input box, store the soft load installation package and the corresponding soft load installation package identifier in an object storage tool.

In an embodiment of the present application, a soft load installation package is pre-made and uploaded to an object storage tool. The pre-made soft load installation package includes OpenResty, a configuration management program written in Golang language, and a first installation script file.

In an embodiment of the present application, the soft load management interface further includes a third input box, and the third input box is used for the operation and maintenance personnel to input a pre-made soft load installation package and a corresponding soft load installation package identifier. The terminal responds to the soft load installation package and the corresponding soft load installation package identifier in the third input box, and uploads the soft load installation package and the soft load installation package identifier to the object storage tool by calling the HTTP interface of the object storage tool, so that the object storage tool stores the soft load installation package and the corresponding soft load installation package identifier.

In the embodiment of the present application, a soft load installation package including a load balancing software and a configuration management program is produced, thereby realizing the installation, registration and execution of grayscale release tasks of the soft load during the interaction between the terminal and the host; the terminal storage space is saved by uploading the produced soft load balancing software to an object storage tool instead of directly storing it in the terminal; and at the same time, the corresponding soft load installation package identifier is saved when storing the soft load installation package, so that the terminal can download the corresponding soft load installation package according to the soft load installation package identifier in the first input box.

Based on the above embodiments, as an optional embodiment, the embodiment of the present application refers to instructing the host to execute the startup command of the second installation script to start the configuration management program and the load balancing software, including:

S701, instructing the host to determine whether there is a configuration management program to be updated that is running according to the startup command of the second installation script;

If there is a configuration management program to be updated that is running, then the configuration management program to be updated is stopped and the configuration management program is started;

If there is no configuration management program to be updated that is running, start the configuration management program;

S702, instructing the host to determine whether there is any load balancing software to be updated that is running according to the startup command of the second installation script;

If there is a configuration management program to be updated that is running, then the configuration management program to be updated is stopped and the configuration management program is started;

If there is no configuration management program to be updated that is running, the configuration management program is started.

In an embodiment of the present application, when the host starts the configuration management program and the load balancing software according to the second installation script, in order to prevent the problem that the host has previously installed other versions of the soft load, and the configuration management program in other versions, i.e., the configuration management program to be updated and the load balancing software, i.e., the load balancing software to be updated, are running, resulting in system failure due to repeated startup of the configuration management program and the load balancing software, in an embodiment of the present application, it is first determined whether there is a running configuration management program to be updated and a running load balancing software to be updated.

In an embodiment of the present application, if there is a configuration management program to be updated running in the host, the host first stops running the configuration management program to be updated according to the startup command in the second installation script, and then starts the configuration management program. If there is no configuration management program to be updated running in the host, the host directly starts the configuration management program to be updated. The configuration management program to be updated can be stopped by the "ps-ef|grep" and "kill" instructions in the startup command, and the configuration management program can be started by the "./main>ops.log&" instruction in the startup command.

In an embodiment of the present application, if there is a load balancing software to be updated running in the host, the host first stops running the load balancing software to be updated according to the startup command in the second installation script, and then starts the load balancing software. The running load balancing software to be updated can be stopped by the "./nginx-s stop" instruction in the startup command, and the load balancing software can be started by the "./nginx" in the startup command.

It should be understood that when there is no configuration management program to be updated and load balancing software to be updated running in the host, the instructions to stop running the configuration management program to be updated and the load balancing software to be updated in the startup command in the second installation script can also be executed, but the instructions at this time have no effect.

In an embodiment of the present application, the startup command includes a wait preset time instruction between the instruction to stop running the configuration management program to be updated and the instruction to start the configuration management program. It can be understood that the host cannot directly start the configuration management program after executing to stop running the configuration management program to be updated, and needs to wait for the host to shut down the process of running the configuration management program to be updated and delete the configuration file of the configuration management program to be updated. Similarly, the startup command also includes a wait preset time instruction between the instruction to stop running the load balancing software to be updated and the instruction to start the load balancing software, which is used for the host to shut down the process of running the load balancing software to be updated and delete the configuration file of the load balancing software to be updated. In addition, the startup command also includes a wait preset time instruction between the instruction to start the configuration management program and the instruction to stop running the load balancing software to be updated to meet the time requirements for generating the configuration file and script file of the configuration management program. For example, if the preset time is 2 seconds, the instruction can be "sleep2".

In the embodiment of the present application, the second installation script obtained according to the installation script parameter information can realize the start and stop of the load balancing software and the configuration management program. By judging whether there are configuration management programs and load balancing software to be updated in the host before starting the configuration management program and the load balancing software in the soft load, the occurrence of system failures caused by repeated starting of the configuration management program and the load balancing software is avoided.

As shown in FIG5 , it exemplarily shows a flow chart of another method for installing a soft load provided in an embodiment of the present application, which is executed by a terminal, and is specifically as follows:

S801, displaying a soft load management interface, where the soft load management interface includes a first input box, a second input box, and a third input box;

S802: In response to the soft load installation package and the corresponding soft load installation package identifier input in the third input box, store the soft load installation package and the corresponding soft load installation package identifier in an object storage tool;

S803: In response to inputting a soft load installation package identifier, installation script parameter information, and a host identifier in the first input box, downloading the soft load installation package corresponding to the soft load installation package identifier from the object storage tool;

S804, sending the soft load installation package to the host corresponding to the host identifier, where the soft load installation package includes a first installation script of the soft load;

S805, modifying the first installation script according to the installation script parameter information to obtain a second installation script for the soft load;

S806, instructing the host to execute the second installation script, instructing the host to execute the startup command of the second installation script, and starting the configuration management program and the load balancing software, and installing the soft load;

S807, receiving registration information of the soft load sent by the host through the configuration management program, where the registration information includes a host identifier;

S808, registering the soft load according to the registration information, and displaying the registration information on the soft load management interface;

S809, instructing the host to modify the configuration file of the load balancing software through the configuration management program according to the grayscale release task, and establishing a corresponding relationship between the grayscale release task and the soft load in the host;

S810. In response to inputting grayscale routing rules in the second input box, the grayscale routing rules in the second input box are sent to the configuration management program of the host, so that the host modifies the configuration file of the load balancing software through the configuration management program, and executes the grayscale publishing task according to the grayscale routing rules through the load balancing software.

It should be noted that the soft load installation method in the embodiment of the present application can not only be used for grayscale release tasks, but also solve other tasks based on soft loads, such as blue-green release.

As shown in Figure 6, it exemplarily shows an interactive flow diagram of a method for installing a soft load provided in an embodiment of the present application. Soft load management software is installed in the terminal, and the software includes a soft load management interface also called a web end and a soft load management program also called a server end. The soft load management interface is displayed on the terminal, and the soft load management program runs on the terminal. The configuration management program in the embodiment of the present application calls the terminal HTTP interface, which can be an HTTP interface for calling the load management program. The host starts the configuration management program and the load balancing software by executing the second installation script. The load balancing software can perform traffic distribution and has a load balancing function, which is used for grayscale release tasks.

Specifically, as shown in Figure 6, the soft load management program receives the soft load installation identifier, host identifier and installation script parameter information sent by the soft load management interface, downloads the soft load installation package in the object storage tool, sends the downloaded soft load installation package to the host, and modifies the first installation script of the soft load installation package in the host, records the modified first installation script as the second installation script, and instructs the host to execute the second installation script. The host receives the instruction of the soft load management program, executes the second installation script, and starts the configuration management program and the load balancing software respectively. After the configuration management program is started, the registration information of the soft load is sent to the soft load management program in real time. The soft load management program receives the registration information, registers the soft load, and sends the registration information to the soft load management interface. The soft load management interface displays the registration information, receives the grayscale routing rules edited by the operation and maintenance personnel on the page, and sends the grayscale routing rules to the soft load management program. The soft load management program sends the received grayscale routing rules to the configuration management program. The configuration management program modifies the configuration file of the load balancing software according to the grayscale routing rules. At this time, the load balancing software can implement the corresponding grayscale release task.

As shown in FIG. 7 , it exemplarily shows an interactive flow chart of another method for installing a soft load in an embodiment of the present application. In an embodiment of the present application, the grayscale control and display module includes a soft load management interface, the grayscale control and display module includes a soft load management program in a terminal, and the load balancing module includes a host. The grayscale control and display module sends the host identifier, the soft load installation package identifier, and the installation script parameter information to the grayscale control and display module. After the grayscale control and display module downloads the soft load installation package, it sends the soft load installation package to the load balancing module, and modifies the first installation script according to the installation script parameter information, instructs the load balancing module to execute the second installation script, and the load balancing module executes the installation script, starts the configuration management program and the load balancing program, and sends the registration information of the soft load to the grayscale control and display module. The grayscale control and display module registers the soft load according to the registration information, and sends the registration information to the grayscale control and display module. The grayscale control and display module displays the received registration information. An embodiment of the present application provides a soft load installation device, as shown in FIG. 8 , the soft load installation device may include: a display module 901, a response module 902, an acquisition module 903, and an indication module 904, wherein,

A display module 901 is used to display a soft load management interface, where the soft load management interface includes a first input box;

A response module 902 is used to respond to the input of the soft load installation package identifier, installation script parameter information and host identifier in the first input box, download the soft load installation package corresponding to the soft load installation package identifier from the object storage tool, and send the soft load installation package to the host corresponding to the host identifier, wherein the soft load installation package includes a first installation script of the soft load;

An acquisition module 903 is used to modify the first installation script according to the installation script parameter information to obtain a second installation script of the soft load;

The instruction module 904 is used to instruct the host to execute the second installation script to install the soft load.

The device of the embodiments of the present application can execute the method provided by the embodiments of the present application, and the implementation principles are similar. The actions performed by each module in the device of each embodiment of the present application correspond to the steps in the method of each embodiment of the present application. For the detailed functional description of each module of the device, please refer to the description in the corresponding method shown in the previous text, which will not be repeated here.

In an optional embodiment, an electronic device is provided, as shown in FIG. 9 , the electronic device 4000 shown in FIG. 9 includes: a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, such as through a bus 4002. Optionally, the electronic device 4000 may also include a transceiver 4004, which may be used for data interaction between the electronic device and other electronic devices, such as data transmission and/or data reception. It should be noted that in actual applications, the transceiver 4004 is not limited to one, and the structure of the electronic device 4000 does not constitute a limitation on the embodiments of the present application.

Processor 4001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. Processor 4001 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

The bus 4002 may include a path to transmit information between the above components. The bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus 4002 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, FIG9 only uses one thick line to represent, but does not mean that there is only one bus or one type of bus.

The memory 4003 may be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, Blu-ray disk, etc.), magnetic disk storage media, other magnetic storage devices, or any other medium that can be used to carry or store computer programs and can be read by a computer, without limitation herein.

The memory 4003 is used to store the computer program for executing the embodiment of the present application, and the execution is controlled by the processor 4001. The processor 4001 is used to execute the computer program stored in the memory 4003 to implement the steps shown in the above method embodiment.

The electronic device package may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. The electronic device shown in FIG9 is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

The embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps and corresponding contents of the aforementioned method embodiment can be implemented. Compared with the prior art, it can be implemented as follows: by displaying a soft load management interface, a first input box is provided to the operation and maintenance personnel, so that the operation and maintenance personnel can clearly enter the soft load installation package identifier corresponding to the soft load to be installed, the host identifier of the host on which the soft load needs to be installed, and the installation script parameter information of the soft load in the first input box; by responding to the soft load installation package identifier, the installation script parameter information and the host identifier entered in the first input box, the soft load installation package corresponding to the soft load installation package identifier is downloaded, and the soft load installation package is sent to the host corresponding to the host identifier, so that the host does not need to manually operate the host to download the soft load installation package, thereby improving the efficiency of downloading the soft load installation package; modifying the first installation script in the soft load installation package through the installation script parameter information in the first input box to generate a second installation script; by instructing the host to execute the second installation script, the host installs the soft load by executing the second installation script, thereby installing the soft load without manually executing the installation command, thereby improving the efficiency of the soft load installation process.

It should be noted that the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

The embodiment of the present application also provides a computer program product, including a computer program, which can implement the steps and corresponding contents of the aforementioned method embodiment when executed by a processor. Compared with the prior art, it can be achieved that: by displaying a soft load management interface, a first input box is provided to the operation and maintenance personnel, so that the operation and maintenance personnel can clearly enter the soft load installation package identifier corresponding to the soft load to be installed, the host identifier of the host on which the soft load needs to be installed, and the installation script parameter information of the soft load in the first input box; by responding to the soft load installation package identifier, the installation script parameter information and the host identifier entered in the first input box, the soft load installation package corresponding to the soft load installation package identifier is downloaded, and the soft load installation package is sent to the host corresponding to the host identifier, so that the host does not need to manually operate the host to download the soft load installation package, thereby improving the efficiency of downloading the soft load installation package; modifying the first installation script in the soft load installation package through the installation script parameter information in the first input box to generate a second installation script; by instructing the host to execute the second installation script, the host installs the soft load by executing the second installation script, thereby installing the soft load without manually executing the installation command, thereby improving the efficiency of the soft load installation process.

The terms "first", "second", "third", "fourth", "1", "2", etc. (if any) in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than that shown or described in the drawings.

It should be understood that, although each operation step is indicated by arrows in the flowchart of the embodiment of the present application, the implementation order of these steps is not limited to the order indicated by the arrows. Unless clearly stated herein, in some implementation scenarios of the embodiment of the present application, the implementation steps in each flowchart can be performed in other orders according to demand. In addition, some or all of the steps in each flowchart may include multiple sub-steps or multiple stages based on actual implementation scenarios. Some or all of these sub-steps or stages may be executed at the same time, and each sub-step or stage in these sub-steps or stages may also be executed at different times respectively. In different scenarios at the execution time, the execution order of these sub-steps or stages may be flexibly configured according to demand, and the embodiment of the present application does not limit this.

The above is only an optional implementation method for some implementation scenarios of the present application. It should be pointed out that for ordinary technicians in this technical field, without departing from the technical concept of the solution of the present application, other similar implementation methods based on the technical ideas of the present application are also within the protection scope of the embodiments of the present application.

Claims (10)

1. A method for installing a soft load, characterized in that it is applied to a terminal, and the method comprises: Displaying a soft load management interface, wherein the soft load management interface includes a first input box; In response to inputting a soft load installation package identifier, installation script parameter information, and a host identifier in the first input box, downloading the soft load installation package corresponding to the soft load installation package identifier from the object storage tool, and sending the soft load installation package to the host corresponding to the host identifier, wherein the soft load installation package includes a first installation script of the soft load; Modify the first installation script according to the installation script parameter information to obtain a second installation script for the soft load; Instruct the host to execute the second installation script to install the soft load. 2. The method according to claim 1, characterized in that the soft load installation package includes load balancing software and a configuration management program, the load balancing software is used for load balancing, and the configuration management program is used to register the soft load; The instructing the host to execute the second installation script to install the soft load includes instructing the host to execute a startup command of the second installation script and start the configuration management program and the load balancing software; The starting of the configuration management program and the load balancing software further includes: receiving registration information of the soft load sent by the host through the configuration management program, wherein the registration information includes the host identifier; Registering the soft load according to the registration information; The registration information is displayed on the soft load management interface. 3. The method according to claim 2, characterized in that the soft load management interface further comprises a second input box, the second input box is used to input a grayscale routing rule, the input grayscale routing rule is used to instruct the host to execute a grayscale publishing task, the grayscale publishing task is stored in the terminal, and the configuration management program is further used to modify a configuration file of the load balancing software; The step of displaying the registration information on the soft load management interface further includes: In response to inputting a grayscale routing rule in the second input box, the grayscale routing rule in the second input box is sent to the configuration management program of the host, so that the host modifies the configuration file of the load balancing software through the configuration management program, and executes the grayscale release task according to the grayscale routing rule through the load balancing software. 4. The method according to claim 3, characterized in that the sending of the grayscale routing rule in the second input box to the configuration management program of the host further comprises: According to the grayscale release task, the host is instructed to modify the configuration file of the load balancing software through the configuration management program, and a corresponding relationship between the grayscale release task and the soft load in the host is established. 5. The method according to claim 2, characterized in that the registration information further includes a soft load identifier corresponding to the soft load, an architecture type of the soft load, a node type of the host, and a status of the soft load, the architecture type of the soft load includes a cluster architecture, an active-standby architecture, and a stand-alone architecture, and the node type of the host includes a cluster node, a master node, a standby node, and a stand-alone node; The soft load identifier, soft load architecture type and node type of the host in the registration information are obtained by the host from the installation script parameter information. 6. The method according to claim 1, characterized in that the soft load management interface comprises a third input box, wherein the third input box is used to input a pre-made soft load installation package and a corresponding soft load installation package identifier; The downloading of the soft load installation package corresponding to the soft load installation package identifier from the object storage tool also includes: In response to the soft load installation package and the corresponding soft load installation package identifier input in the third input box, the soft load installation package and the corresponding soft load installation package identifier are stored in the object storage tool. 7. The method according to claim 2, wherein the step of instructing the host to execute the startup command of the second installation script and start the configuration management program and the load balancing software comprises: Instructing the host to determine whether there is a running configuration management program to be updated according to a startup command of the second installation script; If there is a configuration management program to be updated that is running, then stop running the configuration management program to be updated and start the configuration management program; If there is no configuration management program to be updated that is running, starting the configuration management program; Instructing the host to determine whether there is any running load balancing software to be updated according to the startup command of the second installation script; If there is a configuration management program to be updated that is running, then stop running the configuration management program to be updated and start the configuration management program; If there is no configuration management program to be updated that is running, the configuration management program is started. 8. A soft load installation device, characterized by comprising: A display module, used to display a soft load management interface, wherein the soft load management interface includes a first input box; a response module, configured to, in response to inputting a soft load installation package identifier, installation script parameter information, and a host identifier in the first input box, download the soft load installation package corresponding to the soft load installation package identifier from the object storage tool, and send the soft load installation package to the host corresponding to the host identifier, wherein the soft load installation package includes a first installation script of the soft load; An obtaining module, used to modify the first installation script according to the installation script parameter information to obtain a second installation script of the soft load; The instruction module is used to instruct the host to execute the second installation script to install the soft load. 9. An electronic device comprising a memory, a processor and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of the method according to any one of claims 1 to 7. 10. A computer-readable storage medium having a computer program stored thereon, wherein the computer program implements the steps of the method according to any one of claims 1 to 7 when executed by a processor.