Abstract: A processing device receives a request to include a custom action in a processing definition. The custom action is to be performed in response to an occurrence of an infrastructure event in a third party infrastructure platform. The processing device selects the processing definition that specifies a default action to be performed in response to the occurrence of the infrastructure event. The default action being defined by an infrastructure management platform managing the third party infrastructure platform. The processing device receives, from the third party infrastructure platform, user input defining the custom action relative to the default action in the processing definition and changes the processing definition to include the custom action relative to the default action.

Abstract: The subject matter of this specification can be implemented in, among other things, a method that includes responsive to occurrence of a virtual machine (VM) retirement event, invoking, by a processing device in a management platform, a VM retirement state machine of the management platform to handle retirement of a VM corresponding to the VM retirement event, setting, via the VM retirement state machine, a VM retirement attribute corresponding to the VM to a retiring state, determining, via the VM retirement state machine, that the VM is in a correct state to retire, performing, via the VM retirement state machine, user-customized pre-retirement processes corresponding to the VM, retiring, via the VM retirement state machine, the VM, and setting, via the VM retirement state machine, the VM retirement attribute to a retired state.

Abstract: A processing device receives event notifications for occurrences of infrastructure events from a different event sources. The event notifications have different formats to represent a same type of infrastructure event. The processing device creates uniform event notifications from a base event format for the event notifications, and provides the uniform event notifications to a centralized event handler that corresponds to the base event format within a threshold amount of time to allow a time sensitive action to be performed by the centralized event handler within a time period.

Abstract: By implementing various types of tags, easy management and control of assets in a business system is enabled. These assets may be virtual machines, hardware assets, personnel assets, etc. System tags are determined and associated with an asset automatically. Virtual tags and dynamic tags are tags that do not contain the information sought—rather, these tags contain instructions about how to determine the tag value associated with an asset. Management tags are user-entered tags indicating information about an asset based on the knowledge of an individual. These tags can be combined using Boolean algebraic operators, resulting in a tag-based algebra system, which enables a Tag-Based Query Language for searching a universe of assets based on the associated tags. Additionally, tag-based algebra enables access control based on tags associated with a user, assets in a universe of assets, and enables policies to be enforced in a universe of assets.

Abstract: A processing device receives a request to include a custom action in a processing definition. The custom action is to be performed in response to an occurrence of an infrastructure event in a third party infrastructure platform. The processing device selects the processing definition that specifies a default action to be performed in response to the occurrence of the infrastructure event. The default action being defined by an infrastructure management platform managing the third party infrastructure platform. The processing device receives, from the third party infrastructure platform, user input defining the custom action relative to the default action in the processing definition and changes the processing definition to include the custom action relative to the default action.

Abstract: A processing device receives a request to include a custom action in a processing definition. The custom action is to be performed in response to an occurrence of an infrastructure event in a third party infrastructure platform. The processing device selects the processing definition that specifies a default action to be performed in response to the occurrence of the infrastructure event. The default action being defined by an infrastructure management platform managing the third party infrastructure platform. The processing device receives, from the third party infrastructure platform, user input defining the custom action relative to the default action in the processing definition and changes the processing definition to include the custom action relative to the action.

Abstract: Techniques are disclosed for controlling and managing virtual machines and other such virtual systems. VM execution approval is based on compliance with policies controlling various aspects of VM. The techniques can be employed to benefit all virtual environments, such as virtual machines, virtual appliances, and virtual applications. For ease of discussion herein, assume that a virtual machine (VM) represents each of these environments. In one particular embodiment, a systems management partition (SMP) is created inside the VM to provide a persistent and resilient storage for management information (e.g., logical and physical VM metadata). The SMP can also be used as a staging area for installing additional content or agentry on the VM when the VM is executed. Remote storage of management information can also be used. The VM management information can then be made available for pre-execution processing, including policy-based compliance testing.

Abstract: A method of implementations includes determining, by a processing device in a management platform, an occurrence of an inventory event in a computing environment managed by the management platform, wherein the computing environment comprises a plurality of managed objects, and invoking a relationship handler to obtain identifying attributes for a target managed object corresponding to the inventory event. The relationship handler is further to update the identifying attributes and relationship attributes corresponding to the target managed object in an inventory tree maintained by the management platform, the relationship attributes comprising an identification of affiliations between two or more managed objects and for each managed object affiliated to the target managed object, and schedule a job in a message queue to update each of the attributes for the managed object, the detailed attributes comprising attributes of the managed object that are not identifying attributes or relationship attributes.

Abstract: Techniques are disclosed for controlling and managing virtual machines and other such virtual systems. VM execution approval is based on compliance with policies controlling various aspects of VM. The techniques can be employed to benefit all virtual environments, such as virtual machines, virtual appliances, and virtual applications. For ease of discussion herein, assume that a virtual machine (VM) represents each of these environments. In one particular embodiment, a systems management partition (SMP) is created inside the VM to provide a persistent and resilient storage for management information (e.g., logical and physical VM metadata). The SMP can also be used as a staging area for installing additional content or agentry on the VM when the VM is executed. Remote storage of management information can also be used. The VM management information can then be made available for pre-execution processing, including policy-based compliance testing.

Abstract: A processing device receives a request to include a custom action in a processing definition. The custom action is to be performed in response to an occurrence of an infrastructure event in a third party infrastructure platform. The processing device selects the processing definition that specifies a default action to be performed in response to the occurrence of the infrastructure event. The default action being defined by an infrastructure management platform managing the third party infrastructure platform.

