[ 
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;}}

2. New vm snapshots will use instance vm service offering id as 
{{service_offering_id}}

3. Revert to vm snapshots should use vm snapshot's {{service_offering_id}} 
value.

h3. Example use case:
* VM Instance V created with service offering A
* Take vm snapshot of V -> snap1 (service offering A)
* Change V service offering to B
* Revert to vm snapshot snap 1
It is expected that V has service offering A after last step

  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: 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;}}


> 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;}}
> 2. New vm snapshots will use instance vm service offering id as 
> {{service_offering_id}}
> 3. Revert to vm snapshots should use vm snapshot's {{service_offering_id}} 
> value.
> h3. Example use case:
> * VM Instance V created with service offering A
> * Take vm snapshot of V -> snap1 (service offering A)
> * Change V service offering to B
> * Revert to vm snapshot snap 1
> It is expected that V has service offering A after last step



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

Reply via email to