You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cloudstack.apache.org by "Harikrishna Patnala (JIRA)" <ji...@apache.org> on 2013/02/06 15:15:14 UTC

[jira] [Updated] (CLOUDSTACK-667) VM's base image update facility

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

Harikrishna Patnala updated CLOUDSTACK-667:
-------------------------------------------

    Fix Version/s:     (was: 4.1.0)
                   4.2.0
    
> VM's base image update facility
> -------------------------------
>
>                 Key: CLOUDSTACK-667
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-667
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>            Reporter: Harikrishna Patnala
>            Assignee: Harikrishna Patnala
>             Fix For: 4.2.0
>
>
> When base image update has been performed (e.g patches applied to the golden master image) then on vm restart there is a need of pointing the VM at the new golden master.
>     
> We need to be able to update existing VMs with a new base image to support the pooled desktop.
> In case of pooled desktops if a VM is already restarted and got pointed to the new updated base image, then when the restart of other VMs it should check for the new updated base image (already downloaded previuosly) and point to that.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira