On Jul 11, 2011, at 6:19 PM, Ewan Mellor wrote:
>> [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? > Note that we aren't using zones this way: we're assuming that there can be different kinds of service offerings within a single zone (For example, we have a single zone that contains multiple machine architectures). Lorin -- Lorin Hochstein, Computer Scientist USC Information Sciences Institute 703.812.3710 http://www.east.isi.edu/~lorin _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
