US2016350081A1PendingUtilityA1

Automatic container definition

42
Assignee: RUNNABLE INCPriority: May 27, 2015Filed: May 27, 2015Published: Dec 1, 2016
Est. expiryMay 27, 2035(~8.9 yrs left)· nominal 20-yr term from priority
G06F 8/71G06F 8/30G06F 9/44505
42
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A container configuration system for automatically generating a container configuration for a source application is provided. The container configuration system includes at least one processor and a memory. The at least one processor configured to receive a source element associated with the source application, determine a dependency component from the source element, generate the container configuration including at least the dependency component, and provide the container configuration for execution in an execution environment enabled to execute containers.

Claims

exact text as granted — not AI-modified
1 . A container configuration system for automatically generating a container configuration for a source application, the container configuration system including at least one processor and a memory, the at least one processor configured to:
 receive a source element associated with the source application;   determine a dependency component from the source element;   generate the container configuration including at least the dependency component; and   provide the container configuration for execution in an execution environment enabled to execute containers.   
     
     
         2 . The container configuration system of  claim 1 , wherein the at least one processor is further configured to:
 determine a source element type of the source element; and   receive a configuration model associated with the source element type,   wherein determining a dependency component for the source element includes determining the dependency component based at least in part on the configuration model.   
     
     
         3 . The container configuration system of  claim 2 , wherein the configuration model includes a first dependency component indicator and first dependency component associated with the first dependency component indicator, wherein determining the dependency component from the source element further includes determining the dependency component to be the first dependency component based at least in part on the identifying the dependency component indicator within the source element. 
     
     
         4 . The container configuration system of  claim 1 , wherein generating the container configuration further includes generating a dockerfile. 
     
     
         5 . The container configuration system of  claim 1 , wherein generating the container configuration further includes:
 receiving a template to use as the container configuration; and   editing the container configuration to include a reference to the dependency component.   
     
     
         6 . The container configuration system of  claim 1 , wherein providing the container configuration for execution creates a running container within the execution environment, wherein the at least one processor is further configured to generate a container image from the running container. 
     
     
         7 . The container configuration system of  claim 1 , wherein receiving a source element associated with the source application further includes receiving the source element from a source control system. 
     
     
         8 . A computer-implemented method for automatically generating a container configuration for a source application, the method is performed using at least one processor and a memory, the method comprising:
 receiving a source element associated with the source application;   determining a dependency component from the source element;   generating the container configuration including at least the dependency component; and   providing the container configuration for execution in an execution environment enabled to execute containers.   
     
     
         9 . The method of  claim 8  further comprising:
 determining a source element type of the source element; and 
 receiving a configuration model associated with the source element type, 
 wherein determining a dependency component for the source element includes determining the dependency component based at least in part on the configuration model. 
 
     
     
         10 . The method  claim 9 , wherein the configuration model includes a first dependency component indicator and first dependency component associated with the first dependency component indicator, wherein determining the dependency component from the source element further includes determining the dependency component to be the first dependency component based at least in part on the identifying the dependency component indicator within the source element. 
     
     
         11 . The method of  claim 8 , wherein generating the container configuration further includes generating a dockerfile. 
     
     
         12 . The method of  claim 8 , wherein generating the container configuration further includes:
 receiving a template to use as the container configuration; and   editing the container configuration to include a reference to the dependency component.   
     
     
         13 . The method of  claim 8 , wherein providing the container configuration for execution creates a running container within the execution environment, the method further comprising generating a container image from the running container. 
     
     
         14 . The method of  claim 8 , wherein receiving a source element associated with the source application further includes receiving the source element from a source control system. 
     
     
         15 . A non-transitory computer-readable storage device having embedded therein a set of instructions which, when executed by one or more processors of a computer, causes the computer to:
 receive a source element associated with a source application;   determine a dependency component from the source element;   generate a container configuration including at least the dependency component; and   provide the container configuration for execution in an execution environment enabled to execute containers.   
     
     
         16 . The storage device of  claim 15 , wherein the set of instructions further causes the computer to:
 determine a source element type of the source element; and   receive a configuration model associated with the source element type,   wherein determining a dependency component for the source element includes determining the dependency component based at least in part on the configuration model.   
     
     
         17 . The storage device of  claim 16 , wherein the configuration model includes a first dependency component indicator and first dependency component associated with the first dependency component indicator, wherein determining the dependency component from the source element further includes determining the dependency component to be the first dependency component based at least in part on the identifying the dependency component indicator within the source element. 
     
     
         18 . The storage device of  claim 15 , wherein generating the container configuration further includes generating a dockerfile. 
     
     
         19 . The storage device of  claim 15 , wherein generating the container configuration further includes:
 receiving a template to use as the container configuration; and   editing the container configuration to include a reference to the dependency component.   
     
     
         20 . The storage device of  claim 15 , wherein providing the container configuration for execution creates a running container within the execution environment, wherein the set of instructions further causes the computer to generate a container image from the running container.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.