Installation of software stacks including uncoordinated projects

• US 20060036652A1
• Filed: 04/28/2005
• Published: 02/16/2006
• Est. Priority Date: 04/28/2004
• Status: Active Grant

• Current Assignee: Rogue Wave Software Incorporated (Perforce Software Incorporated)
• Original Assignee: OpenLogic, Inc. (Perforce Software Incorporated)
• Inventors: Cope, Rod, Weidner, Eric
• Granted Patent: US 7,669,199 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

A tool is provided for addressing a number of issues related to installing software stacks including multiple uncoordinated components such as open source projects. The tool selects a plurality of software projects, addresses dependency and resource issues and installs the projects on a computer as a functional stack. A test procedure is also created to verify proper installation. A project filter is also provided for controlling access to or installation of projects in accordance with filter criteria. In this manner, compliance with internal policies regarding the use of open source or other software is facilitated.

Claims

1. A method for use in installing stacks of uncoordinated software projects, comprising the steps of:

first operating a computer based tool to receive information identifying a plurality of uncoordinated software projects to be installed;

second operating said computer based tool to retrieve information from storage concerning installation for said plurality of uncoordinated software projects;

processing said information using said computer based tool to obtain an installation procedure for said plurality of uncoordinated software projects; and

executing said installation procedure using said computer based tool.

2. A method as set forth in claim 1, wherein said retrieved information relates to resources required by said plurality of uncoordinated projects.

3. A method as set forth in claim 2, wherein said resources comprise one of ports and files used by said plurality of uncoordinated projects.

4. A method as set forth in claim 2, wherein said step of executing comprises performing a series of checks to identify potential conflicts concerning said resources.

5. A method as set forth in claim 1, wherein said step of processing comprises determining a sequence for installing said plurality of uncoordinated projects.

6. A method as set forth in claim 1, wherein said step of executing comprises configuring at least one of said plurality of uncoordinated projects for an identified database.

7. A method as set forth in claim 1, wherein said step of executing comprises running a test dependent on said plurality of uncoordinated projects to confirm proper installation and operation of said projects.

8. A method as set forth in claim 1, further comprising the steps of receiving, after said step of executing, update information identifying an update for one of said uncoordinated software projects, processing said update information using said computer based tool to obtain a further installation procedure for said update and executing said further installation procedure using said computer based tool.

9. A method as set forth in claim 1, further comprising the steps of receiving, after said step of executing, update information identifying an update for one of said uncoordinated software projects and prompting a user for instructions concerning said update.

10. A method as set forth in claim 1, wherein at least one of said plurality of uncoordinated software projects is an open source project and said step of processing comprises determining said installation procedure for said stack including said open source project.

11. A method as set forth in claim 1, wherein at least one of said plurality of uncoordinated software projects is an application development project that operates at a tools or applications layer of said stack above an operating system level of said stack and said step of processing comprises determining said installation procedure for said stack including said application development project.

12. A method as set forth in claim 1, further comprising the step of operating said computer based tool to execute a project filter whereby said plurality of uncoordinated software projects are selected based on filter criteria defining a policy regarding one of access to and use of software projects.

13. A method as set forth in claim 1, further comprising the step of substituting, after said step of executing, for a first project of said plurality of projects, a substitute project having substantially equivalent functionality.

14. A system operable to install software, comprising:

a configuration module for configuring a plurality of uncoordinated software projects into a stack, said uncoordinated software projects being free of specific preconfiguration for cooperative and dependent operation in said stack; and

an installer for installing the stack on a computer.

15. A system as set forth in claim 14, wherein the stack is a compilation of the plurality of uncoordinated software projects into a plurality of dependent software projects.

16. A system as set forth in claim 14, further comprising a shared resource, wherein the shared resource comprises a function;

a constant;

a class;

an object;

a structure; and

/or license information, and wherein the plurality of dependent software projects are operable to use at least a portion of the shared resource.

17. A system as set forth in claim 14, wherein the stack is operable to manage a first project, wherein the first project includes at least one dependent software project.

18. A system as set forth in claim 17, wherein the first project is user configurable based on inclusion of said at least one dependent software project.

19. A system as set forth in claim 14, wherein a configuration module is adapted to determine installation conflicts.

20. A system as set forth in claim 14, wherein said configuration module is further operative for configuring said stack, after installation of said stack on said computer, with respect to an update for one of said projects.

21. A system as set forth in claim 14, wherein said configuration module is further operative for prompting a user for instructions regarding an update available for one of said software projects.

