Comment 5 for bug 1172808

Hi Armando,

I don't see it as creating a port just for the sake of checking the quota - I see it as creating the port earlier at the point where you can still meaningfully return an error to the user. The port will then be kept and passed down with the request just as if the user had created it and passed it into Nova.

Whether Nova holds a port from quantum through the create requests or a reservation on a port from quantum still comes down to Nova having to hold and manage an object from Quantum for a transaction that spans multiple Nova nodes, so I don't really see the need to introduce a reservation object. Why not just hold the port ?

I think centralizing quota management into Nova would be moving the wrong way - there is probably a need for a common external quota service that can be shared by all projects and that would be better that adding more integration into Nova itself. There was a discussion about this in Portland, but the concerns were how to make it sufficiently robust and scale-able. I think that's maybe a whole different topic (which also includes Domain level quotas, etc) than just addressing this issue