[openstack-dev] [nova] Nova API extensions NOT to be ported to v3
dkranz at redhat.com
Mon Jul 1 14:55:11 UTC 2013
I have used it. In the case where large numbers of instances are to be
created, it (in theory) allows the compute system to optimize the
request. It also avoids rate limit and other such issues that could come
from hundreds of calls to create a server in sequence.
On 07/01/2013 10:23 AM, Mauro S M Rodrigues wrote:
> One more though, about os-multiple-create: I was also thinking to
> remove it, I don't see any real advantage to use it since it doesn't
> offer any kind of flexibility like chose different flavors, images and
> other attributes. So anyone creating multiple servers would probably
> prefer an external automation tool instead of multiple server IMHO.
> So anyone using it? There are a good reason to keep it? Did I miss
> something about this extension?
> On 06/28/2013 09:31 AM, Christopher Yeoh wrote:
>> The following is a list of API extensions for which there are no
>> plans to port. Please shout if you think any of them needs to be!
>> Also I'd like to propose that after H2 any new API extension
>> submitted HAS to have a v3 version. That will give us enough time to
>> ensure that the V3 API in Havana can do everything that the V2 one
>> except where we explicitly don't want to support something.
>> For developers who have had new API extensions merged in H2 but
>> haven't submitted a v3 version, I'd appreciate it if you could check
>> the following etherpad to see if your extension is on the list and
>> put it on there ASAP if it isn't there already:
>> I've tried to keep track of new API extensions to make sure we do v3
>> ports but may have missed some.
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev