Open askfongjojo opened 8 months ago
Thank you, this sounds very useful. Prototype in #2058.
@david-crespo: Wow, thanks for the quick turnaround on the prototype! In the PR, you raised a very interesting question about how/if we can present silo image information. I can think of the corner case that the silo image being demoted back into a project subsequently. It'll not be appropriate to show its details for another project user at that point.
One other thing I am also wondering is the usefulness of disk/snapshot/image "genealogy". I have seen that kind of information in VMware for snapshots. In our case, it may look something like this:
disk aaa-1 | from image aaa, created on 2024-01-23 09:30 AM | from snapshot yyy-3, created on 2024-01-22 12:30 PM | from disk yyy, created on 2024-01-22 10:15 AM | from snapshot xxx-1, created on 2024-01-15 11:28 PM |_ from disk xxx, created on 2024-01-10 12:39: PM ...
The history can go on and on if the user keeps iterating on the same disk/snapshot/image family. The feature also has the caveat of exposing information from other projects. We can perhaps keep it bound by capping it some maximum number of generations and stop the traversal as soon as the origin falls outside of the current project. If you think this may be useful and not prone to major issues, I can make a separate ticket for such a feature and get some UX opinions on the presentation.
Travis just requested this feature and I had totally forgotten about this issue and the prototype. It would be really useful. I'm going to put it in the Unscheduled milestone to make it slightly harder to forget.
There are two places to which such information can be added: