More inline,
Salvatore
On 20 January 2016 at 16:51, Shraddha Pandhe
wrote:
> Thank you all for the comments.
>
> The client that we expect to call this API with thousands of network-ids
> is nova-scheduler.
>
> Since this call is happening in the middle of
Thank you all for the comments.
The client that we expect to call this API with thousands of network-ids is
nova-scheduler.
Since this call is happening in the middle of scheduling, we don't want to
spend time in paginating or sending multiple requests. I have tens of
thousands of networks and
So having a URI too long error is, in this case, likely an indication
that you're requesting too many things at once.
You could:
1. Request 100 at a time in parallel
2. Find a query that would give you all those networks & page through
the reply
3. Page through all the user's networks and
I tend to agree with Doug and Ryan's stance. If you need to pass 1000s of
network-id on a single request you're probably not doing things right on
the client side.
As Ryan suggested you can try and split the request in multiple requests
with acceptable URI lenght and send them in parallel; this
Hi Doug,
What would be the reason for such timeout? Based on my current test, it
doesn't take more than few hundreds of milliseconds to return.
What I am trying to do is,
I have a Neutron extension that returns IP usage per subnet per network. It
needs to support:
1. Return usage info for all
Hi folks,
I am writing a Neutron extension which needs to take 1000s of network-ids
as argument for filtering. The CURL call is as follows:
curl -i -X GET
'http://hostname:port/neutron/v2.0/extension_name.json?net-id=fffecbd1-0f6d-4f02-aee7-ca62094830f5=fffeee07-4f94-4cff-bf8e-a2aa7be59e2e'
-H
It would have to be a POST, but even that will start to have timeout issues. An
API which requires that kind of input is kind of a bad idea. Perhaps you could
describe what you’re trying to do?
Thanks,
doug
> On Jan 19, 2016, at 4:59 PM, Shraddha Pandhe
> wrote: