Tiered cloud storage for different availability and performance requirements

Patent metadata

Field	Value
Publication number	US-12197292-B2
Application number	US-202318215593-A
Country	US
Kind code	B2
Filing date	Jun 28, 2023
Priority date	Aug 18, 2016
Publication date	Jan 14, 2025
Grant date	Jan 14, 2025

Abstract

A system and method for a tiered cloud storage for different availability and performance requirements includes a gateway, a block store configured to cache data, and an object store configured to persistently store data. The gateway, the block store, and the object store are in a compute zone. The gateway may receive from a user application a file access call and process the file access call. The gateway may also send the file access call to the block store. Then, the gateway may determine to store data in the object store and flush the data from the block store to the object store.

First claim

The invention is claimed as follows:

1. A method comprising:
heuristically determining a frequency of replication for a cloud storage system based on prioritization of at least one of data consistency or data loss;
determining, in response to a write access call to store first data, by a first gateway in a first compute zone including a first block store and a first object store, that the first object store exceeds a predetermined threshold capacity;
responsive to determining that the first block store exceeds the predetermined threshold capacity, throttling, by the first gateway, a speed at which the first gateway processes the write access call to allow other data to be flushed from the first block store to the first object store, wherein the first object store has a flat and non-hierarchical structure; and
replicating metadata used by the first gateway at the frequency of replication to a second gateway in a second compute zone, the metadata comprising information regarding which data is stored in the first block store and which data is flushed to the first object store and stored in the first object store, wherein the second compute zone further includes a second block store and a second object store.

2. The method of claim 1 , further comprising receiving, by the first gateway, from a user application the write access call.

3. The method of claim 1 , further comprising replicating a data cache in the first block store at the frequency of replication to the second block store, wherein the data cache stores data cached in the first block store.

4. The method of claim 3 , wherein at least one of the data cache and the metadata is replicated synchronously.

5. The method of claim 3 , wherein both the data cache and the metadata are replicated asynchronously.

6. The method of claim 1 , further comprising expanding, by the first gateway, a capacity of the first block store.

7. The method of claim 1 , further comprising:
determining, by the first gateway, whether an object in the first object store is modified, wherein the object is associated with a block in the first block store; and
responsive to determining that the object is modified, determining, by the first gateway, whether it is safe to retrieve the object from the first object store.

8. The method of claim 7 , further comprising: responsive to determining that it is not safe to retrieve the object from the first object store, delaying, by the first gateway, the retrieval of the object.

9. The method of claim 8 , wherein the retrieval of the object is delayed until the modification of the object is updated to the second compute zone.

10. A cloud storage system comprising:
a first gateway;
a first block store; and
a first object store, wherein the first gateway, the first block store, and the first object store are in a first compute zone,
wherein the first gateway comprises one or more processors configured by executing computer instructions to:
heuristically determine a frequency of replication for the cloud storage system based on prioritization of at least one of data consistency or data loss;
determine, in response to a write access call to store first data, that the first object store exceeds a predetermined threshold capacity; and
responsive to determining that the first block store exceeds the predetermined threshold capacity, throttle a speed at which the first gateway processes the write access call to allow other data to be flushed from the first block store to the first object store, wherein the first object store has a flat and non-hierarchical structure,
wherein metadata used by the first gateway is replicated at the frequency of replication to a second gateway in a second compute zone, the metadata comprising information regarding which data is stored in the first block store and which data is flushed to the first object store and stored in the first object store, wherein the second compute zone further includes a second block store and a second object store.

11. The cloud storage system of claim 10 , wherein the first gateway is a Portable Operating System Interface layer.

12. The cloud storage system of claim 10 , wherein the first gateway is further configured to expand a capacity of the first block store.

13. The cloud storage system of claim 10 , wherein a data cache in the first block store is replicated at the frequency of replication to the second block store, wherein the data cache stores data cached in the first block store.

14. The cloud storage system of claim 13 , wherein at least one of the data cache and the metadata are replicated synchronously.

15. The cloud storage system of claim 13 , wherein both the data cache and the metadata are replicated asynchronously.

16. The cloud storage system of claim 10 , wherein the first gateway is further configured to:
determine whether an object in the first object store is modified, wherein the object is associated with a block in the first block store; and
responsive to determining that the object is modified, determine whether it is safe to retrieve the object from the first object store.

17. The cloud storage system of claim 16 , wherein the first gateway is further configured to: responsive to determining that it is not safe to retrieve the object from the first object store, delay the retrieval of the object.

18. The cloud storage system of claim 17 , wherein the retrieval of the object is delayed until the modification of the object is updated to the second compute zone.

19. A computer readable, non-transitory storage medium including instructions that, when executed by one or more processors in a cloud storage system, cause the cloud storage system to:
heuristically determine a frequency of replication for the cloud storage system based on prioritization of at least one of data consistency or data loss;
determine, in response to a write access call to store first data, by a first gateway in a first compute zone including a first block store and a first object store, that the first object store exceeds a predetermined threshold capacity; and
responsive to determining that the first block store exceeds the predetermined threshold capacity, throttle, by the first gateway, a speed at which the first gateway processes the write access call to allow other data to be flushed from the first block store to the first object store, wherein the first object store has a flat and non-hierarchical structure,
wherein metadata used by the first gateway is replicated at the frequency of replication to a second gateway in a second compute zone, the metadata comprising information regarding which data is stored in the first block store and which data is flushed to the first object store and stored in the first object store, wherein the second compute zone further includes a second block store and a second object store.

20. The computer readable, non-transitory storage medium of claim 19 , wherein a data cache in the first block store is replicated at the frequency of replication to the second block store, wherein the data cache stores data cached in the first block store.

Assignees

• Red Hat Inc

Inventors

• Chen Huamin
• Vyas Jay

Classifications

• H04L67/565

  Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561) · CPC title

• H04L67/561

  Adding application-functional data or data for application control, e.g. adding metadata · CPC title

• H04L67/10

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title

• G06F11/2097

  maintaining the standby controller/processing unit updated (initialisation or re-synchronisation thereof G06F11/1658 and subgroups) · CPC title

• G06F16/182

  Distributed file systems · CPC title