[openstack-dev] [Nova] [Horizon] Insufficient (?) features in current Nova API
tsufiev at mirantis.com
Fri Apr 10 07:19:58 UTC 2015
Chris, thank you for clearly rephrasing me. Yes, that is exactly what I
On Fri, Apr 10, 2015 at 9:51 AM, Chris Friesen <chris.friesen at windriver.com>
> On 04/09/2015 10:13 PM, Monty Taylor wrote:
>> On 04/09/2015 02:40 PM, Timur Sufiev wrote:
>>> While analyzing Horizon behavior on a large scale we faced some
>>> issues which are most probably caused by inefficient calls to Nova API
>>> Horizon, more specifically described at
>>> Since my knowledge of Nova existing APIs is not very comprehensive I am
>>> quite sure whether current Nova API indeed doesn't support requesting the
>>> details of a multiple instances limited by their <instance_id>-s (passed
>>> part of `search_opts` parameter) or I just failed to find the proper REST
>>> call at http://developer.openstack.org/api-ref-compute-v2.1.html
>>> Nova developers, could you please help me on that matter?
>> I recommend not trying to do any of that - but instead doing a 'list' to
>> get the entire set of data and then filtering out the things you don't
>> want client side.
> The current code does what you recommend, but as mentioned in the bug
> report listed above they've run into performance issues.
> They want to show the names for instances that cinder volumes are attached
> to, or that have floating IP addresses. Currently the retrieve the entire
> list of instances in order to get the names of the (potentially much
> smaller) set of instances that they actually care about.
> If there was a "give me info on these specific instances" command in the
> nova API the above scenarios would be more efficient.
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev