CaaS Controller Bare Metal Selection Policy

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Private cloud environments face challenges in managing container clusters due to limited machine inventories and resource diversity, requiring a more nuanced approach than public clouds, which often have virtually infinite resources. This necessitates a system that can efficiently select and manage bare metal machines based on various constraints such as cost, performance, and security for cluster creation and autoscaling.

Innovation Solution

A managed container service controller that leverages a CaaS portal to receive cluster information and utilizes BMaaS, VMaaS, and STaaS controllers to manage resource inventory and deployment decisions, employing policy-based constraints and best-fit algorithms to select suitable bare metal machines for cluster creation and management, even in hybrid environments spanning public and private clouds.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a best-fit algorithm is used to select bare metal machines based on policy constraints, then resource utilization efficiency is improved, but system complexity increases

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system segments the cluster creation process into distinct phases: receiving cluster information, evaluating policy constraints, calculating excess resource metrics, and selecting bare metal machines. This segmentation allows the best-fit algorithm to be applied in a controlled manner without overwhelming system complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary evaluation of policy constraints and machine inventory before cluster creation. By pre-calculating excess resource metrics and establishing policy-based selection criteria in advance, the system reduces complexity during the actual cluster deployment while maintaining high resource utilization efficiency.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If policy-based constraints are applied for machine selection, then resource allocation optimization is improved, but processing time increases

Engineering Contradiction:
Improveresource allocation optimizationVSAvoidprocessing time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system pre-establishes policy constraints and evaluates the machine inventory against these policies before cluster creation requests are processed. By performing this preliminary filtering and metric calculation in advance, the system optimizes resource allocation while minimizing the processing time required during actual cluster deployment.

Inventive Principle:
Principle #10Preliminary action

3Manufacturing precision

If comprehensive inventory evaluation is performed for each cluster request, then cluster creation accuracy is improved, but computational overhead increases

Engineering Contradiction:
Improvecluster creation accuracyVSAvoidcomputational overhead
Core Design Contradiction:
Manufacturing precisionVSPower

Solution Approach 1:

The system applies different evaluation depths to different aspects of machine selection. For policy constraint evaluation, comprehensive checks are performed to ensure accuracy. For excess resource metric calculation, the system uses optimized algorithms that provide sufficient precision without exhaustive computation, thereby reducing overall computational overhead while maintaining cluster creation accuracy.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12001865B2Container-as-a-service (CAAS) controller for private cloud container cluster management
Publication Date: 2024.06.04 HEWLETT PACKARD ENTERPRISE DEV LP
  • US12001865B2 patent drawing
  • US12001865B2 patent drawing
  • US12001865B2 patent drawing

AI summary

Embodiments described herein are generally directed to a controller of a managed container service that facilitates selection among bare metal machines available within a private cloud. According to an example, a request is received by a Container-as-a-Service controller from a CaaS portal to create a cluster based at least in part on resources of a private cloud of a customer of a managed container service. An inventory of bare-metal machines available within the private cloud is received from a Bare-Metal-as-a-Service (BMaaS) provider associated with the private cloud. A particular bare metal machine is identified for the cluster by selecting among the available bare-metal machines based on cluster information associated with the request, the inventory, and a best fit algorithm configured in accordance with a policy established by the customer.