System and method for relocating customer virtual machine instances in a multi-tenant cloud service

A non-transitory computer-readable medium storing computer-executable instructions that, when executed by at least a processor of a computer, cause the computer to:

• generate a graphical user interface on a display screen, wherein the graphical user interface is associated with monitoring and controlling a maintenance of a source compute node;
• in response to a system administrator interaction with the graphical user interface, access an application programming interface (API);
• in response to accessing the API, execute the API, through at least the processor accessing one or more memories, such that the application programming interface includes instructions configured for controlling execution of maintenance of source nodes by;
• establishing a maintenance schedule of a source node, wherein a selected maintenance is to be performed on the source node, and wherein the maintenance schedule specifies a prescheduled time to begin maintenance of the source node;
• in response to arriving at the prescheduled time, automatically performing the following steps:
• assigning a maintenance tag to the source node when the selected maintenance is to be performed in accordance with the established maintenance schedule;
• identifying one or more virtual machine instances that are configured on the source node and will be affected by the maintenance schedule;
• selecting a target node that is available to host the one or more virtual machine instances of the source node;
• updating, by the API, a source node property that disables new virtual machine instances from launching on the source node;
• determining, by the API, a source node profile and source node properties;
• applying, by the API, the source node profile and the source node properties to the target node;
• relocating the one or more virtual machine instances from the source node to the target node to vacate the source node of virtual machine instances prior to performing the selected maintenance on the source node;
• in response to the relocating, re-initiating run-time execution of the one or more virtual machines on the target node;
• verifying, by the API, that the one or more virtual machine instances are running on the target node;
• in response to the verifying, performing the selected maintenance on the source node;
• in response to completing the selected maintenance on the source node, removing, by the API, the maintenance tag from the source node and adding, by the API, the source node to an available node pool.

A computing system, comprising:

• a display screen having a graphical user interface, wherein the graphical user interface is associated with monitoring and controlling a maintenance of a source compute node;
• at least an application programming interface (API) accessible by the graphical user interface by a system administrator, wherein the API is connected to at least one processor connected to at least one memory comprising a non-transitory computer readable medium;
• and
• a multi-tenant control module stored on the memory and including instructions that, when executed by the at least one processor, cause the at least one processor to:
• execute the application programming interface (API), through the at least one processor accessing one or more memories, wherein the application programming interface controls execution of maintenance of a source node by;
• establishing a maintenance schedule of a source node, wherein a selected maintenance is to be performed on the source node, and wherein the maintenance schedule specifies a prescheduled time to begin maintenance of the source node;
• in response to arriving at the prescheduled time, automatically performing the following steps:
• assigning a maintenance tag to the source node when the selected maintenance is to be performed in accordance with the established maintenance schedule;
• identifying one or more virtual machine instances that are configured on the source node and that will be affected by the maintenance schedule;
• selecting a target node that is available to host the one or more virtual machine instances of the source node;
• updating, by the API, a source node property in order to disable new virtual machine instance launches on the source node;
• determining, by the API, a source node profile and source node properties;
• applying, by the API, the source node profile and the source node properties to the target node;
• live migrating the one or more virtual machine instances from the source node to the target node to vacate the source node of virtual machine instances prior to performing the selected maintenance on the source node;
• in response to the live migrating, re-initiating run-time execution of the one or more virtual machines on the target node;
• verifying, by the API, that the one or more virtual machine instances are running on the target node;
• in response to the verifying, performing the selected maintenance on the source node;
• in response to completing the selected maintenance on the source node, removing, by the API, the maintenance tag from the source node and adding, by the API, the source node to an available node pool.