deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ruben S. Montero" <>
Subject Re: Poor performance with open nebula driver
Date Wed, 04 Jul 2012 09:56:07 GMT

Do you mean back-porting the verbose option to OpenNebula 3.2? In this
line, we plan for our short roadmap to include a version API call so
clients can get the version of the server and adapt themselves to it.

BTW, in  we only support the last stable release, and
encourage people to upgrade. The next stable release (3.6) is scheduled for
next week. This will make OpenNebula 3.2 two versions behind the last
stable. So I think we could just update the driver to use verbose mode, and
throw an exception if the call is not supported.



On Tue, Jul 3, 2012 at 1:40 PM, David Lutterkort <> wrote:

> On Fri, 2012-06-29 at 10:19 +0200, Daniel Molina wrote:
> > In OpenNebula 3.2 when you retrieve the pool of instances through OCCI
> > no extended information is included, hence you have to do one more
> > request per instance to retrieve this information. In OpenNebula 3.4 a
> > verbose option was included for OCCI pools. You can use GET
> > /compute?verbose=true instead of GET /compute and the pool will
> > contain extended information for each element.
> Should this patch be committed ? It seems we'd want the drive rto
> discover whether the ON installation supports the verbose param or not
> and then act accordingly. Is that possible ?
> David

Ruben S. Montero, PhD
Project co-Lead and Chief Architect
OpenNebula - The Open Source Solution for Data Center Virtualization | | @OpenNebula

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message