On 07/01/13 at 11:23am, 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?
I would like to see this extension go away, but only by a small margin.
Just because it complicates the boot/spawn workflow a bit, which really
isn't a big deal.
As far as I understand it the benefit is that if you have a use case for
booting large numbers of the same type of instance then this extension
allows it to happen faster by sending all of the information to the
scheduler in one message. I don't know how useful this actually is in
practice, but I could see it being helpful for someone.
On 06/28/2013 09:31 AM, Christopher Yeoh wrote:
Hi,
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!
baremetal_nodes.py
os_networks.py
networks_associate.py
os_tenant_networks.py
virtual_interfaces.py
createserverext.py
floating_ip_dns.py
floating_ip_pools.py
floating_ips_bulk.py
floating_ips.py
cloudpipe.py
cloudpipe_update.py
volumes.py
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:
https://etherpad.openstack.org/NovaV3ExtensionPortWorkList
I've tried to keep track of new API extensions to make sure we do
v3 ports but may have missed some.
Chris
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
