Re: [jclouds] Token based authentication in openstack-keystone (#433)

Should I close this? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/433#issuecomment-48984007

Re: [jclouds-labs-google] JCLOUDS-458: Addressing suggestions in PR-31 (#33)

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

Re: [jclouds-labs-google] JCLOUDS-458: Addressing suggestions in PR-31 (#33)

[jclouds » jclouds-labs-google #1123](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-google/1123/) 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/jc

Re: [jclouds-labs-openstack] Neutron Refactoring (#111)

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

Re: [jclouds-labs-openstack] Neutron Refactoring (#111)

[jclouds » jclouds-labs-openstack #1403](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-openstack/1403/) 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/jclo

Re: [jclouds-labs-google] JCLOUDS-458: Addressing suggestions in PR-31 (#33)

> +Class expected) { > + assertCodeMakes(method, uri, statusCode, message, "application/json", > content, expected); > + } > + > + private void assertCodeMakes(String method, URI uri, int statusCode, > String message, String contentType, > +String content, Class e

Re: [jclouds] JCLOUDS-622: remove calls to InputSupplier methods (#436)

I like the BlahAndClose methods. Makes code reading easier and using these methods is less error prone. I'm still a little fuzzy about about MultiPartForm gets used in the context of other blobstore operations. But the change itself seems to do what is says. Looks good! --- Reply to this email

[jira] [Comment Edited] (JCLOUDS-626) OutOfMemoryException with FileSystem provider, large content from non-repeatable input streams

[ https://issues.apache.org/jira/browse/JCLOUDS-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061430#comment-14061430 ] Andrew Gaul edited comment on JCLOUDS-626 at 7/14/14 11:48 PM:

[jira] [Commented] (JCLOUDS-626) OutOfMemoryException with FileSystem provider, large content from non-repeatable input streams

[ https://issues.apache.org/jira/browse/JCLOUDS-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061430#comment-14061430 ] Andrew Gaul commented on JCLOUDS-626: - [~knl] Can you test against 1.8.0-SNAPSHOT? I

[jira] [Updated] (JCLOUDS-626) OutOfMemoryException with FileSystem provider, large content from non-repeatable input streams

[ https://issues.apache.org/jira/browse/JCLOUDS-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Gaul updated JCLOUDS-626: Description: The following (incomplete) piece of code dies on my systems with a stacktrace (given

[jira] [Assigned] (JCLOUDS-628) PROPERTY_MAX_CONNECTIONS_PER_CONTEXT not honored for https connections

[ https://issues.apache.org/jira/browse/JCLOUDS-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Gaul reassigned JCLOUDS-628: --- Assignee: Shri Javadekar [~shrinand] Can you investigate this issue further, and perhaps min

Re: [jclouds-chef] JCLOUDS-624 - Fixed bug in ListNodes (#47)

Thanks @luciano-sabenca-movile! A couple comments: * I'd modify the ChefService interface and the strategies to have only a method that accepts a regular `ExecutorService`, and internally call the `listeningDecorator`. It is safe, as it will do nothing if the passed object is already a `Listeni

Re: [jclouds] [JCLOUDS-263] Usage of internalURL services' endpoints (#142)

Hi, I'm using jclouds BlobStore API with Rackspace as provider. The InternalUrlModule is only available for keystone v2_0 not for v1_1. That differs from PublicURLOrInternalIfNull, which has two different classes. Is this done on purpose? or, can i do a PR to make InternalUrlModule available fo

Re: [jclouds-labs-google] JCLOUDS-458: Addressing suggestions in PR-31 (#33)

> +Class expected) { > + assertCodeMakes(method, uri, statusCode, message, "application/json", > content, expected); > + } > + > + private void assertCodeMakes(String method, URI uri, int statusCode, > String message, String contentType, > +String content, Class e

Re: [jclouds-labs-google] JCLOUDS-458: Addressing suggestions in PR-31 (#33)

> +Class expected) { > + assertCodeMakes(method, uri, statusCode, message, "application/json", > content, expected); > + } > + > + private void assertCodeMakes(String method, URI uri, int statusCode, > String message, String contentType, > +String content, Class e

Re: [jclouds-labs-google] JCLOUDS-458: Addressing suggestions in PR-31 (#33)

> +/** > + * This will parse and set an appropriate exception on the command object. > + */ > +@Singleton > +public class GoogleCloudStorageErrorHandler implements HttpErrorHandler { > + public void handleError(HttpCommand command, HttpResponse response) { > + // it is important to always re

Re: [jclouds-labs-google] JCLOUDS-458: Addressing suggestions in PR-31 (#33)

This is looking pretty good to me. I'd like to get a +1 from both @demobox and @nacx before we merge it in. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-google/pull/33#issuecomment-48968435

Re: [jclouds-labs-google] JCLOUDS-458: Addressing suggestions in PR-31 (#33)

@demobox @nacx I made the suggested changes and would like to know your concenrns. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-google/pull/33#issuecomment-48964295

[jira] [Created] (JCLOUDS-628) PROPERTY_MAX_CONNECTIONS_PER_CONTEXT not honored for https connections

Shri Javadekar created JCLOUDS-628: -- Summary: PROPERTY_MAX_CONNECTIONS_PER_CONTEXT not honored for https connections Key: JCLOUDS-628 URL: https://issues.apache.org/jira/browse/JCLOUDS-628 Project: j

Re: [jclouds] Unasync OpenStack Nova and Extension APIs (#417)

+1 --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/417#issuecomment-48939334

Re: [jclouds-chef] JCLOUDS-624 - Fixed bug in ListNodes (#47)

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

Re: [jclouds-chef] JCLOUDS-624 - Fixed bug in ListNodes (#47)

[jclouds » jclouds-chef #1171](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-chef/1171/) 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-chef/pul

[jira] [Commented] (JCLOUDS-624) Bug at ListNodes In ChefContext

[ https://issues.apache.org/jira/browse/JCLOUDS-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14060890#comment-14060890 ] Luciano Sabença commented on JCLOUDS-624: - Hi, all! As promised, I've just creat

[jclouds-chef] JCLOUDS-624 - Fixed bug in ListNodes (#47)

Details can be found at: https://issues.apache.org/jira/browse/JCLOUDS-624 Any suggestions are very welcome! To fix this bug, I used the approach debated in the above link: create new methods to do the operation using an ExecutorService provided by the user.The the old methods are still working,

Re: [jclouds-chef] JCLOUDS-624 - Fixed bug in ListNodes (#46)

Hi! I will close this PR and open a new one with this bug fixed. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-chef/pull/46#issuecomment-48927267

Re: [jclouds-chef] JCLOUDS-624 - Fixed bug in ListNodes (#46)

Closed #46. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-chef/pull/46#event-141318044

Re: [jclouds] Unasync OpenStack Nova and Extension APIs (#417)

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

Re: [jclouds] Unasync OpenStack Nova and Extension APIs (#417)

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

Re: [jclouds] Unasync OpenStack Nova and Extension APIs (#417)

[jclouds » jclouds #1361](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1361/) 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/417#issuecomme

[jira] [Resolved] (JCLOUDS-471) FloatingIPApi.create() does not work, pool needed

[ https://issues.apache.org/jira/browse/JCLOUDS-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignasi Barrera resolved JCLOUDS-471. Resolution: Fixed > FloatingIPApi.create() does not work, pool needed > --

[jira] [Updated] (JCLOUDS-607) ComputeService.createNodesInGroup throws NPE on FloatingAPI.create()

[ https://issues.apache.org/jira/browse/JCLOUDS-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignasi Barrera updated JCLOUDS-607: --- Fix Version/s: 1.7.4 > ComputeService.createNodesInGroup throws NPE on FloatingAPI.create()

Re: [jclouds] JCLOUDS-625 - VolumeBuilder does not allow null id while VolumeImpl allows it to be nullable (#437)

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

Re: [jclouds] JCLOUDS-625 - VolumeBuilder does not allow null id while VolumeImpl allows it to be nullable (#437)

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

Re: [jclouds] JCLOUDS-625 - VolumeBuilder does not allow null id while VolumeImpl allows it to be nullable (#437)

[jclouds » jclouds #1360](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1360/) 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/437#issuecomme

[jira] [Created] (JCLOUDS-627) Add support for aborting putBlob operations

Nikola Knezevic created JCLOUDS-627: --- Summary: Add support for aborting putBlob operations Key: JCLOUDS-627 URL: https://issues.apache.org/jira/browse/JCLOUDS-627 Project: jclouds Issue Typ

[jira] [Created] (JCLOUDS-626) OutOfMemoryException with FileSystem provider, large content from non-repeatable input streams

Nikola Knezevic created JCLOUDS-626: --- Summary: OutOfMemoryException with FileSystem provider, large content from non-repeatable input streams Key: JCLOUDS-626 URL: https://issues.apache.org/jira/browse/JCLOUDS-6

[jira] [Commented] (JCLOUDS-625) VolumeBuilder does not allow null id while VolumeImpl allows it to be nullable

[ https://issues.apache.org/jira/browse/JCLOUDS-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14060539#comment-14060539 ] Werner Buck commented on JCLOUDS-625: - Pull request is at https://github.com/jclouds/

[jclouds] JCLOUDS-625 - VolumeBuilder does not allow null id while VolumeImpl allows it to be nullable (#437)

VolumeBuilder does not allow null id while VolumeImpl allows it to be nullable. You can merge this Pull Request by running: git pull https://github.com/wernerb/jclouds patch-1 Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds/pull/437 -- Commit Summar

[jira] [Created] (JCLOUDS-625) VolumeBuilder does not allow null id while VolumeImpl allows it to be nullable

Werner Buck created JCLOUDS-625: --- Summary: VolumeBuilder does not allow null id while VolumeImpl allows it to be nullable Key: JCLOUDS-625 URL: https://issues.apache.org/jira/browse/JCLOUDS-625 Project:

Jenkins build is back to normal : jclouds-1.7.x-branch » jclouds Open Hosting East1 provider #116

See

Jenkins build is back to stable : jclouds-1.7.x-branch » jclouds compute core #116

See

Re: [jclouds] JCLOUDS-607: ComputeService.createNodesInGroup throws NPE on FloatingIPApi.create() (7641bd6)

> Also fixed all remaining checkstyle errors in the nova api. Thanks, @nacx! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/commit/7641bd61cd56f7f5a4da5ac89769c1d200abe79f#commitcomment-6993673

Re: [jclouds] JCLOUDS-607: ComputeService.createNodesInGroup throws NPE on FloatingIPApi.create() (7641bd6)

Fixed them [here](https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=3b2f02b7). Also fixed all remaining checkstyle errors in the nova api. Thanks for having a look! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/commit/7641bd61cd56f7f5a4

Re: [jclouds-labs-google] JCLOUDS-458: Addressing suggestions in PR-31 (#33)

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