Comment 7 for bug 1172808

Hi Armando,

I don't agree with your reasoning that its creating it early just to avoid a latter error - its creating it at the point where we can still report any errors to the user. That's just good practice in validating as much as you can as early as possible.

I don't consider it leaky as the user can see the ports that are allocated to them in the Quantum API - much more transparent that the internal reservations in Nova.

There should be no need for a major refactor as a user can already pass a port into the API - and the fact that this is only meaningful for Quantum is already handled.

Quota validation as early as possible is only meaningful if its backed up by reserving the resource in some way - for quantum as it stands that means allocating the port, for nova resources it means holding a reservation. Without creating a resource reservation mechanism for Quantum (either in the Quantum API, or as an external service) then I still don't understand how you're going to get around this.

Regards,
Phil