A method and device for cleaning residual data of storage volume

Abstract

The present application relates to the technical field of data storage, and in particular to a method and device for cleaning residual data of a storage volume. The method is applied to a Kubernetes cluster, and the method comprises: receiving a target persistent storage volume PV deletion request, and based on the target PV deletion request, obtaining information of a target storage volume corresponding to the target PV, wherein the target PV deletion request carries an instruction for cleaning residual data in the target storage volume corresponding to the target PV on a storage server; creating a task Job for cleaning residual data of the target storage volume, and starting the container service Pod corresponding to the Job; mounting a preset cleaning script to the Pod, and mounting the target storage volume to the Pod; starting the Pod, and cleaning residual data in the target storage volume based on the preset cleaning script.

Description

Technical Field

[0001] The present application relates to the technical field of data storage, and in particular to a method and device for cleaning residual data of a storage volume. Background Art

[0002] Container technology virtualization technology has become a widely recognized way to share container technology server resources. Container technology can provide system administrators with great flexibility in the process of building container technology operating system instances on demand. Many container services require external persistent storage to store data generated during the operation of container services to ensure data security. Kubernetes is currently the most widely used container orchestration technology. PV (Persistent Volume) in Kubernetes is a volume plug-in like Volume, but has a life cycle independent of the Pod that uses PV. When managing container services and the storage they use on the Kubernetes platform, Pod management corresponds to container service management, and PV management corresponds to storage management. When managing storage through PV resources, there is no management capability for storage volume data. After deleting PV resources in Kubernetes, storage service clients (ISCSI, NFS, etc.) will still have residual data and occupy storage resources. When the storage service client has less storage resources and uses the storage volume again, it is necessary to manually clean up the residual data on the storage service client to provide sufficient storage space for other container services to mount and use normally. Summary of the invention

[0003] The present application provides a storage volume residual data cleaning method and device to solve the problem in the prior art that when a PV resource is deleted, the residual data in the storage volume corresponding to the PV cannot be automatically deleted.

[0004] In a first aspect, the present application provides a method for cleaning residual data of a storage volume, which is applied to a Kubernetes cluster, and the method comprises:

[0005] Receive a target persistent storage volume PV deletion request, and based on the target PV deletion request, obtain information of a target storage volume corresponding to the target PV, wherein the target PV deletion request carries an instruction to clean up residual data in the target storage volume corresponding to the target PV on the storage server;

[0006] Create a task Job for cleaning up residual data of the target storage volume, and start the container service Pod corresponding to the Job;

[0007] Mounting a preset cleanup script to the Pod, and mounting the target storage volume to the Pod;

[0008] The Pod is started, and residual data in the target storage volume is cleaned up based on the preset cleanup script.

[0009] Optionally, based on the target PV deletion request, the step of obtaining information of a target storage volume corresponding to the target PV includes:

[0010] Based on the target PV deletion request, determining the target PV;

[0011] The description information of the target PV is obtained, wherein the description information of the target PV describes information of a target storage volume corresponding to the target PV.

[0012] Optionally, the steps of creating a task Job for cleaning up residual data of the target storage volume and starting a container service Pod corresponding to the Job include:

[0013] Creating a job for cleaning up residual data of the target storage volume;

[0014] Start a Pod that executes the Job.

[0015] Optionally, the step of mounting a preset cleanup script to the Pod and mounting the target storage volume to the Pod includes:

[0016] Mount the preset cleanup script to the first specified directory of the Pod;

[0017] The target storage volume is mounted to a second designated directory of the Pod, wherein the cleanup script is used to delete residual data in the target storage volume mounted under the second designated directory of the Pod.

[0018] Optionally, the step of starting the Pod and cleaning up residual data in the target storage volume based on the preset cleaning script includes:

[0019] Based on the container startup command, execute the cleanup script mounted in the first specified directory of the Pod;

[0020] Based on the cleanup script, residual data in the target storage volume mounted under the second specified directory of the Pod is cleaned up.

[0021] In a second aspect, the present application provides a storage volume residual data cleaning device, which is applied to a Kubernetes cluster, and the device includes:

[0022] A receiving unit, configured to receive a target persistent storage volume PV deletion request, and based on the target PV deletion request, obtain information of a target storage volume corresponding to the target PV, wherein the target PV deletion request carries an instruction to clean up residual data in the target storage volume corresponding to the target PV on the storage server;

[0023] A creation unit, used to create a task Job for cleaning up residual data of the target storage volume, and start a container service Pod corresponding to the Job;

[0024] A mounting unit, used to mount a preset cleanup script to the Pod, and to mount the target storage volume to the Pod;

[0025] A cleaning unit is used to start the Pod and clean up residual data in the target storage volume based on the preset cleaning script.

[0026] Optionally, when acquiring information of a target storage volume corresponding to the target PV based on the target PV deletion request, the receiving unit is specifically configured to:

[0027] Based on the target PV deletion request, determining the target PV;

[0028] The description information of the target PV is obtained, wherein the description information of the target PV describes information of a target storage volume corresponding to the target PV.

[0029] Optionally, when creating a task Job for cleaning up residual data of the target storage volume and starting a container service Pod corresponding to the Job, the creation unit is specifically used to:

[0030] Creating a job for cleaning up residual data of the target storage volume;

[0031] Start a Pod that executes the Job.

[0032] Optionally, when a preset cleanup script is mounted to the Pod and the target storage volume is mounted to the Pod, the mounting unit is specifically used to:

[0033] Mount the preset cleanup script to the first specified directory of the Pod;

[0034] The target storage volume is mounted to a second designated directory of the Pod, wherein the cleanup script is used to delete residual data in the target storage volume mounted under the second designated directory of the Pod.

[0035] Optionally, when the Pod is started and residual data in the target storage volume is cleaned up based on the preset cleanup script, the cleaning unit is specifically used to:

[0036] Based on the container startup command, execute the cleanup script mounted in the first specified directory of the Pod;

[0037] Based on the cleanup script, residual data in the target storage volume mounted under the second specified directory of the Pod is cleaned up.

[0038] In a third aspect, an embodiment of the present application provides a storage volume residual data cleaning device, which is applied to a Kubernetes cluster. The storage volume residual data cleaning device includes:

[0039] A memory for storing program instructions;

[0040] The processor is used to call the program instructions stored in the memory, and execute the steps of the method as described in any one of the first aspects above according to the obtained program instructions.

[0041] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to enable the computer to execute the steps of the method described in any one of the first aspects above.

[0042] In summary, the storage volume residual data cleaning method provided in the embodiment of the present application is applied to a Kubernetes cluster, and the method includes: receiving a target persistent storage volume PV deletion request, and based on the target PV deletion request, obtaining information of the target storage volume corresponding to the target PV, wherein the target PV deletion request carries an instruction to clean up the residual data in the target storage volume corresponding to the target PV on the storage server; creating a task Job for cleaning up the residual data of the target storage volume, and starting the container service Pod corresponding to the Job; mounting a preset cleaning script to the Pod, and mounting the target storage volume to the Pod; starting the Pod, and cleaning up the residual data in the target storage volume based on the preset cleaning script.

[0043] By adopting the storage volume residual data cleaning method provided in the embodiment of the present application, when deleting the PV resources of the Kubernetes cluster, a management job class container (Job) is started, and the preset cleaning script and the storage volume corresponding to the PV resource are mounted to the specified directory in the Pod container service corresponding to the Job. By starting the Pod corresponding to the Job, the cleaning script in the directory specified by the Pod is called to clean up the residual data in the storage volume corresponding to the PV resource, thereby realizing the automatic cleaning of the storage volume residual data, simplifying the cleaning process of the storage volume residual data, and being able to release the storage resources on the storage server in time. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] 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 of the present application or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For ordinary technicians in this field, other drawings can also be obtained based on these drawings of the embodiments of the present application.

[0045] Figure 1 A detailed flow chart of a method for cleaning residual data of a storage volume provided in an embodiment of the present application;

[0046] Figure 2 A schematic diagram of the structure of a storage system provided in an embodiment of the present application;

[0047] Figure 3 A schematic diagram of the structure of a storage volume residual data cleaning device provided in an embodiment of the present application;

[0048] Figure 4 A schematic diagram of the structure of another storage volume residual data cleaning device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0049] The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, rather than limiting the present application. The singular forms of "a", "said" and "the" used in the present application and claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to any or all possible combinations of one or more associated listed items.

[0050] It should be understood that, although the terms first, second, third, etc. may be used to describe various information in the embodiments of the present application, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the present application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, in addition, the word "if" used may be interpreted as "at..." or "when..." or "in response to determination".

[0051] For example, see Figure 1 As shown, it is a detailed flow chart of a storage volume residual data cleaning method provided in an embodiment of the present application, the method is applied to a Kubernetes cluster, and the method includes the following steps:

[0052] Step 100: Receive a target persistent storage volume PV deletion request, and based on the target PV deletion request, obtain information of a target storage volume corresponding to the target PV, wherein the target PV deletion request carries an instruction to clean up residual data in the target storage volume corresponding to the target PV on the storage server.

[0053] In the embodiment of the present application, the user initiates a target PV recovery or deletion request to the Kubernetes cluster through the operation interface or the backend interface, and the Kubernetes cluster receives the target PV recovery / deletion request initiated by the user. The request contains a cleanup field, which indicates that the residual data in the target storage volume on the storage server corresponding to the target PV needs to be cleaned up.

[0054] For example, see Figure 2 As shown, it is a structural diagram of a storage system provided in an embodiment of the present application, wherein the storage system includes a Kubernetes cluster and a storage server. A new container service os-kaas is added to the Kubernetes cluster, which is responsible for the management of PV resources and their corresponding persistent storage volumes on the Kubernetes cluster. When the container service os-kaas is used to recycle or delete the PV in the Kubernetes cluster, the os-kaas container service provides the ability to clean up the residual data of the PV to be recycled or deleted in the storage volume corresponding to the storage server.

[0055] In actual applications, when creating a PV in a Kubernetes cluster, you need to configure a storage volume for the PV on the storage service end to store data. The PV describes the storage volume information corresponding to the PV (such as storage type, mounted file system, capacity, read-write mode, storage volume path, etc.).

[0056] Then, in an embodiment of the present application, when obtaining information of a target storage volume corresponding to the target PV based on the target PV deletion request, a preferred implementation method is to determine the target PV based on the target PV deletion request; and obtain description information of the target PV, wherein the description information of the target PV describes information of the target storage volume corresponding to the target PV.

[0057] Step 110: Create a task Job for cleaning up residual data of the target storage volume, and start the container service Pod corresponding to the Job.

[0058] In an embodiment of the present application, when creating a task Job for cleaning up the residual data of the target storage volume and starting a container service Pod corresponding to the Job, a preferred implementation method is to create a Job for cleaning up the residual data of the target storage volume; and start a Pod that executes the Job.

[0059] Step 120: Mount a preset cleanup script to the Pod, and mount the target storage volume to the Pod.

[0060] In an embodiment of the present application, when a preset cleanup script is mounted to the Pod and the target storage volume is mounted to the Pod, a preferred implementation method is to mount the preset cleanup script to a first designated directory of the Pod; and mount the target storage volume to a second designated directory of the Pod, wherein the cleanup script is used to delete residual data in the target storage volume mounted under the second designated directory of the Pod.

[0061] Step 130: Start the Pod and clean up residual data in the target storage volume based on the preset cleanup script.

[0062] In an embodiment of the present application, when the Pod is started and the residual data in the target storage volume is cleaned up based on the preset cleanup script, a preferred implementation method is to execute the cleanup script mounted under the first specified directory of the Pod based on the container startup command; and based on the cleanup script, clean up the residual data in the target storage volume mounted under the second specified directory of the Pod.

[0063] In practical applications, combined with Figure 2As shown, os-kaas creates a dedicated Job in the Kubernetes cluster to clean up the residual data of the target storage volume. The Kubernetes cluster mounts the configMap named rm-data to the first specified directory ( / opt / clean / ) in the Pod corresponding to the Job. rm-data contains the cleaning script rm-data.sh, which implements the function of deleting the residual data in the second specified directory ( / var / lib / nginx / ). The Pod corresponding to the Job specifies the use of the target storage volume according to the target storage volume information obtained above, that is, the target storage 1 is mounted to the second specified directory ( / var / lib / nginx / ) in the Pod container service corresponding to the Job. Further, the container startup command can be used to execute the cleaning script rm-data.sh in the first specified directory ( / opt / clean / ) to delete all data in the second specified directory ( / var / lib / nginx / ) of the target storage volume mounted in the Pod corresponding to the Job. In this way, all residual data in the target storage volume can be deleted and cleaned up. os-kaas monitors the execution of the Pod corresponding to the dedicated cleaning Job and obtains the cleaning result information (whether the residual data is successfully cleaned).

[0064] Furthermore, the container service os-kaas initiates a request to delete or recycle the target PV to the kube-apiserver of the Kubernetes cluster. The Kubernetes cluster deletes or recycles the target PV and returns the operation result to os-kaas. After receiving the recovery or deletion operation result of the target PV, os-kaas feeds back to the user together with the above-mentioned target storage volume cleanup result.

[0065] Based on the same inventive concept as the above-mentioned embodiment of the invention, for example, refer to Figure 3 As shown, it is a structural schematic diagram of a storage volume residual data cleaning device provided in an embodiment of the present application, and the device is applied to a Kubernetes cluster, and the device includes:

[0066] The receiving unit 30 is used to receive a target persistent storage volume PV deletion request, and based on the target PV deletion request, obtain information of a target storage volume corresponding to the target PV, wherein the target PV deletion request carries an instruction to clean up residual data in the target storage volume corresponding to the target PV on the storage server;

[0067] A creation unit 31 is used to create a task Job for cleaning up residual data of the target storage volume, and start a container service Pod corresponding to the Job;

[0068] A mounting unit 32, used for mounting a preset cleanup script to the Pod, and mounting the target storage volume to the Pod;

[0069] The cleaning unit 33 is used to start the Pod and clean up the residual data in the target storage volume based on the preset cleaning script.

[0070] Optionally, when acquiring information of a target storage volume corresponding to the target PV based on the target PV deletion request, the receiving unit 30 is specifically configured to:

[0071] Based on the target PV deletion request, determining the target PV;

[0072] The description information of the target PV is obtained, wherein the description information of the target PV describes information of a target storage volume corresponding to the target PV.

[0073] Optionally, when creating a task Job for cleaning up residual data of the target storage volume and starting a container service Pod corresponding to the Job, the creation unit 31 is specifically used to:

[0074] Creating a job for cleaning up residual data of the target storage volume;

[0075] Start a Pod that executes the Job.

[0076] Optionally, when mounting a preset cleanup script to the Pod and mounting the target storage volume to the Pod, the mounting unit 32 is specifically used to:

[0077] Mount the preset cleanup script to the first specified directory of the Pod;

[0078] The target storage volume is mounted to a second designated directory of the Pod, wherein the cleanup script is used to delete residual data in the target storage volume mounted under the second designated directory of the Pod.

[0079] Optionally, when the Pod is started and residual data in the target storage volume is cleaned up based on the preset cleanup script, the cleaning unit 33 is specifically used to:

[0080] Based on the container startup command, execute the cleanup script mounted in the first specified directory of the Pod;

[0081] Based on the cleanup script, residual data in the target storage volume mounted under the second specified directory of the Pod is cleaned up.

[0082] The above units may be one or more integrated circuits configured to implement the above methods, such as one or more application specific integrated circuits (ASIC), or one or more digital singnal processors (DSP), or one or more field programmable gate arrays (FPGA). For another example, when a certain unit above is implemented in the form of a processing element scheduling program code, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processors that can call program codes. For another example, these units may be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0083] Furthermore, the storage volume residual data cleaning device provided in the embodiment of the present application, from the hardware level, the hardware architecture diagram of the storage volume residual data cleaning device can be seen in Figure 4 As shown, the storage volume residual data cleaning device may include: a memory 40 and a processor 41,

[0084] The memory 40 is used to store program instructions; the processor 41 calls the program instructions stored in the memory 40 and executes the above method embodiment according to the obtained program instructions. The specific implementation method and technical effect are similar and will not be repeated here.

[0085] Optionally, the present application also provides a storage volume residual data cleaning device, including at least one processing element (or chip) for executing the above method embodiment.

[0086] Optionally, the present application also provides a program product, such as a computer-readable storage medium, which stores computer-executable instructions, and the computer-executable instructions are used to enable the computer to execute the above method embodiments.

[0087] Here, the machine-readable storage medium may be any electronic, magnetic, optical or other physical storage device that may contain or store information, such as executable instructions, data, etc. For example, the machine-readable storage medium may be: RAM (RadomAccess Memory), volatile memory, non-volatile memory, flash memory, storage drive (such as hard disk drive), solid state drive, any type of storage disk (such as CD, DVD, etc.), or similar storage medium, or a combination thereof.

[0088] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which may be in the form of a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, a game console, a tablet computer, a wearable device or a combination of any of these devices.

[0089] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0090] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the embodiments of the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0091] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0092] Moreover, these computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0093] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0094] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A method for cleaning residual data of a storage volume, characterized in that: Applied to a Kubernetes cluster, the method includes: Receive a target persistent storage volume PV deletion request, and based on the target PV deletion request, obtain information of a target storage volume corresponding to the target PV, wherein the target PV deletion request carries an instruction to clean up residual data in the target storage volume corresponding to the target PV on the storage server; Create a task Job for cleaning up residual data of the target storage volume, and start the container service Pod corresponding to the Job; Mounting a preset cleanup script to the Pod, and mounting the target storage volume to the Pod; Starting the Pod and cleaning up residual data in the target storage volume based on the preset cleaning script; The steps of mounting a preset cleanup script to the Pod and mounting the target storage volume to the Pod include: Mount the preset cleanup script to the first specified directory of the Pod; The target storage volume is mounted to a second designated directory of the Pod, wherein the cleanup script is used to delete residual data in the target storage volume mounted under the second designated directory of the Pod.

2. The method according to claim 1, characterized in that Based on the target PV deletion request, the step of obtaining information of a target storage volume corresponding to the target PV includes: Based on the target PV deletion request, determining the target PV; The description information of the target PV is obtained, wherein the description information of the target PV describes information of a target storage volume corresponding to the target PV.

3. The method according to claim 1, characterized in that The steps of creating a task Job for cleaning up residual data of the target storage volume and starting a container service Pod corresponding to the Job include: Creating a job for cleaning up residual data of the target storage volume; Start a Pod that executes the Job.

4. The method according to claim 1, characterized in that The steps of starting the Pod and cleaning up residual data in the target storage volume based on the preset cleaning script include: Based on the container startup command, execute the cleanup script mounted in the first specified directory of the Pod; Based on the cleanup script, residual data in the target storage volume mounted under the second specified directory of the Pod is cleaned up.

5. A storage volume residual data cleaning device, characterized in that: Applied to a Kubernetes cluster, the device includes: A receiving unit, configured to receive a target persistent storage volume PV deletion request, and based on the target PV deletion request, obtain information of a target storage volume corresponding to the target PV, wherein the target PV deletion request carries an instruction to clean up residual data in the target storage volume corresponding to the target PV on the storage server; A creation unit, used to create a task Job for cleaning up residual data of the target storage volume, and start a container service Pod corresponding to the Job; A mounting unit, used to mount a preset cleanup script to the Pod, and to mount the target storage volume to the Pod; A cleaning unit, used to start the Pod and clean up residual data in the target storage volume based on the preset cleaning script; When mounting the preset cleanup script to the Pod and mounting the target storage volume to the Pod, the mounting unit is specifically used for: Mount the preset cleanup script to the first specified directory of the Pod; The target storage volume is mounted to a second designated directory of the Pod, wherein the cleanup script is used to delete residual data in the target storage volume mounted under the second designated directory of the Pod.

6. The device according to claim 5, characterized in that When acquiring information of a target storage volume corresponding to the target PV based on the target PV deletion request, the receiving unit is specifically configured to: Based on the target PV deletion request, determining the target PV; The description information of the target PV is obtained, wherein the description information of the target PV describes information of a target storage volume corresponding to the target PV.

7. The device according to claim 5, characterized in that When creating a task Job for cleaning up residual data of the target storage volume and starting a container service Pod corresponding to the Job, the creation unit is specifically used to: Creating a job for cleaning up residual data of the target storage volume; Start a Pod that executes the Job.

8. The device according to claim 5, characterized in that When the Pod is started and residual data in the target storage volume is cleaned up based on the preset cleanup script, the cleaning unit is specifically used to: Based on the container startup command, execute the cleanup script mounted in the first specified directory of the Pod; Based on the cleanup script, residual data in the target storage volume mounted under the second specified directory of the Pod is cleaned up.

Images