CN110795029B - Cloud hard disk management method, device, server and medium - Google Patents
Cloud hard disk management method, device, server and medium Download PDFInfo
- Publication number
- CN110795029B CN110795029B CN201910949401.4A CN201910949401A CN110795029B CN 110795029 B CN110795029 B CN 110795029B CN 201910949401 A CN201910949401 A CN 201910949401A CN 110795029 B CN110795029 B CN 110795029B
- Authority
- CN
- China
- Prior art keywords
- hard disk
- cloud hard
- target
- target cloud
- searched
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 38
- 238000011084 recovery Methods 0.000 claims description 60
- 238000004590 computer program Methods 0.000 claims description 12
- 239000000126 substance Substances 0.000 claims description 2
- 238000000034 method Methods 0.000 description 8
- 238000004891 communication Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000004064 recycling Methods 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0662—Virtualisation aspects
- G06F3/0664—Virtualisation aspects at device level, e.g. emulation of a storage device or system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
- G06F3/0652—Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0662—Virtualisation aspects
- G06F3/0665—Virtualisation aspects at area level, e.g. provisioning of virtual or logical volumes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F2003/0697—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers device management, e.g. handlers, drivers, I/O schedulers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45583—Memory management, e.g. access or allocation
Abstract
The application discloses a cloud hard disk management method, a cloud hard disk management device, a server and a medium, wherein the cloud hard disk management method comprises the following steps: creating capability information which corresponds to the rear-end storage device and provides the cloud hard disk; acquiring cloud hard disk demand information sent by a user terminal; searching a target cloud hard disk in a cloud hard disk list by using the cloud hard disk demand information, if the target cloud hard disk is searched, mounting the searched target cloud hard disk on a corresponding user virtual machine, if the target cloud hard disk is not searched, searching the back-end storage equipment of which the capability information meets a preset condition, then creating the target cloud hard disk in the searched back-end storage equipment, and mounting the created target cloud hard disk on the corresponding user virtual machine. Therefore, the user can obtain the corresponding target cloud hard disk only by submitting the cloud hard disk requirement information, so that the learning cost of the user is reduced, and the utilization rate of the cloud hard disk is improved.
Description
Technical Field
The present application relates to the field of cloud hard disk technologies, and in particular, to a cloud hard disk management method, an apparatus, a server, and a medium.
Background
The OpenStack is an open-source cloud computing management platform project, almost all types of cloud environments are supported, and the project aims at providing a cloud computing management platform which is simple to implement, can be expanded in a large scale, is rich and has a unified standard. The user can create a cloud hard disk on the OpenStack or select an existing cloud hard disk, mount the cloud hard disk on a corresponding virtual machine, and perform operations such as partitioning and file system creation on the cloud hard disk. In a large openstack environment, multiple types of storage backend devices may exist simultaneously, thousands of virtual machines and cloud hard disk instances exist, and mounting management between the virtual machines and the cloud hard disks is very complicated.
In the prior art, the mounting management between the virtual machine and the cloud hard disk on the OpenStack platform is that a system administrator creates a corresponding cloud hard disk type for a back-end storage device, creates some cloud hard disks for standby, and a user selects an existing cloud hard disk or selects a cloud hard disk type and creates a cloud hard disk, and then mounts the cloud hard disk on a corresponding user virtual machine.
Disclosure of Invention
In view of this, an object of the present application is to provide a method, an apparatus, a server and a medium for managing a cloud hard disk, which can reduce the learning cost of a user and improve the utilization rate of the cloud hard disk. The specific scheme is as follows:
in a first aspect, the application discloses a cloud disk management method applied to an OpenStack platform, including:
creating capability information which corresponds to the back-end storage device and provides the cloud hard disk;
acquiring cloud hard disk demand information sent by a user terminal;
searching a target cloud hard disk in a cloud hard disk list by using the cloud hard disk demand information, if the target cloud hard disk is searched, mounting the searched target cloud hard disk on a corresponding user virtual machine, if the target cloud hard disk is not searched, searching the rear-end storage equipment of which the capability information meets a preset condition, then creating the target cloud hard disk in the searched rear-end storage equipment, and mounting the created target cloud hard disk on the corresponding user virtual machine.
Optionally, the creating capability information of the cloud hard disk corresponding to the back-end storage device includes:
and creating a first access policy, a first recovery policy and a first IO speed of the cloud hard disk which can be provided and correspond to the back-end storage device.
Optionally, the acquiring the cloud disk requirement information sent by the user terminal includes:
and acquiring a second access strategy, a second recovery strategy, a second IO speed and a second storage space of the required cloud hard disk, which are sent by the user terminal.
Optionally, the searching for the target cloud hard disk in the cloud hard disk list by using the cloud hard disk demand information includes:
searching a target cloud hard disk in a cloud hard disk list by using the cloud hard disk demand information; the third access policy of the target cloud hard disk is consistent with the second access policy, the third recovery policy of the target cloud hard disk comprises the second recovery policy, the third IO speed of the target cloud hard disk is greater than or equal to the second IO speed, and the third storage space of the target cloud hard disk is greater than or equal to the second storage space.
Optionally, the searching for the back-end storage device whose capability information meets the preset condition includes:
the searching of the first access policy comprises a second access policy, and the first recovery policy comprises a second recovery policy and the backend storage device with the first IO speed greater than or equal to the second IO speed.
Optionally, the method further includes:
acquiring a unbinding cloud hard disk request sent by a user terminal, generating a corresponding unbinding instruction, then unbinding the target cloud hard disk mounted on the corresponding user virtual machine under the control of the unbinding instruction, and recovering the unbound target cloud hard disk according to the corresponding second recovery strategy.
Optionally, the method further includes:
and if the corresponding second recovery strategy is data clearing, adding the target cloud hard disk with the data cleared into the cloud hard disk list.
In a second aspect, the application discloses a cloud hard disk management device, which is applied to an OpenStack platform and includes:
the back-end storage device information creating module is used for creating capability information which corresponds to the back-end storage device and provides the cloud hard disk;
the cloud hard disk demand information acquisition module is used for acquiring cloud hard disk demand information sent by a user terminal;
the cloud hard disk scheduling module is used for searching a target cloud hard disk in a cloud hard disk list by using the cloud hard disk demand information, mounting the searched target cloud hard disk on a corresponding user virtual machine if the target cloud hard disk is searched, searching the rear-end storage device of which the capacity information meets a preset condition if the target cloud hard disk is not searched, then creating the target cloud hard disk in the searched rear-end storage device, and mounting the created target cloud hard disk on the corresponding user virtual machine.
In a third aspect, the present application discloses a server comprising a processor and a memory; wherein the content of the first and second substances,
the memory is used for storing a computer program;
the processor is configured to execute the computer program to implement the cloud hard disk management method.
In a fourth aspect, the present application discloses a computer-readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the foregoing cloud hard disk management method.
As can be seen, in the application, capability information for providing a cloud hard disk corresponding to a storage device is created first, cloud hard disk demand information sent by a user terminal is obtained, then a target cloud hard disk is searched in a cloud hard disk list by using the cloud hard disk demand information, if the target cloud hard disk is searched, the searched target cloud hard disk is mounted on a corresponding user virtual machine, if the target cloud hard disk is not searched, the back-end storage device of which the capability information meets a preset condition is searched, then the target cloud hard disk is created in the searched back-end storage device, and the created target cloud hard disk is mounted on the corresponding user virtual machine. In this way, the target cloud hard disk can be searched or created by using the acquired cloud hard disk demand information, and the target cloud hard disk is mounted on the user virtual machine, that is, the user can obtain the corresponding target cloud hard disk only by submitting the cloud hard disk demand information, so that the learning cost of the user is reduced.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a cloud disk management method disclosed in the present application;
fig. 2 is a flowchart of a specific cloud hard disk management method disclosed in the present application;
fig. 3 is a schematic structural diagram of a cloud hard disk management apparatus disclosed in the present application;
fig. 4 is a schematic diagram of a specific cloud hard disk management apparatus disclosed in the present application;
fig. 5 is a diagram of a server structure disclosed in the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the prior art, the mounting management between the virtual machine and the cloud hard disk on the OpenStack platform is that a system administrator creates a corresponding cloud hard disk type for a back-end storage device, creates some cloud hard disks for standby, and a user selects an existing cloud hard disk or selects a cloud hard disk type and creates a cloud hard disk, and then mounts the cloud hard disk on a corresponding user virtual machine. Therefore, the cloud hard disk management scheme is provided, the learning cost of a user can be reduced, and the utilization rate of the cloud hard disk is improved.
Referring to fig. 1, an embodiment of the present application discloses a cloud hard disk management method, which is applied to an OpenStack platform, and includes:
step S11: and creating capability information which corresponds to the back-end storage device and provides the cloud hard disk.
In a specific implementation manner, in this embodiment, capability information, which is sent by an administrator terminal and is provided with a cloud hard disk corresponding to a backend storage device defined by the administrator, may be first obtained, and then analyzed, and capability information, which is provided with a standard backend storage device and is provided with a cloud hard disk, corresponding to the backend storage device is created, where the created capability information includes a first access policy, a first recovery policy, a first IO speed, and the like of the cloud hard disk that can be provided, corresponding to the backend storage device. For example:
{
name:storage1
storageBackend:AS5500G2
supportAccessModes：
-ReadWriteonce
-ReadOnlyMany
-ReadWriteMany
recyclePolicy：
-Retain
-Clean
-Delete
Qos
IOSpeed：100M/S
}
the storage backend device AS5500G2 supports three access strategies, namely, a cloud hard disk can reach a single node in a read-write mode, can reach a plurality of nodes in a read-only mode, and can reach a plurality of nodes in a read-write mode; the cloud hard disk provided by the storage back-end equipment supports three recovery strategies: reserving data, clearing data and deleting hard disks; the peak value of IO speed of the cloud disk provided by the storage device is 100M/s.
In addition, in this embodiment, after the capability information is created, the capability information is associated with the corresponding storage backend device, so that all the cloud hard disks created in the storage backend device are associated with the capability information, that is, the cloud hard disk created by this embodiment and the hard disk created by the user may be associated with the capability information of the corresponding storage backend device, which provides the cloud hard disk.
Step S12: and acquiring the cloud hard disk demand information sent by the user terminal.
In a specific implementation manner, the cloud hard disk demand information sent by the user terminal is obtained first, and then is analyzed; the cloud hard disk demand information includes, but is not limited to, a second access policy, a second recovery policy, a second IO speed, a second storage space, and the like, which demand the cloud hard disk, and the second access policy may be that the cloud hard disk can move to a single node in a read-write mode, or the cloud hard disk can move to a plurality of nodes in a read-only mode, or the cloud hard disk can move to a plurality of nodes in a read-write mode; the second recovery strategy can be to retain data or clear data or delete hard disks; for example, the cloud hard disk requirement information is
name:myVolume
accessModes：
-ReadWriteonce
recyclePolicy：
-Retain
resources：
requests：
storage：5GB
IOSpeed：100M/S
}
Namely, a user needs to apply for a cloud hard disk with a storage space of at least 5GB and an IO speed of at least 100M/s, the hard disk can be moved to a single node in a read-write mode, and a recovery strategy after the hard disk is unbound is to reserve data in the hard disk.
Step S13: searching a target cloud hard disk in a cloud hard disk list by using the cloud hard disk demand information, if the target cloud hard disk is searched, mounting the searched target cloud hard disk on a corresponding user virtual machine, if the target cloud hard disk is not searched, searching the rear-end storage equipment of which the capability information meets a preset condition, then creating the target cloud hard disk in the searched rear-end storage equipment, and mounting the created target cloud hard disk on the corresponding user virtual machine.
In a specific implementation manner, in this embodiment, a target cloud hard disk may be first searched in a cloud hard disk list according to cloud hard disk demand information, and specifically, an existing available cloud hard disk list may be obtained from a shader, where a third access policy of the target cloud hard disk is consistent with the second access policy, a third recovery policy of the target cloud hard disk includes the second recovery policy, a third IO speed of the target cloud hard disk is greater than or equal to the second IO speed, and a third storage space of the target cloud hard disk is greater than or equal to the second storage space. That is, the target cloud hard disk with consistent access policies including the demand recovery policy, the IO speed greater than or equal to the demand IO speed, and the storage space greater than or equal to the demand storage space is searched, and if a plurality of cloud hard disks meeting the above conditions are found, it is determined that one cloud hard disk with the smallest storage space is the target cloud hard disk. If the target cloud hard disk cannot be found, finding the back-end storage device of which the capability information meets the preset condition, specifically, finding the first access policy comprises a second access policy, and the first recovery policy comprises a second recovery policy and the back-end storage device of which the first IO speed is greater than or equal to the second IO speed, and then creating the target cloud hard disk in the back-end storage device. It should be noted that, a user creates a virtual machine according to a service requirement, determines cloud hard disk requirement information to be mounted by the virtual machine, and then submits a virtual machine ID and the cloud hard disk requirement information, so that, according to this embodiment, after a target cloud hard disk is found or created, the target cloud hard disk is mounted to a corresponding user virtual machine according to the virtual machine ID.
As can be seen, in the embodiment of the application, capability information corresponding to a storage device and providing a cloud hard disk is created first, cloud hard disk demand information sent by a user terminal is obtained, then a target cloud hard disk is searched in a cloud hard disk list by using the cloud hard disk demand information, if the target cloud hard disk is found, the found target cloud hard disk is mounted on a corresponding user virtual machine, if the target cloud hard disk is not found, the back-end storage device of which the capability information meets a preset condition is found, then the target cloud hard disk is created in the found back-end storage device, and the created target cloud hard disk is mounted on the corresponding user virtual machine. In this way, the target cloud hard disk can be searched or created by using the acquired cloud hard disk demand information, and the target cloud hard disk is mounted on the user virtual machine, that is, the user can obtain the corresponding target cloud hard disk only by submitting the cloud hard disk demand information, so that the learning cost of the user is reduced.
Referring to fig. 2, the embodiment of the present application discloses a specific cloud hard disk management method, including:
step S21: and creating capability information which corresponds to the back-end storage device and provides the cloud hard disk.
Step S22: and acquiring the cloud hard disk demand information sent by the user terminal.
Step S23: searching a target cloud hard disk in a cloud hard disk list by using the cloud hard disk demand information, if the target cloud hard disk is searched, mounting the searched target cloud hard disk on a corresponding user virtual machine, if the target cloud hard disk is not searched, searching the rear-end storage equipment of which the capability information meets a preset condition, then creating the target cloud hard disk in the searched rear-end storage equipment, and mounting the created target cloud hard disk on the corresponding user virtual machine.
For the specific processes of the steps S21 to S23, reference may be made to the corresponding contents disclosed in the foregoing embodiments, and details are not repeated here.
Step S24: acquiring a unbinding cloud hard disk request sent by a user terminal, generating a corresponding unbinding instruction, then unbinding the target cloud hard disk mounted on the corresponding user virtual machine under the control of the unbinding instruction, and recovering the unbound target cloud hard disk according to the corresponding second recovery strategy.
In a specific implementation manner, the embodiment may search the second recovery policy corresponding to the target cloud hard disk for recovery processing by using the ID information of the target cloud hard disk; for example, if the corresponding second recovery policy is to remove data, that is, format, the data in the target cloud hard disk is removed, if the corresponding second recovery policy is to delete a hard disk, the target cloud hard disk is deleted, and if the corresponding second recovery policy is to reserve data, the data is not processed after unbinding, so that the virtual machine user can reuse the data therein. Specifically, a storage back-end interface corresponding to the cloud hard disk may be called to perform corresponding recovery processing on the cloud hard disk, and if the corresponding second recovery policy is to clear data, the target cloud hard disk with the data cleared is added to the cloud hard disk list.
Referring to fig. 3, an embodiment of the present application discloses a cloud disk management device, which is applied to an OpenStack platform, and includes:
the back-end storage device information creating module 11 is configured to create capability information, which is corresponding to the back-end storage device and provides a cloud hard disk;
the cloud hard disk demand information acquisition module 12 is used for acquiring cloud hard disk demand information sent by a user terminal;
the cloud hard disk scheduling module 13 is configured to search a target cloud hard disk in a cloud hard disk list by using the cloud hard disk demand information, mount the searched target cloud hard disk to a corresponding user virtual machine if the target cloud hard disk is found, search the back-end storage device whose capability information meets a preset condition if the target cloud hard disk is not found, then create the target cloud hard disk in the searched back-end storage device, and mount the created target cloud hard disk to the corresponding user virtual machine.
As can be seen, in the embodiment of the application, the capability information of the storage device corresponding to the cloud hard disk is created, the cloud hard disk demand information sent by the user terminal is obtained, then the target cloud hard disk is searched in the cloud hard disk list by using the cloud hard disk demand information, if the target cloud hard disk is found, the found target cloud hard disk is mounted on the corresponding user virtual machine, if the target cloud hard disk is not found, the back-end storage device of which the capability information meets the preset condition is found, then the target cloud hard disk is created in the found back-end storage device, and the created target cloud hard disk is mounted on the corresponding user virtual machine. In this way, the target cloud hard disk can be searched or created by using the acquired cloud hard disk demand information, and the target cloud hard disk is mounted on the user virtual machine, that is, the user can obtain the corresponding target cloud hard disk only by submitting the cloud hard disk demand information, so that the learning cost of the user is reduced.
The back-end storage device information creating module 11 specifically creates a first access policy, a first recovery policy, and a first IO speed of the cloud hard disk, which can be provided and correspond to the back-end storage device.
The cloud hard disk demand information obtaining module 12 is specifically configured to obtain a second access policy, a second recovery policy, a second IO speed, and a second storage space, which are sent by the user terminal and are required for the cloud hard disk.
The cloud hard disk scheduling module 13 specifically includes a target cloud hard disk searching sub-module, configured to search a target cloud hard disk in a cloud hard disk list by using the cloud hard disk demand information; searching a target cloud hard disk in a cloud hard disk list by using the cloud hard disk demand information; the third access policy of the target cloud hard disk is consistent with the second access policy, the third recovery policy of the target cloud hard disk comprises the second recovery policy, the third IO speed of the target cloud hard disk is greater than or equal to the second IO speed, and the third storage space of the target cloud hard disk is greater than or equal to the second storage space.
The cloud hard disk scheduling module 13 specifically includes a backend storage device search sub-module, configured to search for a backend storage device whose first access policy includes a second access policy, and whose first recovery policy includes a second recovery policy and a first IO speed is greater than or equal to a second IO speed.
The cloud hard disk scheduling module 13 specifically further includes a target cloud hard disk unbinding module, which is configured to acquire an unbinding cloud hard disk request sent by a user terminal, generate a corresponding unbinding instruction, then, under the control of the unbinding instruction, unbind the corresponding target cloud hard disk mounted on the user virtual machine, and recycle the unbound target cloud hard disk according to the corresponding second recycling policy.
For example, referring to fig. 4, fig. 4 is a schematic view of a specific cloud hard disk management device disclosed in the embodiment of the present application. Specifically, a system administrator configures backend storage equipment docked by a client in the OpenStack, defines capability information, which is corresponding to the backend storage equipment and provides a cloud hard disk, according to performance characteristics of the backend storage equipment, sends the defined capability information to a backend storage equipment information creation module, creates capability information, which is corresponding to standard backend storage equipment and provides the cloud hard disk, of the backend storage equipment by the backend storage equipment information creation module, sends the created capability information to a cloud hard disk scheduling module, and associates the stored backend equipment with the corresponding capability information; the virtual machine user creates a virtual machine according to the service requirement, then selects a corresponding virtual machine, creates corresponding cloud hard disk requirement information, and sends the corresponding cloud hard disk requirement information to the cloud hard disk requirement information acquisition module, then the cloud hard disk demand information acquisition module analyzes the cloud hard disk demand information and then sends the cloud hard disk demand information to the cloud hard disk scheduling module, the cloud hard disk scheduling module searches a target cloud hard disk in a cloud hard disk list by using the cloud hard disk demand information, if the target cloud hard disk is found, mounting the searched target cloud hard disk on a corresponding user virtual machine, if the target cloud hard disk is not searched, searching the back-end storage device with the capability information meeting preset conditions, then, the target cloud hard disk is created in the found back-end storage device, and the created target cloud hard disk is mounted on the corresponding user virtual machine; the cloud hard disk scheduling module acquires a unbinding cloud hard disk request sent by a user terminal, generates a corresponding unbinding instruction, then, under the control of the unbinding instruction, unbinds the target cloud hard disk mounted on the corresponding user virtual machine, recovers the unbound target cloud hard disk according to the corresponding second recovery strategy, and if the corresponding second recovery strategy is data clearing, adds the data-cleared target cloud hard disk into the cloud hard disk list.
Referring to fig. 5, the embodiment of the present application discloses a server 20, which includes a processor 21 and a memory 22; wherein, the memory 22 is used for saving computer programs; the processor 21 is configured to execute the computer program to implement the following steps:
creating capability information which corresponds to the rear-end storage device and provides the cloud hard disk; acquiring cloud hard disk demand information sent by a user terminal; searching a target cloud hard disk in a cloud hard disk list by using the cloud hard disk demand information, if the target cloud hard disk is searched, mounting the searched target cloud hard disk on a corresponding user virtual machine, if the target cloud hard disk is not searched, searching the rear-end storage equipment of which the capability information meets a preset condition, then creating the target cloud hard disk in the searched rear-end storage equipment, and mounting the created target cloud hard disk on the corresponding user virtual machine.
As can be seen, in the embodiment of the application, capability information corresponding to a storage device and providing a cloud hard disk is created first, cloud hard disk demand information sent by a user terminal is obtained, then a target cloud hard disk is searched in a cloud hard disk list by using the cloud hard disk demand information, if the target cloud hard disk is found, the found target cloud hard disk is mounted on a corresponding user virtual machine, if the target cloud hard disk is not found, the back-end storage device of which the capability information meets a preset condition is found, then the target cloud hard disk is created in the found back-end storage device, and the created target cloud hard disk is mounted on the corresponding user virtual machine. In this way, the target cloud hard disk can be searched or created by using the acquired cloud hard disk demand information, and the target cloud hard disk is mounted on the user virtual machine, that is, the user can obtain the corresponding target cloud hard disk only by submitting the cloud hard disk demand information, so that the learning cost of the user is reduced.
In this embodiment, when the processor 21 executes the computer subprogram stored in the memory 22, the following steps may be specifically implemented: and creating a first access policy, a first recovery policy and a first IO speed of the cloud hard disk which can be provided and correspond to the back-end storage device.
In this embodiment, when the processor 21 executes the computer subprogram stored in the memory 22, the following steps may be specifically implemented: and acquiring a second access strategy, a second recovery strategy, a second IO speed and a second storage space of the required cloud hard disk, which are sent by the user terminal.
In this embodiment, when the processor 21 executes the computer subprogram stored in the memory 22, the following steps may be specifically implemented: searching a target cloud hard disk in a cloud hard disk list by using the cloud hard disk demand information; the third access policy of the target cloud hard disk is consistent with the second access policy, the third recovery policy of the target cloud hard disk comprises the second recovery policy, the third IO speed of the target cloud hard disk is greater than or equal to the second IO speed, and the third storage space of the target cloud hard disk is greater than or equal to the second storage space.
In this embodiment, when the processor 21 executes the computer subprogram stored in the memory 22, the following steps may be specifically implemented: the searching of the first access policy comprises a second access policy, and the first recovery policy comprises a second recovery policy and the backend storage device with the first IO speed greater than or equal to the second IO speed.
In this embodiment, when the processor 21 executes the computer subprogram stored in the memory 22, the following steps may be specifically implemented: acquiring a unbinding cloud hard disk request sent by a user terminal, generating a corresponding unbinding instruction, then unbinding the target cloud hard disk mounted on the corresponding user virtual machine under the control of the unbinding instruction, and recovering the unbound target cloud hard disk according to the corresponding second recovery strategy.
In this embodiment, when the processor 21 executes the computer subprogram stored in the memory 22, the following steps may be specifically implemented: and if the corresponding second recovery strategy is data clearing, adding the target cloud hard disk with the data cleared into the cloud hard disk list.
The memory 22 is used as a carrier for resource storage, and may be a read-only memory, a random access memory, a magnetic disk or an optical disk, and the storage mode may be a transient storage mode or a permanent storage mode.
In addition, the server 20 further includes a power supply 23, a communication interface 24, an input-output interface 25, and a communication bus 26; the power supply 23 is configured to provide an operating voltage for each hardware device on the server 20; the communication interface 24 can create a data transmission channel with an external device for the server 20, and a communication protocol followed by the communication interface is any communication protocol applicable to the technical solution of the present application, and is not specifically limited herein; the input/output interface 25 is configured to acquire external input data or output data to the outside, and a specific interface type thereof may be selected according to specific application requirements, which is not specifically limited herein.
Further, an embodiment of the present application also discloses a computer-readable storage medium for storing a computer program, where the computer program implements the following steps when executed by a processor:
creating capability information which corresponds to the rear-end storage device and provides the cloud hard disk; acquiring cloud hard disk demand information sent by a user terminal; searching a target cloud hard disk in a cloud hard disk list by using the cloud hard disk demand information, if the target cloud hard disk is searched, mounting the searched target cloud hard disk on a corresponding user virtual machine, if the target cloud hard disk is not searched, searching the rear-end storage equipment of which the capability information meets a preset condition, then creating the target cloud hard disk in the searched rear-end storage equipment, and mounting the created target cloud hard disk on the corresponding user virtual machine.
As can be seen, in the embodiment of the application, the capability information of the storage device corresponding to the cloud hard disk is created, the cloud hard disk demand information sent by the user terminal is obtained, then the target cloud hard disk is searched in the cloud hard disk list by using the cloud hard disk demand information, if the target cloud hard disk is found, the found target cloud hard disk is mounted on the corresponding user virtual machine, if the target cloud hard disk is not found, the back-end storage device of which the capability information meets the preset condition is found, then the target cloud hard disk is created in the found back-end storage device, and the created target cloud hard disk is mounted on the corresponding user virtual machine. In this way, the target cloud hard disk can be searched or created by using the acquired cloud hard disk demand information, and the target cloud hard disk is mounted on the user virtual machine, that is, the user can obtain the corresponding target cloud hard disk only by submitting the cloud hard disk demand information, so that the learning cost of the user is reduced.
In this embodiment, when the computer subprogram stored in the computer-readable storage medium is executed by the processor, the following steps may be specifically implemented: and creating a first access policy, a first recovery policy and a first IO speed of the cloud hard disk which can be provided and correspond to the back-end storage device.
In this embodiment, when the computer subprogram stored in the computer-readable storage medium is executed by the processor, the following steps may be specifically implemented: and acquiring a second access strategy, a second recovery strategy, a second IO speed and a second storage space of the required cloud hard disk, which are sent by the user terminal.
In this embodiment, when the computer subprogram stored in the computer-readable storage medium is executed by the processor, the following steps may be specifically implemented: searching a target cloud hard disk in a cloud hard disk list by using the cloud hard disk demand information; the third access policy of the target cloud hard disk is consistent with the second access policy, the third recovery policy of the target cloud hard disk comprises the second recovery policy, the third IO speed of the target cloud hard disk is greater than or equal to the second IO speed, and the third storage space of the target cloud hard disk is greater than or equal to the second storage space.
In this embodiment, when the computer subprogram stored in the computer-readable storage medium is executed by the processor, the following steps may be specifically implemented: the searching of the first access policy comprises a second access policy, and the first recovery policy comprises a second recovery policy and the backend storage device with the first IO speed greater than or equal to the second IO speed.
In this embodiment, when the computer subprogram stored in the computer-readable storage medium is executed by the processor, the following steps may be specifically implemented: acquiring a unbinding cloud hard disk request sent by a user terminal, generating a corresponding unbinding instruction, then unbinding the target cloud hard disk mounted on the corresponding user virtual machine under the control of the unbinding instruction, and recovering the unbound target cloud hard disk according to the corresponding second recovery strategy.
In this embodiment, when the processor executes the computer subprogram stored in the computer readable storage medium, the following steps may be specifically implemented: and if the corresponding second recovery strategy is data clearing, adding the target cloud hard disk with the data cleared into the cloud hard disk list.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The cloud hard disk management method, the cloud hard disk management device, the cloud hard disk management server and the cloud hard disk management medium are introduced in detail, specific examples are applied in the description to explain the principle and the implementation mode of the cloud hard disk management method, and the description of the embodiments is only used for helping to understand the method and the core idea of the cloud hard disk management method; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (8)
1. A cloud hard disk management method is applied to an OpenStack platform and comprises the following steps:
creating capability information which corresponds to the rear-end storage device and provides the cloud hard disk;
acquiring cloud hard disk demand information sent by a user terminal;
searching a target cloud hard disk in a cloud hard disk list by using the cloud hard disk demand information, if the target cloud hard disk is searched, mounting the searched target cloud hard disk on a corresponding user virtual machine, if the target cloud hard disk is not searched, searching the rear-end storage equipment of which the capability information meets a preset condition, then creating the target cloud hard disk in the searched rear-end storage equipment, and mounting the created target cloud hard disk on the corresponding user virtual machine;
the creating of the capability information of the cloud hard disk corresponding to the back-end storage device includes:
creating a first access strategy, a first recovery strategy and a first IO speed of a cloud hard disk which can be provided and correspond to the back-end storage device;
the acquiring of the cloud hard disk demand information sent by the user terminal includes:
and acquiring a second access strategy, a second recovery strategy, a second IO speed and a second storage space of the required cloud hard disk, which are sent by the user terminal.
2. The cloud hard disk management method according to claim 1, wherein the searching for the target cloud hard disk in the cloud hard disk list by using the cloud hard disk requirement information includes:
searching a target cloud hard disk in a cloud hard disk list by using the cloud hard disk demand information; the third access policy of the target cloud hard disk is consistent with the second access policy, the third recovery policy of the target cloud hard disk comprises the second recovery policy, the third IO speed of the target cloud hard disk is greater than or equal to the second IO speed, and the third storage space of the target cloud hard disk is greater than or equal to the second storage space.
3. The cloud hard disk management method according to claim 1, wherein the searching for the backend storage device whose capability information meets a preset condition includes:
the searching of the first access policy comprises a second access policy, and the first recovery policy comprises a second recovery policy and the backend storage device with the first IO speed greater than or equal to the second IO speed.
4. The cloud hard disk management method according to any one of claims 1 to 3, further comprising:
acquiring a unbinding cloud hard disk request sent by a user terminal, generating a corresponding unbinding instruction, then unbinding the target cloud hard disk mounted on the corresponding user virtual machine under the control of the unbinding instruction, and recovering the unbound target cloud hard disk according to the corresponding second recovery strategy.
5. The cloud hard disk management method according to claim 4, further comprising:
and if the corresponding second recovery strategy is data clearing, adding the target cloud hard disk with the data cleared into the cloud hard disk list.
6. The cloud hard disk management device is applied to an OpenStack platform and comprises the following components:
the back-end storage device information creating module is used for creating capability information which corresponds to the back-end storage device and provides the cloud hard disk;
the cloud hard disk demand information acquisition module is used for acquiring cloud hard disk demand information sent by a user terminal;
the cloud hard disk scheduling module is used for searching a target cloud hard disk in a cloud hard disk list by using the cloud hard disk demand information, if the target cloud hard disk is searched, mounting the searched target cloud hard disk on a corresponding user virtual machine, if the target cloud hard disk is not searched, searching the rear-end storage equipment of which the capacity information meets a preset condition, then creating the target cloud hard disk in the searched rear-end storage equipment, and mounting the created target cloud hard disk on the corresponding user virtual machine;
the back-end storage device information creation module specifically creates a first access policy, a first recovery policy and a first IO speed of a cloud hard disk, which can be provided and correspond to the back-end storage device;
the cloud hard disk demand information acquisition module is specifically used for acquiring a second access strategy, a second recovery strategy, a second IO speed and a second storage space of a demand cloud hard disk sent by a user terminal.
7. A server, comprising a processor and a memory; wherein the content of the first and second substances,
the memory is used for storing a computer program;
the processor is configured to execute the computer program to implement the cloud hard disk management method according to any one of claims 1 to 5.
8. A computer-readable storage medium storing a computer program, wherein the computer program when executed by a processor implements the cloud hard disk management method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910949401.4A CN110795029B (en) | 2019-10-08 | 2019-10-08 | Cloud hard disk management method, device, server and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910949401.4A CN110795029B (en) | 2019-10-08 | 2019-10-08 | Cloud hard disk management method, device, server and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110795029A CN110795029A (en) | 2020-02-14 |
| CN110795029B true CN110795029B (en) | 2022-06-17 |
Family
ID=69439292
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910949401.4A Active CN110795029B (en) | 2019-10-08 | 2019-10-08 | Cloud hard disk management method, device, server and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110795029B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112532577B (en) * | 2020-10-22 | 2022-12-27 | 苏州浪潮智能科技有限公司 | Mirror image creation cloud hard disk certificate verification method and device and storage medium |
| CN112328363B (en) * | 2020-11-05 | 2022-12-20 | 北京金山云网络技术有限公司 | Cloud hard disk mounting method and device |
| CN112433811B (en) * | 2020-11-19 | 2023-12-22 | 北京浪潮数据技术有限公司 | Virtual hard disk replacement method, device, equipment, system and readable storage medium |
| CN114579036B (en) * | 2020-11-30 | 2024-02-13 | 北京达佳互联信息技术有限公司 | Storage device management method and related device |
| CN113311995B (en) * | 2021-05-13 | 2023-09-26 | 曙光信息产业股份有限公司 | Cloud hard disk preparation method and device, computer equipment and storage medium |
| CN113821170A (en) * | 2021-08-31 | 2021-12-21 | 济南浪潮数据技术有限公司 | Distributed storage system, access method and component |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016165472A1 (en) * | 2015-07-13 | 2016-10-20 | 中兴通讯股份有限公司 | Method and device for creating virtual machine |
| CN106708430A (en) * | 2016-11-30 | 2017-05-24 | 浪潮软件集团有限公司 | Cloud hard disk implementation method under cloud computing architecture |
| CN106874214A (en) * | 2017-02-15 | 2017-06-20 | 腾讯科技（深圳）有限公司 | The recovery method and relevant apparatus of cloud hard disk resources |
| CN106886369A (en) * | 2017-01-22 | 2017-06-23 | 武汉噢易云计算股份有限公司 | A kind of cloud hard disk management method and system based on OpenStack cloud platforms |
| CN110196749A (en) * | 2018-02-26 | 2019-09-03 | 中兴通讯股份有限公司 | The restoration methods and device of virtual machine, storage medium and electronic device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10277526B2 (en) * | 2017-02-20 | 2019-04-30 | International Business Machines Corporation | Injection of information technology management process into resource request flows |
-
2019
- 2019-10-08 CN CN201910949401.4A patent/CN110795029B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016165472A1 (en) * | 2015-07-13 | 2016-10-20 | 中兴通讯股份有限公司 | Method and device for creating virtual machine |
| CN106708430A (en) * | 2016-11-30 | 2017-05-24 | 浪潮软件集团有限公司 | Cloud hard disk implementation method under cloud computing architecture |
| CN106886369A (en) * | 2017-01-22 | 2017-06-23 | 武汉噢易云计算股份有限公司 | A kind of cloud hard disk management method and system based on OpenStack cloud platforms |
| CN106874214A (en) * | 2017-02-15 | 2017-06-20 | 腾讯科技（深圳）有限公司 | The recovery method and relevant apparatus of cloud hard disk resources |
| CN110196749A (en) * | 2018-02-26 | 2019-09-03 | 中兴通讯股份有限公司 | The restoration methods and device of virtual machine, storage medium and electronic device |
Non-Patent Citations (2)
| Title |
|---|
| Sandipan Ganguly ; Ashish Consul等."A Practical Approach to Hard Disk Failure Prediction in Cloud Platforms: Big Data Model for Failure Management in Datacenters".《2016 IEEE Second International Conference on Big Data Computing Service and Applications (BigDataService)》.2016, * |
| 支持不同存储方式的OpenStack云平台设计与实现;冯伟斌等;《电信科学》;20160420(第04期);第141-145页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110795029A (en) | 2020-02-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110795029B (en) | Cloud hard disk management method, device, server and medium | |
| US10735345B2 (en) | Orchestrating computing resources between different computing environments | |
| CN109343963B (en) | Application access method and device for container cluster and related equipment | |
| US9477499B2 (en) | Managing process migration from source virtual machine to target virtual machine which are on the same operating system | |
| KR102513998B1 (en) | Communication methods and devices, entities and computer readable storage media | |
| CN109614226B (en) | Kubernetes-based stateful application storage management method | |
| US9405589B2 (en) | System and method of optimization of in-memory data grid placement | |
| US10169348B2 (en) | Using a file path to determine file locality for applications | |
| CN106951179B (en) | Data migration method and device | |
| CN104113576A (en) | Method and device for updating client | |
| CN111597148B (en) | Distributed metadata management method for distributed file system | |
| CN105045762A (en) | Management method and apparatus for configuration file | |
| US20190223051A1 (en) | Load balancing method and related device | |
| CN112463290A (en) | Method, system, apparatus and storage medium for dynamically adjusting the number of computing containers | |
| CN111124299A (en) | Data storage management method, device, equipment, system and storage medium | |
| CN109561165A (en) | Domain name system configuration method and relevant apparatus | |
| CN113760847A (en) | Log data processing method, device, equipment and storage medium | |
| JP6951846B2 (en) | Computer system and task allocation method | |
| US11144359B1 (en) | Managing sandbox reuse in an on-demand code execution system | |
| EP2629492A1 (en) | Method, switch, and system for processing a message | |
| CN111694639A (en) | Method and device for updating address of process container and electronic equipment | |
| CN106911741B (en) | Method for balancing virtual network management file downloading load and network management server | |
| US11301436B2 (en) | File storage method and storage apparatus | |
| US11210347B2 (en) | Object search with pagination and non-duplicates support | |
| KR101973946B1 (en) | Distributed computing acceleration platform |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |