Abstract: A method, system and computer program product for performing maintenance operations on a cloud computing node. An administrative server receives an indication that a maintenance operation is to be performed on a cloud computing node. The administrative server identifies which virtual machine(s) on the cloud computing node will be affected by the maintenance operation. The administrative server relocates the virtual machine(s) to be affected by the maintenance operation to other suitable cloud computing node(s) prior to the maintenance operation being performed. The administrative server then performs the maintenance operation on the cloud computing node. The virtual machine(s) may be relocated back to the cloud computing node after the maintenance operation is completed in response to a need to rebalance resources in such a manner. In this manner, maintenance operations may be performed on a cloud computing node without requiring to stop all the virtual machines in the node.

Abstract: A method, system and computer program product for performing maintenance operations on a cloud computing node. An administrative server receives an indication that a maintenance operation is to be performed on a cloud computing node. The administrative server identifies which virtual machine(s) on the cloud computing node will be affected by the maintenance operation. The administrative server relocates the virtual machine(s) to be affected by the maintenance operation to other suitable cloud computing node(s) prior to the maintenance operation being performed. The administrative server then performs the maintenance operation on the cloud computing node. The virtual machine(s) may be relocated back to the cloud computing node after the maintenance operation is completed in response to a need to rebalance resources in such a manner. In this manner, maintenance operations may be performed on a cloud computing node without requiring to stop all the virtual machines in the node.

Abstract: Methods, systems and computer program products are provided for converting a two-tier resource mapping to a one-tier resource mapping. A first mapping from intermediate data buffer to a data destination may be determined. A second mapping from a data source to the intermediate data buffer may also be determined. An optimized mapping from the data source to the data destination may be generated based on the first and second mappings. The optimized mapping may then be used instead of the first and second mappings to collect data from the data source to the data destination, thereby resulting in a one-tier resource mapping. In some instances, the mappings are sets of one or more queries.

Abstract: Converting a two-tier resource mapping to a one-tier resource mapping may include determining a first mapping from an intermediate data buffer to a data destination. A second mapping from a data source to the intermediate data buffer may also be determined. An optimized mapping from the data source to the data destination may be generated based on the first and second mappings. The optimized mapping may then be used instead of the first and second mappings to collect data from the data source to the data destination, thereby resulting in a one-tier resource mapping. In some instances, the mappings may be sets of one or more queries.

Abstract: A method, a system and a computer program product for defining manageable component objects to an application utilizing data roots. A manageable component engine creates a bridge manageable component model utilizing the data roots. Data roots, or root data, are retrieved and stored in a manageable component persistent index of an application. The manageable component persistent index is processed for one or more root objects during an initialization of a manageable component engine. The manageable component engine queries one or more data sources, and accesses data required for creating a manageable component object instance. One or more manageable component objects are registered in a manageable component repository. The manageable component bridge model is created and displayed via a graphical user interface.

Abstract: Methods, apparatuses, and computer program products are provided for acquiring guest operating system instrumentation information in a hypervisor. Embodiments include receiving from a platform management application, by a hypervisor communication module of the hypervisor, a platform request for guest operating system instrumentation information associated with at least one guest operating system executing within the hypervisor; in response to receiving the platform request for the guest operating system instrumentation information, retrieving through shared memory between the hypervisor and the guest operating system, by the hypervisor communication module, the guest operating system instrumentation information associated with the at least one guest operating system; and transmitting, by the hypervisor communication module, the guest operating system instrumentation information to the platform management application.

Abstract: Methods, systems and computer program products are provided for converting a two-tier resource mapping to a one-tier resource mapping. A first mapping from intermediate data buffer to a data destination may be determined. A second mapping from a data source to the intermediate data buffer may also be determined. An optimized mapping from the data source to the data destination may be generated based on the first and second mappings. The optimized mapping may then be used instead of the first and second mappings to collect data from the data source to the data destination, thereby resulting in a one-tier resource mapping. In some instances, the mappings are sets of one or more queries.

Abstract: A method, a system and a computer program product for defining manageable component objects to an application utilizing data roots. A manageable component engine creates a bridge manageable component model utilizing the data roots. Data roots, or root data, are retrieved and stored in a manageable component persistent index of an application. The manageable component persistent index is processed for one or more root objects during an initialization of a manageable component engine. The manageable component engine queries one or more data sources, and accesses data required for creating a manageable component object instance. One or more manageable component objects are registered in a manageable component repository. The manageable component bridge model is created and displayed via a graphical user interface.

Abstract: A computer implemented method, apparatus, and computer usable program code for balancing management loads. Loads are analyzed for a plurality of hardware control points to form an analysis in response to receiving a notification from a hardware control point indicating that a new manageable data processing system has been discovered. One of the plurality of hardware control points is selected using the analysis to form a selected hardware control point. The message is sent to the selected hardware control point to manage the new manageable data processing system, wherein the selected hardware control point manages the new manageable data processing system.

Abstract: This invention is useful in a networked system with densely packaged servers or server blades. The servers are connected to a system management network, a communication network and an image server. A management module attached to the system management network and a network switch monitors and controls network booting from an image server on the communication network to prevent over commitment of network and image server resources in order to avoid a boot storm. The management module collects system information and calculates the number of servers or clients the networked system can boot at any one instant of time without burdening the system. The management module logic controls booting via the system management network and service processor elements, which can block server booting and release servers to boot when other servers have completed their boot process.

