You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Nicolas Vazquez (JIRA)" <ji...@apache.org> on 2016/10/12 20:39:20 UTC

[jira] [Created] (CLOUDSTACK-9539) Support changing Service offering for instance with VM Snapshots

Nicolas Vazquez created CLOUDSTACK-9539:
-------------------------------------------

             Summary: Support changing Service offering for instance with VM Snapshots
                 Key: CLOUDSTACK-9539
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9539
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
            Reporter: Nicolas Vazquez
            Assignee: Nicolas Vazquez


h3. Actual behaviour
CloudStack doesn't support changing service offering for vm instances which have vm snapshots, they should be removed before changing service offering.

h3. Goal
Extend actual behaviour by supporting changing service offering for vms which have vm snapshots. In that case, previously taken snapshots (if reverted) should use previous service offering, future snapshots should use the newest.

h3. Proposed solution:
1) Adding {{service_offering_id}} column on {{vm_snapshots}} table: This way snapshot can be reverted to original state even though service offering can be changed for vm instance.
*NOTE:* For already created vm snapshots, {{service_offering_id}} will be null



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)