State synchronization in a service environment

• US 10,341,199 B2
• Filed: 07/16/2013
• Issued: 07/02/2019
• Est. Priority Date: 07/16/2013
• Status: Active Grant

• Current Assignee: Adobe Inc.
• Original Assignee: Adobe Inc.
• Inventors: Peri, Srinivas, Ivtsan, Aya
• Primary Examiner(s): Nguyen, Dustin
• Application Number:
  US13/943,562
• Publication Number:
  US 20150026323A1
• Time in Patent Office: 2,177 Days
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: H04L 41/5045 Making service definitions prior to deployment
• CPC Class Codes: H04L 41/5058 Service discovery by the service manager
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/55 Push-based network services

Abstract

Techniques for state synchronization in a service environment are described. In at least some embodiments, different synchronization models are employed to synchronize state for resources in a service environment. For instance, embodiments may employ a “pull model” whereby a resource periodically queries for changes in resource state to be applied to the resource. Alternatively or additionally, a “push model” can be employed whereby notifications are pushed to resources, informing the resources that they are to update their state. Thus, based on various considerations for a service environment, instances and/or combinations of the disclosed synchronization models can be implemented.

Claims

1. A system comprising:

one or more processors; and

one or more computer-readable storage media storing computer-executable instructions that, responsive to execution by the one or more processors, cause the system to implement functionalities including;

a configuration manager configured to maintain resource models that each correspond to a different respective role in a service environment and that represent state descriptions for nodes in the service environment that correspond to different respective roles such that a different respective resource model exists for each different respective role, the resource models not including code for synchronizing individual nodes to their respective state description;

a deployment orchestrator configured to ascertain that nodes associated with different roles in the service environment are to synchronize their state in an order specified based on their respective roles, and notify the nodes in the specified order based on their respective roles;

a resource repository that is implemented independently of the configuration manager and the deployment orchestrator and that is configured to;

store configuration packages for updating states of the nodes in the service environment, the configuration packages including code for implementing the resource models; and

respond to a query from a respective agent that resides on a respective node with a configuration package that includes code for synchronizing the respective node with the respective resource model; and

an agent associated with a particular role and that resides on a particular node in the service environment, the agent configured to;

query the configuration manager to determine a particular resource model associated with the particular role; and

query the resource repository for a particular configuration package for synchronizing the particular node with the particular resource model.

2. A system as described in claim 1, wherein the resource models specify different state information for different roles in the service environment.

3. A system as described in claim 1, wherein the respective resource model identifies a software patch to be applied to nodes in the service environment that correspond to the particular role.

4. A system as described in claim 1, wherein a state description for the particular role identifies at least a portion of an initial service deployment for nodes in the service environment that correspond to the particular role.

5. A system as described in claim 1, wherein responsive to a determination that a state of the particular node is to be synchronized with the respective resource model, the agent is configured to retrieve from the resource repository the configuration package that includes code that is installable on the particular node to synchronize its state with the respective resource model.

6. A system as described in claim 1, wherein the agent is further configured to, independent of a query to the deployment orchestrator, receive a notification that a state of the particular node is to be synchronized with the respective resource model, and to retrieve from the resource repository the configuration package that includes code that is installable on the particular node to synchronize its state with the respective resource model.

7. A system as described in claim 1, wherein the deployment orchestrator is further configured to ascertain that nodes associated with the respective role are to be updated, and to notify instances of the agent that reside on the nodes associated with the respective role that the nodes are to update their state.

8. A system as described in claim 7, wherein:

the agent is configured to periodically query for an update to synchronization state according to a pull model for synchronization in the service environment; and

the deployment orchestrator is configured to notify nodes to update their state according to a push model for synchronization in the service environment,

wherein the system is configured to utilize either the pull model or the push model based on synchronization circumstances in the service environment.

18. A system as described in claim 1, wherein the deployment orchestrator is further configured to determine that nodes associated with a first role are finished updating their state, and in response notify one or more other nodes associated with a second role that the one or more other nodes are to update their state.

9. A system comprising:

one or more processors; and

one or more computer-readable storage media storing computer-executable instructions that, responsive to execution by the one or more processors, cause the system to implement functionalities including;

a deployment orchestrator configured to ascertain that nodes associated with a particular role in a service environment are to be updated, and to notify instances of an agent associated with the particular role and that reside on the nodes associated with the particular role that the nodes are to update their state;

a configuration manager configured to maintain resource models that each correspond to a different respective state description for a different respective role in the service environment such that a different respective resource model exists for each different respective role, and to indicate to an instance of an agent that resides on the nodes that the nodes associated with the particular role are to be updated based on a resource model for the particular role, the resource models not including code for synchronizing individual nodes to their respective state description; and

a resource repository that is implemented independently of the deployment orchestrator and the configuration manager and that is configured to;

store configuration packages for updating states of the nodes in the service environment, the configuration packages including code for implementing the resource models; and

respond to queries from the nodes with configuration packages that include code for synchronizing the nodes with their respective resource models.

10. A system as described in claim 9, wherein the resource models specify different state information for different roles in the service environment.

11. A system as described in claim 9, wherein an update to a state of a particular node comprises an installation of a software patch on the particular node.

12. A system as described in claim 9, wherein an update to a state of a particular node comprises at least a portion of an initial service deployment on the particular node.

19. A system as described in claim 9, wherein the deployment orchestrator is further configured to determine that the nodes associated with the particular role are finished updating their state, and to further notify one or more other nodes associated with a different role that the one or more other nodes are to update their state.

20. A system as described in claim 9, wherein the deployment orchestrator is further configured to communicate state information to the configuration manager that describes a change in state for the one or more nodes associated with the first role to be used to update a resource model for the first role.

13. One or more computer-readable storage media comprising instructions stored thereon that, responsive to execution by a computing device, cause the computing device to perform operations comprising:

submitting a query from a node to a configuration manager in a service environment as to whether an update for the node is available based on a role for the node in the service environment, the query identifying the role from among a plurality of roles;

ascertaining based on a response to the query that an update is available for the identified role according to a resource model for the role, such that a different respective resource model exists for each respective one of the plurality of roles;

retrieving the update from a resource repository that is remote from the configuration manager; and

applying the update to the node to synchronize a state of the node with a resource model specified for the role.

14. One or more computer-readable storage media as recited in claim 13, wherein said submitting comprises periodically submitting the query.

15. One or more computer-readable storage media as recited in claim 13, wherein said applying comprises applying the update to modify existing software on the node.

16. One or more computer-readable storage media as recited in claim 13, wherein said applying comprises applying the update as at least part of an initial deployment of a service on the node.

17. One or more computer-readable storage media as recited in claim 13, wherein the query further includes an indication of a current software state of the node.