Abstract: Mechanisms are provided, in a bare metal computing device, for executing a network based boot operation for booting the bare metal computing device. In response to powering-on the bare metal computing device, firmware is executed that executes a stub from a virtual media image accessible by the bare metal computing device. The configuration information of the bare metal computing device indicates that the bare metal computing device is being booted from a local media. The stub configures the firmware environment and a network boot program to utilize a network connection by modifying the configuration information of the bare metal computing device to indicate that the bare metal computing device is being booted from a network device. A control program is obtained from a remotely located boot server using the network boot program and is executed to complete the booting of the bare metal computing device.

Abstract: A vital product data (VPD) system is connected to a network, allowing the VPD system to be accessed for inquiries about VPD. The VPD system includes a baseboard management controller (BMC), a VPD cache, a platform initialization system and a tamper detection switch. The BMC communicates with the tamper detection switch and sets a VPD flag to false when tampering is detected. Queries to the BMC through the network for VPD are then held pending and the VPD cache refreshed with a no-boot power on, using the platform initialization system to collect the new VPD capturing the nature of any modifications after tampering.

Abstract: A mechanism is provided for improved firmware storage and maintenance. For each master device in a plurality of master devices: an amount of Flash memory space required by the master device is identified and the amount of Flash memory space from a Flash component is allocated to the master device as a virtual Flash memory allocation. An initial sector location of the virtual Flash memory allocation in a data structure is recorded as an offset into the Flash component and a length of the virtual Flash memory allocation and device information is also recorded in the data structure. Data that allows the master device to boot up is then loaded into the virtual Flash memory allocation.

Abstract: A mechanism is provided for improved firmware storage and maintenance. For each master device in a plurality of master devices: an amount of flash memory space required by the master device is identified and the amount of Flash memory space from a Flash component is allocated to the master device as a virtual Flash memory allocation. An initial sector location of the virtual Flash memory allocation in a data structure is recorded as an offset into the Flash component and a length of the virtual Flash memory allocation and device information is also recorded in the data structure. Data that allows the master device to boot up is then loaded into the virtual Flash memory allocation.

Abstract: A mechanism is provided for enhancing remote presence capabilities. An update event for a main management module that manages a set of remote presence sessions for remote media established by a plurality of client systems is identified. A determination is made as to whether the main management module is currently maintaining a remote presence session for a remote media established by one of the plurality of client systems. Responsive to the main management module maintaining a remote presence session for the remote media, a handoff of the remote presence session for the remote media is initiated to an auxiliary management module. An update associated with the update event is then permitted to be performed on the main management module while maintaining the remote presence session for the remote media via the auxiliary management module.

Abstract: A mechanism is provided for enhancing remote presence capabilities. An update event for a main management module that manages a set of remote presence sessions for remote media established by a plurality of client systems is identified. A determination is made as to whether the main management module is currently maintaining a remote presence session for a remote media established by one of the plurality of client systems. Responsive to the main management module maintaining a remote presence session for the remote media, a handoff of the remote presence session for the remote media is initiated to an auxiliary management module. An update associated with the update event is then permitted to be performed on the main management module while maintaining the remote presence session for the remote media via the auxiliary management module.

Abstract: A method, apparatus, and computer program product for virtualizing baseboard management controller (‘BMC’) operation in a host computer comprising a base BMC is provided. Example embodiments include executing, by the host computer, a virtual BMC; registering, by the virtual BMC, with the base BMC of the host computer; and processing BMC requests sent to the base BMC by the virtual BMC. In some example embodiments, prior to registration of the virtual BMC, BMC requests are processed by the base BMC. Some other example embodiments include determining, by the base BMC, periodically at a predefined period of time, whether the virtual BMC is active; and upon the base BMC determining that the virtual BMC is not active: deregistering, by the base BMC, the virtual BMC; and processing subsequently received BMC requests by the base BMC.

Abstract: A rapid provisioning method for connecting to a cloud, copying blocks of a virtual machine image to the cloud and booting the virtual machine image in the cloud, wherein some aspects of copying the blocks and booting the virtual machine are contemporaneous or overlap. The method may include starting with copying the blocks of the virtual machine and continuing to copy the blocks of the virtual machine image while the virtual machine image boots in the cloud. The method may also include starting with booting the virtual machine in the cloud from the customer computer and continuing to boot while copying the blocks transferred during boot to cloud storage.

Abstract: A mechanism is provided for improved firmware storage and maintenance. For each master device in a plurality of master devices: an amount of Flash memory space required by the master device is identified and the amount of Flash memory space from a Flash component is allocated to the master device as a virtual Flash memory allocation. An initial sector location of the virtual Flash memory allocation in a data structure is recorded as an offset into the Flash component and a length of the virtual Flash memory allocation and device information is also recorded in the data structure. Data that allows the master device to boot up is then loaded into the virtual Flash memory allocation.

Abstract: A mechanism is provided for improved firmware storage and maintenance. For each master device in a plurality of master devices: an amount of flash memory space required by the master device is identified and the amount of Flash memory space from a Flash component is allocated to the master device as a virtual Flash memory allocation. An initial sector location of the virtual Flash memory allocation in a data structure is recorded as an offset into the Flash component and a length of the virtual Flash memory allocation and device information is also recorded in the data structure. Data that allows the master device to boot up is then loaded into the virtual Flash memory allocation.

Abstract: A method for enabling control in a cloud computing environment includes initializing a portion of computing resources identified for enabling service to a user system in a cloud computing environment. The method may also include enabling service to the user system. Further, the method may include initializing another portion of the computing resources. After the service in the cloud computing environment has been enabled, cloud computing services may be provided by the host system to one or more user systems.

Abstract: A mechanism is provided for enhancing remote presence capabilities. An update event for a main management module that manages a set of remote presence sessions for remote media established by a plurality of client systems is identified. A determination is made as to whether the main management module is currently maintaining a remote presence session for a remote media established by one of the plurality of client systems. Responsive to the main management module maintaining a remote presence session for the remote media, a handoff of the remote presence session for the remote media is initiated to an auxiliary management module. An update associated with the update event is then permitted to be performed on the main management module while maintaining the remote presence session for the remote media via the auxiliary management module.

Abstract: A mechanism is provided for enhancing remote presence capabilities. An update event for a main management module that manages a set of remote presence sessions for remote media established by a plurality of client systems is identified. A determination is made as to whether the main management module is currently maintaining a remote presence session for a remote media established by one of the plurality of client systems. Responsive to the main management module maintaining a remote presence session for the remote media, a handoff of the remote presence session for the remote media is initiated to an auxiliary management module. An update associated with the update event is then permitted to be performed on the main management module while maintaining the remote presence session for the remote media via the auxiliary management module.

Abstract: A chassis is selected from one or more chassis. Each chassis has one or more computing devices installed therein. A computing device is selected from the computing devices installed in the selected chassis. Each computing device is connected to one or more switches within the chassis. A switch is selected from the switches to which the selected computing device is connected. Each switch is connected to a storage-area network (SAN) encompassing one or more SAN storage devices. A SAN storage device is selected from the SAN storage devices connected to the selected switch. Network settings for the selected SAN storage device and/or the selected computing device are configured. The selected SAN storage device is configured for use by the selected computing device. An operating system (OS) instance is selected and deployed onto the selected SAN storage device for use by the selected computing device.

Abstract: Mechanisms for executing a bare metal boot operation for bare metal booting a control program are provided. These mechanisms boot a computing device to a hypervisor ownership phase of the bare metal boot operation. During the hypervisor ownership phase of the bare metal boot operation a hypervisor is loaded and controls and manages platform hardware of the computing device. The computing device is then booted from the hypervisor ownership phase to a transition phase in which the hypervisor releases control and management of the platform hardware of the computing device to the control program. The computing device is then booted from the transition phase to a control program ownership phase in which the control program is in full control and manages the platform hardware. The bare metal boot operation is performed without restarting the computing device and without cycling through initialization of firmware.

Abstract: Mechanisms are provided, in a bare metal computing device, for executing a network based boot operation for booting the bare metal computing device. In response to powering-on the bare metal computing device, firmware is executed that executes a stub from a virtual media image accessible by the bare metal computing device. The configuration information of the bare metal computing device indicates that the bare metal computing device is being booted from a local media. The stub configures the firmware environment and a network boot program to utilize a network connection by modifying the configuration information of the bare metal computing device to indicate that the bare metal computing device is being booted from a network device. A control program is obtained from a remotely located boot server using the network boot program and is executed to complete the booting of the bare metal computing device.

Abstract: Mechanisms for executing a bare metal boot operation for bare metal booting a control program are provided. These mechanisms boot a computing device to a hypervisor ownership phase of the bare metal boot operation. During the hypervisor ownership phase of the bare metal boot operation a hypervisor is loaded and controls and manages platform hardware of the computing device. The computing device is then booted from the hypervisor ownership phase to a transition phase in which the hypervisor releases control and management of the platform hardware of the computing device to the control program. The computing device is then booted from the transition phase to a control program ownership phase in which the control program is in full control and manages the platform hardware. The bare metal boot operation is performed without restarting the computing device and without cycling through initialization of firmware.

Abstract: Virtualizing baseboard management controller operation in a host computer that includes a base BMC, where virtualizing BMC operation includes executing, by the host computer, a virtual BMC; registering, by the virtual BMC, with the base BMC of the host computer; and processing BMC requests by the virtual BMC.

Abstract: A vital product data (VPD) system is connected to a network, allowing the VPD system to be accessed for inquiries about VPD. The VPD system includes a baseboard management controller (BMC), a VPD cache, a platform initialization system and a tamper detection switch. The BMC communicates with the tamper detection switch and sets a VPD flag to false when tampering is detected. Queries to the BMC through the network for VPD are then held pending and the VPD cache refreshed with a no-boot power on, using the platform initialization system to collect the new VPD capturing the nature of any modifications after tampering.

Abstract: A rapid provisioning method for connecting to a cloud, copying blocks of a virtual machine image to the cloud and booting the virtual machine image in the cloud, wherein some aspects of copying the blocks and booting the virtual machine are contemporaneous or overlap. The method may include starting with copying the blocks of the virtual machine and continuing to copy the blocks of the virtual machine image while the virtual machine image boots in the cloud. The method may also include starting with booting the virtual machine in the cloud from the customer computer and continuing to boot while copying the blocks transferred during boot to cloud storage.