Cloud Network Configuration via Template Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The manual and time-consuming process of setting up and managing complex cloud networks, such as CLOS networks, is challenging due to the need for individual configuration and provisioning of numerous devices, which becomes increasingly difficult as the size and scale of the network grow, especially when dealing with devices from different vendors.

Innovation Solution

A method and system for automating network configuration and management through a centralized approach, using a network model that encapsulates network topology, components, and characteristics, allowing for the automatic creation and configuration of devices, independent of vendor-specific configurations, by generating configuration files via iterative selection and application of templates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If manual configuration and provisioning is used for each device, then configuration accuracy can be maintained, but the process becomes increasingly time-consuming and difficult as network size grows

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidsetup time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent uses templates to create standardized configuration patterns that can be copied and applied across multiple devices. These templates encapsulate best practices and standardized settings, allowing rapid deployment while maintaining consistency and accuracy across the network infrastructure.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The configuration process is segmented into reusable template components that can be independently developed, validated, and applied. This segmentation allows the system to handle large networks by breaking down complex configurations into manageable, pre-validated units that can be systematically applied to multiple devices.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If individual device configuration is performed manually, then vendor-specific requirements can be addressed, but device complexity and management difficulty increase with network scale

Engineering Contradiction:
Improvevendor compatibilityVSAvoidmanagement complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal template system that can accommodate multiple vendor-specific device types through a common framework. The templates are designed to be vendor-agnostic at the structural level while incorporating vendor-specific parameters and configurations, allowing the same management system to handle diverse equipment from different manufacturers.

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

Solution Approach 2:

The system applies local quality by allowing vendor-specific configurations to be embedded within standardized template structures. Each template can contain vendor-specific parameters, protocols, and settings tailored to particular device types while maintaining overall configuration consistency through the universal template framework.

Inventive Principle:
Principle #3Local quality

3Reliability

If comprehensive configuration validation is performed manually, then configuration reliability can be ensured, but the process becomes increasingly time-consuming with network growth

Engineering Contradiction:
Improveconfiguration reliabilityVSAvoiddeployment speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent incorporates validation rules and checks within the template definitions themselves, performing configuration validation in advance during template creation and deployment. This preliminary validation ensures configuration reliability is built-in from the start rather than requiring time-consuming manual verification after deployment.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system performs automated self-validation of configurations through embedded validation logic in the templates. The configuration management system automatically checks for consistency, completeness, and correctness of generated configurations without requiring manual verification, thereby maintaining reliability while enabling rapid deployment.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20240015071A1Method and apparatus for holistic rendering of cloud network configuration
Publication Date: 2024.01.11 ORACLE INT CORP
  • US20240015071A1 patent drawing
  • US20240015071A1 patent drawing
  • US20240015071A1 patent drawing

AI summary

The present is directed to systems, methods, and devices for holistic rendering of cloud network configuration. The method can include receiving data characterizing a plurality of devices in a computing network. The method can include generating with the inventory processor a data file characterizing each of the plurality of devices in the computing network. This data file can be generated based on the received data and on a set of static overrides. The method can include generating a configuration file for each of the plurality of devices in the computing network via iterative selection and application of templates to portions of the data file.