System cloud disk data processing method and device, electronic equipment and storage medium

Abstract

The invention provides a system cloud disk data processing method and device, electronic equipment and a storage medium, and the method comprises the steps: unloading a target system cloud disk from a current host under the condition that a system of the target system cloud disk in the current host has a preset processing demand; mounting the target system cloud disk on a normal host in the form of a data disk; after the normal host processes the system of the target system cloud disk and a processed system cloud disk is obtained, unloading the processed system cloud disk from the normal host; and mounting the processed system cloud disk on the current host in the form of a system disk. Through the method and the device, the problem that personalized data is lost when a system cloud disk processes a system in the prior art is solved.

Description

Technical Field

[0001] The present application relates to the field of distributed cloud storage technology, and in particular to a system cloud disk data processing method and device, electronic equipment and storage medium. Background Art

[0002] As distributed cloud storage is increasingly used, a large number of host system disks use cloud disks in distributed cloud storage clusters. When a cloud disk needs to be replaced, the data in the cloud disk needs to be migrated to the new cloud disk. In addition, at the host level, user system file corruption often occurs. System file corruption can cause the cloud host to fail to start, which can seriously affect the user experience.

[0003] In order to repair or migrate system data, the existing technical solution adopts the method of performing system reinstallation on the problematic cloud host (the cloud host with system data repair or migration requirements), but after reinstallation, only the operating system can be restored and personalized data will be lost.

[0004] It can be seen that the system cloud disk in the related technology has a technical problem of losing personalized data when processing the system. Summary of the invention

[0005] The present application provides a system cloud disk data processing method and device, an electronic device and a storage medium, so as to at least solve the problem of personalized data loss when the system cloud disk processes the system in the related art.

[0006] According to one aspect of an embodiment of the present application, a system cloud disk data processing method is provided, including:

[0007] If the target system cloud disk in the current host has a preset processing requirement, uninstall the target system cloud disk from the current host;

[0008] Mount the target system cloud disk on a normal host in the form of a data disk;

[0009] After the normal host processes the system of the target system cloud disk and obtains a processed system cloud disk, uninstalling the processed system cloud disk from the normal host;

[0010] The processed system cloud disk is mounted on the current host in the form of a system disk.

[0011] Optionally, as in the aforementioned method, when the system of the target system cloud disk in the current host has a preset processing requirement, uninstalling the target system cloud disk from the current host includes:

[0012] When the target system cloud disk in the current host has a preset processing requirement, shutting down the current host;

[0013] Call a preset interface to uninstall the target system cloud disk from the current host.

[0014] Optionally, as in the aforementioned method, calling a preset interface to uninstall the target system cloud disk from the current host includes:

[0015] Updating the current task status of the current host to system disk unloading;

[0016] Send a system disk uninstallation startup message to the cloud platform;

[0017] Unmounting the mount record of the target system cloud disk in the current host;

[0018] Calling the preset interface to uninstall the target system cloud disk from the current host;

[0019] In the case where it is determined that the target system cloud disk has been uninstalled in the current host, the current instance on the current host is marked as having no system cloud disk, and the current task state is set to blank to indicate that there is no task to uninstall the system cloud disk in the current host;

[0020] Send a system disk uninstallation completion message to the cloud platform.

[0021] Optionally, as in the aforementioned method, the processing of the target system cloud disk on the normal host and obtaining the processed system cloud disk includes:

[0022] When the preset processing requirement is to repair the system of the target system cloud disk, the system of the target system cloud disk is repaired on the normal host, and a processed system cloud disk is obtained;

[0023] When the preset processing requirement is to migrate the system of the target system cloud disk, the system of the target system cloud disk is migrated to the designated cloud disk on the normal host, and a processed system cloud disk is obtained after the designated cloud disk is migrated into the system.

[0024] Optionally, as in the aforementioned method, mounting the processed system cloud disk on the current host in the form of a system disk includes:

[0025] When it is determined that the current host meets the preset mounting requirements, obtaining the target drive letter of the processed system cloud disk;

[0026] According to the target drive letter, the processed system cloud disk is mounted to the current host.

[0027] Optionally, in the aforementioned method, the preset mounting requirement includes at least one of the following:

[0028] The drive letter of the processed system cloud disk is not obtained;

[0029] The current instance on the current host is in shutdown state;

