Automated service configuration snapshots and fallback
View Patent ↗In general, in one aspect, the invention relates to a method for taking a snapshot of a service instance, including transitioning the service instance to a new state, determining whether to take the snapshot based on the new state, obtaining a property composition of the service instance, and taking the snapshot using the property composition, if the snapshot is to be taken.
1. A method for taking a snapshot of a service instance, comprising:
transitioning the service instance to a new state,
wherein the service instance is an instance of an executable process;
determining whether to take the snapshot based on the new state;
obtaining a property composition of the service instance, wherein the property composition of the service instance comprises at least one configuration property of the service instance;
taking the snapshot using the property composition; and
restarting the service instance using the snapshot.
2. The method of claim 1 , further comprising:
receiving a notification from a monitor corresponding to the service instance, wherein the monitor is associated with the service instance; and
determining whether to transition to the new state based upon the notification and at least one service instance execution dependency.
3. The method of claim 1 , further comprising:
storing the snapshot in a repository.
4. The method of claim 3 , further comprising:
marking the snapshot in the repository.
5. The method of claim 4 , wherein the snapshot is marked using at least one label selected from the group consisting of initial, editing, running, start, boot, and previous.
6. The method of claim 1 , wherein the new state is defined by a state machine associated with the service instance.
7. The method of claim 1 , wherein the property composition of the service instance further comprises at least one configuration property of a service upon which the service instance depends.
8. The method of claim 7 , wherein the property composition of the service instance further comprises at least one configuration property of a meta-service upon which the service depends.
9. The method of claim 1 , wherein the new state is one selected from the group consisting of uninitialized, offline, online, disabled, maintenance, degraded, and legacy-run.
10. A computer system comprising:
a service instance executing on the computer system, wherein the service instance is an instance of an executable process;
a state machine configured to define at least a first state and a second state of the service instance; and
a restarter configured to:
transition the service instance from the first state to the second state,
determine whether to take a snapshot based on the second state,
obtain a property composition of the service instance, wherein the property composition of the service instance comprises at least one configuration property of the service instance, and
take the snapshot of the service instance using the property composition.
11. The computer system of claim 10 , further comprising:
a repository configured to store the snapshot.
12. The computer system of claim 11 , wherein the repository is further configured to mark the snapshot.
13. The computer system of claim 12 , wherein the snapshot is marked using at least one selected from a group consisting of initial, editing, running, start, boot, and previous.
14. The computer system of claim 10 , further comprising:
a delegated restarter operatively connected to the restarter and configured to transition the service instance from the first state to the second state on behalf of the restarter, wherein the delegated restarter is configured to restart the service instance.
15. The computer system of claim 10 , wherein the first state is one selected from the group consisting of uninitialized, offline, online, disabled, maintenance, degraded, and legacy-run.
16. The computer system of claim 10 , wherein the second state is one selected from the group consisting of uninitialized, offline, online, disabled, maintenance, degraded, and legacy-run.
17. The computer system of claim 10 , wherein the property composition of the service instance further comprises at least one configuration property of a service upon which the service instance depends.
18. The computer system of claim 17 , wherein the property composition of the service instance further comprises at least one configuration property of a meta-service upon which the service depends.
19. The computer system of claim 10 , wherein the restarter is further configured to restart the service instance using the snapshot.
20. The computer system of claim 10 , wherein the restarter is further configured to:
receive a notification from a monitor corresponding to the service instance, wherein the monitor is associated with the service instance; and
determine whether to transition to the second state based upon the notification and at least one service instance execution dependency.
21. A distributed system of a plurality of nodes comprising:
a service instance executing on a computer system,
wherein the service instance is an instance of an executable process;
a state machine configured to define at least a first state and a second state of the service instance; and
a restarter configured to:
transition the service instance from the first state to the second state,
determine whether to take a snapshot based on the second state,
obtain a property composition of the service instance, wherein the property composition of the service instance comprises at least one configuration property of the service instance, and
take the snapshot of the service instance using the property composition,
wherein the computer system is one of the plurality of nodes,
wherein the state machine resides on one of the plurality of nodes, and
wherein the restarter resides on one of the plurality of nodes.
22. The distributed system of claim 21 , further comprising:
a repository configured to store the snapshot, wherein the repository resides on at least one of the plurality of nodes.