APPARATUS, SYSTEMS, AND METHODS FOR DISTRIBUTED APPLICATION ORCHESTRATION AND DEPLOYMENT

• US 20160378450A1
• Filed: 06/24/2015
• Published: 12/29/2016
• Est. Priority Date: 06/24/2015
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: CliQr Technologies, Inc. (Cisco Systems, Inc.)
• Inventors: NAGARAJ, Abhinav, FU, Tianying, MALIK, Saad Ali, JOSHI, Gautam
• Granted Patent: US 9,684,502 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 2009/45562 Creating, deleting, cloning virtual machine instances
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• 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

Embodiments disclosed facilitate distributed orchestration and deployment of a cloud based distributed computing application. In some embodiments, the distributed orchestration may be based on a cloud agnostic representation of the application. In some embodiments, an ordered set of events may be obtained based on a starting sequence for the plurality of components, where each event in the ordered set is associated with a corresponding set of prerequisites for initiating execution of the event. Event identifiers corresponding to the ordered set of events may be placed on an event message bus with persistence that is shared between a plurality of distributed nodes associated with a cloud. Upon receiving an indication of completion of prerequisites for one or more events, a plurality of nodes of a distributed orchestration engine may select the one or more events corresponding to the one or more selected event identifiers for execution on the cloud.

Claims

1. A processor-implemented method comprising:

obtaining, based, in part, on a representation of a cloud-based distributed computing application comprising a plurality of components, an ordered set of events based on an execution sequence for the plurality of components, wherein each event in the ordered set is associated with a corresponding set of prerequisites for initiating execution of the event;

receiving, on a shared event message bus with persistence, event identifiers corresponding to one or more events in the ordered set that are ready for execution, wherein the event message bus is shared between a plurality of nodes associated with a cloud, and wherein, for each event in the ordered set that is ready for execution, prerequisites in a corresponding set of prerequisites for initiating execution of the event have been satisfied; and

selecting one or more event identifiers, corresponding to the one or more of the events ready for execution, from the event message bus.

2. The method of claim 1, further comprising:

receiving, on the shared event message bus with persistence, an indication of completion of the one or more events corresponding to the one or more selected event identifiers;

determining one or more additional events that are ready for execution based, in part, on the received indication of completion; and

placing one or more additional event identifiers corresponding to the one or more additional events that are ready for execution on the event message bus.

3. The method of claim 1, wherein the representation of the cloud-based distributed computing application is a cloud agnostic representation of the cloud-based distributed computing application.

4. The processor-implemented method of claim 3, wherein cloud agnostic representation of the cloud-based distributed computing application comprises one or more of:

application topology metadata for the cloud-based distributed computing application, the application topology metadata comprising dependency metadata for a plurality of components of the cloud-based distributed computing application,

configuration metadata for the plurality of components of the cloud-based distributed computing application, and

lifecycle stage metadata for components of the cloud-based distributed computing application.

5. The processor-implemented method of claim 1, further comprising:

providing at least one of;

(i) an indication that the one or more selected event identifiers have been selected, or (ii) an indication that the one or more selected event identifiers are unavailable for selection.

6. The processor-implemented method of claim 1, wherein the ordered set of events and the set of prerequisites for initiating execution of an event are obtained, based further on a lifecycle stage associated with components of the cloud-based distributed computing application.

7. The processor-implemented method of claim 6, wherein the lifecycle stage comprises one of:

startup, initialization, configuration, shutdown, scaling, migration, backup, upgrade or recovery.

8. The processor-implemented method of claim 1, wherein the method is performed by a distributed orchestration engine for the cloud-based distributed computing application using a subset of the plurality of distributed nodes.

9. The processor-implemented method of claim 1, further comprising:

initiating execution of one or more selected events, the one or more selected events corresponding to one or more of the selected event identifiers.

10. The processor-implemented method of claim 9, wherein initiating execution of the one or more selected events comprises:

initiating execution of one or more sets of actions, wherein each of the one or more sets of actions;

corresponds to a selected event in the one or more selected events; and

is obtained from a corresponding event-action map associated with the corresponding selected event, the corresponding event action map being obtained from the representation of the cloud-based distributed computing application.

11. The processor-implemented method of claim 9, further comprising:

upon receiving an indication that execution of a subset of the one or more selected events is unsuccessful;

rolling back any completed actions associated with the execution of the subset of the one or more selected events; and

placing event-identifiers corresponding to events in the subset of the one or more selected events on the event message bus.

12. The processor-implemented method of claim 1, wherein the selection of the at least one event ready for execution is performed by a node, based, at least in part, on a current workload of the node relative to workloads of individual nodes in a subset of the plurality of nodes.

13. An apparatus comprising:

a memory comprising a representation of a cloud-based distributed computing application comprising a plurality of components;

an event message bus with persistence,

a plurality of nodes associated with a cloud, wherein the plurality of nodes are coupled to the memory and the event message bus, wherein the plurality of nodes are configured to;

