Red Hat, Inc.

Red Hat Israel, Ltd.

Adam G Litke

Liron Aravot

Nir Soffer

Federico Simoncelli

Huamin Chen

Michael Howard Henriksen

Fabian Deutsch

Alexander G P Wels

David Vossel

A method includes populating a physical storage volume associated with a second PVC from a data source identified by a first PVC and in response to populating the physical storage volume, associating the physical storage volume with the first PVC.

Pre-population of persistent storage volumes

A first command is received from a workload, by a host system executing a nested container storage interface (CSI) driver, to create a persistent volume. The nested CSI driver converts the first command used by the workload to create the persistent volume to a second command used by the host system to increase a capacity of a previously generated persistent volume allocated to the workload. The second command is transmitted to an undercluster CSI driver of the host system, wherein the second command causes the undercluster CSI driver to increase the capacity of the previously generated persistent volume.

Overlay container storage driver for microservice workloads

A method includes identifying a request for a first persistent volume claim (PVC) from an application in a first namespace, the request including storage requirements of the first PVC and generating a second PVC in a second namespace in view of the storage requirements of the first PVC. The method further includes populating a physical storage volume associated with the second PVC from a data source identified by the first PVC and associating the physical storage volume with the first PVC in the first namespace in response to populating the physical storage volume.

Pre-population of persistent volumes in container based cluster

Dynamic storage provisioning for nested clusters is disclosed. A hosted cluster (HC) storage provisioner, executing in a hosted cluster that is hosted by an infrastructure cluster (IC), receives a request to dynamically provision a hosted cluster (HC) persistent volume object that is coupled to a physical storage. The HC storage provisioner causes an IC control plane executing on the IC to generate IC volume metadata that is backed by a storage volume on the physical storage. The HC storage provisioner determines that the IC volume metadata has been generated. The HC storage provisioner creates HC volume metadata on the hosted cluster that is linked to the IC volume metadata, the HC volume metadata comprising an HC persistent volume object that represents a persistent volume for use by the hosted cluster that is backed, via the IC volume metadata, by the physical storage.

Dynamic storage provisioning for nested clusters

Systems and methods for enhancing storage recollection in a shared storage system by enabling the recollection procedure to differentiate between open and abandoned transaction. An example method comprises: detecting, by a processing device, a transaction marker of a storage system, the transaction marker being stored on shared storage and indicating a modification of the shared storage is incomplete; determining, in view of a locking data structure on the shared storage, whether the transaction marker is associated with an abandoned modification; in response to the transaction marker being associated with an abandoned modification, releasing a portion of the shared storage associated with the abandoned modification; and destroying the transaction marker.

Differentiating open and abandoned transactions in a shared storage environment

Cloning of virtual-machine images can be managed. For example, a computing device can copy a segment of a virtual-machine image stored in a second storage device to a first storage device in response to receiving a first read request for the segment from a virtual machine. The first storage device may be capable of responding to read requests from the virtual machine with less latency than the second storage device. The computing device can also update a log to indicate that the segment is stored on the first storage device. Thereafter, the computing device can receive a second read request for the segment. In response, the computing device can determine that the segment is stored in the first storage device using the log, and provide the segment by obtaining the segment from the first storage device.

Managing virtual-machine image cloning

A system and method are disclosed for detecting and handling volume creation failures. In one implementation, a request to create a new volume in a volume chain for a virtual machine is received. A processing device creates a first metadata file for the new volume, where the first metadata file has a first filename indicating that creation of the new volume has not completed. A reference to a parent volume of the new volume is stored in the first metadata file, along with an indication that the new volume is a leaf of the volume chain. A second metadata file that is associated with the parent volume is updated in view of the new volume. The processing device creates a data file for the new volume and renames the first metadata file to a second filename indicating that creation of the new volume has completed.

Correcting a volume chain after a volume creation failure is detected

A storage manager may initiate a merge operation for a set of writable storage volumes. The storage manager may receive, from a management server, an indication that an allocated disk space of at least one storage volume of the set of writable storage volumes is to be extended, where the at least one storage volume has exceeded a storage threshold during the merge operation. The allocated disk space of the at least one storage volume of the set of writable storage volumes may be extended in response to the received indication. The management server may be notified that the allocated disk space of the at least one storage volume has been extended upon extending the allocated disk space.

Peer to peer volume extension in a shared storage environment

Systems and methods for data storage management technology that use task identifiers to manage tasks and ensure storage modifications occur without unnecessary task duplication. An example method may comprise: generating a task identifier on a first device; transmitting a request comprising the task identifier to create a task on a second device, the task being associated with the task identifier and comprising the allocation of a data storage portion on a shared storage; determining a reply to the task is missing; and in response to determining the reply is missing, detecting whether the task was created on the second device.

Failure resistant volume creation in a shared storage environment

Systems and methods for failure recovery in shared storage operations. An example method comprises: acquiring, by a processing device, a lock with respect to a storage domain comprising a specified disk image; creating a transaction marker associated with the disk image, wherein the transaction marker is represented by a pre-defined tag associated with a logical volume of a block-based storage, wherein the logical volume implements a data area of a new volume associated with the disk image; creating a component of the new volume associated with the disk image; destroying the transaction marker by removing the pre-defined tag representing the transaction marker from the logical volume; and releasing the lock with respect to the storage domain.

Failure recovery in shared storage operations

Implementations of the disclosure provides for determining status of a host operation without accessing the host in a shared storage environment. A method of the disclosure includes acquiring, by a processing device, a lease on a storage volume associated with a storage domain. The lease grants the processing device exclusive access to the storage volume. Responsive to acquiring the lease, a data structure associated with the storage volume is modified to indicate that data of the storage volume is invalid. An update operation is initiated with respect to the storage volume. Upon completion of the update operation, the data structure is updated to indicate that the data valid and the lease on the storage volume is released.

Determining status of a host operation without accessing the host in a shared storage environment

A processing device receives a request to delete a snapshot of a virtual machine. The processing device identifies a volume chain of a virtual disk in a shared storage that includes a destination storage volume and a source storage volume. The snapshot is associated with the source storage volume or the destination storage volume. The processing device instructs a host machine to perform a merge operation to merge data of the source storage volume with data of the destination storage volume and to delete the snapshot. The processing device monitors a set of writable storage volumes that comprises the destination storage volume to determine whether a storage threshold for any storage volume of the set of writable storage volumes is met during the merge operation. In response to the storage threshold being met during the merge operation, the processing device causes the performance of an extension operation to extend the allocated disk space of at least one storage volume of the set of writable storage volumes.

Systems and methods for failure recovery in shared storage operations. An example method comprises: acquiring a lock with respect to a storage domain comprising a specified disk image; creating a transaction marker associated with the disk image; creating a component of a new volume associated with the disk image; destroying the transaction marker; and releasing the lock with respect to the storage domain.

Systems and methods for disk image deletion with failure resistant data erasure. An example method may comprise: receiving a request to delete a first disk image associated with a data storage portion; associating the data storage portion with a second disk image responsive to receiving the request to delete the first disk image; deleting the first disk image; and initiating a data erasure procedure on the data storage portion.

Disk image deletion with failure resistant data erasure

A first identification of a series of volumes associated with a virtual disk that is associated with a virtual machine is received. A second identification of the series of volumes associated with the virtual disk is received. An operation associated with the virtual disk may be identified as being interrupted in view of a comparison of the first identification with the second identification. In response to identifying that the operation has been interrupted, a volume from at least one of the first or second identifications may be removed.

Growing community of inventors

Harrisburg, PA, United States of America

Adam G Litke