I think Intellicache is different. I found a discussion here: http://s.apache.org/NIX
Also, this feature https://cwiki.apache.org/confluence/x/zCPVAQ allows the same use case as the 'update to golden master' On 8/6/13 8:36 AM, "Nguyen Anh Tu" <ng.t...@gmail.com> wrote: >2013/8/6 Murali Reddy <murali.re...@citrix.com> > >> So there is a 'isvolatile' flag to createServiceOffering in starting >>from >> 4.2. VM's created with volatile set to true will have root disks >> re-created. Perhaps You could optimise the implementation of volatile >>VM's >> in case of Intellicache. >> > >Oh I don't know about this flag. We can use Intelicache in CloudStack to >reduce VM's boot times, decrease network volume and traffic, and save on >total of storage costs. Just change allow-cache to "true". > >AFAIK, there is no solution that will update gold-image with out >> recreating the VM to reflect the updates. >> > >Right. And I can use VM.clone instead to do this. > >@All: how we need about this feature? I can make a proposal :-) > >Cheers, >-- > >N.g.U.y.e.N.A.n.H.t.U
