<html><body>
<p><font size="2" face="sans-serif">Sorry, pulling this from the archives [1] because I seem to have lost the original in my mailbox...</font><br>
<br>
<font size="2" face="sans-serif">></font><tt><font size="3"> 1) (this is more for neutron people) Is there a real use case for<br>
> requesting specific gateway IPs and allocation pools when allocating from a<br>
> pool? If not, maybe we should let the pool set a default gateway IP and<br>
> allocation pools. The user can then update them with another call. Another<br>
> option would be to provide "subnet templates" from which a user can choose.<br>
> For instance one template could have the gateway as first IP, and then a<br>
> single pool for the rest of the CIDR.</font></tt><br>
<br>
<tt><font size="3">The use case that always comes to mind when questions like this are asked is "green-field" vs</font></tt><br>
<tt><font size="3">"brown-field" - if I am deploying something new, then no, I don't need the</font></tt><br>
<tt><font size="3">ability to specify gateway IPs. However, if I am dealing with an existing deployment migration,</font></tt><br>
<tt><font size="3">then I will want to be able to represent what is already out there.</font></tt><br>
<br>
<tt><font size="3">> 2) Is the action of creating a subnet from a pool better realized as a</font></tt><br>
<tt><font size="3">> different way of creating a subnet, or should there be some sort of "pool<br>
> action"? Eg.:</font></tt><br>
<font size="2" face="sans-serif">> </font><br>
<tt><font size="3">> POST /subnet_pools/my_pool_id/subnet<br>
> {'prefix_len': 24}<br>
> <br>
> which would return a subnet response like this (note prefix_len might not<br>
> be needed in this case)<br>
> <br>
> {'id': 'meh',<br>
> 'cidr': '192.168.0.0/24',<br>
> 'gateway_ip': '192.168.0.1',<br>
> 'pool_id': 'my_pool_id'}</font></tt><br>
<tt><font size="3">></font></tt><br>
<tt><font size="3">> I am generally not a big fan of RESTful actions. But in this case the<br>
> semantics of the API operation are that of a subnet creation from within a<br>
> pool, so that might be ok.</font></tt><br>
<br>
<tt><font size="3">This would be my preferred approach of the two given.<br>
</font></tt><br>
<font size="2" face="sans-serif">Ryan Moats</font><br>
<br>
<font size="2" face="sans-serif">[1]</font><a href="http://lists.openstack.org/pipermail/openstack-dev/2015-March/058538.html"><font size="2" face="sans-serif"> http://lists.openstack.org/pipermail/openstack-dev/2015-March/058538.html</font></a></body></html>