Feature #5375
Consistent save as functionality
| Status: | Pending | Start date: | 09/18/2017 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 5.6 | |||
| Resolution: | Pull request: |
Description
Currently there are two ways to create a copy of VM to work with:
- Before instantiating the VM, labeling it as going to be saved
- During the VM life-cycle when the user is happy with the state, vm save as template
Having two different logic paths to obtain the same result is confusing and impose artificial limitations. This issue is to remove instantiate as persistent, once the save as functionality is improved.
Related issues
History
#1
Updated by Ruben S. Montero almost 4 years ago
- Related to Feature #5374: Improve VM save_as logic added