CN117406921A - Method for modifying type of mounted volume - Google Patents

Method for modifying type of mounted volume Download PDF

Info

Publication number
CN117406921A
CN117406921A CN202311294477.0A CN202311294477A CN117406921A CN 117406921 A CN117406921 A CN 117406921A CN 202311294477 A CN202311294477 A CN 202311294477A CN 117406921 A CN117406921 A CN 117406921A
Authority
CN
China
Prior art keywords
volume
type
qos
modification
modifying
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.)
Pending
Application number
CN202311294477.0A
Other languages
Chinese (zh)
Inventor
宋洪圆
谢涛涛
宋伟
申嘉童
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Inspur Cloud Information Technology Co Ltd
Original Assignee
Inspur Cloud Information Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Inspur Cloud Information Technology Co Ltd filed Critical Inspur Cloud Information Technology Co Ltd
Priority to CN202311294477.0A priority Critical patent/CN117406921A/en
Publication of CN117406921A publication Critical patent/CN117406921A/en
Pending legal-status Critical Current

Links

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/0629—Configuration or reconfiguration of storage systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23—Updating
    • 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/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/061—Improving I/O performance
    • 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/0647—Migration mechanisms
    • 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
    • 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/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
    • 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/45595—Network integration; Enabling network access in virtual machine instances

Abstract

The invention relates in particular to a method of modifying the type of mounted volume. According to the method for modifying the mounted volume type, a storage service judges whether a volume back end pool and associated QoS configuration have differences according to volume type information before and after modification; for the condition that the storage pool resources at the back end of the volume are consistent and QoS configuration parameters are completely consistent, or the volume types are not associated with QoS, directly calling a storage component to realize volume type modification; for a volume with a change of a back-end pool stored before and after the volume type modification, or a volume with a consistent volume type association of the back-end pool and a difference of volume type association QoS configuration, a calculation component is called, a calculation service calls a calculation-driven setblockIoTune logic, and the QoS configuration of the volume mounted to the virtual machine is modified in real time; and calling a computing drive blockCopy logic to complete volume copy. The method for modifying the type of the mounted volume greatly expands the applicable scene of volume back-end change and upgrade, improves the performance and IOPS of the mounted volume, and realizes the possibility of storing the back-end with higher rate limit.

Description

Method for modifying type of mounted volume
Technical Field
The invention relates to the technical field of cloud computing, in particular to a method for modifying the type of a mounted volume.
Background
With the development of cloud technology, more enterprises and public institutions and individuals migrate traditional applications to a cloud data center, and an OpenStack is used as a cloud platform to provide IAAS (Infrastructure-as-a-Service) layer virtual machine management function for vast users, which has become one of the mainstream cloud technologies.
In the field of cloud computing storage, all cloud storage volumes are storage resources that are abstracted from physical hardware. The cloud storage is generally divided into block storage, object storage and file storage, wherein the block storage is block equipment storage which is provided for a cloud server and can be randomly read and written randomly, and the cloud storage has the characteristics of lasting storage, high reliability and low time delay. Generally, according to different storage back ends, cloud manufacturers provide cloud disks with different types and performances, and each storage back end has different performance index limits due to different characteristics, and is generally defined by QoS (Quality of Service ). Volume QoS allows hardware device level performance limitations to be defined for each volume. In a storage service, by defining a volume type, a storage backend of a volume can be specified; by defining the volume QoS, the read-write IOPS (Input/Output Operations Per Second), i.e. the number of read-write (I/O) operations per second, and read-write bytes restrictions can be specified, and finally the volume type and the volume QoS are associated, so that the storage backend and the performance restriction parameters can be bound. Volumes in the cloud platform can be created corresponding to backend and performance parameter limitations by only specifying the corresponding volume type.
For volumes in the OpenStack cloud computing platform built based on KVM (Keyboard Video Mouse) and QEMU (virtual operating system simulator), a volume type (re-import) operation is supported, i.e., the volumes are modified to different volume types. The type operation mainly involves the Cinder block store and Nova component in the platform. The Cinder block storage mainly provides storage capacity for the cloud platform, and operations related to volumes are mainly completed in the Cinder; nova provides computing power for the cloud platform, and operations related to virtual machines are mainly completed in Nova.
The retrype is also performed for volumes to be retried, which are classified into volumes that are not mounted to the virtual machine, and volumes that have been mounted to the virtual machine. At present, for the OpenStack cloud platform, only volume type modification is supported among the non-mounted volumes configured for the same QoS, and for the volumes mounted to the virtual machine, if the volume type QoS configurations are different, the volume type change cannot be performed.
As the storage back-end increases in the cloud environment, more and more high-performance storage devices and back-ends are introduced into the environment, different volume types of the back-end generally have different QoS constraint parameters, which causes QoS to be an operation bottleneck for modifying the volume types. There is a need for a method to update the performance limit parameters of a used volume in real time as the volume type is modified, to implement the function of modifying a mounted volume to a different QoS volume type.
Based on the above situation, the present invention proposes a method of modifying the type of mounted volume.
Disclosure of Invention
The invention provides a simple and efficient method for modifying the type of the mounted volume in order to make up the defects of the prior art.
The invention is realized by the following technical scheme:
a method of modifying a mounted volume type, characterized by: the method comprises the following steps:
step S1: storage service volume type and QoS configuration check
After receiving the volume type modification request, the storage service judges whether the volume back-end pool and the associated QoS configuration have differences according to the volume type information before and after modification;
step S2: storage drive volume type modification
For the condition that the storage pool resources at the back end of the volume are consistent and QoS configuration parameters are completely consistent, or the volume types are not associated with QoS, directly calling a retrype logic driven by a storage component, and updating database information to realize volume type modification;
step S3: computing drive volume QoS configuration real-time modification
For a volume with a change of a back-end pool before and after volume type modification, or a volume with a consistent volume type association but a difference of volume type association QoS configuration, a calculation component is called, calculation-driven setB lock IoTune logic is called by a calculation service, and the QoS configuration of the volume mounted to the virtual machine is modified in real time;
step S4: computing drive volume copy
And calling a computing drive block copy logic to complete volume copy.
The method for modifying the type of the mounted volume firstly releases the limit of changing the volume mounted to the virtual machine into the volume type with different QoS attribute in the CInder component API (application program interface), and allows the volume type of the volume to be executed mounted to the virtual machine to be modified.
According to the method for modifying the mounted volume type, logic for configuring IO restriction is added in a Nova component, relevant configuration parameters of the volume type QoS are modified in a computing component Nova, the parameters comprise IO performance restriction parameters, a lasting modification identifier and a real-time modification identifier, and the Nova component is called to realize the function of modifying the volume QoS at the front end.
In step S3, the computing component invokes the Libvirt backend interface to modify the IO performance limitation parameters of the volume device mounted to the virtual machine in real time.
In the step S3, in the computing component, when the OpenStack cloud computing platform built based on the KVM and QEMU uses Libvirt as the virtual machine management program, by calling the Libvirt existing interface setlockiotune, the QoS configuration is modified in real time for the dev device already mounted to the virtual machine at the front end.
When the Libvirt component and the virtual operating system simulator QEMU use high versions and virtual machine QEMU processes load virtual machine mounted volume equipment in a blockdev mode, the Libvirt component provides a virDomainBlockcopy interface and supports QEMU to copy remote storage volume equipment.
In the step S4, the computing driver encapsulates the virDomainBlockCopy interface through a definition model, and calls the virDomainBlockCopy interface after the QoS modification is completed, so that the data copying of the volume device between different storage back ends can be completed, the migration of the volume in different storage pools is realized, after the migration is completed, the end task module is called, the device task state is modified, and the volume type modification is completed.
An apparatus for modifying the type of mounted volume, characterized by: comprising a memory and a processor; the memory is used for storing a computer program, and the processor is used for implementing the method steps described above when executing the computer program.
A readable storage medium, characterized by: the readable storage medium has stored thereon a computer program which, when executed by a processor, implements the method steps as described above.
The beneficial effects of the invention are as follows: the method for modifying the type of the mounted volume greatly expands the applicable scene of volume back-end change and upgrade, improves the performance and IOPS of the mounted volume, and realizes the possibility of storing the back-end with higher rate limit.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of the use scenario of the present invention for a mounted volume modified to a different QoS volume type.
FIG. 2 is a flow chart illustrating a modification of the type of a mounted volume according to the present invention.
Detailed Description
In order to enable those skilled in the art to better understand the technical solution of the present invention, the following description will make clear and complete description of the technical solution of the present invention in combination with the embodiments of the present invention. It will be apparent that the described embodiments are only some, but not all, embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.
The QoS-differentiated retrype discussed herein is merely a scenario where the front end modifies QoS, i.e., by KVM and QEMU. Regarding the back-end configuration QoS, storage and devices are not discussed herein. Different volume types are contemplated herein as being different only in the back end, or different in QoS attributes among the volume types, or volume type from a volume type configured with QoS attributes to a volume type not configured with QoS, and volume type from a volume type not configured with QoS attributes to a volume type configured with QoS, provided that the conditions are one different, i.e., representing the volume type being different.
A use scenario in which volumes that have been mounted to a virtual machine are modified to different QoS volume types is presented in fig. 1. As shown, virtual machine vm01 mounts two volumes, volume01 and volume 02. Taking volume01 as an example, volume01 volume uses a volume type of type01, is stored in a shared storage ceph pool01 pool, and is configured with a performance limit QoS01. The volume type of volume01 volume is now supported to be modified to either type02 (with different performance limitations QoS02 configured, same ceph storage backend, same pool 01) or type03 (with different performance limitations QoS02 configured, same ceph storage backend, different pool 02) or type04 (with different performance limitations QoS02 configured, different storage backend-SAN exemplified, different pool 03).
The method for modifying the type of the mounted volume comprises the following steps:
step S1: storage service volume type and QoS configuration check
After receiving the volume type modification request, the storage service judges whether the volume back-end pool and the associated QoS configuration have differences according to the volume type information before and after modification;
for volumes in an OpenStack-based cloud platform, either the un-mounted state or the mounted state, are created by volume type. The volume type identifies the backend of the volume storage, typically for block storage, the volume data is stored into the ceph distributed storage system, FCSAN (storage area network) or local LVM (Logical Volume Manager, logical volume management). At the same time, each back-end is divided into a plurality of storage pools.
Taking ceph distributed storage system as an example, according to different types of physical disks, the storage system can be divided into resource pools such as SSD (solid state disk), SAS (serial attached SCSI), SATA (serial attached SCSI) and the like, and further refined into the storage pool. Therefore, each resource pool may be configured with different performance limiting parameters, i.e. QoS, due to different storage media and user requirements, and the OpenStack-based cloud platform uses volume QoS to identify QoS resources and support binding to different volume types, so as to implement resource performance limitation of the back-end storage pool of the free configuration volume.
When a volume mounted on a virtual machine executes a volume type modification operation, firstly, a storage component extracts and verifies whether a difference exists between a storage back-end resource pool corresponding to two volume types and QoS configuration according to volume type information of the volume to be operated and target volume type information to be modified, and the QoS contains not only the change of configuration parameter values in the QoS but also the check of whether the volume types are related to the QoS.
Step S2: storage drive volume type modification
For the condition that the storage pool resources at the back end of the volume are consistent and QoS configuration parameters are completely consistent, or the volume types are not associated with QoS, directly calling a retrype logic driven by a storage component, and updating database information to realize volume type modification;
step S3: computing drive volume QoS configuration real-time modification
For a volume with a change of a back-end pool before and after volume type modification, or a volume with a consistent volume type association but a difference of volume type association QoS configuration, a calculation component is called, calculation-driven setB lock IoTune logic is called by a calculation service, and the QoS configuration of the volume mounted to the virtual machine is modified in real time;
for the native OpenStack cloud platform, it is not supported to perform operations that change volumes already mounted to the virtual machine to volume types of different QoS attributes. This requires the following modifications to the original functions:
firstly, canceling the limitation of the Cinder component to change the volume already mounted on the virtual machine into the volume type operation with different QoS attribute and adapting; the Nova component logic is then modified, supporting modification of the volume QoS functionality at the front end.
The limitation of changing the volume already mounted to the virtual machine to the volume type with different QoS attribute in the Cinder component API (application program interface) is first released, allowing the volume type of the volume to be executed already mounted to the virtual machine to be modified.
Logic for configuring IO restriction is added in the Nova component, and the Nova component is called to realize the modification of the volume QoS function at the front end. Because the setBlockIoTune interface of Libvirt has the functions of modifying and configuring the device IO related parameters mounted to the virtual machine in real time, only the volume type QoS related configuration parameters including the IO performance limiting parameters, whether to persist modification identifiers and whether to modify identifiers in real time need to be modified in the computing component Nova. When the QoS configuration change is detected, the setblockIoTune interface is called, and the QoS configuration of the volume is updated in real time, so that the QoS configuration of changing the volume type at the front end can be realized.
In step S3, the computing component invokes the Libvirt backend interface to modify the IO performance limitation parameters of the volume device mounted to the virtual machine in real time.
Libvirt is an API for managing the open source of a virtualized platform, a daemon and a management tool.
In the step S3, in the computing component, when the OpenStack cloud computing platform built based on the KVM and QEMU uses Libvirt as the virtual machine management program, by calling the Libvirt existing interface setlockiotune, the QoS configuration is modified in real time for the dev device already mounted to the virtual machine at the front end.
Step S4: computing drive volume copy
And calling a computing drive block copy logic to complete volume copy.
When the Libvirt component and the virtual operating system simulator QEMU use high versions and virtual machine QEMU processes load virtual machine mounted volume equipment in a blockdev mode, the Libvirt component provides a virDomainBlockcopy interface and supports QEMU to copy remote storage volume equipment.
In the step S4, the computing driver encapsulates the virDomainBlockCopy interface through a definition model, and calls the virDomainBlockCopy interface after the QoS modification is completed, so that the data copying of the volume device between different storage back ends can be completed, the migration of the volume in different storage pools is realized, after the migration is completed, the end task module is called, the device task state is modified, and the volume type modification is completed.
The device for modifying the mounted volume type comprises a memory and a processor; the memory is used for storing a computer program, and the processor is used for implementing the method steps described above when executing the computer program.
The readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method steps as described above.
The method for modifying the mounted volume type expands the scene of executing the operation of modifying the volume type by the volume mounted on the virtual machine, supports the operation of changing the volume type when different QoS (quality of service) or one QoS is associated and the other QoS is not associated before and after the volume type is modified, expands the applicable scene of modifying the volume type function and improves the universality of the function.
Different volumes store the backend, generally possess different performance indexes, in order to adapt the ability of each store backend, generally define corresponding performance limiting parameters, namely QoS, on the one hand limit performance indexes, avoid causing the confliction, exert the maximum ability of different backend at the same time. By the method for modifying the mounted volume type, the operation of modifying the mounted volume type is not limited by QoS index, the flexibility of the volume modification back end is improved, and meanwhile, the possibility of changing the back end and increasing QoS limit for the mounted volume is provided.
The above examples are only one of the specific embodiments of the present invention, and the ordinary changes and substitutions made by those skilled in the art within the scope of the technical solution of the present invention should be included in the scope of the present invention.

