Build failed in Jenkins: jclouds-guava-guice-compat » 17.0,4.0,OpenJDK 7 (latest) #210

[jenkins-no-reply]

See 


Changes:

[Andrew Gaul] JCLOUDS-1161: Make AWSS3BlobRequestSignerV4 the default signer.

[Andrew Gaul] JCLOUDS-1182: Added Seoul and Mumbai regions to AWS

--
[...truncated 21312 lines...]
Test suite progress: tests succeeded: 819, failed: 2, skipped: 0.
Starting test 
testQueryParam(org.jclouds.rest.internal.RestAnnotationProcessorTest)
Starting test 
testRequestFilterStripExpect(org.jclouds.rest.internal.RestAnnotationProcessorTest)
[pool-90-thread-2] Test 
testQueryParam(org.jclouds.rest.internal.RestAnnotationProcessorTest) 
succeeded: 1ms
Test suite progress: tests succeeded: 820, failed: 2, skipped: 0.
Starting test 
testQueryParam(org.jclouds.rest.internal.RestAnnotationProcessorTest)
[pool-90-thread-3] Test 
testRequestFilterOverrideOnRequest(org.jclouds.rest.internal.RestAnnotationProcessorTest)
 succeeded: 3ms
Test suite progress: tests succeeded: 821, failed: 2, skipped: 0.
Starting test 
testSkipEncoding(org.jclouds.rest.internal.RestAnnotationProcessorTest)
[pool-90-thread-2] Test 
testQueryParam(org.jclouds.rest.internal.RestAnnotationProcessorTest) 
succeeded: 1ms
Test suite progress: tests succeeded: 822, failed: 2, skipped: 0.
Starting test 
testQueryParam(org.jclouds.rest.internal.RestAnnotationProcessorTest)
[pool-90-thread-3] Test 
testSkipEncoding(org.jclouds.rest.internal.RestAnnotationProcessorTest) 
succeeded: 1ms
Test suite progress: tests succeeded: 823, failed: 2, skipped: 0.
[pool-90-thread-1] Test 
testRequestFilterOverride(org.jclouds.rest.internal.RestAnnotationProcessorTest)
 succeeded: 3ms
Test suite progress: tests succeeded: 824, failed: 2, skipped: 0.
Starting test 
testTwoDifferentEndpointParams(org.jclouds.rest.internal.RestAnnotationProcessorTest)
Starting test 
testTwoDifferentHeaders(org.jclouds.rest.internal.RestAnnotationProcessorTest)
[pool-90-thread-2] Test 
testQueryParam(org.jclouds.rest.internal.RestAnnotationProcessorTest) 
succeeded: 1ms
Test suite progress: tests succeeded: 825, failed: 2, skipped: 0.
Starting test 
testQueryParam(org.jclouds.rest.internal.RestAnnotationProcessorTest)
[pool-90-thread-3] Test 
testTwoDifferentEndpointParams(org.jclouds.rest.internal.RestAnnotationProcessorTest)
 succeeded: 1ms
Test suite progress: tests succeeded: 826, failed: 2, skipped: 0.
[pool-90-thread-2] Test 
testQueryParam(org.jclouds.rest.internal.RestAnnotationProcessorTest) 
succeeded: 1ms
Test suite progress: tests succeeded: 827, failed: 2, skipped: 0.
Starting test 
testTwoSameHeaders(org.jclouds.rest.internal.RestAnnotationProcessorTest)
Starting test 
testQueryParam(org.jclouds.rest.internal.RestAnnotationProcessorTest)
[pool-90-thread-1] Test 
testTwoDifferentHeaders(org.jclouds.rest.internal.RestAnnotationProcessorTest) 
succeeded: 2ms
Test suite progress: tests succeeded: 828, failed: 2, skipped: 0.
[pool-90-thread-2] Test 
testQueryParam(org.jclouds.rest.internal.RestAnnotationProcessorTest) 
succeeded: 1ms
Test suite progress: tests succeeded: 829, failed: 2, skipped: 0.
Starting test 
testQueryParam(org.jclouds.rest.internal.RestAnnotationProcessorTest)
Starting test testURI(org.jclouds.rest.internal.RestAnnotationProcessorTest)
[pool-90-thread-1] Test 
testURI(org.jclouds.rest.internal.RestAnnotationProcessorTest) succeeded: 0ms
Test suite progress: tests succeeded: 830, failed: 2, skipped: 0.
[pool-90-thread-2] Test 
testQueryParam(org.jclouds.rest.internal.RestAnnotationProcessorTest) 
succeeded: 1ms
Test suite progress: tests succeeded: 831, failed: 2, skipped: 0.
Starting test testUnwrap1(org.jclouds.rest.internal.RestAnnotationProcessorTest)
[pool-90-thread-3] Test 
testTwoSameHeaders(org.jclouds.rest.internal.RestAnnotationProcessorTest) 
succeeded: 4ms
Test suite progress: tests succeeded: 832, failed: 2, skipped: 0.
Starting test testUnwrap3(org.jclouds.rest.internal.RestAnnotationProcessorTest)
Starting test testUnwrap2(org.jclouds.rest.internal.RestAnnotationProcessorTest)
[pool-90-thread-1] Test 
testUnwrap1(org.jclouds.rest.internal.RestAnnotationProcessorTest) succeeded: 
5ms
Test suite progress: tests succeeded: 833, failed: 2, skipped: 0.
[pool-90-thread-2] Test 
testUnwrap2(org.jclouds.rest.internal.RestAnnotationProcessorTest) succeeded: 
2ms
Test suite progress: tests succeeded: 834, failed: 2, skipped: 0.
[pool-90-thread-3] Test 
testUnwrap3(org.jclouds.rest.internal.RestAnnotationProcessorTest) succeeded: 
4ms
Test suite progress: tests succeeded: 835, failed: 2, skipped: 0.
Starting test 
testUnwrapValueNamed(org.jclouds.rest.internal.RestAnnotationProcessorTest)
Starting test 
testVirtualHost(org.jclouds.rest.internal.RestAnnotationProcessorTest)
Starting test testUnwrap4(org.jclouds.rest.internal.RestAnnotationProcessorTest)
[pool-90-thread-3] Test 
testVirtualHost(org.jclouds.rest.internal.RestAnnotationProcessorTest) 
succeeded: 1ms
Test 

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

[Andrew Gaul]

Closed #1008.

-- 
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1008#event-828500622

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

[Andrew Gaul]

Pushed to master as 7826d22d301b1a6accef2b7686700231ffba7e29.

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

[jira] [Commented] (JCLOUDS-1161) Signed PUT requests using signature v4

[Andrew Gaul (JIRA)]

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

Andrew Gaul commented on JCLOUDS-1161:
--

We now use the V4 signer for AWS, addressing #1.  For #2, should jclouds strip 
out the MD5 for signed URLs?

