Method for operating and maintaining application in cloud system and computing device

Abstract

According to the method for operating and maintaining the applications in the cloud system, due to the fact that information of various faults of the applications is stored in a fault knowledge base in a cloud management platform, under the condition that a first application breaks down, the cloud management platform generates first configuration information through the fault knowledge base; the first configuration information is used for configuring a tool for detecting the fault, in addition, the first operation and maintenance environment can be configured by the tenant, and the first detection tool can be operated in the first operation and maintenance environment subsequently. According to the application, the bastion host does not need to be used for remote access, so that the cost of the tenant is reduced, and the security of the application data of the tenant is guaranteed.

Description

[0001] This application claims the priority of the Chinese patent application filed with the China Patent Office on June 28, 2023, with application number 202310777012.4 and application name “A method and computing device for application operation and maintenance”, the entire contents of which are incorporated by reference in this application. Technical Field

[0002] The present application relates to the field of cloud service systems, and more specifically, to a method and computing device for application operation and maintenance in a cloud system. Background Art

[0003] With the development of cloud technology, traditional data center applications are gradually migrating to cloud platforms. In the process of application migration, multi-cloud and hybrid cloud have become a preferred option for more and more enterprises due to the data affinity and disaster recovery level of the application. At this time, the application will be distributed to multiple public cloud vendors, Internet data centers (IDCs) in multiple regions, and other places. Through the cloud management platform, one-stop multi-cloud and multi-data center application unified distribution, update, upgrade and other life cycle capabilities can be achieved. At this time, how to operate and maintain these applications becomes a problem that needs to be considered.

[0004] In the current technical solutions, the operation and maintenance of these applications are all done by uniformly collecting the fault information of the applications on the cloud, and then the local personnel directly perform the operation and maintenance operations, or provide remote connection to the bastion host and authorize remote professional operation and maintenance personnel to perform the operation and maintenance operations. Further processing based on the analysis conclusions of the fault information needs to be performed by local operation and maintenance, which requires a high level of professional technical skills of local operation and maintenance personnel; if professional operation and maintenance personnel need to intervene, it is necessary to provide connection and authorization means such as the bastion host, at this time, there will be security issues and increased cost investment.

[0005] As can be seen from the above, in the current solutions, the operation and maintenance of cloud applications either requires the ability of local operation and maintenance personnel, or there are security issues and increased cost investment. Therefore, a method of operation and maintenance in cloud systems is needed, which can make operation and maintenance more convenient and reduce user costs. Summary of the invention

[0006] The present application provides a method for operating and maintaining applications in a cloud system, which can reduce user costs and ensure the security of user application data.

[0007] In a first aspect, a method for operating and maintaining an application in a cloud system is provided. The method can be applied in a cloud service system. The method can be executed by a cloud management platform (or a computing device in a cloud management platform), or can also be executed by a component (such as a chip or circuit) of the cloud management platform (or a computing device in a cloud management platform). The cloud management platform is used to manage an infrastructure for providing cloud services, the infrastructure includes multiple cloud data centers, each of which has at least one application deployed, and the cloud management platform is configured with a fault knowledge base, which stores information on various faults of the application.

[0008] The method includes: in the event of a failure in an application in a cloud data center, displaying first configuration information to a tenant, the first configuration information being used to configure a detection tool for detecting the failure, wherein the first configuration information is generated based on information about the first failure and a failure knowledge base; receiving second configuration information from the tenant, the second configuration information being used to determine a first operation and maintenance environment in the cloud data center; and running the first detection tool in the first operation and maintenance environment.

[0009] In the present application, the data center is one of the multiple cloud data centers, and the application is one of the multiple applications.

[0010] In the present application, "fault information" may include, for example, at least one of the following: fault phenomenon, fault type, fault impact, time of occurrence of the fault, and duration of the fault. Optionally, the fault information may also include a suspected cause of the fault.

[0011] Exemplarily, the "fault knowledge base" may store the mapping relationship between the fault information, the suspected cause of the fault, and the information of the detection tool corresponding to the suspected cause of the fault. Exemplarily, the "fault knowledge base" may store the mapping relationship between the fault information and the information of the detection tool corresponding to the fault information. For example, based on the information of the first fault and the mapping relationship, the suspected cause of the first fault can be determined, and the information of the first detection tool of the first fault can be determined, and the first configuration information can be generated based on the information of the detection tool. For another example, based on the information of the first fault and the mapping relationship, the information of the first detection tool can be directly determined.

[0012] Exemplarily, the information of the first detection tool may include at least one of the following: the name of the first detection tool, the type of the detection tool, etc. The first configuration information may configure the first detection tool based on the information of the first detection tool. For example, the first configuration information is used to configure at least one of the following: a specific task performed by the first detection tool, a command executed by the first detection tool, an execution order of tasks corresponding to the first detection tool, whether the first detection tool (or between various tasks) is executed serially or in parallel, etc. Among them, the first configuration information includes the name of the first detection tool.

[0013] It should be noted that the following “information of the first repair tool” and “fourth configuration information” can also be understood with reference to the above-mentioned “information of the first detection tool” and “first configuration information” and will not be elaborated on herein.

[0014] For another example, the "fault knowledge base" can store the mapping relationship between fault information and suspected causes of the fault. In the present application, it is not limited to the mapping relationship between which information the specific mapping relationship stored in the fault knowledge base is. As long as the fault knowledge base or the cloud management platform can determine the detection tool based on the fault information, it falls within the reserved scope of the present application. For example, the mapping relationship can be stored in the form of a table. Therefore, when an application fails, the fault knowledge base module in the cloud management platform can determine the suspected cause of the fault based on the fault information and generate the first configuration information. Exemplarily, the first configuration information may include at least one of the following: a first detection tool, the order of use of the first detection tool, the steps for detecting the first fault, and so on.

[0015] In the present application, the second configuration information may include information about the connection method between the first detection tool and the first operation and maintenance environment. For example, the information about the connection method may include one or more of the following: application programming interface (API) interface, address, protocol, access credentials, etc. For another example, the second configuration information may also include at least one of the following: the name of the operation and maintenance environment, the user name of the operation and maintenance environment, the login password of the operation and maintenance environment, the certificate of the operation and maintenance environment, and so on. Based on the second configuration information, the detection tool can be connected to the operation and maintenance environment.

[0016] In this application, the cloud management platform and tenant applications can be deployed in different environments. For example, the cloud management platform is deployed in a public cloud, and the cloud data center is deployed in an Internet data center, or; the cloud management platform is deployed in public cloud #1, and the data center is deployed in public cloud #2, or; the cloud management platform and the cloud data center are both deployed in a private cloud. For another example, the cloud management platform can also be deployed in a hybrid cloud, and the cloud data center can be deployed in a public cloud, and so on.

[0017] In the present application, the operation and maintenance environment can be determined by the second configuration information. Exemplarily, the tenant can configure the operation and maintenance environment through the second configuration information. At this point, it can also be understood that the second configuration information includes some configuration information of the operation and maintenance environment, so that the detection tool can be connected to the operation and maintenance environment; exemplarily, the tenant can also enter an address in the second configuration information, and the configuration information of the operation and maintenance environment is stored in the address. At this point, it can also be understood that the configuration information of the operation and maintenance environment has been preset in a certain database in advance, and the tenant only needs to point to the address, and the subsequent cloud management platform can access the address to obtain the configuration information of the operation and maintenance environment.

