Thanks for the reply Kirk. Will it auto-delete templates if there are not any VMs cloned from them? Is there a better way to keep templates up-to-date with patches?
We will be patching these templates fairly often as Microsoft releases new patches. It sounds like our secondary storage will grow quite quick if it doesn't delete old templates, or if we have long-lived VMs that are linked to these old templates. This does explain why our secondary storage has grown more than we expected lately. Thanks for any help or guidance you can provide! Sean > On Apr 18, 2016, at 7:24 PM, Kirk Kosinski <kirk.kosin...@shapeblue.com> > wrote: > > Hi, yes that is a good way to do it. Note that if you do delete a template > that is in use, it won't actually be deleted on the back-end (i.e. the > database entries will remain, as will the files on secondary storage), rather > it is just hidden from the end-users in the UI and API. Giving a new > template the same name as a deleted one might be a bit confusing so you could > consider adding a version number or date code. > > Best regards, > > Regards, > > Kirk Kosinski > > kirk.kosin...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HS > @shapeblue > > -----Original Message----- > From: Sean Lair [mailto:sl...@ippathways.com] > Sent: Monday, April 18, 2016 3:09 PM > To: users@cloudstack.apache.org > Subject: Best way to update Templates > > Hello, > > We need to periodically update our templates, for example installing the > latest Windows updates in our Windows Server templates Is there a way to > update existing templates or do we just need to delete the old template and > create new one with the same name? > > The only issue I see with that so far is that we lose the linkage between > instaces (VMs) and templates. > > Thanks > Sean >