> Signed PUT requests using signature v4
> --
>
> Key: JCLOUDS-1161
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1161
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Affects Versions: 2.0.0
> Environment: Tried this on commit 
> 557a1156945590c221094a1ccc983ba9e1d99a60.
> {noformat}
> commit 557a1156945590c221094a1ccc983ba9e1d99a60
> Author: Iván Lomba 
> Date:   Tue Aug 16 22:12:47 2016 +0200
> JCLOUDS-482: Fix ProfitBricksComputeServiceLiveTest custom hardware assert
> {noformat}
>Reporter: Shri Javadekar
> Fix For: 2.0.0
>
>
> JIRA issues JCLOUDS-766 and JCLOUDS-1090 mention that signed put requests 
> don't work with jclouds. This is because "v4 URL signing requires a content 
> hash for the server to accept the PUT request but the jclouds API does not 
> allow for this". There is another way for doing this. The AWS 
> documentation[1] says that phrase UNSIGNED-PAYLOAD can be used when the 
> content hash is not available.
> The current code in jclouds already uses UNSIGNED-PAYLOAD as the content hash 
> and signs the requests. However, even with that signed put requests were 
> failing for me.
> Here are a couple of things I had to do to get signed put requests to work.
> 1. Use AWSS3BlobRequestSignerv4.
> {noformat}
> diff --git 
> a/providers/aws-s3/src/main/java/org/jclouds/aws/s3/blobstore/config/AWSS3BlobStoreContextModule.java
>  
> b/providers/aws-s3/src/main/java/org/jclouds/aws/s3/blobstore/config/AWSS3BlobStoreContextModule.java
> index 6c551d5..79ea8c7 100644
> --- 
> a/providers/aws-s3/src/main/java/org/jclouds/aws/s3/blobstore/config/AWSS3BlobStoreContextModule.java
> +++ 
> b/providers/aws-s3/src/main/java/org/jclouds/aws/s3/blobstore/config/AWSS3BlobStoreContextModule.java
> @@ -16,7 +16,7 @@
>   */
>  package org.jclouds.aws.s3.blobstore.config;
> -import org.jclouds.aws.s3.blobstore.AWSS3BlobRequestSigner;
> +import org.jclouds.aws.s3.blobstore.AWSS3BlobRequestSignerV4;
>  import org.jclouds.aws.s3.blobstore.AWSS3BlobStore;
>  import org.jclouds.blobstore.BlobRequestSigner;
>  import org.jclouds.s3.blobstore.S3BlobStore;
> @@ -34,6 +34,6 @@ public class AWSS3BlobStoreContextModule extends 
> S3BlobStoreContextModule {
> @Override
> protected void bindRequestSigner() {
> -  bind(BlobRequestSigner.class).to(AWSS3BlobRequestSigner.class);
> +  bind(BlobRequestSigner.class).to(AWSS3BlobRequestSignerV4.class);
> }
>  }
> {noformat}
> 2. In my application, I had to make sure that the contentMD5 is not added to 
> the blob builder.
> {noformat}
> blob = blobStore.blobBuilder(newBlobName())
> .forSigning()
> .payload(input)
> .contentLength(input.size())
> //.contentMD5(input.hash(Hashing.md5()))  
> <<< HAD TO REMOVE THIS
> 
> .contentType(MediaType.OCTET_STREAM.toString())
> .build();
> request = signer.signPutBlob(containerName, blob,
> requestTimeoutSeconds);
> {noformat}
> Ofcourse, #2 above is the responsibility of the app writer. But jclouds 
> should change the default signer to AWSS3BlobRequestSignerV4.
> [1] 
> http://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-query-string-auth.html



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

[jira] [Commented] (JCLOUDS-1161) Signed PUT requests using signature v4

[ASF subversion and git services (JIRA)]

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

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

Commit 7826d22d301b1a6accef2b7686700231ffba7e29 in jclouds's branch 
refs/heads/master from [~shrinand]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=7826d22 ]

JCLOUDS-1161: Make AWSS3BlobRequestSignerV4 the default signer.

Added new live tests and fixed some unit tests accordingly.


