Templating Component for Transparent Cloud Resource Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In containerized cloud environments, integrating command line tool interactions with operator/services is challenging, leading to inconsistencies, increased complexity, and reliability issues, as well as difficulties in managing and cleaning up cloud resources, which can result in longer delivery times, increased costs, and service level agreement violations.

Innovation Solution

A templating and detemplating component that allows transparent integration with the cloud environment, enabling execution of commands through a command line tool and creation of custom resources, with a reconciliation loop to maintain the desired state, thereby imitating customer behavior and reducing external dependencies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If command line tool interactions are integrated with operator/services in containerized cloud environments, then automation extent is improved, but device complexity increases

Engineering Contradiction:
Improveautomation of cloud resource managementVSAvoidsystem complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (the operator framework and reconciliation loop mechanism) that mediates between command line tool interactions and the underlying cloud infrastructure. This intermediary translates ad-hoc commands into standardized resource operations, managing complexity internally while presenting a simplified interface to users, thereby improving automation without proportionally increasing observable system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments cloud resource management into distinct operational layers: command line interface layer, operator layer, and infrastructure layer. Each layer handles specific responsibilities independently, allowing automation to be implemented at the operator layer without propagating complexity to the interface layer, thus improving automation extent while containing device complexity within modular boundaries.

Inventive Principle:
Principle #1Segmentation

2Productivity

If command line tool interactions are integrated with operator/services, then productivity is improved, but reliability deteriorates due to inconsistencies

Engineering Contradiction:
Improvedelivery timeVSAvoidsystem consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The reconciliation loop implements continuous feedback by monitoring the actual state of cloud resources and comparing it against the desired state defined by commands. When inconsistencies are detected, the system automatically initiates corrective actions to restore consistency. This feedback mechanism ensures reliability is maintained even as productivity increases through automated command execution.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system dynamically adapts command execution based on the current state of resources. Rather than rigidly executing commands regardless of context, the operator framework dynamically determines the appropriate actions needed to achieve the desired state, ensuring consistency is maintained while enabling flexible and productive automation.

Inventive Principle:
Principle #15Dynamics

3Ease of operation

If external infrastructure is used to manage cloud resources, then ease of operation is improved, but device complexity increases and reliability decreases

Engineering Contradiction:
Improvecloud resource managementVSAvoidexternal infrastructure complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The operator framework enables self-service cloud resource management by allowing the system to automatically execute commands and manage resources without requiring external infrastructure or manual intervention. The reconciliation loop continuously monitors and self-corrects resource states, providing ease of operation while eliminating the need for complex external management systems.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20240176659A1Transparently executing actions within a containerized cloud environment
Publication Date: 2024.05.30 SAP SE
  • US20240176659A1 patent drawing
  • US20240176659A1 patent drawing
  • US20240176659A1 patent drawing

AI summary

In an example embodiment, a templating and detemplating component that allows for transparent integration with a cloud environment irrespective of the implementation is provided. It allows for two distinct ways of making changes in the cloud environment: (1) execution of commands through a command line tool; and (2) creation of custom resources by a user or system component.