# US 2024/0202040 A1 · Managing workloads in a container orchestration system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0202040 A1
- Document ID: US20240202040A1
- Status: Published application
- Kind: A1
- Application number: 18/169,392
- Filed: 2023-02-15
- Published: 2024-06-20
- Earliest claimed: 2022-12-19
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Jakob Christopher Lang; Utz Bacher
- Web page: https://patentgrep.com/patent/US20240202040A1

## CPC

- G06F 9/5044: {considering hardware capabilities}
- G06F 9/505: {considering the load}
- G06F 9/5077: {Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455)}
- G06N 10/00: Quantum computing, i.e. information processing based on quantum-mechanical phenomena
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS

## Abstract

A computer-implemented method of using a workload management system designed for workloads of a first computing architecture as well as for workloads of a second computing architecture is disclosed. The method comprises deploying a workload management control plane under a first computing architecture, identifying, by the workload management control plane, a requested remote workload only available for the second computing architecture, creating, by the workload management control plane, a proxy compute resource as interface for the requested remote workload, starting, by the proxy compute resource, the remote workload, controlling, by the proxy compute resource, an operation of the remote workload in a 1:1 relationship, by: upon receiving a termination signal, terminating the remote workload by the proxy compute resource and self-terminating the proxy compute resource, and upon a termination of the remote workload terminate the proxy compute resource.

## Claims

### Claim 1

A computer-implemented method for using a workload management system designed for workloads of a first computing architecture for workloads of a second computing architecture, the method comprising:
deploying a workload management control plane under a first computing architecture;
identifying, by the workload management control plane, a requested remote workload only available for the second computing architecture;
creating, by the workload management control plane, a proxy compute resource as interface for the requested remote workload;
starting, by the proxy compute resource, the requested remote workload; and
controlling, by the proxy compute resource, an operation of the remote workload in a 1:1 relationship comprising:
upon receiving a termination signal, terminating the remote workload by the proxy compute resource; and
upon a termination of the remote workload, self-terminating by the proxy compute resource.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
monitoring continuously, by the proxy compute resource, a correct operation of the remote workload.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
forwarding, by the proxy compute resource, network traffic to and from the remote workload.

### Claim 4 (depends on 1)

The method of claim 1, wherein the starting further comprises:
starting the remote workload with the same deployment characteristics, as specified by the received request.

### Claim 5 (depends on 1)

The method of claim 1, wherein the starting further comprises:
ensuring, by the proxy compute resource, availability of resources required to operate the remote workload.

### Claim 6 (depends on 1)

The method of claim 1, wherein the starting further comprises:
upon determining an executing related remote workload, terminating the executing related remote workload with all associated resources.

### Claim 7 (depends on 1)

The method of claim 1, wherein the first computing architecture is an x86 architecture.

### Claim 8 (depends on 7)

The method of claim 7, wherein the second computing architecture is a zSystems architecture.

### Claim 9 (depends on 1)

The method of claim 1, wherein the workload management system is a container management platform.

### Claim 10 (depends on 1)

The method of claim 1, wherein a request of the remote workload to a storage system or I/O attachments is forwarded to and performed by the proxy compute resource.

### Claim 11

A workload management system designed for workloads of a first computing architecture enabled for a workload of a second computing architecture, the workload management system comprising:
a processor and a memory, the memory being operatively coupled to the processor, wherein the memory stores program code portions, which, when executed by the processor, enable the processor to:
deploy a workload management control plane under a first computing architecture;
identify, by the workload management control plane, a requested remote workload only available for the second computing architecture;
create, by the workload management control plane, a proxy compute resource as interface for the requested remote workload;
start, by the proxy compute resource, the requested remote workload; and
control, by the proxy compute resource, an operation of the remote workload in a 1:1 relationship, comprising:
upon reception of a termination signal, terminating the remote workload by the proxy compute resource; and
upon a termination of the remote workload, self-terminating by the proxy compute resource.

### Claim 12 (depends on 11)

The workload management system of claim 11, wherein the processor is also enabled to:
monitor continuously, by the proxy compute resource, a correct operation of the remote workload.

### Claim 13 (depends on 11)

The workload management system of claim 11, wherein the processor is also enabled to:
forward, using the proxy compute resource, network traffic to and from the remote workload.

### Claim 14 (depends on 11)

The workload management system of claim 11, wherein the processor, during the start, is also enabled to:
start the remote workload with the same deployment characteristics, as specified by the received request.

### Claim 15 (depends on 11)

The workload management system of claim 11, wherein the processor, during the start, is also enabled to:
ensure availability, using the proxy compute resource, of resources required to operate the remote workload.

### Claim 16 (depends on 11)

The workload management system of claim 11, wherein the processor, during the start, is also enabled to:
upon a determination of an executing related remote workload, terminate the determined executing related remote workload with all associated resources.

### Claim 17 (depends on 11)

The workload management system of claim 11, wherein the first computing architecture is an x86 architecture.

### Claim 18 (depends on 17)

The workload management system of claim 17, wherein the second computing architecture is a zSystems architecture.

### Claim 19 (depends on 11)

The workload management system of claim 11, wherein the workload management system is a container management platform.

### Claim 20

A computer program product for using a workload management system designed for workloads of a first computing architecture, for workloads of a second computing architecture, the computer program product comprising:
a computer readable storage medium having program instructions embodied therewith, the program instructions being executable by one or more computing systems or controllers to cause the one or more computing systems to:
deploy a workload management control plane under a first computing architecture;
identify, using the workload management control plane, a requested remote workload only available for the second computing architecture;
create, using the workload management control plane, a proxy compute resource as interface for the requested remote workload;
start, using the proxy compute resource, the remote workload; and
control, using the proxy compute resource, an operation of the remote workload in a 1:1 relationship, comprising:
upon receiving a termination signal, terminating the remote workload by the proxy compute resource; and
upon termination of the remote workload, self-termination by the proxy compute resource.
