ZERO-DOWNTIME CLOUD CONNECTOR UPGRADES

• US 20170153885A1
• Filed: 12/01/2015
• Published: 06/01/2017
• Est. Priority Date: 12/01/2015
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Regan, Gregory John, Cooper, Andrew John
• Granted Patent: US 10,021,171 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 8/656 while running
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

Presented herein are zero-downtime upgrade techniques for cloud connector/extension software components. In particular, an on-premises node that runs a first version of a cloud connector software component, receives a second version of the cloud connector software component from a cloud-based software platform. The second version of the cloud connector software component is installed and initialized at the on-premises node such that the first and second versions of the cloud connector software component run in parallel at the on-premises node. Management of the subscriptions of the on-premises services to the cloud-based software platform is then transferred from the first version of the cloud connector software component to the second version of the cloud connector software component.

Claims

1. A method comprising:

at an on-premises node running a first version of a cloud connector software component, receiving a second version of the cloud connector software component from a cloud-based software platform, where the first version of the cloud connector software component is associated with subscriptions of the cloud-based software platform to on-premises services;

installing and initializing the second version of the cloud connector software component at the on-premises node such that the second version of the cloud connector software component runs in parallel with the first version of the cloud connector software component at the on-premises node; and

migrating subscriptions of the cloud-based software platform to the on-premises services from the first version of the cloud connector software component to the second version of the cloud connector software component.

2. The method of claim 1, wherein prior to migrating the subscriptions from the first version of the cloud connector software component to the second version of the cloud connector software component, the method further comprises:

performing end-to-end verification of the second version of the cloud connector software component, wherein the end-to-end verification is configured to confirm that the second version of the cloud connector software can communicate with both the cloud-based software platform and the on-premises services.

3. The method of claim 2, further comprising:

determining that the end-to-end verification was successful such that the second version of the cloud connector software can communicate with both the cloud-based software platform and the on-premises services; and

migrating the subscriptions from the first version of the cloud connector software component to the second version of the cloud connector software component only when it is determined that the updated version of the cloud connector software can communicate with both the cloud-based software platform and the on-premises services.

4. The method of claim 2, further comprising:

determining that the end-to-end verification was unsuccessful such that the second version of the cloud connector software cannot communicate with at least one of the cloud-based software platform or the on-premises services; and

preventing migration of the subscriptions from the first version of the cloud connector software component to the second version of the cloud connector software component.

5. The method of claim 1, wherein migration of the subscriptions is orchestrated by the cloud-based software platform.

6. The method of claim 1, wherein the on-premises node includes a local proxy configured to dynamically direct local inbound traffic to one of the first version of the cloud connector software component or the second version of the cloud connector software component during transfer of the subscriptions from the first version of the cloud connector software component to the second version of the cloud connector software component.

7. The method of claim 6, further comprising:

following installing and initializing the second version of the cloud connector software component at the on-premises node, registering a local port address of the second version of the cloud connector software component with the local proxy.

8. An apparatus comprising:

at least one network interface port;

a memory comprising a first version of a cloud connector software component; and

a processor configured to;

run the first version of a cloud connector software component, where the first version of the cloud connector software component is associated with subscriptions of a cloud-based software platform to on-premises services,

receive second version of the cloud connector software component from the cloud-based software platform via the at least one network interface port,

install and initialize the second version of the cloud connector software component such that the second version of the cloud connector software component runs in parallel with the first version of the cloud connector software component; and

migrate, under the control of the cloud-based software platform, subscriptions of the cloud-based software platform to the on-premises services from the first version of the cloud connector software component to the second version of the cloud connector software component.

9. The apparatus of claim 8, wherein prior to migrating the subscriptions from the first version of the cloud connector software component to the second version of the cloud connector software component, the processor is configured to:

perform end-to-end verification of the second version of the cloud connector software component, wherein the end-to-end verification is configured to confirm that the second version of the cloud connector software can communicate with both the cloud-based software platform and the on-premises services.

10. The apparatus of claim 9, wherein the processor is configured to:

determine that the end-to-end verification was successful such that the second version of the cloud connector software can communicate with both the cloud-based software platform and the on-premises services; and

migrate the subscriptions from the first version of the cloud connector software component to the second version of the cloud connector software component only when it is determined that the updated version of the cloud connector software can communicate with both the cloud-based software platform and the on-premises services.

11. The apparatus of claim 9, wherein the processor is configured to:

determine that the end-to-end verification was unsuccessful such that the second version of the cloud connector software cannot communicate with at least one of the cloud-based software platform or the on-premises services; and

prevent migration of the subscriptions from the first version of the cloud connector software component to the second version of the cloud connector software component.

12. The apparatus of claim 8, wherein the processor is further configured to execute a local proxy that is configured to dynamically direct local inbound traffic to one of the first version of the cloud connector software component or the second version of the cloud connector software component during transfer of the subscriptions from the first version of the cloud connector software component to the second version of the cloud connector software component.

13. The apparatus of claim 12, wherein following installing and initializing the second version of the cloud connector software component, the processor is configured to register a local port address for the second version of the cloud connector software component with the local proxy.

14. One or more non-transitory computer readable storage media encoded with instructions that, when executed by a processor, cause the processor to:

at an on-premises node running a first version of a cloud connector software component, receive a second version of the cloud connector software component from a cloud-based software platform, where the first version of the cloud connector software component is associated with subscriptions of the cloud-based software platform to on-premises services;

install and initialize the second version of the cloud connector software component at the on-premises node such that the second version of the cloud connector software component runs in parallel with the first version of the cloud connector software component at the on-premises node; and

migrate subscriptions of the cloud-based software platform to the on-premises services from the first version of the cloud connector software component to the second version of the cloud connector software component.

15. The non-transitory computer readable storage media of claim 14, wherein prior to migrating the subscriptions from the first version of the cloud connector software component to the second version of the cloud connector software component, the non-transitory computer readable storage media further instructions that, when executed by a processor, cause the processor to:

perform end-to-end verification of the second version of the cloud connector software component, wherein the end-to-end verification is configured to confirm that the second version of the cloud connector software can communicate with both the cloud-based software platform and the on-premises services.

16. The transitory computer readable storage media of claim 15, further comprising instructions that, when executed by a processor, cause the processor to:

determine that the end-to-end verification was successful such that the second version of the cloud connector software can communicate with both the cloud-based software platform and the on-premises services; and

migrate the subscriptions from the first version of the cloud connector software component to the second version of the cloud connector software component only when it is determined that the updated version of the cloud connector software can communicate with both the cloud-based software platform and the on-premises services.

17. The transitory computer readable storage media of claim 15, further comprising instructions that, when executed by a processor, cause the processor to:

determine that the end-to-end verification was unsuccessful such that the second version of the cloud connector software cannot communicate with at least one of the cloud-based software platform or the on-premises services; and

prevent migration of the subscriptions from the first version of the cloud connector software component to the second version of the cloud connector software component.

18. The non-transitory computer readable storage media of claim 14, wherein migration of the subscriptions is orchestrated by the cloud-based software platform.

19. The non-transitory computer readable storage media of claim 14, wherein the on-premises node includes a local proxy configured to dynamically direct local inbound traffic to one of the first version of the cloud connector software component or the second version of the cloud connector software component during transfer of the subscriptions from the first version of the cloud connector software component to the second version of the cloud connector software component.

20. The non-transitory computer readable storage media of claim 19, further comprising instructions that, when executed by a processor, cause the processor to:

following install and initialization of the second version of the cloud connector software component at the on-premises node, register a local port address of the second version of the cloud connector software component with the local proxy.