[0030] The current task status of the current host is that the system disk is not mounted;

[0031] After the processing, the system cloud disk is a bootable disk.

[0032] Optionally, as in the aforementioned method, mounting the processed system cloud disk to the current host according to the target drive letter includes:

[0033] When it is determined that the processed system cloud disk requested to be mounted on the current host is a system disk, directly determining the drive letter assigned to the processed system cloud disk as a default drive letter;

[0034] Updating the current task status of the current host to system disk mounting;

[0035] Send system disk mount startup message to the cloud platform;

[0036] Calling the preset interface, and mounting the processed system cloud disk in the current host according to the target drive letter;

[0037] In the case where it is determined that the processed system cloud disk has been mounted in the current host, the current instance on the current host is identified as having the system cloud disk mounted, and the current task state is set to blank to indicate that there is no task for mounting the system cloud disk in the current host;

[0038] Adding a mounting record of mounting the processed system cloud disk in the current host and a mapping relationship between the processed system cloud disk and the current instance;

[0039] Send a system disk mounting completion message to the cloud platform.

[0040] According to another aspect of the embodiment of the present application, a system cloud disk data processing device is also provided, including:

[0041] An uninstallation module, used for uninstalling the target system cloud disk from the current host when there is a preset processing requirement for the system of the target system cloud disk in the current host;

[0042] A first mounting module, used to mount the target system cloud disk to a normal host in the form of a data disk;

[0043] a processing module, configured to, after the normal host processes the system of the target system cloud disk and obtains a processed system cloud disk, uninstall the processed system cloud disk from the normal host;

[0044] The second mounting module is used to mount the processed system cloud disk on the current host in the form of a system disk.

[0045] According to another aspect of the embodiments of the present application, there is also provided an electronic device, including a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; wherein the memory is used to store a computer program; and the processor is used to execute the method steps in any of the above embodiments by running the computer program stored in the memory.

[0046] According to another aspect of the embodiments of the present application, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the method steps in any of the above embodiments when executed.

[0047] In an embodiment of the present application, when a system cloud disk in a host has a preset processing requirement, the system cloud disk is processed by another host. When a system of the target system cloud disk in the current host has a preset processing requirement, the target system cloud disk is unloaded from the current host; the target system cloud disk is mounted on a normal host in the form of a data disk; after the normal host processes the system of the target system cloud disk and obtains the processed system cloud disk, the processed system cloud disk is unloaded from the normal host; and the processed system cloud disk is mounted on the current host as a system disk. Since the target system cloud disk in the current host is mounted on the normal host in the form of a data disk, the normal host can process the system data of the target system cloud disk and obtain the processed system cloud disk. After the processed system cloud disk is mounted back on the current host, the processing is completed, and the purpose of not having to reinstall the system of the target system cloud disk is achieved. The personalized data in the target system cloud disk will not be lost, and the technical effect of processing the system cloud disk and retaining the personalized data is achieved, thereby solving the problem of personalized data loss when the system cloud disk processes the system in the related technology. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0049] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0050] Figure 1 is a schematic diagram of a hardware environment of an optional system cloud disk data processing method according to an embodiment of the present application;

[0051] Figure 2 It is a flowchart of an optional system cloud disk data processing method according to an embodiment of the present application;

[0052] Figure 3 is a schematic diagram of an optional system cloud disk data processing method according to another embodiment of the present application;

[0053] Figure 4 It is a schematic diagram of a process of uninstalling a system cloud disk in an optional system cloud disk data processing method according to an embodiment of the present application;

[0054] Figure 5 is a schematic diagram of an optional system cloud disk data processing method according to another embodiment of the present application;

[0055] Figure 6 It is a schematic diagram of a process of mounting a system cloud disk in an optional system cloud disk data processing method according to an embodiment of the present application;

[0056] Figure 7 It is a structural block diagram of an optional system cloud disk data processing device according to an embodiment of the present application;

[0057] Figure 8 It is a structural block diagram of an optional electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0058] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0059] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0060] According to one aspect of an embodiment of the present application, a system cloud disk data processing method is provided. Optionally, in this embodiment, the system cloud disk data processing method can be applied to Figure 1 In the hardware environment composed of terminal 1402 and server 1404 shown in FIG. Figure 1 As shown, server 1404 is connected to terminal 1402 via a network, and can be used to provide services (such as game services, application services, etc.) for the terminal or a client installed on the terminal. A database can be set up on the server or independently of the server to provide data storage services for server 1404.

