GitHub user mike-tutkowski opened a pull request:
https://github.com/apache/cloudstack/pull/674
getUsedBytes should query the SolidFire cluster to acquire the size oâ¦
â¦f the given volume if there is no volume_details info for that volume
(and then create a volume_details row for this volume so we don't have to make
that cluster call for this purpose again)
********************
This only impacts the SolidFire storage plug-in.
In supporting back-end snapshots, I re-wrote how the getUsedBytes method
works (which is called by the capacity manager).
The implementation now depends on a new row in the volume_details table for
the volume in question that says how large the backend volume that supports
your virtual disk is (the virtual disk's size is kept track of in the volumes
table).
Since this addition to the volume_details table is new in 4.6 and these
kinds of volumes have been created before 4.6, we need to make sure if no
applicable volume_details row exits for the volume in question that we go
retrieve the necessary info from the applicable SolidFire cluster and create a
row in the volume_details table for future reference.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mike-tutkowski/cloudstack sf-related
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/674.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #674
----
commit 0f2f6f3b7e82f8a24f3fc76e0b52cb94feb0e794
Author: Mike Tutkowski <mike.tutkow...@solidfire.com>
Date: 2015-08-06T17:59:30Z
getUsedBytes should query the SolidFire cluster to acquire the size of the
given volume if there is no volume_details info for that volume (and then
create a volume_details row for this volume so we don't have to make that
cluster call for this purpose again)
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