> Signed PUT requests using signature v4
> --
>
> Key: JCLOUDS-1161
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1161
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Affects Versions: 2.0.0
> Environment: Tried this on commit 
> 557a1156945590c221094a1ccc983ba9e1d99a60.
> {noformat}
> commit 557a1156945590c221094a1ccc983ba9e1d99a60
> Author: Iván Lomba 
> Date:   Tue Aug 16 22:12:47 2016 +0200
> JCLOUDS-482: Fix ProfitBricksComputeServiceLiveTest custom hardware assert
> {noformat}
>Reporter: Shri Javadekar
> Fix For: 2.0.0
>
>
> JIRA issues JCLOUDS-766 and JCLOUDS-1090 mention that signed put requests 
> don't work with jclouds. This is because "v4 URL signing requires a content 
> hash for the server to accept the PUT request but the jclouds API does not 
> allow for this". There is another way for doing this. The AWS 
> documentation[1] says that phrase UNSIGNED-PAYLOAD can be used when the 
> content hash is not available.
> The current code in jclouds already uses UNSIGNED-PAYLOAD as the content hash 
> and signs the requests. However, even with that signed put requests were 
> failing for me.
> Here are a couple of things I had to do to get signed put requests to work.
> 1. Use AWSS3BlobRequestSignerv4.
> {noformat}
> diff --git 
> a/providers/aws-s3/src/main/java/org/jclouds/aws/s3/blobstore/config/AWSS3BlobStoreContextModule.java
>  
> b/providers/aws-s3/src/main/java/org/jclouds/aws/s3/blobstore/config/AWSS3BlobStoreContextModule.java
> index 6c551d5..79ea8c7 100644
> --- 
> a/providers/aws-s3/src/main/java/org/jclouds/aws/s3/blobstore/config/AWSS3BlobStoreContextModule.java
> +++ 
> b/providers/aws-s3/src/main/java/org/jclouds/aws/s3/blobstore/config/AWSS3BlobStoreContextModule.java
> @@ -16,7 +16,7 @@
>   */
>  package org.jclouds.aws.s3.blobstore.config;
> -import org.jclouds.aws.s3.blobstore.AWSS3BlobRequestSigner;
> +import org.jclouds.aws.s3.blobstore.AWSS3BlobRequestSignerV4;
>  import org.jclouds.aws.s3.blobstore.AWSS3BlobStore;
>  import org.jclouds.blobstore.BlobRequestSigner;
>  import org.jclouds.s3.blobstore.S3BlobStore;
> @@ -34,6 +34,6 @@ public class AWSS3BlobStoreContextModule extends 
> S3BlobStoreContextModule {
> @Override
> protected void bindRequestSigner() {
> -  bind(BlobRequestSigner.class).to(AWSS3BlobRequestSigner.class);
> +  bind(BlobRequestSigner.class).to(AWSS3BlobRequestSignerV4.class);
> }
>  }
> {noformat}
> 2. In my application, I had to make sure that the contentMD5 is not added to 
> the blob builder.
> {noformat}
> blob = blobStore.blobBuilder(newBlobName())
> .forSigning()
> .payload(input)
> .contentLength(input.size())
> //.contentMD5(input.hash(Hashing.md5()))  
> <<< HAD TO REMOVE THIS
> 
> .contentType(MediaType.OCTET_STREAM.toString())
> .build();
> request = signer.signPutBlob(containerName, blob,
> requestTimeoutSeconds);
> {noformat}
> Ofcourse, #2 above is the responsibility of the app writer. But jclouds 
> should change the default signer to AWSS3BlobRequestSignerV4.
> [1] 
> http://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-query-string-auth.html



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

[jira] [Commented] (JCLOUDS-1182) Missing region in `listAssignableLocations` for AWS EC2

[ASF subversion and git services (JIRA)]

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

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

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

JCLOUDS-1182: Added Seoul and Mumbai regions to AWS

This commit addresses test failures in
AWSS3ServiceIntegrationLiveTest#testGetAssignableLocations.


> Missing region in `listAssignableLocations` for AWS EC2
> ---
>
> Key: JCLOUDS-1182
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1182
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute
>Affects Versions: 2.0.0
>Reporter: Abdysamat Mamutov
>  Labels: aws
> Fix For: 2.0.0
>
>
> In the following example:
> {code:java}
> context = ContextBuilder.newBuilder("aws-ec2" )
> .credentials(accessKey, secretKey)
> .modules( ImmutableSet. of(new 
> Log4JLoggingModule(), new JschSshClientModule() ) )
> .overrides( properties )
> .buildView(ComputeServiceContext.class);
> computeService = context.getComputeService();
> computeService.listAssignableLocations()
> {code}
> in the returned list i don't see *ap-northeast-2* region (Seul).



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

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

[Ashkan Paya]

Is this change going to be included in jclouds 2.0 ?

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

[jira] [Resolved] (JCLOUDS-1173) List method has different behavior on different cloud providers