[0061] The above network may include but is not limited to at least one of the following: wired network, wireless network. The above wired network may include but is not limited to at least one of the following: wide area network, metropolitan area network, local area network, and the above wireless network may include but is not limited to at least one of the following: WIFI (Wireless Fidelity), Bluetooth. The terminal may not be limited to a PC, a mobile phone, a tablet computer, etc.

[0062] The system cloud disk data processing method of the embodiment of the present application can be executed by a server, or by a terminal, or by both a server and a terminal. The terminal can also execute the system cloud disk data processing method of the embodiment of the present application by a client installed thereon.

[0063] Taking the system cloud disk data processing method in this embodiment executed by the server as an example, Figure 2 A method for processing system cloud disk data provided in an embodiment of the present application includes the following steps:

[0064] Step S202, when the system of the target system cloud disk in the current host has a preset processing requirement, the target system cloud disk is uninstalled from the current host.

[0065] The system cloud disk data processing method in this embodiment can be applied to scenarios where system cloud disks in a distributed cloud storage cluster need to be processed, such as: repairing system data in a system cloud disk where system damage occurs, migrating the system cloud disk, etc. It can also be other scenarios where system cloud disks in a distributed cloud storage cluster need to be processed.

[0066] Specifically, the target system cloud disk is a cloud disk located in the current host and used as a system disk. When the system of the target system cloud disk has a preset processing requirement, in this embodiment, the target system cloud disk is uninstalled from the current host. Uninstallation in this embodiment refers to disconnecting the connection between the target system cloud disk and the current host, for example, disconnecting the network connection between the two.

[0067] The preset processing requirements may include but are not limited to: repairing the system in case of system damage; migrating the system of the target system cloud disk to other cloud disks, etc.

[0068] Furthermore, after the target system cloud disk is uninstalled, the current host is in a "no system disk" state. In this case, the current host is prohibited from all operations except deletion and evacuation (evacuation is not allowed to be pulled up), where evacuation means that after the host machine (i.e., the current host in this embodiment) crashes, the virtual machine on the crashed host machine is migrated to other normal host machines.

[0069] Step S204, mounting the target system cloud disk on a normal host in the form of a data disk.

[0070] Specifically, the normal host in this embodiment is a host that can process data for the system, and the data processing method corresponds to the aforementioned preset processing requirements. For example, when the system is damaged, the normal host has data that can be used to repair the system; when the system of the target system cloud disk needs to be migrated to other cloud disks, the normal host can be used to migrate data on different cloud disks.

[0071] After the target system cloud disk is uninstalled from the current host, in order to process the system in the target system cloud disk, the target system cloud disk can be displayed to the outside in the format of a "data disk" and mounted on a normal host as a data disk.

[0072] Step S206, after the normal host processes the system of the target system cloud disk and obtains the processed system cloud disk, the processed system cloud disk is uninstalled from the normal host.

[0073] Specifically, after the target system cloud disk is mounted on the normal host, the normal host can see the data in the target system cloud disk, and then the normal host can process the system of the target system cloud disk and obtain the processed system cloud disk. And after obtaining the processed system cloud disk, it is necessary to mount the processed system cloud disk to the current host, and then it is necessary to uninstall the processed system cloud disk from the normal host.

[0074] As an optional implementation, the following steps can be used to implement processing of the target system cloud disk system on a normal host, and obtain the processed system cloud disk, including: when the preset processing requirement is to repair the target system cloud disk system, the target system cloud disk system is repaired on the normal host, and the processed system cloud disk is obtained; when the preset processing requirement is to migrate the target system cloud disk system, the target system cloud disk system is migrated to a designated cloud disk on the normal host, and the processed system cloud disk is obtained after the designated cloud disk is migrated into the system.

[0075] Step S208, mounting the processed system cloud disk on the current host in the form of a system disk.

[0076] Specifically, after the processed system cloud disk is uninstalled from the normal host, the processed system cloud disk is allowed to be mounted as a "system disk" on the cloud disk host in the "no system disk" state, and then the processed system cloud disk can be mounted on the current host in the form of a system disk; after completing the mounting operation, the host returns to normal state (that is, "with system disk" state), and the "processed system cloud disk" is displayed to the outside in the format of a "system disk".

