I can see two sides to this: 1. it is a distraction: GCE especially an inexperienced api, when we know all new apis change (v1beta12 anyone?) While fun, it implies coding to another spec outside our control (ala) EC2, and implies setting up an OAUTH 2 layer. esp as the current EC2 api isn't 100% yet, nor one's ability to easily build or run it, I can see adding another api layer as a distraction and involve maintenance while GCE grows up. 2. field of dreams.. if we build it, they will come! Actually I don't buy into this at all, but maybe somebody has evidence of this ever working out.
-A On Fri, Jun 29, 2012 at 5:18 PM, David Chamard <da...@cloud.ca> wrote: > I think that google (specially google app engine) has a big developer base > that will try/use GCE in the short term. > A few 3rd party tools already announced compatibility with GCE. > It could be another crowd that will use Cloudstack. > > David > > > On Fri, Jun 29, 2012 at 8:15 PM, Chiradeep Vittal < > chiradeep.vit...@citrix.com> wrote: > >> If I was new to CloudStack / IAAS cloud, it would be a learning experience >> to map concepts from one cloud implementation to another. See if the >> abstractions in CloudStack are abstract enough or perhaps they need more >> refinement. >> It could attract more folks (GOOG fans) to the CloudStack community. >> >> >> On 6/29/12 5:04 PM, "David Nalley" <da...@gnsa.us> wrote: >> >> >On Fri, Jun 29, 2012 at 8:01 PM, George Reese >> ><george.re...@enstratus.com> wrote: >> >> One has an AWS API to take advantage of the AWS ecosystem. No Google >> >> ecosystem exists. >> >> >> > >> >I agree. >> > >> >When/If GCE gets market traction, and the follow on ecosystem tools >> >perhaps it will be time to do it. Aside from that, what is the >> >benefit? (maybe I have missed one. >> > >> >--David >> >>