[Andrew Gaul (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCLOUDS-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Gaul resolved JCLOUDS-1173.
--
   Resolution: Fixed
 Assignee: Andrew Gaul
Fix Version/s: 2.0.0

Glad 2.0.0-SNAPSHOT works for you.  Note that you do not have to call 
{{createDirectory}} -- directories are largely a jclouds fiction and blobstores 
actually support this functionality via prefix and delimiter.  Directories will 
go away in 2.1.0.

> List method has different behavior on different cloud providers
> ---
>
> Key: JCLOUDS-1173
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1173
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Affects Versions: 1.9.2
>Reporter: Ryan MacDowell
>Assignee: Andrew Gaul
> Fix For: 2.0.0
>
> Attachments: ListTest.java
>
>
> I'm seeing different behavior for the BlobStore list method of aws-s3 and 
> transient.  On aws-s3 the PageSet contains the directory itself and on azure 
> and transient it does not.  
> The example below shows that transient gives a size of 1 and aws-s3 gives a 
> size of 2 even though they are setup exactly the same.  
> {code:title=ListTest.java}
> import org.jclouds.ContextBuilder;
> import org.jclouds.blobstore.BlobStore;
> import org.jclouds.blobstore.BlobStoreContext;
> import org.jclouds.blobstore.domain.Blob;
> import com.amazonaws.auth.AWSCredentials;
> import com.amazonaws.auth.DefaultAWSCredentialsProviderChain;
> public class ListTest {
>   public static void main(String[] args) {
>   String containerName = "test.container";
>   String dataString = "testData";
>   String testDirectory = "testDirectory";
>   String blobName = "blob1";
>   AWSCredentials creds = new 
> DefaultAWSCredentialsProviderChain().getCredentials();
>   //Setup the contexts
>   BlobStoreContext transientContext = 
> ContextBuilder.newBuilder("transient")
>   .credentials(creds.getAWSAccessKeyId(), 
> creds.getAWSSecretKey())
>   .build(BlobStoreContext.class);
>   BlobStoreContext awsS3Context = 
> ContextBuilder.newBuilder("aws-s3")
>   .credentials(creds.getAWSAccessKeyId(), 
> creds.getAWSSecretKey())
>   .build(BlobStoreContext.class);
>   //Setup the blobstores
>   BlobStore transientStore = transientContext.getBlobStore();
>   BlobStore awsStore = awsS3Context.getBlobStore();
>   //Setup the container
>   transientStore.createContainerInLocation(null, containerName);
>   awsStore.createContainerInLocation(null, containerName);
>   //Setup the directories
>   transientStore.createDirectory(containerName, testDirectory);
>   awsStore.createDirectory(containerName, testDirectory);
>   //setup the blobs
>   Blob transientBlob = transientStore.blobBuilder(testDirectory 
> +"/" + blobName).build();
>   Blob awsBlob = awsStore.blobBuilder(testDirectory +"/" + 
> blobName).build();
>   //create the payloads
>   byte[] transientPayload = dataString.getBytes();
>   byte[] awsPayload = dataString.getBytes();
>   //set the payloads
>   transientBlob.setPayload(transientPayload);
>   awsBlob.setPayload(awsPayload);
>   //Upload the blobs
>   transientStore.putBlob(containerName, transientBlob);
>   awsStore.putBlob(containerName, awsBlob);
>   System.out.println("Directory size should be the same but is 
> not: transient + " + transientStore.list(containerName).size()
>   + ", aws = " + 
> awsStore.list(containerName).size());
>   }
> }
> {code}



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

[jira] [Commented] (JCLOUDS-1173) List method has different behavior on different cloud providers

[Ryan MacDowell (JIRA)]

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

Ryan MacDowell commented on JCLOUDS-1173:
-

Hi [~gaul], 
I just ran my test code with the 2.0.0-SNAPSHOT and it seems to have the 
correct behavior.  Thanks for looking into it!


> List method has different behavior on different cloud providers
> ---
>
> Key: JCLOUDS-1173
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1173
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Affects Versions: 1.9.2
>Reporter: Ryan MacDowell
> Attachments: ListTest.java
>
>
> I'm seeing different behavior for the BlobStore list method of aws-s3 and 
> transient.  On aws-s3 the PageSet contains the directory itself and on azure 
> and transient it does not.  
> The example below shows that transient gives a size of 1 and aws-s3 gives a 
> size of 2 even though they are setup exactly the same.  
> {code:title=ListTest.java}
> import org.jclouds.ContextBuilder;
> import org.jclouds.blobstore.BlobStore;
> import org.jclouds.blobstore.BlobStoreContext;
> import org.jclouds.blobstore.domain.Blob;
> import com.amazonaws.auth.AWSCredentials;
> import com.amazonaws.auth.DefaultAWSCredentialsProviderChain;
> public class ListTest {
>   public static void main(String[] args) {
>   String containerName = "test.container";
>   String dataString = "testData";
>   String testDirectory = "testDirectory";
>   String blobName = "blob1";
>   AWSCredentials creds = new 
> DefaultAWSCredentialsProviderChain().getCredentials();
>   //Setup the contexts
>   BlobStoreContext transientContext = 
> ContextBuilder.newBuilder("transient")
>   .credentials(creds.getAWSAccessKeyId(), 
> creds.getAWSSecretKey())
>   .build(BlobStoreContext.class);
>   BlobStoreContext awsS3Context = 
> ContextBuilder.newBuilder("aws-s3")
>   .credentials(creds.getAWSAccessKeyId(), 
> creds.getAWSSecretKey())
>   .build(BlobStoreContext.class);
>   //Setup the blobstores
>   BlobStore transientStore = transientContext.getBlobStore();
>   BlobStore awsStore = awsS3Context.getBlobStore();
>   //Setup the container
>   transientStore.createContainerInLocation(null, containerName);
>   awsStore.createContainerInLocation(null, containerName);
>   //Setup the directories
>   transientStore.createDirectory(containerName, testDirectory);
>   awsStore.createDirectory(containerName, testDirectory);
>   //setup the blobs
>   Blob transientBlob = transientStore.blobBuilder(testDirectory 
> +"/" + blobName).build();
>   Blob awsBlob = awsStore.blobBuilder(testDirectory +"/" + 
> blobName).build();
>   //create the payloads
>   byte[] transientPayload = dataString.getBytes();
>   byte[] awsPayload = dataString.getBytes();
>   //set the payloads
>   transientBlob.setPayload(transientPayload);
>   awsBlob.setPayload(awsPayload);
>   //Upload the blobs
>   transientStore.putBlob(containerName, transientBlob);
>   awsStore.putBlob(containerName, awsBlob);
>   System.out.println("Directory size should be the same but is 
> not: transient + " + transientStore.list(containerName).size()
>   + ", aws = " + 
> awsStore.list(containerName).size());
>   }
> }
> {code}



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

[jira] [Issue Comment Deleted] (JCLOUDS-1173) List method has different behavior on different cloud providers

[Ryan MacDowell (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCLOUDS-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ryan MacDowell updated JCLOUDS-1173:

Comment: was deleted

(was: Hi [~gaul], 
I just ran my test code with the 2.0.0-SNAPSHOT and it seems to have the 
correct behavior.  Thanks for looking into it!
)

> List method has different behavior on different cloud providers
> ---
>
> Key: JCLOUDS-1173
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1173
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Affects Versions: 1.9.2
>Reporter: Ryan MacDowell
> Attachments: ListTest.java
>
>
> I'm seeing different behavior for the BlobStore list method of aws-s3 and 
> transient.  On aws-s3 the PageSet contains the directory itself and on azure 
> and transient it does not.  
> The example below shows that transient gives a size of 1 and aws-s3 gives a 
> size of 2 even though they are setup exactly the same.  
> {code:title=ListTest.java}
> import org.jclouds.ContextBuilder;
> import org.jclouds.blobstore.BlobStore;
> import org.jclouds.blobstore.BlobStoreContext;
> import org.jclouds.blobstore.domain.Blob;
> import com.amazonaws.auth.AWSCredentials;
> import com.amazonaws.auth.DefaultAWSCredentialsProviderChain;
> public class ListTest {
>   public static void main(String[] args) {
>   String containerName = "test.container";
>   String dataString = "testData";
>   String testDirectory = "testDirectory";
>   String blobName = "blob1";
>   AWSCredentials creds = new 
> DefaultAWSCredentialsProviderChain().getCredentials();
>   //Setup the contexts
>   BlobStoreContext transientContext = 
> ContextBuilder.newBuilder("transient")
>   .credentials(creds.getAWSAccessKeyId(), 
> creds.getAWSSecretKey())
>   .build(BlobStoreContext.class);
>   BlobStoreContext awsS3Context = 
> ContextBuilder.newBuilder("aws-s3")
>   .credentials(creds.getAWSAccessKeyId(), 
> creds.getAWSSecretKey())
>   .build(BlobStoreContext.class);
>   //Setup the blobstores
>   BlobStore transientStore = transientContext.getBlobStore();
>   BlobStore awsStore = awsS3Context.getBlobStore();
>   //Setup the container
>   transientStore.createContainerInLocation(null, containerName);
>   awsStore.createContainerInLocation(null, containerName);
>   //Setup the directories
>   transientStore.createDirectory(containerName, testDirectory);
>   awsStore.createDirectory(containerName, testDirectory);
>   //setup the blobs
>   Blob transientBlob = transientStore.blobBuilder(testDirectory 
> +"/" + blobName).build();
>   Blob awsBlob = awsStore.blobBuilder(testDirectory +"/" + 
> blobName).build();
>   //create the payloads
>   byte[] transientPayload = dataString.getBytes();
>   byte[] awsPayload = dataString.getBytes();
>   //set the payloads
>   transientBlob.setPayload(transientPayload);
>   awsBlob.setPayload(awsPayload);
>   //Upload the blobs
>   transientStore.putBlob(containerName, transientBlob);
>   awsStore.putBlob(containerName, awsBlob);
>   System.out.println("Directory size should be the same but is 
> not: transient + " + transientStore.list(containerName).size()
>   + ", aws = " + 
> awsStore.list(containerName).size());
>   }
> }
> {code}



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

[jira] [Commented] (JCLOUDS-1173) List method has different behavior on different cloud providers

[Ryan MacDowell (JIRA)]

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

Ryan MacDowell commented on JCLOUDS-1173:
-

Hi [~gaul], 
I just ran my test code with the 2.0.0-SNAPSHOT and it seems to have the 
correct behavior.  Thanks for looking into it!


> List method has different behavior on different cloud providers
> ---
>
> Key: JCLOUDS-1173
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1173
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Affects Versions: 1.9.2
>Reporter: Ryan MacDowell
> Attachments: ListTest.java
>
>
> I'm seeing different behavior for the BlobStore list method of aws-s3 and 
> transient.  On aws-s3 the PageSet contains the directory itself and on azure 
> and transient it does not.  
> The example below shows that transient gives a size of 1 and aws-s3 gives a 
> size of 2 even though they are setup exactly the same.  
> {code:title=ListTest.java}
> import org.jclouds.ContextBuilder;
> import org.jclouds.blobstore.BlobStore;
> import org.jclouds.blobstore.BlobStoreContext;
> import org.jclouds.blobstore.domain.Blob;
> import com.amazonaws.auth.AWSCredentials;
> import com.amazonaws.auth.DefaultAWSCredentialsProviderChain;
> public class ListTest {
>   public static void main(String[] args) {
>   String containerName = "test.container";
>   String dataString = "testData";
>   String testDirectory = "testDirectory";
>   String blobName = "blob1";
>   AWSCredentials creds = new 
> DefaultAWSCredentialsProviderChain().getCredentials();
>   //Setup the contexts
>   BlobStoreContext transientContext = 
> ContextBuilder.newBuilder("transient")
>   .credentials(creds.getAWSAccessKeyId(), 
> creds.getAWSSecretKey())
>   .build(BlobStoreContext.class);
>   BlobStoreContext awsS3Context = 
> ContextBuilder.newBuilder("aws-s3")
>   .credentials(creds.getAWSAccessKeyId(), 
> creds.getAWSSecretKey())
>   .build(BlobStoreContext.class);
>   //Setup the blobstores
>   BlobStore transientStore = transientContext.getBlobStore();
>   BlobStore awsStore = awsS3Context.getBlobStore();
>   //Setup the container
>   transientStore.createContainerInLocation(null, containerName);
>   awsStore.createContainerInLocation(null, containerName);
>   //Setup the directories
>   transientStore.createDirectory(containerName, testDirectory);
>   awsStore.createDirectory(containerName, testDirectory);
>   //setup the blobs
>   Blob transientBlob = transientStore.blobBuilder(testDirectory 
> +"/" + blobName).build();
>   Blob awsBlob = awsStore.blobBuilder(testDirectory +"/" + 
> blobName).build();
>   //create the payloads
>   byte[] transientPayload = dataString.getBytes();
>   byte[] awsPayload = dataString.getBytes();
>   //set the payloads
>   transientBlob.setPayload(transientPayload);
>   awsBlob.setPayload(awsPayload);
>   //Upload the blobs
>   transientStore.putBlob(containerName, transientBlob);
>   awsStore.putBlob(containerName, awsBlob);
>   System.out.println("Directory size should be the same but is 
> not: transient + " + transientStore.list(containerName).size()
>   + ", aws = " + 
> awsStore.list(containerName).size());
>   }
> }
> {code}



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

Re: [jclouds/jclouds-labs] Configuration to deploy VMs from the Marketplace (#328)

[Ignasi Barrera]

Compute live tests are passing. Merged to master.

-- 
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/328#issuecomment-254502155

Re: [jclouds/jclouds-labs] Configuration to deploy VMs from the Marketplace (#328)

[Ignasi Barrera]

Closed #328.

-- 
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/328#event-827449451

Re: [jclouds/jclouds-labs] Configuration to deploy VMs from the Marketplace (#328)

[Ignasi Barrera]

@nacx pushed 1 commit.

2e38743  Null guards


-- 
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/328/files/3e5c92d9f3b859ad9d13f76c4894b7322962e891..2e3874301895557c366bc0c613605d68704f9305

[jclouds/jclouds-labs] Configuration to deploy VMs from the Marketplace (#328)

[Ignasi Barrera]

This also introduces a small change to store the jclouds group in the virtual 
machine tags so we can properly identify vms with custom names in the 
corresponding group.

With this commit we also have the version details (there is an extra api call 
needed to determine if the vm is from the Marketplace) in each image, and we 
can better fallback to the generic operating system (Linux/Windows) if we can't 
parse the specific version.

/cc @andreaturli 
You can view, comment on, or merge this pull request online at:

  https://github.com/jclouds/jclouds-labs/pull/328

-- Commit Summary --

  * Configuration to deploy VMs from the Marketplace
  * Configure jclouds group in virtualmachine tags

-- File Changes --

M 
azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/compute/AzureComputeServiceAdapter.java
 (21)
M 
azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/compute/functions/VMImageToImage.java
 (99)
M 
azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/compute/functions/VirtualMachineToNodeMetadata.java
 (8)
A 
azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/Plan.java 
(47)
M 
azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/VMImage.java 
(8)
M 
azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/Version.java 
(51)
M 
azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/VirtualMachine.java
 (37)
M 
azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/features/OSImageApi.java
 (10)
M 
azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/features/VirtualMachineApi.java
 (7)
M 
azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/features/VirtualMachineApiLiveTest.java
 (2)
M 
azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/features/VirtualMachineApiMockTest.java
 (166)
M azurecompute-arm/src/test/resources/createvirtualmachineresponse.json (5)
M azurecompute-arm/src/test/resources/virtualmachine.json (5)

-- Patch Links --

https://github.com/jclouds/jclouds-labs/pull/328.patch
https://github.com/jclouds/jclouds-labs/pull/328.diff

-- 
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/328