[0018] In this application, since the fault knowledge base in the cloud management platform stores information on various faults of the application, when a first application fails, the cloud management platform generates first configuration information through the fault knowledge base, and the first configuration information is used to configure a tool for detecting the fault. In addition, in this application, the tenant can configure the first operation and maintenance environment, and then the first detection tool can be run in the first operation and maintenance environment. In this application, the cloud management platform can be used to operate and maintain the application, and there is no need to use a bastion host for remote access, which reduces the cost of the tenant and ensures the security of the tenant's application data.

[0019] In one possible scenario, in this application, when an application in a data center fails, the entire operation and maintenance process can be automatically started without the need for tenant authorization.

[0020] In one possible scenario, the cloud management platform sends a second alarm message to the tenant, and the second alarm message is used to indicate that the application has failed. At this time, the cloud management platform will receive a first instruction from the tenant, and the first instruction is used to instruct the operation and maintenance of the application. The technical solution can also be understood as, in this application, when the tenant receives the second alarm message, the tenant can log in to the cloud management platform and authorize the remote operation and maintenance.

[0021] In another possible scenario, when the fault detection perception module detects a fault, the first configuration information can be generated through the fault knowledge base, and because the tenant has preset the second configuration information in advance, the cloud management platform can obtain the configuration information of the operation and maintenance environment. This scenario can also be understood as the cloud management platform itself can obtain the first configuration information and the second configuration information after the user completes the authorization in advance. Only when the information in the fault knowledge base is insufficient to solve the fault will professional operation and maintenance personnel intervene to check and repair the fault and update the knowledge base, thereby achieving the goal of automated application operation and maintenance.

[0022] In a possible implementation, the method further includes: receiving input information from a tenant, the input information including information about the fault. The technical solution can also be understood as, in this application, if a tenant finds that an application has failed, the tenant can also actively input the information about the failure into the cloud management platform, so as to facilitate the fault knowledge base to generate an operation and maintenance statement definition (an example of the first configuration information).

[0023] Optionally, in another possible scenario, when the fault detection perception module in the cloud management platform detects that a certain application has failed, it can proactively generate information about the failure and generate an operation and maintenance statement definition through a fault knowledge base.

[0024] Exemplarily, when the fault detection perception module detects a fault, a first alarm message may be sent to the tenant, where the alarm message includes information about the fault, and the tenant does not need to manually fill in the information about the fault.

[0025] In combination with the first aspect, in a possible implementation manner, the method further includes: the first detection tool includes multiple types of tools, and each type of tool in the multiple types of tools is used to detect at least one type of fault.

[0026] Exemplarily, the "operation and maintenance tools" in this application may include various levels and / or types of fault location analysis tools, for example, including but not limited to: network analysis tools on the Linux operating system, disk input / output (IO) detection and analysis tools, performance analysis tools, and script tools for status reading and system log extraction on the Linux operating system. For another example, it also includes: cross-host network layer routing analysis tools, command line script tools for connectivity checks, network packet loss detection tools, etc.; virtualization analysis tools for container platforms, fault analysis tools for middleware, and other analysis tools for applications such as structured query language (SQL) databases that rely on middleware, etc.

[0027] In combination with the first aspect, in a possible scenario, the tenant can update the displayed first configuration information, for example, the tenant can change the detection tool in the first configuration information. Exemplarily, the tenant can continue to add tools or delete tools based on historical experience. For another example, the tenant can add some additional information to the displayed first configuration information. Exemplarily, the tenant can specify the frequency of executing the detection tool. For example, the tenant can specify the frequency of remote operation and maintenance as one of the following: single immediate execution, single scheduled execution, multiple scheduled executions, or periodic execution, etc.

[0028] In combination with the first aspect, in a possible implementation, the fault knowledge base stores judgment information of the operation result of the first detection tool, the actual cause of the first fault, and information of the first repair tool corresponding to the actual cause of the first fault; the method also includes: determining the operation result of running the first detection tool in the first operation and maintenance environment; determining the actual cause of the first fault based on the operation result and the judgment information of the operation result in the fault knowledge base; determining the information of the first repair tool based on the actual cause of the first fault and in the fault knowledge base, and determining fourth configuration information based on the information of the first repair tool, the fourth configuration information being used to configure the first repair tool to repair the first fault; and running the first repair tool in the first operation and maintenance environment.

[0029] For example, the determination information of the operation result includes various determination results (or a combination of various determination results), and a mapping relationship between the actual cause of the first fault corresponding to each of the various determination results (or a combination of various determination results). Therefore, the actual cause of the first fault can be determined based on different determination results, combined with the information of the first repair tool, and the fourth configuration information is determined. Exemplarily, each tool in the first detection tool will correspond to an operation result (for example, successful operation, or failed operation), and the actual cause of the corresponding fault is determined by the combination of the operation results of each tool.

[0030] Exemplarily, the first configuration information may include determination information of the operation result of the first detection tool, and the corresponding determination information may be subsequently found through the first configuration information. Exemplarily, the suspected cause of the first fault may be the same as the actual cause of the first fault. Exemplarily, the actual cause of the first fault may be different from the suspected cause of the first fault.

[0031] It can be seen from the above scheme that in this application, the real cause of the fault can be determined based on the operation result of the detection tool, and then a tool to repair the fault can be configured through the fault knowledge base, and the operation and maintenance process can be executed again.

[0032] In a second aspect, the present application proposes a computing device, which is used to execute the method of the first aspect above. Specifically, the device may include a unit and / or module for executing a method for application operation and maintenance proposed in the present application, such as a transceiver unit and / or a processing unit. In the present application, the computing device is applied to a cloud management platform. Alternatively, the computing device is a cloud management platform.

[0033] In a third aspect, the present application provides a computing device, the device comprising: at least one processor, configured to execute a computer program or instruction stored in a memory to perform the method of the first aspect. Optionally, the device further comprises a memory, configured to store a computer program or instruction. Optionally, the device further comprises a communication interface, and the processor reads the computer program or instruction stored in the memory through the communication interface.

[0034] In one implementation, the device is a computing device used in a cloud management platform for implementing the functions of the above communication method in a chip. Alternatively, the device is a cloud management platform.

[0035] In another implementation, the device is a chip, a chip system or a circuit applied to a cloud management platform for implementing the functions of the above-mentioned communication method in a chip.

[0036] In a fourth aspect, the present application provides a processor, comprising: an input circuit, an output circuit and a processing circuit. The processing circuit is used to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the method of the first aspect.

[0037] In the specific implementation process, the processor can be one or more chips, the input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be a transistor, a gate circuit, a trigger, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a transceiver, and the signal output by the output circuit can be, for example, but not limited to, output to a transmitter and transmitted by the transmitter, and the input circuit and the output circuit can be the same circuit, which is used as an input circuit and an output circuit at different times. The embodiments of the present application do not limit the specific implementation methods of the processor and various circuits.

[0038] For the operations such as sending and acquiring / receiving involved in the processor, unless otherwise specified, or unless they conflict with their actual function or internal logic in the relevant description, they can be understood as operations such as processor output, reception, input, etc., or as sending and receiving operations performed by the radio frequency circuit and antenna, and this application does not limit this.

[0039] In a fifth aspect, a processing device is provided, comprising a processor and a memory. The processor is used to read instructions stored in the memory, and can receive signals through a transceiver and transmit signals through a transmitter to execute the method of the first aspect.

[0040] Optionally, the number of the processors is one or more, and the number of the memories is one or more.

[0041] Optionally, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

[0042] In the specific implementation process, the memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated with the processor on the same chip or can be set on different chips respectively. The embodiments of the present application do not limit the type of memory and the setting method of the memory and the processor.

