Software application updating in a local network

• US 10,873,645 B2
• Filed: 09/09/2019
• Issued: 12/22/2020
• Est. Priority Date: 03/24/2014
• Status: Active Grant

• Current Assignee: Tanium Inc.
• Original Assignee: Tanium Inc.
• Inventors: Freilich, Max, White, Andrew R., Hunt, Christian L., Constantine, Peter, Lincroft, Peter
• Primary Examiner(s): Patel, Hitesh
• Application Number:
  US16/565,247
• Publication Number:
  US 20200007642A1
• Time in Patent Office: 470 Days
• CPC Class Codes: H04L 41/08 Configuration management of networks or network elements address allocation H04L61/50
• CPC Class Codes: H04L 67/1089 Hierarchical topologies
• 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/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

A method of updating software, performed by respective machines in a linear communication orbit includes, at a local server executed by a respective machine, receiving, via the linear communication orbit, update metadata. At an update module executed by the respective machine, an update module evaluates software version information using the update metadata to determine a set of one or more updates to be applied to one or more software programs. A patch module sends, via the linear communication orbit, requests for one or more software update files corresponding to the set of one or more updates, and receives the one or more software update files corresponding to the set of one or more updates. The update module then updates the one or more of the software programs by applying the received one or more software update files to the one or more of the software programs.

Claims

1. A method of data caching and distribution, comprising:

at each respective machine in a plurality of machines that are included in a linear communication orbit, wherein the linear communication orbit includes machines at two end nodes, comprising a head node and a tail node, and the linear communication orbit is coupled to a server via at least one of the machines at the two end nodes;

executing a plurality of software programs;

executing a local server distinct from the plurality of software programs;

at the local server, receiving, via the linear communication orbit, update metadata;

at an update module executed by the respective machine, the update module distinct from the local server and the plurality of software programs,

receiving the update metadata from the local server; and

evaluating software version information using the update metadata to determine a set of one or more updates to be applied to one or more of the plurality of software programs;

sending, via the linear communication orbit, one or more requests so as to request one or more software update files corresponding to the set of one or more updates;

receiving the one or more software update files corresponding to the set of one or more updates; and

at the update module, updating the one or more of the software programs by applying the received one or more software update files to the one or more of the software programs;

wherein the linear communication orbit comprises a linearly arranged sequence of machines configured to sequentially convey messages to each machine in the linearly arranged sequence of machines in the linear communication orbit.

2. The method of claim 1, wherein the software version information identifies one or more software applications already installed at the respective machine, and prior updates that have been applied to the one or more software applications.

3. The method of claim 2, wherein the update metadata includes applicability rules for evaluating the software version information so as to identify updates that have not yet been applied to the one or more software applications.

4. The method of claim 2, wherein the update metadata includes applicability rules for evaluating the software version information so as to identify one or more groups of software update files corresponding to updates that have not yet been applied to the one or more software applications.

5. The method of claim 1, wherein receiving the software update files corresponding to the set of one or more updates comprises a set of operations, including:

sending, via the linear communication orbit, one or more file manifest requests for file manifests corresponding to the set of one or more updates;

receiving, via the linear communication orbit, in response to the one or more file manifest requests, one or more file manifests corresponding to the set of one or inure updates;

identifying, from the received one or more file manifests, a plurality of individual update files that are not locally stored at the respective machine;

sending, via the linear communication orbit, shard requests for each of the individual update files that are not locally stored at the respective machine;

receiving, via the linear communication orbit, in response to the shard requests, the requested individual update files; and

combining one or more subsets of the individual update files received in response to the shard requests and individual update files, if any, already locally stored at the respective machine, to generate at least one of the software update files corresponding to the set of one or more updates.

6. The method of claim 5, wherein the set of operations for receiving the software update files corresponding to the set of one or more updates is performed by a patch module distinct from the update module and the local server.

7. The method of claim 5, wherein a respective file manifest of the one or more file manifests corresponds to two or more of the individual update files, which comprise shards of a respective software update file that when combined, form the respective software update file.

8. The method of claim 7, wherein, prior to the respective machine sending the shard requests, a first plurality of shards of the respective software update file are, in aggregate, locally cached at other machines, other than the respective machine, in the linear communication orbit, and wherein the requested individual update files received by the respective machine in response to the shard requests include the first plurality of shards of the respective software update file, received from the other machines in the linear communication orbit that have locally cached one or more of the first plurality of shards of the respective software update file.

9. A system, comprising a respective machine in a plurality of machines that are included in a linear communication orbit, wherein the linear communication orbit includes machines at two end nodes, comprising a head node and a tail node, and the linear communication orbit is coupled to a server via at least one of the machines at the two end nodes;

the system comprising;

one or more processors;

memory storing one or more programs for execution by the one or more processors, the one or more programs including instructions for;

executing a plurality of software programs;

executing a local server distinct from the plurality of software programs;

at the local server, receiving, via the linear communication orbit, update metadata;

at an update module executed by the respective machine, the update module distinct from the local server and the plurality of software programs;

receiving the update metadata from the local server; and

evaluating software version information using the update metadata to determine a set of one or more updates to be applied to one or more of the plurality of software programs;

sending, via the linear communication orbit, one or more requests so as to request one or more software update files corresponding to the set of one or more updates;

receiving the one or more software update files corresponding to the set of one or more updates; and

at the update module, updating the one or more of the software programs by applying the received one or more software update files to the one or more of the software programs;

