Landing Area Device Pre-allocation for Computing Resource Availability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Computing resources are not instantly available to clients upon request, leading to a temporary gap where data generated by landing area devices must be stored and later transferred to deployed physical assets, causing inefficiencies and potential latency.
Innovation Solution
A method involving a resource use manager that allocates landing area devices, determines necessary physical assets using machine learning, prepares and deploys these assets, and transfers operations from landing area devices to physical assets, utilizing incremental backups to synchronize data and minimize transfer latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If physical assets are prepared and deployed before client requests, then computing resources are instantly available to clients, but the complexity of coordinating asset preparation, data synchronization, and deployment increases
Solution Approach 1:
The system performs preliminary actions by proactively preparing physical assets before client requests are made. The resource preparation manager identifies needed assets, initiates their preparation, and pre-synchronizes data to landing area devices, so that when clients request resources, they are immediately available without waiting for asset preparation and data transfer.
Solution Approach 2:
Landing area devices serve as intermediary storage systems between the physical assets and clients. They temporarily hold synchronized copies of data and applications, allowing the system to decouple the asset preparation process from client access. This intermediary layer enables instant resource availability while managing complexity by providing a buffer that simplifies the coordination between asset deployment and client requests.
2Reliability
If data is transferred from landing area devices to physical assets after deployment, then data consistency is maintained, but transfer latency occurs
Solution Approach 1:
The system performs data synchronization in advance by copying data from physical assets to landing area devices before clients need access. This preliminary data preparation eliminates the need for time-consuming data transfers after asset deployment, as the landing area devices already contain synchronized copies ready for immediate client access.
Solution Approach 2:
The system creates copies of data and applications from physical assets and stores them in landing area devices. These copies serve as immediate-access replicas that maintain data consistency with the source assets while eliminating transfer latency. Clients access the copied data in the landing area devices rather than transferring data in real-time from the physical assets.
3Productivity
If landing area devices are used as secondary storage systems, then resource allocation efficiency improves, but the quantity of devices required increases
Solution Approach 1:
Landing area devices are designed as multi-functional components that serve multiple purposes: they act as secondary storage systems for cached data, serve as temporary landing zones for newly deployed assets, and function as data synchronization intermediaries. This universality allows the system to maximize the utilization of each device, reducing the total quantity needed while maintaining high resource allocation efficiency.
Solution Approach 2:
The system implements a lifecycle management approach where landing area devices are temporarily allocated for specific purposes and then recovered for reuse. When data is successfully transferred from landing area devices to physical assets, the landing area devices are cleared and made available for new synchronization tasks. This recycling approach reduces the need for permanent dedicated storage devices, optimizing the quantity required.
Data Source
AI summary
A method for managing computing resources includes obtaining, by a resource use manager, a physical asset request from a client, in response to the physical asset request: initiating allocation of a landing area device to the client based on the physical asset request, determining a physical asset to be provided to the client, sending, to a manufacturer, a physical asset preparation request, obtaining a confirmation of deployment of the physical asset from the client, performing a restoration on the physical asset using a most recent landing area incremental backup, and after the initiating the restoration, initiating a transfer of operation from the landing area device to the physical asset.