Re: [jclouds-site] Added Google Analytics and removed old site docs (887453c)

@everett-toews: Hadn't you already added something regarding Google Analytics to the site? I could be confusing things... --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/commit/887453cd8a677b3d8330c6d7287f9e92a82e71c8#commitcomment-5506696

Re: [jclouds-labs-openstack] Adds support for multi-region implementation of Rackspace Cloud Files API (#79)

> + > +import com.google.common.base.Function; > +import com.google.common.base.Supplier; > + > +/** > + * @author Jeremy Daggett > + */ > +@Singleton > +public class RegionToCDNEndpoint implements Function { > + > + private final Supplier>> endpointsSupplier; > + > + @Inject > + public Regi

Re: [jclouds-labs-openstack] Adds support for multi-region implementation of Rackspace Cloud Files API (#79)

[jclouds-labs-openstack-pull-requests #167](https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack-pull-requests/167/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/79#issuecomment-36197272

Re: [jclouds-labs-openstack] Adds support for multi-region implementation of Rackspace Cloud Files API (#79)

[jclouds » jclouds-labs-openstack #873](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-openstack/873/) SUCCESS This pull request looks good [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.com/jcloud

Re: [jclouds-labs-openstack] Adds support for multi-region implementation of Rackspace Cloud Files API (#79)

[jclouds-labs-openstack-pull-requests #166](https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack-pull-requests/166/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/79#issuecomment-36195691

Re: [jclouds-labs-openstack] Adds support for multi-region implementation of Rackspace Cloud Files API (#79)

[jclouds » jclouds-labs-openstack #872](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-openstack/872/) SUCCESS This pull request looks good [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.com/jcloud

Re: [jclouds-labs-openstack] Adds support for multi-region implementation of Rackspace Cloud Files API (#79)

> + public CDNContainer(String name, boolean enabled, boolean logRetention, > int ttl, URI uri, URI sslUri, URI streamingUri, URI iosUri) { > + this.name = checkNotNull(name, "name required"); > + this.enabled = enabled; > + this.logRetention = logRetention; > + this.ttl = tt

Re: [jclouds-site] Rebranding proposal (#58)

Go to http://ad45a6d358f43958e25a-1b323d3a83db100c58eca5c5f5e6a3c4.r84.cf1.rackcdn.com/ to review your changes. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36179544

Re: [jclouds-site] Rebranding proposal (#58)

[jclouds-site-pull-requests #195](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/195/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36179288

Re: [jclouds] JCLOUDS-453. Add OpenStack Keystone v2.0 OS-KSADM Admin Extension support (#303)

I've executed the live tests against a devstack havana and all the added live tests passed. Great job @pnavarro! Once the typo in the skip exception is fixed, I think this PR is good to merge. @everett-toews Do you think this PR should supersede https://github.com/jclouds/jclouds/issues/290? -

Re: [jclouds] JCLOUDS-453. Add OpenStack Keystone v2.0 OS-KSADM Admin Extension support (#303)

> + * @author Pedro Navarro > + */ > +@Test(groups = "live", testName = "RoleAdminApiLiveTest", singleThreaded = > true) > +public class RoleAdminApiLiveTest extends BaseKeystoneApiLiveTest { > + > + private Optional roleAdminOption; > + > + private Role testRole; > + > + @BeforeClass(groups

Re: [jclouds] Update README.md (#304)

> Is there an easy way of squashing on github without forcing me to clone the > repo? You should be able to do this by [rebasing locally](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html) and then force pushing to your repo. But there's no need to spend too much time

Re: [jclouds] Update README.md (#304)

Is there an easy way of squashing on github without forcing me to clone the repo? On Wed, Feb 26, 2014 at 6:53 PM, BuildHive wrote: > jclouds >> jclouds > #868SUCCESS > > This pull request looks good > (what's this?)

Re: [jclouds] Update README.md (#304)

[jclouds » jclouds #868](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/868/) SUCCESS This pull request looks good [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/304#issuecomment

Re: [jclouds] Update README.md (#304)

[jclouds-pull-requests #622](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/622/) UNSTABLE Looks like there's a problem with this pull request --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/304#issuecomment-36151269

Re: [jclouds] Update README.md (#304)

[jclouds-java-7-pull-requests #1092](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1092/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/304#issuecomment-36151305

Re: [jclouds] Update README.md (#304)

[jclouds-java-7-pull-requests #1091](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1091/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/304#issuecomment-36151180

Re: [jclouds] Update README.md (#304)

[jclouds-pull-requests #621](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/621/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/304#issuecomment-36151165

Re: [jclouds] Update README.md (#304)

Thanks, @johnbendi? Could you squash down your three commits? Otherwise, +1 - looks good to me! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/304#issuecomment-36150066

Re: [jclouds] Update README.md (#304)

[jclouds » jclouds #867](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/867/) SUCCESS This pull request looks good [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/304#issuecomment

Re: [jclouds] Update README.md (#304)

@demobox I have updated with your proposals. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/304#issuecomment-36144908

Re: [jclouds] Update README.md (#304)

[jclouds-java-7-pull-requests #1090](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1090/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/304#issuecomment-36143183

Re: [jclouds] Update README.md (#304)

[jclouds-pull-requests #620](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/620/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/304#issuecomment-36143141

Re: [jclouds] Update README.md (#304)

[jclouds » jclouds #866](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/866/) SUCCESS This pull request looks good [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/304#issuecomment

Re: [jclouds] Update README.md (#304)

Thanks, @johnbendi! Just a couple of comments... --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/304#issuecomment-36141357

Re: [jclouds] Update README.md (#304)

> @@ -12,7 +12,7 @@ Features > Even if you don't need the portable apis we provide, or could roll it your > own, programming against cloud environments can be challenging. We focus on > the following areas so that you can focus on using the cloud, rather than > troubleshooting it! > > * SIMP

Re: [jclouds] Update README.md (#304)

> @@ -1,7 +1,7 @@ > jclouds > == > jclouds allows provisioning and control of cloud resources, including > blobstore > -and compute, from Java and Clojure. Our API gives allows developers to use > +and compute, from Java and Clojure. Our API gives/allows developers the > opportunity to u

Re: [jclouds-site] Rebranding proposal (#58)

> but Akka defines itself as a toolkit too Ah...interesting data point. Thanks! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36140965

Re: [jclouds] Update README.md (#304)

Made corrections for clarity of message. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/304#issuecomment-36135990

[jclouds] Update README.md (#304)

You can merge this Pull Request by running: git pull https://github.com/johnbendi/jclouds patch-1 Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds/pull/304 -- Commit Summary -- * Update README.md -- File Changes -- M README.md (4) -- Patch

Re: [jclouds-site] Rebranding proposal (#58)

In terms of ranking I think people search for things like "digitalocean java api", "s3 java", etc. But I'm not sure how people search for this kind of thing: perhaps "portable" isn't also relevant in searches… I just don't know, and would also like to have feedback from more people on this :) J

Re: [jclouds-site] Rebranding proposal (#58)

> I think toolkit is a better name I'd be curious to hear what others have to say on this. I agree that jclouds does quite a lot of things, but I wonder if there is any kind of precedence for calling what we do a "toolkit". E.g. in terms of search rankings, do we think people are likely to sear

Re: [jclouds] JCLOUDS-453. Add OpenStack Keystone v2.0 OS-KSADM Admin Extension support (#303)

[jclouds-pull-requests #619](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/619/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/303#issuecomment-36131684

Re: [jclouds] JCLOUDS-453. Add OpenStack Keystone v2.0 OS-KSADM Admin Extension support (#303)

[jclouds-java-7-pull-requests #1089](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1089/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/303#issuecomment-36131730

Re: [jclouds] JCLOUDS-453. Add OpenStack Keystone v2.0 OS-KSADM Admin Extension support (#303)

[jclouds » jclouds #865](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/865/) SUCCESS This pull request looks good [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/303#issuecomment

Re: [jclouds-site] Rebranding proposal (#58)

Go to http://3c529895763ecb8a8cf5-8b5ff73a2fe803863960f0ac1c5775da.r50.cf1.rackcdn.com/ to review your changes. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36116484

Re: [jclouds-site] Rebranding proposal (#58)

[jclouds-site-pull-requests #194](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/194/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36116316

Re: [jclouds] JCLOUDS-453. Add OpenStack Keystone v2.0 OS-KSADM Admin Extension support (#303)

Thanks for the quick update! I'll run the live tests against a devstack later today, but apart from the minor comments, in general it LGTM. Just an advice: when committing changes that address review comments, don't squash the commits, until the PR is ready to be merged. This way we can focus o

Re: [jclouds-site] Rebranding proposal (#58)

Go to http://11e1685771642b44f348-bb0388ed1166b0878c4afb3f7cef0832.r62.cf1.rackcdn.com/ to review your changes. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36114773

Re: [jclouds-site] Rebranding proposal (#58)

[jclouds-site-pull-requests #193](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/193/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36114464

Re: [jclouds-site] Rebranding proposal (#58)

Go to http://10720684367b760da111-612fee7537882e5d5391dafbf9b878ad.r97.cf1.rackcdn.com/ to review your changes. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36113179

Re: [jclouds-site] Rebranding proposal (#58)

[jclouds-site-pull-requests #192](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/192/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36113017

Re: [jclouds-site] Rebranding proposal (#58)

We should also write a blog post announcing the "new year changes": new site, 1.7.0 (with all its stuff) and 1.7.1, and ideally should be published along with the new site, to properly announce it. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pul

Re: [jclouds-site] Rebranding proposal (#58)

Thinking more about it, I think *toolkit* is a better name. jclouds is not just a library, is a set of libraries that can be used to manage the cloud, so I think *toolkit* defines better what jclouds is. I've just uploaded a commit with the slogan changed in the main page, and also rebranded th

Re: [jclouds] Refactor SoftLayer CCI support (#296)

Hi Ignasi, I think you are right, a little of context could definitely ease the review. Recently I've been working with SoftLayer and I tried to fix some blocking issue (PR#200, PR#204) but unfortunately they didn't fix them all. In particular VirtualGuestToNodeMetadata happens to be slow and bug