scottsignal commented on issue #12169: URL: https://github.com/apache/cloudstack/issues/12169#issuecomment-3608708654
> > > > It's not possible to guarantee a template will always be around and it's a waste of space to keep older templates. > > > > > > > > > you can force-delete the template. the vm instances created from it will not be impacted. > > > the image of vm instance is created from a base image which is the template image. if the vm instance is linked to another vm template which might cause some issues, for example > > > > > > * the base image is removed from primary storage as ACS thinks the template is not used by vm instance > > > * volume migration might cause data corruption > > > > > > What about just removing the association? Like a 1-way trip with a warning message that says this? > > the 2nd issue might not occur, but the 1st issue might still exist. > > I think the safe way for now is, force-deleting the template. templates will be removed from secondary storage, vms are not impacted. when vms is expunged or reinstalled, ACS will clean up the unused template image on primary storage. I just hate the idea of having to force delete the template/ISO and then turn around and upload the same template over just so it can be reassigned. So essentially, every time we provision an instance on behalf of a customer using a Template/ISO that cannot be exposed to a customer we would have to do this. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
