Local Resource Type Model for Clusterware Node Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing clusterware technologies face challenges in efficiently managing resources and adding or removing nodes from a cluster due to varying resource configurations across nodes, which complicates modular incremental system growth and node management.

Innovation Solution

The introduction of a Local Resource type model within clusterware, which allows for the storage of a single local resource profile that can be used to configure resources across all nodes, enabling automatic configuration and management of resources during node addition or removal, including the use of override profiles stored on each server for unique settings.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If traditional resource management approaches are used in clusterware, then resource configuration can be manually controlled, but the complexity of managing resources increases when nodes are added or removed, especially with varying resource configurations across nodes

Engineering Contradiction:
ImproveNode addition and removal operationVSAvoidResource configuration management complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent uses resource profiles as templates that can be copied and applied to multiple nodes. When a node is added to the cluster, the system automatically copies the appropriate resource profile to configure resources on the new node, eliminating manual configuration complexity while maintaining consistency across nodes.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent segments resource configuration into separate resource profiles that can be independently defined and applied. Each resource type has its own profile that can be selectively applied to nodes, allowing flexible configuration management without increasing overall system complexity.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If resource profiles are stored on each server for unique settings, then flexibility for unique node configurations is achieved, but the complexity of managing and synchronizing these profiles increases

Engineering Contradiction:
ImproveUnique node configuration flexibilityVSAvoidProfile storage and synchronization complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements local quality by allowing each server to store its own override profiles for unique configurations while using a centralized resource profile for standard settings. This enables nodes to have customized local configurations without requiring synchronization of entire configuration sets, reducing management complexity while maintaining flexibility.

Inventive Principle:
Principle #3Local quality

3Manufacturing precision

If manual resource configuration is performed during node addition, then precise control over resource settings is achieved, but the time required for node addition and removal increases

Engineering Contradiction:
ImproveResource configuration precisionVSAvoidNode addition and removal time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent prepares resource profiles in advance with all necessary configuration settings defined before nodes are added to the cluster. When a node is added, the system automatically applies the pre-defined profile, eliminating the need for manual configuration during node addition while ensuring precise resource settings are applied consistently.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8949425B2“Local resource” type as a way to automate management of infrastructure resources in oracle clusterware
Publication Date: 2015.02.03 ORACLE INT CORP
  • US8949425B2 patent drawing
  • US8949425B2 patent drawing
  • US8949425B2 patent drawing

AI summary

A method and computer-readable storage representing resources in a cluster by a plurality of attribute-value pairs that together are part of a “resource profile,” in which each attribute-value pair defines all, or a portion of, a management policy that applies to the resource. Included is a built-in resource type called a “Local Resource” type. Local resources that are attached to the server are instantiated with a combination of the resource profile and values of the Local Resource type.