[0077] In an embodiment of the present application, when a system cloud disk in a host has a preset processing requirement, the system cloud disk is processed by another host. Since the target system cloud disk in the current host is mounted on the normal host in the form of a data disk, the normal host can process the system data of the target system cloud disk and obtain the processed system cloud disk. After mounting the processed system cloud disk back to the current host, the processing is completed, and the purpose of not having to reinstall the system of the target system cloud disk is achieved. Furthermore, the personalized data in the target system cloud disk will not be lost, and the technical effect of processing the system cloud disk and retaining the personalized data is achieved, thereby solving the problem of personalized data loss when the system cloud disk is processed in the related art.

[0078] like Figure 3 As shown, as an optional implementation, as in the aforementioned method, the step S202 uninstalls the target system cloud disk from the current host when the system of the target system cloud disk in the current host has a preset processing requirement, including the following steps:

[0079] Step S302: When the system of the target system cloud disk in the current host has a preset processing requirement, the current host is shut down.

[0080] That is to say, when it is determined that the system of the target system cloud disk has preset processing requirements, the current host is shut down.

[0081] Step S304, calling a preset interface to uninstall the target system cloud disk from the current host.

[0082] After shutting down the current host, the target system cloud disk in the current host is uninstalled through a preset interface. Optionally, the target system cloud disk can be uninstalled by calling Libvirt (a life cycle virtualization interface for processing cloud hosts).

[0083] In this embodiment, the target system cloud disk is uninstalled after the current host is shut down, thereby avoiding unexpected situations such as accidental loss or error of data in the target system cloud disk and improving data integrity.

[0084] As an optional implementation, as in the aforementioned method, the aforementioned step S304 can be implemented by calling the preset interface to uninstall the target system cloud disk from the current host through the following steps: updating the current task status of the current host to the system disk being uninstalled; sending a system disk uninstallation start message to the cloud platform; canceling the mount record of the target system cloud disk mounted in the current host; calling the preset interface to uninstall the target system cloud disk from the current host; when it is determined that the target system cloud disk has been uninstalled in the current host, marking the current instance on the current host as a non-existent system cloud disk, and setting the current task status to blank to indicate that there is no task to uninstall the system cloud disk in the current host; sending a system disk uninstallation completion message to the cloud platform. Specifically, as Figure 4As shown, when it is necessary to uninstall the target system cloud disk in the current host, the request to uninstall the target system cloud disk can be verified, and the verification content may include: whether the current host is turned off. If the verification passes, that is, the current host is turned off, the status of the current task of the current host can be updated to the system disk uninstallation. For example, the task state (that is, the status of the current task) can be updated to "detaching_sys_disk" through the API (for the computing service API entry service), and then the uninstallation request is sent to the current host (that is, DHost). After obtaining the uninstallation request, the current host can send a "detach_volume.start" message to the cloud platform to send a system disk uninstallation start message to the cloud platform, and cancel the mount record of the target system cloud disk in the current host by canceling the mount record recorded by Cinder (the cloud platform service responsible for the life cycle of the cloud hard disk). Then call Libvirt to uninstall the target system cloud disk in the current host. When it is detected that the cloud disk to be uninstalled is a system disk, the current instance on the current host is marked as having no system cloud disk by updating vm state to "without_sys_disk", and the current task state is cleared by clearing taskstate (for example, restoring task state to None) to indicate that there is no task to uninstall the system cloud disk in the current host. Finally, a "detach_volume.end" message is sent to the cloud platform to send a system disk uninstallation completion message to the cloud platform.

[0085] Furthermore, the method may further include: when an abnormality occurs in the uninstallation operation of the target system cloud disk from the current host, setting the current task state to blank. That is, the current host may restore the task state to None.

[0086] like Figure 5 As shown, as an optional implementation, as in the above method, the processed system cloud disk can be mounted on the current host in the form of a system disk through the following steps:

[0087] Step S502, when it is determined that the current host meets the preset mounting requirements, the target drive letter of the processed system cloud disk is obtained.

[0088] That is to say, before mounting the processed system cloud disk to the current host, it is necessary to determine whether the current host meets the preset mounting requirements. Only when it meets the preset mounting requirements, the target drive letter of the processed system cloud disk is obtained.

