CLOUD ORCHESTRATED CLOUD CONNECTOR UPGRADES

• US 20170155550A1
• 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: Cooper, Andrew John
• Granted Patent: US 10,110,434 B2
• Time in Patent Office: Days
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/0859 by keeping history of different configuration generations or by rolling back to previous configuration versions
• CPC Class Codes: H04L 41/0873 Checking configuration conflicts between network elements
• CPC Class Codes: H04L 41/0886 Fully automatic configuration
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]

Abstract

Presented herein are techniques for orchestrating an update of an on-premises cloud connector from a cloud-based software platform. In particular, a first version of a first cloud connector is running in an active-active configuration across first and second nodes in an on-premises cluster. The first cloud connector is associated with user subscriptions to a first on-premises application and the first cloud connector connects the first on-premises application to a first cloud service hosted at a cloud-based software platform application. The first cloud connector is updated from the first version to a second version on each of the first and second nodes in a sequential manner. The update of the first cloud connector from the first version to the second version is initiated at the cloud-based software platform.

Claims

1. A method comprising:

running first and second instances of a first version of a first cloud connector at first and second nodes, respectively, in an on-premises cluster, wherein the first cloud connector is associated with user subscriptions to a first on-premises application and wherein the first cloud connector connects the first on-premises application to a first cloud service hosted at a cloud-based software platform application; and

updating the first cloud connector from the first version to a second version on each of the first and second nodes in a sequential manner,

wherein the updating of the first cloud connector from the first version to the second version is initiated at the cloud-based software platform.

2. The method of claim 1, wherein a sequence for updating the first cloud connector at each of the first and second nodes is determined by the cloud-based software platform.

3. The method of claim 1, wherein updating the first cloud connector from the first version to a second version on each of the first and second nodes in a sequential manner includes:

receiving, at the first node, the second version of the first cloud connector from the cloud-based software platform,

deactivating the first version of the first cloud connector;

installing and initializing the second version of the first cloud connector at the first node.

4. The method of claim 3, further comprising:

temporarily re-assigning a subscription associated with the first cloud connector at the first node to an instance of the first cloud connector at a third node in the on-premises cluster during upgrade of the first cloud connector at the first node from the first version to the second version.

5. The method of claim 3, further comprising:

performing end-to-end verification of the second version of the first cloud connector at the first node, wherein the end-to-end verification is configured to confirm that the second version of the cloud connector can communicate with both the first cloud service and the first on-premises application.

6. The method of claim 5, further comprising:

determining that the end-to-end verification was successful such that that the second version of the first cloud connector can communicate with both the first cloud service and the first on-premises application; and

notifying the cloud-based software platform that second version of the first cloud connector is active at the first node.

7. The method of claim 5, further comprising:

determining that the end-to-end verification was unsuccessful such that the second version of the first cloud connector cannot communicate with at least one of the first cloud service or the first on-premises application;

uninstalling the second version of the first cloud connector;

reinstalling and reinitializing the first version of the first cloud connector; and

notifying the cloud-based software platform that the upgrade to the second version of the first cloud connector was unsuccessful.

8. The method of claim 1, further comprising:

running a first version of a second cloud connector at the first and second nodes, respectively, in the on-premises cluster, wherein the second cloud connector is associated with subscriptions of a second on-premises application and wherein the second cloud connector connects the second on-premises application to a second cloud service hosted at the cloud-based software platform; and

updating the second cloud connector from the first version to a second version on each of the first and second nodes in a sequential manner,

wherein the updating of the first cloud connector from the first version to the second version of the first cloud connector and the update of the second cloud connector from the first version to the second version of the second cloud connector occur simultaneously in the on-premises cluster.

9. The method of claim 1, wherein the first and second instances of the first version of the first cloud connector run in an active-active configuration across the first and second nodes.

10. The method of claim 1, further comprising:

prior to updating the first cloud connector from the first version to the second version on each of the first and second nodes, performing an upgrade test to ensure that all of the instances of the first cloud connector are running on the first and second nodes.

11. An apparatus in an on-premises cluster, comprising:

