What about 'extending' Neutron's response with more data from other API calls (e.g. Other Neutron API calls, or even Nova)? Unless there's a requirement that there has to be a 1:1 mapping from the commands to the API.
Can we, say, take that response and 'join' it with Nova's response as well[1]? That way you get the Pool Names as well, you could even make the requests in parallel.
Another alternative is to request the details of each floating ip (I'm not sure if it can be batched in a single request) and then add the floating_network_id to each floating_ip output row.
Thanks for looking at this.
What about 'extending' Neutron's response with more data from other API calls (e.g. Other Neutron API calls, or even Nova)? Unless there's a requirement that there has to be a 1:1 mapping from the commands to the API.
To be specific,
As you showed, if Neutron is available then we are making a request to developer. openstack. org/api- ref-networking- v2-ext. html#listFloati ngIps
http://
Can we, say, take that response and 'join' it with Nova's response as well[1]? That way you get the Pool Names as well, you could even make the requests in parallel.
[1]: http:// developer. openstack. org/api- ref-compute- v2.1.html# listfloatingips Object
Another alternative is to request the details of each floating ip (I'm not sure if it can be batched in a single request) and then add the floating_network_id to each floating_ip output row.