cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Vazquez (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-9539) Support changing Service offering for instance with VM Snapshots
Date Fri, 14 Oct 2016 15:11:20 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-9539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Nicolas Vazquez updated CLOUDSTACK-9539:
----------------------------------------
    Description: 
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: Existing vm snapshots are populated on update script by {{UPDATE vm_snapshots s JOIN
vm_instance v ON v.id = s.vm_id SET s.service_offering_id = v.service_offering_id;}}

  was:
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


> 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: Existing vm snapshots are populated on update script by {{UPDATE vm_snapshots s
JOIN vm_instance v ON v.id = s.vm_id SET s.service_offering_id = v.service_offering_id;}}



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

Mime
View raw message