<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body dir="auto">
<div><br>
</div>
<div>On Apr 18, 2014, at 17:03, "Ryan Moats" <<a href="mailto:rmoats@us.ibm.com">rmoats@us.ibm.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<p><font size="2" face="sans-serif">Apologies if this is posted to the wrong place, but after talking with Kyle Mestery (<a href="mailto:mestery@cisco.com">mestery@cisco.com</a>), he suggested that I bring my question here...</font><br>
<br>
<font size="2" face="sans-serif">I'm trying to make sense of the allow_overlapping_ips configuration parameter in neutron. </font><br>
<br>
<font size="2" face="sans-serif">When this entry is true, then a tenant can have subnets with overlapping IPs in different networks (i.e. the scope of the subnet validation search is the other subnets associated with the network) which makes sense.</font><br>
<br>
<font size="2" face="sans-serif">But, when this entry is false, then the validation search appears to cover all subnets across all tenants. I'm trying to understand the logic of this, because I would have expected that in this case, the search scope would
be all subnets across a single tenant. </font><br>
<br>
<font size="2" face="sans-serif">As it is now, it looks like if an install has this configuration parameter set to false, then there is no way for that install to reuse the net 10 address space.</font><br>
<br>
<font size="2" face="sans-serif">Can somebody lend me a hand and either (a) tell me I'm reading the code wrong or (b) explain why that choice was made?</font><br>
</p>
</div>
</blockquote>
<div>You are reading the code correctly. This feature is largely a legacy option for older distros that do not support namespaces or when the deployer chooses to run in a flat mode without tenant isolation.</div>
<div><br>
</div>
<div>mark</div>
</body>
</html>