Deployment of business logic software and data content onto network servers

• US 20030078959A1
• Filed: 10/18/2001
• Published: 04/24/2003
• Est. Priority Date: 10/18/2001
• Status: Active Grant

• Current Assignee: Valtrus Innovations Limited (f/k/a Dolya Holdco 9 Limited) (Key Patent Innovations Limited)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Kennedy, Paul, Dahbura, Tony, Yeung, Wilson, Liu, Phillip
• Granted Patent: US 7,496,645 B2
• Time in Patent Office: Days
• US Class Current: 709/201
• CPC Class Codes: G06F 8/62 Uninstallation
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• 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 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A tool for the deployment of software onto servers and other network resources provides a mechanism for parties that do not manage the operation of the servers to deploy new software. The new software is uploaded into an update directory, and a cut-over process is carried out whereby the contents of a live directory, where the currently-executing version of the software is stored, is synchronized with the update directory. Prior to this synchronization, the current state of the live directory is stored in a rollback directory. After the cut-over process, the live directory of the server becomes the source for deployment of the software to update directories in other servers. If the new version of the software is not operating to satisfaction, the information in the rollback directory is used to return the server to the prior version of the software while the new software is being revised.

Claims

1. A method for deploying software associated with a resource on a network, comprising the steps of:

storing a copy of the software in a first designated directory on an intermediate server;

synchronizing the contents of a second designated directory on said intermediate server to said first designated directory;

executing an application on said intermediate server in accordance with the software in said second designated directory;

synchronizing the contents of a predetermined directory on a destination server to said second designated directory; and

executing an application on said destination server in accordance with the software in said predetermined directory.

2. The method of claim 1 wherein a plurality of intermediate servers are present, and wherein said copy of the software is stored in the first designated directory in a master intermediate server, and further including the step of synchronizing a first designated directory in each of the other intermediate servers to the second designated directory of the master intermediate server.

3. The method of claim 1 wherein the step of synchronizing the contents of the second designated directory includes the step of synchronizing the contents of a third designated directory to said second designated directory prior to synchronizing said second designated directory to said first designated directory.

4. The method of claim 3 further including the step of rolling back the contents of said third designated directory to said second designated directory in response to a malfunction in the execution of the application after the second designated directory has been synchronized to said first designated directory.

5. The method of claim 3 wherein said third designated directory contains information which identifies files that are added to said second designated directory and files in said second designated directory that are modified when said second designated directory is synchronized to said first designated directory.

6. The method of claim 5 wherein said information contained in said third designated directory also identifies files that are being deleted from said second designated directory.

7. The method of claim 6 wherein said third designated directory also contains a copy of the files that are being deleted.

8. The method of claim 7 wherein said rollback step includes copying the files that were deleted from said third designated directory to said second designated directory.

9. The method of claim 5 wherein said third designated directory also contains a copy of an unmodified version of the files that are being modified.

10. The method of claim 9 wherein said rollback step includes copying said unmodified versions of the files from said third designated directory to said second designated directory.

11. The method of claim 1 wherein the step of synchronizing the contents of the predetermined directory on the destination server comprises the steps of:

synchronizing the contents of an update directory on said destination server to said second designated directory on said intermediate server; and

synchronizing the contents of said predetermined directory to said update directory.

12. The method of claim 1 further including the step of generating a manifest of differences between said predetermined directory on the destination server and the second designated directory on said intermediate server prior to synchronizing said predetermined directory.

13. The method of claim 12 further including the step of storing the differences listed on said manifest in a storage system separate from said intermediate server and said destination server.

14. The method of claim 1 wherein said synchronizing steps comprise the steps of determining the differences between first and second directories to be synchronized, and transmitting only those files which differ between the two directories from the first directory to the second directory.

15. The method of claim 14 wherein said synchronizing steps further include the optional step of deleting files from the second directory which are not present in the first directory.

16. The method of claim 14 wherein the step of determining differences comprises the step of preparing a digest of each file in each of said first and second directories, and comparing the digests of the two directories to one another.

17. The method of claim 16 wherein a digest contains information regarding attributes of each file, including its size and last modification date.

18. A method for deploying software associated with a resource on a network, comprising the steps of:

storing information in a database that identifies one or more hosts associated with the resource;

receiving a request to update software for said resource;

retrieving said information from said database and displaying hosts which are available for updating;

receiving a designation of at least one of the displayed hosts;

determining differences between software currently executing on the designated host and an updated version of the software;

storing information relating to said differences in said database; and

updating the software on the designated host.