Abstract: A method, computer program product, and system for allocating resources on computer systems are provided. The method, computer program product, and system provide for displaying a resource allocation matrix, the resource allocation matrix including a plurality of cells, each of the plurality of cells indicating a quantity of one of a plurality of resources on one of a plurality of physical systems allocated to one of a plurality of virtual systems hosted by the one physical system, receiving an input changing the quantity indicated in a cell, the cell indicating the quantity of a resource on a physical system allocated to a virtual system hosted by the physical system, and adjusting the quantity of the resource allocated to the virtual system based on the input.

Abstract: A method, system and computer program product for automatically switching remote shared devices in a dense server environment. A device driver in a server blade may be configured to receive a request to access a shared device from the server blade and issue a query to a service processor as to whether the requested shared device is being accessed. If the requested shared device is not being accessed by the requesting server blade, then the device driver may wait to receive a response from the service processor indicating that the requested shared device is available. Once the requested shared device is available, the service processor may connect the requested shared device with the requesting server blade. The request to access the requested shared device may then be transferred to the requested shared device by the device driver.

Abstract: A method, system and computer program product for remotely booting devices. A deployment server may remotely transmit authentication parameter(s), e.g., public key, secret key, to a service unit configured to establish a private connection between server blades and the deployment server. The service unit may remotely install the authentication parameter(s) onto the server blade(s) to be booted by either the deployment server or another boot server. By the service unit remotely installing the authentication parameter(s) onto the server blade(s), the need to manually install them during each network boot operation may be alleviated. By remotely transmitting authentication parameter(s) instead of manually installing them on the devices to be booted during each network boot operation, the deployment server may be able to generate unique authentication parameter(s), e.g., public/private key pair, secret key, for each network boot operation thereby substantially reducing the exposure to replay attacks.

Abstract: A method and system for providing performance analysis on a computer system is disclosed. The computer system includes at least one resource group and at least one node. The method and system include obtaining performance data for a plurality of monitors for the at least one resource group and analyzing the performance data to determine whether performance of the system can be improved using the at least one resource group. Preferably, performance is improved by moving the resource group between nodes. The method and system include graphically displaying the performance data graphically displaying performance data for at least one monitor of the plurality of monitors for the at least one resource group.

Abstract: A system for storing and configuring CMOS setting information remotely in a sewer blade environment includes a management module having includes persistent storage containing a table of CMOS setting information for each server blade. Each server blade includes boot block software that executes when the blade is booted. The boot block software initiates communication with the management module and retrieves its CMOS settings from the table. Thus, CMOS settings for a particular blade location remain unchanged each time a blade is replaced or upgraded. The management module and saver blades may implement a programming interface tat includes command abstractions for each CMOS setting. The management module sends command abstractions to each sewer blade during the CMOS configuration process. The server blade interprets the commands and maps the commands to specific CMOS bit addresses thereby making the specific CMOS implementation employed by any server blade transparent to the management module.

Abstract: A system for monitoring server blades includes a cabinet having a plurality of racks configured to receive a server blade. The server blade includes one or more microprocessors, memory, and a service processor all interconnected via one or more busses. The system includes a management blade to monitor the local service processors. Upon installation, a new blade identifies itself to the management blade by its physical slot position within the cabinet. In response to a reset, the local blade service processor determines from a tamper latch whether the blade has been removed from the chassis since the last power-on event. If the tamper latch is broken, the local service processor informs the management blade and resets the tamper latch. The local service processor of each blade may send a periodic heartbeat to the management blade, which monitors for loss of the heartbeat signal to determine when a blade is removed.

Abstract: A system and method for determining an active service processor from two or more redundant service processors in the system. The system typically includes two management modules and at least one managed subsystem such as a server blade. Each management module includes a service processor and control logic. The control logic is configured to receive various status signals from the service processor and to generate a control signal based thereon. The control signal is provided, via an interconnect plane, to determination logic on each managed subsystem. The determination logic receives a control signal from each management module and generates a switch signal based on the state of the control signals. The switch signal controls switching logic configured to receive bus signals from the service processors on each management module. Based on the control signal, one of the service processor bus signals is provided to managed instrumentation on the managed subsystem.

Abstract: This invention is comprised of a data processing system containing at least one main processor connected to a system bus, a system memory connected to the system bus and accessible to each of the main processors, a tamper mechanism, and a local service processor. The tamper mechanism is configured to change state each time the system is inserted into a slot in a rack enclosure. The local service processor is connected to the tamper mechanism and configured to update an insertion log upon detecting a change in state of the tamper mechanism. The insertion log provides a count and a history of rack insertions to which the system has been subjected. The system may include a non-volatile storage element which is updated exclusively by the local service processor that contains the insertion log. The insertion log may include an insertion counter. In this embodiment, the local service processor is configured to increment the insertion counter upon each insertion.

Abstract: This invention is useful in a networked system with densely packaged servers or server blades. The servers are connected to a system management network, a communication network and an image server. A management module attached to the system management network and a network switch monitors and controls network booting from an image server on the communication network to prevent over commitment of network and image server resources in order to avoid a boot storm. The management module collects system information and calculates the number of servers or clients the networked system can boot at any one instant of time without burdening the system. The management module logic controls booting via the system management network and service processor elements, which can block server booting and release servers to boot when other servers have completed their boot process.

Abstract: A method and system for storing and configuring CMOS setting information remotely in a server blade environment. The system includes a management module configured to act as a service processor to a data processing configuration comprising a set of one or more server blades sharing common resources such as system power and cooling fans. The management module includes persistent storage in which is stored a table containing CMOS setting information for each server blade in the configuration. Each server blade includes boot block software that executes when the blade is booted after power-on or system reset. The boot block software initiates communication with the management module and retrieves its CMOS settings from the management modules CMOS setting table. In this manner, CMOS settings for a particular blade location in the configuration remain unchanged each time a blade is replaced or upgraded.