Comment 4 for bug 1111572

so I wrote a patch to fix this issue, but it wasn't until I started running the unit tests that I realized that the command in the bug request is actually wrong. It should be allocation_pools (with an "s").

When you run that, you get an error from Quantum saying that allocation_pools is read-only and can't be updated.

quantum subnet-update foo --allocation-pools start=10.1.0.10,end=10.1.0.254
Cannot update read-only attribute allocation_pools

This is actually already documented here: http://docs.openstack.org/api/openstack-network/2.0/content/Concepts-d1e369.html

I have the code to make allocation pools writable similar to what we already do for host_routes or dns_nameservers, but its more of a spec question whether we would want to make that change.