Jenkins build is back to normal : jclouds #3480

2016-09-17 Thread jenkins-no-reply 
See

Jenkins build is back to normal : jclouds » jclouds Amazon Simple Storage Service (S3) provider #3480

2016-09-17 Thread jenkins-no-reply 
See

Re: [jclouds/jclouds-karaf] Added Azure ARM (#84)

2016-09-17 Thread Ignasi Barrera 
I've already opened the issues and corresponding PRs: 
https://github.com/apache/servicemix-bundles/pull/85 & 
https://github.com/apache/servicemix-bundles/pull/86
I've tried the change with the servicemix bundles and everything keeps working 
:)
There is a version named `bundles-2016.09` so we can expect a new servicemix 
bundle release this month. Let's see if those PRs enter that release! 
Meanwhile, good to merge with the custom bundles, and update karaf to remove 
them once there is a servicemix release that includes them?

-- 
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-karaf/pull/84#issuecomment-247809619

Re: [jclouds/jclouds] Do not fail AWS S3 signer tests with expiry (76995a3)

2016-09-17 Thread Andrew Gaul 
@nacx Thanks for the pointer; addressed by 
080bcce224e8752840b332debd1a3be7a4ae8c5f.

-- 
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/commit/76995a363d1cabaee26066b52a476ae28c4fd638#commitcomment-19067352

