[GUI] [ENHANCEMENT] Host local storage support

[torchiaf]

Is your enhancement related to a problem? Please describe.

Related PR https://github.com/harvester/dashboard/pull/1076

We added LVM and Longhorn V2 storage support in Harvester v1.4. We want to add some restrictions to Volumes, Snapshots and Images functionalities when handling these types of storage and improve error handling.

Describe the solution you'd like

• Remove 'Export to Image' action for Longhorn V2 volumes.
• Remove 'Take a snapshot' action for Longhorn V2 volumes (TBD).
• Disable 'Size' inputBox for Longhorn V2 volumes in edit mode and add a warning banner - both Volumes and Virtual Machines page.
• Delete unsaved disk in host edit page should clean related data, add new disk back should have empty fields. (see comment)

Describe alternatives you've considered

Additional context

[torchiaf]

@a110605 I think keeping the removed disks is something we want by design, there is a dedicate logic to do that:

https://github.com/harvester/dashboard/blob/ed19b0de38713d7f8e363de0cc14006f7c4c218d/edit/host/index.vue#L214-L219

addDisk(id) {
  const removedDisk = findBy(this.removedDisks, 'blockDevice.id', id);

  if (removedDisk) {
    return this.newDisks.push(removedDisk);
  }

I'm not sure if we want to remove this behavior. @bk201 what do you think ?

[harvesterhci-io-github-bot]

Pre Ready-For-Testing Checklist

• [ ] If labeled: require/HEP Has the Harvester Enhancement Proposal PR submitted? The HEP PR is at:

• [ ] Where is the reproduce steps/test steps documented? The reproduce steps/test steps are at:

• [ ] Is there a workaround for the issue? If so, where is it documented? The workaround is at:

• [ ] Have the backend code been merged (harvester, harvester-installer, etc) (including backport-needed/*)? The PR is at:

  • [ ] Does the PR include the explanation for the fix or the feature?

  • [ ] Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart? The PR for the YAML change is at: The PR for the chart change is at:

• [ ] If labeled: area/ui Has the UI issue filed or ready to be merged? The UI issue/PR is at:

• [ ] If labeled: require/doc, require/knowledge-base Has the necessary document PR submitted or merged? The documentation/KB PR is at:

• [ ] If NOT labeled: not-require/test-plan Has the e2e test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue?

  • The automation skeleton PR is at:
  • The automation test case PR is at:

• [ ] If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility? The compatibility issue is filed at:

[harvesterhci-io-github-bot]

Automation e2e test issue: harvester/tests#1565

[a110605]

harvester/dashboard#1076

That behavior is strange from my perspective. Is there any harm to clean up the previous remove disk ? cc @bk201

@Vicente-Cheng said backend have no limitation to update disk CR.

[tserong]

I think we need to disable encryption for LHv2 volumes as well (this is on the LH roadmap for v1.8 -- https://github.com/longhorn/longhorn/wiki/Roadmap#longhorn-v18-january-2025)

[tserong]

...and just to confirm, LHv2 does support snapshots. I can successfully snapshot and restore volumes using the LH GUI, so the backend functionality works fine. It's behaving weirdly on the Harvester side - I can create snapshots, but when restoring, the new volumes get stuck somehow, but that means we have a separate issue to fix; I don't think that means we should disable snapshots for V2 volumes.

I'll open a separate issue for the snapshot restore weirdness once I've got some more details...