obtain, based, in part, on the representation of the cloud-based distributed computing application, an ordered set of events based on an execution sequence for the plurality of components, wherein each event in the ordered set is associated with a corresponding set of prerequisites for initiating execution of the event;

receive, on the shared event message bus, one or more event identifiers corresponding to one or more events in the ordered set that are ready for execution, wherein, for each event in the ordered set that is ready for execution, prerequisites in a corresponding set of prerequisites for initiating execution of the event have been satisfied; and

select, from the shared event message bus, one or more of the event identifiers corresponding to the one or more of the events ready for execution.

14. The apparatus of claim 13, wherein the plurality of nodes are further configured to:

receive, on the shared event message bus with persistence, an indication of completion of the one or more selected events;

determine one or more additional events that are ready for execution based, in part, on the received indication of completion; and

place one or more additional event identifiers, corresponding to the one or more of the additional events ready for execution on the event message bus.

15. The apparatus of claim 13, wherein the representation of the cloud-based distributed computing application in memory comprises a cloud agnostic representation of the cloud-based distributed computing application.

16. The apparatus of claim 15, wherein cloud agnostic representation of the cloud-based distributed computing application in memory comprises one or more of:

application topology metadata for the cloud-based distributed computing application, the application topology metadata comprising dependency metadata for a plurality of components of the cloud-based distributed computing application,

configuration metadata for the plurality of components of the cloud-based distributed computing application, and

lifecycle stage metadata for components of the cloud-based distributed computing application.

17. The apparatus of claim 13, wherein upon selection of the one or more event identifiers corresponding to the one or more events ready for execution by one or more corresponding nodes in the plurality of nodes, the one or more corresponding nodes are further configured to:

provide at least one of;

(i) an indication that the one or more selected event identifiers have been selected, or (ii) an indication that the one or more selected event identifiers are unavailable for selection.

18. The apparatus of claim 13, wherein the plurality of nodes are configured to obtain the ordered set of events and the set of prerequisites for initiating execution of an event, based further on a lifecycle stage associated with the components of the cloud-based distributed computing application.

19. The apparatus of claim 18, wherein the lifecycle stage comprises one of:

startup, initialization, configuration, shutdown, scaling, migration, backup, upgrade or recovery.

20. The apparatus of claim 13, wherein upon selection of the one or more event identifiers corresponding to the one or more events ready for execution by one or more corresponding nodes in the plurality of nodes, the one or more corresponding nodes are further configured to:

initiate execution of one or more selected events, the one or more selected events corresponding to one or more of the selected event identifiers.

21. The apparatus of claim 20, wherein to initiate execute the selected event, the one or more corresponding nodes are configured to:

initiate execution of one or more sets of actions, wherein each of the one or more sets of actions;

corresponds to a selected event in the one or more selected events; and

is obtained from a corresponding event-action map associated with the corresponding selected event, the corresponding event action map being obtained from the representation of the cloud-based distributed computing application.

22. The apparatus of claim 20, wherein upon receiving an indication that execution of a subset of selected events is unsuccessful:

rolling back any completed actions associated with the execution of the subset of selected events; and

placing event-identifiers corresponding to events in the subset on the event message bus.

23. A non-transitory computer-readable medium comprising instructions, which, when executed by a processor, perform steps in a method, the steps comprising:

obtaining, based, in part, on a representation of a cloud based distributed computing application comprising a plurality of components, an ordered set of events based on an execution sequence for the plurality of components, wherein each event in the ordered set is associated with a corresponding set of prerequisites for initiating execution of the event;

receiving, on a shared event message bus with persistence, event identifiers corresponding to one or more events in the ordered set that are ready for execution, wherein the event message bus is shared between a plurality of nodes associated with a cloud, and wherein, for each event in the ordered set that is ready for execution, prerequisites in a corresponding set of prerequisites for initiating execution of the event have been satisfied; and

selecting one or more event identifiers, corresponding to the one or more of the events ready for execution, from the event message bus.

24. The non-transitory medium of claim 23, the steps further comprising:

receiving, on the shared event message bus with persistence, an indication of completion of the one or more events corresponding to the one or more selected event identifiers;

determining one or more additional events that are ready for execution based, in part, on the received indication of completion; and

placing one or more additional event identifiers corresponding to the one or more additional events that are ready for execution on the event message bus.

25. The non-transitory medium of claim 23, the steps further comprising:

initiating execution of one or more selected events, the one or more selected events corresponding to one or more of the selected event identifiers.

26. The non-transitory medium of claim 25, wherein initiating execution of the one or more selected events comprises the steps of:

initiating execution of one or more sets of actions, wherein each of the one or more sets of actions;

corresponds to a selected event in the one or more selected events; and

is obtained from a corresponding event-action map associated with the corresponding selected event, the corresponding event action map being obtained from the representation of the cloud-based distributed computing application.

27. The non-transitory medium of claim 25, the steps further comprising:

upon receiving an indication that execution of a subset of the one or more selected events is unsuccessful;

rolling back any completed actions associated with the execution of the subset of the one or more selected events; and

placing event-identifiers corresponding to events in the subset of the one or more selected events on the event message bus.