Cloud software operation and maintenance system, operation and maintenance method and related device

Abstract

The embodiment of the invention provides a cloud software operation and maintenance system, an operation and maintenance method and a related device. The cloud software operation and maintenance system comprises a virtual machine daemon process deployed on a cloud virtual machine; the virtual machine daemon process is used for periodically acquiring keep-alive software information corresponding to the cloud virtual machine and acquiring software process information running in the cloud virtual machine; and under the condition that the software process corresponding to the software represented by the keep-alive software information does not exist in the software process information, establishing the software process corresponding to the software represented by the keep-alive software information. And the maintenance efficiency of the cloud software operation and maintenance system is improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of cloud computing technology, and in particular to a cloud software operation and maintenance system, operation and maintenance method, and related devices. Background Art

[0002] In the field of cloud computing, as cloud services mature and are widely used, more and more users deploy private software on cloud virtual machines according to their needs. As business grows, the number of cloud virtual machines will increase. The required private software is deployed in each cloud virtual machine.

[0003] The existing operation and maintenance method requires operation and maintenance personnel to manually log in to each cloud virtual machine to check the software running status. This manual operation and maintenance method has low maintenance efficiency when facing a large number of cloud virtual machines. Summary of the invention

[0004] In view of this, multiple implementations of the present application are dedicated to providing a cloud software operation and maintenance system, operation and maintenance method and related devices, which can improve the operation and maintenance efficiency of cloud software to a certain extent.

[0005] One embodiment of the present application provides a cloud software operation and maintenance system, including: a virtual machine daemon deployed on a cloud virtual machine; the virtual machine daemon is used to periodically obtain keep-alive software information corresponding to the cloud virtual machine, and obtain software process information running in the cloud virtual machine; when it is determined that the software process corresponding to the software represented by the keep-alive software information does not exist in the software process information, establish a software process corresponding to the software represented by the keep-alive software information.

[0006] One embodiment of the present application provides a cloud software operation and maintenance method, the method comprising: periodically obtaining keep-alive software information corresponding to the cloud virtual machine through a virtual machine daemon process, and obtaining software process information running in the cloud virtual machine; when it is determined that the software process corresponding to the software represented by the keep-alive software information does not exist in the software process information, establishing the software process corresponding to the software represented by the keep-alive software information.

[0007] One embodiment of the present application provides a computer device, which includes a memory and a processor, wherein the memory stores at least one computer program, and the at least one computer program is loaded and executed by the processor to implement the aforementioned cloud software operation and maintenance method.

[0008] One embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores at least one computer program, and when the at least one computer program is executed by a processor, it can implement the aforementioned cloud software operation and maintenance method.

[0009] One embodiment of the present application provides a computer program product, which is used to implement the aforementioned cloud software operation and maintenance method.

[0010] In multiple implementations provided in this specification, through a virtual machine daemon process deployed on a cloud virtual machine, keep-alive software information and software process information running in the cloud virtual machine are periodically obtained. When it is determined that the software process corresponding to the keep-alive software does not exist, the software process is automatically established, so that the software on the cloud virtual machine can continue to run stably, thereby realizing automated operation and maintenance of cloud software and improving the maintenance efficiency of the cloud software operation and maintenance system. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 A system diagram of a cloud-based software operation and maintenance system provided for one embodiment of the present application.

[0012] Figure 2 An interactive schematic diagram of a cloud software operation and maintenance system provided for one embodiment of the present application.

[0013] Figure 3 A schematic diagram of the modules of a cloud software operation and maintenance system provided for one embodiment of the present application.

[0014] Figure 4 A flowchart of a cloud software operation and maintenance method provided for one embodiment of the present application.

[0015] Figure 5 A schematic diagram of a computer device provided for one embodiment of the present application. DETAILED DESCRIPTION

[0016] The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments.

[0017] In the description of the embodiments of the present application, it should be understood that the terms "first" and "second" are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of the present application, the meaning of "multiple" is two or more, unless otherwise clearly and specifically defined.

