Critical Path Resource UI for Data Center Bootstrapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional tools for building data centers in cloud infrastructure require significant manual effort, are time-consuming, error-prone, and do not scale well, leading to increased build time and resource waste.

Innovation Solution

A Cloud Infrastructure Orchestration Service (CIOS) that utilizes predefined configuration files to identify dependencies, optimize parallel processing, and manage the order of service bootstrapping, using a virtual bootstrap environment (ViBE) to reduce manual intervention and eliminate circular dependencies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual bootstrapping operations are used for each service, then service provisioning can be performed, but build time increases and errors occur

Engineering Contradiction:
Improveservice provisioning accuracyVSAvoiddata center build time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system implements self-service through automated dependency resolution where the orchestration service automatically identifies and provisions required services in the correct sequence without manual intervention. The system self-manages the complex coordination of multiple services by automatically detecting dependencies and executing bootstrapping operations in the optimal order, eliminating manual effort while maintaining high reliability.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary action by pre-defining service dependencies and bootstrapping sequences in configuration files before actual deployment. The orchestration service analyzes these predefined dependencies ahead of time to generate an optimized execution plan, allowing services to be bootstrapped in parallel where possible while ensuring correct sequencing, thus reducing overall build time without sacrificing reliability.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If manual bootstrapping operations are used for each service, then service provisioning can be performed, but resource waste increases

Engineering Contradiction:
Improveservice provisioning accuracyVSAvoidcomputing resource waste
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The orchestration service automatically monitors service provisioning status and dynamically adjusts resource allocation based on actual needs. It detects when services are successfully provisioned and stops allocating additional resources, preventing waste. The system also identifies and eliminates redundant operations by analyzing the service dependency graph, ensuring each resource is used only when necessary for meeting provisioning requirements.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements dynamic resource management by continuously adapting resource allocation based on real-time provisioning status. The orchestration service can pause and resume bootstrapping operations, adjust parallel execution levels, and reallocate resources dynamically as services become available, optimizing resource utilization while maintaining reliable service provisioning throughout the build process.

Inventive Principle:
Principle #15Dynamics

3Productivity

If service dependencies are not properly managed, then bootstrapping can proceed, but circular dependencies cause failures

Engineering Contradiction:
Improvebootstrapping speedVSAvoidbootstrapping success rate
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary dependency analysis by parsing service configuration files before bootstrapping begins. The orchestration service builds a complete dependency graph and detects circular dependencies in advance, preventing bootstrapping failures before they occur. This upfront analysis allows the system to generate a valid execution plan that guarantees acyclic service provisioning sequences, maintaining both speed and reliability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring service provisioning status and comparing actual progress against the planned sequence. The orchestration service detects deviations from the expected progression and can intervene to correct issues, ensuring that circular dependencies are identified and resolved. This feedback loop maintains bootstrapping success rate while preserving optimal speed through automated correction rather than complete failure.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20260064431A1User interface for critical path resources
Publication Date: 2026.03.05 ORACLE INT CORP
  • US20260064431A1 patent drawing
  • US20260064431A1 patent drawing
  • US20260064431A1 patent drawing

AI summary

The present embodiments relate to determining a critical path that identifies an order for bootstrapping a subset of resources within a data center under build. A cloud infrastructure orchestration service (CIOS) can identify from configuration files associated with resources to be bootstrapped within the data set, a set of capabilities. The CIOS can identify a first set of capabilities on which publishing each respective capability depends. User input can be received identifying a selected flock. The CIOS can identify the unpublished capabilities on which capabilities corresponding to the selected flock depend. Those unpublished capabilities can be ranked and provided via a visualization to the user. The unpublished capabilities can be ranked according to identifying, for a respective unpublished capability, a set of capabilities that are capable of being published responsive to publishing the respective unpublished capability.