Development and build environment for packaged software delivery

• US 7,458,073 B1
• Filed: 12/03/2003
• Issued: 11/25/2008
• Est. Priority Date: 12/02/2003
• Status: Expired due to Term

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Kakumani, Badari, Balint, Matthew, Darling, Glen, Devlin, Mala
• Primary Examiner(s): Zhen; Li B
• Application Number:
  US10/728,370
• Time in Patent Office: 1,819 Days
• Field of Search: 717168-172, 717/122, 717/167, 717/163, 719/331
• US Class Current: 717/168
• CPC Class Codes: G06F 8/656 while running
• CPC Class Codes: G06F 9/4416 Network booting; Remote initial program loading [RIPL]
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: G06F 9/45537 Provision of facilities of other operating environments, e.g. WINE I/O emulation G06F13/105

Abstract

A development and build environment creates information used by the master node and nodes in a network of nodes to perform software loading and evaluation during boot and normal runtime. The invention creates metadata and dependency data for packages and modules. Module metadata are created and inserted into the package that includes information such as the module'"'"'s: binary signature, name, directory path, characteristics, and API dependency information. Packages are formed based on features/characteristics or purpose. A package contains one or more modules. Metadata are created for each package and inserted into the package that includes information such as the package'"'"'s: name, build date, and characteristics.

Claims

1. A method of a build environment for packaged software delivery in a distributed network of nodes, the method comprising the computer-implemented steps of:

the build environment compiling source code files into one or more executable file modules;

wherein each of the one or more modules contains an image for a process or a dynamically linked library (DLL);

the build environment creating a software package that comprises the one or more modules, wherein the software package is delivered to the nodes in the distributed network;

wherein the software package is created based on at least one of a feature, characteristic, or purpose;

the build environment creating metadata for a first module, of the one or more modules, that includes any module information such as the first module'"'"'s;

binary signature, name, directory path, and characteristics, wherein the first module provides and uses at least one application program interface (API);

the build environment gathering API dependency information for the first module by

(a) receiving a list of dependent modules for a given process or DLL of the first module;

(b) storing, in the metadata of the first module, dependency information for the dependent modules in the list, wherein the dependency information includes API names and versions that the process or DLL depends on;

(c) collecting additional dependency information from one or more module specifications that are separate from the list of dependent modules, wherein the additional dependency information includes API names and versions that the process or DLL depends on; and

(d) storing the additional dependency information in the metadata of the first module; and

the build environment inserting the metadata of the first module into the software package.

2. A method as recited in claim 1, wherein a linker creates the list of dependent modules for the given process or DLL and places the list in the metadata of the first module.

3. A method as recited in claim 1, further comprising the steps of:

creating metadata for each API; and

inserting the API metadata into the software package, wherein metadata for an API includes, but is not limited to;

the API'"'"'s name and version.

4. A method as recited in claim 1, further comprising the step of:

calculating a binary signature for each module of the one or more modules and inserting the binary signature into the respective module'"'"'s metadata;

wherein each unique version of a module will have a unique binary signature.

5. A method as recited in claim 1, further comprising the steps of:

creating metadata for the software package that includes any package information such as the software package'"'"'s;

name, build date, and characteristics; and

inserting the metadata of the software package into the software package.

6. A method of a build environment for packaged software delivery in a distributed network of nodes, the method comprising the computer-implemented steps of:

the build environment compiling source code files into one or more executable file modules;

wherein each of the one or more modules contains an image for a process or a dynamically linked library (DLL);

the build environment creating a software package that comprises the one or more modules, wherein the software package is delivered to the nodes in the distributed network;

the build environment creating metadata for a first module, of the one or more modules, that includes any module information such as the first module'"'"'s;

binary signature, name, directory path, and characteristics, wherein the first module provides and uses at least one application program interface (API);

the build environment gathering API dependency information for the first module by

(a) receiving a list of dependent modules for a given process or DLL of the first module; and

(b) storing, in the metadata of the first module, dependency information for the dependent modules in the list, wherein the dependency information includes API names and versions that the process or DLL depends on; and

the build environment inserting the metadata of the first module into the software package.

