Using a non-default GW IP should set the allocation pool also accordingly

Is that how it behaves in stock devstack? I dont' see this requirement in documentation.

Pls see below with openstack running with openvswitch :

curl -i http://10.204.217.83:9696/v2.0/subnets.json -X POST -H "X-Auth-Token: <token>" -H "Conten
t-Type: application/json" -H "Accept: application/json" -H "User-Agent: python-neutronclient" -d '{"subnet": {"network_id": "02b7d689-ea66-4d7b-9373-658f
10ad1012", "ip_version": 4, "cidr": "20.1.1.0/24", "gateway_ip": "20.1.1.10"}}'

DEBUG: neutronclient.client RESP:{'date': 'Mon, 28 Jul 2014 14:28:38 GMT', 'status': '201', 'content-length': '412', 'content-type': 'application/json; c
harset=UTF-8'} {"subnet": {"name": "", "enable_dhcp": true, "network_id": "02b7d689-ea66-4d7b-9373-658f10ad1012", "tenant_id": "3136f090ef9c493e9c70184ce678482c", "dns_nameservers": [], "allocation_pools": [{"start": "20.1.1.1", "end": "20.1.1.9"}, {"start": "20.1.1.11", "end": "20.1.1.254"}], "host_routes": [], "ip_version": 4, "gateway_ip": "20.1.1.10", "cidr": "20.1.1.0/24", "id": "620ae687-fd94-4f6c-af0c-d52177d9e7b7"}}

Created a new subnet:
+------------------+---------------------------------------------+
| Field | Value |
+------------------+---------------------------------------------+
| allocation_pools | {"start": "20.1.1.1", "end": "20.1.1.9"} |
| | {"start": "20.1.1.11", "end": "20.1.1.254"} |
| cidr | 20.1.1.0/24 |
| dns_nameservers | |
| enable_dhcp | True |
| gateway_ip | 20.1.1.10 |
| host_routes | |
| id | 620ae687-fd94-4f6c-af0c-d52177d9e7b7 |
| ip_version | 4 |
| name | |
| network_id | 02b7d689-ea66-4d7b-9373-658f10ad1012 |
| tenant_id | 3136f090ef9c493e9c70184ce678482c |
+------------------+---------------------------------------------+
root@nodec43:~#

we can release note this and take it up if/when need arises.

We have decided not to work on it for 1.10 release

no plan to fix in 1.1, marked accordingly

I think it is open for interpretation in understanding allocation-pool. Neutron does not impose any such requirement and if we do this way for gw_ip, what will do if dns_nameservers[] are within the pool, for multiple such reserved entries within single allocation-pool, are we going to slice alloc-pool to number of allocation-pools to display. IMO, we should continue to display as user has configured