22. A system as set forth in claim 14, wherein said configuration module is further operative for executing a project filter whereby said plurality of uncoordinated software projects are selected based on filter criteria defining a policy regarding one of access to and use of software projects.

23. A system as set forth in claim 14, wherein said installer is further operative for substituting for a first project of said stack a substitute project having substantially equivalent functionality.

24. An apparatus for use in installing stacks of uncoordinated software projects comprising:

interface logic for receiving stack information identifying a stack including a plurality of uncoordinated software projects to be installed on a processing platform;

storage for storing installation information related to said plurality of uncoordinated software projects; and

processing logic for selectively accessing said installation information based on said stack information, determining an installation procedure for said stack and executing said installation procedure.

25. An apparatus as set forth in claim 24, wherein said processing logic is operative for performing a series of checks to identify potential conflicts concerning resources required by said plurality of uncoordinated software projects.

26. An apparatus as set forth in claim 24, wherein said processing logic is operative for determining a sequence for installing said plurality of uncoordinated projects.

27. An apparatus as set forth in claim 24, wherein said processing logic is operative for running a test dependent on said plurality of uncoordinated projects to confirm proper installation and operation of said projects.

28. An apparatus as set forth in claim 24, wherein said processing logic is operative for receiving information identifying an update for one of said uncoordinated software projects, processing said update information to obtain a further installation procedure for said update, and executing said further installation procedure.

29. An apparatus as set forth in claim 24, wherein said processing logic is operative for receiving update information identifying an update for one of said uncoordinated software projects and prompting a user for instructions concerning said update.

30. An apparatus as set forth in claim 24, wherein said processing logic is further operative for executing a project filter whereby said plurality of uncoordinated software projects are selected based on filter criteria defining a policy regarding one of access to and use of software projects.

31. A method for use in installing stacks including at lest one open source software project, comprising the steps of:

providing a graphical installer tool for assisting a user in identifying a set of software projects including at least one open source software project for installation on a subject machine, wherein the installer tool is operative to ensure that the set of projects is free from unsatisfied required dependency relationships;

receiving a first set of projects, established using the graphical installer tool, for installation on the subject machine;

executing logic to determine an installation procedure including an installation sequence for installing the set of projects on the subject machine;

installing the set of projects on the subject machine in accordance with the determined installation procedure;

determining a test procedure, specific to said set of projects, for verifying proper installation of said set of projects on said subject machine; and

after said step of installing, executing said test procedure.

32. A method as set forth in claim 31, further comprising the steps of identifying first and second software projects having substantially equivalent functionality for optional inclusion in said set of projects, first installing said first project in said set of projects and second installing said second project in said set of projects.

33. A method as set forth in claim 31, further comprising the step of identifying an update for a first project of said set of projects and installing said update.

34. A method as set forth in claim 31, wherein said step of providing comprises executing a project filter whereby said set of software projects is selected based on filter criteria defining a policy regarding one of access to and use of software projects.

35. A system operable to install software, comprising

storage for storing information regarding at least one open source software component;

a filter that compares first filter information for a computer to second filter information of said at least one open source software project; and

an installer response to said filter to determine an installation procedure for the computer based on a comparison of the first and second filter information.

36. A system as set forth in claim 35, wherein the storage further stores information regarding at least one proprietary software project.

37. A system as set forth in claim 35, wherein second filter information includes an association with respect to one of a General Public License, a Lesser General Public License, and a proprietary license.

38. A method for use in installing software comprising:

first operating a computer based tool to select a plurality of uncoordinated software projects;

based on a selection of the plurality of uncoordinated projects establishing a shared resource; and

installing the plurality of uncoordinated software projects on a computer, wherein the plurality of uncoordinated software projects are each operable to use the shared resource.

39. A method as set forth in claim 38, wherein the shared resource comprises one of a function;

a constant;

a class;

an object;

a structure and/or license information.

40. A method as set forth in claim 48, wherein the shared resource is a library of functions for the plurality of uncoordinated software projects.

40-1. A method as set forth in claim 48, wherein the shared resource is a library of functions for the plurality of uncoordinated software projects.

41. A method for use in installing stacks of uncoordinated software projects, comprising the steps of:

accessing a configuration module operative for assisting in installation of stacks of software projects including stacks of uncoordinated projects;

providing, to said configuration module, input information regarding a stack of interest; and

receiving installation information from said installation module regarding a first stack of software projects.

42. A method as set forth in claim 41, wherein said input information includes information regarding a project or a function of said stack.

43. A method as set forth in claim 41, wherein said installation information includes one of an installation procedure for said first stack, projects reflecting a configuration for use in said first stack, and installation tools for use in installing said first stack.