IP Library Granted Patent US 11,874,733
Granted Patent B2
US 11,874,733 · App. 17/750,155 · Granted Jan 16, 2024

Recovering a container storage system

Inventors: Simon Dodsley (Boca Raton, FL); Remko Deenik (Rosmalen, NL); Jon Owings (Buford, GA); Sergey Zhuravlev (Bothell, WA); Joshua Robinson (Madrid, ES)
Assignee: Pure Storage, Inc.
G06F11/0793G06F11/008G06F11/079G06F11/0727G06F11/0751G06F11/3034
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,874,733
App. No.
17/750,155
Granted
Jan 16, 2024
Kind
B2
Abstract

Recovery of a container storage provider, including: storing, within a first database, configuration information related to the container storage provider; storing, within a second database, the configuration information; and responsive to detecting that one or more components associated with the container storage provider have become unavailable, creating a replacement component using configuration information contained in the second database.

Claims (23)

1. A method comprising: storing, within a first database, configuration information related to a container storage provider, the configuration information indicating storage resources provided to one or more containerized applications managed by a container orchestration system; storing, within a second database, the configuration information; and responsive to detecting that one or more components associated with the container storage provider have become unavailable, creating a replacement component using configuration information in the second database, wherein creating the replacement component using configuration information in the second database comprises creating a new container storage provider.

2. The method of claim 1 , wherein creating the replacement component using configuration information in the second database further comprises creating a new instance of the first database.

3. The method of claim 1 , further comprising:

receiving, by the container storage provider, a request for persistent storage for use by a containerized application;

selecting, in dependence upon information contained in the request, one or more storage resources from a pool of storage resources;

providing, to the containerized application, the one or more storage resources, wherein information associated with the one or more storage resources are stored within the first database.

4. The method of claim 1 , wherein creating a new container storage provider comprises creating one or more containers that include components of a container storage provider service.

5. The method of claim 1 , wherein the new container storage provider comprises a new instance of the container storage provider.

6. The method of claim 5 , wherein the configuration information in the second database is used to configure the new instance of the container storage provider the same as the container storage provider.

7. The method of claim 1 , wherein at least one of the first database or the second database is hosted by a cloud-based storage system.

8. The method of claim 1 , wherein at least one of the first database or the second database is hosted by a cloud services provider.

9. The method of claim 1 , wherein the container storage provider supports a service provided by a cloud services provider.

10. The method of claim 9 , wherein the cloud services provider is embodied as a private cloud, a public cloud, or a hybrid cloud.

11. A method comprising: storing, within a first database, configuration information related to a container storage provider, the configuration information indicating storage resources provided to one or more containerized applications managed by a container orchestration system; storing, within a second database, the configuration information; and responsive to detecting that one or more components associated with the container storage provider have become unavailable, creating a replacement component using configuration information in the second database, wherein creating the replacement component using configuration information in the second database comprises creating a new instance of the first database.

12. The method of claim 11 , wherein creating the replacement component using configuration information in the second database further comprises creating a new instance of the container storage provider.

13. The method of claim 11 , further comprising: receiving, by the container storage provider, a request for persistent storage for use by a containerized application; selecting, in dependence upon information contained in the request, one or more storage resources from a pool of storage resources; providing, to the containerized application, the one or more storage resources, wherein information associated with the one or more storage resources are stored within the first database.

14. The method of claim 11 , wherein the configuration information in the second database is used to configure the new instance of the first database the same as the second database.

15. The method of claim 11 , wherein at least one of the first database or the second database is hosted by a cloud-based storage system.

16. The method of claim 11 , wherein at least one of the first database or the second database is hosted by a cloud services provider.

17. The method of claim 11 , wherein the container storage provider supports a service provided by a cloud services provider.

18. The method of claim 17 , wherein the cloud services provider is embodied as a private cloud, a public cloud, or a hybrid cloud.

19. A computer program product disposed upon a non-transitory storage medium and comprising computer program instructions that, when executed, cause a computer to carry out the steps of: storing, within a first database, configuration information related to a container storage provider, the configuration information indicating storage resources provided to one or more containerized applications managed by a container orchestration system; storing, within a second database, the configuration information; and responsive to detecting that one or more components associated with the container storage provider have become unavailable, creating a replacement component using configuration information in the second database, wherein creating the replacement component using configuration information in the second database comprises at least one of 1) creating a new instance of the container storage provider or 2) creating a new instance of the first database.

20. The computer program product of claim 19 , wherein the container storage provider supports a service provided by a public cloud.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 20, 2022
From: DODSLEY, SIMON; DEENIK, REMKO; OWINGS, JON; ZHURAVLEV, SERGEY; ROBINSON, JOSHUA
To: PURE STORAGE, INC.
Reel/Frame 059976/0642 →
Continuity (7)
Continuation 17027132 · Sep 21, 2020
Continuation In Part 16681355 · Nov 12, 2019
Continuation 15957195 · Apr 19, 2018
Continuation In Part 15179301 · Jun 10, 2016
Continuation 14920994 · Oct 23, 2015
Provisional Application 63051664 · Jul 14, 2020
Related Publication 20220283895A1 · Sep 8, 2022