State tracking in distributed computing systems

• US 10,469,318 B1
• Filed: 12/22/2016
• Issued: 11/05/2019
• Est. Priority Date: 12/22/2016
• Status: Active Grant

• Current Assignee: Nutanix Incorporated
• Original Assignee: Nutanix Incorporated
• Inventors: Parthasarathy, Ranjan, Khinvasara, Abhijit S., Yarlagadda, Bharath, Gupta, Vinod
• Primary Examiner(s): Algibhah, Hamza N
• Application Number:
  US15/388,995
• Time in Patent Office: 1,048 Days
• Field of Search: 709226
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• 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/0863 by rolling back to previous configuration versions
• CPC Class Codes: H04L 47/722 at the destination endpoint, e.g. reservation of terminal resources or buffer space
• CPC Class Codes: H04L 47/803 Application aware
• 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

Systems and methods commence upon detecting certain computing system specification change events. Changes are recorded in resource usage intent specification records that characterize desired states associated with respective resources of the computing system. The change event causes generation of a data state snapshot of data stored in the computing system. A state tuple is constructed to associate the desired state with the data state. The state tuple is committed to a version control system. At any time, a user or process can select a selected system state tuple from committed tuples stored in the version control system. The tuple is analyzed to determine its associated desired state and its data state. Actions are taken to restore the data state of the tuple to the computing system, and then bringing the computing system to the state of the tuple so as to reproduce the desired system state in the computing system.

Claims

1. A method, comprising:

receiving a resource usage specification for a computing system, the resource usage specification describing deployment of one or more virtual machines on one or more nodes of the computer system, the resource usage specification describing the deployment of the one or more virtual machines using one or more attributes and corresponding values;

generating a snapshot of data stored in the computing system, the snapshot of data representing one or more virtual disks corresponding to respective virtual machines of the one or more virtual machines described by the resource usage specification;

associating the resource usage specification with the snapshot; and

committing an association of the resource usage specification with the snapshot to a version control system, wherein the association is one of a plurality of associations managed at the version control system.

2. The method of claim 1, wherein the resource usage specification includes one or changes from a current system state, and further comprising applying the resource usage specification over resources of the computing system.

3. The method of claim 1, wherein the snapshot is generated prior to applying one or more changes associated with the resource usage specification the resource usage specification to the computing system.

4. The method of claim 1, wherein the snapshot and the resource usage specification are storage on a first one or more databases, and the associations are storage on a second database.

5. The method of claim 1, wherein the one or more attributes describe at least one entity in the computing system.

6. The method of claim 1, further comprising quiescing at least a portion of the computing system prior to generating the snapshot.

7. The method of claim 1, wherein a unique identifier is associated with at least one of the resource usage specification or the snapshot.

8. The method of claim 1, wherein the associations at the version control system are managed by at least one user through at least one of, a management interface or a version control system console.

9. The method of claim 1, wherein a repository of the version control system stores one or more data records associated with at least one of, the association of the resource usage specification with the snapshot, the snapshot, snapshot metadata, or the resource usage specification.

10. The method of claim 1, wherein the version control system is at least one of, a source code control system, a source code repository, or GitHub.

11. A non-transitory computer readable medium having stored thereon a sequence of instructions which, when executed by a processor causes performs a set of acts comprising:

receiving a resource usage specification for a computing system, the resource usage specification describing deployment of one or more virtual machines on one or more nodes of the computer system, the resource usage specification describing the deployment of the one or more virtual machines using one or more attributes and corresponding values;

generating a snapshot of data stored in the computing system, the snapshot of data representing one or more virtual disks corresponding to respective virtual machines of the one or more virtual machines described by the resource usage specification;

associating the resource usage specification with the snapshot; and

committing an association of the resource usage specification with the snapshot to a version control system, wherein the association is one of a plurality of associations managed at the version control system.

12. The computer readable medium of claim 11, wherein the resource usage specification includes one or changes from a current system state, and the set of acts further comprise applying the resource usage specification over resources of the computing system.

13. The computer readable medium of claim 12, wherein the snapshot is generated prior to applying one or more changes associated with the resource usage specification the resource usage specification to the computing system.

14. The computer readable medium of claim 11, wherein the snapshot and the resource usage specification are storage on a first one or more databases, and the associations are storage on a second database.

15. The computer readable medium of claim 11, wherein the one or more attributes describe at least one entity in the computing system.

16. The computer readable medium of claim 11, the set of acts further comprising quiescing at least a portion of the computing system prior to generating the snapshot.

17. The computer readable medium of claim 11, wherein a unique identifier is associated with at least one of the resource usage specification or the snapshot.

18. The computer readable medium of claim 11, wherein the associations at the version control system are managed by at least one user through at least one of, a management interface or a version control system console.

19. A system comprising:

a storage medium having stored thereon a sequence of instructions; and

a processor that executes the sequence of instructions to perform a set of acts comprising,

receiving a resource usage specification for a computing system, the resource usage specification describing deployment of one or more virtual machines on one or more nodes of the computer system, the resource usage specification describing the deployment of the one or more virtual machines using one or more attributes and corresponding values;

generating a snapshot of data stored in the computing system, the snapshot of data representing one or more virtual disks corresponding to respective virtual machines of the one or more virtual machines described by the resource usage specification;

associating the resource usage specification with the snapshot; and

committing an association of the resource usage specification with the snapshot to a version control system, wherein the association is one of a plurality of associations managed at the version control system.

20. The system of claim 19, wherein the associations at the version control system are managed by at least one user through at least one of, a management interface or a version control system console.