Dispatch Node Policy Imports for Cloud Infrastructure

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The transition to cloud computing introduces challenges in evaluating policies due to the complexity of working with lower-level data primitives, leading to errors and confusion in cloud infrastructure provisioning.

Innovation Solution

A dispatch node receives a policy file and infrastructure plan data, parses the policy file to determine imports, queries the infrastructure plan data via an API for object data, and executes the policy file to obtain a policy check result, providing it to the cloud infrastructure provisioning platform, thereby simplifying the policy evaluation process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If policies are evaluated using lower-level data primitives from cloud infrastructure provisioning platforms, then the system can handle raw data directly, but the complexity of working with these data primitives causes errors and confusion in policy evaluation

Engineering Contradiction:
Improvepolicy evaluation complexityVSAvoidpolicy evaluation accuracy
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent introduces an intermediary layer between the cloud infrastructure provisioning platform and the policy evaluation system. This intermediary translates lower-level data primitives into higher-level abstractions that are easier to work with, thereby reducing evaluation complexity while maintaining accuracy. The intermediary acts as a mediator that converts raw data into a standardized format that policy files can process without errors.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If policies are designed to handle complex raw data files, then comprehensive policy evaluation is possible, but the policies become overly complex and difficult to manage

Engineering Contradiction:
Improvepolicy coverageVSAvoidpolicy structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the data processing into distinct layers: raw data from the cloud platform, translated data through the intermediary, and policy definitions at the highest abstraction level. This segmentation allows policies to focus on business logic rather than data formatting details, reducing policy structure complexity while maintaining comprehensive coverage through the intermediary's translation capabilities.

Inventive Principle:
Principle #1Segmentation

3Productivity

If the system works directly with lower-level data primitives, then data access is direct and efficient, but errors and confusion increase in policy evaluation

Engineering Contradiction:
Improvedata processing efficiencyVSAvoidpolicy evaluation reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The intermediary performs preliminary translation of data primitives into higher-level abstractions before the policy evaluation process begins. This preliminary action ensures that when policies execute, they are working with cleaned, standardized data that is both efficient to process and reliable for evaluation, preventing errors before they occur rather than handling them during execution.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11102280B1Infrastructure imports for an information technology platform
Publication Date: 2021.08.24 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11102280B1 patent drawing
  • US11102280B1 patent drawing
  • US11102280B1 patent drawing

AI summary

A method includes a dispatch node receiving a policy file and infrastructure plan data from a cloud infrastructure provisioning platform. The policy file comprises one or more imports that include a configuration import, a plan import, and/or a state import. Each import of the one or more imports comprises one or more data fields. The dispatch node parses the policy file to determine at least the one or more imports. The dispatch node queries the infrastructure plan data stored in a memory via an API for object data related to the one or more data fields of the one or more imports. The dispatch node determines, based on the query, the object data via the API. The dispatch node executes the policy file based on the object data to obtain a policy check result. The dispatch node then provides the policy check result to the cloud infrastructure provisioning platform.