Abstract: Technology described herein relates to management of operational execution by one or more plugins, services and/or consoles of a computing system. A method can comprise registering, by a conflict resolution manager (CRM) controller of a system, a subset of control components of a set of control components of the system, wherein the registering comprises logging operation capabilities of the subset of control components, ranking, by the CRM controller, respective control components of the subset, wherein the ranking is performed based on an operation comprised by the operation capabilities, and generating, by the CRM controller, a permission for performance of the operation by a selected control component of the subset having a highest rank determined by the ranking. The control components can comprise a plugin of, or to be installed at, at least one of the system or a management console of the system, which can be a computing system.

Abstract: According to one embodiment, a plugin ranking system includes computer-executable instructions for use in a computing environment configured with multiple hardware components. The instructions may be executed to determine a collective operating characteristic of the hardware components, and rank the plurality of plugins according to a relevance of the management function of each plugin to the determined operating characteristic in which the plugins are each configured to perform a different management function for managing the computing environment. Once ranked, the instructions can then provide an indication of the ranked plugins for consumption by a user.

Abstract: In accordance with embodiments of the present disclosure, a system may include a plurality of chassis, each chassis comprising a plurality of information handling systems and a private inter-chassis network configured to couple the plurality of chassis to one another. Each chassis of the plurality of chassis may be configured to advertise a message to the private inter-chassis network, the message comprising information regarding such chassis. The plurality of chassis may detect the presence of each other based on messages advertised from each chassis and the plurality of chassis may nominate a lead chassis from the plurality of chassis to serve as a single point of management of the system.

Abstract: In accordance with embodiments of the present disclosure, an information handling system may include a processor and a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution by the processor, cause the processor to (i) read plug-in configuration data setting forth data regarding user interface modifications to be made to a user interface of a management console application; (ii) based on the plug-in configuration data, call one or more pluggable modules; and (iii) integrate user interface features defined by the plug-in configuration data and the one or more pluggable modules into the user interface of the management console application.

Abstract: In accordance with embodiments of the present disclosure, a system may include a plurality of chassis, each chassis comprising a plurality of information handling systems and a private inter-chassis network configured to couple the plurality of chassis to one another. Each chassis of the plurality of chassis may be configured to advertise a message to the private inter-chassis network, the message comprising information regarding such chassis. The plurality of chassis may detect the presence of each other based on messages advertised from each chassis and the plurality of chassis may nominate a lead chassis from the plurality of chassis to serve as a single point of management of the system.

Abstract: In accordance with embodiments of the present disclosure, an information handling system may include a processor and a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution by the processor, cause the processor to (i) read plug-in configuration data setting forth data regarding user interface modifications to be made to a user interface of a management console application; (ii) based on the plug-in configuration data, call one or more pluggable modules; and (iii) integrate user interface features defined by the plug-in configuration data and the one or more pluggable modules into the user interface of the management console application.

Abstract: A system and method for determining fault isolation in an enterprise computing system is disclosed. A method includes automatically troubleshooting errors in an enterprise computing system that receives at an analyzer engine a status notification from a first component. In response to receiving the status notification, the method automatically selects a first analyzer policy file from a set of analyzer policy files based on the status notification received at the analyzer engine, wherein the analyzer policy file contains troubleshooting logic for determining root causes for errors. The method automatically attempts to communicate with a second component based on the troubleshooting logic within the first analyzer policy file. The method automatically determines a root cause for the status notification based on the troubleshooting logic in the selected analyzer policy file and based on information obtained in connection with the attempt to communicate with the second component.

Abstract: A system and method for determining fault isolation in an enterprise computing system is disclosed. A method includes automatically troubleshooting errors in an enterprise computing system that receives at an analyzer engine a status notification from a first component. In response to receiving the status notification, the method automatically selects a first analyzer policy file from a set of analyzer policy files based on the status notification received at the analyzer engine, wherein the analyzer policy file contains troubleshooting logic for determining root causes for errors. The method automatically attempts to communicate with a second component based on the troubleshooting logic within the first analyzer policy file. The method automatically determines a root cause for the status notification based on the troubleshooting logic in the selected analyzer policy file and based on information obtained in connection with the attempt to communicate with the second component.

Abstract: A system and method for determining fault isolation in an enterprise computing system is disclosed. A method includes automatically troubleshooting errors in an enterprise computing system that receives at an analyzer engine a status notification from a first component. In response to receiving the status notification, the method automatically selects a first analyzer policy file from a set of analyzer policy files based on the status notification received at the analyzer engine, wherein the analyzer policy file contains troubleshooting logic for determining root causes for errors. The method automatically attempts to communicate with a second component based on the troubleshooting logic within the first analyzer policy file. The method automatically determines a root cause for the status notification based on the troubleshooting logic in the selected analyzer policy file and based on information obtained in connection with the attempt to communicate with the second component.

Abstract: A system and method for determining fault isolation in an enterprise computing system is disclosed. A method includes automatically troubleshooting errors in an enterprise computing system that receives at an analyzer engine a status notification from a first component. In response to receiving the status notification, the method automatically selects a first analyzer policy file from a set of analyzer policy files based on the status notification received at the analyzer engine, wherein the analyzer policy file contains troubleshooting logic for determining root causes for errors. The method automatically attempts to communicate with a second component based on the troubleshooting logic within the first analyzer policy file. The method automatically determines a root cause for the status notification based on the troubleshooting logic in the selected analyzer policy file and based on information obtained in connection with the attempt to communicate with the second component.