[0089] As an optional implementation, Figure 6As shown, as in the aforementioned method, the preset mounting requirements include at least one of the following: the drive letter of the processed system cloud disk is not obtained; the current instance on the current host is in a shutdown state; the current task state of the current host is that the system disk is not mounted, for example, the task state of the current host is "without_sys_disk"; the processed system cloud disk is a bootable disk. The above preset mounting requirements can be judged by the aforementioned API, and the mounting of the system disk can be represented by the newly added parameter bootable. The API can verify that the current instance on the current host is in a shutdown state through the following steps: check whether the current instance is in a shutdown state, and report an error if it is not; whether the task state of the host is "without_system_disk"; if not, report an error. The API can verify whether the current task state of the current host is mounted with the system disk through the following steps: check whether the current instance has mounted the system disk, and report an error if not. The API verifies that the processed system cloud disk is a bootable disk through the following steps: whether bootable is True in Volume Metadata (i.e., the metadata of the volume), where the "bootable" attribute is used to indicate whether the volume can be used as a boot disk (Boot Disk), and an error is reported if it is not True. The API can verify whether the drive letter of the processed system cloud disk is obtained through the following steps: whether the device (i.e., drive letter) is specified, and an error is reported after checking the device configuration (the drive letter allocation logic is uniformly handed over to the compute, which can be compatible with the drive letter prefix). The API can also execute the following logic: If bootable is True, delete_on_terminate is True, which means that the processed system cloud disk is judged to be a bootable root device volume (Boot Disk), and when the associated instance or virtual machine is terminated, the processed system cloud disk will be automatically deleted.

[0090] Step S504: mount the processed system cloud disk to the current host according to the target drive letter.

[0091] After obtaining the target drive letter, it can be determined that the processed system cloud disk can be mounted in the current host, and the processed system cloud disk can be mounted to the current host according to the target drive letter. For example, when the target drive letter is A, the system cloud disk is displayed as drive A after being mounted to the current host.

[0092] By directly determining the target drive letter, the time consumed in determining the drive letter can be effectively reduced, thereby improving the efficiency of mounting.

[0093] As an optional implementation, as in the aforementioned method, step S404 can be implemented by the following steps to mount the processed system cloud disk to the current host according to the target drive letter: when it is determined that the processed system cloud disk requested to be mounted on the current host is a system disk, directly determine the drive letter assigned to the processed system cloud disk as the default drive letter; update the current task status of the current host to be system disk mounting; send a system disk mounting start message to the cloud platform; call the preset interface to mount the processed system cloud disk in the current host according to the target drive letter; when it is determined that the processed system cloud disk has been mounted in the current host, mark the current instance on the current host as a mounted system cloud disk, and set the current task status to blank to indicate that there is no task to mount the system cloud disk in the current host; add a mounting record of mounting the processed system cloud disk in the current host and the mapping relationship between the processed system cloud disk and the current instance; send a system disk mounting completion message to the cloud platform. Specifically, as Figure 6 As shown, when the current host perceives that the processed system cloud disk requested to be mounted on the current host is a system disk (for example, bootable is True), the drive letter verification process skips the non-cloud disk drive letter and directly returns the default drive letter, such as a. When the API perceives the operation of mounting a system disk (for example, bootable is True), it can update the current task state of the current host to the system disk mounting by setting the host task state state to "attaching_system_disk", and send a cloud disk mounting request to the current host. After receiving the cloud disk mounting request, the current host can send a system disk mounting start message to the cloud platform by sending an "attach_volume.start" message. Call the preset interface (for example, libirt) to mount the processed system cloud disk in the current host according to the target drive letter. When the system disk mounting operation is sensed (for example, bootable is True), the normal state of the current instance (for example, vmstate) is set according to the host operation state, and when the host operation state indicates that the processed system cloud disk has been mounted in the current host, the current instance on the current host is identified as the mounted system cloud disk, that is, the normal state is identified as the mounted system cloud disk, and the current task state is set to blank to indicate that there is no task to mount the system cloud disk in the current host; by adding the mounting record recorded by Cinder, the mounting record of the processed system cloud disk mounted in the current host is added, and by adding the cloud disk instance mapping relationship recorded by Nova (that is, the mapping relationship between the processed system cloud disk and the current instance), the mapping relationship between the processed system cloud disk and the current instance is added. The system disk mounting completion message is sent to the cloud platform by sending the "attach_volume.end" message to the cloud platform.

