Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR

2014-01-28 Thread Edgar Magana
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

Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR

2014-01-28 Thread Carl Baldwin
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

Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR

2014-01-24 Thread Paul Ward
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

Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR

2014-01-23 Thread CARVER, PAUL
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.

Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR

2014-01-23 Thread Paul Ward
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'

Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR

2014-01-23 Thread CARVER, PAUL
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

Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR

2014-01-23 Thread Paul Ward
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

Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR

2014-01-22 Thread Carl Baldwin
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

Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR

2014-01-22 Thread Paul Ward
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

Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR

2014-01-21 Thread Carl Baldwin
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)" > >

Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR

2014-01-21 Thread Paul Ward
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

Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR

2014-01-21 Thread Paul Ward
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

Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR

2014-01-21 Thread Carl Baldwin
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

Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR

2014-01-21 Thread Carl Perry
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

Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR

2014-01-21 Thread Ian Wells
/30 is the minimum allowable mask, not /31. On 21 January 2014 22:04, Edgar Magana wrote: > Wouldn't be easier just to check if: > > cidr is 32? > > I believe it is a good idea to not allow /32 network but this is just my > opinion > > Edgar > > From: Paul Ward > Reply-To: OpenStack List > Da

Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR

2014-01-21 Thread Edgar Magana
Wouldn't be easier just to check if: cidr is 32? I believe it is a good idea to not allow /32 network but this is just my opinion Edgar From: Paul Ward Reply-To: OpenStack List Date: Tuesday, January 21, 2014 12:35 PM To: OpenStack List Subject: [openstack-dev] [neutron] Neutron should