Dynamic Cloud Storage Deployment via Availability Zone Routability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional approaches to deploying cloud-based storage systems are impractical in large hybrid environments, particularly when networking and security are managed by separate teams, as they require manual selection of infrastructure components and assume the creation of a new infrastructure from scratch, leading to reliability issues and developer unfriendliness.

Innovation Solution

A method that determines the routability of availability zones to an on-premises network and processes deployment intent to dynamically deploy cloud-based storage systems, using sorted subnets and intents for resource configuration, including minimum resource deployment, IO optimization, data mobility, and data mobility between cloud and on-premises networks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If conventional approaches provision brand-new cloud infrastructure environment from scratch, then infrastructure can be created, but deployment reliability deteriorates due to manual selection errors and infrastructure incompatibility

Engineering Contradiction:
Improveinfrastructure creationVSAvoiddeployment reliability
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The system performs preliminary actions by automatically discovering and validating cloud infrastructure components (subnets, availability zones, VPCs) before deployment. The deployment manager proactively checks routability to on-premises networks and validates capacity requirements, preventing deployment failures before they occur.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The deployment manager acts as an intermediary between the developer's high-level intent and the complex cloud infrastructure details. It translates abstract deployment requirements into concrete infrastructure selections, shielding developers from low-level complexity while ensuring reliable deployment through automated validation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If manual selection of cloud infrastructure components is used, then developer control is maintained, but deployment complexity increases and errors occur

Engineering Contradiction:
Improvedeveloper controlVSAvoiddeployment complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system enables self-service by allowing developers to specify high-level deployment intent (e.g., storage capacity, performance requirements) without manually selecting infrastructure components. The deployment manager autonomously handles component selection, validation, and provisioning based on the developer's intent.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The deployment manager provides universal functionality by handling multiple aspects of deployment (infrastructure discovery, validation, selection, provisioning) through a single interface. Developers interact with one system that manages the entire deployment lifecycle, reducing operational complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If all low-level details of cloud infrastructure are exposed to developer workflow, then complete control is available, but workflow complexity proliferates and developer friendliness decreases

Engineering Contradiction:
Improvedeveloper controlVSAvoiddeveloper friendliness
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system extracts low-level infrastructure details from the developer's workflow. The deployment manager handles subnet selection, availability zone choice, and capacity validation, removing these complex details from the developer's direct control while preserving high-level adaptability through intent-based specifications.

Inventive Principle:
Principle #2Taking out (Extraction)

4Productivity

If conventional deployment approaches are used in hybrid environments with separate networking and security teams, then infrastructure can be provisioned, but impracticality increases due to coordination overhead

Engineering Contradiction:
Improveinfrastructure provisioningVSAvoiddeployment practicality
Core Design Contradiction:
ProductivityVSEase of manufacture

Solution Approach 1:

The system merges the roles of networking and security validation into the automated deployment process. The deployment manager simultaneously checks network routability and security group configurations, eliminating the need for separate coordination steps with networking and security teams.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS12147687B2System and method for dynamic cloud-based storage system deployment
Publication Date: 2024.11.19 DELL PROD LP
  • US12147687B2 patent drawing
  • US12147687B2 patent drawing
  • US12147687B2 patent drawing

AI summary

A method, computer program product, and computing system for determining whether an availability zone of a plurality of availability zones is routable to an on-premises network. An intent associated with the deployment of a cloud-based storage system is processed. The cloud-based storage system is deployed in the availability zone based upon, at least in part, whether the availability zone is routable to an on-premises network and the intent associated with the deployment of the cloud-based storage system.