Could you raise a enhancement request? On 10/19/12 2:15 PM, "Tamas Monos" <[email protected]> wrote:
>Hi, > >I'm not sure you can at all. >I think CloudStack uses linked-in clones for virtual disks so the >template must stay on the primary storage otherwise will render the VM >unusable. >All VMs based on the same template will use the same shared linked-in >cloned virtual disks. >I hope in the future this will be changed as causes more trouble than >space it saves for us. > >Regards > >Tamas Monos DDI >+44(0)2034687012 >Chief Technical Office >+44(0)2034687000 >Veber: The Hosting Specialists Fax +44(0)871 522 >7057 >http://www.veber.co.uk > >Follow us on Twitter: www.twitter.com/veberhost >Follow us on Facebook: www.facebook.com/veberhost > >-----Original Message----- >From: Fabrice Brazier [mailto:[email protected]] >Sent: 19 October 2012 13:02 >To: [email protected] >Subject: Re: Template deletion on the primary storage > >Hi Nitin, > >thanks for your reply. But I don"t want to keep the template on the >primary storage after 1 hour. >I have a lot of template in CloudStack, around one template for one VM. >If I have 20 VM, I have 20 templates on CloudStack. So I don"t want to >use twice space on the primary storage. >Where can I change this rule ? > >Regards, >Fabrice > >2012/10/18 Nitin Mehta <[email protected]> > >> The templates do get cleaned up if there is no active volume referring >> to it on the primary storage. There is a storage clean up thread >> running which cleans them up. Check for storage.cleanup.interval in >> the global settings to see how often it runs. >> Btw for XS case we just keep 1 copy of the template and all the >> volumes of the vms created from the same template refer to it thus >> saving us from keeping N copies of the same template. >> >> On 18-Oct-2012, at 3:37 PM, Fabrice Brazier wrote: >> >> > Hi Folks, >> > >> > >> > >> > When you create a VM from a template, the template is deployed on >> > the primary storage and the VM is created from this template then. >> > >> > The template on the primary storage is not deleted and takes space. >> > I guess, the purpose is to save time when you deploy the same >> > template on >> the >> > same primary storage with a cloning process. >> > >> > Does it possible to delete these templates after a specific time ? >> > >> > >> > >> > For a customer, it's taking a lot of space and we want to delete >> > these templates through CloudStack and not manually in the datastore. >> > >> > >> > >> > Thanks for your feedback, >> > >> > Fabrice >> > >> > >> > >> > -- >> > Fabrice Brazier >> > *Apalia*(tm)* >> > *FR: +33-632-73-53-00 >> > *http://www.apalia.net** >> > **[email protected]* >> >> >
