# US 2014/0195853 A1 · Cloud management using a component health model > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2014/0195853 A1 - Document ID: US20140195853A1 - Status: Published application - Kind: A1 - Application number: 13/737,469 - Filed: 2013-01-09 - Published: 2014-07-10 - Earliest claimed: 2013-01-09 - Assignees: Microsoft Corporation - Applicants: Microsoft Corporation - Inventors: Abhishek Singh; Srikanth Raghavan; Ajay Mani; Saad Syed - Web page: https://patentgrep.com/patent/US20140195853A1 ## CPC - G06F 11/2294: {by remote test} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Embodiments are directed to establishing a model for testing cloud components and to preventing cascading failures in cloud components. In one scenario, a computer system models identified cloud components (including cloud hardware components and/or cloud software components) as health entities. Each health entity is configured to provide state information about the cloud component. The computer system establishes declarative safety conditions which declaratively describe cloud computing conditions that are to be maintained at the identified cloud components. The computer system then tests against the declarative safety conditions to determine which cloud components are or are becoming problematic. Upon determining that an error has occurred, the computer system notifies users of the error and the component at which the error occurred. Guarded interfaces are established to ensure that actions taken to fix the error do not cause further failures. ## Claims ### Claim 1 A computer system comprising the following: one or more processors; system memory; one or more computer-readable storage media having stored thereon computer-executable instructions that, when executed by the one or more processors, causes the computing system to perform a method for establishing a model for testing cloud components, the method comprising the following: an act of modeling one or more identified cloud components including at least one of cloud hardware components and cloud software components as health entities, wherein the health entities are configured to provide state information about the cloud component; an act of establishing one or more declarative safety conditions which declaratively describe cloud computing conditions that are to be maintained at the identified cloud components; and (e.g. customer should have at most one blade down at any given time, or availability must be this high) an act of testing against at least one of the one or more declarative safety conditions to determine which cloud components are or are becoming problematic. ### Claim 2 (depends on 1) The computer system of claim 1, wherein the state information comprises one or more of the following: an indication of the last time the component was updated, an indication of recent computing events, an indication of recent computing errors, and an indication of component dependencies. ### Claim 3 (depends on 1) The computer system of claim 1, wherein the health entities include a health indicator, the health indicator indicating where each cloud component's health is trending. ### Claim 4 (depends on 1) The computer system of claim 1, wherein the modeling results in a health model for cloud management components that manage cloud hardware. ### Claim 5 (depends on 4) The computer system of claim 4, wherein the health model identifies the health of cloud components at a plurality of hierarchical levels including a cluster level, a data center level and a cloud level. ### Claim 6 (depends on 5) The computer system of claim 5, further comprising presenting a graphical user interface (GUI) that shows a graphical representation of the health model, including one or more of the cloud components at each hierarchical level. ### Claim 7 (depends on 6) The computer system of claim 6, further comprising identifying one or more cloud component problems using the graphical representation of the GUI health model GUI. ### Claim 8 (depends on 7) The computer system of claim 7, wherein the identified problem is mapped to one or more known, potential failures. ### Claim 9 (depends on 8) The computer system of claim 8, wherein the identified problem is further mapped to one or more of the most likely cloud components to experience that failure. ### Claim 10 (depends on 7) The computer system of claim 7, wherein the GUI includes one or more controls for each cloud component, at each of the hierarchical levels. ### Claim 11 A computer system comprising the following: one or more processors; system memory; one or more computer-readable storage media having stored thereon computer-executable instructions that, when executed by the one or more processors, causes the computing system to perform a method for preventing cascading failures in cloud components, the method comprising the following: an act of establishing one or more declarative safety conditions which declaratively describe cloud computing conditions that are to be maintained at one or more cloud components including at least one of hardware components and software components; an act of detecting that at least one of the declarative safety conditions is no longer being met, indicating that an error has occurred at one or more components of a specified cloud; an act of determining, based on which safety condition is no longer being met, where the error occurred within the specified cloud; and an act of sending a notification to one or more users indicating that the error occurred, the notification further indicating the cloud component at which the error occurred. ### Claim 12 (depends on 11) The computer system of claim 11, further comprising an act of establishing a guarded interface to prevent one or more specified actions from occurring in response to the detected failure. ### Claim 13 (depends on 12) The computer system of claim 12, wherein customized guarded interfaces are provided for user-provided cloud components. ### Claim 14 (depends on 12) The computer system of claim 12, wherein upon determining that the declarative safety condition is no longer being met, performing at least one of an automatic and a user-specified action to remedy the error. ### Claim 15 (depends on 14) The computer system of claim 14, further comprising preventing the automatic or user-specified action if the action is guarded against by the guarded interface. ### Claim 16 (depends on 12) The computer system of claim 12, wherein a notification is automatically sent to other nodes in the cloud identifying that the node that experienced an error. ### Claim 17 (depends on 12) The computer system of claim 12, wherein each cloud component includes a health indicator that indicates the trending health for that node. ### Claim 18 (depends on 17) The computer system of claim 17, wherein the health indicator is used to identify cloud components that are near failure. ### Claim 19 (depends on 18) The computer system of claim 18, wherein if the health indicator reaches a specified level at an identified component, error detection is automatically initiated to determine the error at the identified component. ### Claim 20 A computer system comprising the following: one or more processors; system memory; one or more computer-readable storage media having stored thereon computer-executable instructions that, when executed by the one or more processors, causes the computing system to perform a method for establishing a model for testing cloud components, the method comprising the following: an act of modeling one or more identified cloud components including at least one of cloud hardware components and cloud software components as health entities, wherein the health entities are configured to provide state information about the cloud component, the modeling resulting in a health model for cloud management components that manage cloud hardware, the health model identifying the health of cloud components at a plurality of hierarchical levels including a cluster level, a data center level and a cloud level; an act of establishing one or more declarative safety conditions which declaratively describe cloud computing conditions that are to be maintained at the identified cloud components; an act of testing against at least one of the one or more declarative safety conditions to determine which cloud components are or are becoming problematic; and an act of presenting a graphical user interface (GUI) that shows a graphical representation of the health model, including one or more of the cloud components at each hierarchical level.