Implement Progress Bar + Estimated Time Remaining + Cancel Button for Volume Snapshots
- Vorherrschende Sprache
- Java
- Sterne
- 3.1k
- Forks
- 1.4k
- Ø Merge
- 6 T. 19 Std.
- Gemergte PRs (30 T.)
- 32
Beschreibung
##### ISSUE TYPE
* Improvement Request
##### COMPONENT NAME
~~~
Volume Snapshots
~~~
##### CLOUDSTACK VERSION
~~~
4.19.0
~~~
##### CONFIGURATION
##### OS / ENVIRONMENT
##### SUMMARY
Currently when taking Volume Snapshots, users have no idea how long the operation takes.
Cloudstack will just show a circle loading animation, with no indication on progress or time left.
As a result, user does not know if there is a bug in the snapshot process, or its actually in progress.
This becomes even worse for large volumes (eg. 10TB) where it can take hours to complete.
And if the user waits too long, they will think the system hanged and would then attempt to create a new Volume Snapshot, resulting in 2 on going copies, which will slow down the entire system.
Volume Snapshot seems to be a very intensive operation. In this case, user should be allowed to cancel an ongoing volume snapshot if desired, to save system resources from an unmeaningful operation.
My suggestion is to add a progress bar to the following UI for better user experience:



This implementation should be neutral to the underlying storage, such as NFS, Object Storage, Ceph, Linstor etc
##### STEPS TO REPRODUCE
~~~
~~~
##### EXPECTED RESULTS
~~~
Better user experience for volume snapshots
~~~
##### ACTUAL RESULTS
~~~
- Cant tell if Volume Snapshot hanged, or is in progress (especially large Volumes)
- Cant monitor progress of snapshot
- Cant cancel Volume Snapshot
~~~
Beitragsleitfaden
Rechercherichtung
Beginnen Sie mit der Überprüfung der in den verknüpften Screenshots dargestellten Volume Snapshots UI und des bestehenden Ablaufs für Snapshot-Operationen. Legen Sie fest, wie Fortschritt, geschätzte Zeit und Abbruch für NFS, Object Storage, Ceph und Linstor funktionieren sollen; fertig ist die Aufgabe, wenn Benutzer Snapshots überwachen und abbrechen können, ohne storage-spezifisches Verhalten.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- java
- Bereich
- backend, cloud, frontend, infrastructure
- Issue-Typ
- Feature
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 25/100