Re: [jclouds/jclouds-karaf] Added Azure ARM (#84)

2016-09-17 Thread Andrew Phillips 
> I wouldn't feel comfortable upgrading OkHttp. It is a great library, but that 
> kind of client validations, imposing strict restrictions on what they expect 
> from servers, can be a show stopper for some providers.

Fair point - if that's something that we can't easily verify (e.g. via a PR) 
except by testing the providers live, then that would indeed seem like a bit of 
a big change given the current goal.

"Option 2" (ServiceMix request) sounds like a good plan, in that case!

-- 
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-karaf/pull/84#issuecomment-247807927

Re: [jclouds/jclouds] Do not fail AWS S3 signer tests with expiry (76995a3)

2016-09-17 Thread Ignasi Barrera 
@andrewgaul Looks like this introduces a coupe [checkstyle 
viilations](https://jclouds.ci.cloudbees.com/job/jclouds/3479/org.apache.jclouds.provider$aws-s3/violations/file/src/test/java/org/jclouds/aws/s3/blobstore/integration/AWSS3BlobSignerLiveTest.java/).

-- 
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/commit/76995a363d1cabaee26066b52a476ae28c4fd638#commitcomment-19067051

Re: [jclouds/jclouds-karaf] Added Azure ARM (#84)

2016-09-17 Thread Ignasi Barrera 
I'm a bit hesitant to upgrade OkHttp. Some time ago I wanted to upgrade it to 
version 3.0.0, but there were several errors due to client validations. Looking 
at the changelog... it is significant, and there are changes such as this one 
in 2.4.0:

>Forbid response bodies on HTTP 204 and 205 responses. Webservers that return 
>such malformed responses will now trigger a ProtocolException in the client.

That introduces validations that may cause the driver to fail on certain 
providers (we know how tricky/far-from-the-spec-correctness many provider apis 
are), and that could be an issue since some of them (Docker, openstack-marconi, 
azure ARM, use OkHttp by default to leverage some features such as PATCH 
requests, etc.

I wouldn't feel comfortable upgrading OkHttp. It is a great library, but that 
kind of client validations, imposing strict restrictions on what they expect 
from servers, can be a show stopper for some providers.

> Failing that, we would want to open a ticket with Servicemix for them to 
> create a new bundle for the version we need, I'd say.

Yep. I have it in my TODO list

-- 
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-karaf/pull/84#issuecomment-247807072

Re: [jclouds/jclouds-karaf] Fix OSGiScriptEngineManager package (#83)

2016-09-17 Thread Andrew Phillips 
> Squashed, amended the commit message and pushed to master as ed2a6b47

Thanks, Ignasi!

-- 
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-karaf/pull/83#issuecomment-247806799

Build failed in Jenkins: jclouds #3479

2016-09-17 Thread jenkins-no-reply 
See 

Changes:

[Andrew Gaul] Do not fail AWS S3 signer tests with expiry

--
[...truncated 32145 lines...]
[JENKINS] Archiving 

 to 
org.apache.jclouds.provider/rackspace-cloudservers-us/2.0.0-20160917.203405-689/rackspace-cloudservers-us-2.0.0-20160917.203405-689-javadoc.jar
[JENKINS] Archiving 

 to 
org.apache.jclouds.provider/rackspace-cloudservers-us/2.0.0-20160917.203405-689/rackspace-cloudservers-us-2.0.0-20160917.203405-689-sources.jar
[JENKINS] Archiving 

 to 
org.apache.jclouds.provider/elastichosts-syd-v/2.0.0-SNAPSHOT/elastichosts-syd-v-2.0.0-SNAPSHOT.pom
[JENKINS] Archiving 
 to 
org.apache.jclouds.driver/jclouds-slf4j/2.0.0-SNAPSHOT/jclouds-slf4j-2.0.0-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.jclouds.driver/jclouds-slf4j/2.0.0-20160917.201623-724/jclouds-slf4j-2.0.0-20160917.201623-724.jar
[JENKINS] Archiving 

 to 
org.apache.jclouds.driver/jclouds-slf4j/2.0.0-20160917.201623-724/jclouds-slf4j-2.0.0-20160917.201623-724-tests.jar
[JENKINS] Archiving 

 to 
org.apache.jclouds.driver/jclouds-slf4j/2.0.0-20160917.201623-724/jclouds-slf4j-2.0.0-20160917.201623-724-javadoc.jar
[JENKINS] Archiving 

 to 
org.apache.jclouds.driver/jclouds-slf4j/2.0.0-20160917.201623-724/jclouds-slf4j-2.0.0-20160917.201623-724-sources.jar
[JENKINS] Archiving 
 to 
org.apache.jclouds/jclouds-skeletons-project/2.0.0-SNAPSHOT/jclouds-skeletons-project-2.0.0-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.jclouds.provider/rackspace-cloudblockstorage-us/2.0.0-SNAPSHOT/rackspace-cloudblockstorage-us-2.0.0-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.jclouds.provider/rackspace-cloudblockstorage-us/2.0.0-20160917.203354-686/rackspace-cloudblockstorage-us-2.0.0-20160917.203354-686.jar
[JENKINS] Archiving 

 to 
org.apache.jclouds.provider/rackspace-cloudblockstorage-us/2.0.0-20160917.203354-686/rackspace-cloudblockstorage-us-2.0.0-20160917.203354-686-tests.jar
[JENKINS] Archiving 

 to 
org.apache.jclouds.provider/rackspace-cloudblockstorage-us/2.0.0-20160917.203354-686/rackspace-cloudblockstorage-us-2.0.0-20160917.203354-686-javadoc.jar
[JENKINS] Archiving 

 to 
org.apache.jclouds.provider/rackspace-cloudblockstorage-us/2.0.0-20160917.203354-686/rackspace-cloudblockstorage-us-2.0.0-20160917.203354-686-sources.jar
[JENKINS] Archiving 

 to 
org.apache.jclouds.provider/serverlove-z1-man/2.0.0-SNAPSHOT/serverlove-z1-man-2.0.0-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.jclouds.provider/rackspace-cloudservers-uk/2.0.0-SNAPSHOT/rackspace-cloudservers-uk-2.0.0-SNAPSHOT.pom
[JENKINS] Archiving 
 to 
org.apache.jclouds.api/cloudwatch/2.0.0-SNAPSHOT/cloudwatch-2.0.0-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.jclouds.api/cloudwatch/2.0.0-20160917.202120-720/cloudwatch-2.0.0-20160917.202120-720.jar
[JENKINS] Archiving 

 to

Build failed in Jenkins: jclouds » jclouds Amazon Simple Storage Service (S3) provider #3479

2016-09-17 Thread jenkins-no-reply 
See 


--
[...truncated 71 lines...]
[pool-1-thread-3] Test 
testTransformableToContains(org.jclouds.aws.s3.AWSS3ProviderTest) succeeded: 
17ms
Test suite progress: tests succeeded: 4, failed: 0, skipped: 0.
Starting test 
testPutWithReducedRedundancy(org.jclouds.aws.s3.AWSS3ClientExpectTest)
[pool-2-thread-1] Test 
testPutWithReducedRedundancy(org.jclouds.aws.s3.AWSS3ClientExpectTest) 
succeeded: 2055ms
Test suite progress: tests succeeded: 5, failed: 0, skipped: 0.
Starting test 
testSignGetBlob(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerV4ExpectTest)
Starting test 
testSignGetBlobWithOptions(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerV4ExpectTest)
[pool-3-thread-1] Test 
testSignGetBlob(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerV4ExpectTest) 
skipped.
Test suite progress: tests succeeded: 5, failed: 0, skipped: 1.
Starting test 
testSignGetBlobWithTime(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerV4ExpectTest)
[pool-3-thread-2] Test 
testSignGetBlobWithOptions(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerV4ExpectTest)
 skipped.
Test suite progress: tests succeeded: 5, failed: 0, skipped: 2.
Starting test 
testSignPutBlob(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerV4ExpectTest)
Starting test 
testSignPutBlobWithTime(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerV4ExpectTest)
Starting test 
testSignRemoveBlob(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerV4ExpectTest)
[pool-3-thread-4] Test 
testSignPutBlob(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerV4ExpectTest) 
skipped.
Test suite progress: tests succeeded: 5, failed: 0, skipped: 3.
[pool-3-thread-2] Test 
testSignRemoveBlob(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerV4ExpectTest) 
skipped.
Test suite progress: tests succeeded: 5, failed: 0, skipped: 4.
[pool-3-thread-5] Test 
testSignPutBlobWithTime(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerV4ExpectTest)
 succeeded: 171ms
Test suite progress: tests succeeded: 6, failed: 0, skipped: 4.
[pool-3-thread-3] Test 
testSignGetBlobWithTime(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerV4ExpectTest)
 succeeded: 173ms
Test suite progress: tests succeeded: 7, failed: 0, skipped: 4.
Starting test 
testSignGetBlobWithTime(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerExpectTest)
Starting test 
testSignPutBlobWithTime(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerExpectTest)
Starting test 
testSignGetBlob(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerExpectTest)
Starting test 
testSignGetBlobWithOptions(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerExpectTest)
Starting test 
testSignPutBlob(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerExpectTest)
[pool-4-thread-3] Test 
testSignGetBlob(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerExpectTest) 
succeeded: 787ms
Test suite progress: tests succeeded: 8, failed: 0, skipped: 4.
Starting test 
testSignRemoveBlob(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerExpectTest)
[pool-4-thread-4] Test 
testSignGetBlobWithOptions(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerExpectTest)
 succeeded: 788ms
Test suite progress: tests succeeded: 9, failed: 0, skipped: 4.
[pool-4-thread-5] Test 
testSignPutBlob(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerExpectTest) 
succeeded: 788ms
Test suite progress: tests succeeded: 10, failed: 0, skipped: 4.
[pool-4-thread-1] Test 
testSignGetBlobWithTime(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerExpectTest) 
succeeded: 791ms
Test suite progress: tests succeeded: 11, failed: 0, skipped: 4.
[pool-4-thread-2] Test 
testSignPutBlobWithTime(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerExpectTest) 
succeeded: 792ms
Test suite progress: tests succeeded: 12, failed: 0, skipped: 4.
[pool-4-thread-3] Test 
testSignRemoveBlob(org.jclouds.aws.s3.blobstore.AWSS3BlobSignerExpectTest) 
succeeded: 85ms
Test suite progress: tests succeeded: 13, failed: 0, skipped: 4.
Starting test testCopyObjectInvalidName(org.jclouds.aws.s3.AWSS3ClientTest)
Starting test 
testGetBucketLocationEUIsStillDefault(org.jclouds.aws.s3.AWSS3ClientTest)
Starting test testGetBucketLocation(org.jclouds.aws.s3.AWSS3ClientTest)
Starting test testPutBucketEu(org.jclouds.aws.s3.AWSS3ClientTest)
Starting test testPutBucketDefault(org.jclouds.aws.s3.AWSS3ClientTest)
[pool-5-thread-1] Test 
testCopyObjectInvalidName(org.jclouds.aws.s3.AWSS3ClientTest) succeeded: 733ms
Test suite progress: tests succeeded: 14, failed: 0, skipped: 4.
Starting test testPutObject(org.jclouds.aws.s3.AWSS3ClientTest)
[pool-5-thread-2] Test 
testGetBucketLocation(org.jclouds.aws.s3.AWSS3ClientTest) succeeded: 737ms
Test suite progress: tests succeeded: 15, failed: 0, skipped: 4.
[pool-5-thread-3] Test 
testGetBucketLocationEUIsStillDefault(org.jclouds.aws.s3.AWSS3ClientTest) 
succeeded: 737ms
Test suite progress: tests succeeded: 16, failed: 0, skipped: 4.
Starting test testAbortMultipartUpload(org.jclouds.aws.s3.AWSS3ClientTest)
Starting test testAllRegions(org.jclouds.aws.s3.AWSS3ClientTest)

Re: [jclouds/jclouds-karaf] Fix OSGiScriptEngineManager package (#83)

2016-09-17 Thread Ignasi Barrera 
Squashed, amended the commit message and pushed to master as 
[ed2a6b47](http://git-wip-us.apache.org/repos/asf/jclouds-karaf/commit/ed2a6b47).

-- 
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-karaf/pull/83#issuecomment-247806439

Re: [jclouds/jclouds-karaf] Fix OSGiScriptEngineManager package (#83)

2016-09-17 Thread Ignasi Barrera 
Closed #83.

-- 
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-karaf/pull/83#event-793136018

[jira] [Commented] (JCLOUDS-1172) Script engines are not loaded in the interactive shell

2016-09-17 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/JCLOUDS-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15499646#comment-15499646
 ] 

ASF subversion and git services commented on JCLOUDS-1172:
--

Commit ed2a6b470743db5b035ab6db786d9ec0999d63b3 in jclouds-karaf's branch 
refs/heads/master from [~nacx]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-karaf.git;h=ed2a6b4 ]

JCLOUDS-1172: Fix OSGiScriptEngineManager package and logs


> Script engines are not loaded in the interactive shell
> --
>
> Key: JCLOUDS-1172
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1172
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-karaf
>Affects Versions: 1.9.2
>Reporter: Ignasi Barrera
>Assignee: Andrew Phillips
> Fix For: 2.0.0
>
> Attachments: JCLOUDS-1172.patch
>
>
> When using the interactive shell, the script engines that are used to render 
> the values of the columns are not loaded, resulting in blank output lines 
> when running commands.
> This affects only the interactive shell.
> See this discussion for more details: 
> https://github.com/jclouds/jclouds-karaf/pull/77#issuecomment-244901813



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

2016-09-17 Thread Andrew Gaul 
These four tests now succeed on master.  You need to fix these two which fail 
with your change:

```
AWSS3BlobSignerLiveTest>S3BlobSignerLiveTest.testSignGetUrlWithTimeExpired:55->BaseBlobSignerLiveTest.testSignGetUrlWithTimeExpired:115
 » AWSResponse
AWSS3BlobSignerLiveTest>S3BlobSignerLiveTest.testSignPutUrlWithTimeExpired:79->BaseBlobSignerLiveTest.testSignPutUrlWithTimeExpired:179
 » AWSResponse
```

-- 
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-247804244

Re: [jclouds/jclouds-labs] Fix package export for OSGi (#318)

2016-09-17 Thread Andrew Phillips 
> Yes, I've tested all PRs together and ARM works fine in the CLI :)

Nice ;-) Good to go for me, in that case!

-- 
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/318#issuecomment-247795651

Re: [jclouds/jclouds-labs] Fix package export for OSGi (#318)

2016-09-17 Thread Ignasi Barrera 
Yes, I've tested all PRs together and ARM works fine in the CLI :)

-- 
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/318#issuecomment-247795531

Re: [jclouds/jclouds-karaf] Added Azure ARM (#84)

2016-09-17 Thread Andrew Phillips 
PS: There appears to be a bundle for 2.7.5 (OkHttp) and its dependency, Okio 
1.6.0: 

* 
http://search.maven.org/#artifactdetails%7Corg.apache.servicemix.bundles%7Corg.apache.servicemix.bundles.okhttp%7C2.7.5_1%7Cbundle
* 
http://search.maven.org/#artifactdetails%7Corg.apache.servicemix.bundles%7Corg.apache.servicemix.bundles.okio%7C1.6.0_1%7Cbundle

Have we tried upgrading to these versions to see if that might work? Still the 
same major version, so hopefully the changes required should be minimal? 
Haven't checked what the changes are from OkHttp 2.2.0 to 2.7.5, I hasten to 
add...

-- 
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-karaf/pull/84#issuecomment-247791079

Re: [jclouds/jclouds-labs] Fix package export for OSGi (#318)

2016-09-17 Thread Andrew Phillips 
+1 pending a successful test - looks good to me. Were you able to try this out 
locally, @nacx?

-- 
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/318#issuecomment-247790821

Re: [jclouds/jclouds-karaf] Added Azure ARM (#84)

2016-09-17 Thread Andrew Phillips 
> I'd like to focus on what we really need so we can include this as soon as 
> possible for the 2.0 release, and once that is done, take time to create 
> proper bundles for all OkHttp modules and move to servicemix.

As a potentially temporary fix, this makes sense to me and looks good, assuming 
local testing works. In terms of what the best next step would be, I think we'd 
ideally like to upgrade OkHttp to a newer/the newest option for which a bundle 
exists - have we tested that?

Failing that, we would want to open a ticket with Servicemix for them to create 
a new bundle for the version we need, I'd say.

Thanks for taking this on, @nacx!

-- 
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-karaf/pull/84#issuecomment-247789834

Re: [jclouds/jclouds-karaf] Fix OSGiScriptEngineManager package (#83)

2016-09-17 Thread Andrew Phillips 
Oops :-( Sorry, sloppy testing on my part. Changes look good to me - thanks, 
@nacx!

When you merge, could you change the commit title to reference the issue 
number? Thanks!

-- 
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-karaf/pull/83#issuecomment-247788653

Re: [jclouds/jclouds-karaf] Added Azure ARM (#84)

2016-09-17 Thread Andrew Phillips 
demobox commented on this pull request.



> @@ -566,7 +566,7 @@ limitations under the License.
 
 
 
-  
+  

Er...oops :-( Thanks for catching that! Mind changing the commit title to refer 
to the JIRA issue?

Thanks, @nacx!

-- 
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-karaf/pull/84#pullrequestreview-460129