Inline Policy Management via Multi-Level Object Handle
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional network storage systems face inefficiencies due to hierarchical data organization, which leads to duplication of content and administrative overhead, and lack the ability to seamlessly manage data policies across different storage tiers, making it cumbersome to apply policies to collections of data objects.
Innovation Solution
A distributed object store in a network storage server system that uses system-generated, location-independent global object identifiers for data objects, allowing seamless migration and embedding policy information within the object handle for inline policy management, along with an object location subsystem to manage location changes, enabling transparent migration and efficient policy application.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If path names are used to organize data in a hierarchical structure, then navigation and retrieval are enabled, but data duplication and administrative overhead increase
Solution Approach 1:
The patent segments the data organization into two independent parts: a hierarchical namespace for navigation purposes and a flat object store for actual data storage. This segmentation allows the namespace to provide structured access paths while the object store eliminates duplication by storing each object once with a unique identifier, resolving the contradiction between navigability and data redundancy.
Solution Approach 2:
The patent introduces an intermediary layer (the namespace) that sits between the user and the actual data objects. This namespace provides hierarchical path names for navigation without requiring the underlying data to be organized hierarchically, allowing efficient retrieval while preventing data duplication in the storage layer.
2Ease of operation
If path names are tied to storage location, then data access is straightforward, but transparent migration of data objects becomes difficult
Solution Approach 1:
The patent introduces an intermediary mapping layer that decouples path names from physical storage locations. The namespace maintains path-to-object mappings while the object store uses location-independent identifiers. This intermediary structure enables straightforward data access through familiar path names while simultaneously allowing transparent migration, as objects can be moved without changing their namespace entries or affecting client access.
Solution Approach 2:
The patent adds an additional dimension to data access by introducing a two-level indirection: clients access data through hierarchical path names in the namespace, which map to location-independent object identifiers in the object store. This dimensional separation allows path names to remain stable while physical locations change, enabling transparent migration without affecting data access.
3Reliability
If policies are managed out-of-band by system administrators, then policy application is possible, but the process becomes cumbersome and less efficient
Solution Approach 1:
The patent enables self-service policy management by embedding policy information directly within object metadata and enabling automated policy evaluation and enforcement by the storage system. Objects carry their own policy identifiers, allowing the system to automatically apply appropriate policies without requiring manual administrator intervention for each policy decision, thereby simplifying the process while maintaining reliable policy application.
Solution Approach 2:
The patent implements preliminary action by associating policy identifiers with objects at the time of object creation or import. This advance association of policy information with objects allows the system to automatically enforce policies later without requiring real-time administrator intervention, making the policy management process more efficient while ensuring consistent and reliable policy application.
4Ease of operation
If hierarchical organization is used for data storage, then navigation is enabled, but it leads to inefficiencies in data management
Solution Approach 1:
The patent segments navigation functionality from data storage by implementing a separate namespace layer that provides hierarchical organization for navigation purposes, while the underlying object store maintains a flat, efficient structure for data management. This segmentation allows the system to provide intuitive navigation through path names while eliminating the inefficiencies of hierarchical storage, such as data duplication and complex management operations.
Data Source
AI summary
A distributed object store in a network storage system uses location-independent global object identifiers (IDs) for stored data objects. The global object ID enables a data object to be seamlessly moved from one location to another without affecting clients of the storage system, i.e., “transparent migration”. The global object ID can be part of a multilevel object handle, which also can include a location ID indicating the specific location at which the data object is stored, and a policy ID identifying a set of data management policies associated with the data object. The policy ID may be associated with the data object by a client of the storage system, for example when the client creates the object, thus allowing “inline” policy management. An object location subsystem (OLS) can be used to locate an object when a client request does not contain a valid location ID for the object.