introduce initial, unit tested google cloud platform element set

This is the minimum needed for my codelab (compute engine is the first and only cloud product supported, and only part of GCE at that) but I think it also builds a decent starting point for cloud polymer components. I defined a naming convention for elements and files to hopefully avoid a proliferation of confusing and inconsistent names used across the many cloud products.
Understood on the crunch :)
On Jun 19, 2014 6:35 AM, "Marc Cohen" <notifications@github.com> wrote:

> In gcloud-compute.html:
>
> > +
> > +##### Example
> > +
> > +    <gcloud-gapi ...></gcloud-gapi>
> > +    <gcloud-config ...></gcloud-config>
> > +    <gcloud-compute-instance id="my-vm">my-vm
> > +    </gcloud-compute-disk>
> > +
> > +@element gcloud-compute-instance
> > +@blurb gcloud-compute-instance creates a Compute Engine VM
> > +@status alpha
> > +@url https://github.com/GoogleWebComponents/google-gcloud
> > +-->
> > +
> > +<polymer-element name="gcloud-compute-instance"
> > +  attributes="name zone netName diskName diskType diskBoot diskAutodel diskSize diskImage"
>
> I like the current attribs for the boot disk because it provides easier
> usability but I'd also like to add a disk object for power users. Beyond
> that, one can start a VM with auxiliary disks beyond the boot drive, and
> there's no way to express that with my current attribute set. Having the
> disk attributes be a "disks" (plural) attrib, which takes an array of json
> objects would be very powerful. I'll add an issue to do that but don't want
> to try to sweep that in now as I'm crunching this for next week's codelab.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/GoogleWebComponents/google-gcloud/pull/1/files#r13967425>
> .
>