Count resources to check quota in API

We propose a new approach of counting consumed resources and checking the count against the quota limits in the API instead of the current reserve/commit model where a reservation record is created, quota usage records are created and marked as “in_use” when they are committed, and the reservation record deleted. Since Nova has already introduced this feature during Pike [1], we will take the same approach as Nova did.