Reduced downtime during upgrade of an application hosted in a data center
A 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; 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; 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 contracting, by the lifecycle management software, state of the second appliance to remove a portion unused by the services at the second version.
1. A method of upgrading an application in a software-defined data center (SDDC), comprising:
performing an in-place upgrade of a lifecycle management software executing in the SDDC from a first version to a second version;
deploying, by the lifecycle management software, a second appliance, wherein a first appliance executes services of the application at a first version of the application, wherein the second appliance executes services of the application at a second version of the application, and wherein the services of the application in the first appliance are active and the services of the application in the second appliance are inactive;
expanding, by the lifecycle management software, a state of the first appliance to support both the services of the application at the first version of the application and the services of the application at the second version of the application;
replicating, by the lifecycle management software, the state of the first appliance to the second appliance;
performing, by the lifecycle management software, a switchover to stop the services of the application in the first appliance and to start the services of the application in the second appliance; and
contracting, by the lifecycle management software, a state of the second appliance to remove a portion unused by the services of the application at the second version of the application.
2. The method of claim 1 , wherein the lifecycle management software includes a lifecycle manager executing on the first appliance.
3. The method of claim 1 , wherein the step of expanding comprises expanding a schema of a database executing in the first appliance to support both the services of the application at the first version of the application and the services of the application at the second version of the application.
4. The method of claim 1 , wherein the step of expanding comprises expanding a configuration file of the first appliance to support both a service at the first version of the application and a service at the second version of the application.
5. The method of claim 1 , wherein the step of replicating comprises replicating a database executing in the first appliance at the first version of the application to a database executing in the second appliance at the second version of the application.
6. The method of claim 1 , wherein the step of replicating comprises copying a state of the application from the first appliance to the second appliance, wherein the state of the application includes a user file portion of a configuration file, and wherein the configuration file includes a template portion at the first version of the application in the first appliance and a template portion at the second version of the application in the second appliance.
7. The method of claim 1 , wherein the step of contracting comprises contracting a schema of a database executing in the second appliance to remove a portion unused by the services of the application at the second version of the application.
8. The method of claim 1 , wherein a network identity of the application is preserved during the switchover.
9. A non-transitory computer readable medium storing instructions to be executed in a computing device to cause the computing device to perform a method of upgrading an application in a software-defined data center (SDDC), comprising:
performing an in-place upgrade of a lifecycle management software executing in the SDDC from a first version to a second version;
deploying, by the lifecycle management software, a second appliance, wherein a first appliance executes services of the application at a first version of the application, wherein the second appliance executes services of the application at a second version of the application, and wherein the services of the application in the first appliance are active and the services of the application in the second appliance are inactive;
expanding, by the lifecycle management software, a state of the first appliance to support both the services of the application at the first version of the application and the services of the application at the second version of the application;
replicating, by the lifecycle management software, the state of the first appliance to the second appliance;
performing, by the lifecycle management software, a switchover to stop the services of the application in the first appliance and to start the services of the application in the second appliance; and
contracting, by the lifecycle management software, a state of the second appliance to remove a portion unused by the services of the application at the second version of the application.
10. The non-transitory computer readable medium of claim 9 , wherein the lifecycle management software includes a lifecycle manager executing on the first appliance.
11. The non-transitory computer readable medium of claim 9 , wherein the step of expanding comprises expanding a schema of a database executing in the first appliance to support both the services of the application at the first version of the application and the services of the application at the second version of the application.
12. The non-transitory computer readable medium of claim 9 , wherein the step of expanding comprises expanding a configuration file of the first appliance to support both a service at the first version of the application and a service at the second version of the application.
13. The non-transitory computer readable medium of claim 9 , wherein the step of replicating comprises replicating a database executing in the first appliance at the first version of the application to a database executing in the second appliance at the second version of the application.
14. The non-transitory computer readable medium of claim 9 , wherein the step of replicating comprises copying a state of the application from the first appliance to the second appliance, wherein the state of the application includes a user file portion of a configuration file, and wherein the configuration file includes a template portion at the first version of the application in the first appliance and a template portion at the second version of the application in the second appliance.
15. The non-transitory computer readable medium of claim 9 , wherein the step of contracting comprises contracting a schema of a database executing in the second appliance to remove a portion unused by the services of the application at the second version of the application.
16. 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 a lifecycle management software configured to upgrade an application executing in a software-defined data center (SDDC), the lifecycle management software configured to:
perform an in-place upgrade of the lifecycle management software from a first version to a second version;
deploy a second appliance, wherein a first appliance executes services of the application at a first version of the application, wherein the second appliance executes services of the application at a second version of the application, and wherein the services of the application in the first appliance are active and the services of the application in the second appliance are inactive;
expand a state of the first appliance to support both the services of the application at the first version of the application and the services of the application at the second version of the application;
replicate the state of the first appliance to the second appliance;
perform a switchover to stop the services of the application in the first appliance and to start the services of the application in the second appliance; and
contract a state of the second appliance to remove a portion unused by the services of the application at the second version of the application.
17. The virtualized computing system of claim 16 , wherein the lifecycle management software includes a lifecycle manager executing on the first appliance.
18. The virtualized computing system of claim 16 , wherein the step of expanding comprises expanding a schema of a database executing in the first appliance to support both the services of the application at the first version of the application and the services of the application at the second version of the application.
19. The virtualized computing system of claim 16 , wherein the step of expanding comprises expanding a configuration file of the first appliance to support both a service at the first version of the application and a service at the second version of the application.
20. The virtualized computing system of claim 16 , wherein the step of replicating comprises replicating a database executing in the first appliance at the first version of the application to a database executing in the second appliance at the second version of the application.