Fault processing method and device of cloud host, electronic equipment and storage medium
By determining the fault processing chain in the cloud server and migrating the virtual machine according to the priority order, the problem of slow virtual machine migration speed is solved, resulting in failure failure failure failures not be handled in time, and the success rate of fault processing and business stability are improved.
Patent Information
- Application Number
- CN202410987860.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-23
- Publication Date
- 2024-11-12
AI Technical Summary
When the cloud server host fails, the virtual machine migration speed is slow, resulting in the failure not being processed in time, which may cause the host to go down but the virtual machine has not been migrated, affecting business continuity and stability.
After the host fails, the fault processing chain is determined according to the fault condition, which includes at least two fault processing methods. The virtual machine is migrated according to the priority order of the fault processing chain. If the migration fails, switch to the next processing method until it is completed. Migration or troubleshooting is completed and rollback or cleanup operations are performed if necessary.
It improves the success rate of fault handling, avoids the inability to handle virtual machines due to migration failure, reduces labor costs, and ensures high availability and business continuity of cloud hosts.
Smart Images

Figure CN118939459A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of data processing technology, and in particular to a cloud host fault handling method and device, electronic equipment, and storage medium. Background Art
[0002] As cloud computing technology matures, cloud servers have become more advantageous than traditional IDCs, and cloud-based services have become a trend. As the main body that carries customer services, the high availability of cloud servers determines the continuity and stability of customer services, and their importance is self-evident.
[0003] At present, different failure situations may occur in the host machine, and there are some scenarios where the virtual machines cannot self-heal in time. Usually, the failure of the host machine is gradually serious until it crashes or crashes. At present, the existing technology handles the virtual machines in the failed host machine in a traditional single processing method, and the migration speed is slow. Therefore, as the failure time increases, the host machine may crash but the virtual machines in the host machine have not been migrated, resulting in some virtual machine failures cannot be handled in time. Summary of the invention
[0004] The present invention provides a cloud host fault handling method, device, electronic device and storage medium.
[0005] According to a first aspect of the present disclosure, a method for handling a cloud host failure is provided, comprising:
[0006] After confirming that the host system has a fault, determine a fault handling chain according to the fault situation; wherein the fault handling chain includes at least two fault handling methods;
[0007] The virtual machines in the host system are migrated according to the priority order of the fault handling methods in the fault handling chain; wherein the host system includes at least one virtual machine.
[0008] Optionally, migrating the virtual machines in the host system according to the priority order of the fault handling methods in the fault handling chain includes:
[0009] Determine, according to the priority order of the fault handling methods of the fault handling chain, a first fault handling method to migrate the virtual machines in the host system;
[0010] Acquire a virtual machine that fails to migrate, and determine a second fault handling method to migrate the virtual machine that fails to migrate according to the priority order of the fault handling methods in the fault handling chain;
[0011] The host system migration step is repeated until the migration of the virtual machines in the host system is completed, or the fault handling method in the fault handling chain is determined.
[0012] Optionally, before obtaining the virtual machine that failed to migrate, and determining the second fault handling method to migrate the virtual machine that failed to migrate according to the priority order of the fault handling methods in the fault handling chain, the method further includes:
[0013] Rollback or cleanup is performed on the virtual machine whose migration fails.
[0014] Optionally, after confirming that the host system has a fault, determining the fault handling chain according to the fault condition further includes:
[0015] Analyze the fault condition of the host system and determine at least two fault handling methods; wherein the fault handling methods corresponding to different fault conditions have different priority orders;
[0016] A fault handling chain is generated according to the priority order between the fault handling modes.
[0017] Optionally, the migration step includes a pre-operation, a main operation and a post-operation, and the step of rolling back or cleaning up the failed virtual machine also includes:
[0018] When the migration failure step is a pre-operation, rolling back or clearing the pre-operation of the virtual machine that failed to migrate; or
[0019] When the migration failure step is the main operation, roll back or clean up the pre-operation and the main operation of the virtual machine that failed to migrate; or
[0020] When the migration failure step is a post-operation, the pre-operation, main operation and post-operation of the virtual machine that failed to migrate are rolled back or cleared.
[0021] According to a second aspect of the present disclosure, a cloud host fault handling device is provided, comprising:
[0022] A determination unit, configured to determine a fault handling chain according to the fault condition after confirming that the host system has a fault; wherein the fault handling chain includes at least two fault handling methods;
[0023] A migration unit is used to migrate the host system according to the priority order of the fault processing methods in the fault processing chain.
[0024] Optionally, the migration unit includes:
[0025] A first migration module, configured to determine a first fault handling method to migrate the virtual machines in the host system according to the priority order of the fault handling methods in the fault handling chain;
[0026] A second migration module is used to obtain a virtual machine that has failed to migrate, and determine a second fault handling method to migrate the virtual machine that has failed to migrate according to the priority order of the fault handling methods in the fault handling chain;
[0027] The third migration module is used to repeat the steps of host system migration until the migration of the virtual machines in the host system is completed, or the fault handling method in the fault handling chain is determined.
[0028] Optionally, the device further comprises:
[0029] The rollback unit is used to obtain the virtual machine that failed to migrate in the second migration module, and determine the second fault handling method to perform rollback or cleanup on the virtual machine that failed to migrate before migrating the virtual machine that failed to migrate according to the priority order of the fault handling methods in the fault handling chain.
[0030] Optionally, the determining unit further includes:
[0031] A determination module, configured to analyze the fault condition of the host system and determine at least two fault handling methods; wherein the fault handling methods corresponding to different fault conditions have different priority orders;
[0032] A generating module is used to generate a fault processing chain according to the priority order between the fault processing modes.
[0033] Optionally, the migration step includes a pre-operation, a main operation and a post-operation, and the rollback unit also includes
[0034] A first rollback module is used to roll back or clean up the preceding operation of the virtual machine that failed to migrate when the migration failed step is a preceding operation; or
[0035] A second rollback module is used to roll back or clean up the pre-operation and main operation of the virtual machine that failed to migrate when the migration failed step is the main operation; or
[0036] The third rollback module is used to roll back or clean up the pre-operation, main operation and post-operation of the virtual machine that failed to migrate when the migration failure step is a post-operation.
[0037] According to a third aspect of the present disclosure, there is provided an electronic device, including:
[0038] at least one processor; and
[0039] a memory communicatively connected to the at least one processor; wherein,
[0040] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method described in the first aspect.
[0041] According to a fourth aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer instructions is provided, wherein the computer instructions are used to enable the computer to execute the method described in the first aspect.
[0042] According to a fifth aspect of the present disclosure, a computer program product is provided, comprising a computer program, wherein when the computer program is executed by a processor, the computer program implements the method as described in the first aspect above.
[0043] The cloud host fault handling method, device, electronic device and storage medium provided by the present disclosure have the following main technical solutions: after confirming that a host system fault occurs, determining a fault handling chain according to the fault situation; wherein the fault handling chain includes at least two fault handling methods; migrating the host system according to the priority order of the fault handling methods in the fault handling chain; wherein the host system includes at least one virtual machine. Compared with the related art, the embodiment of the present application determines a fault handling chain by analyzing the fault situation, processes the host system according to the fault handling chain, and sends the virtual machine that failed to be processed by the previous fault handling method to the next fault handling method for processing, thereby avoiding the situation where the subsequent virtual machines cannot be processed due to the virtual machine being stuck, improving the success rate of fault handling, and reducing labor costs.
[0044] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0045] The accompanying drawings are used to better understand the present solution and do not constitute a limitation of the present disclosure.
[0046] Figure 1 A flowchart of a cloud host fault handling method provided by an embodiment of the present disclosure;
[0047] Figure 2 A flowchart of a cloud host fault handling method provided by an embodiment of the present disclosure;
[0048] Figure 3 A flowchart of a cloud host fault handling method provided by an embodiment of the present disclosure;
[0049] Figure 4 A schematic diagram of a return operation provided by an embodiment of the present disclosure;
[0050] Figure 5 A schematic diagram of the structure of a cloud host fault handling device provided by an embodiment of the present disclosure;
[0051] Figure 6 A schematic diagram of the structure of a cloud host fault handling device provided by an embodiment of the present disclosure;
[0052] Figure 7 A schematic block diagram of an exemplary electronic device provided for an embodiment of the present disclosure. DETAILED DESCRIPTION
[0053] The following is a description of exemplary embodiments of the present disclosure in conjunction with the accompanying drawings, including various details of the embodiments of the present disclosure to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present disclosure. Similarly, for the sake of clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description.
[0054] The following describes a cloud host fault handling method, device, electronic device, and storage medium according to an embodiment of the present disclosure with reference to the accompanying drawings.
[0055] Figure 1 A flowchart of a cloud host fault handling method provided by an embodiment of the present disclosure.
[0056] like Figure 1 As shown, the method comprises the following steps:
[0057] Step 101, after confirming that a host system fails, determine a fault processing chain according to the fault situation; wherein the fault processing chain includes at least two fault processing methods.
[0058] In some embodiments, fault handling methods include hot migration, evacuation, cold migration, manual failover, etc. Different fault handling methods are applicable to different processing scenarios. For example, hot migration migrates virtual machines, containers, or applications running in the host system from one physical server to another without interrupting services; evacuation is usually used to respond to natural disasters, security threats, or other emergencies to protect data and ensure the continuous operation of the business.
[0059] Different fault handling methods are combined to form a complete fault handling chain. In practical applications, a suitable fault handling chain can be designed and executed according to the specific fault type, system requirements and emergency plan to maximize the reliability and availability of the system. Specifically, it can be determined according to the fault situation, and the embodiments of the present application are not limited to this.
[0060] The host machine is a physical computer running virtualization software, which provides hardware resources such as CPU, memory, storage, etc. The virtual machine is a computer system simulated by software running on the host machine. It uses the hardware resources of the host machine to run an independent operating system, just like running multiple independent computer systems on a physical machine.
[0061] Step 102: Migrate the host system according to the priority order of the fault handling methods in the fault handling chain; wherein the host system includes at least one virtual machine.
[0062] In some embodiments, in the current fault situation, applicable fault handling methods can be placed in the fault handling chain, but the handling effects may be different. There are different priorities of fault handling methods in the fault handling chain. When migrating, the processing order is determined according to the priority order of the fault handling methods. Use the fault handling methods with higher priorities to handle first, and then consider using other fault handling methods with lower priorities. Specifically, according to the specific situation of the system and the design of the fault handling chain, the priority order of the fault handling methods can be flexibly adjusted, and the host system can be migrated in time to minimize the impact of the fault on the system and ensure the normal operation of the system.
[0063] The cloud host fault handling method provided by the present disclosure has the following main technical solutions: after confirming that the host system has a fault, determining a fault handling chain according to the fault situation; wherein the fault handling chain includes at least two fault handling methods; migrating the host system according to the priority order of the fault handling methods in the fault handling chain; wherein the host system includes at least one virtual machine. Compared with the related art, the embodiment of the present application determines a fault handling chain by analyzing the fault situation, processes the host system according to the fault handling chain, and sends the virtual machine that failed to be processed by the previous fault handling method to the next fault handling method for processing, thereby avoiding the situation where the subsequent virtual machines cannot be processed due to the virtual machine being stuck, improving the success rate of fault handling, and reducing labor costs.
[0064] In some embodiments, the fault handling methods in the fault handling chain have different priority orders, so when processing, the priority order is used. Figure 2 , Figure 2A schematic flow chart of a cloud host fault handling method provided by an embodiment of the present disclosure, wherein migrating the host system according to the priority order of the fault handling methods in the fault handling chain includes:
[0065] Step 201: Determine a first fault handling method to migrate a virtual machine in the host system according to the priority order of the fault handling methods in the fault handling chain.
[0066] In some embodiments, there is a priority order for the fault handling methods in the fault handling chain, and when determining the first fault handling method, it is determined according to the priority order.
[0067] Assume that there is a processing chain of A->B->C (such as hot migration->cold migration->evacuation), and there are a total of 30 virtual machines that need to be processed. After processing method A is executed, 10 virtual machines are successfully restored, and the remaining virtual machines either fail to be restored or cannot support this recovery method due to the type of virtual machine; after processing method B is executed, another 10 virtual machines are restored; and the last 10 virtual machines are completed by processing method C. Relying on this layer-by-layer filtering processing, each virtual machine can be processed as much as possible. When all processing methods are executed and there are still failed virtual machines, an alarm needs to be notified for manual intervention.
[0068] Please refer to Table 1, which is a task division table provided in an embodiment of the present application, as shown in Table 1;
[0069] Table 1
[0070]
[0071]
[0072] In actual operation, the priority order of fault handling methods can be flexibly adjusted according to the specific situation of the host system and the design of the fault handling chain, and the virtual machines in the host system can be migrated in time to minimize the impact of the fault on the system and ensure the normal operation of the host system.
[0073] Step 202: Acquire a virtual machine that has failed to migrate, and determine a second fault handling method to migrate the virtual machine that has failed to migrate according to the priority order of the fault handling methods in the fault handling chain.
[0074] After obtaining the virtual machine that failed to migrate, determine the second fault handling method to migrate the virtual machine that failed to migrate according to the priority order of the fault handling methods in the fault handling chain. : According to the priority order in the fault handling chain, for example, the second fault handling method may be manual failover. In this case, the virtual machine that failed to migrate needs to be manually migrated to other normal nodes or servers.
[0075] Step 203, repeating the host system migration step until the migration of the virtual machines in the host system is completed, or the fault handling method in the fault handling chain is determined.
[0076] Repeat the above steps until all virtual machines are migrated or the fault handling method is determined. If all virtual machines are successfully migrated, the entire migration process is completed;
[0077] See also Figure 3 , Figure 3 A flowchart of a cloud host fault handling method provided by an embodiment of the present disclosure includes:
[0078] Step 301 , analyzing the fault condition of the host system and determining at least two fault handling methods; wherein the fault handling methods corresponding to different fault conditions have different priority orders.
[0079] In some embodiments, network failures and storage failures may have different degrees of impact on the host system, so the priority order of their fault handling methods is also different. The administrator should determine the priority order of the fault handling methods corresponding to different fault situations based on the specific situation and system requirements, and take corresponding measures in a timely manner to restore the normal operation of the system.
[0080] Step 302: Generate a fault handling chain according to the priority order of the fault handling modes.
[0081] The fault handling methods are sorted according to their priority order to generate a fault handling chain. The arrangement order of the fault handling methods represents the priority order of the faults.
[0082] In some embodiments, before obtaining a virtual machine that failed to migrate, and determining a second fault handling method to migrate the virtual machine that failed to migrate according to the priority order of the fault handling methods in the fault handling chain, the method further includes: performing rollback or cleanup on the virtual machine that failed to migrate. The migration step includes a pre-operation, a main operation, and a post-operation. When performing rollback or cleanup on the virtual machine that failed to migrate, the specific steps include:
[0083] When the migration failure step is a pre-operation, rolling back or clearing the pre-operation of the virtual machine that failed to migrate; or
[0084] When the migration failure step is the main operation, roll back or clean up the pre-operation and the main operation of the virtual machine that failed to migrate; or
[0085] When the migration failure step is a post-operation, the pre-operation, main operation and post-operation of the virtual machine that failed to migrate are rolled back or cleared.
[0086] See also Figure 4 , Figure 4 A schematic diagram of a return operation provided in an embodiment of the present application is shown in FIG. Figure 4 As shown, Figure 4 If the migration failure step is a post-operation, the post-operation, main operation and pre-operation will be rolled back in reverse order, so that the subsequent task flow can proceed normally when the execution is successful, and it will automatically roll back to the state before the execution when the execution fails. This feature can flexibly realize the reasonable combination of processing tasks and meet the coverage requirements of multiple fault scenarios.
[0087] In order to pass shared variables in multiple processing chains, we can use the existing variable passing features of any task flow package. For example, the store parameter is used to pass information that can be obtained before all tasks are run; the provides parameter is used to pass information generated after a task is executed; and the requires parameter is used to indicate the information that a task depends on when it is executed.
[0088] Corresponding to the above-mentioned cloud host fault handling method, the present invention also provides a cloud host fault handling device. Since the device embodiment of the present invention corresponds to the above-mentioned method embodiment, the details not disclosed in the device embodiment can be referred to the above-mentioned method embodiment, and will not be repeated in the present invention.
[0089] Figure 5 A schematic diagram of a cloud host fault handling device provided by an embodiment of the present disclosure is shown in FIG. Figure 5 As shown, including:
[0090] The determination unit 41 is used to determine a fault handling chain according to the fault situation after confirming that the host system has a fault; wherein the fault handling chain includes at least two fault handling methods;
[0091] The migration unit 42 is used to migrate the host system according to the priority order of the fault processing methods in the fault processing chain; wherein the host system includes at least one virtual machine.
[0092] The cloud host fault handling device provided by the present disclosure has the following main technical solutions: after confirming that the host system has a fault, determining a fault handling chain according to the fault situation; wherein the fault handling chain includes at least two fault handling methods; migrating the host system according to the priority order of the fault handling methods in the fault handling chain; wherein the host system includes at least one virtual machine. Compared with the related art, the embodiment of the present application determines a fault handling chain by analyzing the fault situation, processes the host system according to the fault handling chain, and sends the virtual machine that failed to be processed by the previous fault handling method to the next fault handling method for processing, thereby avoiding the situation where the subsequent virtual machines cannot be processed due to the virtual machine being stuck, improving the success rate of fault handling, and reducing labor costs.
[0093] Furthermore, in a possible implementation of the embodiment of the present disclosure, as Figure 6 As shown, the migration unit 42 includes:
[0094] A first migration module 421, configured to determine a first fault handling method to migrate the virtual machines in the host system according to the priority order of the fault handling methods in the fault handling chain;
[0095] The second migration module 422 is used to obtain the virtual machine that failed to migrate, and determine the second fault handling method to migrate the virtual machine that failed to migrate according to the priority order of the fault handling methods in the fault handling chain;
[0096] The third migration module 423 is used to repeat the steps of host system migration until the migration of the virtual machines in the host system is completed, or the fault handling method in the fault handling chain is determined.
[0097] Furthermore, in a possible implementation of the embodiment of the present disclosure, as Figure 6 As shown, the device also includes:
[0098] The rollback unit 43 is used to obtain the virtual machine that failed to migrate in the second migration module 422, and determine the second fault handling method to perform rollback or cleanup on the virtual machine that failed to migrate before migrating the virtual machine that failed to migrate according to the priority order of the fault handling methods in the fault handling chain.
[0099] Furthermore, in a possible implementation of the embodiment of the present disclosure, as Figure 6 As shown, the determining unit 41 further includes:
[0100] The determination module 411 is used to analyze the fault condition of the host system and determine at least two fault handling methods; wherein the fault handling methods corresponding to different fault conditions have different priority orders;
[0101] The generating module 412 is used to generate a fault processing chain according to the priority order between the fault processing modes.
[0102] Furthermore, in a possible implementation of the embodiment of the present disclosure, as Figure 6 As shown, the migration step includes a pre-operation, a main operation and a post-operation, and the rollback unit 43 also includes
[0103] A first rollback module 431 is configured to roll back or clear the preceding operation of the virtual machine that failed to migrate when the migration failure step is a preceding operation; or
[0104] A second rollback module 432 is used to roll back or clean up the pre-operation and main operation of the virtual machine that failed to migrate when the migration failed step is the main operation; or
[0105] The third rollback module 433 is used to roll back or clear the pre-operation, main operation and post-operation of the virtual machine that failed to migrate when the migration failure step is a post-operation.
[0106] It should be noted that the above explanation of the method embodiment is also applicable to the device of the embodiment of the present disclosure, and the principle is the same, which is no longer limited in the embodiment of the present disclosure.
[0107] According to an embodiment of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium and a computer program product.
[0108] Figure 7 A schematic block diagram of an example electronic device 500 that can be used to implement an embodiment of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present disclosure described and / or required herein.
[0109] like Figure 7As shown, the device 500 includes a computing unit 501, which can perform various appropriate actions and processes according to a computer program stored in a ROM (Read-Only Memory) 502 or a computer program loaded from a storage unit 508 to a RAM (Random Access Memory) 503. In the RAM 503, various programs and data required for the operation of the device 500 can also be stored. The computing unit 501, the ROM 502, and the RAM 503 are connected to each other via a bus 504. An I / O (Input / Output) interface 505 is also connected to the bus 504.
[0110] A number of components in the device 500 are connected to the I / O interface 505, including: an input unit 506, such as a keyboard, a mouse, etc.; an output unit 507, such as various types of displays, speakers, etc.; a storage unit 508, such as a disk, an optical disk, etc.; and a communication unit 509, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 509 allows the device 500 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.
[0111] The computing unit 501 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 501 include, but are not limited to, a CPU (Central Processing Unit), a GPU (Graphic Processing Units), various dedicated AI (Artificial Intelligence) computing chips, various computing units running machine learning model algorithms, a DSP (Digital Signal Processor), and any appropriate processor, controller, microcontroller, etc. The computing unit 501 performs the various methods and processes described above, such as a fault handling method for a cloud host. For example, in some embodiments, the fault handling method for a cloud host may be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as a storage unit 508. In some embodiments, part or all of the computer program may be loaded and / or installed on the device 500 via the ROM 502 and / or the communication unit 509. When the computer program is loaded into the RAM 503 and executed by the computing unit 501, one or more steps of the method described above may be performed. Alternatively, in other embodiments, the computing unit 501 may be configured to execute the aforementioned cloud host fault handling method in any other appropriate manner (eg, by means of firmware).
[0112] Various embodiments of the systems and techniques described above herein may be implemented in digital electronic circuit systems, integrated circuit systems, FPGAs (Field Programmable Gate Arrays), ASICs (Application-Specific Integrated Circuits), ASSPs (Application Specific Standard Products), SOCs (System On Chips), CPLDs (Complex Programmable Logic Devices), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include: being implemented in one or more computer programs that may be executed and / or interpreted on a programmable system including at least one programmable processor that may be a dedicated or general-purpose programmable processor that may receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.
[0113] The program code for implementing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.
[0114] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any suitable combination of the foregoing. More specific examples of machine-readable storage media may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a RAM, a ROM, an EPROM (Electrically Programmable Read-Only-Memory) or a flash memory, an optical fiber, a CD-ROM (Compact Dis sc Read-Only Memory), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0115] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (Cathode-Ray Tube) or LCD (Liquid Crystal Display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).
[0116] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: LAN (Local Area Network), WAN (Wide Area Network), the Internet, and blockchain networks.
[0117] A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship between the client and the server is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services ("Virtual Private Server", or "VPS" for short). The server may also be a server of a distributed system, or a server combined with a blockchain.
[0118] It should be noted that artificial intelligence is a discipline that studies how computers can simulate certain human thought processes and intelligent behaviors (such as learning, reasoning, thinking, planning, etc.), and includes both hardware-level and software-level technologies. Artificial intelligence hardware technologies generally include technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, and big data processing; artificial intelligence software technologies mainly include computer vision technology, speech recognition technology, natural language processing technology, as well as machine learning / deep learning, big data processing technology, knowledge graph technology, and other major directions.
[0119] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this disclosure can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved, and this document does not limit this.
[0120] The above specific implementations do not constitute a limitation on the protection scope of the present disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present disclosure shall be included in the protection scope of the present disclosure.
Claims
1. A method for troubleshooting a cloud host, characterized in that: include: After confirming that the host system has a fault, determine a fault handling chain according to the fault situation; wherein the fault handling chain includes at least two fault handling methods; The virtual machines in the host system are migrated according to the priority order of the fault handling methods in the fault handling chain; wherein the host system includes at least one virtual machine.
2. The method according to claim 1, characterized in that: The migrating the virtual machines in the host system according to the priority order of the fault handling methods in the fault handling chain includes: Determine, according to the priority order of the fault handling methods of the fault handling chain, a first fault handling method to migrate the virtual machines in the host system; Acquire a virtual machine that fails to migrate, and determine a second fault handling method to migrate the virtual machine that fails to migrate according to the priority order of the fault handling methods in the fault handling chain; The host system migration step is repeated until the migration of the virtual machines in the host system is completed, or the fault handling method in the fault handling chain is determined.
3. The method according to claim 2, characterized in that Before obtaining the virtual machine that failed to migrate, and determining the second fault handling method to migrate the virtual machine that failed to migrate according to the priority order of the fault handling methods in the fault handling chain, the method further includes: Rollback or cleanup is performed on the virtual machine whose migration fails.
4. The method according to claim 1, characterized in that: After confirming that the host system has a fault, determining the fault handling chain according to the fault condition includes: Analyze the fault condition of the host system and determine at least two fault handling methods; wherein the fault handling methods corresponding to different fault conditions have different priority orders; A fault handling chain is generated according to the priority order between the fault handling modes.
5. The method according to claim 3, characterized in that: The migration step includes a pre-operation, a main operation and a post-operation, and the rollback or cleanup of the virtual machine that failed to migrate includes: When the migration failure step is a pre-operation, rolling back or clearing the pre-operation of the virtual machine that failed to migrate; or When the migration failure step is the main operation, roll back or clean up the pre-operation and the main operation of the virtual machine that failed to migrate; or When the migration failure step is a post-operation, the pre-operation, main operation and post-operation of the virtual machine that failed to migrate are rolled back or cleared.
6. A cloud host fault handling device, characterized in that: include: A determination unit, configured to determine a fault handling chain according to the fault condition after confirming that the host system has a fault; wherein the fault handling chain includes at least two fault handling methods; A migration unit is used to migrate virtual machines in the host system according to the priority order of the fault processing methods in the fault processing chain; wherein the host system includes at least one virtual machine.
7. The device according to claim 6, characterized in that The migration unit comprises: A first migration module, configured to determine a first fault handling method to migrate the virtual machines in the host system according to the priority order of the fault handling methods in the fault handling chain; A second migration module is used to obtain a virtual machine that has failed to migrate, and determine a second fault handling method to migrate the virtual machine that has failed to migrate according to the priority order of the fault handling methods in the fault handling chain; The third migration module is used to repeat the steps of host system migration until the migration of the virtual machines in the host system is completed, or the fault handling method in the fault handling chain is determined.
8. An electronic device, characterized in that: include: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 5.
9. A non-transitory computer-readable storage medium storing computer instructions, characterized in that: The computer instructions are used to cause the computer to execute the method according to any one of claims 1-5.
10. A computer program product, characterized in that The invention comprises a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 5.
