Right now we force tenants choose a CIDR even if they don't care what
address they get. This allows them to skip that required input.
More importantly, if the network is fully routed, not only do tenants not
know which CIDR to configure, allowing them to choose arbitrary CIDRs can
disrupt the
Salvatore Orlando sorla...@nicira.com writes:
Neutron is adding a new concept of subnet pool. [...]
http://specs.openstack.org/openstack/neutron-specs/specs/kilo/subnet-allocation.html
I apologize for asking this question so long after this spec has been
proposed and discussed - but what is
On 3/21/15, 9:10 AM, Salvatore Orlando
sorla...@nicira.commailto:sorla...@nicira.com wrote:
If we feel a need for specifying the relative position of gateway address and
allocation pools when creating a subnet from a pool which will pick a CIDR from
its prefixes, then the integer value
How would you represent that you want the last address in a /26 network if
you don't know what address range you are getting? 0.0.0.63? That seems
pretty confusing when the resulting address turns out to be 192.168.10.191.
It isn't a new concept to think about the network and host parts of an IP
On Mon, Mar 23, 2015 at 8:52 AM, John Belamaric jbelama...@infoblox.com wrote:
On 3/21/15, 9:10 AM, Salvatore Orlando sorla...@nicira.com wrote:
If we feel a need for specifying the relative position of gateway address
and allocation pools when creating a subnet from a pool which will pick a
An integer index doesn't do it for me. Maybe I'm the only one.
It is part of an IP address. It isn't a new concept to think about
the network and host parts of an IP address separately. Why would we
change the notation from dotted quad (ipv4) to integer just because we
mask out the network
On Mon, Mar 23, 2015 at 4:23 PM, Kevin Benton blak...@gmail.com wrote:
How would you represent that you want the last address in a /26 network if
you don't know what address range you are getting? 0.0.0.63? That seems
pretty confusing when the resulting address turns out to be 192.168.10.191.
I don't think they would be surprised if we call it offset or index.
To me, 0.0.0.63 didn't say that I'd get something ending in .63.
Perhaps this is just a difference in backgrounds then. Even though I'm work
on network stuff all of the time, when I see that it's not obvious that it
will be
I just think that we might bury this discussion considering what Carl said,
and that I agree with.
So far we don't even know if we'll ever need this feature. When a concrete
use case will come for asking things like: gimme a /22 Ipv4 network and
make sure I have a pool spanning from the 1st to the
: 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
] [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 c...@ecbaldwin.net wrote:
On Fri, Mar 20, 2015 at 1:34 PM, Jay
On Fri, Mar 20, 2015 at 12:18 PM, Jay Pipes jaypi...@gmail.com wrote:
2) Is the action of creating a subnet from a pool better realized as a
different way of creating a subnet, or should there be some sort of
pool action? Eg.:
POST /subnet_pools/my_pool_id/subnet
{'prefix_len': 24}
which
On 03/20/2015 02:51 PM, Carl Baldwin wrote:
On Fri, Mar 20, 2015 at 12:18 PM, Jay Pipes jaypi...@gmail.com wrote:
What about this instead?
POST /v2.0/subnets
{
'network_id': 'meh',
'gateway_ip_template': '*.*.*.1'
'prefix_len': 24,
'pool_id': 'some_pool'
}
At least that way it's
On Fri, Mar 20, 2015 at 12:18 PM, Jay Pipes jaypi...@gmail.com wrote:
What about this instead?
POST /v2.0/subnets
{
'network_id': 'meh',
'gateway_ip_template': '*.*.*.1'
'prefix_len': 24,
'pool_id': 'some_pool'
}
At least that way it's clear the gateway attribute is not an IP,
On Fri, Mar 20, 2015 at 12:58 PM, Dean Troyer dtro...@gmail.com wrote:
I thought about doing *s but in the world of Classless Inter-Domain
Routing where not all networks are /24, /16, or /8 it seemed a bit
imprecise. But, maybe that doesn't matter.
So do a CIDR host address: 0.0.0.1/24 can
On 03/09/2015 09:05 AM, Salvatore Orlando wrote:
POST /v2.0/subnets
{'network_id': 'meh',
'gateway_ip': '0.0.0.1',
'prefix_len': 24,
'pool_id': 'some_pool'}
would indicate that the user wishes to use the first address in the
range as the gateway IP, and the API would return something like
On Fri, Mar 20, 2015 at 1:09 PM, Dean Troyer dtro...@gmail.com wrote:
Template is totally the wrong word. It is a host address without a network.
The prefix is there for the same purpose, to OR it back into a network
address.
I just want us to stop inventing things that already exist. You
On 03/20/2015 03:02 PM, Carl Baldwin wrote:
On Fri, Mar 20, 2015 at 12:18 PM, Jay Pipes jaypi...@gmail.com wrote:
2) Is the action of creating a subnet from a pool better realized as a
different way of creating a subnet, or should there be some sort of
pool action? Eg.:
POST
On Fri, Mar 20, 2015 at 1:07 PM, Jay Pipes jaypi...@gmail.com wrote:
On 03/20/2015 02:51 PM, Carl Baldwin wrote:
On Fri, Mar 20, 2015 at 12:18 PM, Jay Pipes jaypi...@gmail.com wrote:
What about this instead?
POST /v2.0/subnets
{
'network_id': 'meh',
'gateway_ip_template':
On Fri, Mar 20, 2015 at 1:34 PM, Jay Pipes jaypi...@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.
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 c...@ecbaldwin.net wrote:
On Fri, Mar 20, 2015 at 1:34 PM, Jay Pipes jaypi...@gmail.com wrote:
How is 0.0.0.1 a host address?
)
Subject: Re: [openstack-dev] [api][neutron] Best API for generating subnets
from pool
On Tue, Mar 10, 2015 at 12:24 PM, Salvatore Orlando sorla...@nicira.com wrote:
I guess that frustration has now become part of the norm for Openstack.
It is not the first time I frustrate people because I ask
, but at least the base functionality will
be there.
-Ryan
-Original Message- From: Carl Baldwin
[mailto:c...@ecbaldwin.net] Sent: Tuesday, March 10, 2015 11:44 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [api][neutron] Best API
Honestly, I'm a little frustrated that this is coming up now when we
tried very hard to discuss this during the spec review and we thought
we got to a resolution. It seems a little late to go back to the
drawing board.
On Mon, Mar 9, 2015 at 7:05 AM, Salvatore Orlando sorla...@nicira.com wrote:
On Mon, Mar 9, 2015 at 5:34 PM, Tidwell, Ryan ryan.tidw...@hp.com wrote:
With implicit allocations, the thinking is that this is where a subnet is
created in a backward-compatible way with no subnetpool_id and the subnets
API’s continue to work as they always have.
Correct.
In the case of a
On 10 March 2015 at 16:48, Carl Baldwin c...@ecbaldwin.net wrote:
Honestly, I'm a little frustrated that this is coming up now when we
tried very hard to discuss this during the spec review and we thought
we got to a resolution. It seems a little late to go back to the
drawing board.
I
On Tue, Mar 10, 2015 at 12:24 PM, Salvatore Orlando sorla...@nicira.com wrote:
I guess that frustration has now become part of the norm for Openstack.
It is not the first time I frustrate people because I ask to reconsider
decisions approved in specifications.
I'm okay revisiting decisions.
Greetings!
Neutron is adding a new concept of subnet pool. To put it simply, it is a
collection of IP prefixes from which subnets can be allocated. In this way
a user does not have to specify a full CIDR, but simply a desired prefix
length, and then let the pool generate a CIDR from its prefixes.
, March 09, 2015 6:06 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [api][neutron] Best API for generating subnets from
pool
Greetings!
Neutron is adding a new concept of subnet pool. To put it simply, it is a
collection of IP prefixes from which subnets can be allocated
29 matches
Mail list logo
