Managing power request during cluster operations

1. A method of handling power requests during cluster operations, the method comprising:

executing a delegated process on a network resource by a first controller of an information handling system (IHS) that is a node within a cluster of IHSs, the IHS having the first controller and a second controller;

determining, by the first controller of the IHS, that a request for a power operation of the IHS is received; and

in response to determining that the request for the power operation is received:

transferring the delegated process to another network resource managed by another node in the cluster;

scheduling the power operation using the second controller of the IHS, based on transference of the delegated process; and

preventing, during the transference of the delegated process, the IHS from (i) performing a power operation of the IHS and (ii) implementing of a new delegated process, the preventing comprising: disabling power operations for both the first controller and the second controller; ignoring any new power operation requests and any new delegated process requests prior to execution of the scheduled power operation by the first controller; and re-enabling power operations for both the first controller and the second controller on completion of the transferring of the delegated process.

2. The method of claim 1 , wherein executing the delegated process comprises supporting a selected one of a virtualization machine (VM) and a clustered service.

3. The method of the claim 1 , wherein transferring the delegated process comprises entering a reboot-in-process state that prevents both: (i) starting new delegated processes; and (ii) implementing the power operation.

4. The method of claim 1 , further comprising:

determining whether the delegated process has completed transference to another processing subsystem; and

in response to determining that the delegated process has completed transference:

entering a normal operation state that enables power operations by at least the first controller, the power operations begin a selected one of: (a) powering down; and (b) soft rebooting of the IHS.

5. The method of claim 1 , further comprising:

determining a time duration required to transfer the delegated process;

scheduling a reboot of the IHS based on the time duration; and

informing the second controller of the IHS of the scheduled reboot in response to receiving a power operation request.

6. The method of claim 5 , wherein:

the first controller comprises a host processor subsystem that reboots the IHS in response to the power operation only after completion of the transfer of the delegated process; and

the second controller comprises a remote access controller (RAC) that is enabled to cause the power operation of the host processor subsystem.

7. The method of claim 1 , further comprising:

generating, by the second controller, a power operation request to the first controller; and

communicating, by the first controller, a power operation enable or disable command to the second controller in response to receiving the power operation request and based on a current status of whether the first controller is processing the delegated process.

8. An information handling system (IHS) in a cluster of IHSs, the IHS comprising:

a network interface coupled to a network;

a first controller communicatively coupled, via the network interface, to a network resource that executes a delegated process;

a second controller communicatively coupled to the first controller and to the network interface, the second controller being configured to communicate a power operation request to the first controller;

a power operation utility that, when executed by the first controller, enables the IHS to:

determine that a request for a power operation of the IHS is received; and

in response to determining that the request for the power operation is received:

transfer the delegated process to another network resource managed by another node in the cluster;

schedule the power operation based on transference of the delegated process; and

prevent, during the transference of the delegated process, the IHS from (i) performing a power operation of the IHS and (ii) implementing of a new delegated process, wherein to prevent the performing and the implementing the IHS: disables power operations for both the first controller and the second controller; ignores any new power operation requests and any new delegated process requests prior to execution of the scheduled power operation by the first controller; and re-enables power operations for both the first controller and the second controller on completion of the transfer.

9. The IHS of claim 8 , wherein executing the delegated process comprises a selected one of a virtualization machine (VM) and a clustered service.

10. The IHS of claim 8 , wherein the first controller enables the IHS to enter a reboot-in-process state during transfer of the delegated process that prevents both: (i) starting new delegated processes; and (ii) implementing the power operation.

11. The IHS of claim 8 , wherein the first controller enables the IHS to:

determine whether the delegated process has completed the transference to another processing subsystem; and

in response to determining that the delegated process has completed the transference, enter a normal operation state that enables power operations by at least the first controller, the power operations begin a selected one of: (a) powering down; and (b) soft rebooting of the IHS.

12. The IHS of claim 8 , further comprising the second controller that is enabled to cause the power operation of the IHS, wherein the first controller enables the IHS to:

determine a time duration required to transfer the delegated process;

schedule a reboot of the first controller based on the time duration; and

inform the second controller of the IHS of the scheduled reboot in response to receiving a power operation request.

13. The IHS of claim 12 , wherein:

the first controller comprises a host processor subsystem that reboots the IHS in response to the power operation only after completion of the transfer of the delegated process; and

the second controller comprises a remote access controller (RAC) that is enabled to cause the power operation of the host processor subsystem.

14. A power operation controller of an information handling system (IHS) in a cluster of IHSs, the power operation controller comprising:

a network interface coupled to a network;

a memory containing a power operation utility;

a processor subsystem communicatively coupled to the network interface and the memory and that executes the power operation utility to cause the IHS to:

execute, via the network interface, a delegated process on a network resource;

determine that a request for a power operation of the IHS is received; and

in response to determining that the request for the power operation is received:

trigger a first controller to transfer the delegated process to another network resource managed by another node in the cluster;

schedule the power operation using a second controller of the IHS, based on transference of the delegated process; and

prevent, during the transference of the delegated process, the IHS from (i) performing a power operation of the IHS and (ii) implementing of a new delegated process, wherein to prevent the performing and the implementing, the power operation controller: disables power operations for both the first controller and the second controller; ignores any new power operation requests and any new delegated process requests prior to execution of the scheduled power operation; and re-enables power operations for both the first controller and the second controller on completion of the transfer.

15. The power operation controller of claim 14 , wherein executing the delegated process comprises a selected one of a virtualization machine (VM) and a clustered service.

16. The power operation controller of claim 14 , wherein the processor subsystem enables the IHS to enter a reboot-in-process state during transfer of the delegated process that prevents both: (i) starting new delegated processes; and (ii) implementing the power operation.

17. The power operation controller of claim 14 , wherein the processor subsystem enables the IHS to:

determine whether the delegated process has completed the transference to another processing subsystem; and

in response to determining that the delegated process has completed the transference, enter a normal operation state that enables power operations by at least the processor subsystem, the power operations begin a selected one of: (a) powering down; and (b) soft rebooting of the IHS.

18. The power operation controller of claim 14 , wherein the processor subsystem comprises:

the first controller that executes the delegated process; and

the second controller that is enabled to cause the power operation of the IHS, wherein the first controller enables the IHS to:

determine a time duration required to transfer the delegated process;

schedule a reboot of the first controller based on the time duration; and

inform the second controller of the IHS of the scheduled reboot in response to receiving a power operation request.

19. The power operation controller of claim 18 , wherein:

the first controller comprises a host processing subsystem that reboots the IHS in response to the power operation only after completion of the transfer of the delegated process; and

the second controller comprises a remote access controller (RAC) that is enabled to cause the power operation of the host processing subsystem.

20. The power operation controller of claim 19 , wherein the processor subsystem comprises:

system memory that is used by the host processing subsystem; and

a RAC service manager contained in the system memory and executed by the host processor subsystem to communicatively couple to the RAC, wherein the RAC is communicatively coupled, via the network interface, to a customer system and enables the IHS to:

determine whether a power operation request is received from the customer system; and

in response to determining that the power operation request is received from the customer system:

communicate the power operation request with the host processor subsystem via the RAC service manager to prompt transfer of the delegated process by the host processor subsystem;

receive a reboot schedule from the host processor subsystem; and

ignore any power operation requests and any new delegated process requests prior to execution of the power operation by the host processor subsystem.