Global Namespace Object Name Globalization for Multi-Tenant Storage

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Data replication in multi-tenant storage environments faces object name conflicts when upstream and downstream storage groups have objects with the same names, leading to replication halts and potential exposure of sensitive information.

Innovation Solution

Implementing a global namespace for object names in multi-tenant storage groups, where conflicting object names are globalized by adding unique identifiers, preventing conflicts without modifying existing object names, and de-globalizing names when communicating with non-globalized storage groups.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data replication is performed across storage groups with the same object names, then data redundancy and availability are improved, but object name conflicts occur causing replication to halt

Engineering Contradiction:

Improvedata availabilityVSAvoidobject name conflicts

Core Design Contradiction:

ReliabilityVSObject-generated harmful factors

Solution Approach 1:

The patent introduces a global namespace as an intermediary layer between storage groups. This global namespace acts as a mediator that resolves name conflicts by providing a unified naming space where object names from different storage groups are uniquely identified without direct conflicts, enabling seamless data replication across multi-tenant environments

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent transitions from local namespace management to a global namespace dimension. By elevating object name management to a global scope, the system can accommodate object names from multiple storage groups without conflicts, effectively adding a dimensional layer to name resolution that prevents replication halts

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

2Reliability

If object names are globalized by adding unique identifiers, then name conflicts are prevented, but object names become more complex and longer

Engineering Contradiction:

Improvename uniquenessVSAvoidobject name structure

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the object name into components: the original object name and a unique identifier suffix. This segmentation allows the system to maintain the original meaningful name while adding uniqueness through a separate identifier component, making the complexity manageable and systematic rather than chaotic

Inventive Principle:

Principle #1Segmentation

3Reliability

If a global namespace is implemented for all storage groups, then name conflicts are eliminated, but compatibility with non-globalized storage groups is reduced

Engineering Contradiction:

Improvename conflict resolutionVSAvoidstorage group compatibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements a dynamic naming approach where the system can adapt its behavior based on the storage group it is communicating with. When interacting with non-globalized storage groups, the system de-globalizes names to maintain compatibility, while using globalized names within its own globalized storage groups, thus maintaining versatility across different system types

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS10769172B2Globalized object names in a global namespace

Publication Date: 2020.09.08 HEWLETT PACKARD ENTERPRISE DEV LP

AI summary

Examples include globalized object names in a global namespace. Some examples may relate to creation of an object with a globalized object name in a global namespace based on a determination. The determination may relate to a global namespace name pattern or the determination may be based on globalization information.