Skip to content

Select additional disk for application #7739

Closed
Closed

Description

@DavidePrincipi

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.

Image

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.

See also

Discussion https://mattermost.nethesis.it/nethesis/pl/m54mhkfat3fnmkaan9dcd3bsue

Footnotes

  1. the "Default Storage" can be the root filesystem or a specific additional disk, depending on the /etc/nethserver/volumes.conf file. ↩

Activity

  1. added this to the NethServer 8.7 milestone on Nov 10, 2025
  2. changed the title [-]Design NethServer block storage[/-] [+]Select additional disk for application[/+] on Nov 10, 2025
  3. moved this from ToDo to In Progress in NethServeron Nov 10, 2025
  4. AmaLuci commented on Nov 12, 2025

    @AmaLuci

    Mockups ready for review in Figma

  5. moved this from In Progress to Testing in NethServeron Nov 12, 2025
  6. AmaLuci commented on Nov 14, 2025

    @AmaLuci

    @DavidePrincipi @andre8244 @gsanchietti I made few changes based on your feedback
    Figma file

  7. gsanchietti commented on Nov 14, 2025

    @gsanchietti
    Member

    LGTM

  8. DavidePrincipi commented on Nov 14, 2025

    @DavidePrincipi
    MemberAuthor

    LGTM ✔️

    ℹ️ A similar workflow must be implemented also in the Restore and Clone/Move workflows.

  9. removed their assignment
    on Nov 14, 2025
  10. andre8244 commented on Nov 14, 2025

    @andre8244
    Contributor

    LGTM 🏁

  11. removed their assignment
    on Nov 14, 2025
  12. moved this from Testing to Done in NethServeron Nov 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions