Bug #4108

saveas action create non-persistent image

Added by Laurent Grawet almost 5 years ago. Updated almost 5 years ago.

Status:ClosedStart date:10/29/2015
Priority:HighDue date:
Assignee:Carlos Martín% Done:

0%

Category:Core & System
Target version:Release 4.14.2
Resolution:fixed Pull request:
Affected Versions:OpenNebula 4.14

Description

Hi,

When a user run saveas command (in sunstone cloud view for example) the image is saved as non-persistent. Users expect to have their modifications saved inside the image. Also, they can't change persistent state from cloud view.
But maybe I'm missing some setting ?

Thank you,

Laurent

Associated revisions

Revision 45b33cab
Added by Carlos Martín almost 5 years ago

Bug #4108: Add option to create persistent images in onevm save-as-template

Revision 6bbe71a3
Added by Carlos Martín almost 5 years ago

Bug #4108: Add option to create persistent images in onevm save-as-template

(cherry picked from commit 45b33cabc5440e73051db06056388a7f732a7cdb)

History

#1 Updated by Ignacio M. Llorente almost 5 years ago

  • Assignee set to Carlos Martín

#2 Updated by Carlos Martín almost 5 years ago

  • Status changed from Pending to New

The proposed solution is to ask the user if he wants the saved image to be persistent or not. To avoid complexity, the image persistency cannot changed from the cloud view afterwards. This will work via the cloud view, user view, and CLI (onevm save).

#3 Updated by Carlos Martín almost 5 years ago

  • Status changed from New to Closed
  • Resolution set to fixed

#4 Updated by Laurent Grawet almost 5 years ago

Thank you Carlos!
I think it would be interesting to declare a default value for persistency (0/1) via yaml config file in this case. This concerns all sunstone views. But maybe a new feature request would be more appropriated ?

Cheers,

Laurent

#5 Updated by Laurent Grawet almost 5 years ago

New feature request #4172 opened

Also available in: Atom PDF