Abstract: Methods, computer program products, computer systems, and the like providing for executing orchestration operations across data center infrastructures are disclosed. In one embodiment, the method includes analyzing a property graph to determine whether a node representing at least one entity in a first data center infrastructure has a contact point with a node representing one or more entities representing one or more core physical or hardware-based resources in a second data center infrastructure. If a contact point exist between nodes of associated with the first and second data centers, the orchestration operation is executed on the at least one entity in the first data center and a corresponding orchestration operation is executed on at least another entity in the second data center infrastructure represented at a contact point in the dependency relationships of the property graph.

Abstract: Various systems and methods are provided for propagating information throughout a data center or other network environment. For instance, in certain embodiments, the functionality disclosed herein includes determines propagation rules, and then either stores and/or propagates those rules throughout the datacenter or other network environment. Propagation rules define various conditions or other variables that govern propagation of information throughout a system, such as those systems described herein. The propagation rules can then be used to perform various other functionality. For instance, the functionality described herein can be used to process updates to entities. The functionality described herein can also be used to process updates to propagation metadata. Additionally, the functionality described herein can be used to process the creation of new relationships. The functionality described herein can also be used to process the deletion of objects and/or relationships.

Abstract: Methods, computer program products, computer systems, and the like providing for executing orchestration operations across data center infrastructures are disclosed. In one embodiment, the method includes analyzing a property graph to determine whether a node representing at least one entity in a first data center infrastructure has a contact point with a node representing one or more entities representing one or more core physical or hardware-based resources in a second data center infrastructure. If a contact point exist between nodes of associated with the first and second data centers, the orchestration operation is executed on the at least one entity in the first data center and a corresponding orchestration operation is executed on at least another entity in the second data center infrastructure represented at a contact point in the dependency relationships of the property graph.

Abstract: Methods, computer program products, computer systems, and the like providing for representation and analysis of entities and their relationships are disclosed. The method, for example, includes selecting a node of a plurality of nodes in a property graph, analyzing entity information associated with the node, and, in response to the analyzing, storing the entity information in dependency information. Each node of the plurality of nodes represents an entity of a plurality of entities, and is coupled to at least one other node of the plurality of nodes by one or more links of a plurality of links of the property graph. Each of the one or more links represents a relationship between the each node and the at least one other node. The entity information is information regarding the entity. The dependency information is configured to facilitate orchestration of one or more of the plurality of entities.

Abstract: Various systems and methods are provided for propagating information throughout a data center or other network environment. For instance, in certain embodiments, the functionality disclosed herein includes determines propagation rules, and then either stores and/or propagates those rules throughout the datacenter or other network environment. Propagation rules define various conditions or other variables that govern propagation of information throughout a system, such as those systems described herein. The propagation rules can then be used to perform various other functionality. For instance, the functionality described herein can be used to process updates to entities. The functionality described herein can also be used to process updates to propagation metadata. Additionally, the functionality described herein can be used to process the creation of new relationships. The functionality described herein can also be used to process the deletion of objects and/or relationships.

Abstract: Methods, computer program products, computer systems, and the like providing for representation and analysis of entities and their relationships are disclosed. The method, for example, includes selecting a node of a plurality of nodes in a property graph, analyzing entity information associated with the node, and, in response to the analyzing, storing the entity information in dependency information. Each node of the plurality of nodes represents an entity of a plurality of entities, and is coupled to at least one other node of the plurality of nodes by one or more links of a plurality of links of the property graph. Each of the one or more links represents a relationship between the each node and the at least one other node. The entity information is information regarding the entity. The dependency information is configured to facilitate orchestration of one or more of the plurality of entities.

Abstract: The disclosed computer-implemented method for enabling multiple-perspective administration of computing systems may include (1) receiving, from a user, a request to administer a computing system that includes a plurality of types of components, (2) identifying an administrative role of the user, (3) identifying a primary component of a primary type of component that is administered by the user in the administrative role, (4) identifying a secondary component of a secondary type of component that is not administered by the user in the administrative role, and (5) providing, via a graphical user interface, a perspective of the computing system to the user that (a) enables the user to administer the computing system by administering the primary component and view information about the secondary component in terms of the primary component and (b) prevents the user from administering the secondary component. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: Service level representations of applications being made highly available are automatically created and published, based on their operational representations. A repository containing multiple application service templates is maintained. Each application service template defines the attributes of an application type to include in corresponding service level representations. To create a service level representation for a specific application instance, an appropriate application service template is selected from the repository. The attributes of a copy of the selected template are populated with values describing the application instance and its associated resources (including a service identifier), thereby automatically creating a service level representation of the application instance. The attributes can be populated with data read from resources of the operational representation of the application instance.

Abstract: Registry information systems and methods are presented. In one embodiment, an application resource switchover method comprises receiving a switchover indication wherein the switchover indication includes an indication to switchover execution of at least one service of an application running on a primary system resource to running on a secondary system resource; performing a switchover preparation process, wherein the switchover preparation process includes automatically generating a switchover plan including indications of switchover operations for performance of a switchover process; and performing the switchover process in which the at least one of the application services is brought up on the secondary system resource in accordance with the plan of switchover operations. In one embodiment, automatically generating a plan of switchover operations includes analyzing the switchover indication, wherein the analyzing includes determining a type of switchover corresponding to the switchover indication.

Abstract: A system and method for visually depicting component states in a computing system. A graphical analysis tool includes a graphical user interface for use in viewing the history of a selected component. A user selects a system component for viewing and then using a timeline “drags” the state of the selected component to various points on the timeline in order to view states of the component at the selected point in time. States of the selected component may also be played forward or backward in a continuous manner. Logging agents in the system are configured to log data corresponding to detected events and forward the log data to a central repository. The analysis tool may access the data in the repository for use in creating visual displays. Point-in-time snapshots of a component may also be stored in the central repository and used to reproduce the history.

Abstract: Registry information systems and methods are presented. In one embodiment, an application resource switchover method comprises receiving a switchover indication wherein the switchover indication includes an indication to switchover execution of at least one service of an application running on a primary system resource to running on a secondary system resource; performing a switchover preparation process, wherein the switchover preparation process includes automatically generating a switchover plan including indications of switchover operations for performance of a switchover process; and performing the switchover process in which the at lease one of the application services is brought up on the secondary system resource in accordance with the plan of switchover operations. In one embodiment, automatically generating a plan of switchover operations includes analyzing the switchover indication, wherein the analyzing includes determining a type of switchover corresponding to the switchover indication.