> [Snip summary] > > The only question that needs to be considered is where do we move > from here? Do we accept the limitation that the EC2 API and any tool > which relies upon that will be only available for single-zone > deployments, and if you want distributed zones, you must use the OS > API?
Up to now, I have assumed that zones would be used as the construct that isolated different service offerings, e.g. VMware vs XenServer or 10G networking versus 1G, or whatever. Zones therefore play two roles: they give you the architecture for large-scale deployments, and they also allow for distinguished service offerings. Are you thinking along these lines? If so, then I would say that your proposed limitation above is not acceptable. We don't want a situation where tenants have to stop using the EC2 API as soon as their service provider wants to offer a rich set of offerings. Cheers, Ewan. _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