[0018] In the related art, with the widespread application of cloud computing services, more and more users deploy private software on cloud virtual machines according to their needs, which improves resource utilization and the flexibility of business deployment.

[0019] For example, in a specific application scenario, an enterprise may deploy private business-critical software on a large number of cloud virtual machines. As the business grows, the number of cloud virtual machines may increase. In order to ensure the normal operation of these private software, they need to be managed and maintained.

[0020] The R&D personnel let the private software send heartbeats to the background server regularly, and then regularly detect the heartbeat status update time of the background server to determine whether the software is offline, and then the background server sends instructions to the operation and maintenance software receiving end on the cloud server to execute the instructions. However, the R&D personnel further discovered that this solution has the following disadvantages: network problems may lead to wrong judgments. The private software is actually online, but due to network delays, interruptions and other problems, the background server may mistakenly judge that the cloud software is offline, and then issue wrong instructions to interfere with the normal process; even if a problem is found in the private software, it is necessary to resend the private software restart command to the command receiving end, but the command receiving end may also be offline or suspended, causing the restart command to fail. As a result, in the actual work process, it is still necessary to manually log in to the virtual machine to actually check the software running status, which consumes a lot of manpower and time, and the operation and maintenance efficiency is low.

[0021] See also Figure 1 . One embodiment of the present application provides a cloud software operation and maintenance system. The cloud software operation and maintenance system may include a client, a cloud host, and a cloud virtual machine. The client may be an electronic device with network access capability. Specifically, for example, the client may be a desktop computer, a tablet computer, a laptop computer, a smart phone, etc. The user may use the client to communicate with the cloud host for operation and management. Alternatively, the client may also be software that can run in an electronic device.

[0022] A cloud host can be a physical server or a virtualized resource pool deployed on a cloud computing platform, equipped with hardware resources such as network communication modules, processors, and memory. The cloud host can communicate with cloud virtual machines to collaboratively complete computing tasks. Cloud virtual machines run on cloud hosts and are virtual computing resources created based on virtualization technology.

[0023] See also Figure 1 and Figure 2 An embodiment of the present application provides an example of an application scenario of a cloud software operation and maintenance system. The cloud software operation and maintenance system may include a client, a cloud host, and a cloud virtual machine.

[0024] In daily operations, enterprises may need to deploy private software on multiple cloud virtual machines to meet business needs. For example, an Internet company needs to deploy its core business applications on hundreds of cloud virtual machines to provide services to users. As the number of cloud virtual machines increases, more and more manual effort is required to manage and maintain the software running on each cloud virtual machine.

[0025] In this scenario example, the enterprise's IT administrator can use the client to interact with the cloud host to manage the deployment and operation of private software on the cloud virtual machine. Specifically, the administrator can send software download instructions to the cloud host through the client. The cloud host downloads the required software executable file from the software warehouse according to the instruction and stores it at the specified address of the cloud virtual machine. At the same time, the cloud host writes the software information corresponding to the downloaded software executable file into the specified configuration file of the cloud virtual machine as the keep-alive software information.

[0026] A virtual machine daemon can be deployed on each cloud virtual machine. The virtual machine daemon is used to periodically read the keep-alive software information from the specified configuration file of the cloud virtual machine and obtain the software process information running in the cloud virtual machine. When it is determined that the software process information does not contain the software process corresponding to the software represented by the keep-alive software information, the virtual machine daemon will automatically establish the software process corresponding to the software. Specifically, the virtual machine daemon establishes the corresponding software process by starting to execute the software executable file in the specified address.

[0027] For example, suppose that an enterprise needs to ensure that the business application "AppA" continues to run on the cloud virtual machine. The keep-alive software information may include the executable file name and version information of "AppA", as well as the specified address where the executable file is stored. The virtual machine daemon periodically (for example, every 10 seconds) reads the keep-alive software information from the specified configuration file, obtains the currently running software process information, and checks whether "AppA" is running. If "AppA" is not running, the virtual machine daemon will start the executable file of "AppA" from the specified address, establish the software process of "AppA", and ensure the continuity of the software service.

