Cloud Infrastructure Orchestration Rollback for Configuration Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cloud infrastructure orchestration services face challenges in efficiently managing infrastructure provisioning and deployment, particularly in large-scale environments, with manual interventions leading to deviations and a lack of automated tools that can handle both provisioning and deployment seamlessly, and existing tools lack the ability to automatically handle rollback operations due to the absence of tracking previous configurations.

Innovation Solution

A cloud infrastructure orchestration service (CIOS) that automates both provisioning and deployment using a declarative approach, maintaining a history of configurations and variable inputs to enable automatic rollback to a previous state in case of failures, thereby reducing manual errors and ensuring robustness.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If automated rollback operations are implemented, then system reliability is improved, but device complexity increases due to the need for configuration history tracking

Engineering Contradiction:
Improverollback reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by capturing and storing configuration states before infrastructure changes are applied. This allows the rollback mechanism to restore to known good states without requiring complex real-time analysis during failure scenarios.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates copies of configuration states at different points in time, storing them in a history database. These copies enable the rollback operation to restore previous configurations without needing to maintain the original state, simplifying the rollback mechanism.

Inventive Principle:
Principle #26Copying

2Ease of operation

If manual intervention is used for infrastructure provisioning, then ease of operation is reduced, but automation extent is limited

Engineering Contradiction:
Improveprovisioning easeVSAvoidautomation extent
Core Design Contradiction:
Ease of operationVSExtent of automation

Solution Approach 1:

The system enables self-service by automatically capturing configuration states, detecting failures, and executing rollback operations without requiring manual intervention. The infrastructure orchestration service autonomously manages the entire lifecycle including provisioning, monitoring, and recovery.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring infrastructure health and comparing actual states against desired states. When deviations are detected, the system automatically triggers rollback operations to restore compliance, creating a closed-loop control system.

Inventive Principle:
Principle #23Feedback

3Loss of information

If configuration history is tracked for rollback, then loss of information is reduced, but device complexity increases

Engineering Contradiction:
Improveconfiguration information lossVSAvoidtracking complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system performs preliminary capture of configuration states before changes are applied, storing them in a structured format in a database. This preliminary action ensures that configuration information is preserved in an organized manner that simplifies later retrieval and restoration operations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12449959B2Techniques for implementing rollback of infrastructure changes in a cloud infrastructure orchestration service
Publication Date: 2025.10.21 ORACLE INT CORP
  • US12449959B2 patent drawing
  • US12449959B2 patent drawing
  • US12449959B2 patent drawing

AI summary

Techniques for implementing rollback of infrastructure changes in an infrastructure orchestration service are described. In certain examples, an infrastructure orchestration service is disclosed that manages both provisioning and deploying of infrastructure assets within a cloud environment. The service receives a plan comprising a set of instructions associated with a set of infrastructure assets of an execution target and identifies a first state of the set of infrastructure assets. The service executes the set of instructions in the plan to achieve a second state for the set of infrastructure assets. Based in part on the executing, the service receives a trigger for rolling back the plan to restore the set of infrastructure assets in the plan to the first state and executes a rollback plan for the plan. The service then transmits a result associated with the execution of the rollback plan.