Rick, thank you for your interest. jclouds has a compute provider for GCE which David Alves started and Andrew Bayer has worked on. This provider has seen some use, although still needs some work, and Andrew Bayer had some criticisms of the authentication code.
jclouds lacks a storage provider for GCS which we track in JIRA: https://issues.apache.org/jira/browse/JCLOUDS-458 Presently we recommend the GCS-S3 compatible API which has several drawbacks: http://jclouds.apache.org/documentation/userguide/using-s3/ Two students have expressed interest in working on this in the context of Google Summer of Code, although official contributions from Google would give us more confidence in the path forward. For example, Google deprecated the XML API long ago, but still considers the JSON API experimental. jclouds also has some support for Google App Engine, although I cannot comment on its state. On Tue, Mar 04, 2014 at 11:39:06AM -0800, Rick Wright wrote: > Hi all, > We are looking into ways that we can contribute to the Google provider code > and wanted to know what would be the most useful things we could do to > improve it. Is there functionality that is needed, tests that need to be > written/improved or documentation that needs to be updated? > > We are happy to contribute random fixes/improvements, but if there are > specific things that would be more useful it would probably make sense to > focus on those. > > Thanks for any input that you have, > Rick Wright > @wrigri on github -- Andrew Gaul http://gaul.org/