[0043] It should be understood that the related data interaction process, such as sending indication information, can be a process of outputting indication information from the processor, and receiving capability information can be a process of receiving input capability information by the processor. Specifically, the data output by the processor can be output to the transmitter, and the input data received by the processor can come from the transceiver. Among them, the transmitter and the transceiver can be collectively referred to as a transceiver.

[0044] The processing device in the fifth aspect may be one or more chips. The processor in the processing device may be implemented by hardware or by software. When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor may be a general-purpose processor implemented by reading software code stored in a memory, which may be integrated in the processor or located outside the processor and exist independently.

[0045] In a sixth aspect, a computing cluster is provided, comprising at least one computing device, each computing device comprising a processor and a memory; the processor of the at least one computing device is used to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method described in any possible implementation manner in the first aspect.

[0046] Optionally, the processor may be a general-purpose processor, which may be implemented by hardware or software. When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor may be a general-purpose processor implemented by reading software code stored in a memory, which may be integrated in the processor or located outside the processor and exist independently.

[0047] In a seventh aspect, a computer-readable storage medium is provided, wherein the computer-readable medium stores a program code for execution by a device, wherein the program code includes a method for executing the above-mentioned first aspect.

[0048] According to an eighth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the method according to the first aspect.

[0049] In a ninth aspect, a chip system is provided, comprising a processor for calling and running a computer program from a memory, so that a device equipped with the chip system executes the method of the first aspect.

[0050] In a tenth aspect, a cloud service system is provided, which includes a cloud management platform, wherein the cloud management platform is used to execute the method in any possible implementation of the first aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] Figure 1 It is a schematic diagram of a cloud service scenario to which this application is applicable.

[0052] Figure 2 It is a schematic block diagram of a system architecture applicable to the present application.

[0053] Figure 3 It is a schematic block diagram of a method 300 for application operation and maintenance in a cloud system provided by the present application.

[0054] Figure 4 It is a schematic flowchart of a method for application operation and maintenance in a cloud system provided by the present application.

[0055] Figure 5 It is a schematic block diagram of a cloud management platform and tenant business deployment method provided by this application.

[0056] Figure 6 This is another schematic block diagram of a cloud management platform and tenant business deployment method provided by this application.

[0057] Figure 7 This is another schematic block diagram of a cloud management platform and tenant business deployment method provided by this application.

[0058] Figure 8 is a schematic block diagram of a computing device 800 provided in the present application.

[0059] Fig. 9 is a schematic block diagram of a computing device 900 provided in the present application.

[0060] Fig.10 This is a schematic diagram of the architecture of a computing device cluster provided by this application.

[0061] Fig.11 It is a schematic diagram of the connection between computing devices 1000A and 1000B provided by the present application through a network. DETAILED DESCRIPTION

[0062] In order to facilitate understanding of the technical solution of the present application, the following first briefly introduces some of the professional terms involved in the present application.

[0063] 1. Tenants

[0064] "Tenant" is a logical concept. For example, after a person or an enterprise registers an account on a public cloud platform, the platform considers it a "tenant". The cloud system will allocate cloud resources based on "tenants" as the basic unit. Usually, tenants can rent services provided by cloud service providers on cloud computing platforms. Tenants need to provide identity information, contact information and contact information, as well as debit account information for paying cloud service rental.

[0065] It should be understood that tenants of cloud services can be individuals, enterprises, schools, hospitals, administrative agencies, etc.

[0066] 2. Remote operation and maintenance

[0067] "Remote operation and maintenance" means that a computer system technical service engineer or manager connects to a target computer or network system that needs maintenance and management through a local area network, the Internet, or a bastion host, and performs operations such as installation, configuration, maintenance, monitoring, and management of the remote system locally. Engineers can view and handle problems without having to be on site. Usually, remote maintenance relies on remote desktop technology or other remote control tools.

[0068] With the development of cloud technology, traditional data center applications are gradually migrated to cloud platforms. In the process of application migration, multi-cloud and hybrid cloud have become a preferred option for more and more enterprises due to the data affinity and disaster recovery level of the application. At this time, the application will be distributed to multiple public cloud vendors, Internet data centers (IDC) data centers in multiple regions, and other places. Through the cloud management platform, one-stop multi-cloud and multi-data center application unified distribution, update, upgrade and other life cycle capabilities can be achieved. At this time, how to operate and maintain these applications becomes a problem that needs to be considered. In the current technical solutions, the operation and maintenance of these applications are all carried out by uniformly collecting the fault information of the applications on the cloud, and then the local personnel directly perform the operation and maintenance operations, or provide remote connection to the bastion host to authorize remote professional operation and maintenance personnel to perform the operation and maintenance operations. Further processing based on the analysis conclusions of the fault information needs to be performed by local operation and maintenance, which requires a high level of professional technical level of local operation and maintenance personnel; if professional operation and maintenance personnel need to intervene, it is necessary to provide connection and authorization means such as the bastion host, at this time, there will be security issues and increase cost investment. Therefore, in the current solutions, the operation and maintenance of cloud applications either requires the ability of local operation and maintenance personnel, or there are security issues and increased cost investment. Therefore, a method for operation and maintenance in cloud systems is needed.

[0069] In view of this, the present application proposes a method for operating and maintaining applications in a cloud system, thereby detecting application failures, providing secure remote operation and maintenance management capabilities, and reducing tenant costs.

[0070] Figure 1 is a schematic block diagram of a cloud scenario applicable to an embodiment of the present application. Figure 1 As shown, the cloud scenario may include: a cloud management platform 110 , the Internet 120 , and a client 130 .

[0071] like Figure 1 As shown, the cloud management platform 110 is used to manage the infrastructure that provides multiple cloud services. The infrastructure includes multiple cloud data centers, each of which includes multiple servers, and each server includes cloud service resources to provide corresponding cloud services to tenants. In the embodiment of the present application, the cloud service resources can be cloud databases.

[0072] The cloud management platform 110 may be located in a cloud data center, which may provide an access interface (such as an interface or an application program interface (API)). The tenant may operate the client 130 to remotely access the access interface to register a cloud account and password on the cloud management platform 110, and log in to the cloud management platform 110. After the cloud management platform 110 successfully authenticates the cloud account and password, the tenant may further pay to select and purchase a virtual machine of specific specifications (processor, memory, disk) on the cloud management platform 110. After the paid purchase is successful, the cloud management platform 110 provides the remote login account and password of the purchased virtual machine, and the client 130 may remotely log in to the virtual machine, install and run the tenant's application in the virtual machine. Therefore, the tenant may create, manage, log in and operate virtual machines in the cloud data center through the cloud management platform 110.

[0073] The functions of the cloud management platform 110 include, but are not limited to, a tenant console, computing management services, network management services, storage management services, authentication services, and image management services. The tenant console provides an interface or application programming interface (API) to interact with tenants. The computing management service is used to manage servers running virtual machines and containers and bare metal servers. The network management service is used to manage network services (such as gateways, firewalls, etc.). The storage management service is used to manage storage services (such as data bucket services). The authentication service is used to manage tenant accounts and passwords, and the image management service is used to manage virtual machine images. Tenants can use the client 130 to log in to the cloud management platform 110 through the Internet 120 to manage the rented cloud services.

