kladderadeng commented on issue #10588: URL: https://github.com/apache/cloudstack/issues/10588#issuecomment-2750285517
The issue I have is not that it is possible to change the OS Type retroactively on an uploaded ISO. I am sure there are usecases (someone makes a mistake or wants to find the best OS type for a particular ISO). My issue is, that changing the ISO / Image OS type, changes all Instances that where once created by that ISO and there is a) no indicator that this is going to happen b) there seems to be no way to prevent someone doing that (on purpose or by accident) c) there is no visible connection between the ISO and the Instances that show which instances will be affected If we continue with ACS, we will host hundreds of Windows VMs on it. Knowing that we can destroy the whole fleet of VMs by making a single change on an ISO does not make me sleep well. It is not like you select all Instances, click on delete, then on OK. You make a change on a part of the infrastructure that does not have any visible connection to the instances anymore, but it making changes to them. This is really worrying to me. If I were to make a wish, I either - wish there would be no invisible connection between ISOs and Instances. Personally I do not see a usecase why I would change the OS type of all Instances that originated from a particular ISO by changing the OS type of the ISO. I would change the OS Type of the particular instance directly. - If this behavior is intended, having a global setting that prevents to change the OS type of an ISO retroactively would prevent a disaster that is about to happen with the current behavior, at least for Windows VMs. -- 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]
