© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
I've pushed up this:
https:/
Which reflects my admittedly poor understanding of all of the issues at hand.
To be clear - I'm not trying to suggest changes to defaults - only that things like the gate (specifically inclusive of the actual gate) need to be able to sanely express "this network range is safe for the cloud to use for networking things". Although the gate is an obvious and very present example, one can easily imagine people wanting to tell devstack to use particular ranges when running at home so as to not have devstack trying to step on IPs that run the TV or the fridge or whatnot.
In the case where no such ranges have been communicated, the current behavior seems fine.
If it needs to be the case that there need to be _2_ ranges set and they need to be different and non-overlapping, then let's be explicit about that and we make sure devstack-gate always does that.