I am trying to reach out by email. But my email got bounced back.
I have filed a launchpad issue 1503462. This is now marked as duplicate of 1457986.
I am glad to see there are more parties that are interested in this feature. I would like to see how we can coordinate the effort on this feature.
We have two use-cases for this feature:
1. To assist nova to select a network when creating a new VM instance.
For this use-case, we like to have a tenant-id in GET request and get ip-margins for all the networks belong to the network.
2. To provide information to monitor tools to show the capacities on dash-board.
For this use-case, we need to return network name in the response.
So ideally, we would like to have the following REST API:
GET on /v2.0/<tenant-id>, the returned data is in the form of
{ "network-1-uuid": { "total-ips" : 256 "available-ips" : count1, "name" : test-network, }
}
We also have the implementation and accompanying tempest test scripts.
I am curious to see where we are on this issue. Is the draft REST API ready? Can we incorporate my use-case input into the considerations.
<email address hidden>
I am trying to reach out by email. But my email got bounced back.
I have filed a launchpad issue 1503462. This is now marked as duplicate of 1457986.
I am glad to see there are more parties that are interested in this feature. I would like to see how we can coordinate the effort on this feature.
We have two use-cases for this feature:
1. To assist nova to select a network when creating a new VM instance.
For this use-case, we like to have a tenant-id in GET request and get ip-margins for all the networks belong to the network.
2. To provide information to monitor tools to show the capacities on dash-board.
For this use-case, we need to return network name in the response.
So ideally, we would like to have the following REST API:
GET on /v2.0/<tenant-id>, the returned data is in the form of
{ "network-1-uuid": { "total-ips" : 256
"available- ips" : count1,
"name" : test-network,
}
}
We also have the implementation and accompanying tempest test scripts.
I am curious to see where we are on this issue. Is the draft REST API ready? Can we incorporate my use-case input into the considerations.
<email address hidden>