Great news! Feel free to send a pull request to add the GCE examples to the repo and to fix the compute-basics. If possible, though, use jclouds 1.7.1 instead of 1.7.0, as it is the latest released version.
The document looks good to me too. If you want, you can also take a look at the provider specific guides [1] to see how they look like, and eventually send a PR to the site repo [2] to add the starter guide for GCE. Thanks for your effort! Ignasi [1] http://jclouds.apache.org/guides/ [2] https://github.com/jclouds/jclouds-site On 12 March 2014 09:55, Nirmal Fernando <nir...@wso2.com> wrote: > This is some great work Suriya! Thanks for your effort. I'm sure jclouds > community will incorporate your fixes and excellent documentation. > > > On Wed, Mar 12, 2014 at 2:18 PM, Sathyasuriya Priya > <sathyasur...@gmail.com>wrote: > >> Thanks Ignasi >> osFamily(OsFamily.CENTOS) did the trick. I am able to add/remove/list >> nodes. >> Created JIRA issue [1] >> >> I have come up with following tutorial for newcomers on getting started >> with GCE. >> Pls take a look and provide comments on where it could be improved. >> >> https://docs.google.com/document/d/1hHB2Wm8ZNS9LaDs178Xn9YseaYiMMeh8Vx47-AqvsVI >> >> I also have a patch to compute-basics [2], such that it works with GCE. >> The changes are minimal: >> 1. Updating version in pom.xml to 1.7.0, add GCE dependencies. >> 2. Updating MainApp.java to support GCE >> 3. Added two commands listimages, listnodes to MainApp.java >> Let me know if I should raise a jira & pull request for it. >> >> [1] https://issues.apache.org/jira/browse/JCLOUDS-495 >> [2] https://github.com/jclouds/jclouds-examples >> >> Thanks >> >> >> On Tue, Mar 11, 2014 at 1:51 AM, Ignasi Barrera <ignasi.barr...@gmail.com >> >wrote: >> >> > Hi, >> > >> > If you don't specify any template details, jclouds will try to find an >> > image known to work in the provider. The predicate you are seeing is >> > the default one defined for the GCE provider [1], but it seems that >> > it's not the appropriate one. That predicate should always find a >> > usable template (at least one with SSH enabled). Mind opening a JIRA >> > [2] issue to fix this? >> > >> > You can build the example by providing custom values to the template >> > builder. The Chef examples do that [3]. You don't have to stick to the >> > provider's default template. You can build the examples by instructing >> > the templateBuilder to look for a template that will work nice with >> > the example. >> > >> > >> > >> > HTH! >> > >> > Ignasi >> > >> > >> > [1] >> > >> https://github.com/jclouds/jclouds-labs-google/blob/master/google-compute-engine/src/main/java/org/jclouds/googlecomputeengine/GoogleComputeEngineApiMetadata.java#L68-L69 >> > [2] https://issues.apache.org/jira/browse/JCLOUDS >> > [3] >> > >> https://github.com/jclouds/jclouds-examples/blob/master/chef-basics/src/main/java/org/apache/jclouds/examples/chef/basics/MainApp.java#L154 >> > >> > On 11 March 2014 09:35, Sathyasuriya Priya <sathyasur...@gmail.com> >> wrote: >> > > hi Ignasi, >> > > >> > > Just an update and clarification on creating an example project for >> GCE. >> > > I started with the compute-basics example project. One important change >> > > needed was to change the dependency versions to 1.7.1 in pom. >> > > >> > > I see that compute.listImages(), compute.listNodes() are working fine. >> > > However, compute.createNodesInGroup() is failing with below error. >> > > >> > >>> adding node to group mygroup >> > > error: no image matched predicate: >> > > >> > >> And(nullEqualToIsParentOrIsGrandparentOfCurrentLocation(),And(osFamily(gcel),osVersion(1[012].[01][04]))) >> > > >> > > I was thinking the issue is with compute.templateBuilder(). Any way to >> > > relax the predicate constraint ? >> > > I also tried to look into how live tests are able to create nodes in >> > > BaseComputeServiceLiveTest and see very similar code is being used. >> > > Any help/directions to look for is appreciated. >> > > >> > > [1] >> > > >> > >> https://github.com/jclouds/jclouds-examples/blob/master/compute-basics/pom.xml >> > > >> > > Thanks >> > > Suriya >> > > >> > > >> > > >> > > On Mon, Mar 10, 2014 at 4:30 AM, Andrea Turli <andrea.tu...@gmail.com >> > >wrote: >> > > >> > >> Hi Suriya, >> > >> >> > >> for "network operations quota exceeded" please look at your ' >> > >> https://console.developers.google.com/project/ >> > <PROJECT_ID>/compute/quotas' >> > >> and try to clean up networks before running the liveTests. >> > >> >> > >> Best, >> > >> Andrea >> > >> >> > >> >> > >> On Mon, Mar 10, 2014 at 12:22 PM, Ignasi Barrera >> > >> <ignasi.barr...@gmail.com>wrote: >> > >> >> > >> > Thanks for checking! >> > >> > >> > >> > If you are going to write something in you blog, that would be >> > excelent. >> > >> > Also, if you want to contribute your code examples to the >> > >> > jclouds-examples repo [1] or add a GCE starter guide to the main >> > >> > jclouds site [2], you're very welcome too! :) >> > >> > >> > >> > Just let us know if we can help! >> > >> > >> > >> > >> > >> > >> > >> > I. >> > >> > >> > >> > [1] https://github.com/jclouds/jclouds-examples >> > >> > [2] https://github.com/jclouds/jclouds-site/tree/master/guides >> > >> > >> > >> > On 10 March 2014 12:11, Sathyasuriya Priya <sathyasur...@gmail.com> >> > >> wrote: >> > >> > > Thanks Ignasi. >> > >> > > Yes, you are right. I don't need any changes to start using. >> > >> > > >> > >> > > I am able to run the live tests following below instructions [1], >> > [2]. >> > >> > > >> > >> > > I feel some steps are not clear(for a new jclouds/gce user), and >> > would >> > >> > like >> > >> > > to post my steps in a bit more detailed manner(may be in my blog). >> > >> > > >> > >> > > I will start looking at how to use in a separate example >> > >> > project(following >> > >> > > your suggestion [3]), and try to post them as well. >> > >> > > >> > >> > > In case if anybody is interested on result of my live tests: >> > >> > > Single OAuth live test passed: >> > >> > > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: >> > 3.573 >> > >> sec >> > >> > > >> > >> > > Some GCE live tests failed: >> > >> > > Tests run: 86, Failures: 2, Errors: 0, Skipped: 11 >> > >> > > >> > >> > > Looks to me failures are due to network operations quota exceeded. >> > >> > > >> > >> > > statusCode=403, message=FORBIDDEN, headers={}}, >> > operationType=insert, >> > >> > > errors=[Error{code=QUOTA_EXCEEDED, message=Quota 'NETWORKS' >> > exceeded. >> > >> > > Limit: 5.0}]} >> > >> > > >> > >> > > >> > >> > > [1] >> > >> > > >> > >> > >> > >> >> > >> https://github.com/jclouds/jclouds-labs-google/tree/master/google-compute-engine >> > >> > > [2] >> > https://github.com/jclouds/jclouds-labs-google/tree/master/oauth >> > >> > > [3] >> > http://www.mail-archive.com/dev@jclouds.apache.org/msg04369.html >> > >> > > >> > >> > > On Mon, Mar 10, 2014 at 1:36 AM, Ignasi Barrera < >> > >> > ignasi.barr...@gmail.com>wrote: >> > >> > > >> > >> > >> Hi Suriya, >> > >> > >> >> > >> > >> Despite being in a different "labs" repository, the GCE provider >> is >> > >> > >> also released as part of the regular release process. You'll find >> > the >> > >> > >> release artifacts in Maven Central [1], so you download or >> include >> > >> > >> them as a dependency where needed. Moving the provider to the >> main >> > >> > >> repository should not be a blocker for downstream projects, as >> > long as >> > >> > >> they can use the released artifacts. >> > >> > >> >> > >> > >> Creating the provider metadata class should be ideal, but I'm not >> > sure >> > >> > >> if it would be a must. A "provider" in jclouds is just an "api", >> > >> > >> exposed in a concrete location, with a set of defaults (check >> this >> > [2] >> > >> > >> core concept definition page). Many providers have common APIs >> > (think >> > >> > >> about OpenStack providers). While the API they expose is the same >> > >> > >> (nova, swift, etc), the endpoints where they expose the api and >> > some >> > >> > >> defaults change. That is what the provider metadata describes. >> > >> > >> >> > >> > >> Even though if there is no provider metadata describing a >> "concrete >> > >> > >> deployment of the api", you can still instanciate the provider, >> > using >> > >> > >> the ContextBuilder normally. >> > >> > >> You can use "google-compute-engine" as the provider id, and use >> the >> > >> > >> default endpoint, defined by the GoogleComputeEngineApiMetadata >> > [3]. >> > >> > >> If you have the provider dependency in your classpath, jclouds >> will >> > >> > >> find it and pick it up. >> > >> > >> >> > >> > >> >> > >> > >> >> > >> > >> So, taking into account these things (if I am not missing >> > something) >> > >> > >> you should be already able to use the GCE provider without having >> > to >> > >> > >> wait for those changes in the jclouds side. >> > >> > >> >> > >> > >> >> > >> > >> >> > >> > >> HTH! >> > >> > >> >> > >> > >> >> > >> > >> Ignasi >> > >> > >> >> > >> > >> >> > >> > >> [1] >> > >> > >> >> > >> > >> > >> >> > >> http://search.maven.org/#artifactdetails%7Corg.apache.jclouds.labs%7Cgoogle-compute-engine%7C1.7.1%7Cjar >> > >> > >> [2] http://wiki.apache.org/jclouds/Core%20Concepts >> > >> > >> [3] >> > >> > >> >> > >> > >> > >> >> > >> https://github.com/jclouds/jclouds-labs-google/blob/master/google-compute-engine/src/main/java/org/jclouds/googlecomputeengine/GoogleComputeEngineApiMetadata.java#L78-L85 >> > >> > >> >> > >> > >> On 10 March 2014 09:18, Sathyasuriya Priya < >> sathyasur...@gmail.com >> > > >> > >> > wrote: >> > >> > >> > Dear Jclouds developers, >> > >> > >> > >> > >> > >> > I am Suriyapriya Veluchamy, currently an MS CS student at NPU, >> > >> > Fremont, >> > >> > >> CA, >> > >> > >> > USA. >> > >> > >> > I am interested in the following GSOC project in Stratos. >> > >> > >> > https://issues.apache.org/jira/browse/STRATOS-480 >> > >> > >> > >> > >> > >> > I have some queries on the GCE support in jclouds, since this >> is >> > >> > needed >> > >> > >> for >> > >> > >> > Stratos to integrate with GCE. >> > >> > >> > https://github.com/jclouds/jclouds-labs-google >> > >> > >> > >> > >> > >> > I looked at a relevant email thread as well. >> > >> > >> > >> http://www.mail-archive.com/dev@jclouds.apache.org/msg04369.html >> > >> > >> > >> > >> > >> > I understand the following JIRA issue is for moving the >> separate >> > GCE >> > >> > >> > project to the core project. >> > >> > >> > https://issues.apache.org/jira/browse/JCLOUDS-172 >> > >> > >> > >> > >> > >> > I would like to understand the complexity of this work, based >> on >> > >> > which I >> > >> > >> > would decide whether it could be part of my gsoc work. I have >> > come >> > >> up >> > >> > >> with >> > >> > >> > list of todo items, based on my analysis. Pls correct me or add >> > >> other >> > >> > >> items >> > >> > >> > needed as well. >> > >> > >> > >> > >> > >> > 1. Create GCEProviderMetadata extending BaseProviderMetadata >> > >> (similar >> > >> > to >> > >> > >> > AWSEC2ProviderMetadata) - this is needed for >> > >> > >> > ContextBuilder.newBuilder(provider) to pick up GCE ? >> > >> > >> > 2. Move all the files (oauth, google-compute-engine) to >> > >> > >> > jclouds-providers-project. >> > >> > >> > 3. Hopefully, jclouds should pick up GCE as provider. Fix any >> > issues >> > >> > that >> > >> > >> > come up. >> > >> > >> > 4. Andrew Bayer's criticisms of OAuth code - I couldn't find >> the >> > >> > relevant >> > >> > >> > discussion/email related to this. Any idea if this is a >> critical >> > >> piece >> > >> > >> and >> > >> > >> > how much effort is needed to fix it. >> > >> > >> > >> > >> > >> > I am assuming other jclouds components are provider agnostic >> and >> > >> > >> shouldn't >> > >> > >> > break. Do you aware of any other code changes needed in other >> > >> > components. >> > >> > >> > >> > >> > >> > Also, I came across the GCE API java library from google. Any >> > idea >> > >> > why we >> > >> > >> > don't use it directly (instead rely on REST apis). May be for >> > OAuth >> > >> > >> support >> > >> > >> > alone we can make use of this ? >> > >> > >> > https://developers.google.com/compute/docs/api/api-lib/java >> > >> > >> > >> > >> > >> > I was able to build jclouds-labs-google and run unittests >> > >> > successfully. >> > >> > >> > I will try to work on an example to make use of this project >> and >> > >> will >> > >> > >> > update. >> > >> > >> > >> > >> > >> > Thanks >> > >> > >> > Suriya >> > >> > >> >> > >> > >> > >> >> > >> > > > > -- > > Thanks & regards, > Nirmal > > Senior Software Engineer- Platform Technologies Team, WSO2 Inc. > Mobile: +94715779733 > Blog: http://nirmalfdo.blogspot.com/
