For libvirt, if the operator wishes to use shared storage, they must
manually configure the sharing resource provider in placement and
associate it via aggregate with the compute node. However, the libvirt
driver was still reporting the (same) DISK_GB inventory in the compute
node provider.
With this patch, we check the provider tree to see if a sharing provider
of DISK_GB is present. If so, we don't report that inventory - because
it's already accounted for by the sharing provider.
Reviewed: https:/ /review. openstack. org/560459 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=7e48b227d06 22b268f74d1a559 aca4cd3784f7cf
Committed: https:/
Submitter: Zuul
Branch: master
commit 7e48b227d0622b2 68f74d1a559aca4 cd3784f7cf
Author: Eric Fried <email address hidden>
Date: Wed Apr 11 09:47:49 2018 -0500
libvirt: Don't report DISK_GB if sharing
For libvirt, if the operator wishes to use shared storage, they must
manually configure the sharing resource provider in placement and
associate it via aggregate with the compute node. However, the libvirt
driver was still reporting the (same) DISK_GB inventory in the compute
node provider.
With this patch, we check the provider tree to see if a sharing provider
of DISK_GB is present. If so, we don't report that inventory - because
it's already accounted for by the sharing provider.
Co-Authored-By: Bhagyashri Shewale <email address hidden> 5fc0bc6d25f3554 8621e8c8c2f
Closes-Bug: #1771728
Change-Id: Iea283322124cb3