Well say Carl!
I am sorry I did not get back to you on this topic before.
In general and after thinking about it, it makes sense to leave could
admin to adage the /32 cases if any.
Edgar
On 1/28/14 1:46 PM, "Carl Baldwin" wrote:
>I think I agree. The new check isn't adding much value and we co
I think I agree. The new check isn't adding much value and we could
debate for a long time whether /30 is useful and should be disallowed
or not. There are bigger fish to fry.
Carl
On Fri, Jan 24, 2014 at 10:43 AM, Paul Ward wrote:
> Given your obviously much more extensive understanding of ne
Given your obviously much more extensive understanding of networking than
mine, I'm starting to move over to the "we shouldn't make this fix" camp.
Mostly because of this:
"CARVER, PAUL" wrote on 01/23/2014 08:57:10 PM:
> Putting a friendly helper in Horizon will help novice users and
> provide
Paul Ward wrote:
>Given your statement about routers potentially using a /30 network, I think we
>should leave the restriction at /30
>rather than /29. I'm assuming your statement that >some routers use /30
>subnets to connect to each other could
>potentially apply to neutron-created routers.
R, PAUL"
> To: "OpenStack Development Mailing List (not for usage questions)"
> ,
> Date: 01/23/2014 02:26 PM
> Subject: Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR
>
> Paul Ward:
> Thank you to all who have participated in this thread. I'
Paul Ward:
Thank you to all who have participated in this thread. I've just proposed a
fix in gerrit. For those involved thus far, if you could review I would be
greatly appreciative!
https://review.openstack.org/#/c/68742/1
I wouldn't go so far as to say this verification SHOULDN'T be added
in
> To: "OpenStack Development Mailing List (not for usage questions)"
> ,
> Date: 01/21/2014 05:32 PM
> Subject: Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR
>
> I think there may be some confusion between the two concepts: subnet
> and allocation p
of the subnet.
>
>
>
> Carl Baldwin wrote on 01/21/2014 09:22:55 PM:
>
>> From: Carl Baldwin
>> To: OpenStack Development Mailing List
>> ,
>> Date: 01/21/2014 09:27 PM
>
>
>> Subject: Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR
ailing List
,
> Date: 01/21/2014 09:27 PM
> Subject: Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR
>
> The bottom line is that the method you mentioned shouldn't validate
> the subnet. It should assume the subnet has been validated and
> validate the pool. It
ith a subnet of 255.255.255.255, so it got
> through somehow. I will look into that more tomorrow.
>
>
>
> Carl Baldwin wrote on 01/21/2014 05:27:49 PM:
>
> > From: Carl Baldwin
> > To: "OpenStack Development Mailing List (not for usage questions)"
> >
k Development Mailing List (not for usage questions)"
> ,
> Date: 01/21/2014 05:32 PM
> Subject: Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR
>
> I think there may be some confusion between the two concepts: subnet
> and allocation pool. You are right that
n a single-IP subnet without a gateway, which is also a dead
end.
Thoughts?
Edgar Magana wrote on 01/21/2014 03:04:47 PM:
> From: Edgar Magana
> To: OpenStack List ,
> Date: 01/21/2014 03:10 PM
> Subject: Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR
>
> Woul
I think there may be some confusion between the two concepts: subnet
and allocation pool. You are right that an ipv4 subnet smaller than
/30 is not useable on a network.
However, this method is checking the validity of an allocation pool.
These pools should not include room for a gateway nor bro
Using a /32 has use cases. When trying to build a L3 only routed network
/32 routes are required. While it can be inconvenient for the more
generic L2 network use case, I wouldn't remove it since there are other
use cases where it is useful.
-Carl
On 01/21/2014 12:35 PM, Paul Ward wrote:
>
> Cu
ul Ward
> Reply-To: OpenStack List
> Date: Tuesday, January 21, 2014 12:35 PM
> To: OpenStack List
> Subject: [openstack-dev] [neutron] Neutron should disallow /32 CIDR
>
> Currently, NeutronDbPluginV2._validate_allocation_pools() does some very
> basic checking to be sure the s
utron should disallow /32 CIDR
Currently, NeutronDbPluginV2._validate_allocation_pools() does some very
basic checking to be sure the specified subnet is valid. One thing that's
missing is checking for a CIDR of /32. A subnet with one IP address in it
is unusable as the sole IP address will be al
Currently, NeutronDbPluginV2._validate_allocation_pools() does some very
basic checking to be sure the specified subnet is valid. One thing that's
missing is checking for a CIDR of /32. A subnet with one IP address in it
is unusable as the sole IP address will be allocated to the gateway, and
t
17 matches
Mail list logo