7. A method as recited in claim 6, wherein a linker creates the list of dependent modules for the given process or DLL and places the list in the metadata of the first module.

8. A method as recited in claim 6, further comprising the step of:

the build environment collecting additional dependencies from one or more module specifications that are separate from the list of dependent modules and placing the additional dependencies into the metadata of the first module;

wherein the additional dependencies documented in each module lists API names and versions that the process or DLL depends on.

9. A method as recited in claim 6, further comprising the steps of:

creating metadata for each API; and

inserting the API metadata into the software package, wherein metadata for an API includes, but is not limited to;

the API'"'"'s name and version.

10. A method as recited in claim 6, further comprising the step of:

calculating a binary signature for each module of the one or more modules and inserting the binary signature into the respective module'"'"'s metadata;

wherein each unique version of a module will have a unique binary signature.

11. A method as recited in claim 6, wherein packages are created based on at least one of a feature, characteristic, or purpose.

12. A method as recited in claim 6, further comprising the steps of:

creating metadata for the software package that includes any package information such as the package'"'"'s;

name, build date, and characteristics; and

inserting the metadata of the software package into the software package.

13. An apparatus for a build environment for packaged software delivery in a distributed network of nodes, comprising:

means for the build environment compiling source code files into one or more executable file modules;

wherein each of the one or more modules contains an image for a process or a dynamically linked library (DLL);

means for the build environment creating a software package that comprises the one or more modules, wherein the software package is delivered to the nodes in the distributed network;

means for the build environment creating metadata for a first module, of the one or more modules, that includes any module information such as the first module'"'"'s;

binary signature, name, directory path, and characteristics, wherein the first module provides and uses at least one application program interface (API);

means for the build environment gathering API dependency information for the first module by

(a) receiving a list of dependent modules for a given process or DLL of the first module; and

(b) storing, in the metadata of the first module, dependency information for the dependent modules in the list, wherein the dependency information includes API names and versions that the process or DLL depends on; and

means for the build environment inserting the metadata of the first module into the software package.

14. An apparatus as recited in claim 13, further comprising:

a linker, wherein said linker creates the list of dependent modules for the given process or DLL and places the list in the metadata of the first module.

15. An apparatus as recited in claim 13, further comprising:

means for the build environment collecting additional dependencies from one or more module specifications that are separate from the list of dependent modules and placing the additional dependencies into the metadata of the first module;

wherein the additional dependencies documented in each module lists API names and versions that the process or DLL depends on.

16. An apparatus as recited in claim 13, further comprising:

means for creating metadata for each API; and

means for inserting the API metadata into the software package, wherein metadata for an API includes, but is not limited to;

the API'"'"'s name and version.

17. An apparatus as recited in claim 13, further comprising:

means for calculating a binary signature for each module of the one or more modules and inserting the binary signature into the respective module'"'"'s metadata, wherein each unique version of a module will have a unique binary signature.

18. An apparatus as recited in claim 13, wherein packages are created based on at least one of a feature, characteristic, or purpose.

19. An apparatus as recited in claim 13, further comprising:

means for creating metadata for the software package that includes any package information such as the software package'"'"'s;

name, build date, and characteristics; and

means for inserting the metadata of the software package into the software package.

20. A computer-readable medium, tangibly embodied on a physical storage medium, wherein the computer-readable medium is one of a volatile medium or a non-volatile medium, the computer-readable medium carrying one or more sequences of instructions of a build environment for packaged software delivery in a distributed network of nodes, which instructions, when executed by one or more processors, cause the one or more processors to carry out the steps of:

compiling source code files into one or more executable file modules;

wherein each of the one or more modules contains an image for a process or a dynamically linked library (DLL);

creating a software package that comprises the one or more modules, wherein the software package is delivered to the nodes in the distributed network;

creating metadata for a first module, of the one or more modules, that includes any module information such as the module'"'"'s;

binary signature, name, directory path, and characteristics, wherein the first module provides and uses at least one application program interface (API);

gathering API dependency information for the first module by

(a) receiving a list of dependent modules for a given process or DLL of the first module; and

