Comment 7 for bug 1475792
Revision history for this message
| Brian Haley (brian-haley) wrote Re: Change Neutron so that it can auto-allocate networks | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
@Alexis - so in your opinion this should stay a two-step process:
1) get a list of networks as we do today
2) allocate a network if none exist
And since GET can't have side-effects (like creating a resource), then a PUT is required?
@Jay - I'd rather not have to add a config option to Nova to make the call, but instead have all this logic live in Neutron, since it would have to be configured there by an admin to work anyway.
This would also allow what is allocated to be completely opaque to Nova - it could be a similar-looking 10.0.0.0/16 subnet for everyone, or it could be pulled from a subnetpool, but Nova doesn't need to know the details, only Neutron does.
And I don't think we should change this behavior:
1) get list of tenant-specific networks
2) get list of shared networks
3) if above yielded nothing, make a network
Some deployments will want to use a public (shared) network and want that to be the default.