Method and system for managing software installs in a distributed computer network

• US 20040243995A1
• Filed: 05/27/2003
• Published: 12/02/2004
• Est. Priority Date: 05/27/2003
• Status: Active Grant

• Current Assignee: Akamai Technologies, Inc.
• Original Assignee: Akamai Technologies, Inc.
• Inventors: Sheehy, Justin J.
• Granted Patent: US 7,353,509 B2
• Time in Patent Office: Days
• US Class Current: 717/174
• CPC Class Codes: G06F 8/61 Installation

Abstract

A method of and system for managing installs to a set of one or more field machines in a distributed network environment. In an illustrative embodiment, the system includes at least one change coordinator server that includes a database with data identifying a current state of each field machine, and a change controller routine for initiating a given control action to initiate an update to the current state on a given field machine. In particular, the change controller routine may include a scheduling algorithm that evaluates data from the database and identifies a set of field machines against which the given control action may be safely executed at a given time. At least one install server is responsive to the change controller routine initiating the given control action for invoking the update to the current state on the given field machine.

Claims

1. A system for managing installs to a set of one or more field machines in a distributed network environment, comprising:

at least one change coordinator server that includes a database with data identifying a current state of each field machine, and a change controller routine for initiating a given control action to initiate an update to the current state on a given field machine; and

at least one install server responsive to the change controller routine initiating the given control action for invoking the update to the current state on the given field machine.

2. The system as described in claim 1 wherein the change controller routine includes a scheduling algorithm that evaluates data from the database and identifies a set of field machines against which the given control action may be safely executed at a given time.

3. The system as described in claim 2 wherein the scheduling algorithm implements a given heuristic.

4. The system as described in claim 2 wherein the given heuristic assigns a rank ordered set of field machines to a set of one or more timeslots.

5. The system as described in claim 1 further including an install reporter routine that executes on the given field machine for providing the change controller server with information on the current state of the given field machine.

6. The system as described in claim 5 wherein the information identifies a given software release and an IP address of the given field machine.

7. The system as described in claim 1 wherein the install server invokes installation using an application deployment utility.

8. The system as described in claim 5 wherein field machines are servers of a content delivery network (CDN).

9. Apparatus for managing installs to a set of hosts, wherein the installs are invoked from a set of one or more install servers, the apparatus comprising:

a database of install states of the set of hosts; and

a change controller routine for using data from the database and initiating a given control action to a given one of the install servers to initiate an install on one or more given hosts.

10. The apparatus as described in claim 9 wherein the change controller routine evaluates install state data from the database and identifies a subset of the hosts against which the given control action may be safely executed at a given time.

11. The apparatus as described in claim 10 wherein the change controller routine implements a given heuristic.

12. The apparatus as described in claim 11 wherein the given heuristic assigns a rank ordered set of hosts to a set of one or more timeslots.

13. A system for managing installs to a set of one or more field machines, comprising:

a set of change coordinator servers, wherein each change coordinator server includes a database, an install listener routine that receives reports from install reporter routines running on the given field machines and populates the database with data identifying the given software release running on the field machines, and a change controller routine for initiating a given control action to initiate an install on a given field machine, wherein the given control action is initiated if the given field machine requires an install of a new software release; and

a set of install servers, wherein each install server is responsive to a change controller routine in a given change coordinator server initiating the given control action for invoking installation of the new software release on a given field machine.

14. The system as described in claim 13 wherein each change coordinator server also includes code for synchronizing its database with the databases in other change coordinator servers.

15. The system as described in claim 13 wherein each of the set of install servers has the capability of communicating with a given change coordinator server to enable the given change coordinator server to manage installs for the set of install servers.

16. The system as described in claim 13 wherein a given change coordinator routine includes a rules-based scheduling engine that evaluates data from the database against at least one rule to determine which field machines are eligible for installation at a given time.