19. The method of claim 18 further including the step of storing a script file containing commands that define an operation to be performed, and wherein said step of updating the software includes the following steps:

retrieving said script file in response to designation of an operation to be performed;

forwarding said commands to the designated host; and

executing said commands on the host.

20. The method of claim 19 wherein said script file is stored in a file system and said commands are executed by an agent that is running on said host, and wherein said script file is retrieved by a gateway that receives said designations and forwards said commands to said agent for execution.

21. The method of claim 20 wherein said gateway further carries out the steps of monitoring the status of execution of said commands, and storing information regarding said status in said database.

22. The method of claim 19 wherein said script file contains commands that relate to service operations that are performed on a host.

23. The method of claim 22 wherein one of said service operations comprises a cut-over operation that includes the steps of synchronizing files in a first directory on the host with those in a second directory on the host, and causing the host to execute the files in said second directory.

24. The method of claim 23 wherein said cut-over operation further includes the step of synchronizing files in said second directory with those in a third directory, and another one of said service operations comprises a rollback operation that includes the steps of synchronizing files in said third directory with those in said second directory, and causing said host to execute the files in said second directory.

25. The method of claim 22 wherein said service operations include the stopping and starting of the operation of the host.

26. The method of claim 19 wherein said script file contains commands that relate to the synchronization of two directories on two respective hosts.

27. The method of claim 26 wherein one of the hosts comprises a source and contains a directory that stores a current version of the software that executes on that host, and the other host comprises a destination that contains a first directory that stores a current version of the software that executes on that host and a second, update directory, and wherein the synchronization comprises the steps of:

comparing the contents of the first directory in the destination host with the current directory in the source host and determining differences in their contents; and

storing said differences in the update directory in the destination host.

28. A method for deploying software associated with a resource on a network, comprising the steps of:

storing information in a database that identifies one or more hosts associated with the resource;

storing a script file that contains commands relating to the synchronization of two directories;

receiving a request to update software for said resource;

retrieving said information from said database and displaying hosts which are available for updating;

receiving a designation of at least one of the displayed hosts;

running said script file to determine differences between a directory on the designated host and a source directory; and

transmitting files that correspond to said differences from said source directory to said host.

29. The method of claim 28 wherein said script file is stored in a file system and said commands are executed by an agent that is running on said host, and wherein said script file is retrieved by a gateway that receives said designations and forwards said commands to said agent for execution.

30. The method of claim 29 wherein said gateway further carries out the steps of monitoring the status of execution of said commands, and storing information regarding said status in said database.

31. The method of claim 28 wherein said source directory is located on a source host and stores a current version of software that executes on the source host, and said designated host contains a first version of software that executes on said designated host and a second, update directory, and wherein the synchronization comprises the steps of:

comparing the contents of the first directory in the destination host with the current directory in the source host and determining differences in their contents; and

storing said differences in the update directory in the destination host.

32. The method of claim 28 further including the step of storing a second script file containing commands that relate to service operations that are performed on a designated host.

33. The method of claim 32 wherein one of said service operations comprises a cut-over operation that includes the steps of synchronizing files in a first directory on the host with those in a second directory on the host, and causing the host to execute the files in said second directory.

34. The method of claim 33 wherein said cut-over operation further includes the step of synchronizing files in said second directory with those in a third directory, and another one of said service operations comprises a rollback operation that includes the steps of synchronizing files in said third directory with those in said second directory, and causing said host to execute the files in said second directory.

35. The method of claim 32 wherein said service operations include the stopping and starting of the operation of the host.

36. A system for deploying software onto a network resource, comprising:

a database containing information that identifies one or more hosts associated with the resource;

a user interface via which a user can transmit requests to perform operations associated with the deployment of software;

a storage system that stores script files containing commands that pertain to said operations; and

a gateway that is responsive to a request from said user interface to retrieve said information and cause said user interface to display hosts which are available for updating, and is responsive to the designation of at least one displayed host to retrieve a script file associated with a requested operation and send commands from said script file to the designated host to perform the requested operation.

37. The system of claim 36 wherein said commands are executed by an agent that is resident on the designated host.

38. The system of claim 36 wherein one of said script files contains commands that relate to service operations that are performed on a host.

39. The system of claim 38 wherein one of said service operations comprises a cut-over operation in which files in a first directory on the host are synchronized with those in a second directory on the host, and wherein the host executes the files in said second directory.

40. The system of claim 39 wherein files in said second directory are synchronized with those in a third directory, and another one of said service operations comprises a rollback operation in which files in said third directory are synchronized with those in said second directory, and the host executes the files in said second directory.