[0028] When an updated version of "AppA" needs to be deployed, the administrator can use the client to send an update command to the cloud host. After receiving the command, the cloud host downloads the new version of the "AppA" executable file and stores it at the specified address of the cloud virtual machine. At the same time, it updates the keep-alive software information in the specified configuration file to include the new version information. When the virtual machine daemon process periodically reads the keep-alive software information next time, it finds that the software represented by the keep-alive software information is an updated version of "AppA" in the currently running software process information. At this time, the virtual machine daemon process will close the old version of the "AppA" software process, and start executing the new version of the "AppA" executable file in the specified address, establish a new software process, and realize automatic software update.

[0029] If the enterprise decides to stop running "AppA" on the cloud virtual machine, the administrator can send a software stop command to the cloud host through the client. After receiving the command, the cloud host deletes the software information of "AppA" targeted by the stop command in the specified configuration file of the corresponding cloud virtual machine. Subsequently, the cloud virtual machine recognizes that the keep-alive software information of "AppA" has been deleted based on the updated specified configuration file, and then shuts down the software process corresponding to "AppA". Since the virtual machine daemon process no longer contains the information of "AppA" when periodically reading the keep-alive software information, it will not start "AppA" again, thereby achieving precise control of the software.

[0030] Through this scenario example, the cloud software operation and maintenance system realizes the automated operation and maintenance of software on cloud virtual machines. Administrators can interact with the cloud host through the client to remotely deploy, update, or stop the software on the cloud virtual machine, while the virtual machine daemon is responsible for automatically monitoring and maintaining the operation of the software on the cloud virtual machine. In this way, the maintenance efficiency of the cloud software operation and maintenance system is improved and the operation and maintenance costs are reduced.

[0031] See also Figure 3 . An embodiment of the present application provides a cloud software operation and maintenance system. The cloud software operation and maintenance system may include: a virtual machine daemon process deployed on a cloud virtual machine; the virtual machine daemon process is used to periodically obtain keep-alive software information corresponding to the cloud virtual machine, and obtain software process information running in the cloud virtual machine; when it is determined that the software process corresponding to the software represented by the keep-alive software information does not exist in the software process information, establish the software process corresponding to the software represented by the keep-alive software information.

[0032] In this embodiment, the cloud virtual machine can be a virtualized computing resource deployed on a cloud computing platform. The cloud virtual machine has hardware resources such as network communication capabilities, processors, and memory. Users can deploy private software on the cloud virtual machine according to their own needs to meet specific business functions.

[0033] In this embodiment, the virtual machine daemon process can be a background process or service for monitoring the running status of the software process in the cloud virtual machine. The virtual machine daemon process can be implemented by a software module, for example, it can be run in a daemon mode in a Linux system, and can be run as a system service in a Windows system.

[0034] In this embodiment, the virtual machine daemon process periodically performs monitoring operations at preset time intervals. The time interval can be configured according to actual needs, for example, once every 5 seconds, 10 seconds or 1 minute. By periodically obtaining the keep-alive software information and software process information, the virtual machine daemon process can timely monitor the running status of the software that needs to ensure continuous operation, and timely discover and handle abnormal situations.

[0035] In this embodiment, the keep-alive software information may include identification information corresponding to the software that needs to be ensured to continue running. For example, the keep-alive software information may be the executable file name, process name, or unique identifier of the business software. By obtaining the keep-alive software information, the virtual machine daemon process can clearly identify the software that needs to be kept alive.

[0036] In this embodiment, the software process information may include information about the software process currently running on the cloud virtual machine. The virtual machine daemon process may obtain the software process information by querying the process management interface of the operating system of the cloud virtual machine, such as using the ps command in a Linux system or querying the process list in the task manager in a Windows system.

