Google Compute Engine API front-end to CloudStack

[Chiradeep Vittal <Ch...@citrix.com>]

Along the lines of the AWS API front-end to CloudStack, would anybody be interested in developing the GCE front-end? The GCE API [1] is quite elementary — the most complex piece would be adding an OAuth2 server and integrate that with CloudStack's API key management.

GCE maps to basic zone: the mapping between GCE concepts and CloudStack resources are:

Network == Security Group
Firewall == Ingress Rule
Image == Template
Instance == Vm / Instance
Project == Account (or Project)
Zone == Zone
Disk == Volume
User == User (or Account depending on how Project is mapped)
Machinetype == service offering

[1]https://developers.google.com/compute/
--
Chiradeep

Re: Google Compute Engine API front-end to CloudStack

[Adrian Cole <ad...@jclouds.org>]

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.Vittal@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
>> ><ge...@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
>>
>>

Re: Google Compute Engine API front-end to CloudStack

[David Chamard <da...@cloud.ca>]

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.Vittal@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
> ><ge...@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
>
>

Re: Google Compute Engine API front-end to CloudStack

[Chiradeep Vittal <Ch...@citrix.com>]

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
><ge...@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

Re: Google Compute Engine API front-end to CloudStack

[David Nalley <da...@gnsa.us>]

On Fri, Jun 29, 2012 at 8:01 PM, George Reese
<ge...@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

Re: Google Compute Engine API front-end to CloudStack

[George Reese <ge...@enstratus.com>]

One has an AWS API to take advantage of the AWS ecosystem. No Google
ecosystem exists.

Sent from my iPhone

On Jun 29, 2012, at 18:59, Chiradeep Vittal <Ch...@citrix.com> wrote:

> Along the lines of the AWS API front-end to CloudStack, would anybody be interested in developing the GCE front-end? The GCE API [1] is quite elementary — the most complex piece would be adding an OAuth2 server and integrate that with CloudStack's API key management.
>
> GCE maps to basic zone: the mapping between GCE concepts and CloudStack resources are:
>
> Network == Security Group
> Firewall == Ingress Rule
> Image == Template
> Instance == Vm / Instance
> Project == Account (or Project)
> Zone == Zone
> Disk == Volume
> User == User (or Account depending on how Project is mapped)
> Machinetype == service offering
>
> [1]https://developers.google.com/compute/
> --
> Chiradeep