Why does getting the instance id require the API to block?  I can create 1 or 
1000 UUIDs in order (1) time in the API server and hand back 1000 instance ids 
in a list of <server> entries in the same amount of time.  I'm more concerned 
about an external user hitting the API server 1000 times to generate a 1000 
instance request, then hitting the API server 1000 more times to check the 
status until a 1000 instances return "running".  That's a lot of socket 
connections.

The SeverDetailsResponse isn't a list?  You can't just return:
<server>
...
</server>
<server>
...
</server>
<server>
...
</server>


Brian Schott, CTO
Nimbis Services, Inc.
brian.sch...@nimbisservices.com





On May 23, 2011, at 11:52 AM, Ed Leafe wrote:

> On May 23, 2011, at 11:41 AM, Jorge Williams wrote:
> 
>> I don't see how that peculates anything.  Treat the instance id as the 
>> reservation id on single instance creations -- have a separate reservation 
>> id when launching multiple instances.  End of the day even if you have the 
>> capability to launch multiple instances at once you should be able to poll a 
>> specific instance for changes.  
> 
> 
>       I'm not too crazy about an API call returning one thing (instance ID) 
> for one call, and a different thing (reservation ID) for the same call, with 
> the only difference being the value of one parameter. Do we do anything like 
> that anywhere else in the API?
> 
>       Also, with distributed zones, getting an instance ID requires the api 
> to block until the host selection can be completed, and the host's zone 
> database updated with the new instance information. Granted, that's not an 
> agonizingly slow or expensive operation even if it does involve several 
> inter-zone HTTP calls, but it isn't the cleanest and most scalable design IMO.
> 
> 
> -- Ed Leafe
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Reply via email to