Hierarchical Dynamic Templates for Virtualized Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for creating, deploying, and managing templates for cloud-based virtualized systems are inefficient, leading to increased storage needs, manual updates, and difficulties in handling multi-tenant environments, which result in minimal reuse of templates and significant administrative effort.

Innovation Solution

The implementation of dynamic templates with a hierarchical structure that allows for selective deployment, updating, and management of virtualized systems, using Role-Based Access Control (RBAC) for user authentication and incremental fingerprinting to track changes, enabling efficient cloning, migration, and rollback capabilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional complete templates are used to ensure all products and tenants are supported, then system completeness is improved, but storage space requirements increase and template reuse decreases

Engineering Contradiction:
Improvesystem completenessVSAvoidstorage space
Core Design Contradiction:
ReliabilityVSVolume of stationary object

Solution Approach 1:

The patent segments a complete template into a hierarchical structure with a base template containing common configurations and multiple product-specific templates containing product-specific configurations. This segmentation allows the base template to be reused across multiple products while only product-specific portions need to be replicated, significantly reducing storage requirements while maintaining system completeness.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a nested template structure where product-specific templates are nested within the base template hierarchy. The base template serves as the parent containing shared configurations, and product templates are children that inherit from the base. This nesting allows automatic inheritance of common configurations while storing only differential product-specific configurations, reducing overall storage needs.

Inventive Principle:
Principle #7Nested doll (Nesting)

2Reliability

If conventional complete templates are used to ensure all products and tenants are supported, then system completeness is improved, but administrative effort increases

Engineering Contradiction:
Improvesystem completenessVSAvoidadministrative effort
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

By segmenting templates into base and product-specific components, administrators can update the base template once to propagate changes across all products automatically, rather than manually updating each complete template individually. This segmentation dramatically reduces administrative effort while ensuring all products remain complete and consistent.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The base template serves as a universal template that can be reused across multiple products and tenants. This multi-functionality allows a single base template to support numerous products, reducing the total number of templates administrators must manage and update, thereby reducing time loss.

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

3Reliability

If conventional templates are updated to fix security vulnerabilities or update configurations, then system security is improved, but template update complexity increases

Engineering Contradiction:
Improvesystem securityVSAvoidtemplate update complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The hierarchical template structure segments security-related configurations into the base template, allowing security updates to be applied once at the base level and automatically inherited by all product templates. This segmentation simplifies the update process compared to manually updating each complete template while maintaining security across all products.

Inventive Principle:
Principle #1Segmentation

4Reliability

If conventional templates are used in multi-tenant environments, then tenant isolation is improved, but template reuse decreases

Engineering Contradiction:
Improvetenant isolationVSAvoidtemplate reuse
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent applies local quality by allowing tenant-specific customizations at the product template level while maintaining common configurations at the base template level. Each tenant can have localized modifications specific to their needs while inheriting the standardized base configuration, ensuring both tenant isolation and template reuse.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10089097B2Dynamic templates for virtualized systems
Publication Date: 2018.10.02 EXTREME NETWORKS INC
  • US10089097B2 patent drawing
  • US10089097B2 patent drawing
  • US10089097B2 patent drawing

AI summary

Methods, systems and computer readable media for dynamic templates for virtualized systems are described. A method for initially deploying a virtualized can include receiving a selection indicating a dynamic template, and installing a base configuration using base configuration information obtained from the dynamic template. The method can also include traversing a hierarchy within the dynamic template and installing one or more sub-level configurations according to the hierarchy. The method can further include stopping the traversing and installing when a termination condition is reached.