Craig McClanahan
|
Posted: September 09, 2009 21:37 by Craig McClanahan
|
|
In conversations with various folks implementing the Sun Cloud API, a recurrent request has been to support a way to request that cloud resources be allocated in a specific geographic location (such as a particular data center), in order to optimize access to those resources from the Internet, and/or to minimize network latencies between cloud resources by co-locating them. This message is a proposal for adding this capability to the Sun Cloud API. The proposed changes are: * Add a new "Location" resource model, with "name", "uri", and "description" fields. * In the "Cloud" resource model, add a "locations" field, which will return an array of Location resources for the various locations supported by this service implementation. * In the "VDC" resource model, add a "location" field, which contains the URI of the location in which this VDC, and all its contained resources, will be allocated. If an updated version of the API supports a "Create VDC" function, the location URI would be included in the incoming VDC representation to select the desired location. If the value were not included, the service implementation would select a default location. Treating a VDC as the finest grained resource that can be geographically located (versus perhaps a Cluster or a VM) seems to make the most sense, given technical limitations around implementing VNets -- which, since they can span clusters, would need to extend outside the bounds of a data center if two clusters that were part of the same VDC were in different locations. Craig |
Proposal: Adding Location Affinity to the Sun Cloud API
29 topics, 131 posts
» Share this
Replies: 1 - Last Post: September 10, 2009 20:02
by: jxstanford
by: jxstanford
showing 1 - 2 of 2
jxstanford
|
Posted: September 10, 2009 20:02 by jxstanford
|
|
I generally think this is a good idea. Not sure if "datacenter" is the right level of abstraction, but definitely some sort of geo support. This may help solve regulatory and compliance issues in some cases. The one concern would be ensuring that reasonable decisions were made about the proximity of storage and compute. I'm not sure I would want my cloud storage in EU and compute in US, but this is probably more of a policy and/or tooling issue and less of an API issue. John |
Replies: 1 - Last Post: September 10, 2009 20:02
by: jxstanford
by: jxstanford
