Resiliency Graph for Cloud Infrastructure K-Redundancy

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud computing systems face challenges in applying traditional high availability architectures due to their on-demand scalability and flexibility, which complicates the implementation of resilient solutions.

Innovation Solution

The method involves creating a resiliency graph by modifying a network topology graph, translating Service Level Agreements (SLAs) into the graph, and identifying overlaps and dependencies to optimize infrastructure sharing for high availability, using techniques like 1:K replication and K-redundancy to ensure critical system resilience.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional high availability architectures are applied to cloud computing systems, then system reliability is improved, but device complexity and adaptability deteriorate due to the rigid structure conflicting with on-demand scalability and flexibility requirements

Engineering Contradiction:
Improvesystem reliabilityVSAvoidadaptability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent applies dynamics by creating a resiliency graph that dynamically adapts to changing cloud infrastructure configurations. The system continuously monitors topology changes, process flows, and SLA requirements, automatically updating the resiliency graph to maintain optimal high availability configurations without rigid pre-definition, thus resolving the conflict between reliability and adaptability

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes parameters by translating SLA requirements into quantifiable metrics within the resiliency graph. By converting qualitative service level agreements into measurable parameters (such as failure thresholds, recovery time objectives), the system can dynamically adjust resiliency configurations based on changing business requirements while maintaining reliability

Inventive Principle:
Principle #35Parameter changes

2Productivity

If infrastructure resources are shared to optimize cloud computing efficiency, then productivity is improved, but reliability deteriorates due to increased points of failure and dependencies

Engineering Contradiction:
Improveinfrastructure sharing efficiencyVSAvoidsystem reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies segmentation by dividing the shared infrastructure into distinct process flows and mapping them onto the topology graph. By identifying and separating critical process dependencies, the system can apply targeted resiliency measures to specific segments while maintaining efficient resource sharing across non-critical components, thus preserving both productivity and reliability

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements beforehand cushioning by proactively identifying overlaps and dependencies in the resiliency graph before failures occur. The system pre-configures backup paths and redundancy mechanisms for critical process flows, ensuring that when resource sharing creates potential failure points, compensatory measures are already in place to maintain reliability

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

3Reliability

If comprehensive resiliency monitoring and graph modification are implemented, then reliability is improved, but device complexity and computational overhead increase

Engineering Contradiction:
Improvecloud system resiliencyVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces the resiliency graph as an intermediary layer between the physical cloud infrastructure and the management system. This graph abstracts complex topology relationships, process flows, and SLA requirements into a unified representation, simplifying the computational task of analyzing resiliency while maintaining comprehensive monitoring capabilities

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a virtual copy of the cloud infrastructure topology in the form of the resiliency graph. By maintaining this graphical model that mirrors the physical system, the patent enables complex resiliency analysis and optimization without directly complicating the physical infrastructure, as all monitoring and control operations occur on the simplified graphical representation

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9077613B2System and method for graph based K-redundant resiliency for IT cloud
Publication Date: 2015.07.07 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US9077613B2 patent drawing
  • US9077613B2 patent drawing
  • US9077613B2 patent drawing

AI summary

A method for enabling resiliency for cloud computing systems is described. The method includes modifying a topology graph of a network architecture by mapping processes flows onto the topology graph. A resiliency graph is created based on the modified topology graph. The method includes modifying the resiliency graph by translating at least one SLA into the resiliency graph. Overlaps and dependencies in the modified resiliency graph are identified. Apparatus and computer readable instructions are also described.