[0037] In some cases, after obtaining the keep-alive software information and software process information, the virtual machine daemon process can determine whether the software process corresponding to the keep-alive software exists in the current software process information. If it is determined that the software process does not exist, the virtual machine daemon process can automatically establish the software process corresponding to the software that needs to be kept alive.

[0038] In this embodiment, establishing a software process may include executing the corresponding software executable file and starting the software application. For example, if the keep-alive software information indicates that a database service needs to be run, and the virtual machine daemon finds that the database service process is not running, it can execute a startup command or script to restart the database service to ensure the continuous operation of the critical software. For example, suppose that the keep-alive software information indicates that a Web server process needs to run continuously. The virtual machine daemon checks the list of running processes on the cloud virtual machine every 10 seconds. When it detects that the Web server process does not exist, it automatically executes the startup command to re-establish the software process. In this way, the continuous operation of the business services on the cloud virtual machine is guaranteed.

[0039] In this embodiment, by deploying a virtual machine daemon process on a cloud virtual machine, periodically obtaining keep-alive software information and software process information, and automatically establishing the software process when it is determined that the software process corresponding to the keep-alive software does not exist. In this way, the software on the cloud virtual machine can run continuously and stably, realizing the automated operation and maintenance of cloud software, and improving the maintenance efficiency of the cloud software operation and maintenance system.

[0040] In some embodiments, the cloud virtual machine daemon process periodically reads the keep-alive software information from a specified configuration file of the cloud virtual machine; wherein the software executable file corresponding to the keep-alive software information is stored at a specified address; when it is determined that the software process information does not contain the software process corresponding to the software represented by the keep-alive software information, a software process corresponding to the software represented by the keep-alive software information is established, including: starting the software process that executes the software executable file in the specified address.

[0041] In this embodiment, the virtual machine daemon process can periodically read the keep-alive software information from the specified configuration file of the cloud virtual machine. The specified configuration file can be a configuration file stored in the cloud virtual machine. The specified configuration file can contain identification information of the software that needs to be ensured to continue running. By reading the keep-alive software information from the specified configuration file, the virtual machine daemon process can dynamically obtain the list of software that needs to be monitored, making the cloud software operation and maintenance system more flexible and configurable.

[0042] In this embodiment, the executable file of the software corresponding to the keep-alive software information is stored at a specified address. The specified address may be the file path or directory location where the software executable file is located in the cloud virtual machine. In this way, the virtual machine daemon process can accurately locate and execute the corresponding software when needed. Specifically, when it is determined that the software process corresponding to the software represented by the keep-alive software information does not exist in the software process information, the virtual machine daemon process can establish the software process corresponding to the software by starting the software executable file stored in the specified address.

[0043] In this embodiment, by deploying a virtual machine daemon process on a cloud virtual machine, the keep-alive software information is periodically read from a specified configuration file. When it is determined that the software process corresponding to the keep-alive software does not exist, the software executable file at the specified address can be started to establish the software process. In this way, the software on the cloud virtual machine can run continuously and stably, realizing the automated operation and maintenance of cloud software and improving the maintenance efficiency of the cloud software operation and maintenance system.

[0044] In some implementations, the cloud host downloads the software execution file and stores it at a designated address, and writes the software information corresponding to the downloaded software execution file into the designated configuration file as the keep-alive software information.

[0045] In this embodiment, the cloud host can download the software execution file and store it at the specified address of the cloud virtual machine. The cloud host can also write the software information corresponding to the downloaded software execution file into the specified configuration file of the cloud virtual machine as the keep-alive software information.

[0046] In this embodiment, the cloud host can be a physical server or a virtualized resource pool deployed on a cloud computing platform, and has hardware resources such as a network communication module, a processor, and a memory. The cloud host can communicate with the cloud virtual machine to collaboratively complete computing tasks. The cloud virtual machine can run in the cloud host and is a virtual computing resource created based on virtualization technology. The software executable file is downloaded by the cloud host and stored at a specified address. The virtual machine daemon of the cloud virtual machine can access and start the corresponding software when needed. The cloud host can write the software information corresponding to the downloaded software executable file into a specified configuration file, and the virtual machine daemon can periodically read the keep-alive software information from the specified configuration file.

