Configuring and deploying portable application containers for improved utilization of server capacity

• US 20060095435A1
• Filed: 10/21/2005
• Published: 05/04/2006
• Est. Priority Date: 10/22/2004
• Status: Abandoned Application

• Current Assignee: Bellsouth Intellectual Property Corporation (AT&T, Inc.)
• Original Assignee: Bellsouth Intellectual Property Corporation (AT&T, Inc.)
• Inventors: Lockhart, James Michael, Johnson, Christopher, Bowman, Richard, Kolar, Joseph Daniel, Talathi, Suhas, Tailor, Dilip
• Application Number:
  US11/255,494
• Publication Number:
  US 20060095435A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

Computer-implemented methods, configurations, computer program products and systems configure and deploy portable application containers (PACs) in a shared server environment. A method involves receiving metadata describing an application and receiving an instruction on what metadata to use in configuring the application where the application is associated with a PAC. The method also involves transforming the metadata into a list of commands in response to receiving the instruction and deploying the list of commands to a group of servers wherein the commands are operative to create the PAC. The PAC is a logical construct of the application configured to be logically separate from and to execute via any server in the group of servers. Each server in the group of servers can be used by multiple PACs to enable improved utilization of server capacity.

Claims

1. A computer-implemented method for configuring and deploying a portable application container, the method comprising:

receiving metadata describing an application;

receiving an instruction on what metadata to use in configuring the application wherein the application comprises a portable application container;

in response to receiving the instruction, generating a list of commands based on the metadata; and

deploying the list of commands to a logical group of servers wherein the commands are operative to create the portable application container;

wherein the portable application container comprises a logical construct of the application configured to be logically separate from and to execute via any server in the logical group of servers; and

wherein each server in the group of logical servers can be used by a plurality of portable application containers thereby enabling improved utilization of server capacity.

2. The method of claim 1, wherein receiving the metadata comprises receiving the metadata into a repository further comprising prior to receiving the metadata into the repository:

receiving the metadata via a web interface;

reviewing the metadata for conformance standards; and

in response to the metadata meeting conformance standards, transferring the metadata to the repository.

3. The method of claim 2, wherein receiving the metadata via a web interface comprises receiving at least one of the following:

a description of the portable application container;

a name of the portable application container;

a logical group of servers selection;

a type of PAC;

allocated shares for the PAC to determine correlated hardware;

a logical volume name and size; and

a disk/volume group name, size, and quantity.

4. The method of claim 2, wherein reviewing the metadata comprises at least one of the following:

correlating the metadata to one or more central processing unit resources and memory resources; and

ensuring that the metadata complies with naming standards to avoid use of the same name twice.

5. The method of claim 1, further comprising:

receiving the list of commands and executing the commands;

creating the portable application container in response to executing the commands; and

populating one or more storage arrays with at least one of data or binaries defined by the metadata and associated with the portable application container wherein the data and binaries comprise at least one of file systems, volumes, or disk groups that are accessible to any server in the logical group of servers.

6. The method of claim 5, wherein receiving the metadata comprises receiving configuration components that inform the logical group of servers where the data or binaries are located in the storage arrays and wherein the configuration components comprise at least one of the following:

a cluster service group;

a workload management profile;

a job scheduler;

a monitoring module;

a knowledge module;

a backup recovery profile;

a public TCP/IP address;

a backup TCP/IP address;

a user identifier; and

a group identifier.

7. The method of claim 1, wherein generating a list of commands based on the metadata comprises calling one or more core scripts to transform the metadata into the list of commands therein creating at least one of the following for the portable application container:

login information;

file systems;

storage;

IP addresses; and

a cluster configuration.

8. The method of claim 7, wherein calling one or more core scripts to transform the metadata into the list of commands comprises at least one of the following:

abstracting a storage configuration for the logical group of servers and providing functions to access sections of the storage configuration for the logical group of servers;

abstracting a storage configuration for the PAC and providing functions to access sections of the storage configuration for the PAC;

abstracting a storage configuration for a consolidated infrastructure software stack and providing functions to access sections of the storage configuration for the consolidated infrastructure software stack; and

abstracting a shared global configuration and providing functions in support of creating at least one of pathnames, configuration locking, time stamps, an IP address pool, a UID pool, a GID pool, or eTrust connectivity.

9. A deployment engine comprising a computer-readable medium having control logic stored therein for causing a computer to configure and deploy portable application containers (PACs) to a group of servers (POD), the deployment engine comprising at least one of the following:

