We have upgraded to OpenNebula 4.14.2 last week and we see that volatile disk quota is called now System disks quota but we are seeing the following behaviour which it is different from the volatile disk quota on previous release (4.12):
- We import a image from our AppMarket and we saved it on one of the local datastores. Then, we instantiate it and we see that the System disks quota is equal to the size of this image.
Therefore, I am a bit lost here, I understood “System disks quota” includes volatile or cloned disks but from I previous post in the past, I understand it is including now anything that is in the system datastore. Is that right? If it is so, what is the difference between put a quota on the images datastore (IMAGE_DS) or put it on the “System disks”. Also, what do you think is the best approach to follow in this case?
Thanks in advance,