[0094] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

[0095] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM (Read-Only Memory) / RAM (Random Access Memory), a disk, or an optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0096] According to another aspect of an embodiment of the present application, a system cloud disk data processing device for implementing the above-mentioned system cloud disk data processing device method is also provided. Figure 7 is a structural block diagram of an optional system cloud disk data processing device according to an embodiment of the present application, such as Figure 7 As shown, the device may include:

[0097] The unloading module 71 is used to unload the target system cloud disk from the current host when there is a preset processing requirement for the system of the target system cloud disk in the current host;

[0098] The first mounting module 72 is used to mount the target system cloud disk to a normal host in the form of a data disk;

[0099] The processing module 73 is used to process the system of the target system cloud disk on the normal host and, after obtaining the processed system cloud disk, uninstall the processed system cloud disk from the normal host;

[0100] The second mounting module 74 is used to mount the processed system cloud disk to the current host in the form of a system disk.

[0101] It should be noted that the unloading module 71 in this embodiment can be used to execute the above step S202, the first mounting module 72 in this embodiment can be used to execute the above step S204, the processing module 73 in this embodiment can be used to execute the above step S206, and the second mounting module 74 in this embodiment can be used to execute the above step S208.

[0102] The device in this embodiment, in addition to the above-mentioned modules, may also include a module for executing any method in any of the above-mentioned embodiments of the system cloud disk data processing method.

[0103] It should be noted that the examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the contents disclosed in the above embodiments. It should be noted that the above modules as part of the device can be run in Figure 1 In the hardware environment shown, it can be implemented by software or by hardware, wherein the hardware environment includes a network environment.

[0104] According to another aspect of an embodiment of the present application, an electronic device for implementing the above-mentioned system cloud disk data processing method is also provided. The electronic device may be a server, a terminal, or a combination thereof.

[0105] According to another embodiment of the present application, there is also provided an electronic device, including: Figure 8 As shown, the electronic device may include: a processor 1501 , a communication interface 1502 , a memory 1503 and a communication bus 1504 , wherein the processor 1501 , the communication interface 1502 , and the memory 1503 communicate with each other via the communication bus 1504 .

[0106] Memory 1503, used for storing computer programs;

[0107] The processor 1501 is used to implement the following steps when executing the program stored in the memory 1503:

[0108] Step S202, when the system of the target system cloud disk in the current host has a preset processing requirement, the target system cloud disk is uninstalled from the current host.

[0109] Step S204, mounting the target system cloud disk on a normal host in the form of a data disk.

[0110] Step S206, after the normal host processes the system of the target system cloud disk and obtains the processed system cloud disk, the processed system cloud disk is uninstalled from the normal host.

[0111] Step S208, mounting the processed system cloud disk on the current host in the form of a system disk.

[0112] Optionally, in this embodiment, the above-mentioned communication bus can be a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus. The communication interface is used for communication between the above-mentioned electronic device and other devices.

[0113] The memory may include a random access memory (RAM) or a non-volatile memory (NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0114] As an example, the memory 1503 may include, but is not limited to, the unloading module 71, the first mounting module 72, the processing module 73, and the second mounting module 74 in the system cloud disk data processing device. In addition, it may also include, but is not limited to, other module units in the system cloud disk data processing device, which will not be repeated in this example.

[0115] The above-mentioned processor can be a general-purpose processor, which can include but not be limited to: CPU (Central Processing Unit), NP (Network Processor), etc.; it can also be DSP (Digital Signal Processor), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0116] An embodiment of the present application further provides a computer-readable storage medium, the storage medium including a stored program, wherein the method steps of the above method embodiment are executed when the program is run.

[0117] Optionally, in this embodiment, the storage medium may include, but is not limited to, various media that can store program codes, such as a USB flash drive, a ROM, a RAM, a mobile hard disk, a magnetic disk, or an optical disk.

[0118] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0119] If the integrated units in the above embodiments are implemented in the form of software functional units and sold or used as independent products, they can be stored in the above computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling one or more computer devices (which may be personal computers, servers, or network devices, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.

[0120] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0121] In the several embodiments provided in the present application, it should be understood that the disclosed client can be implemented in other ways. Among them, 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. For example, 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 units or modules, which can be electrical or other forms.

