Hi, I can't find where I recently commented on this topic. But @davecahill reminded me of the issue this morning.

The fact that pool-members are a collection at the top-level of the data model seems very very awkward to me. It's like having an CLI operation that would list all the ports in MidoNet, across all devices. It just feels wrong to me.

Moreover, Dave brought up that this breaks aliasing. Because the CLI has no way to know that a certain member in the top-level member collection is the same member that the member collection contained in a pool returns. Thus they get different aliases in different scopes.