cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Murali Reddy <>
Subject Re: [Discuss] Using XenServer 6.2's Clone-on-Boot feature on CloudStack
Date Tue, 06 Aug 2013 12:28:50 GMT
On 06/08/13 12:30 PM, "Nguyen Anh Tu" <> wrote:

>Hi Chiradeep,
>Exactly Intellicache. As I know, to use this, VDIs on XenServer/XCP must
>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
>+ allow-caching = true. It enables cache mode on local SR.
>Maybe we'll add a service offering tag so AgentMgr can realize this

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 <>
>> 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" <> wrote:
>> >Hi guys,
>> >
>> >Is anyone concerned about using XenServer 6.2's clone-on-boot feature
>> >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
>> >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

View raw message