[0047] In this embodiment, after the virtual machine daemon process obtains the keep-alive software information and the software process information, it determines whether the software process corresponding to the keep-alive software exists in the current software process information. If it is determined that the software process does not exist, the virtual machine daemon process can establish the software process corresponding to the software by starting the software execution file stored in the specified address. In this way, the business software on the cloud virtual machine is guaranteed to run continuously and stably.

[0048] In this embodiment, with the assistance of the cloud host, the cloud software operation and maintenance system can realize remote deployment and automated maintenance of the software. The cloud host can download and distribute software executable files, and update the keep-alive software information, and the virtual machine daemon process can monitor and maintain the running status of the software process. This makes the cloud software operation and maintenance system have good flexibility and scalability, and improves the maintenance efficiency of the cloud software operation and maintenance system.

[0049] In some embodiments, the cloud virtual machine daemon process periodically reads the keep-alive software information from a specified configuration file of the cloud virtual machine; wherein the software executable file corresponding to the keep-alive software information is stored at a specified address; when the software represented by the read keep-alive software information is an updated version relative to the software of the same name in the software process information, the software process of the software is closed, and the software process of the software executable file of the software in the specified address is started.

[0050] In this embodiment, the specified configuration file may include identification information and version information of the software that needs to be ensured to run continuously. By reading the keep-alive software information from the specified configuration file, the virtual machine daemon process can dynamically obtain the software list that needs to be monitored and its version status. When the software represented by the keep-alive software information read by the virtual machine daemon process is an updated version of the software with the same name in the software process information, the virtual machine daemon process can close the existing software process of the software, and start executing the new version software executable file of the software in the specified address to establish a new software process.

[0051] Specifically, the virtual machine daemon can determine whether there is a new version by comparing the version number in the keep-alive software information with the version number in the currently running software process information. If it is found that the software represented by the keep-alive software information is an updated version, the old version of the software process is closed first to avoid version conflicts or resource occupation problems, and then the new version of the software executable file is started to ensure that the software upgrade is carried out smoothly. In this way, the software on the cloud virtual machine can run continuously and stably and automatically complete the version update, realizing the automated operation and upgrade maintenance of cloud software.

[0052] In some embodiments, the cloud virtual machine daemon process periodically reads the keep-alive software information from a specified configuration file of the cloud virtual machine; when the cloud host included in the cloud software operation and maintenance system receives a software stop instruction, the software information of the software targeted by the stop instruction is deleted from the specified configuration file, and the cloud virtual machine closes the software process corresponding to the software represented by the software information.

[0053] In this embodiment, when the cloud host included in the cloud software operation and maintenance system receives a software stop instruction, the cloud host will delete the software information of the software targeted by the software stop instruction in the designated configuration file of the cloud virtual machine. Since the virtual machine daemon periodically reads the keep-alive software information from the designated configuration file, when it detects that the keep-alive software information of a certain software has been deleted, the virtual machine daemon will no longer monitor the software, nor will it restart the software after it stops. In some embodiments, a status identifier may be set corresponding to each software information in the designated configuration file, and the cloud host may set the status identifier corresponding to the software information indicated by the software stop instruction to disabled. In this way, after the cloud virtual machine reads the designated configuration file through the virtual machine daemon, it finds the software information with a disabled status identifier, and can identify and close the process corresponding to the software information by querying the current software process information, thereby ensuring that the software is completely stopped from executing.

[0054] See also Figure 4 The embodiment of the present application also provides a cloud software operation and maintenance method. The cloud software operation and maintenance method can be applied to a cloud software operation and maintenance system. The cloud software operation and maintenance method can include the following steps.

[0055] Step S110: periodically obtaining the keep-alive software information corresponding to the cloud virtual machine through the virtual machine daemon process, and obtaining the software process information running in the cloud virtual machine.