wherein the linear communication orbit comprises a linearly arranged sequence of machines configured to sequentially convey messages to each machine in the linearly arranged sequence of machines in the linear communication orbit.

10. The system of claim 9, wherein the software version information identifies one or more software applications already installed at the respective machine, and prior updates that have been applied to the one or more software applications.

11. The system of claim 10, wherein the update metadata includes applicability rules for evaluating the software version information so as to identify updates that have not yet been applied to the one or more software applications.

12. The system of claim 10, wherein the update metadata includes applicability rules for evaluating the software version information so as to identify one or more groups of software update files corresponding to updates that have not yet been applied to the one or more software applications.

13. The system of claim 9, wherein receiving the software update files corresponding to the set of one or more updates comprises a set of operations, including:

sending, via the linear communication orbit, one or more file manifest requests for file manifests corresponding to the set of one or more updates;

receiving, via the linear communication orbit, in response to the one or more file manifest requests, one or more file manifests corresponding to the set of one or more updates;

identifying, from the received one or more file manifests, a plurality of individual update files that are not locally stored at the respective machine;

sending, via the linear communication orbit, shard requests for each of the individual update files that are not locally stored at the respective machine;

receiving, via the linear communication orbit, in response to the shard requests, the requested individual update files; and

combining one or more subsets of the individual update files received in response to the shard requests and individual update files, if any, already locally stored at the respective machine, to generate at least one of the software update files corresponding to the set of one or more updates.

14. The system of claim 13, wherein the set of operations for receiving the software update files corresponding to the set of one or more updates is performed by a patch module distinct from the update module and the local server.

15. The system of claim 13, wherein a respective file manifest of the one or more file manifests corresponds to two or more of the individual update files, which comprise shards of a respective software update file that when combined, form the respective software update file.

16. The system of claim 15, wherein, prior to the respective machine sending the shard requests, a first plurality of shards of the respective software update file are, in aggregate, locally cached at other machines, other than the respective machine, in the linear communication orbit, and wherein the requested individual update files received by the respective machine in response to the shard requests include the first plurality of shards of the respective software update file, received from the other machines in the linear communication orbit that have locally cached one or more of the first plurality of shards of the respective software update file.

17. A non-transitory computer readable storage medium storing one or more programs for execution by a respective machine of a plurality of machines arranged in a linear communication orbit so as to sequentially convey messages to each of the machines in the linear communication orbit, wherein the linear communication orbit includes machines at two end nodes, comprising a head node and a tail node, and the linear communication orbit is coupled to a server via one of the two end nodes;

the one or more programs including instructions for;

executing a plurality of software programs;

executing a local server distinct from the plurality of software programs;

at the local server, receiving, via the linear communication orbit, update metadata;

at an update module executed by the respective machine, the update module distinct from the local server and the plurality of software programs,

receiving the update metadata from the local server; and

evaluating software version information using the update metadata to determine a set of one or more updates to be applied to one or more of the plurality of software programs;

sending, via the linear communication orbit, one or more requests so as to request one or more software update files corresponding to the set of one or more updates;

receiving the one or more software update files corresponding to the set of one or more updates; and

at the update module, updating the one or more of the software programs by applying the received one or more software update files to the one or more of the software programs;

wherein the linear communication orbit comprises a linearly arranged sequence of machines configured to sequentially convey messages to each machine in the linearly arranged sequence of machines in the linear communication orbit.

18. The non-transitory computer readable storage medium of claim 17, wherein receiving the software update files corresponding to the set of one or more updates comprises a set of operations, including:

sending, via the linear communication orbit, one or more file manifest requests for file manifests corresponding to the set of one or more updates;

receiving, via the linear communication orbit, in response to the one or more file manifest requests, one or more file manifests corresponding to the set of one or more updates;

identifying, from the received one or more file manifests, a plurality of individual update files that are not locally stored at the respective machine;

sending, via the linear communication orbit, shard requests for each of the individual update files that are not locally stored at the respective machine;

receiving, via the linear communication orbit, in response to the shard requests, the requested individual update files.

19. The non-transitory computer readable storage medium of claim 18, wherein the set of operations for receiving the software update files corresponding to the set of one or more updates is performed by a patch module distinct from the update module and the local server.

20. The non-transitory computer readable storage medium of claim 18, wherein a respective file manifest of the one or more file manifests corresponds to two or more of the individual update files, which comprise shards of a respective software update file that when combined, form the respective software update file.

21. The non-transitory computer readable storage medium of claim 20, wherein, prior to the respective machine sending the shard requests, a first plurality of shards of the respective software update file are, in aggregate, locally, cached at other machines, other than the respective machine, in the linear communication orbit, and wherein the requested individual update files received by the respective machine in response to the shard requests include the first plurality of shards of the respective software update file, received from the other machines in the linear communication orbit that have locally cached one or more of the first plurality of shards of the respective software update file.

22. The non-transitory computer readable storage medium of claim 17, wherein the software version information identifies one or more software applications already installed at the respective machine, and prior updates that have been applied to the one or more software applications.

23. The non-transitory computer readable storage medium of claim 22, wherein the update metadata includes applicability rules for evaluating the software version information so as to identify updates that have not yet been applied to the one or more software applications.

24. The non-transitory computer readable storage medium of claim 22, wherein the update metadata includes applicability rules for evaluating the software version information so as to identify one or more groups of software update files corresponding to updates that have not yet been applied to the one or more software applications.