andrijapanicsb commented on issue #803: URL: https://github.com/apache/cloudstack-primate/issues/803#issuecomment-708203074
I didn't ask for it - we are now in GA - and ues, backend changes, below is my take on it: it's not only the UI - it's also the backend - and IF we should support it or not - probably NOT - as we don't have (atm) a way for ACS to validate if the customer wanted to cheat by choosing a smaller custom disk size, than the real volume size (from the template, 5GB in this example, but couild be anything...) - thus tricking the billing (we don't resize or anything - we just assign an offering in the DB, for billing purposes - AFAIK) Also, starting from 4.15 and onwards, any newly registered template (for VMware, as this bug is related to VMware only) - we are using templates as they are - i.e. NO choosing of offering for each disk, or anything (in background we assign each disk/volume to a custom offering with the same size as the size of the volume) - so absolutely no need to invest any effor here - IMO at least. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