at least one network interface port;

a memory; and

a processor configured to;

run a first instance of a first version of a first cloud connector, wherein the first cloud connector is associated with user subscriptions to a first on-premises application, the first cloud connector connects the first on-premises application to a first cloud service hosted at a cloud-based software platform application, and a second instance of the first version of the first cloud connector also runs at a second apparatus in the on-premises cluster,

receive a second version of the first cloud connector from the cloud-based software platform,

deactivate the first version of the first cloud connector, and

install and initialize the second version of the first cloud connector at the first node.

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

transfer a subscription associated with the first instance of the first cloud connector to an instance of the first cloud connector at a third apparatus in the on-premises cluster during upgrade of the first cloud connector from the first version to the second version.

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

perform end-to-end verification of the second version of the first cloud connector at the first node, wherein the end-to-end verification is configured to confirm that the second version of the cloud connector can communicate with both the first cloud service and the first on-premises application.

14. The apparatus of claim 13, wherein the processor is configured to:

determine that the end-to-end verification was successful such that that the second version of the first cloud connector can communicate with both the first cloud service and the first on-premises application; and

notify the cloud-based software platform that second version of the first cloud connector is active at the first node.

15. The apparatus of claim 13, wherein the processor is configured to:

determine that the end-to-end verification was unsuccessful such that the second version of the first cloud connector cannot communicate with at least one of the first cloud service or the first on-premises application;

uninstall the second version of the first cloud connector;

reinstall and reinitializing the first version of the first cloud connector; and

notify the cloud-based software platform that the upgrade to the second version of the first cloud connector was unsuccessful.

16. One or more non-transitory computer readable storage media encoded with instructions that, when executed by one or more processors, cause the one or more processors to:

run first and second instances of a first version of a first cloud connector at first and second nodes, respectively, in an on-premises cluster, wherein the first cloud connector is associated with user subscriptions to a first on-premises application and wherein the first cloud connector connects the first on-premises application to a first cloud service hosted at a cloud-based software platform application; and

update the first cloud connector from the first version to a second version on each of the first and second nodes in a sequential manner,

wherein the updating of the first cloud connector from the first version to the second version is initiated at the cloud-based software platform.

17. The non-transitory computer readable storage media of claim 16, wherein updating the first cloud connector from the first version to a second version on each of the first and second nodes in a sequential manner includes instructions that, when executed by one or more processors, cause the one or more processors to:

receive, at the first node, the second version of the first cloud connector from the cloud-based software platform,

deactivate the first version of the first cloud connector;

install and initialize the second version of the first cloud connector at the first node.

18. The non-transitory computer readable storage media of claim 17, further comprising instructions that, when executed by one or more processors, cause the one or more processors to:

temporarily re-assign a subscription associated with the first cloud connector at the first node to an instance of the first cloud connector at a third node in the on-premises cluster during upgrade of the first cloud connector at the first node from the first version to the second version.

19. The non-transitory computer readable storage media of claim 17, further comprising instructions that, when executed by one or more processors, cause the one or more processors to:

perform end-to-end verification of the second version of the first cloud connector at the first node, wherein the end-to-end verification is configured to confirm that the second version of the cloud connector can communicate with both the first cloud service and the first on-premises application.

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

determine that the end-to-end verification was successful such that that the second version of the first cloud connector can communicate with both the first cloud service and the first on-premises application; and

notify the cloud-based software platform that second version of the first cloud connector is active at the first node.

21. The non-transitory computer readable storage media of claim 19, further comprising instructions that, when executed by one or more processors, cause the one or more processors to:

determine that the end-to-end verification was unsuccessful such that the second version of the first cloud connector cannot communicate with at least one of the first cloud service or the first on-premises application;

uninstall the second version of the first cloud connector;

reinstall and reinitializing the first version of the first cloud connector; and

notify the cloud-based software platform that the upgrade to the second version of the first cloud connector was unsuccessful.

22. The non-transitory computer readable storage media of claim 19, wherein the first and second instances of the first version of the first cloud connector run in an active-active configuration across the first and second nodes.