Type-Based Resource Dependency Management in Clusterware

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Clusterware systems lack the ability to manage resource dependencies effectively, particularly in expressing dependencies between resources and resource types, leading to inflexible resource management and potential service availability issues.

Innovation Solution

The introduction of type-based resource dependencies, where resource profiles define attributes that specify dependencies on resource types rather than specific resources, allowing for flexible management and provisioning of resources based on types, enabling anonymous resource association and inheritance of default attributes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If clusterware systems use specific resource dependencies, then resource management is straightforward and deterministic, but the system lacks flexibility and scalability for dynamic resource provisioning

Engineering Contradiction:

Improveflexibility in resource managementVSAvoidcomplexity of dependency management

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces resource types as an intermediary layer between specific resources and applications. Instead of applications directly depending on specific resources, they depend on resource types, which then map to specific resource instances. This intermediary abstraction enables flexible resource management while maintaining manageable complexity through standardized type definitions and automated provisioning mechanisms.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If clusterware systems manage resources based on specific instances, then resource allocation is precise, but the system cannot easily reprovision or replace resources

Engineering Contradiction:

Improveservice availabilityVSAvoidautomatic reprovisioning capability

Core Design Contradiction:

ReliabilityVSExtent of automation

Solution Approach 1:

The patent makes resource types universal by defining them with standardized attributes and dependencies that can be satisfied by any resource instance of that type. This allows the system to automatically reprovision resources by finding alternative instances that match the required type specifications, thereby maintaining service availability while enabling automated resource replacement and scaling.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Manufacturing precision

If clusterware systems require custom code for resource management, then specific resource requirements can be met, but the system becomes difficult to maintain and scale

Engineering Contradiction:

Improveprecision in resource provisioningVSAvoidease of resource management

Core Design Contradiction:

Manufacturing precisionVSEase of manufacture

Solution Approach 1:

The patent transforms resource management from custom code-based to parameter-based configuration. Resource types are defined with configurable attributes and dependencies that can be adjusted without modifying code. This allows precise resource provisioning through parameter specification while maintaining ease of management through standardized, code-free configuration mechanisms.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS8438573B2Dependency on a resource type

Publication Date: 2013.05.07 ORACLE INT CORP

AI summary

A clusterware manager on a cluster of nodes interprets a resource profile. The resource profile defines resource profile attributes. The attributes include at least one attribute that defines a cluster dependency based on resource type. The attribute does not identify any particular resource of that resource type. Dependencies between resources are managed based on the attribute that specifies the cluster dependency.