[jclouds/jclouds] Move Digital Ocean rate limit handler to core to make it reusable (#1023)

The way to deal with rate limits is very similar in every provider. One just needs to read from the response how much to wait until new requests can be made, and wait accordingly. This change generalises the digitalocean2 rate limit handler so it can be reused and configured by all providers.

Re: [jclouds/jclouds-labs] JCLOUDS-1183 - oneandone-monitoringcenter-api (#322)

@nacx Could we close [this ](https://github.com/jclouds/jclouds-labs/pull/325) one first, i would need to merge it with this one, we've talked about this above. Thanks -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Jenkins build is back to normal : jclouds-guava-guice-compat » 17.0,4.0,OpenJDK 7 (latest) #211

See

Re: [jclouds/jclouds-labs] JCLOUDS-1183 - oneandone-monitoringcenter-api (#322)

I'm not sure why the checks fail, but a local build succeeds. Mind squashing and rebasing so I can cleanly merge it? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [jclouds/jclouds] Log information according to the auth precedence (#1022)

Closed #1022. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/1022#event-828712661

Re: [jclouds/jclouds] Log information according to the auth precedence (#1022)

Merged to master as [edbb2c0e](http://git-wip-us.apache.org/repos/asf/jclouds/commit/edbb2c0e). -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/1022#issuecomment-254752032

[jclouds/jclouds] Log information according to the auth precedence (#1022)

This basically changes the `toString()` method of the SSH connection classes so it matches the order in which credentials are taken into account: first public key, then password. Otherwise, if the user set both, the public key was used to authenticate, but a "password based auth" was printed to

Re: [jclouds/jclouds] JCLOUDS-1161: Make AWSS3BlobRequestSignerV4 the default signer. (#1008)

>Is this change going to be included in jclouds 2.0 Yes! -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/1008#issuecomment-254735506