+1 On May 23, 2011, at 11:54 AM, Vishvananda Ishaya wrote:
> So I think we've identified the real problem... > > :) > > sounds like we really need to do the UUID switchover to optimize here. > > Vish > > On May 23, 2011, at 9:42 AM, Jay Pipes wrote: > >> On Mon, May 23, 2011 at 12:33 PM, Brian Schott >> <brian.sch...@nimbisservices.com> wrote: >>> 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. >> >> Instance IDs aren't currently UUIDs :) They are auto-increment >> integers that are local to the zone database. And because they are >> currently assigned by the zone, the work of identifying the >> appropriate zone to place a requested instance in would need to be a >> synchronous operation (you can't have the instance ID until you find >> the zone to put it in). >> >> -jay >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~openstack >> Post to : openstack@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
