Enabling attributes for containerization of applications

• US 10,565,092 B2
• Filed: 10/06/2017
• Issued: 02/18/2020
• Est. Priority Date: 10/06/2017
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Benes, Eduard, Marhefka, Matus
• Primary Examiner(s): Wang, Philip
• Application Number:
  US15/727,320
• Publication Number:
  US 20190108116A1
• Time in Patent Office: 865 Days
• Field of Search: None
• CPC Class Codes: G06F 11/0712 in a virtual computing platform, e.g. logically partitioned systems
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/301 where the computing system is a virtual computing platform, e.g. logically partitioned systems virtual machines G06F9/45533; logical partitioning of resources G06F9/5077
• CPC Class Codes: G06F 11/302 where the computing system component is a software system
• CPC Class Codes: G06F 11/3055 Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction by redundancy in operation G06F11/14; error detection or correction by redundancy in hardware G06F11/16
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 11/3696 Methods or tools to render software testable
• CPC Class Codes: G06F 21/552 involving long-term monitoring or reporting
• CPC Class Codes: G06F 2201/86 Event-based monitoring
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: G06F 9/455 Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

Implementations of the disclosure include a framework to provide an optimal execution environment for applications in software containers. In one implementation an apparatus is provided that includes a memory to store a plurality of application containers and a processing device coupled to the memory. The processing device is to identify an application to execute in a container associated with a first environment. A monitoring component is injected into the first environment to collect event data associated with an interaction of the application with one or more system resources. Using the collected event data, an indication of a restraint on an execution of the application is identified. Thereupon, one or more attributes are generated to update the application container to execute the application in a second environment in view of the restraint.

Claims

1. An apparatus comprising:

a memory; and

a processing device, operatively coupled to the memory, to;

identify an application to execute in an application container associated with a first environment;

inject a monitoring component into the first environment to collect event data associated with an interaction of the application with one or more system resources;

identify, using the collected event data and a containerization technology specification associated with the application container, an indication of a restraint that causes a break in an execution of the application; and

generate one or more attributes for reconfiguration of application container to execute the application in a second environment by determining that the one or more attributes cause the restraint to be removed.

2. The apparatus of claim 1, wherein the one or more attributes to remove the restraint on executing the application from the application container of the second environment.

3. The apparatus of claim 1, wherein the processing device is further to adjust a privilege level for operations executed by the application in the second environment.

4. The apparatus of claim 1, wherein the processing device is further to modify permissions with regard to an account associated with the application container.

5. The apparatus of claim 1, wherein the processing device is further to:

determine whether the one or more attributes to update the application container are in compliance with a container policy associated with the second environment; and

generate an instance of the application to execute in the second environment in view of the determined compliance with the container policy.

6. The apparatus of claim 1, wherein the processing device is further to:

determine, using the collected event data, whether the application is sharing data outside of the application container with another system process; and

responsive to determining that the application in the application container is sharing data, inject the monitoring component into the first environment outside of the application container.

7. The apparatus of claim 6, wherein the processing device is further to, responsive to determining that the application in the application container is not sharing data, inject the monitoring component inside of the application container.

8. A method comprising:

receiving, by a processing device, execution test components to apply to an application of an application container in a first environment;

responsive to applying the execution test components, intercept, by the processing device, events associated with an interaction of the application with one or more system resources;

detect, by the processing device, a restraint that causes a break in an execution of the application in view of the events and a containerization technology specification associated with the application container;

determining, by the processing device, one or more attributes for reconfiguration of the application container in view of determining that the one or more attributes cause the restraint to be removed.

9. The method of claim 8, further comprising generating an instance of the application for the reconfigured application container of a second environment to remove the restraint on the execution of the application.

10. The method of claim 8, further comprising modifying permissions with regard to an account associated with the application container.

11. The method of claim 9, further comprising:

determining whether the one or more attributes to update the application container are in compliance with a container policy associated with the second environment; and

generating the instance of the application to execute in the second environment in view of the determined compliance with the container policy.

12. The method of claim 8, further comprising:

determining, using the intercepted events, whether the application is sharing data outside of the application container with another system process; and

responsive to determining that the application in the application container is sharing data, injecting a monitoring component into the first environment outside of the application container.

13. The method of claim 12, further comprising, responsive to determining that the application in the application container is not sharing data, injecting the monitoring component inside of the application container.

14. A non-transitory computer-readable medium comprising instructions that, when executed by a processing device, cause the processing device to:

identify, by the processing device, an application to execute in an application container associated with a first environment;

inject a monitoring component into the first environment to collect event data associated with an interaction of the application with one or more system resources;

identify, using the collected event data and a containerization technology specification associated with the application container, an indication of a restraint that causes a break in an execution of the application; and

generate one or more attributes for reconfiguration of the application container to execute the application in a second environment by determining that the one or more attributes cause the restraint to be removed.

15. The non-transitory computer-readable medium of claim 14, wherein the one or more attributes to remove the restraint on executing the application from the application container of the second environment.

16. The non-transitory computer-readable medium of claim 14, wherein the processing device is further to adjust a privilege level for operations executed by the application in the second environment.

17. The non-transitory computer-readable medium of claim 14, wherein the processing device is further to modify permissions with regard to an account associated with the application container.

18. The non-transitory computer-readable medium of claim 14, wherein the processing device is further to:

determine whether the one or more attributes to update the application container are in compliance with a container policy associated with the second environment; and

generate an instance of the application to execute in the second environment in view of the determined compliance with the container policy.

19. The non-transitory computer-readable medium of claim 14, wherein the processing device is further to:

determine, using the collected event data, whether the application is sharing data outside of the application container with another system process; and

responsive to determining that the application in the application container is sharing data, inject the monitoring component into the first environment outside of the application container.

20. The non-transitory computer-readable medium of claim 19, wherein the processing device is further to, responsive to determining that the application in the application container is not sharing data, inject the monitoring component inside of the application container.