Dual File-System Naming for VM Cloning and Namespace Isolation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing virtualized computing systems face challenges in efficiently managing file systems for Virtual Machines (VMs) due to namespace pollution and inefficient cloning processes, particularly in distributed environments where VMs have limited awareness of global file system identifiers, leading to security and management complexities.

Innovation Solution

Implementing a dual naming scheme with global and client-specific identifiers for file systems, coupled with a shadow virtual disk mechanism, to manage and clone VMs efficiently, ensuring unique global IDs across the system and client-specific names within subsets, while maintaining separate views of storage structures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If global identifiers are used for all file systems in a distributed environment, then unique identification across the system is achieved, but namespace pollution and security complexities increase

Engineering Contradiction:
Improveunique identificationVSAvoidnamespace management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent divides the identifier system into two segments: global identifiers (UUIDs) that are unique across the entire distributed system, and client-specific names that are local to each client's namespace. This segmentation allows each identifier type to serve its specific purpose without the drawbacks of using a single identifier system for both global uniqueness and local accessibility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements local quality by allowing each client to have its own namespace with client-specific names that are meaningful and accessible only to that client. Meanwhile, the global identifier maintains uniqueness system-wide. This enables local optimization for ease of use while maintaining global optimization for uniqueness.

Inventive Principle:
Principle #3Local quality

2Productivity

If VMs are cloned in distributed file system environments, then rapid deployment is achieved, but file system management becomes complex due to namespace pollution

Engineering Contradiction:
Improvecloning speedVSAvoidfile system management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent enables efficient VM cloning by copying the virtual disk files associated with the file systems. When a VM is cloned, the file system metadata is copied along with the virtual disk, allowing the cloned VM to inherit the file system structure. The global identifier is updated to reflect the new VM, while client-specific names remain consistent, enabling rapid deployment without complex file system management.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If multiple clients access the same file system with different names, then flexibility is improved, but security and namespace management become problematic

Engineering Contradiction:
Improveclient-specific naming flexibilityVSAvoidnamespace security
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent adds another dimension to the naming system by introducing a client-specific namespace layer over the global identifier. Instead of having a single flat namespace, the system creates a hierarchical view where each client sees file systems through its own namespace with client-specific names, while the underlying global identifier ensures unique identification and proper access control across all clients.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS12536134B2File systems with global and local naming
Publication Date: 2026.01.27 GOOGLE LLC
  • US12536134B2 patent drawing
  • US12536134B2 patent drawing

AI summary

A method for data storage includes specifying a plurality of File Systems (FSs) for use by multiple clients, including assigning to the FSs both respective global identifiers and respective client-specific names. The plurality of FSs is managed using the global identifiers, and files are stored for the clients in the FSs using the client-specific names.