(b) storing, in the metadata of the first module, dependency information for the dependent modules in the list, wherein the dependency information includes API names and versions that the process or DLL depends on; and

inserting the metadata of the first module into the software package.

21. A computer-readable medium as recited in claim 20, wherein a linker creates the list of dependent modules for the given process or DLL and places the list in the metadata of the first module.

22. A computer-readable medium as recited in claim 20, wherein the one or more stored sequences of instructions which, when executed by the one or more processors, further cause the one or more processors to carry out the step of:

collecting additional dependencies from one or more module specifications that are separate from the list of dependent modules and placing the additional dependencies into the metadata of the first module;

wherein the additional dependencies documented in each module lists API names and versions that the process or DLL depends on.

23. A computer-readable medium as recited in claim 20, wherein the one or more stored sequences of instructions which, when executed by the one or more processors, further cause the one or more processors to carry out the steps of:

creating metadata for each API; and

inserting the API metadata into the software package, wherein metadata for an API includes, but is not limited to;

the API'"'"'s name and version.

24. A computer-readable medium as recited in claim 20, wherein the one or more stored sequences of instructions which, when executed by the one or more processors, further cause the one or more processors to carry out the step of:

calculating a binary signature for each module of the one or more modules and inserting the binary signature into the respective module'"'"'s metadata, wherein each unique version of a module will have a unique binary signature.

25. A computer-readable medium as recited in claim 20, wherein packages are created based on at least one of a feature, characteristic, or purpose.

26. A computer-readable medium as recited in claim 20, wherein the one or more stored sequences of instructions which, when executed by the one or more processors, further cause the one or more processors to carry out the steps of:

creating metadata for the software package that includes any package information such as the software package'"'"'s;

name, build date, and characteristics; and

inserting the metadata of the software package into the software package.

27. An apparatus running a build environment for packaged software delivery in a distributed network of nodes, the apparatus comprising:

a network interface that is coupled to a data network for receiving one or more packet flows therefrom;

a processor;

one or more stored sequences of instructions, of the build environment, which instructions, when executed by the processor, cause the processor to carry out the steps of;

compiling source code files into one or more executable file modules;

wherein each of the one or more modules contains an image for a process or a dynamically linked library (DLL);

creating a software package that comprises the one or more modules, wherein the software package is delivered to the nodes in the distributed network;

wherein packages are created based on at least one of a feature, characteristic, or purpose;

creating metadata for a first module, of the one or more modules, that includes any module information such as the first module'"'"'s;

binary signature, name, directory path, and characteristics, wherein the first module provides and uses at least one application program interface (API);

gathering API dependency information for the first module by

(a) receiving a list of dependent modules for a given process or DLL of the first module;

(b) storing, in the metadata of the first module, dependency information for the dependent modules in the list, wherein the dependency information includes API names and versions that the process or DLL depends on;

(c) collecting additional dependency information from one or more module specifications that are separate from the list of dependent modules, wherein dependency information includes API names and versions that the process or DLL depends on; and

(d) storing the additional dependency information in the metadata of the first module; and

inserting the metadata of the first module into the software package.

28. An apparatus as recited in claim 27, wherein a linker creates the list of dependent modules for the given process or DLL and places the list in the metadata of the first module.

29. An apparatus as recited in claim 27, wherein the one or more stored sequences of instructions which, when executed by the processor, further cause the processor to carry out the steps of:

creating metadata for each API; and

inserting the API metadata into the software package, wherein metadata for an API includes, but is not limited to;

the API'"'"'s name and version.

30. An apparatus as recited in claim 27, wherein the one or more stored sequences of instructions which, when executed by the processor, further cause the processor to carry out the step of:

calculating a binary signature for each module of the one or more modules and inserting the binary signature into the respective module'"'"'s metadata, wherein each unique version of a module will have a unique binary signature.

31. An apparatus as recited in claim 27, wherein the one or more stored sequences of instructions which, when executed by the processor, further cause the processor to carry out the steps of:

creating metadata for the software package that includes any package information such as the software package'"'"'s;

name, build date, and characteristics; and

inserting the metadata of the software package into the software package.