1. Proposed title of this feature request
REST api: Image statistics for templates

2. Who is the customer behind the request?
Account name: 	ASML Netherlands B.V.
TAM/SRM customer: no
Strategic Customer: yes

3. What is the nature and description of the request?
 The CU wants to see the image statistics for templates via REST API. In case that the template contains qcow2 image, they can only see the max size of the images, but not the actual allocated size.

4. Why does the customer need this? (List the business requirements here)
templates will always be created with thin provisioned disk images. We know the configured size of course, but we have to look in the filesystem how large the disk image file actually is. This information can and will be used for forecasting the size of and the load on the filesystem(s). Templates are created on a day to day basis and by knowing the actual size of a template it is more manageable.

5. How would the customer like to achieve this? (List the functional requirements here)
either within the statistics collection or in the template collection an entry which states the disk usage. This can be static as the template will not change. No specific requirements, besides that it will be presented in bytes. Perhaps you need to add some additional fields if the template resides on more data stores, a value per datastore for instance?

6. For each functional requirement listed in question 5, specify how Red Hat
and the customer can test to confirm the requirement is successfully
implemented.
https://${RHEV-M}:8443/api/templates/${template}/disks
There is element <size>${size}</size> that contains the size of the disk. There should be one more element that will show the the actual size taken by the disk.

7. Is there already an existing RFE upstream or in Red Hat bugzilla?
no

8. Does the customer have any specific timeline dependencies?
no

9. Is the sales team involved in this request and do they have any additional input?
no

10. List any affected packages or components.
REST API

11. Would the customer be able to assist in testing this functionality if
implemented?
Yes