Service Request Template Retrieval for Cloud Pod Scheduling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In cloud computing environments, there is a need to optimize the management of pooled and configurable computing resources to efficiently allocate and schedule workloads across computing racks, ensuring efficient resource utilization and optimal service delivery while managing operational costs.

Innovation Solution

A computer system with a pod manager that provides an interface for orchestrating and managing computing resources, allowing for the allocation and scheduling of resources across computing racks, using service request templates to construct and execute actions on computing pods, and enabling the composition of nodes from pooled compute, memory, and network resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If service request templates are stored and reused for constructing service requests, then productivity is improved by reducing redundant operations, but device complexity increases due to template management infrastructure

Engineering Contradiction:
Improveservice request construction efficiencyVSAvoidtemplate management system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

Service request templates are prepared and stored in advance in a data store, containing pre-defined structures for common service requests. When a service request is needed, the system retrieves the appropriate template and populates it with specific parameters, avoiding the need to construct the entire service request from scratch each time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates and stores copies of service request templates that can be reused multiple times. Instead of recreating the same service request structure repeatedly, the system retrieves stored template copies and modifies them with different parameter values to generate new service requests.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If computing resources are pooled and allocated dynamically, then adaptability is improved for managing heterogeneous resources, but loss of information increases due to payload modifications during allocation

Engineering Contradiction:
Improveresource allocation flexibilityVSAvoidservice request payload integrity
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The system extracts the payload portion of service requests and separates it from the request structure. Templates store only the essential structure and metadata, while payloads are retrieved and populated separately, ensuring that critical information is preserved and not lost during template instantiation.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system introduces an intermediary payload retrieval mechanism that acts as a buffer between template instantiation and service request execution. Payloads are stored separately in the data store and retrieved during the service request construction process, ensuring information integrity while allowing flexible resource allocation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10506028B2Techniques of preserving service request payloads
Publication Date: 2019.12.10 AMERICAN MEGATRENDS
  • US10506028B2 patent drawing
  • US10506028B2 patent drawing
  • US10506028B2 patent drawing

AI summary

In an aspect of the disclosure, a method, a computer-readable medium, and a computer system are provided. A first device of the computer system provides a service interface for retrieving stored service request templates for executing actions on a computing pod. The first device receives, at the service interface, a template request for a service request template for constructing a reused service request, the reused service request requesting the computing pod to execute a first action. The first device retrieves the service request template from a data store in accordance with information provided by the template request. The first device sends the service request template in a response to the template request.