Bug 928820 - [RFE] Snapshot tree
Summary: [RFE] Snapshot tree
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: RFEs
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Rob Young
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On: 1539837
Blocks: 1213937
TreeView+ depends on / blocked
 
Reported: 2013-03-28 14:09 UTC by Jiri Belka
Modified: 2020-07-25 09:17 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-24 13:44:55 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:
sherold: Triaged+


Attachments (Terms of Use)

Description Jiri Belka 2013-03-28 14:09:39 UTC
Description of problem:
Please implement snapshot tree so one can make a "branch" of a snapshot and this branch can live its own life without interfering with other branches. It is not possible right now, now the snapshot are linear. I feel this as *big* disadvantage. In my case I cannot for example save work when working with old snapshot (snapshot_1 -> i upgrade OS, cannot save into snapshot as there is snapshot_2, snapshot_3...).

Our competitor has this funcionality.

Version-Release number of selected component (if applicable):
sf11

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:
Previewing old snapshot and saving/commiting changes breaks following/newer snapshots.

Expected results:
To be able to work with older snapshots and save work into older snapshosts, or their branches, thus a 'snapshot tree' funcionality is needed.

Additional info:

Comment 2 Sean Cohen 2014-07-29 13:22:11 UTC
Closing old RFE's that are out of scope for the next releases
Feel free to re-open if a new justification is raised from the field.
Sean

Comment 16 Doron Fediuck 2018-06-24 13:44:55 UTC
Closing old issues.
If still needed please provide the use case and re-open.

Comment 17 Franta Kust 2019-05-16 13:09:49 UTC
BZ<2>Jira Resync


Note You need to log in before you can comment on or make changes to this bug.