On 06/08/13 12:30 PM, "Nguyen Anh Tu" <ng.t...@gmail.com> wrote:
>Hi Chiradeep, > >Exactly Intellicache. As I know, to use this, VDIs on XenServer/XCP must >be >set two params: >+ on-boot = persist (or reset). If persist, VM's data (except OS) will be >keep when reboot. Otherwise, it will be destroy on local SR when setting >to >"reset". >+ allow-caching = true. It enables cache mode on local SR. > >Maybe we'll add a service offering tag so AgentMgr can realize this >option. 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. >Whatever we change, Xapi must set two above params for VDIs to use this >feature. However, Intellicache seemly can't update changes to VMs which >were booted before changing of Master image. AFAIK, there is no solution that will update gold-image with out recreating the VM to reflect the updates. > > >2013/8/6 Chiradeep Vittal <chiradeep.vit...@citrix.com> > >> Is this the Intellicache feature? What changes does it require from >> CloudStack. >> Would just using service offering tags work? >> >> On 8/5/13 12:23 AM, "Nguyen Anh Tu" <ng.t...@gmail.com> wrote: >> >> >Hi guys, >> > >> >Is anyone concerned about using XenServer 6.2's clone-on-boot feature >>on >> >CloudStack? With it, we can quickly deploy a huge of VMs from a single >> >golden template. This is amazing for some scenarios. For example: we >>can >> >allocate a special/dedicated cluster with only one golden template. And >> >when an update or patch be applied to golden template, changes >> >automatically apply to every VMs. >> > >> >Thought? >> > >> >Thanks, >> > >> >-- >> > >> >N.g.U.y.e.N.A.n.H.t.U >> >> > > >-- > >N.g.U.y.e.N.A.n.H.t.U >