[0074] Figure 2 is a schematic block diagram of a system architecture applicable to this application, such as Figure 2 As shown, the technical solution provided by the present application mainly includes a "cloud management platform 210" and an "operating environment 220", both of which support running on standard physical machines or virtual machines and other hardware devices. Among them, the "cloud management platform 210" includes a "cloud application management center 211" and a "cloud application operation and maintenance center 212". The core of the "cloud management platform 210" is the "cloud application management center 211", and the "cloud application operation and maintenance center 212" is the management and control core of the present application. In the present application, the "cloud application operation and maintenance center 212" can provide the first configuration information (for example, "operation and maintenance statement definition"), and complete the construction and distribution of the operation and maintenance tool set in combination with the fault perception process. The "application operating environment 220" may include a "user application operating environment 221" and a "temporary operation and maintenance environment 222". For example, after the "cloud application operation and maintenance center 212" generates the operation and maintenance tool set, it can be distributed using the standard capabilities of the cloud application. For example, the operation and maintenance demands can be executed in the "user application operating environment 221". Therefore, Figure 2 It is shown that the environment 221 in which the tenant application runs may include a temporary operation and maintenance tool set, which means that during the operation and maintenance process, the operation and maintenance tool set performs operation and maintenance operations in the environment 221, and the operation and maintenance tool set will be closed after the operation and maintenance is completed (it can also be understood that the resources corresponding to the tool set are released and recycled). Figure 2 A detailed introduction to each module in the.

[0075] First, the various modules included in the "cloud application operation and maintenance center 212" are introduced. The "cloud application operation and maintenance center 212" includes a "fault detection perception module 2121", a "fault knowledge base module 2122", a "fault tool center module 2123", and an "operation and maintenance audit module 2124", among which:

[0076] (1) Fault detection and perception module 2121: can perceive faults in the application running environment through alarm information, logs, control indicator analysis, etc. It should be noted that in this application, tenants are also allowed to actively declare suspected faults in the application running environment.

[0077] (2) Fault knowledge base module 2122: For example, professional operation and maintenance personnel can establish a fault knowledge base based on existing background knowledge and historical experience, and professional operation and maintenance personnel can set possible causes for various types of suspected faults. Subsequently, the fault knowledge base can generate first configuration information and fourth configuration information (for example, in the form of operation and maintenance statement definition) based on various types of faults and their corresponding causes.

[0078] (3) Fault tool center module 2123: For example, professional operation and maintenance personnel can gather and collect tools based on their operation and maintenance skills for infrastructure at all levels to form a fault tool center. The fault tool center can provide various types of tools that can be used to perform various specific operation and maintenance tasks in the operation and maintenance statement definition generated by the fault knowledge base.

[0079] The "task" in this application can be understood as how each configured tool is executed during execution, or it can also be understood as the actions and steps that each tool needs to perform.

[0080] (4) Operation and maintenance audit module 2124: responsible for process control in terms of security auditing. For example, it can read the operation status record in the operation and maintenance statement definition and finally generate an operation and maintenance work report for subsequent users or auditors to use.

[0081] Exemplarily, the "operation and maintenance tools" in this application may include fault location analysis tools at various levels, for example, including but not limited to: network analysis tools on the Linux operating system, disk input / output (IO) detection and analysis tools, performance analysis tools, and script tools for status reading and system log extraction on the Linux system, etc. For another example, it also includes: cross-host network layer routing analysis tools, command line script tools for connectivity checks, network packet loss detection tools, etc.; virtualization analysis tools for container platforms, fault analysis tools for middleware, and other analysis tools for applications such as structured query language (SQL) databases that rely on middleware, etc.

[0082] The following is an introduction to the various modules included in the "temporary operation and maintenance environment 222". The "temporary operation and maintenance environment 222" includes the "operation and maintenance execution agent module 2221", "operation and maintenance information configuration module 2222", "operation and maintenance task result processing module 2223", "operation and maintenance status management module 2224" and "operation and maintenance tool kit module 2225".

[0083] (1) Operation and maintenance execution agent module 2221: It can be understood as the execution subject of local operation and maintenance work, which reads the operation and maintenance statement definition and completes the series connection of the operation and maintenance process.

[0084] (2) Operation and maintenance information configuration module 2222: It can be understood as the input of local operation and maintenance information, and can provide users with methods for defining the environment information required for fault operation and maintenance through graphics, command lines, application programming interface (API), etc.

[0085] (3) Operation and maintenance task result processing module 2223: used to standardize the output results, convert the format of the operation results of each operation and maintenance tool, and finally obtain information such as success, failure, and fault cause.

[0086] (4) Operation and maintenance status management module 2224: can record the status information of all executed tasks, can write back to the status information defined in the operation and maintenance declaration, and restrict the information and records related to the completed operation and maintenance actions from being modified.

[0087] (5) Operation and maintenance tool suite module 2225: can be used to provide operation and maintenance processing tools for various infrastructure, applications, middleware and other technology stacks.

[0088] It should be noted that Figure 2This is only an example, and the present application does not limit the specific modules included in the system architecture. For example, multiple modules can be combined into one module, and the combined module has the functions of implementing the corresponding modules in the present application.

[0089] Figure 3 This is a schematic flow chart of a method 300 for operating and maintaining an application in a cloud system provided by the present application. The method can be executed by a cloud management platform. The cloud management platform in the present application is used to manage the infrastructure for providing cloud services. The infrastructure includes multiple cloud data centers, and each cloud data center has at least one application deployed. In addition, as mentioned above, the cloud management platform in the present application is configured with a fault knowledge base, which stores information on various faults of the application, such as Figure 3 The method comprises:

[0090] 310 , when a first failure occurs in a first application in a first cloud data center, the cloud management platform displays first configuration information to the tenant.

[0091] In the present application, the first configuration information is used to configure a first detection tool for detecting a first fault, wherein the first configuration information is generated based on information about the first fault and a fault knowledge base.

[0092] In the present application, the “first data center” is one of the multiple cloud data centers, and the first application is one of the multiple applications.

[0093] In the present application, "information on various failures of the application" may include, for example, at least one of the following: phenomenon of the failure, type of failure, impact of the failure, suspected cause of the failure, time of occurrence of the failure, and duration of the failure. Among them, "phenomenon of failure" may include, for example: power outage in the data center, server failure in the data center, inability to start the application in the data center, response timeout of the application, inability to report and update the monitoring log and running status of the application, etc.; "type of failure" may include, for example: application type failure, environment type failure, infrastructure type failure; "impact of failure" may include, for example: single point failure (for example, the failure affects a certain function), large-scale failure, the geographical scope affected by the failure, and the severity of the failure, for example, the failure affects the core function of the application, or the failure affects the secondary function of the application. "Suspected cause of failure" may include, for example: configuration error, software problem, hardware problem, etc.; illustratively, the first failure may be that the monitoring log of the application cannot be reported and updated.

[0094] In the present application, “information on various failures of an application” may also be understood as information on failures corresponding to the environment in which the application is located.

[0095] In one possible implementation, the method further includes the step of: the cloud management platform receiving input information from the tenant, the input information including information about the first fault. In another possible implementation, the method further includes the step of: the cloud management platform sending first alarm information to the tenant, the first alarm information including information about the first fault.

[0096] In one possible implementation, for example, the "fault knowledge base" may store the mapping relationship between the fault information, the suspected cause of the fault, and the information of the detection tool corresponding to the suspected cause of the fault. For another example, the "fault knowledge base" may store the mapping relationship between the fault information and the first detection tool. In the present application, it is not limited to the mapping relationship between which information is specifically stored in the fault knowledge base. As long as the fault knowledge base or the cloud management platform can determine the first detection tool based on the fault information, it falls within the reserved scope of the present application. For example, the mapping relationship can be stored in the form of a table. Therefore, when the first fault occurs in the first application, the fault knowledge base module in the cloud management platform can determine the first detection tool for the first fault based on the information of the first fault, and generate the first configuration information.

[0097] Exemplarily, the information of the first detection tool may include at least one of the following: the name of the first detection tool, the type of the detection tool, etc. The first configuration information may configure the first detection tool based on the information of the first detection tool. For example, the first configuration information is used to configure at least one of the following: a specific task performed by the first detection tool, a command executed by the first detection tool, an order of execution of tasks of the first detection tool, whether the first detection tool (or between various tasks) is executed serially or in parallel, etc. Among them, the first configuration information includes the name of the first detection tool.

[0098] In a possible implementation, before step 310, the method further includes: receiving a first instruction from the tenant, the first instruction being used to instruct to operate and maintain the first application. This step can also be understood as starting the entire operation and maintenance process in this application by way of tenant authorization.

[0099] Exemplarily, the fault perception module in the cloud management platform sends a second alarm message to the tenant, and the second alarm message is used to indicate to the tenant that a first fault occurs in the first application. Based on the second alarm message, the tenant inputs a first instruction to the cloud management platform, and the first instruction is used to instruct the operation and maintenance process of the first application. Specifically, when the user receives the second alarm message, the tenant can log in to the cloud management platform and apply for authorization to enable remote operation and maintenance of the first application. At this time, the cloud application operation and maintenance center imports the information of the first fault obtained into the fault knowledge base, and the fault knowledge base analyzes the possible cause of the fault (i.e., the suspected cause of the fault) and generates the first configuration information.

[0100] In one possible implementation, the fault knowledge base in the present application may be, for example, an AIOps system, which can integrate historical fault information of public clouds and hybrid clouds and improve fault handling efficiency.

[0101] In this application, the way in which tenants enable authorized remote operation and maintenance is not limited to the triggering of alarm information. It can also be that the tenant actively authorizes the triggering of remote operation and maintenance, or professional operation and maintenance personnel actively apply for remote operation and maintenance and are authorized and approved by the IDC user, and then remote operation and maintenance is performed.

[0102] For example, the first configuration information may be an operation and maintenance statement definition. The following is an introduction to the "operation and maintenance statement definition" in this application.

[0103] Exemplarily, in the present application, the "operation and maintenance declaration definition" can be described in a standardized format such as yaml or json. It should be understood that the yaml or json format is a resource object created by Kubernetes, wherein the json format is used for message transmission between interfaces and is suitable for development; the yaml format is used for configuration and management, and is suitable for cloud platform management. yaml is a concise non-markup language. In addition, the operation and maintenance declaration definition can also specify that modifications to executed tasks and status are not allowed, thereby ensuring that all results are traceable. Exemplarily, the operation and maintenance declaration definition can define multiple types of tools, define the execution order of tools during this operation and maintenance process, or define the order of detecting faults. For example, the operation and maintenance declaration definition can be described in the form of a table. The following Table 1 illustrates a possible operation and maintenance declaration definition.

[0104] Table 1

[0105]

[0106] In a possible implementation, the method further includes: the cloud management platform generates a tool set according to the first configuration information, and the tool set (i.e., the first detection tool) may include multiple types of tools, and each type of tool in the multiple types of tools is used to detect a type of fault. For example, each tool in the tool set can be used to detect the first fault.

[0107] Optionally, after step 310, the method further includes: the cloud management platform receives third configuration information from the tenant, the third configuration information is used to configure at least one of the following: the frequency of running the first detection tool, and the updated first detection tool.

[0108] Exemplarily, the tenant can also manually specify the scope of the remote operation and maintenance declaration definition. For example, the tenant can customize the operation and maintenance declaration scope, or use the first configuration information configured by the cloud management platform or copy the first configuration information of the historical remote operation and maintenance task to determine the first configuration information of this operation and maintenance. Exemplarily, the tenant can update the first configuration information determined by the cloud management platform, for example, the tenant continues to add tools to the first configuration information, or deletes tools. For another example, the tenant can specify the execution frequency of remote operation and maintenance. For example, the tenant can specify the frequency of remote operation and maintenance as one of the following: single immediate execution, single scheduled execution, multiple scheduled executions, or periodic execution, etc.

[0109] 320. Receive second configuration information from the tenant, where the second configuration information is used to configure a first operation and maintenance environment in the first cloud data center.

[0110] In the present application, for example, the second configuration information includes information about the connection method between the first detection tool and the first operation and maintenance environment. The information about the connection method may include, for example, one or more of the following: API interface, address, protocol, access credentials, etc. For another example, the second configuration information may also include at least one of the following: the name of the operation and maintenance environment, the user name of the operation and maintenance environment, the login password of the operation and maintenance environment, the certificate of the operation and maintenance environment, and so on. Based on the second configuration information, the first detection tool can be connected to the operation and maintenance environment.

[0111] In the present application, the first operation and maintenance environment is configured by the tenant, thereby ensuring the security of the remote operation and maintenance process, preventing the operation and maintenance tools from accessing the tenant's more private personal information during the remote process, and ensuring the security of user application data.

[0112] In one possible implementation, after the tenant completes the remote operation and maintenance authorization, he will obtain specific execution instructions for starting operation and maintenance locally, and execute the instructions in the environment where the local application is located (which can also be understood as running the first detection tool). When executing specific instructions, you can choose to run the first detection tool directly in the environment where the application is running, or, based on the opened temporary operation and maintenance environment, connect to the environment where the local application is located through the temporary operation and maintenance environment, thereby executing the first detection tool in the first operation and maintenance environment. The execution of instructions will use the multi-cloud application management channel to pull up the operation and maintenance application and related information. The "temporary operation and maintenance environment" in this application can, for example, be a pre-configured environment, and the first detection tool can be connected to the first operation and maintenance environment based on the temporary operation and maintenance environment.

[0113] For example, the "second configuration information" in the present application may be an environment declaration definition. Exemplarily, the environment declaration definition may be described in a standardized format such as yaml or json. The information of each infrastructure or resource may also be defined in the environment declaration definition. The format may be extended, and the operation and maintenance permissions of each tool may also be defined to control the scope of influence on the environment, for example, whether each tool is a read-only operation or a write operation in the environment, or, both read-only operation and write operation exist. Among them, the information of the infrastructure may include, for example, at least one of the following: the type of Iaas (for example, whether Iaas is a virtualized or physical machine), the type of switch, the type of networking, and the like; the information of the resource may include, for example, at least one of the following: resources of the virtual machine, CPU resources, memory resources, and the like. In addition, the operation and maintenance declaration definition may also reference and associate the environment declaration definition. The environment declaration only defines the environment where the tenant's local application is located, so that it can be read by the operation and maintenance declaration definition and cannot act outside the local environment. The environment declaration definition may be described in the form of a table, for example, and the following Table 2 illustrates a possible environment declaration definition, based on which the first detection tool can be connected to the first operation and maintenance environment.

[0114] Table 2

[0115]

[0116] Exemplarily, the operation and maintenance execution agent in the cloud management platform will drive the execution of operation and maintenance tools at each stage based on the operation and maintenance declaration definition and the environment declaration definition, and can obtain the running results of the operation and maintenance tasks.

[0117] 330. Run a first detection tool in a first operation and maintenance environment.

[0118] Optionally, the first configuration information also includes determination information of the operation result of the first detection tool. At this time, the real cause of the first fault corresponding to the information of the first fault can be determined based on the operation result and the determination information of the operation result. Then, the cloud management platform can determine the fourth configuration information based on the real cause of the first fault and the fault knowledge base. The fourth configuration information is used to configure the first repair tool for repairing the first fault. The cloud management platform runs the first repair tool in the first operation and maintenance environment.

[0119] In a possible implementation, the "fault knowledge base" in the present application may store the judgment information of the operation result of the first detection tool, the real cause of the first fault, and the information of the first repair tool corresponding to the real cause of the first fault. The real cause of the first fault is determined according to the operation result and the judgment information of the operation result in the fault knowledge base; the information of the first repair tool is determined according to the real cause of the first fault and the fault knowledge base, and the fourth configuration information is determined according to the information of the first repair tool, and the fourth configuration information is used to configure the first repair tool to repair the first fault.

[0120] For example, the judgment information of the operation result includes the judgment results corresponding to each operation and maintenance tool, and the mapping relationship between each judgment result and the real cause of the first fault. For example, the judgment result may be to determine whether a tool or a task runs successfully or fails. For example, based on the operation result of a tool and the judgment result in the judgment information, it is determined that the tool runs successfully. Therefore, based on different judgment results, the real cause of the first fault can be determined, combined with the information of the first repair tool, and the fourth configuration information is determined, and the corresponding fault repair processing measures are executed.

[0121] For example, the determination information of the operation result includes various determination results (or combinations of various determination results), and the mapping relationship between the actual cause of the first fault corresponding to each of the various determination results (or combinations of various determination results). Therefore, the actual cause of the first fault can be determined based on different determination results, combined with the information of the first repair tool, and the fourth configuration information is determined. Exemplarily, each tool in the first detection tool corresponds to a determination result, and the actual cause of the corresponding fault is determined by the combination of the determination results of each tool.

[0122] Exemplarily, the information of the first repair tool may include at least one of the following: the name of the first repair tool, the type of the first repair tool. The fourth configuration information may include at least one of the following: the specific task executed by the first repair tool, the command executed by the first repair tool, the order of execution of the tasks of the first repair tool, whether the first repair tool (or each task) is executed serially or in parallel, etc. The fourth configuration information includes the name of the first repair tool.

[0123] Exemplarily, the first configuration information may include determination information of the operation result of the first detection tool, and the corresponding determination information may be subsequently found through the first configuration information.

[0124] Based on the above description, it can also be understood that in this application, in a possible implementation scenario, the fault knowledge base stores the mapping relationship between the fault information (e.g., the fault phenomenon, the fault type, the fault impact), the fault cause, and the detection tool information, and the fault knowledge base can generate the first configuration information based on the mapping relationship. In addition, the fault knowledge base stores the mapping relationship between the judgment information of the operation result, the real cause of the fault, and the repair tool information, and the fault knowledge base can generate the fourth configuration information based on the mapping relationship.

[0125] In the present application, the first detection tool may include at least one detection tool, and the first repair tool may also include at least one detection tool. Exemplarily, in some scenarios, some tools in the first detection tool may be the same as some tools in the first repair tool.

[0126] If the initial operation and maintenance statement is executed and the cause of the fault and the treatment measures are still not obtained, the SRE operation and maintenance personnel can import the updated operation and maintenance statement definition into the fault knowledge base based on the operation and maintenance statement after monitoring the status, and then re-execute the updated operation and maintenance process. In other words, the cloud management platform in this application can update the operation and maintenance task status multiple times and continuously execute subsequent tasks based on the operation and maintenance statement definition. It should be understood that the specific execution of this task can be serial or parallel, without limitation.

[0127] Optionally, the operation and maintenance tool includes manual interactive execution tasks, which allows SRE operation and maintenance personnel to directly use the tool to perform some configuration updates and command execution within the scope of the allowed permissions at some stages. All input and output of interactive tasks will also be automatically updated to the task execution results. Finally, when the task is executed to the fault repair exit, the task ends, and the operation and maintenance audit module will record the task status of all processes and feedback to update the fault knowledge base.

[0128] When the fault is repaired and the local operation and maintenance is completed, the tenant can shut down the remote operation and maintenance on the cloud management platform, and the cloud management platform will receive the shutdown instruction. At the same time, the cloud operation and maintenance center can close the connection with the local operation and maintenance tool set and destroy the temporary operation and maintenance environment.

[0129] Figure 4 This is a schematic flow chart of application operation and maintenance provided by this application, such as Figure 4As shown, if the fault detection perception module detects that a certain application has failed, a fault alarm can be sent to the tenant (or SRE at the same time) through the cloud management platform. After receiving the fault alarm from the cloud management platform, the tenant can log in to the cloud management platform for authorization, thereby starting remote operation and maintenance. At this time, the multi-cloud management platform configures the operation and maintenance tools through the fault tool center in the fault knowledge base, the fault tool center can pull the operation and maintenance tools through the local fault tool set, and the tenant can open the local operation and maintenance environment and set the local operation and maintenance environment information. Then, the local fault tool set can execute the operation and maintenance tools step by step based on the operation and maintenance statement definition configured by the tenant, and synchronize the operation results of each step to the operation and maintenance audit. Optionally, in this application, the SRE can also monitor the status of the operation and maintenance task. When the operation and maintenance task is completed, if the cause of the fault and the repair measures are still unknown, the SRE can also manually update the fault knowledge base so that the fault knowledge base can generate an updated operation and maintenance statement definition, thereby determining the updated operation and maintenance tool, and then execute the updated task again, and synchronize the operation results to the operation and maintenance audit. When the fault detection and perception module detects that the fault has been eliminated and the operation and maintenance task is completed, the operation results in the operation and maintenance can be updated to the fault knowledge base. At this time, the tenant can close the remote operation and maintenance, and usually also close the local operation and maintenance tool.

[0130] In this application, the deployment relationship between the cloud management platform and the tenant data center is not limited to the scenario of interaction between the public cloud and the private cloud. The following introduces the deployment method between the environment where the cloud management platform in this application is located and the environment where the tenant application is located.

[0131] Method 1

[0132] The cloud management platform is located in the public cloud, and the tenant business is located in the tenant IDC. For example, the cloud management platform can be provided by a public cloud vendor, providing multi-cloud management capabilities at the regional or global level. The IDC only applies for an independent tenant account on the multi-cloud management platform. The tenant environment is located in the self-built IDC computer room and is connected to the cloud management platform of the public cloud vendor through dedicated lines, VPNs, public networks, etc. Remote operation and maintenance is initiated in the tenant account of the cloud management platform and pushed to the self-built IDC environment to perform operation and maintenance tasks, such as Figure 5 shown.

[0133] Method 2

[0134] The cloud management platform is located in the public cloud, and the tenant business is in other cloud environments. The cloud management platform is provided by public cloud vendors and provides multi-cloud management capabilities at the regional or global level. IDC tenants apply for independent tenant accounts on the cloud management platform. The tenant environment is located in the environment of other cloud vendors that are purchased or leased and connected to the multi-cloud management platform of the public cloud vendor through dedicated lines, VPNs, public networks, etc. Optionally, the two cloud vendor tenant accounts can be authorized to take over the operation and maintenance of the cloud resources of the corresponding vendor, such as Figure 6 shown.

[0135] Method 3

[0136] The cloud management platform and tenant services are both part of the private cloud environment: The cloud management platform and tenant services are deployed in a private cloud scenario and can belong to the same data center or different data centers. Figure 7 shown.

