[openstack-dev] [api][neutron] Best API for generating subnets from pool
ryan.tidwell at hp.com
Fri Mar 20 23:08:54 UTC 2015
Great suggestion Kevin. Passing 0.0.0.1 as gateway_ip_template (or whatever you call it) is essentially passing an address index, so when you OR 0.0.0.1 with the CIDR you get your gateway set as the first usable IP in the subnet. The intent of the user is to allocate the first usable IP address in the subnet to the gateway. The wildcard notation for gateway IP is really a more convoluted way of expressing this intent. Something like address_index is a little more explicit in my mind. I think Kevin is on to something.
From: Kevin Benton [mailto:blak111 at gmail.com]
Sent: Friday, March 20, 2015 2:34 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [api][neutron] Best API for generating subnets from pool
What if we just call it 'address_index' and make it an integer representing the offset from the network start address?
On Fri, Mar 20, 2015 at 12:39 PM, Carl Baldwin <carl at ecbaldwin.net<mailto:carl at ecbaldwin.net>> wrote:
On Fri, Mar 20, 2015 at 1:34 PM, Jay Pipes <jaypipes at gmail.com<mailto:jaypipes at gmail.com>> wrote:
> How is 0.0.0.1 a host address? That isn't a valid IP address, AFAIK.
It isn't a valid *IP* address without the network part. However, it
can be referred to as the "host address on the network" or the host
part of the IP address.
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStackfirstname.lastname@example.org?subject:unsubscribe>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev