Vmware should report actual capacity instead of unknown

Registered by jingtao liang on 2016-06-07

Now, the vmware driver report the driver status to cinder like this:
data = {'volume_backend_name': backend_name,
                    'vendor_name': 'VMware',
                    'driver_version': self.VERSION,
                    'storage_protocol': 'vmdk',
                    'reserved_percentage': 0,
                    'total_capacity_gb': 'unknown',
                    'free_capacity_gb': 'unknown'}

The total capacity and free capacity are unknown.I think if we can report the actual capacity will be better.Tks

Blueprint information

Status:
Not started
Approver:
Sean McGinnis
Priority:
Low
Drafter:
jingtao liang
Direction:
Approved
Assignee:
None
Definition:
Approved
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

how does this bp work now? --wangxiyuan

imitev: Capacity stats for VMDK driver have been implemented here https://review.opendev.org/#/c/605762/ but then reverted with this change https://review.opendev.org/#/c/662548/ due to performance concerns. The only option for optimization that I've identified is caching but this would introduce potential issues related to stale cache which should not be underestimated considering the topic. Once the capacity stats are available thin provisioning support could be enabled for VMDK driver.

(?)

Work Items