TECHNIQUES FOR COORDINATON OF APPLICATION COMPONENTS DEPLOYED ON DISTRIBUTED VIRTUAL MACHINES

• US 20170364380A1
• Filed: 06/16/2016
• Published: 12/21/2017
• Est. Priority Date: 06/16/2016
• Status: Active Application

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Frye, JR., Dwight Rodney, Lemen, Michael J., Damle, Vinod Jagannath
• Granted Patent: US 10,289,438 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 2009/45591 Monitoring or debugging support
• CPC Class Codes: G06F 2009/45595 Network integration; Enabling network access in virtual machine instances
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• 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

Abstract

One embodiment is a method and includes monitoring by a module associated with a first application component installed on a first virtual machine (“VM”) a state of at least one second application component installed on a second VM and on which a state of the first application component is at least partially dependent, in which the state of the at least one second application component is made available by a module associated with the at least one application component; determining that the state of the at least one second application component has changed from a first state to a second state; and updating the state of the first application component based on a current state of the first application component and the second state of the at least one second application component.

Claims

1. A method comprising:

monitoring by a module associated with a first application component installed on a first virtual machine (“

VM”

) a state of at least one second application component installed on a second VM and on which a state of the first application component is at least partially dependent, wherein the state of the at least one second application component is made available by a module associated with the at least one application component;

determining that the state of the at least one second application component has changed from a first state to a second state; and

updating the state of the first application component based on a current state of the first application component and the second state of the at least one second application component.

2. The method of claim 1 further comprising:

detecting a change in an operational status of the first application component; and

updating the state of the first application component based on a current state of the first application component and a current operational status of the first application.

3. The method of claim 1, wherein the state of the at least one second application component is made available to the module associated with the first application component via an entry in a shared data store associated with the first and second VMs.

4. The method of claim 1, wherein the at least one second application component comprises a plurality of second application components, and wherein the state of the at least one second application component comprises a derived group state representing a collective state of the plurality of second application components.

5. The method of claim 1, wherein the current state of the first application component is an OFF state in which the first application is non-functional and the second state of the at least one second application component is a READY state in which the at least one second application is fully operational, and wherein the updating the state of the first application component comprises transitioning the state of the first application component to a STARTING state in which startup tasks necessary to bring the first application component into a functional state are performed.

6. The method of claim 1, wherein the current state of the first application component is an OFF state in which the first application is non-functional and the second state of the at least one second application component is other than a READY state, and wherein the updating the state of the first application component comprises transitioning the state of the first application component to an IDLE state in which the first application component awaits transition of the at least one second application component to the READY state.

7. The method of claim 2, wherein the current state of the first application component is a STARTING state in which startup tasks necessary to bring the first application component into a functional state are performed and wherein upon completion of the startup tasks, the method further comprises transitioning the state of the first application component to a READY state in which the first application component is fully operational.

8. The method of claim 2, wherein the current state of the first application component is a READY state in which the first application component is fully operational, and either the state of the at least one second application component is the READY state or the first application component becomes non-operational, the method further comprising transitioning the state of the first application component to a STOPPING state, in which shutdown activities are performed in connection with the first application component, and subsequently transitioning the first application component to an IDLE state when shutdown activities of the first application component have been completed.

9. One or more non-transitory tangible media having encoded thereon logic that includes code for execution and when executed by a processor is operable to perform operations comprising:

monitoring by a module associated with a first application component installed on a first virtual machine (“

VM”

) a state of at least one second application component installed on a second VM and on which a state of the first application component is at least partially dependent, wherein the state of the at least one second application component is made available by a module associated with the at least one application component;

determining that the state of the at least one second application component has changed from a first state to a second state; and

updating the state of the first application component based on a current state of the first application component and the second state of the at least one second application component.

10. The media of claim 9, wherein the operations further comprise:

detecting a change in an operational status of the first application component; and

updating the state of the first application component based on a current state of the first application component and a current operational status of the first application.

11. The media of claim 9, wherein the state of the at least one second application component is made available to the module associated with the first application component via an entry in a shared data store associated with the first and second VMs.

12. The media of claim 9, wherein the at least one second application component comprises a plurality of second application components, and wherein the state of the at least one second application component comprises a derived group state representing a collective state of the plurality of second application components.

13. The media of claim 9, wherein the current state of the first application component is an OFF state in which the first application is non-functional and the second state of the at least one second application component is a READY state in which the at least one second application is fully operational, and wherein the updating the state of the first application component comprises transitioning the state of the first application component to a STARTING state in which startup tasks necessary to bring the first application component into a functional state are performed.

14. The media of claim 9, wherein the current state of the first application component is an OFF state in which the first application is non-functional and the second state of the at least one second application component is other than a READY state, and wherein the updating the state of the first application component comprises transitioning the state of the first application component to an IDLE state in which the first application component awaits transition of the at least one second application component to the READY state.

15. The media of claim 10, wherein the current state of the first application component is a STARTING state in which startup tasks necessary to bring the first application component into a functional state are performed and wherein upon completion of the startup tasks, the method further comprises transitioning the state of the first application component to a READY state in which the first application component is fully operational.

16. The media of claim 10, wherein the current state of the first application component is a READY state in which the first application component is fully operational, and either the state of the at least one second application component is the READY state or the first application component becomes non-operational, the method further comprising transitioning the state of the first application component to a STOPPING state, in which shutdown activities are performed in connection with the first application component, and subsequently transitioning the first application component to an IDLE state when shutdown activities of the first application component have been completed.

17. An apparatus comprising:

a memory element configured to store data;

a processor operable to execute instructions associated with the data; and

a plug-in module associated with a first application component installed on a first virtual machine (“

VM”

) configured to;

monitor a state of at least one second application component installed on a second VM and on which a state of the first application component is at least partially dependent, wherein the state of the at least one second application component is made available by a module associated with the at least one application component;

determine that the state of the at least one second application component has changed from a first state to a second state; and

update the state of the first application component based on a current state of the first application component and the second state of the at least one second application component.

18. The apparatus of claim 17, wherein the module is further configured to:

detect a change in an operational status of the first application component; and

update the state of the first application component based on a current state of the first application component and a current operational status of the first application.

19. The apparatus of claim 17, wherein the state of the at least one second application component is made available to the module associated with the first application component via an entry in a shared data store associated with the first and second VMs.

20. The apparatus of claim 17, wherein the at least one second application component comprises a plurality of second application components, and wherein the state of the at least one second application component comprises a derived group state representing a collective state of the plurality of second application components.