Re: [jclouds/jclouds-site] Release notes for the 2.0.1 release (#195)

nacx commented on this pull request. > +## Credits + +jclouds would like to thank everyone who contributed time and effort in order to make this release happen: + +* [Svetoslav Neykov](https://github.com/neykov) for his support on the karaf integration and for having contributed teh Vagrant

Re: [jclouds/jclouds-site] Release notes for the 2.0.1 release (#195)

Go to http://f192800187877c28d77d-912ab9cfe4c8304192c331e3bef81678.r92.cf5.rackcdn.com/ to review your changes. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [jclouds/jclouds-site] Release notes for the 2.0.1 release (#195)

demobox commented on this pull request. > +## Credits + +jclouds would like to thank everyone who contributed time and effort in order to make this release happen: + +* [Svetoslav Neykov](https://github.com/neykov) for his support on the karaf integration and for having contributed teh

Re: [jclouds/jclouds-labs] Oneandone compute api (#338)

That's the problem. The `PROPERTY_MAX_RATE_LIMIT_WAIT` controls how much time you are willing to wait for a rate limited request to be retried. In OneAndOne, it seems that in most cases you'll have to wait, at least, one minute, so the value you are setting does not seem OK. You should set it

Re: [jclouds/jclouds-labs] Oneandone compute api (#338)

This is an example of the error i get, the problems is the flow breaks and tests fail, i have this property set `properties.put(PROPERTY_MAX_RATE_LIMIT_WAIT, 60 * 1000);` it is passed to rate limit class, one minute is the maximum time needed to wait for a new limit, i am not sure what is

Re: [jclouds/jclouds-site] Release notes for the 2.0.1 release (#195)

Go to http://18a1cfe8f7d9cd8a50b0-32b7a8a1564e44899e8c2ab4210c7d12.r94.cf5.rackcdn.com/ to review your changes. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

[jclouds/jclouds-site] Release notes for the 2.0.1 release (#195)

This is the draft for the 2.0.1 release notes. The branch is pushed to thee ASF remote, so feel free to commit directly to it to amend/fix/add/remove anything. You can view, comment on, or merge this pull request online at: https://github.com/jclouds/jclouds-site/pull/195 -- Commit Summary --

Jenkins build is back to normal : jclouds-cli-2.0.x-branch #28

https://jclouds.ci.cloudbees.com/job/jclouds-cli-2.0.x-branch/28/

[jira] [Updated] (JCLOUDS-1219) Add support for Packet.net

[ https://issues.apache.org/jira/browse/JCLOUDS-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignasi Barrera updated JCLOUDS-1219: Labels: packet (was: ) > Add support for Packet.net > -- > >

[jira] [Resolved] (JCLOUDS-1219) Add support for Packet.net

[ https://issues.apache.org/jira/browse/JCLOUDS-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignasi Barrera resolved JCLOUDS-1219. - Resolution: Fixed Fix Version/s: 2.1.0 > Add support for Packet.net >

Build failed in Jenkins: jclouds-cli-2.0.x-branch #27

https://jclouds.ci.cloudbees.com/job/jclouds-cli-2.0.x-branch/27/-- Started by upstream project "jclouds-karaf-2.0.x-branch" build number 36 originally caused by: Started by upstream project "jclouds-labs-2.0.x-branch" build number 39 originally caused by:

Jenkins build is back to normal : jclouds-karaf-2.0.x-branch #36

https://jclouds.ci.cloudbees.com/job/jclouds-karaf-2.0.x-branch/36/

Jenkins build is still unstable: jclouds-karaf #2092

https://jclouds.ci.cloudbees.com/job/jclouds-karaf/2092/

Jenkins build is still unstable: jclouds-karaf » jclouds :: Karaf :: Integration Tests #2092

https://jclouds.ci.cloudbees.com/job/jclouds-karaf/org.apache.jclouds.karaf$itests/2092/

Re: [jclouds/jclouds-labs] vagrant: Tests can be executed concurrently - fix test assumptions (#364)

Closed #364. -- 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-labs/pull/364#event-966862743

Re: [jclouds/jclouds-labs] vagrant: Tests can be executed concurrently - fix test assumptions (#364)

Local tests passed now without transient failures. Thanks @neykov! Pushed to [master](http://git-wip-us.apache.org/repos/asf/jclouds-labs/commit/32d728ee) and [2.0.x](http://git-wip-us.apache.org/repos/asf/jclouds-labs/commit/82cad92e). -- You are receiving this because you are subscribed to

Re: [jclouds/jclouds-labs] Checks existence of node before getting SecurityGroups and Images (#360)

Squashed and pushed to [master](http://git-wip-us.apache.org/repos/asf/jclouds-labs/commit/550ca7d5) and [2.0.x](http://git-wip-us.apache.org/repos/asf/jclouds-labs/commit/e4e42454). Thanks @danielestevez! -- You are receiving this because you are subscribed to this thread. Reply to this

Re: [jclouds/jclouds-labs] Checks existence of node before getting SecurityGroups and Images (#360)

Closed #360. -- 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-labs/pull/360#event-966854389

Re: [jclouds/jclouds-labs] Checks existence of node before getting SecurityGroups and Images (#360)

danielestevez commented on this pull request. > @@ -123,8 +123,7 @@ public Image call() throws Exception { Image image = resourceDefinitionToImage.create(cloneTemplate.getSourceNodeId(), cloneTemplate.getName()) .apply(definitions.get(0)); -

Re: [jclouds/jclouds-labs] Checks existence of node before getting SecurityGroups and Images (#360)

@danielestevez pushed 1 commit. fe3a13b Fixes log message again -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/jclouds/jclouds-labs/pull/360/files/fee81c55eff009ed917785036decd884ca105b50..fe3a13bd07d2927ab4f69c8e1ce8ee451c048857

[jclouds/jclouds-labs] vagrant: Tests can be executed concurrently - fix test assumptions (#364)

Tests from the same class are executed concurrently so don't share state in the class. Additionally use temporary files/folders to allow for parallel builds. You can view, comment on, or merge this pull request online at: https://github.com/jclouds/jclouds-labs/pull/364 -- Commit Summary --

Re: [jclouds/jclouds-labs] Checks existence of node before getting SecurityGroups and Images (#360)

nacx requested changes on this pull request. > @@ -123,8 +123,7 @@ public Image call() throws Exception { Image image = resourceDefinitionToImage.create(cloneTemplate.getSourceNodeId(), cloneTemplate.getName()) .apply(definitions.get(0)); -

Re: [jclouds/jclouds-labs] Checks existence of node before getting SecurityGroups and Images (#360)

@danielestevez pushed 1 commit. fee81c5 Fixes missing log message -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/jclouds/jclouds-labs/pull/360/files/c24e690f26b4e3fae5b3663f129f8e4bdcfa20b7..fee81c55eff009ed917785036decd884ca105b50

Jenkins build is still unstable: jclouds-karaf » jclouds :: Karaf :: Integration Tests #2091

https://jclouds.ci.cloudbees.com/job/jclouds-karaf/org.apache.jclouds.karaf$itests/2091/

Jenkins build is still unstable: jclouds-karaf #2091

https://jclouds.ci.cloudbees.com/job/jclouds-karaf/2091/

Build failed in Jenkins: jclouds-karaf-2.0.x-branch #35

https://jclouds.ci.cloudbees.com/job/jclouds-karaf-2.0.x-branch/35/-- Started by upstream project "jclouds-labs-2.0.x-branch" build number 38 originally caused by: Started by an SCM change Building remotely on 2641fb47 (standard m1.large lxc-fedora17 large)

Re: [jclouds/jclouds-labs] Oneandone compute api (#338)

This is the expected behavior. When you exceed the rate limit, the API returns a 429 error, and then the retry handler is invoked. It is OK that the request has failed. It is the retry handler that will decide if that failed request can be retried in a while The current implementation properly

Re: [jclouds/jclouds] Return lastModified and size when listing S3 parts (#1063)

nacx commented on this pull request. > + */ +@Beta +public final class PartIdsFromHttpResponseFull extends ParseSax.HandlerWithResult> { + private final StringBuilder currentText = new StringBuilder(); + + private final DateService dateParser; + +

Re: [jclouds/jclouds] Return lastModified and size when listing S3 parts (#1063)

nacx approved this pull request. +1 Thanks @andrewgaul! > +import com.google.auto.value.AutoValue; +import com.google.common.annotations.Beta; + +@AutoValue +@Beta +public abstract class ListMultipartUploadResponse { + public abstract int partNumber(); + public abstract Date lastModified();

Re: [jclouds/jclouds-labs] Fix NPE in ARM VirtualMachineToNodeMetadata (#363)

Pushed to [master](http://git-wip-us.apache.org/repos/asf/jclouds-labs/commit/550ca7d5) and [2.0.x](http://git-wip-us.apache.org/repos/asf/jclouds-labs/commit/7611db87). -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [jclouds/jclouds-labs] Fix NPE in ARM VirtualMachineToNodeMetadata (#363)

Closed #363. -- 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-labs/pull/363#event-966592173