[0122] 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 provided in this embodiment.

[0123] 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. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0124] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A system cloud disk data processing method, characterized in that: include: If the target system cloud disk in the current host has a preset processing requirement, uninstall the target system cloud disk from the current host; Mount the target system cloud disk on a normal host in the form of a data disk; After the normal host processes the system of the target system cloud disk and obtains a processed system cloud disk, uninstalling the processed system cloud disk from the normal host; The processed system cloud disk is mounted on the current host in the form of a system disk.

2. The method according to claim 1, characterized in that When the target system cloud disk in the current host has a preset processing requirement, uninstalling the target system cloud disk from the current host includes: When the target system cloud disk in the current host has a preset processing requirement, shutting down the current host; Call a preset interface to uninstall the target system cloud disk from the current host.

3. The method according to claim 2, characterized in that The calling of a preset interface to uninstall the target system cloud disk from the current host includes: Updating the current task status of the current host to system disk unloading; Send a system disk uninstallation startup message to the cloud platform; Unmounting the mount record of the target system cloud disk in the current host; Calling the preset interface to uninstall the target system cloud disk from the current host; In the case where it is determined that the target system cloud disk has been uninstalled in the current host, the current instance on the current host is marked as having no system cloud disk, and the current task state is set to blank to indicate that there is no task to uninstall the system cloud disk in the current host; Send a system disk uninstallation completion message to the cloud platform.

4. The method according to claim 3, characterized in that The processing of the target system cloud disk on the normal host and obtaining a processed system cloud disk includes: When the preset processing requirement is to repair the system of the target system cloud disk, the system of the target system cloud disk is repaired on the normal host, and a processed system cloud disk is obtained; When the preset processing requirement is to migrate the system of the target system cloud disk, the system of the target system cloud disk is migrated to the designated cloud disk on the normal host, and a processed system cloud disk is obtained after the designated cloud disk is migrated into the system.

5. The method according to claim 4, characterized in that The step of mounting the processed system cloud disk on the current host in the form of a system disk includes: When it is determined that the current host meets the preset mounting requirements, obtaining the target drive letter of the processed system cloud disk; According to the target drive letter, the processed system cloud disk is mounted to the current host.

6. The method according to claim 5, characterized in that The preset mounting requirement includes at least one of the following: The drive letter of the processed system cloud disk is not obtained; The current instance on the current host is in shutdown state; The current task status of the current host is that the system disk is not mounted; After the processing, the system cloud disk is a bootable disk.

7. The method according to claim 5, characterized in that The step of mounting the processed system cloud disk to the current host according to the target drive letter includes: When it is determined that the processed system cloud disk requested to be mounted on the current host is a system disk, directly determining the drive letter assigned to the processed system cloud disk as a default drive letter; Updating the current task status of the current host to system disk mounting; Send system disk mount startup message to the cloud platform; Calling the preset interface, and mounting the processed system cloud disk in the current host according to the target drive letter; In the case where it is determined that the processed system cloud disk has been mounted in the current host, the current instance on the current host is identified as having the system cloud disk mounted, and the current task state is set to blank to indicate that there is no task for mounting the system cloud disk in the current host; Adding a mounting record of mounting the processed system cloud disk in the current host and a mapping relationship between the processed system cloud disk and the current instance; Send a system disk mounting completion message to the cloud platform.

8. A system cloud disk data processing device, characterized in that: include: An uninstallation module, used for uninstalling the target system cloud disk from the current host when there is a preset processing requirement for the system of the target system cloud disk in the current host; A first mounting module, used to mount the target system cloud disk to a normal host in the form of a data disk; a processing module, configured to, after the normal host processes the system of the target system cloud disk and obtains a processed system cloud disk, uninstall the processed system cloud disk from the normal host; The second mounting module is used to mount the processed system cloud disk on the current host in the form of a system disk.

9. An electronic device comprising a processor, a communication interface, a memory and a communication bus, wherein: The processor, the communication interface and the memory communicate with each other via the communication bus, wherein: The memory is used to store computer programs; The processor is configured to execute the method according to any one of claims 1 to 7 by running the computer program stored in the memory.

10. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, wherein the computer program is configured to execute the method according to any one of claims 1 to 7 when executed.

Images