harikrishna-patnala commented on issue #12099: URL: https://github.com/apache/cloudstack/issues/12099#issuecomment-4046249370
@bradh352 I hope we tried to answer you on why that exception came up when a disk size is given in a compute offering. DiskOffering strictness is used when operator wants users to change or not to change the whole diskoffering of a root disk. If DiskOffering strictness is enabled, then a user cannot change the disk offering of that root disk using the following action. <img width="353" height="129" alt="Image" src="https://github.com/user-attachments/assets/4468eff7-8366-41b8-9f30-a355c351d387"; /> There is a bit of flexibility given when it comes to resizing of the volumes. While a disk offering is created, an operator can still chose whether root disk size can be resized or not using below option in the disk offering <img width="199" height="71" alt="Image" src="https://github.com/user-attachments/assets/cefba136-b4f1-4c75-8722-e25eb2c0e3e7"; /> The suggested way if an operator wants to have good control on disk parameters of a root disk, is to create a disk offering separately and link it in the compute offering, like below (by disabling "Compute only disk offering") <img width="730" height="343" alt="Image" src="https://github.com/user-attachments/assets/99bccd1f-491a-49d4-8161-4d7a03199761"; /> The above details are all about Disk offerings and the strictness details. In your case, if you want to have disk size (400G) specified in the offering and allow resize, then create a disk offering with disk size 400G and link to a compute offering with keeping the default values (disabled) of "Disk Offering Strictness" in the compute offering and "Disk size strictness" in the disk offering. -- 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]