a layered POD library comprising computer-readable program code for causing a computer to abstract a storage configuration for the POD and provide functions to access sections of the storage configuration for the POD;

a layered PAC library comprising computer-readable program code for causing the computer to abstract a storage configuration for the PAC and provide functions to access sections of the storage configuration for the PAC; and

a layered consolidated infrastructure software stack (CISS) library comprising computer-readable program code for causing the computer to abstract a storage configuration for a CISS and provide functions to access sections of the storage configuration for the CISS wherein there is a different CISS library for each type of server in the POD.

10. The deployment engine of claim 9, further comprising a layered global library comprising computer-readable program code for causing the computer to abstract a shared global configuration and provide functions in support of creating at least one of pathnames, configuration locking, time stamps, an IP address pool, a UID pool, a GID pool, or eTrust connectivity.

11. The deployment engine of claim 9, wherein the computer readable program code for causing the computer to configure and deploy one or more PACs comprises computer-readable program code for causing the computer to:

receive metadata describing an application;

receive an instruction on what metadata to use in configuring the application wherein the application comprises a PAC;

in response to receiving the instruction, transform the metadata into a list of commands; and

deploy the list of commands to the POD wherein the commands are operative to create the PAC;

wherein the PAC comprises a logical construct of the application configured to be logically separate from and to execute via any server in the POD; and

wherein each server in the POD can be used by a plurality of PACs thereby enabling improved utilization of server capacity.

12. The deployment engine of claim 11, wherein the computer-readable program code for causing the computer to transform the metadata into a list of commands comprises computer-readable program code for causing the computer to call one or more core functions to transform the metadata into the list of commands therein creating at least one of the following for the PAC:

login information;

file systems;

storage;

IP addresses; and

a cluster configuration.

13. The deployment engine of claim 12, wherein the computer-readable program code for causing the computer to transform the metadata into a list of commands comprises computer-readable program code for causing the computer to, in response to calling the core functions, abstract a storage configuration for at least one of the POD, the PAC, or the CISS and provide functions to access sections of the storage configuration for at least one of the POD, the PAC, or the CISS.

14. A computer-implemented system for configuring and deploying a portable application container (PAC), the system comprising:

a repository operative to receive metadata describing an application; and

a deployment engine operative to;

receive an instruction on what metadata to use in configuring the application wherein the application comprises a PAC;

in response to receiving the instruction, retrieve the metadata from the repository and generate a list of commands based on the metadata; and

deploy the list of commands to a logical group of servers wherein the commands are operative to create the PAC;

wherein the PAC comprises a logical construct of the application configured to be logically separate from and to execute via any server in the logical group of servers.

15. The system of claim 14 further comprising the logical group of servers wherein each server in the group of logical servers can be used by a plurality of PACs thereby enabling improved utilization of server capacity and wherein at least one server within the logical group of servers is operative to:

receive the list of commands and executing the commands;

create the PAC in response to executing the commands; and

populate one or more storage arrays with at least one of data or binaries defined by the metadata and associated with the PAC wherein the data and binaries comprise at least one of file systems, volumes, or disk groups that are accessible to any server in the logical group of servers.

16. The system of claim 15, wherein the deployment engine operative to retrieve the metadata is operative to receive configuration components that inform the logical group of servers where the data or binaries are located in the storage arrays and wherein the configuration components comprise at least one of the following:

a cluster service group;

a workload management profile;

a job scheduler;

a monitoring module;

a knowledge module;

a backup recovery profile;

a public TCP/IP address;

a backup TCP/IP address;

a user identifier; and

a group identifier.

17. The system of claim 14, wherein the deployment engine is further operative to:

generate or update a virtual root operative to receive a copy of the list of commands; and

copy the virtual root to each server in the group of servers.

18. The system of claim 17, further comprising the virtual root operative to update the list of commands on the group of servers.

19. The system of claim 14, further comprising a PAC requirements package server operative to:

receive the metadata via a web interface comprising a PAC requirements package;

receive a review the metadata for conformance standards; and

in response to the metadata meeting conformance standards, transfer the metadata to the repository.

20. The system of claim 19, wherein receiving the metadata via the PAC requirements package comprises receiving at least one of the following:

a description of the portable application container;

a name of the portable application container;

a logical group of servers selection;

a type of PAC;

allocated shares for the PAC to determine correlated hardware;

a logical volume name and size; and

a disk/volume group name, size, and quantity.