Adrian James Johnson

US Patent:

20140006844, Jan 2, 2014

Filed:

Jun 17, 2013

Appl. No.:

13/919769

Inventors:

Ian Alderman - Madison WI, US
Chris Chalfant - Carmel IN, US
Ian Chesal - Ontario, CA
Doug Clayton - Durham NC, US
Rob Futrick - Austin TX, US
Dan Harris - New Haven CT, US
Andrew Kaczorek - Carmel IN, US
Jason Stowe - Greenwich CT, US
Adrian Johnson - Oakland CA, US
Ben Watrous - Greenwich CT, US
Dave Watrous - Schenectady NY, US
Archit Kulshrestha - Weehawken NJ, US

International Classification:

G06F 11/07

US Classification:

714 41

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.

US Patent:

20150363281, Dec 17, 2015

Filed:

Aug 24, 2015

Appl. No.:

14/833880

Inventors:

- Greenwich CT, US
Chris M. Chalfant - Fishers IN, US
Ian Chesal - Santa Clara CA, US
Douglas Clayton - Durham NC, US
S. Robert Futrick - Austin TX, US
Daniel Harris - New Haven CT, US
Andrew Kaczorek - Carmel IN, US
Jason Stowe - Greenwich CT, US
Adrian Johnson - Oakland CA, US
Ben Watrous - Greenwich CT, US
David Watrous - Schenectady NY, US
Archit Kulshrestha - Weehawken NJ, US

Assignee:

Cycle Computing, LLC - Greenwich CT

International Classification:

G06F 11/20
H04L 29/08
H04L 12/26

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.

US Patent:

20150242234, Aug 27, 2015

Filed:

Sep 27, 2013

Appl. No.:

14/432135

Inventors:

- Greenwich CT, US
Adrian Johnson - Oakland CA, US
Jason A. Stowe - Greenwich CT, US
Ben Watrous - Greenwich CT, US

International Classification:

G06F 9/455
G06F 9/46
G06F 9/50

Abstract:

A system and method is provided to dynamically optimize the topography of a compute cluster in real time based on the runtime configuration, specified as metadata, of jobs in a queuing or scheduling environment. The system provisions or terminates multiple types of virtualized resources based on the profile of all applications of the jobs in a current queue based on their aggregate runtime configuration specified as requirements and rank expressions within associated metadata. The system will continually request and terminate compute resources as jobs enter and exit the queue, keeping the cluster as minimal as possible while still being optimized to complete all jobs in the queue, optimized for cost, runtime or other metric. End users can specify the runtime requirements of jobs, thereby preventing the user from having to know about the physical profile of the compute cluster to specifically architect their jobs.