IP Library Granted Patent US 9,146,840
Granted Patent B2
US 9,146,840 · App. 13/919,769 · Granted Sep 29, 2015

Method and system for automatically detecting and resolving infrastructure faults in cloud infrastructure

Inventors: Ian Alderman (Madison, WI); Chris M. Chalfant (Fishers, IN); Ian Chesal (Santa Clara, CA); Douglas Clayton (Durham, NC); S. Robert Futrick (Austin, TX); Daniel Harris (New Haven, CT); Andrew Kaczorek (Carmel, IN); Jason Stowe (Greenwich, CT); Adrian Johnson (Oakland, CA); Ben Watrous (Greenwich, CT); David Watrous (Schenectady, NY); Archit Kulshrestha (Weehawken, NJ)
Assignee: Cycle Computing, LLC
G06F11/3668G06F11/0709G06F11/0793G06F11/36G06F11/3604H04L41/5035H04L41/5038H04L41/5096
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 9,146,840
App. No.
13/919,769
Granted
Sep 29, 2015
Kind
B2
Abstract

Systems and methods are provided for any party in a cloud ecosystem (cloud providers of such resources, the intermediate management software for such resources, and the end user of such resources) to detect and resolve faulty resources synchronously or asynchronously, before said faults adversely affect the users' workloads. The system requests a service or set of one or more resources within a cloud, automatically checking the infrastructure for various faults that would cause it to be non-functional, including pre-defined and user-defined checks, and resolving them before including the infrastructure in the working service cluster of resources. The system presents an API to the user that returns only functional, production-quality resources that are not in a faulty state. An API that tests and resolves bad infrastructure can be registered during the request or a preceding/subsequent API call, removing the need for the end-user to deal with various types of infrastructure faults.

Claims (24)

1. A process for validating a service or set of one or more resources within a cloud for a user, comprising:

automatically checking an infrastructure to detect for any faults including pre-defined and user-defined checks that would cause the infrastructure to be non-functional;

resolving any faults that are detected;

including the infrastructure in a working service cluster of resources; and

presenting to the user only functional resources that are free of faults.

2. The process of claim 1 , wherein the step of resolving the fault is performed synchronously.

3. The process of claim 1 , wherein the step of resolving the fault is performed asynchronously.

4. The process of claim 1 , wherein the process further comprises the step of removing from working service a faulty server infrastructure in a running computing environment.

5. A process of using management or client software, comprising:

receiving resources from a cloud application programming interface that may be non-faulty or faulty;

running fault tests against the resources or service to detect for the presence of faults;

making the detected faulty resources non-faulty; and

communicating the resources to a client application.

6. The process of claim 5 , wherein the step of making comprises removing the detected fault.

7. The process of claim 5 , wherein the step of making comprises correcting the detected fault.

8. A process for validating cloud-based resources in order to maintain a list of fault-free resources, comprising:

(a) testing the ability to log into an infrastructure server;

(b) testing the ability to access a file system within the infrastructure server;

(c) alerting the results of steps (a) and (b) back to fault detection and resolution software, in at least one of Cloud, Management, or Client software; and

if a fault is detected in any of steps (a)-(c), performing at least one of (d) holding the resources for examination, (e) ensuring that a resource in which the fault was detected is not re-acquired, or (f) shutting down the resource.

9. The process of claim 8 , wherein steps (a)-(c) are performed by software run external to the cloud-based resources.

10. The process of claim 8 , wherein at least one of steps (a)-(f) is performed synchronously.

11. The process of claim 8 , wherein at least one of steps (a)-(f) is performed asynchronously.

12. The process of claim 8 , wherein if no fault is detected in any of steps (a)-(c), further including the step of including the server infrastructure in a working server cluster of resources.

Assignments (2)
SECURITY INTEREST Recorded Jul 21, 2015
From: CYCLE COMPUTING LLC
To: VENTURE LENDING & LEASING VII, INC.
Reel/Frame 036140/0016 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 16, 2013
From: ALDERMAN, IAN; CHALFANT, CHRIS M.; CHESAL, IAN; CLAYTON, DOUGLAS; FUTRICK, S. ROBERT; HARRIS, DANIEL; KACZOREK, ANDREW; STOWE, JASON; JOHNSON, ADRIAN; WATROUS, BEN; WATROUS, DAVID; KULSHRESTHA, ARCHIT
To: CYCLE COMPUTING, LLC
Reel/Frame 031210/0685 →
Continuity (2)
Provisional Application 61660300 · Jun 15, 2012
Related Publication 20140006844A1 · Jan 2, 2014