[0056] Step S120: when it is determined that the software process corresponding to the software represented by the keep-alive software information does not exist in the software process information, a software process corresponding to the software represented by the keep-alive software information is established.

[0057] In this embodiment, the specific functions and effects achieved by the operation and maintenance method of the cloud software can be explained with reference to other embodiments of the present application and will not be repeated here.

[0058] In some embodiments, the cloud virtual machine daemon process periodically reads the keep-alive software information from a specified configuration file of the cloud virtual machine; wherein the software executable file corresponding to the keep-alive software information is stored at a specified address; when it is determined that the software process information does not contain the software process corresponding to the software represented by the keep-alive software information, the step of establishing the software process corresponding to the software represented by the keep-alive software information includes: starting the software process that executes the software executable file in the specified address.

[0059] In this embodiment, the specific functions and effects achieved can be explained by referring to other embodiments of the present application, and will not be repeated here.

[0060] In some embodiments, the cloud virtual machine daemon process periodically reads the keep-alive software information from a specified configuration file of the cloud virtual machine; wherein the software executable file corresponding to the keep-alive software information is stored at a specified address; the method further includes: when the software represented by the read keep-alive software information is an updated version relative to the software of the same name in the software process information, closing the software process of the software; and, starting a software process that executes the software executable file of the software in the specified address.

[0061] In this embodiment, the specific functions and effects achieved can be explained by referring to other embodiments of the present application, and will not be repeated here.

[0062] In some embodiments, the cloud software operation and maintenance method may further include: upon receiving a software stop instruction, deleting the software information of the software targeted by the stop instruction in the keep-alive software information; and closing the software process corresponding to the software represented by the software information.

[0063] In this embodiment, the specific functions and effects achieved can be explained by referring to other embodiments of the present application, and will not be repeated here.

[0064] The present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the processor implements the aforementioned cloud software operation and maintenance method.

[0065] The embodiment of the present application also provides a computer program product comprising instructions, which, when executed by a processor, enables a computer to implement the aforementioned cloud software operation and maintenance method.

[0066] See also Figure 5The present description embodiment may provide a computer device, the computer device comprising: a memory, and one or more processors communicatively connected to the memory; the memory stores instructions executable by the one or more processors, the instructions are executed by the one or more processors, so that the one or more processors implement the aforementioned cloud software operation and maintenance method.

[0067] In some embodiments, the computer device may include a processor, a non-volatile storage medium, an internal memory, a communication interface, a display device, and an input device connected by a system bus. The non-volatile storage medium may store an operating system and related computer programs.

[0068] The user information or user account information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, etc.) involved in multiple implementation methods of the present application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0069] It should be understood that the specific examples in this article are only intended to help those skilled in the art to better understand the embodiments of the present application, rather than to limit the scope of the present invention.

[0070] It can be understood that in the various implementations of the present application, the size of the serial number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the implementation methods of the present application.

[0071] It can be understood that the various embodiments described in this application can be implemented individually or in combination, and the embodiments of this application are not limited to this.

[0072] Unless otherwise stated, all technical and scientific terms used in the embodiments of the present application have the same meaning as those generally understood by those skilled in the art of the technical field of the present application. The terms used in the present application are only for the purpose of describing specific embodiments and are not intended to limit the scope of the present application. The term "and / or" used in the present application includes any and all combinations of one or more related listed items. The singular forms of "a kind of", "above" and "the" used in the embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings.

[0073] It can be understood that the processor of the embodiment of the present application can be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method implementation can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (DigitalSignal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiment of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and executed. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0074] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (programmable ROM, PROM), an erasable programmable read-only memory (erasable PROM, EPROM), an electrically erasable programmable read-only memory (EEPROM) or a flash memory. The volatile memory may be a random access memory (RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0075] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0076] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method implementation methods and will not be repeated here.

[0077] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device implementation described above is only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0078] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0079] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0080] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0081] The above is only a specific implementation of the present application, but the protection scope of the present invention is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A cloud software operation and maintenance system, characterized in that: include: A virtual machine daemon deployed on a cloud virtual machine; The virtual machine daemon is used to periodically obtain the keep-alive software information corresponding to the cloud virtual machine, and to obtain the software process information running in the cloud virtual machine; when it is determined that the software process corresponding to the software represented by the keep-alive software information does not exist in the software process information, a software process corresponding to the software represented by the keep-alive software information is established.

2. The cloud software operation and maintenance system according to claim 1, characterized in that: The cloud virtual machine daemon process periodically reads the keep-alive software information from a specified configuration file of the cloud virtual machine; wherein the software executable file corresponding to the keep-alive software information is stored at a specified address; When it is determined that the software process corresponding to the software represented by the keep-alive software information does not exist in the software process information, establishing the software process corresponding to the software represented by the keep-alive software information includes: Start a software process that executes the software execution file in the specified address.

3. The cloud software operation and maintenance system according to claim 2, characterized in that: The cloud-based software operation and maintenance system includes a cloud host that downloads a software execution file and stores it at a designated address, and writes software information corresponding to the downloaded software execution file into the designated configuration file as the keep-alive software information.

4. The cloud software operation and maintenance system according to claim 1, characterized in that: The cloud virtual machine daemon process periodically reads the keep-alive software information from a specified configuration file of the cloud virtual machine; wherein the software executable file corresponding to the keep-alive software information is stored at a specified address; When the software represented by the read keep-alive software information is an updated version relative to the software with the same name in the software process information, the software process of the software is closed, and the software process of the software executable file of the software in the designated address is started.

5. The cloud software operation and maintenance system according to claim 1, characterized in that: The cloud virtual machine daemon process periodically reads the keep-alive software information from the specified configuration file of the cloud virtual machine; when the cloud host included in the cloud software operation and maintenance system receives a software stop instruction, the software information of the software targeted by the stop instruction is deleted from the specified configuration file, and the cloud virtual machine closes the software process corresponding to the software represented by the software information.

6. A cloud software operation and maintenance method, characterized in that: The method comprises: Periodically obtaining keep-alive software information corresponding to the cloud virtual machine through the virtual machine daemon process, and obtaining software process information running in the cloud virtual machine; When it is determined that the software process corresponding to the software indicated by the keep-alive software information does not exist in the software process information, a software process corresponding to the software indicated by the keep-alive software information is established.

7. The operation and maintenance method according to claim 6, characterized in that: The cloud virtual machine daemon process periodically reads the keep-alive software information from a specified configuration file of the cloud virtual machine; wherein the software executable file corresponding to the keep-alive software information is stored at a specified address; In the case where it is determined that the software process corresponding to the software represented by the keep-alive software information does not exist in the software process information, the step of establishing the software process corresponding to the software represented by the keep-alive software information includes: Start a software process that executes the software execution file in the specified address.

8. The operation and maintenance method according to claim 6, characterized in that: The cloud virtual machine daemon process periodically reads the keep-alive software information from a specified configuration file of the cloud virtual machine; wherein the software executable file corresponding to the keep-alive software information is stored at a specified address; the method further includes: If the software represented by the read keep-alive software information is an updated version of the software with the same name in the software process information, closing the software process of the software; and, A software process for executing the software execution file of the software in the designated address is started.

9. The operation and maintenance method according to claim 6, characterized in that: The method further comprises: In case of receiving a software stop instruction, deleting the software information of the software targeted by the stop instruction in the keep-alive software information; and The software process corresponding to the software represented by the software information is closed.

10. A computer device, characterized in that: The computer device includes a memory and a processor, wherein the memory stores at least one computer program, and the at least one computer program is loaded and executed by the processor to implement the operation and maintenance method of the cloud software as described in any one of claims 6 to 9.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores at least one computer program, and when the at least one computer program is executed by the processor, it can implement the operation and maintenance method of the cloud software as described in any one of claims 6 to 9.

12. A computer program product, characterized in that The computer program product is used to implement the operation and maintenance method of the cloud software as described in any one of claims 6 to 9.

Images