[0137] In this application, in a possible scenario, the tenant can complete the authorization in advance, provide a complete tool set and environmental information, and each time an application fails, a fault handling workflow will be automatically generated and automatically executed. Only when the fault knowledge base information is insufficient to solve the fault, will professional operation and maintenance personnel intervene to process and repair and update the knowledge base, so as to achieve the goal of automatically repairing the application. For example, in this scenario, it can be a permanent operation and maintenance environment, and the operation and maintenance tool set is also permanent to provide a full set of tools required for operation and maintenance. At this time, the tenant can preset the environment where the application is located in advance. In this scenario, the above-mentioned "temporary operation and maintenance environment" can be understood as a permanent operation and maintenance environment, because even after the operation and maintenance is completed, the environment will not be destroyed, so it can be understood as a "permanent operation and maintenance environment." Other operation and maintenance processes are similar to the operation and maintenance processes under the temporary operation and maintenance environment introduced above, and will not be repeated.

[0138] In addition, in this application, the cloud operation and maintenance center capabilities can also be serviced to provide cloud service capabilities to the outside world. For example, the professional operation and maintenance capabilities of public cloud vendors can be packaged into professional services. This scenario is also limited to public cloud scenarios, and is also applicable in private cloud scenarios.

[0139] It can be understood that the term "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0140] Those skilled in the art should be aware that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed in the form of hardware or computer software driving hardware 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.

[0141] The embodiment of the present application can divide the computing device into functional modules according to the above method example. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. The following is an example of dividing each functional module corresponding to each function.

[0142] Figure 8 8 is a schematic block diagram of a computing device 800 provided in an embodiment of the present application. As shown in the figure, the computing device 800 may include: a transceiver module 810, a processing module 820, and a display module 830.

[0143] Among them, the above-mentioned modules are respectively used to execute the steps of the above-mentioned methods, which will not be repeated here.

[0144] It should also be understood that the computing device 800 herein is embodied in the form of a functional unit. The term "unit" herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (e.g., a shared processor, a dedicated processor, or a group processor, etc.) and a memory for executing one or more software or firmware programs, a combined logic circuit, and / or other suitable components that support the described functionality.

[0145] The computing device 800 of each of the above schemes has the function of implementing the corresponding steps of the above method 300. The functions can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the determination unit can be replaced by a processor to respectively perform the sending and receiving operations and related processing operations in each method embodiment. In addition, the determination unit can be a processing circuit.

[0146] In a possible implementation, the device 800 may be a device in the method 300 described above that is applied in a cloud management platform, and the device is used to execute the method 300 described above.

[0147] In another possible implementation, the device 800 may be the cloud management platform in the above method 300 , and the cloud management platform is used to execute the actions in the above method 300 .

[0148] It should be pointed out that Figure 8 The computing device in the above method can be the cloud management platform (or the computing device in the cloud management platform) in the above method embodiment, or it can be a chip or chip system corresponding to the cloud management platform (or the computing device in the cloud management platform), such as a system on chip (SoC). The processing unit is a processor or microprocessor or integrated circuit integrated on the chip. This is not limited here.

[0149] Fig. 9 is a schematic block diagram of another computing device 900 provided in an embodiment of the present application. As shown in the figure, the device 900 includes: at least one processor 920. The processor 920 is coupled to the memory and is used to execute instructions stored in the memory to send signals and / or receive signals. Optionally, the device 900 also includes a memory 930 for storing instructions. Optionally, the device 900 also includes a transceiver 910, and the processor 920 controls the transceiver 910 to send signals and / or receive signals.

[0150] It should be understood that the processor 920 and the memory 930 may be combined into one processing device, and the processor 920 is used to execute the program code stored in the memory 930 to implement the above functions. In specific implementation, the memory 930 may also be integrated into the processor 920 or independent of the processor 920.

[0151] It should also be understood that the transceiver 910 may include a transceiver (or receiver) and a transmitter (or transmitter). The transceiver may further include an antenna, and the number of antennas may be one or more. The transceiver 910 may also be a communication interface or an interface circuit.

[0152] Specifically, the processor 920 in the device 900 may correspond to the processing module 820 in the device 800. The transceiver 910 in the device 900 may correspond to the processing module 810 in the device 800.

[0153] As a solution, the device 900 is used to implement the steps corresponding to the device applied in the cloud management platform in the above method 300 embodiment.

[0154] As another solution, the device 900 is used to implement the steps corresponding to the cloud management platform in the above method 300 embodiment.

[0155] For example, the processor 920 is configured to execute a computer program or instruction stored in the memory 930 to implement each step in the above method 300 .

[0156] Fig.10 : is a schematic diagram of the architecture of a computing device cluster provided in an embodiment of the present application. The computing device cluster includes at least one computing device. The computing device may be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device may also be a terminal device such as a desktop computer, a laptop computer, or a smart phone. Fig.10 As shown, the computing device cluster includes at least one computing device 1000. The memory 1030 in one or more computing devices 1000 in the computing device cluster may store the same instructions for executing the actions executed by the cloud management platform (or computing devices in the cloud management platform) in the above embodiment 300.

[0157] In some possible implementations, the memory 1030 of one or more computing devices 1000 in the computing device cluster may also respectively store partial instructions for executing the actions performed by the cloud management platform (or, computing devices in the cloud management platform) in the method 300 described in the above embodiment. In other words, the combination of one or more computing devices 1000 can jointly execute instructions for executing the actions performed by the cloud management platform (or, computing devices in the cloud management platform) described in the above embodiment.

[0158] It should be noted that the memory 1030 in different computing devices 1000 in the computing device cluster may store different instructions, which are respectively used to execute part of the functions of the computing device 1000. That is, the instructions stored in the memory 1030 in different computing devices 1000 may implement the functions of one or more modules of the transceiver module 810 and the processing module 820.

[0159] Alternatively, the memory 1030 in different computing devices 1000 in the computing device cluster may store different instructions, which are respectively used to execute part of the functions of the cloud management platform (or the computing devices in the cloud management platform) corresponding to the above devices 800 and 900. That is, the instructions stored in the memory 1030 in different computing devices 1000 can implement the functions of one or more modules in the transceiver module 810 and the processing module 820.

[0160] In some possible implementations, one or more computing devices in the computing device cluster may be connected via a network, which may be a wide area network or a local area network. Fig.11 A possible implementation is shown. Fig.11 As shown, two computing devices 1000A and 1000B are connected via a network. Specifically, they are connected to the network via a communication interface in each computing device.

[0161] It should be understood that Fig.11 The functions of the computing device 1000A shown in FIG. 1000A may also be completed by multiple computing devices 1000. Similarly, the functions of the computing device 1000B may also be completed by multiple computing devices 1000.

[0162] In this embodiment, a computer program product including instructions is also provided, and the computer program product may be software or a program product including instructions that can be run on a computing device cluster or stored in any available medium. When the computer program product is run by a computing device cluster, the computing device cluster executes the method provided above, or the computing device cluster implements the function of the apparatus provided above.

[0163] In this embodiment, a computer-readable storage medium is also provided, and the computer-readable storage medium can be any available medium that can be stored by a computing device or a data storage device such as a data center containing one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital video disc (DVD)), or a semiconductor medium (e.g., a solid-state hard disk), etc. The computer-readable storage medium includes instructions, and when the instructions in the computer-readable storage medium are executed on a computing device, the computing device executes the method provided above.

[0164] 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.

[0165] 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 embodiments and will not be repeated here.

[0166] 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 embodiments described above are 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.

[0167] 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 solution of this embodiment.

[0168] 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.

[0169] If the functions are implemented in the form of software functional units and sold or used as independent products, they 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. The computer software product is stored in a storage medium and includes several 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 methods 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.

[0170] The above is only a specific implementation of the present application, but the protection scope of the present application 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 application should be based on the protection scope of the claims.

Claims