41. The system of claim 38 wherein said service operations include the stopping and starting of the operation of the host.

42. The system of claim 36 wherein said script file contains commands that relate to the synchronization of two directories on two respective hosts.

43. The system of claim 42 wherein one of the hosts comprises a source and contains a directory that stores a current version of the software that executes on that host, and the other host comprises a destination that contains a first directory that stores a current version of the software that executes on that host and a second, update directory, and wherein the synchronization compares the contents of the first directory in the destination host with the directory in the source host and determines differences in their contents, and stores said differences in the update directory in the destination host.

44. A user interface for the deployment of software associated with a resource on a network, comprising:

a display which provides a user with a selection between at least one type of operation to be performed on a host associated with the resource, and at least one type of operation to be performed between multiple hosts associated with the resource;

means responsive to a user'"'"'s selection for displaying one or more hosts associated with the resource on which the selected type of operation can be performed; and

means responsive to the designation of at least one host and a particular operation for sending a request to perform said designated operation on said designated host.

45. The user interface of claim 44 wherein said means for displaying one or more hosts includes a database containing information that identifies hosts associated with the resource and definitions of the types of operations that are authorized to be performed on each host via requests from said interface.

46. The user interface of claim 45 wherein said display further provides a user with a further selection between sending a request directly to a host to perform the designated operation or sending the request to another person to control the performance of the operation.

47. The user interface of claim 46 wherein said further selection is displayed only if the information contained in the database indicates that the user is authorized to send the request directly to the host.

48. The user interface of claim 44 wherein said display further provides a user with a further selection between sending a request directly to a host to perform the designated operation or sending the request to another person to control the performance of the operation.

49. The user interface of claim 44 wherein selection of a type of operation to be performed on a host causes a further selection to be displayed in which the user can view hosts by their name or by the type of service they provide.

50. The user interface of claim 44 further including means responsive to the termination of a designated operation for displaying the results of the operation.

51. The user interface of claim 50 wherein the display of the results provides the user with the ability to view the results on a host-by-host basis.

52. The user interface of claim 51 wherein said operations are performed in response to commands in a script file, and the results for a host are displayed as the output from the script file when it is run on the designated host.

53. A method for deploying software associated with a resource on a network, comprising the steps of:

storing a copy of the software in a predetermined directory on an source server;

executing an application on said source server in accordance with the software in said predetermined directory;

synchronizing the contents of a first designated directory on a destination server to said predetermined directory;

synchronizing the contents of a second designated directory on said destination server to said first designated directory; and

executing an application on said destination server in accordance with the software in said second designated directory.

54. The method of claim 53 wherein the step of synchronizing the contents of the second designated directory includes the step of synchronizing the contents of a third designated directory to said second designated directory prior to synchronizing said second designated directory to said first designated directory.

55. The method of claim 54 further including the step of rolling back the contents of said third designated directory to said second designated directory in response to a malfunction in the execution of the application after the second designated directory has been synchronized to said first designated directory.

56. The method of claim 55 wherein said third designated directory contains information which identifies files that are added to said second designated directory and files in said second designated directory that are modified when said second designated directory is synchronized to said first designated directory.

57. The method of claim 55 wherein said information contained in said third designated directory also identifies files that are being deleted from said second designated directory.

58. The method of claim 56 wherein said third designated directory also contains a copy of the files that are being deleted.

59. The method of claim 57 wherein said rollback step includes copying the files that were deleted from said third designated directory to said second designated directory.

60. The method of claim 55 wherein said third designated directory also contains a copy of an unmodified version of the files that are being modified.

61. The method of claim 60 wherein said rollback step includes copying said unmodified versions of the files from said third designated directory to said second designated directory.

62. The method of claim 53 further including the step of generating a manifest of differences between said second designated directory on the destination server and the predetermined directory on said source server prior to synchronizing said first designated directory.

63. The method of claim 62 further including the step of storing the differences listed on said manifest in a storage system separate from said source server and said destination server.

64. The method of claim 53 wherein said synchronizing steps comprise the steps of determining the differences between first and second directories to be synchronized, and transmitting only those files which differ between the two directories from the first directory to the second directory.

65. The method of claim 64 wherein said synchronizing steps further include the optional step of deleting files from the second directory which are not present in the first directory.

66. The method of claim 64 wherein the step of determining differences comprises the step of preparing a digest of each file in each of said first and second directories, and comparing the digests of the two directories to one another.

67. The method of claim 66 wherein a digest contains information regarding attributes of each file, including its size and last modification date.