<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">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.<br>
<br>
-David<br>
<br>
On 07/01/2013 10:23 AM, Mauro S M Rodrigues wrote:<br>
</div>
<blockquote cite="mid:51D190CB.6000100@linux.vnet.ibm.com"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">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.<br>
<br>
So anyone using it? There are a good reason to keep it? Did I
miss something about this extension?<br>
<br>
On 06/28/2013 09:31 AM, Christopher Yeoh wrote:<br>
</div>
<blockquote
cite="mid:CANCY3edbUN8WuUVYc81+cC=juiYFQbakQ9uxAs11y59JZ-x1hA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>Hi,<br>
<br>
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!<br>
<br>
<div class="" id="magicdomid179"><span class="">baremetal_nodes.p</span><span
class="">y</span></div>
<div class="" id="magicdomid75"><span class="">os_networks.py</span></div>
<div class="" id="magicdomid76"><span class="">networks_associate.py</span></div>
<div class="" id="magicdomid77"><span class="">os_tenant_networks.py</span></div>
<div class="" id="magicdomid78"><span class="">virtual_interfaces.py</span></div>
<div class="" id="magicdomid79"><span class="">createserverext.py</span><span
class=""></span></div>
<div class="" id="magicdomid132"><span class="">floating_ip_dns.py</span></div>
<div class="" id="magicdomid135"><span class="">floating_ip_pools.py</span><span
class=""></span></div>
<div class="" id="magicdomid136"><span class="">floating_ips_bulk.py</span></div>
<div class="" id="magicdomid138"><span class="">floating_ips.py</span></div>
<div class="" id="magicdomid139">cloudpipe.py</div>
<span class=""></span>
<div class="" id="magicdomid83"><span class="">cloudpipe_update.py</span></div>
<div class="" id="magicdomid84"><span class="">volumes.py</span></div>
<div class="" id="magicdomid85"><br>
</div>
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.<br>
<br>
</div>
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:<br>
<br>
<a moz-do-not-send="true"
href="https://etherpad.openstack.org/NovaV3ExtensionPortWorkList">https://etherpad.openstack.org/NovaV3ExtensionPortWorkList</a><br>
<br>
</div>
I've tried to keep track of new API extensions to make sure
we do v3 ports but may have missed some.<br>
<br>
</div>
Chris<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>