Managing a containerized service using a system manager and a deployment engine indicating an operational status of the one or more containers

Patent metadata

Field	Value
Publication number	US-12591439-B2
Application number	US-202318197248-A
Country	US
Kind code	B2
Filing date	May 15, 2023
Priority date	May 15, 2023
Publication date	Mar 31, 2026
Grant date	Mar 31, 2026

Abstract

A containerized service can be managed using a system manager and a deployment engine. The system manager can receive a service identifier that can identify a configuration file of the containerized service. The configuration file can be used to initiate one or more containers to run the containerized service. The system manager can transmit the configuration file to the deployment engine integrated with the system manager. The deployment engine can create a service container prior to initiating the one or more containers that can run the containerized service based on a container status of the service container. The service container can be used to manage the one or more containers. The system manager can initiate the containerized service in response to receiving a ready notification from the deployment engine indicating an operational status of the one or more containers.

First claim

What is claimed is:

1 . A system comprising:
a processing device; and a memory device including instructions that are executable by the processing device for causing the processing device to perform operations comprising:
receiving, by a system manager, a service identifier configured to identify a configuration file of a containerized service, the configuration file usable to initiate one or more containers to run the containerized service;
transmitting, by the system manager, the configuration file to a deployment engine integrated with the system manager, the deployment engine being configured to create a service container prior to initiating the one or more containers, the service container usable to manage the one or more containers configured to run the containerized service based on a container status of the service container;
initiating, by the system manager, the containerized service in response to receiving a ready notification from the deployment engine indicating an operational status of the one or more containers;
determining, by the system manager, the operational status for a lifecycle of the one or more containers based on the container status of the service container;
detecting, by the system manager, an adjustment to the operational status of the one or more containers to be inactive;
in response to detecting the adjustment to the operational status of the one or more containers to be inactive, adjusting, by the system manager, a service status of the containerized service to be inactive;
in response to adjusting the service status of the containerized service to be inactive, identifying, by the system manager, a restart configuration of the containerized service; and
adjusting, by the system manager, the service status of the containerized service to be active based on the restart configuration, the service status of the containerized service being active indicating that the containerized service is restarted and that the container status of the service container is active.

2 . The system of claim 1 , wherein the deployment engine is configured to transmit the ready notification to the system manager in response to receiving an activation message from a particular container of the one or more containers, and wherein the activation message is configured to indicate that the particular container is active.

3 . The system of claim 2 , wherein the deployment engine is further configured to identify the particular container of the one or more containers by parsing metadata of the configuration file.

4 . The system of claim 1 , wherein the operations further comprise, subsequent to initiating the containerized service:
identifying a descendant service associated with the containerized service using the service identifier, wherein the descendant service is created based on the containerized service; and in response to identifying the descendant service, adjusting a resource allocation of the containerized service or the descendant service.

5 . The system of claim 1 , wherein the operations further comprise, prior to receiving the ready notification from the deployment engine:
determining that a predetermined amount of time has been exceeded with respect to waiting to receive the ready notification from the deployment engine; and in response to determining that the predetermined amount of time has been exceeded, preventing the containerized service from being initiated.

6 . A method comprising:
receiving, by a system manager, a service identifier configured to identify a configuration file of a containerized service, the configuration file usable to initiate one or more containers to run the containerized service; transmitting, by the system manager, the configuration file to a deployment engine integrated with the system manager, the deployment engine being configured to create a service container prior to initiating the one or more containers, the service container usable to manage the one or more containers configured to run the containerized service based on a container status of the service container; initiating, by the system manager, the containerized service in response to receiving a ready notification from the deployment engine indicating an operational status of the one or more containers; determining, by the system manager, the operational status for a lifecycle of the one or more containers based on the container status of the service container; detecting, by the system manager, an adjustment to the operational status of the one or more containers to be inactive; in response to detecting the adjustment to the operational status of the one or more containers to be inactive, adjusting, by the system manager, a service status of the containerized service to be inactive; in response to adjusting the service status of the containerized service to be inactive, identifying, by the system manager, a restart configuration of the containerized service; and adjusting, by the system manager, the service status of the containerized service to be active based on the restart configuration, the service status of the containerized service being active indicating that the containerized service is restarted and that the container status of the service container is active.

7 . The method of claim 6 , wherein the deployment engine is configured to transmit the ready notification to the system manager in response to receiving an activation message from a particular container of the one or more containers, and wherein the activation message is configured to indicate that the particular container is active.

8 . The method of claim 7 , wherein the deployment engine is further configured to identify the particular container of the one or more containers by parsing metadata of the configuration file.

9 . The method of claim 6 , further comprising, subsequent to initiating the containerized service:
identifying a descendant service associated with the containerized service using the service identifier, wherein the descendant service is created based on the containerized service; and in response to identifying the descendant service, adjusting a resource allocation of the containerized service or the descendant service.

10 . The method of claim 6 , further comprising, prior to receiving the ready notification from the deployment engine:
determining that a predetermined amount of time has been exceeded with respect to waiting to receive the ready notification from the deployment engine; and in response to determining that the predetermined amount of time has been exceeded, preventing the containerized service from being initiated.

11 . A non-transitory computer-readable medium comprising program code executable by a processing device for causing the processing device to perform operations comprising:
receiving, by a system manager, a service identifier configured to identify a configuration file of a containerized service, the configuration file usable to initiate one or more containers to run the containerized service; transmitting, by the system manager, the configuration file to a deployment engine integrated with the system manager, the deployment engine being configured to create a service container prior to initiating the one or more containers, the service container usable to manage the one or more containers configured to run the containerized service based on a container status of the service container; initiating, by the system manager, the containerized service in response to receiving a ready notification from the deployment engine indicating an operational status of the one or more containers; determining, by the system manager, the ope

Assignees

• Red Hat Inc

Inventors

• Rothberg Valentin
• Walsh Daniel

Classifications

• G06F9/44505 Primary

  Configuring for program initiating, e.g. using registry, configuration files · CPC title