Cluster partition handling during upgrade of a highly available application hosted in a data center

Patent metadata

Field	Value
Publication number	US-12314700-B2
Application number	US-202217979808-A
Country	US
Kind code	B2
Filing date	Nov 3, 2022
Priority date	Jul 18, 2022
Publication date	May 27, 2025
Grant date	May 27, 2025

Abstract

An example method of upgrading an application in a software-defined data center (SDDC) includes: deploying, by lifecycle management software executing in the SDDC, a second appliance, a first appliance executing services of the application at a first version, the second appliance having services of the application at a second version, the services in the first appliance being active and the services in the second appliance being inactive; setting, by the lifecycle management software, the first and second appliances as a preemptive pair, where the first appliance is protected and the second appliance is unprotected by fault domain management (FDM) software executing in the SDDC; performing, by the lifecycle management software, a switchover to stop the services of the first appliance and start the services of the second appliance; and setting, by the lifecycle management software, the first appliance as unprotected and the second appliance as protected by the FDM software.

First claim

What is claimed is:

1. A method of upgrading an application in a software-defined data center (SDDC), comprising:
deploying, by lifecycle management software executing in the SDDC, a first appliance and a second appliance, the first appliance executing services of the application at a first version, the second appliance having services of the application at a second version, the services in the first appliance being active and the services in the second appliance being inactive;
controlling, by the lifecycle management software, the first appliance and the second appliance as a preemptive pair, where the first appliance is protected and the second appliance is unprotected by fault domain management (FDM) software executing in the SDDC;
performing, by the lifecycle management software, a switchover to stop the services of the first appliance and start the services of the second appliance, the first appliance being set as unprotected and the second appliance being set as protected by the FDM software;
expanding, by the lifecycle management software, state of the first appliance to support both the services at the first version and the services at the second version;
replicating, by the lifecycle management software, the state of the first appliance to the second appliance; and
contracting, by the lifecycle management software, state of the second appliance to remove a portion thereof that is unused by the services at the second version.

2. The method of claim 1 , wherein the FDM software detects that the first appliance requires restart due to a failure prior to performing the switchover, and wherein the FDM software restarts the first appliance.

3. The method of claim 1 , wherein the FDM software detects that the first appliance requires restart due to a failure during the switchover, and wherein the FDM software selectively restarts the first appliance based on configuration data of the FDM software.

4. The method of claim 1 , wherein the FDM software detects that a host having the second appliance has failed prior to performing the switchover, and wherein the FDM software takes no action to restart the second appliance in response.

5. The method of claim 1 , wherein the FDM software detects that a host having the second appliance has failed during the switchover, and wherein the FDM software restarts the second appliance in response.

6. The method of claim 1 , wherein the first appliance and the second appliance are separated by a network partition, wherein the FDM software detects failure of either the first appliance or the second appliance, and wherein the FDM software selectively restarts either the first appliance or the second appliance depending on a version of configuration data of the first appliance compared with the second appliance.

7. A non-transitory computer readable medium comprising instructions to be executed in a computing device to cause the computing device to carry out a method of upgrading an application in a software-defined data center (SDDC), comprising:
deploying, by lifecycle management software executing in the SDDC, a first appliance and a second appliance, the first appliance executing services of the application at a first version, the second appliance having services of the application at a second version, the services in the first appliance being active and the services in the second appliance being inactive;
controlling, by the lifecycle management software, the first appliance and the second appliance as a preemptive pair, where the first appliance is protected and the second appliance is unprotected by fault domain management (FDM) software executing in the SDDC;
performing, by the lifecycle management software, a switchover to stop the services of the first appliance and start the services of the second appliance, the first appliance being set as unprotected and the second appliance being set as protected by the FDM software;
expanding, by the lifecycle management software, state of the first appliance to support both the services at the first version and the services at the second version;
replicating, by the lifecycle management software, the state of the first appliance to the second appliance; and
contracting, by the lifecycle management software, state of the second appliance to remove a portion thereof that is unused by the services at the second version.

8. The non-transitory computer readable medium of claim 7 , wherein the FDM software detects that the first appliance requires restart due to a failure prior to performing the switchover, and wherein the FDM software restarts the first appliance.

9. The non-transitory computer readable medium of claim 7 , wherein the FDM software detects that the first appliance requires restart due to a failure during the switchover, and wherein the FDM software selectively restarts the first appliance based on configuration data of the FDM software.

10. The non-transitory computer readable medium of claim 7 , wherein the FDM software detects that a host having the second appliance has failed prior to performing the switchover, and wherein the FDM software takes no action to restart the second appliance in response.

11. The non-transitory computer readable medium of claim 7 , wherein the FDM software detects that a host having the second appliance has failed during the switchover, and wherein the FDM software restarts the second appliance in response.

12. The non-transitory computer readable medium of claim 7 , wherein the first appliance and the second appliance are separated by a network partition, wherein the FDM software detects failure of either the first appliance or the second appliance, and wherein the FDM software selectively restarts either the first appliance or the second appliance depending on a version of configuration data of the first appliance compared with the second appliance.

13. A virtualized computing system, comprising:
at least one host having a hardware platform; and
a software platform executing on the hardware platform, the software platform including lifecycle management software configured to upgrade an application executing in a software-defined data center (SDDC), the lifecycle management software configured to:
deploy a first appliance and a second appliance, the first appliance executing services of the application at a first version, the second appliance having services of the application at a second version, the services in the first appliance being active and the services in the second appliance being inactive;
control the first appliance and the second appliance as a preemptive pair, where the first appliance is protected and the second appliance is unprotected by fault domain management (FDM) software executing in the SDDC;
perform a switchover to stop the services of the first appliance and start the services of the second appliance, the first appliance being set as unprotected and the second appliance being set as protected by the FDM software;
expand state of the first appliance to support both the services at the first version and the services at the second version;
replicate the state of the first appliance to the second appliance; and
contract state of the second appliance to remove a portion thereof that is unused by the services at the second version.

14. The virtualized computing system of claim 13 , wherein the FDM software is configured to detect that the first appliance requires restart due to a failure prior to performing the switchover, and wherein the FDM software is configured to restart the first appliance.

15. The virtualized computing system of claim 13 , wherein the FDM

Assignees

• VMware LLC

Inventors

• Sinha Sandeep
• Sakhardande Aniket Avinash
• Singh Rahul Kumar
• Mutalik Chandrika
• Kodenkiri Akash
• Tammana Vasantha Kumari

Classifications

• G06F8/71

  Version control (security arrangements therefor G06F21/57); Configuration management · CPC title

• G06F11/2023

  Failover techniques · CPC title

• G06F11/1433

  during software upgrading · CPC title

• G06F8/65 Primary

  Updates (security arrangements therefor G06F21/57) · CPC title