Abstract: A method of implementations includes determining, by a processing device in a management platform, an occurrence of an inventory event in a computing environment managed by the management platform, wherein the computing environment comprises a plurality of managed objects, and invoking a relationship handler to obtain identifying attributes for a target managed object corresponding to the inventory event. The relationship handler is further to update the identifying attributes and relationship attributes corresponding to the target managed object in an inventory tree maintained by the management platform, the relationship attributes comprising an identification of affiliations between two or more managed objects and for each managed object affiliated to the target managed object, and schedule a job in a message queue to update each of the attributes for the managed object, the detailed attributes comprising attributes of the managed object that are not identifying attributes or relationship attributes.

Abstract: A processing device receives event notifications for occurrences of infrastructure events from a different event sources. The event notifications have different formats to represent a same type of infrastructure event. The processing device creates uniform event notifications from a base event format for the event notifications, and provides the uniform event notifications to a centralized event handler that corresponds to the base event format within a threshold amount of time to allow a time sensitive action to be performed by the centralized event handler within a time period.

Abstract: The subject matter of this specification can be implemented in, among other things, a method that includes responsive to occurrence of a virtual machine (VM) retirement event, invoking, by a processing device in a management platform, a VM retirement state machine of the management platform to handle retirement of a VM corresponding to the VM retirement event, setting, via the VM retirement state machine, a VM retirement attribute corresponding to the VM to a retiring state, determining, via the VM retirement state machine, that the VM is in a correct state to retire, performing, via the VM retirement state machine, user-customized pre-retirement processes corresponding to the VM, retiring, via the VM retirement state machine, the VM, and setting, via the VM retirement state machine, the VM retirement attribute to a retired state.

Abstract: Techniques are disclosed for controlling and managing virtual machines and other such virtual systems. VM execution approval is based on compliance with policies controlling various aspects of VM. The techniques can be employed to benefit all virtual environments, such as virtual machines, virtual appliances, and virtual applications. For ease of discussion herein, assume that a virtual machine (VM) represents each of these environments. In one particular embodiment, a systems management partition (SMP) is created inside the VM to provide a persistent and resilient storage for management information (e.g., logical and physical VM metadata). The SMP can also be used as a staging area for installing additional content or agentry on the VM when the VM is executed. Remote storage of management information can also be used. The VM management information can then be made available for pre-execution processing, including policy-based compliance testing.

Abstract: Techniques are disclosed for controlling and managing virtual machines and other such virtual systems. VM execution approval is based on compliance with policies controlling various aspects of VM. The techniques can be employed to benefit all virtual environments, such as virtual machines, virtual appliances, and virtual applications. For ease of discussion herein, assume that a virtual machine (VM) represents each of these environments. In one particular embodiment, a systems management partition (SMP) is created inside the VM to provide a persistent and resilient storage for management information (e.g., logical and physical VM metadata). The SMP can also be used as a staging area for installing additional content or agentry on the VM when the VM is executed. Remote storage of management information can also be used. The VM management information can then be made available for pre-execution processing, including policy-based compliance testing.

Abstract: Methods and apparatus for storing and transmitting historical configuration data associated with information technology assets are disclosed. The system reads and stores a first version of data with a timestamp. The system then performs a local update by reading a second version of data with a timestamp, replacing the first set of data and timestamp, and storing the changes between the first and second versions of data. The system also may receive update requests from a remote location for the latest version of data. The changes between versions of data are sent to the remote location, where the changes between versions of data are stored and are usable to create the requested latest version of data and/or prior versions of data.

Abstract: Techniques are disclosed for controlling and managing virtual machines and other such virtual systems. VM execution approval is based on compliance with policies controlling various aspects of VM. The techniques can be employed to benefit all virtual environments, such as virtual machines, virtual appliances, and virtual applications. For ease of discussion herein, assume that a virtual machine (VM) represents each of these environments. In one particular embodiment, a systems management partition (SMP) is created inside the VM to provide a persistent and resilient storage for management information (e.g., logical and physical VM metadata). The SMP can also be used as a staging area for installing additional content or agentry on the VM when the VM is executed. Remote storage of management information can also be used. The VM management information can then be made available for pre-execution processing, including policy-based compliance testing.

Abstract: Techniques are disclosed for controlling and managing virtual machines and other such virtual systems. VM execution approval is based on compliance with policies controlling various aspects of VM. The techniques can be employed to benefit all virtual environments, such as virtual machines, virtual appliances, and virtual applications. For ease of discussion herein, assume that a virtual machine (VM) represents each of these environments. In one particular embodiment, a systems management partition (SMP) is created inside the VM to provide a persistent and resilient storage for management information (e.g., logical and physical VM metadata). The SMP can also be used as a staging area for installing additional content or agentry on the VM when the VM is executed. Remote storage of management information can also be used. The VM management information can then be made available for pre-execution processing, including policy-based compliance testing.

Abstract: Methods and apparatus of locating an unauthorized virtual machine are disclosed. A virtual machine is registered with a management system. When the virtual machine is requested to start, the system determines whether the virtual machine is in an authorized environment. In an authorized environment, the virtual machine is enabled to operate normally. In an unauthorized environment, the virtual machine is disabled. The disabled virtual machine gathers information about the unauthorized environment and transmits the information to the virtual machine owner.

Abstract: Techniques are disclosed for controlling and managing virtual machines and other such virtual systems. VM execution approval is based on compliance with policies controlling various aspects of VM. The techniques can be employed to benefit all virtual environments, such as virtual machines, virtual appliances, and virtual applications. For ease of discussion herein, assume that a virtual machine (VM) represents each of these environments. In one particular embodiment, a systems management partition (SMP) is created inside the VM to provide a persistent and resilient storage for management information (e.g., logical and physical VM metadata). The SMP can also be used as a staging area for installing additional content or agentry on the VM when the VM is executed. Remote storage of management information can also be used. The VM management information can then be made available for pre-execution processing, including policy-based compliance testing.