Comment 4 for bug 1585572

@vikas, I don't think the kv store is an issue; we could store the pool id probably as a tag for the corresponding network but the problem is that I don't think we know the association.
That is, when the pool is created there is no reference to the network and when network is created there is no reference to the pool. As far as the remote driver/plugin is concerned, it has no idea about the pools and the IPAM stuff. Am I missing something here?

The default docker IPAM driver, uses the same pool if the same cidr is specified during the network creation of multiple networks. Furthermore, it does not allow overlapping cidrs within an address space as of now.

The OpenStack user expectation is that she can specify overlapping or identical cidrs for different networks.