Claims (8)

1. A method of modifying a mounted volume type, characterized by: the method comprises the following steps:
step S1: storage service volume type and QoS configuration check
After receiving the volume type modification request, the storage service judges whether the volume back-end pool and the associated QoS configuration have differences according to the volume type information before and after modification;
step S2: storage drive volume type modification
For the condition that the storage pool resources at the back end of the volume are consistent and QoS configuration parameters are completely consistent, or the volume types are not associated with QoS, directly calling a retrype logic driven by a storage component, and updating database information to realize volume type modification;
step S3: computing drive volume QoS configuration real-time modification
For a volume with a change of a back-end pool stored before and after the volume type modification, or a volume with a consistent volume type association of the back-end pool and a difference of volume type association QoS configuration, a calculation component is called, a calculation service calls a calculation-driven setblockIoTune logic, and the QoS configuration of the volume mounted to the virtual machine is modified in real time;
step S4: computing drive volume copy
And calling a computing drive blockCopy logic to complete volume copy.
2. The method of modifying a mounted volume type of claim 1, wherein: the Cinder component API is first to remove the restriction on changes to volumes already mounted to the virtual machine to volume types of different QoS attributes, allowing changes to volume types of volumes already mounted to the virtual machine to be executed.
3. The method of modifying a mounted volume type of claim 2, wherein: logic for configuring IO restriction is added in the Nova component, relevant configuration parameters of volume type QoS are modified in the computing component Nova, including IO performance restriction parameters, whether a modification mark is durable and whether a modification mark is real-time, and the Nova component is called to realize the function of modifying the volume QoS at the front end.
4. A method of modifying a mounted volume type as claimed in claim 3, wherein: in step S3, the computing component invokes the Libvirt backend interface to modify the IO performance limitation parameters of the volume device mounted to the virtual machine in real time.
5. The method of modifying a mounted volume type of claim 4, wherein: in the step S3, in the computing component, when the OpenStack cloud computing platform built based on the KVM and QEMU uses Libvirt as the virtual machine management program, by calling the Libvirt existing interface setlockiotune, the QoS configuration is modified in real time for the dev device already mounted to the virtual machine at the front end.
6. The method of modifying a mounted volume type of claim 5, wherein: in the step S4, the computing driver encapsulates the virDomainBlockCopy interface through a definition model, and calls the virDomainBlockCopy interface after the QoS modification is completed, so that the data copying of the volume device between different storage back ends can be completed, the migration of the volume in different storage pools is realized, after the migration is completed, the end task module is called, the device task state is modified, and the volume type modification is completed.
7. An apparatus for modifying the type of mounted volume, characterized by: comprising a memory and a processor; the memory is adapted to store a computer program, the processor being adapted to implement the method steps of any of claims 1 to 6 when the computer program is executed.
8. A readable storage medium, characterized by: the readable storage medium has stored thereon a computer program which, when executed by a processor, implements the method steps of any of claims 1 to 6.
CN202311294477.0A 2023-10-09 2023-10-09 Method for modifying type of mounted volume Pending CN117406921A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311294477.0A CN117406921A (en) 2023-10-09 2023-10-09 Method for modifying type of mounted volume

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311294477.0A CN117406921A (en) 2023-10-09 2023-10-09 Method for modifying type of mounted volume

