This more has to do with failing before the instance makes it to a compute node and having all the port information details before it's sent to the compute node. Quota restraints like bandwidth would be an attribute of a port (which quantum would manage) and nova-compute should not know anything about. On Thu, May 16, 2013 at 6:28 AM, Henry Gessau <gessau at cisco.com> wrote: > On Wed, May 15, at 3:53 pm, Aaron Rosen wrote: > > > I created the following blueprint and wanted to hear what the community > > though before starting on it. > > > > https://blueprints.launchpad.net/nova/+spec/nova-api-quantum-create-port > > You address specifically the issue with the "number of ports" quota. > > Although we are not ready for it yet, you may want to take into account > that > one day there could be additional quota restraints (like bandwidth). I.e. > just > try to ensure that it will not be too hard to add those when the time > comes. > > -- Henry > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130516/cd2f654e/attachment.html>