Edge Node File System Partitioning for Seamless Remote Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Updating resource-constrained edge nodes in distributed computing environments is challenging due to limited computing resources, which can drain performance and introduce security risks, and requires offline updates that disrupt system functionality.
Innovation Solution
Utilizing a staging node with more resources to partition the file system of the edge node, allowing updates to be performed remotely without taking the edge node offline, by mounting the file system on two partitions and synchronizing the updated copy during normal operation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If updates are performed on resource-constrained edge nodes directly, then the edge nodes can be updated, but the limited computing resources are drained and performance is negatively impacted
Solution Approach 1:
A staging node is introduced as an intermediary between the management node and the edge node. The staging node receives update files from the management node and transfers them to the edge node, allowing updates to occur without consuming the edge node's limited computing resources for update processing.
Solution Approach 2:
The update process is segmented into distinct phases: update file preparation at the management node, transfer via the staging node, and application at the edge node. This segmentation allows the edge node to remain operational during the update process while still receiving updates.
2Reliability
If edge nodes are taken offline for updates, then updates can be performed without resource constraints, but system functionality is disrupted
Solution Approach 1:
The update file is prepared and validated at the management node before being transferred to the edge node. This preliminary action ensures the update is ready to be applied without interrupting the edge node's operation, as the update can be applied in-place during runtime.
Solution Approach 2:
The edge node continues to perform its normal functions throughout the update process. The update is applied to the running system without requiring a shutdown, maintaining continuous operation of the distributed computing environment.
3Reliability
If large update files are transferred to resource-constrained edge nodes, then the edge nodes can be updated, but storage space requirements exceed available capacity
Solution Approach 1:
The update file is extracted from the management node and temporarily stored at the staging node, which has sufficient storage capacity. From the staging node, only the necessary update portions are transferred to the edge node, reducing the storage burden on resource-constrained edge devices.
Data Source
AI summary
Edge nodes in distributed computing environments can be updated according to some aspects described herein. For example, a first node in the distributed computing environment can receive an update request from a management node. The update request can include an update file for updating a second node. In response to receiving the update request, the first node can generate a first partition and a second partition, containing the update file, within the first node. Additionally, the first node can generate a network tunnel between the first node and the second node. The first node can mount a file system for the second node onto the first partition and a copy of the file system onto the second partition of the first node via the network tunnel. The first node also can update the file system in the second partition using the update file to generate an updated file system.