Comment 3 for bug 1729621

Please note that Pike and Ocata schedulers are not affected by this issue, since starting in Ocata, we stop using the ComputeNode.vcpus_used value from the CoreFilter (which was deprecated/removed in Ocata) and instead use the (accurate) information from the placement API service about allocated VCPU resources for instances. Placement doesn't care or know about whether an instance is shutdown or not -- only if the instance is "on" the host.