1. A method for application operation and maintenance in a cloud system, characterized in that: The method is applied to a cloud management platform, the cloud management platform is used to manage the infrastructure for providing cloud services, the infrastructure includes multiple cloud data centers, each cloud data center has at least one application deployed, the cloud management platform is configured with a fault knowledge base, the fault knowledge base stores information on multiple faults of the application, the method includes: When a first fault occurs in a first application in a first cloud data center, first configuration information is displayed to a tenant, where the first configuration information is used to configure a first detection tool for detecting the first fault, and the first configuration information is generated according to information about the first fault and the fault knowledge base; receiving second configuration information from the tenant, where the second configuration information is used to determine a first operation and maintenance environment in the first cloud data center; Run the first detection tool in the first operation and maintenance environment.

2. The method according to claim 1, characterized in that Before displaying the first configuration information to the tenant, the method further includes: A first instruction is received from the tenant, where the first instruction is used to instruct operation and maintenance of the first application.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: Input information is received from the tenant, where the input information includes information about the first fault.

4. The method according to claim 1 or 2, characterized in that: The method further comprises: A first alarm message is sent to the tenant, where the first alarm message includes information about the first fault.

5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: Sending second alarm information to the tenant, where the second alarm information is used to indicate to the tenant that the first failure occurs in the first application.

6. The method according to any one of claims 1 to 5, characterized in that The fault knowledge base stores a mapping relationship between the fault information and the detection tool information, and the method further includes: Determining information of the first detection tool according to information of the first fault and the mapping relationship; The first configuration information is generated according to the information of the first detection tool.

7. The method according to claim 6, characterized in that The fault information includes at least one of the following: the phenomenon of the fault, the type of the fault, the impact of the fault, the suspected cause of the fault, the time when the fault occurs, and the duration of the fault.

8. The method according to any one of claims 1 to 7, characterized in that The first detection tool includes a plurality of types of tools, each type of tool in the plurality of types of tools is used to detect at least one type of fault.

9. The method according to claim 8, characterized in that After displaying the first configuration information to the tenant, the method further includes: Receive third configuration information from the tenant, where the third configuration information is used to configure at least one of the following: a frequency of running the first detection tool, and an updated first detection tool.

10. The method according to any one of claims 1 to 9, characterized in that The second configuration information includes information about a connection method between the first detection tool and the first operation and maintenance environment.

11. The method according to any one of claims 1 to 10, characterized in that The fault knowledge base stores the determination information of the operation result of the detection tool, the real cause of the fault, and the information of the repair tool corresponding to the real cause of the fault. The method further comprises: Determine a first operation result of running the first detection tool in the first operation and maintenance environment; Determine the true cause of the first fault according to the first operation result and the determination information of the operation result in the fault knowledge base; Determine information of the first repair tool according to the real cause of the first fault and the fault knowledge base, and determine fourth configuration information according to the information of the first repair tool, wherein the fourth configuration information is used to configure the first repair tool to repair the first fault; The first repair tool is run in the first operation and maintenance environment.

12. The method according to any one of claims 1 to 11, characterized in that: The cloud management platform is deployed in a public cloud, and the first cloud data center is deployed in an Internet data center, or; The cloud management platform is deployed in a first public cloud, and the first cloud data center is deployed in a second public cloud, or; The cloud management platform and the first cloud data center are both deployed in a private cloud.

13. A computing device, characterized in that: The computing device is applied to a cloud management platform, and the cloud management platform is used to manage the infrastructure for providing cloud services, and the infrastructure includes multiple cloud data centers, and at least one application is deployed on each cloud data center. The cloud management platform is configured with a fault knowledge base, and the fault knowledge base stores information on multiple faults of the application. The computing device includes: a display module, a transceiver module, and a processing module, wherein: In the case where a first fault occurs in a first application in a first cloud data center, the display module is used to display first configuration information to the tenant, where the first configuration information is used to determine a first detection tool for detecting the first fault, and the first configuration information is generated according to information about the first fault and the fault knowledge base; The transceiver module is used to receive second configuration information from the tenant, where the second configuration information is used to configure a first operation and maintenance environment in the first cloud data center; The processing module is used to run the first detection tool in the first operation and maintenance environment.

14. The computing device according to claim 13, characterized in that The transceiver unit is further used to receive a first instruction from the tenant, where the first instruction is used to instruct operation and maintenance of the first application.

15. The computing device according to claim 13 or 14, characterized in that The transceiver unit is used to receive input information from the tenant, where the input information includes information about the first fault.

16. The computing device according to claim 13 or 14, characterized in that The transceiver unit is used to send first alarm information to the tenant, where the first alarm information includes information about the first fault.

17. The computing device according to claim 16, characterized in that The transceiver unit is used to send second alarm information to the tenant, where the second alarm information is used to indicate to the tenant that the first failure occurs in the first application.

18. The computing device according to any one of claims 13 to 17, characterized in that: The fault knowledge base stores a mapping relationship between the information of the first fault and the information of the first detection tool. The processing unit is used to determine information of a first detection tool according to information of the first fault and the mapping relationship; The processing unit is used to generate the first configuration information according to the information of the first detection tool.

19. The computing device according to claim 18, characterized in that The fault information includes at least one of the following: the phenomenon of the fault, the type of the fault, the impact of the fault, the suspected cause of the fault, the time when the fault occurs, and the duration of the fault.

20. The computing device according to any one of claims 13 to 19, characterized in that The first detection tool includes a plurality of types of tools, each type of tool in the plurality of types of tools is used to detect at least one type of fault.

21. The computing device according to any one of claims 13 to 20, characterized in that The transceiver unit is used to receive third configuration information from the tenant, where the third configuration information is used to configure at least one of the following: a frequency of running the first detection tool, and an updated first detection tool.

22. The computing device according to any one of claims 13 to 21, characterized in that The second configuration information includes information about a connection method between the first detection tool and the first operation and maintenance environment.

23. The computing device according to any one of claims 13 to 22, characterized in that The fault knowledge base stores the determination information of the operation result of the first detection tool, the real cause of the first fault, and the information of the first repair tool corresponding to the real cause of the first fault. The processing unit is used to determine the operation result of running the first detection tool in the first operation and maintenance environment; The processing unit is used to determine the real cause of the first fault corresponding to the information of the first fault according to the operation result and the determination information of the operation result in the fault knowledge base; The processing unit is used to determine the real cause of the first fault according to the real cause of the first fault and the determination information of the operation result in the fault knowledge base, and determine third configuration information according to the real cause of the first fault, wherein the third configuration information is used to configure a first repair tool for repairing the first fault; The processing unit is used to run the first repair tool in the first operation and maintenance environment.

24. The computing device according to any one of claims 13 to 23, characterized in that: The cloud management platform is deployed in a public cloud, and the first cloud data center is deployed in an Internet data center, or; The cloud management platform is deployed in a first public cloud, and the first cloud data center is deployed in a second public cloud, or; The cloud management platform and the first cloud data center are both deployed in a private cloud.

25. A computing device, characterized in that The method comprises a processor and a memory, wherein the processor runs instructions in the memory, so that the processor performs the method according to any one of claims 1 to 12.

26. A computing device cluster, characterized in that: comprising at least one computing device, each computing device comprising a processor and a memory; The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method according to any one of claims 1 to 12.

27. A computer program product comprising instructions, characterized in that When the instructions are executed by a computing device cluster, the computing device cluster is caused to perform the method according to any one of claims 1 to 12.

28. A computer-readable storage medium, characterized in that: The method comprises computer program instructions, and when the computer program instructions are executed by a computing device cluster, the computing device cluster performs the method according to any one of claims 1 to 12.

Images