You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some NS8 applications may require large amounts of storage for their data. To prevent filling the primary node’s storage—which is reserved for container data and benefits from fast random access performance—the workflow allows selecting an additional disk to store application data.
Scenario
The user installs, restores, moves or clones an application and wants to use an additional disk for its data storage.
Solution
During the node selection step, nodes with additional disks are clearly marked.
The user selects the NS8 node where the application will be installed, restored, moved or cloned.
In the next step, the user chooses where to store the application data: either in Default storage1 or on an available additional disk. Each disk displays its total size and available free space.
If the selected node has no additional disks, the workflow ends after node selection.
Once the workflow is completed, the chosen storage location cannot be changed.
Non-goals
The available disk space check, extremely useful in restore, move and clone scenarios, is a future goal.
Activity
[-]Design NethServer block storage[/-][+]Select additional disk for application[/+]AmaLuci commentedon Nov 12, 2025
Mockups ready for review in Figma
AmaLuci commentedon Nov 14, 2025
@DavidePrincipi @andre8244 @gsanchietti I made few changes based on your feedback
Figma file
gsanchietti commentedon Nov 14, 2025
LGTM
DavidePrincipi commentedon Nov 14, 2025
LGTM ✔️
ℹ️ A similar workflow must be implemented also in the Restore and Clone/Move workflows.
andre8244 commentedon Nov 14, 2025
LGTM 🏁