Network Data Volume Parameter Modification via Provisioning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In environments where multiple users share network-hosted resources, modifying operational parameters such as storage capacity, throughput, or bandwidth can lead to increased complexity and latency due to the need for additional data volumes, which complicates user application logic and request processing.
Innovation Solution
A data center system that allows users to modify operational parameters by provisioning a new data volume that meets the requested specifications, where the new volume handles read and write requests while the old volume migrates data to it, eventually deallocating resources for the old volume.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If additional data volumes are provisioned to meet user storage needs, then storage capacity is increased, but device complexity and latency increase
Solution Approach 1:
The system creates a copy of the volume manifest file from the first data volume to the second data volume, allowing the second volume to serve as a functional duplicate for meeting storage needs without requiring complex additional infrastructure. The copy operation preserves the manifest structure and data organization, enabling the new volume to immediately assume the role of the original volume.
Solution Approach 2:
After successfully copying the volume manifest file and establishing the second data volume as a functional replacement, the system deallocates the first data volume, recovering its resources for reuse. This process eliminates the need to maintain multiple complex volume structures simultaneously, reducing device complexity while maintaining increased storage capacity.
2Quantity of substance
If additional data volumes are provisioned to meet user storage needs, then storage capacity is increased, but request processing latency increases
Solution Approach 1:
The system performs preliminary actions by copying the volume manifest file to the second data volume before deallocating the first volume. This ensures that the second volume is fully prepared and ready to immediately handle read and write requests, eliminating any latency that would result from incremental data migration or post-provisioning configuration.
Solution Approach 2:
By copying the entire volume manifest file structure to the second data volume, the system creates an immediately functional storage volume that can handle requests without delay. The copy operation preserves all necessary metadata and organization structures, allowing the new volume to assume full operational responsibility instantly.
3Productivity
If data is migrated from old volume to new volume, then resource allocation efficiency is improved, but data transfer time is required
Solution Approach 1:
The system uses a copy operation rather than incremental migration to transfer data between volumes. The volume manifest file is copied in its entirety to the second data volume, which then becomes immediately functional. This approach eliminates prolonged data transfer times while achieving complete resource reallocation, as the copy operation is performed once and the new volume is ready for immediate use.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A user can set or modify operational parameters of a data volume stored on a network-accessible storage device in a data center. For example, the user may be provided access to a data volume and may request a modification to the operational parameters of the data volume. Instead of modifying the existing data volume, the data center can provision a new data volume and migrate data stored on the existing data volume to the new data volume. While the data migration takes place, the existing data volume may block input/output (I/O) requests and the new data volume may handle such requests instead. Once the data migration is complete, the data center may deallocate the data blocks of the existing data volume such that the data blocks can be reused by other data volumes. If a request is received for data not yet migrated to the new data volume, then the new data volume prioritizes a migration of the requested data.