Publications (1)

Publication Number Publication Date
CN117406921A true CN117406921A (en) 2024-01-16

Family

ID=89497168

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311294477.0A Pending CN117406921A (en) 2023-10-09 2023-10-09 Method for modifying type of mounted volume

Country Status (1)

Country Link
CN (1) CN117406921A (en)

Similar Documents

Publication Publication Date Title
US20200241613A1 (en) Persistent reservations for virtual disk using multiple targets
US20180329647A1 (en) Distributed storage system virtual and storage data migration
US8312471B2 (en) File system independent content aware cache
JP5615698B2 (en) Virtual machine migration
US9671977B2 (en) Handling data block migration to efficiently utilize higher performance tiers in a multi-tier storage environment
US9489396B2 (en) Intermediation of hypervisor file system and storage device models
US11693789B2 (en) System and method for mapping objects to regions
US20160364424A1 (en) Partition-based index management in hadoop-like data stores
JP7016964B2 (en) Systems and methods for running applications on multi-tenant container platforms
US20210173572A1 (en) System and method for managing volumes of data in a block storage system
CN110046026B (en) Method for specifying virtual disk speed limit by cloud host, computing equipment and cloud platform
EP1637987A2 (en) Operation environment associating data migration method
US9940293B1 (en) Method for efficient storage and backup of data via SCSI transport
US11797494B2 (en) Snapshot management in distributed file systems
JP2022546566A (en) System and method for marking application consistency points in time
US20220027076A1 (en) System and Method for Sustaining Single NVMe Subsystem by a Federated Storage Array for NVMe-oF Connectivity
KR20230170024A (en) Zone Segment Drive Management
CN113806300A (en) Data storage method, system, device, equipment and storage medium
CN113296891B (en) Platform-based multi-scene knowledge graph processing method and device
US10606495B2 (en) Creating a structurally aware block storage system
US9135457B1 (en) System and method for recording and applying access privileges in a virtualized environment
IL295006A (en) Virtual machine perfect forward secrecy
US10606506B2 (en) Releasing space allocated to a space efficient target storage in a copy relationship with a source storage
CN111767169A (en) Data processing method and device, electronic equipment and storage medium
US20180322187A1 (en) Dynamic alternate keys for use in file systems utilizing a keyed index

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