CN110413584B - Data storage method, device, equipment and storage medium - Google Patents
Data storage method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN110413584B CN110413584B CN201910675356.8A CN201910675356A CN110413584B CN 110413584 B CN110413584 B CN 110413584B CN 201910675356 A CN201910675356 A CN 201910675356A CN 110413584 B CN110413584 B CN 110413584B
- Authority
- CN
- China
- Prior art keywords
- data block
- storage
- physical machine
- mounting
- data
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
-
- 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
- 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/4557—Distribution of virtual machine instances; Migration and load balancing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a data storage method, a data storage device, data storage equipment and a data storage medium, and belongs to the field of cloud computing. The data storage method comprises the following steps: creating a storage data block in a distributed file system; determining that a target carrier for mounting the storage data block is a physical machine; and converting the storage data block into a data block of a small computer system interface protocol, and mounting the data block to the physical machine. According to the method and the device, the data blocks in the distributed file system are mounted on the physical machine for being stored by a user, and the storage resources of the physical machine are not used, so that when the physical machine is offline or a disk on the physical machine is damaged, the resources stored in the data blocks cannot be lost, and the reliability of data is further effectively ensured; and then the reliability of the data can be ensured under the condition of saving the resource overhead.
Description
Technical Field
The present application relates to the field of cloud computing, and in particular, to a data storage method, apparatus, device, and storage medium.
Background
With the rapid development of cloud computing, the service is increasing continuously, the requirements on computing, network and IO (Input/Output) are higher and higher, the physical machine (bare machine) is directly used as a delivery resource, the demand is higher and higher, each cloud platform is also continuously on-line with the physical machine service, and the high-performance physical machine resource of a user is directly provided. However, the physical machine is a hardware resource, and has natural defects in data reliability and backup.
At present, three schemes of hardware raid, network raid, real-time backup and the like are mainly used for solving the reliability and the backup of direct delivery of physical machine resources of each cloud platform, however, the hardware raid increases the hardware cost, and data cannot be acquired in real time when a physical machine is down. The network raid has high requirements on the network, and has a large influence on the overall cost. The real-time backup architecture is difficult to implement and has high requirements on the network. Therefore, how to guarantee the reliability of data while saving the resource overhead.
Disclosure of Invention
In view of this, the data storage method, apparatus, device and storage medium provided in the embodiments of the present application can ensure reliability of data while saving resource overhead.
In a first aspect, an embodiment of the present application provides a data storage method, where the method includes: creating a storage data block in a distributed file system; determining that a target carrier for mounting the storage data block is a physical machine; and converting the storage data block into a data block of a small computer system interface protocol, and mounting the data block to the physical machine.
In the implementation process, because the data blocks in the distributed file system are mounted on the physical machine for storage by a user without using the storage resources of the physical machine, the resources stored in the data blocks can still not be lost when the physical machine is offline or a disk on the physical machine is damaged, and the reliability of the data is further effectively ensured; and then the reliability of the data can be ensured under the condition of saving the resource overhead.
With reference to the first aspect, an embodiment of the present application provides a first possible implementation manner of the first aspect, where the converting the storage data block into a data block of a small computer system interface protocol includes: and converting the block storage service protocol of the storage data block into a data block of the small computer system interface protocol through the small computer system interface gateway.
In the implementation process, the protocol conversion is carried out on the storage data blocks, and the data blocks after the protocol conversion are mounted on the physical machines, so that on one hand, each physical machine can only see the data blocks mounted by itself, but cannot see other data blocks which are not mounted on the physical machine, the isolation of data is effectively realized, and the safety of the data is ensured; on the other hand, because the data blocks in the distributed file system are mounted on the physical machine for storage by the user without using the storage resources of the physical machine, the resources stored in the data blocks can still not be lost when the physical machine is offline or the disk on the physical machine is damaged, and the reliability of the data is further effectively ensured; furthermore, the technical problems of inflexibility and difficulty in backup of local storage of the physical machine are solved.
With reference to the first aspect, an embodiment of the present application provides a second possible implementation manner of the first aspect, where determining that the target carrier on which the storage data block is mounted is a physical machine includes: acquiring a mounting instruction input by a user; and determining that the target carrier for mounting the storage data block is the physical machine according to the mounting instruction.
In the implementation process, a mounting instruction input by a user is obtained; and determining the target carrier mounted with the storage data block as the physical machine according to the mounting instruction, thereby accurately determining the target carrier.
With reference to any one implementation manner of the first aspect to the second possible implementation manner of the first aspect, an embodiment of the present application provides a third possible implementation manner of the first aspect, and the method further includes: acquiring an unloading instruction input by a user; unloading the data block corresponding to the unloading instruction on the physical machine; and returning the unloaded data blocks to the distributed file system in a state to be used.
In the implementation process, the data blocks are unloaded from the target carrier by acquiring the unloading instruction input by the user, so that the data blocks return to the distributed file system again, and the resource reuse rate is further improved.
With reference to the third possible implementation manner of the first aspect, an embodiment of the present application provides a fourth possible implementation manner of the first aspect, and the method further includes: determining that a target carrier mounting the storage data block is a virtual machine; and mounting the storage data block to the virtual machine.
In the implementation process, the data sharing between the physical machine and the virtual machine can be realized by mounting the storage data blocks unloaded from the physical machine to the virtual machine.
In a second aspect, an embodiment of the present application provides a data storage device, where the device includes: a creating unit for creating a storage data block in the distributed file system; the processing unit is used for determining that a target carrier for mounting the storage data block is a physical machine; and the first mounting unit is used for converting the storage data block into a data block of a small computer system interface protocol and mounting the data block to the physical machine.
With reference to the second aspect, an embodiment of the present application provides a first possible implementation manner of the second aspect, where the first mounting unit is further configured to: if the block storage service protocol of the storage data block is converted into the data block of the small computer system interface protocol through the small computer system interface gateway.
With reference to the second aspect, an embodiment of the present application provides a second possible implementation manner of the second aspect, where the processing unit is further configured to: acquiring a mounting instruction input by a user; and determining that the target carrier for mounting the storage data block is the physical machine according to the mounting instruction.
With reference to any one implementation manner of the second possible implementation manner of the second aspect to the second possible implementation manner of the second aspect, in an embodiment of the present application, the apparatus further includes an unloading unit, configured to: acquiring an unloading instruction input by a user; unloading the data block corresponding to the unloading instruction on the physical machine; and returning the unloaded data blocks to the distributed file system in a state to be used.
With reference to the second aspect, the present application provides a fourth possible implementation manner of the second aspect, where the apparatus further includes: a second mounting unit for: determining that a target carrier mounting the storage data block is a virtual machine; and mounting the storage data block to the virtual machine.
In a third aspect, an electronic device provided in an embodiment of the present application includes: a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the data storage method according to any one of the first aspect when executing the computer program.
In a fourth aspect, an embodiment of the present application provides a storage medium, on which instructions are stored, and when the instructions are executed on a computer, the instructions cause the computer to execute the data storage method according to any one of the first aspect.
In a fifth aspect, an embodiment of the present application provides a computer program product, which when run on a computer, causes the computer to execute the data storage method according to any one of the first aspect.
Additional features and advantages of the disclosure will be set forth in the description which follows, or in part may be learned by the practice of the above-described techniques of the disclosure, or may be learned by practice of the disclosure.
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 is a flowchart of a data storage method according to an embodiment of the present application;
fig. 2 is an application scenario diagram of a data storage method according to an embodiment of the present application;
FIG. 3 is a flow chart of another data storage method provided by an embodiment of the present application;
fig. 4 is a schematic structural diagram of a data storage device according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The above-mentioned drawbacks of the prior art are considered by the applicant to be the result of practical and careful study, and therefore, the discovery process of the above-mentioned problems and the solutions proposed by the embodiments of the present application in the following description should be the contribution of the applicant to the present application in the course of the present application.
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
Some embodiments of the present application will be described in detail below with reference to the accompanying drawings. The embodiments described below and the features of the embodiments can be combined with each other without conflict.
Referring to fig. 1, which is a flowchart of a data storage method provided in an embodiment of the present application, it should be understood that the method shown in fig. 1 may be executed by a data storage device, where the data storage device may correspond to the electronic device shown in fig. 5, which may be various devices capable of executing the method, such as a computer or a server, for example, and the embodiment of the present application is not limited thereto, and specifically includes the following steps:
step S101, creating a storage data block in the distributed file system.
Alternatively, the storage data block may also be referred to as disk. The storage data block is used to provide a storage space. For example, the capacity of the memory data block may be 1GB, 2GB, or the like. Here, the number of the carbon atoms is not particularly limited.
Alternatively, the storage data block may be created by a user in the distributed file system Ceph. Such as where a user may create blocks of storage data of different sizes in a distributed file system as desired. For example, after a user logs in the cloud platform, an instruction for creating a storage data block is input, and a background (storage service) creates a corresponding storage data block according to the instruction input by the user.
It is to be understood that the above examples are illustrative only and not limiting.
Optionally, the storage service is a service for managing storage, and is mainly used for managing storage data blocks of the distributed file system, and can also be used for mounting the storage data blocks to the virtual machine.
Optionally, the storage service may be deployed on the cloud platform, or may be deployed on a server independently, and the server may communicate with the cloud platform. Here, the number of the carbon atoms is not particularly limited.
Of course, in actual use, the storage data block may be created in advance by a developer. Here, the number of the carbon atoms is not particularly limited.
And step S102, determining a target carrier for mounting the storage data block.
Optionally, the object carrier comprises a physical machine.
As an embodiment, step S102 includes: acquiring a mounting instruction input by a user; and determining that the target carrier for mounting the storage data block is the physical machine according to the mounting instruction.
Optionally, the mount instruction includes a physical machine to be mounted with the storage data block. I.e., a mount instruction, is used to instruct that the storage data block be mounted on a physical machine.
As an application scenario, after creating a storage data block, a user may specify to mount a certain storage data block on a physical machine.
As another application scenario, the user may select to mount a certain storage data block or a certain number of storage data blocks on the physical machine 1 on the operation interface. Of course, the user may mount a plurality of storage data blocks on different physical machines. For example, the storage data block 1 is designated to be mounted on the physical machine 1, the storage data block 2 is designated to be mounted on the physical machine 2, and the storage data block 10 is designated to be mounted on the physical machine 5.
As another implementation scenario, a user may input a series of mounting parameters, and a background generates a mounting instruction after monitoring the mounting parameters input by the user, so as to determine a target carrier on which the storage data block is mounted through the mounting instruction.
In the implementation process, a mounting instruction input by a user is obtained; and determining the target carrier mounted with the storage data block as the physical machine according to the mounting instruction, thereby accurately determining the target carrier.
And step S103, converting the storage data block into a data block of a small computer system interface protocol, and mounting the data block to the physical machine.
Optionally, converting the storage data block into a data block of a small computer system interface protocol, including: a block storage service protocol rbd for storing data blocks is converted into data blocks of an Small Computer System Interface protocol (iSCSI) through an SCSI gateway.
As an implementation scenario, the cloud platform includes a storage gateway, and the storage service is in communication with the storage gateway, and the storage gateway is configured to convert the storage data block into a data block of a small computer system interface protocol, and further configured to mount the data block to the physical machine.
Optionally, the storage gateway may be deployed on a cloud platform, or may be deployed independently. Here, the number of the carbon atoms is not particularly limited.
It should be understood that mounting in this application refers to mapping a data block onto a physical machine, rather than mounting the data block on the physical machine. Namely, the data blocks are mounted on the physical machine through the mapping relation between the data blocks and the physical machine, so as to be used by a user.
Alternatively, the mapping relationship may be generated based on a mount instruction input by a user.
In the implementation process, the protocol conversion is carried out on the storage data blocks, and the data blocks after the protocol conversion are mounted on the physical machines, so that on one hand, each physical machine can only see the data blocks mounted by itself, but cannot see other data blocks which are not mounted on the physical machine, the isolation of data is effectively realized, and the safety of the data is ensured; on the other hand, because the data blocks in the distributed file system are mounted on the physical machine for storage by the user without using the storage resources of the physical machine, the resources stored in the data blocks can still not be lost when the physical machine is offline or the disk on the physical machine is damaged, and the reliability of the data is further effectively ensured; furthermore, the technical problems of inflexibility and difficulty in backup of local storage of the physical machine are solved.
In a possible embodiment, the method further comprises: acquiring an unloading instruction input by a user; unloading the data block corresponding to the unloading instruction on the physical machine; and returning the unloaded data blocks to the distributed file system in a state to be used.
Optionally, the uninstall instruction includes a data block to be uninstalled and a physical machine on which the data block is mounted. For example, the user inputs an unload instruction to unload the data block N from the physical machine 2, so that the data block N is unloaded from the physical machine 2 according to the unload instruction.
It is to be understood that the above examples are illustrative only and not limiting.
Optionally, the offload instruction is used to break the mapping between the data blocks and the target carrier, thereby causing the data blocks to revert to the distributed file system.
It should be appreciated that the stored content in the data blocks that are returned to the distributed file system is unchanged.
Optionally, returning the unloaded data block to the distributed file system in a state to be used includes: the unloaded data block is converted into a storage data block through a protocol; and storing the data block to be used and returning to the distributed file system.
Alternatively, the data block may be mounted on the virtual machine after being unloaded from the physical machine.
In the implementation process, the data blocks are unloaded from the target carrier by acquiring the unloading instruction input by the user, so that the data blocks return to the distributed file system again, and the resource reuse rate is further improved.
Alternatively, data blocks unloaded from the physical machine may be automatically mounted onto the virtual machine after being returned to the distributed file system.
In a possible embodiment, the object carrier further comprises a virtual machine, and the method further comprises: and mounting the storage data block to the virtual machine.
Optionally, the virtual machine is deployed on a physical machine, and the virtual machine itself is isolated from the physical machine.
In the implementation process, the data sharing between the physical machine and the virtual machine can be realized by mounting the storage data blocks unloaded from the physical machine to the virtual machine.
As an application scenario, when a physical machine and a virtual machine exist at the same time, a mounting target is determined by monitoring a mounting instruction input by a user, and if the mounting target is the physical machine, a storage data block is mounted on the physical machine. And if the mounting target is the virtual machine, mounting the storage data block on the virtual machine.
Of course, in actual use, the storage data block mounted on the virtual machine may also be unloaded, and the unloading process may refer to the above process of unloading the data block from the physical machine, which is not described herein again.
Of course, after the data blocks unloaded from the physical machine are returned to the distributed file system, the storage data blocks can be mounted on the virtual machine after the mounting instruction of the user is monitored. Specifically, the method comprises the following steps:
in a possible embodiment, the method further comprises: determining that a target carrier for mounting the storage data block is a virtual machine, and mounting the storage data block to the virtual machine.
As an application scenario, after a user unloads a data block F mounted on a physical machine, the data block F is converted into a storage data block F through a protocol and returned to a distributed file system, and when it is monitored that the user needs to mount the storage data block F on a virtual machine, the storage data block F is mounted on the virtual machine.
Of course, in actual use, the user may also choose not to mount the storage data block F on the virtual machine. For example, the user may also choose to mount the storage data block G on the virtual machine.
Of course, in actual use, the data blocks unloaded from the physical machine can be subsequently re-mounted on the physical machine. Here, the number of the carbon atoms is not particularly limited.
The data storage method in the embodiment of the present application is described above with reference to fig. 1, and the data storage method in the embodiment of the present application is described in detail below, by way of example and without limitation, with reference to fig. 2 and 3. Specifically, the method shown in fig. 3 includes:
in step S201, a storage data block is created.
Optionally, the storage data block is created by a storage service. For a specific implementation of step S201, reference may be made to the above description.
Step S202, a volume pool is formed.
Alternatively, a volume pool refers to a collection of multiple storage data blocks.
In step S203, the virtual machine is mounted on the physical machine or the virtual machine.
Alternatively, whether to mount on the physical machine or the virtual machine is determined by a mount instruction input by a user. For a specific implementation of step S203, reference may be made to the above description.
Alternatively, step S204 is executed if the virtual machine is mounted, and step S207 is executed if the physical machine is mounted.
Step S204, converting into a data block of the small computer system interface protocol.
In one embodiment, the storage gateway translates the storage data blocks into data blocks of a small computer system interface protocol.
Alternatively, if mounted to a physical machine, it is converted into a data block of the SCSI protocol. For a specific implementation of step S204, reference may be made to the above description.
And step S205, mounting to a physical machine.
That is, the data block translated into the small computer system interface protocol is mounted to the physical machine.
In one embodiment, the storage gateway mounts the data blocks translated into the SCSI protocol to the physical machine.
Alternatively, the specific implementation of step S205 may refer to the above description.
And step S206, unloading the data block from the physical machine.
Optionally, step S206, includes: acquiring an unloading instruction input by a user; unloading the data block corresponding to the unloading instruction on the physical machine; and returning the unloaded data blocks to the distributed file system in a state to be used. For a specific implementation of step S206, reference may be made to the above description.
And step S207, mounting to the virtual machine.
Namely, if the storage data block is mounted to the virtual machine, the storage data block is directly mounted to the virtual machine.
As one embodiment, the storage service mounts the storage data block directly onto the virtual machine.
Alternatively, the specific implementation of step S207 may refer to the above description.
And step S208, unloading the data block from the virtual machine.
As one embodiment, a storage service offloads blocks of data from a virtual machine.
Alternatively, the detailed implementation of step S208 may refer to the description of step S206.
According to the data storage method provided by the embodiment of the application, the storage data block is established in the distributed file system; determining that a target carrier for mounting the storage data block is a physical machine; and converting the storage data block into a data block of a small computer system interface protocol, and mounting the data block to the physical machine. On one hand, each physical machine can only see the data block mounted by the physical machine, but cannot see other data blocks which are not mounted on the physical machine, so that the data isolation is effectively realized, and the data security is ensured; on the other hand, in the application, the data blocks in the distributed file system are mounted on the physical machine for storage by a user, and the storage resources of the physical machine are not used, and the data blocks mounted on the physical machine are not actually stored on the physical machine but only have a logical relationship with the physical machine, so that the resources stored in the data blocks can not be lost when the physical machine is offline or a disk on the physical machine is damaged, and the reliability of data is further effectively ensured; and then the reliability of the data can be ensured under the condition of saving the resource overhead.
Referring to fig. 4, fig. 4 shows a data storage device corresponding to the data storage method shown in fig. 1, it should be understood that the device 300 corresponds to the method embodiment shown in fig. 1, and can perform the steps related to the method embodiment, and the specific functions of the device 300 can be referred to the description above, and the detailed description is omitted here as appropriate to avoid repetition. The device 300 includes at least one software functional module that can be stored in a memory in the form of software or firmware (firmware) or solidified in an Operating System (OS) of the device 300. Specifically, the apparatus 300 includes:
a creating unit 310, configured to create a storage data block in the distributed file system;
the processing unit 320 is configured to determine that the target carrier on which the storage data block is mounted is a physical machine;
the first mounting unit 330 is configured to convert the storage data block into a data block of an scsi protocol, and mount the data block to the physical machine.
Optionally, the first mounting unit 330 is further configured to: if the object carrier is the physical machine, converting the block storage service protocol of the storage data block into a data block of a small computer system interface protocol through a small computer system interface gateway.
Optionally, the processing unit 320 is further configured to: acquiring a mounting instruction input by a user; and determining that the target carrier for mounting the storage data block is the physical machine according to the mounting instruction.
In a possible embodiment, the apparatus 300 further comprises: an unloading unit for: acquiring an unloading instruction input by a user; unloading the data block corresponding to the unloading instruction on the physical machine; and returning the unloaded data blocks to the distributed file system in a state to be used.
In a possible embodiment, the apparatus 300 further comprises: a second mounting unit for: determining that a target carrier mounting the storage data block is a virtual machine; and mounting the storage data block to the virtual machine.
Fig. 5 is a block diagram of an electronic device 500 in an embodiment of the present application, as shown in fig. 5. Electronic device 500 may include a processor 510, a communication interface 520, a memory 530, and at least one communication bus 540. Wherein the communication bus 540 is used for realizing direct connection communication of these components. The communication interface 520 of the device in the embodiment of the present application is used for performing signaling or data communication with other node devices. Processor 510 may be an integrated circuit chip having signal processing capabilities.
The Processor 510 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; but may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor 510 may be any conventional processor or the like.
The Memory 530 may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Read-Only Memory (EPROM), an electrically Erasable Read-Only Memory (EEPROM), and the like. The memory 530 stores computer readable instructions that, when executed by the processor 510, enable the electronic device 500 to perform the steps associated with the method embodiment of fig. 1 described above.
The electronic device 500 may also include a memory controller.
The memory 530, memory controller, and processor 510 are electrically connected to each other directly or indirectly to enable data transmission or interaction. For example, these elements may be electrically coupled to each other via one or more communication buses 540. The processor 510 is used to execute executable modules stored in the memory 530, such as software functional modules or computer programs included in the apparatus 300. Also, the apparatus 300 is configured to perform the following method: creating a storage data block in a distributed file system; determining that a target carrier for mounting the storage data block is a physical machine; and converting the storage data block into a data block of a small computer system interface protocol, and mounting the data block to the physical machine.
Alternatively, the electronic device 500 may be a computer, or may also be a device such as a server or a cloud server.
It will be appreciated that the configuration shown in FIG. 5 is merely illustrative and that the electronic device 500 may include more or fewer components than shown in FIG. 5 or may have a different configuration than shown in FIG. 5. The components shown in fig. 5 may be implemented in hardware, software, or a combination thereof.
The embodiment of the present application further provides a storage medium, where the storage medium stores instructions, and when the instructions are run on a computer, when the computer program is executed by a processor, the method in the method embodiment is implemented, and in order to avoid repetition, details are not repeated here.
The present application also provides a computer program product which, when run on a computer, causes the computer to perform the method of the method embodiments.
From the above description of the embodiments, it is clear to those skilled in the art that the present application can be implemented by hardware, or by software plus a necessary general hardware platform, and based on such understanding, the technical solution of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a usb disk, a removable hard disk, etc.), and includes several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the method of the various implementation scenarios of the present application.
The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
Claims (8)
1. A method of data storage, the method comprising:
creating a storage data block in a distributed file system; the storage data block is used for providing a storage space;
determining that a target carrier for mounting the storage data block is a physical machine;
converting the storage data block into a data block of a small computer system interface protocol, and mounting the data block to the physical machine;
the method further comprises the following steps:
acquiring an unloading instruction input by a user;
unloading the data block corresponding to the unloading instruction on the physical machine;
returning the unloaded data blocks to the distributed file system in a state to be used;
automatically mounting the unloaded data blocks onto a virtual machine; the virtual machine is deployed on a physical machine, and the virtual machine itself is isolated from the physical machine.
2. The method of claim 1, wherein converting the stored data block into a data block of a small computer system interface protocol comprises:
and converting the block storage service protocol of the storage data block into a data block of the small computer system interface protocol through the small computer system interface gateway.
3. The method of claim 1, wherein determining that the target carrier on which the block of storage data is mounted is a physical machine comprises:
acquiring a mounting instruction input by a user;
and determining that the target carrier for mounting the storage data block is a physical machine according to the mounting instruction.
4. A data storage device, characterized in that the device comprises:
a creating unit for creating a storage data block in the distributed file system; the storage data block is used for providing a storage space;
the processing unit is used for determining that a target carrier for mounting the storage data block is a physical machine;
the first mounting unit is used for converting the storage data block into a data block of a small computer system interface protocol and mounting the data block to the physical machine;
the device further comprises:
the unloading unit is used for acquiring an unloading instruction input by a user, unloading a data block corresponding to the unloading instruction on the physical machine, and returning the unloaded data block to the distributed file system in a to-be-used state;
the second mounting unit is used for automatically mounting the unloaded data blocks onto the virtual machine; the virtual machine is deployed on a physical machine, and the virtual machine itself is isolated from the physical machine.
5. The apparatus of claim 4, wherein the first mounting unit is further configured to:
and converting the block storage service protocol of the storage data block into a data block of the small computer system interface protocol through the small computer system interface gateway.
6. The apparatus of claim 4, wherein the processing unit is further configured to:
acquiring a mounting instruction input by a user;
and determining that the target carrier for mounting the storage data block is the physical machine according to the mounting instruction.
7. An electronic device, comprising: memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the data storage method according to any one of claims 1 to 3 when executing the computer program.
8. A storage medium for storing instructions which, when executed on a computer, cause the computer to perform a data storage method as claimed in any one of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910675356.8A CN110413584B (en) | 2019-07-24 | 2019-07-24 | Data storage method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910675356.8A CN110413584B (en) | 2019-07-24 | 2019-07-24 | Data storage method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110413584A CN110413584A (en) | 2019-11-05 |
| CN110413584B true CN110413584B (en) | 2021-04-02 |
Family
ID=68363020
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910675356.8A Active CN110413584B (en) | 2019-07-24 | 2019-07-24 | Data storage method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110413584B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114579036B (en) * | 2020-11-30 | 2024-02-13 | 北京达佳互联信息技术有限公司 | Storage device management method and related device |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103747064A (en) * | 2013-12-26 | 2014-04-23 | 广东中科遥感技术有限公司 | Mounting method, client and system based on MooseFS distributed file system |
| CN104506589A (en) * | 2014-12-10 | 2015-04-08 | 上海爱数软件有限公司 | Resource migration scheduling method based on super fusion storage |
| CN105892943A (en) * | 2016-03-30 | 2016-08-24 | 上海爱数信息技术股份有限公司 | Access method and system for block storage data in distributed storage system |
| US9942271B2 (en) * | 2005-12-29 | 2018-04-10 | Nextlabs, Inc. | Information management system with two or more interactive enforcement points |
| CN108170513A (en) * | 2017-12-28 | 2018-06-15 | 上海优刻得信息科技有限公司 | Method, apparatus, system and the storage medium of carry are carried out to network disk |
| CN109697020A (en) * | 2017-10-23 | 2019-04-30 | 中移(苏州)软件技术有限公司 | A kind of date storage method, server and system |
| US10346188B1 (en) * | 2014-06-13 | 2019-07-09 | Veritas Technologies Llc | Booting virtual machine instances in a distributed data processing architecture |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103475732A (en) * | 2013-09-25 | 2013-12-25 | 浪潮电子信息产业股份有限公司 | Distributed file system data volume deployment method based on virtual address pool |
| CN103618767B (en) * | 2013-11-15 | 2017-01-18 | 华为技术有限公司 | Virtual machine configuration method and related equipment |
-
2019
- 2019-07-24 CN CN201910675356.8A patent/CN110413584B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9942271B2 (en) * | 2005-12-29 | 2018-04-10 | Nextlabs, Inc. | Information management system with two or more interactive enforcement points |
| CN103747064A (en) * | 2013-12-26 | 2014-04-23 | 广东中科遥感技术有限公司 | Mounting method, client and system based on MooseFS distributed file system |
| US10346188B1 (en) * | 2014-06-13 | 2019-07-09 | Veritas Technologies Llc | Booting virtual machine instances in a distributed data processing architecture |
| CN104506589A (en) * | 2014-12-10 | 2015-04-08 | 上海爱数软件有限公司 | Resource migration scheduling method based on super fusion storage |
| CN105892943A (en) * | 2016-03-30 | 2016-08-24 | 上海爱数信息技术股份有限公司 | Access method and system for block storage data in distributed storage system |
| CN109697020A (en) * | 2017-10-23 | 2019-04-30 | 中移(苏州)软件技术有限公司 | A kind of date storage method, server and system |
| CN108170513A (en) * | 2017-12-28 | 2018-06-15 | 上海优刻得信息科技有限公司 | Method, apparatus, system and the storage medium of carry are carried out to network disk |
Non-Patent Citations (2)
| Title |
|---|
| DHTbd: A Reliable Block-Based Storage System for High Performance Clusters;George Parisis et al;《2011 11th IEEE/ACM International Symposium on Cluster, Cloud and Grid Computing》;20110712;第392-401页 * |
| 面向虚拟机的分布式块存储系统设计及实现;贾博文 等;《微型电脑应用》;20150331;第31卷(第3期);第32-37页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110413584A (en) | 2019-11-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210216360A1 (en) | Virtual machine migration method and apparatus | |
| US10002054B2 (en) | Method and system for performing automatic system recovery | |
| US11748091B2 (en) | Virtualization platform for creating, deploying, modifying, and relocating applications | |
| US20160378525A1 (en) | Technologies for application migration using lightweight virtualization | |
| CN106886434B (en) | Distributed application installation method and device | |
| US10613847B2 (en) | Information handling system to treat demoted firmware with replacement firmware | |
| CN109684038B (en) | Docker service container log processing method and device and electronic equipment | |
| US9378122B2 (en) | Adopting an existing automation script to a new framework | |
| US20180189089A1 (en) | Virtual machine image conversion | |
| CN106406980B (en) | A kind of dispositions method and device of virtual machine | |
| CN111181787A (en) | BMC parameter configuration method, device, equipment and medium | |
| CN111143031A (en) | Method and device for changing capacity of virtual machine | |
| CN110413584B (en) | Data storage method, device, equipment and storage medium | |
| US10572151B2 (en) | System and method to allocate available high bandwidth memory to UEFI pool services | |
| US11631011B2 (en) | Automatically remediating storage device issues using machine learning techniques | |
| CN111444074A (en) | Data monitoring method and device, electronic equipment and readable storage medium | |
| CN111045783A (en) | Method and device for generating container mirror image, storage medium and electronic equipment | |
| CN115291973A (en) | Method and device for connecting database by application on cloud, electronic equipment and storage medium | |
| CN115016862A (en) | Kubernetes cluster-based software starting method, device, server and storage medium | |
| US11675602B2 (en) | Methods and systems for creating root-of-trust for computing system components | |
| CN114296747A (en) | Installation method and device of software installation package | |
| CN108920628B (en) | Distributed file system access method and device adaptive to big data platform | |
| CN110049065B (en) | Attack defense method, device, medium and computing equipment of security gateway | |
| US20160191320A1 (en) | Relocating an embedded cloud for fast configuration of a cloud computing environment | |
| US20200326976A1 (en) | Operating cluster computer system with coupling facility |
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 | ||
| CB02 | Change of applicant information |
Address after: No. 6 Science and Education Software Park, Binhu District, Wuxi City, Jiangsu Province Applicant after: Huayun data holding group Co., Ltd Address before: No. 6 Science and Education Software Park, Binhu District, Wuxi City, Jiangsu Province Applicant before: WUXI CHINAC DATA TECHNICAL SERVICE Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |