Re: [jclouds/jclouds] Use file.separator in tests instead of slash (#1021)

2016-10-13 Thread Zack Shoylev 
zack-shoylev commented on this pull request.



> @@ -584,12 +584,12 @@ public void testListMarkerPrefix() throws Exception {
   final String container = getContainerName();
   try {
  blobStore.createContainerInLocation(null, container);
- blobStore.putBlob(container, 
blobStore.blobBuilder("a/a").payload("").build());
- blobStore.putBlob(container, 
blobStore.blobBuilder("b/b").payload("").build());
- ListContainerOptions options = new 
ListContainerOptions().afterMarker("b/").recursive();
+ blobStore.putBlob(container, blobStore.blobBuilder("a" + 
File.separator + "a").payload("").build());

Valid point. I'll look into it some more tomorrow.

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

Re: [jclouds/jclouds] Use file.separator in tests instead of slash (#1021)

2016-10-13 Thread Andrew Gaul 
andrewgaul requested changes on this pull request.



> @@ -584,12 +584,12 @@ public void testListMarkerPrefix() throws Exception {
   final String container = getContainerName();
   try {
  blobStore.createContainerInLocation(null, container);
- blobStore.putBlob(container, 
blobStore.blobBuilder("a/a").payload("").build());
- blobStore.putBlob(container, 
blobStore.blobBuilder("b/b").payload("").build());
- ListContainerOptions options = new 
ListContainerOptions().afterMarker("b/").recursive();
+ blobStore.putBlob(container, blobStore.blobBuilder("a" + 
File.separator + "a").payload("").build());

This is backwards -- the Filesystem blobstore should map the path separator and 
not the tests.

-- 
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/1021#pullrequestreview-4187901

[jclouds/jclouds] Use file.separator in tests instead of slash (#1021)

2016-10-13 Thread Zack Shoylev 

You can view, comment on, or merge this pull request online at:

  https://github.com/jclouds/jclouds/pull/1021

-- Commit Summary --

  * Use file.separator in tests instead of slash

-- File Changes --

M 
blobstore/src/test/java/org/jclouds/blobstore/integration/internal/BaseContainerIntegrationTest.java
 (8)

-- Patch Links --

https://github.com/jclouds/jclouds/pull/1021.patch
https://github.com/jclouds/jclouds/pull/1021.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/pull/1021

[jclouds/jclouds] reduce payload for GET VirtualGuests (#1020)

2016-10-13 Thread Andrea Turli 
Using this objectMask instead of previous, json payload passes from 69.8 M
```
$ curl -uuser:api-key 
https://api.softlayer.com/rest/v3/SoftLayer_Account/VirtualGuests?objectMask=powerState%3BoperatingSystem.passwords%3Bdatacenter%3BbillingItem%3BblockDevices.diskImage%3BtagReferences
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
 12  145M   12 18.0M0 0   321k  0  0:07:44  0:00:57  0:06:47  401k
```

down to

```
$ curl -uuser:api-key 
https://api.softlayer.com/rest/v3/SoftLayer_Account/VirtualGuests?objectMask=powerState%3BoperatingSystem.passwords%3Bdatacenter%3BbillingItem%3BblockDevices.diskImage%3BtagReferences.tag.name
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100  277k  100  277k0 0  77421  0  0:00:03  0:00:03 --:--:-- 77426
```
from 145 MB to 277 KB, @aledsage and @nacx wdyt?
You can view, comment on, or merge this pull request online at:

  https://github.com/jclouds/jclouds/pull/1020

-- Commit Summary --

  * reduce payload for GET VirtualGuests

-- File Changes --

M 
providers/softlayer/src/main/java/org/jclouds/softlayer/features/AccountApi.java
 (2)
A providers/softlayer/src/test/resources/logback-test.xml (42)
D providers/softlayer/src/test/resources/logback.xml (34)

-- Patch Links --

https://github.com/jclouds/jclouds/pull/1020.patch
https://github.com/jclouds/jclouds/pull/1020.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/pull/1020

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

2016-10-13 Thread Andrew Gaul (JIRA) 

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

Andrew Gaul commented on JCLOUDS-1173:
--

[~ryanmacdow...@gmail.com] Can you test with 2.0.0-SNAPSHOT?  It includes 
several fixes for listing.

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

Jenkins build is back to normal : jclouds-cli #1181

2016-10-13 Thread jenkins-no-reply 
See

Jenkins build is back to normal : jclouds-guava-guice-compat » 19.0-rc1,3.0,OpenJDK 7 (latest) #208

2016-10-13 Thread jenkins-no-reply 
See

Build failed in Jenkins: jclouds-cli #1180

2016-10-13 Thread jenkins-no-reply 
See 

--
[...truncated 5099 lines...]
[INFO] --- maven-surefire-plugin:2.17:test (integration) @ jclouds-cli-assembly 
---
[JENKINS] Recording test results
[INFO] 
[INFO] --- duplicate-finder-maven-plugin:1.1.1:check (default) @ 
jclouds-cli-assembly ---
[INFO] Skipping duplicate-finder execution!
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.15:check (default) @ jclouds-cli-assembly 
---
[INFO] 
[INFO] --- modernizer-maven-plugin:1.4.0:modernizer (modernizer) @ 
jclouds-cli-assembly ---
[INFO] 
[INFO] --- maven-install-plugin:2.4:install (default-install) @ 
jclouds-cli-assembly ---
[INFO] Installing 

 to 
/home/jenkins/.m2/repository/org/apache/jclouds/cli/jclouds-cli-assembly/2.0.0-SNAPSHOT/jclouds-cli-assembly-2.0.0-SNAPSHOT.jar
[INFO] Installing 
 to 
/home/jenkins/.m2/repository/org/apache/jclouds/cli/jclouds-cli-assembly/2.0.0-SNAPSHOT/jclouds-cli-assembly-2.0.0-SNAPSHOT.pom
[INFO] Installing 

 to 
/home/jenkins/.m2/repository/org/apache/jclouds/cli/jclouds-cli-assembly/2.0.0-SNAPSHOT/jclouds-cli-assembly-2.0.0-SNAPSHOT-tests.jar
[INFO] Installing 

 to 
/home/jenkins/.m2/repository/org/apache/jclouds/cli/jclouds-cli-assembly/2.0.0-SNAPSHOT/jclouds-cli-assembly-2.0.0-SNAPSHOT-sources.jar
[INFO] Installing 

 to 
/home/jenkins/.m2/repository/org/apache/jclouds/cli/jclouds-cli-assembly/2.0.0-SNAPSHOT/jclouds-cli-assembly-2.0.0-SNAPSHOT.tar.gz
[INFO] Installing 

 to 
/home/jenkins/.m2/repository/org/apache/jclouds/cli/jclouds-cli-assembly/2.0.0-SNAPSHOT/jclouds-cli-assembly-2.0.0-SNAPSHOT.zip
[INFO] 
[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ 
jclouds-cli-assembly ---
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-assembly/2.0.0-SNAPSHOT/maven-metadata.xml
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-assembly/2.0.0-SNAPSHOT/maven-metadata.xml
 (2 KB at 30.9 KB/sec)
Uploading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-assembly/2.0.0-SNAPSHOT/jclouds-cli-assembly-2.0.0-20161013.182807-948.jar
Uploaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-assembly/2.0.0-SNAPSHOT/jclouds-cli-assembly-2.0.0-20161013.182807-948.jar
 (28 KB at 273.6 KB/sec)
Uploading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-assembly/2.0.0-SNAPSHOT/jclouds-cli-assembly-2.0.0-20161013.182807-948.pom
Uploaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-assembly/2.0.0-SNAPSHOT/jclouds-cli-assembly-2.0.0-20161013.182807-948.pom
 (12 KB at 131.5 KB/sec)
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-assembly/maven-metadata.xml
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-assembly/maven-metadata.xml
 (603 B at 14.4 KB/sec)
Uploading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-assembly/2.0.0-SNAPSHOT/maven-metadata.xml
Uploaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-assembly/2.0.0-SNAPSHOT/maven-metadata.xml
 (2 KB at 21.1 KB/sec)
Uploading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-assembly/maven-metadata.xml
Uploaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-assembly/maven-metadata.xml
 (603 B at 7.7 KB/sec)
Uploading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-assembly/2.0.0-SNAPSHOT/jclouds-cli-assembly-2.0.0-20161013.182807-948-tests.jar
Uploaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-assembly/2.0.0-SNAPSHOT/jclouds-cli-assembly-2.0.0-20161013.182807-948-tests.jar
 (12 KB at 128.5 KB/sec)
Uploading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/cli/jclouds-cli-assembly/2.0.0-SNAPSHOT/maven-metadata.xml
Uploaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/c

Build failed in Jenkins: jclouds-guava-guice-compat » 19.0-rc1,3.0,OpenJDK 7 (latest) #207

2016-10-13 Thread jenkins-no-reply 
See 


Changes:

[Ignasi Barrera] JCLOUDS-1182: Added Seoul and Mumbai regions to AWS

[Zack Shoylev] jclouds was not properly retrying on an expect: 100-continue PUT 
request

--
[...truncated 12710 lines...]
Test suite progress: tests succeeded: 70, failed: 1, skipped: 7.
Starting test 
testListMarkerAfterLastKey(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
[TestNG] Test 
testListMarkerAfterLastKey(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 3ms
Test suite progress: tests succeeded: 71, failed: 1, skipped: 7.
Starting test 
testListMarkerPrefix(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
[TestNG] Test 
testListMarkerPrefix(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 3ms
Test suite progress: tests succeeded: 72, failed: 1, skipped: 7.
Starting test 
containerExists(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
[TestNG] Test 
containerExists(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 2ms
Test suite progress: tests succeeded: 73, failed: 1, skipped: 7.
Starting test 
deleteContainerIfEmptyWithContents(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
*** allocated new container jenkins-blobstore13...
[TestNG] Test 
deleteContainerIfEmptyWithContents(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 3ms
Test suite progress: tests succeeded: 74, failed: 1, skipped: 7.
Starting test 
deleteContainerIfEmptyWithoutContents(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
*** allocated new container jenkins-blobstore14...
[TestNG] Test 
deleteContainerIfEmptyWithoutContents(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 3ms
Test suite progress: tests succeeded: 75, failed: 1, skipped: 7.
Starting test 
deleteContainerWithContents(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
*** allocated new container jenkins-blobstore15...
[TestNG] Test 
deleteContainerWithContents(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 4ms
Test suite progress: tests succeeded: 76, failed: 1, skipped: 7.
Starting test 
deleteContainerWithoutContents(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
*** allocated new container jenkins-blobstore16...
[TestNG] Test 
deleteContainerWithoutContents(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 2ms
Test suite progress: tests succeeded: 77, failed: 1, skipped: 7.
Starting test 
testDirectory(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
[TestNG] Test 
testDirectory(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 skipped.
Test suite progress: tests succeeded: 77, failed: 1, skipped: 8.
Starting test 
testListContainer(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
[TestNG] Test 
testListContainer(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 18ms
Test suite progress: tests succeeded: 78, failed: 1, skipped: 8.
Starting test 
testListContainerMarker(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
[TestNG] Test 
testListContainerMarker(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 40ms
Test suite progress: tests succeeded: 79, failed: 1, skipped: 8.
Starting test 
testListContainerMaxResults(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
[TestNG] Test 
testListContainerMaxResults(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 62ms
Test suite progress: tests succeeded: 80, failed: 1, skipped: 8.
Starting test 
testListContainerPrefix(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
[TestNG] Test 
testListContainerPrefix(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 40ms
Test suite progress: tests succeeded: 81, failed: 1, skipped: 8.
Starting test 
testListRootUsesDelimiter(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
[TestNG] Test 
testListRootUsesDelimiter(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 37ms
Test suite progress: tests succeeded: 82, failed: 1, skipped: 8.
Starting test 
testNotWithDetails(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
[TestNG] Test 
testNotWithDetails(org.jclouds.filesystem.integration.FilesystemContainerIntegrationTest)
 succeeded: 4ms
Test suite progress: tests succeeded: 83, failed: 1, skipped: 8.
Starting test 
testPutTwiceIsOkAndDoesntOverwrite(org.jclouds.filesystem.integration.FilesystemC

Jenkins build is back to stable : jclouds-labs-google #962

2016-10-13 Thread jenkins-no-reply 
See

Re: [jclouds/jclouds] JCLOUDS-1179 This also addresses the same problem with other providers (#1018)

2016-10-13 Thread Zack Shoylev 
merged

-- 
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/1018#issuecomment-253578451

Jenkins build is back to stable : jclouds-labs-google » jclouds Google Cloud Storage provider #962

2016-10-13 Thread jenkins-no-reply 
See

Re: [jclouds/jclouds] JCLOUDS-1179 This also addresses the same problem with other providers (#1018)

2016-10-13 Thread Zack Shoylev 
Closed #1018.

-- 
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/1018#event-822829025

[jira] [Resolved] (JCLOUDS-1179) putBlob doesn't handle 401s

2016-10-13 Thread Zack Shoylev (JIRA) 

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

Zack Shoylev resolved JCLOUDS-1179.
---
   Resolution: Fixed
Fix Version/s: 2.0.0

> putBlob doesn't handle 401s 
> 
>
> Key: JCLOUDS-1179
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1179
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Affects Versions: 1.9.2, 2.0.0
> Environment: Devstack on Ubuntu 14.04
>Reporter: Nick Howes
>Assignee: Zack Shoylev
>  Labels: openstack-swift
> Fix For: 2.0.0
>
>
> After the token used by jclouds expires, subsequent `putBlob` requests to 
> swift fail with 401.
> Unlike other operations, the `putBlob` command does not resolve this by 
> `POST`ing to keystone, but instead tries a few times to `PUT` the blob to 
> swift. Each request fails with a 401 and then it gives up.
> Other operations such as a get _will_ handle a retry by refreshing the auth 
> token, after which subsequent puts work (until the next expiry)
> Project to reproduce can be found here 
> https://github.com/UniversityofWarwick/jclouds-bug
> It should be noted that when running this script I have altered [token] 
> expiration in /etc/keystone/keystone.conf to be 2 seconds.



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

[jira] [Commented] (JCLOUDS-1179) putBlob doesn't handle 401s

2016-10-13 Thread ASF subversion and git services (JIRA) 

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

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

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

jclouds was not properly retrying on an expect: 100-continue PUT request that 
requires re-athentication because of java protocol code

JCLOUDS-1179 This fix also addresses the same problem with other providers

No currently working tests because of 
https://github.com/square/okhttp/issues/675

This is a common problem in other tools as well 
https://curl.haxx.se/mail/lib-2004-08/0002.html


> putBlob doesn't handle 401s 
> 
>
> Key: JCLOUDS-1179
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1179
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Affects Versions: 1.9.2, 2.0.0
> Environment: Devstack on Ubuntu 14.04
>Reporter: Nick Howes
>Assignee: Zack Shoylev
>  Labels: openstack-swift
> Fix For: 2.0.0
>
>
> After the token used by jclouds expires, subsequent `putBlob` requests to 
> swift fail with 401.
> Unlike other operations, the `putBlob` command does not resolve this by 
> `POST`ing to keystone, but instead tries a few times to `PUT` the blob to 
> swift. Each request fails with a 401 and then it gives up.
> Other operations such as a get _will_ handle a retry by refreshing the auth 
> token, after which subsequent puts work (until the next expiry)
> Project to reproduce can be found here 
> https://github.com/UniversityofWarwick/jclouds-bug
> It should be noted that when running this script I have altered [token] 
> expiration in /etc/keystone/keystone.conf to be 2 seconds.



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

Re: [jclouds/jclouds] 1182: Added Seoul and Mumbai regions to AWS (#1013)

2016-10-13 Thread Ignasi Barrera 
Pushed to master as 
[b06795eb](http://git-wip-us.apache.org/repos/asf/jclouds/commit/b06795eb).

-- 
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/1013#issuecomment-253567564

[jira] [Commented] (JCLOUDS-945) ListContainerOption's marker support in LocalBlobStore buggy

2016-10-13 Thread ASF subversion and git services (JIRA) 

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

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

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

JCLOUDS-945: ignore marker prefix test on GCS


> ListContainerOption's marker support in LocalBlobStore buggy
> 
>
> Key: JCLOUDS-945
> URL: https://issues.apache.org/jira/browse/JCLOUDS-945
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Reporter: Ka-Hing Cheung
>Assignee: Andrew Gaul
>  Labels: filesystem, transient
> Fix For: 2.0.0
>
>
> adding this test fails
> {code}
> --- 
> a/blobstore/src/test/java/org/jclouds/blobstore/integration/TransientBlobIntegrationTest.java
> +++ 
> b/blobstore/src/test/java/org/jclouds/blobstore/integration/TransientBlobIntegrationTest.java
> @@ -16,12 +16,34 @@
>   */
>  package org.jclouds.blobstore.integration;
>  
> +import org.jclouds.blobstore.BlobStore;
> +import org.jclouds.blobstore.domain.PageSet;
> +import org.jclouds.blobstore.domain.StorageMetadata;
>  import org.jclouds.blobstore.integration.internal.BaseBlobIntegrationTest;
> +import org.jclouds.blobstore.options.ListContainerOptions;
> +import org.jclouds.utils.TestUtils;
>  import org.testng.annotations.Test;
>  
> +import static org.assertj.core.api.Assertions.assertThat;
> +
>  @Test(groups = { "integration" })
>  public class TransientBlobIntegrationTest extends BaseBlobIntegrationTest {
> public TransientBlobIntegrationTest() {
>provider = "transient";
> }
> +
> +   @Test
> +   public void testListMarker() throws Exception {
> +  BlobStore blobStore = view.getBlobStore();
> +  final String container = getContainerName();
> +  try {
> + blobStore.createContainerInLocation(null, container);
> + blobStore.putBlob(container, 
> blobStore.blobBuilder("a/b").payload("").build());
> + ListContainerOptions options = new 
> ListContainerOptions().afterMarker("a/");
> + PageSet res = blobStore.list(container, 
> options);
> + assertThat(res).hasSize(1);
> +  } finally {
> + returnContainer(container);
> +  }
> +   }
>  }
> {code}



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

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

2016-10-13 Thread Ignasi Barrera (JIRA) 

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

Ignasi Barrera resolved JCLOUDS-1182.
-
   Resolution: Fixed
Fix Version/s: 2.0.0

> 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] 1182: Added Seoul and Mumbai regions to AWS (#1013)

2016-10-13 Thread Ignasi Barrera 
Closed #1013.

-- 
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/1013#event-822774512

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

2016-10-13 Thread ASF subversion and git services (JIRA) 

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

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

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

JCLOUDS-1182: Added Seoul and Mumbai regions to AWS


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

Jenkins build became unstable: jclouds-labs-google » jclouds Google Cloud Storage provider #961

2016-10-13 Thread jenkins-no-reply 
See

Jenkins build became unstable: jclouds-labs-google #961

2016-10-13 Thread jenkins-no-reply 
See

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

2016-10-13 Thread Ignasi Barrera 
nacx commented on this pull request.



> @@ -143,4 +143,17 @@ protected Server turnOnServer(String serverId) {
protected Server turnOFFServer(String serverId) {
   return api.serverApi().updateStatus(serverId, 
Server.UpdateStatus.create(Types.ServerAction.POWER_OFF, 
Types.ServerActionMethod.SOFTWARE));
}
+
+   protected Server GetRandomServerWithMonitoringPolicy() throws 
InterruptedException {
+  List result = api.serverApi().list();
+  for (Server server : result) {
+ Thread.sleep(2000);
+ server = api.serverApi().get(server.id());
+ if (server.monitoringPolicy() != null) {
+return server;
+ }
+  }
+
+  return null;

+1

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

Re: [jclouds/jclouds] JCLOUDS-1179 This also addresses the same problem with other providers (#1018)

2016-10-13 Thread Ignasi Barrera 
LGTM but before merging please amend the commit message and write a proper 
explanation and add the relevant links, for reference.

-- 
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/1018#issuecomment-253518993

[jira] [Commented] (JCLOUDS-1179) putBlob doesn't handle 401s

2016-10-13 Thread Zack Shoylev (JIRA) 

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

Zack Shoylev commented on JCLOUDS-1179:
---

[~nacx] Yep.

> putBlob doesn't handle 401s 
> 
>
> Key: JCLOUDS-1179
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1179
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Affects Versions: 1.9.2, 2.0.0
> Environment: Devstack on Ubuntu 14.04
>Reporter: Nick Howes
>Assignee: Zack Shoylev
>  Labels: openstack-swift
>
> After the token used by jclouds expires, subsequent `putBlob` requests to 
> swift fail with 401.
> Unlike other operations, the `putBlob` command does not resolve this by 
> `POST`ing to keystone, but instead tries a few times to `PUT` the blob to 
> swift. Each request fails with a 401 and then it gives up.
> Other operations such as a get _will_ handle a retry by refreshing the auth 
> token, after which subsequent puts work (until the next expiry)
> Project to reproduce can be found here 
> https://github.com/UniversityofWarwick/jclouds-bug
> It should be noted that when running this script I have altered [token] 
> expiration in /etc/keystone/keystone.conf to be 2 seconds.



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

[jira] [Commented] (JCLOUDS-1179) putBlob doesn't handle 401s

2016-10-13 Thread Ignasi Barrera (JIRA) 

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

Ignasi Barrera commented on JCLOUDS-1179:
-

Does it also happen with the Oracle JDK?

> putBlob doesn't handle 401s 
> 
>
> Key: JCLOUDS-1179
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1179
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Affects Versions: 1.9.2, 2.0.0
> Environment: Devstack on Ubuntu 14.04
>Reporter: Nick Howes
>Assignee: Zack Shoylev
>  Labels: openstack-swift
>
> After the token used by jclouds expires, subsequent `putBlob` requests to 
> swift fail with 401.
> Unlike other operations, the `putBlob` command does not resolve this by 
> `POST`ing to keystone, but instead tries a few times to `PUT` the blob to 
> swift. Each request fails with a 401 and then it gives up.
> Other operations such as a get _will_ handle a retry by refreshing the auth 
> token, after which subsequent puts work (until the next expiry)
> Project to reproduce can be found here 
> https://github.com/UniversityofWarwick/jclouds-bug
> It should be noted that when running this script I have altered [token] 
> expiration in /etc/keystone/keystone.conf to be 2 seconds.



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

[jclouds/jclouds] Fix base compute service live tests (#1019)

2016-10-13 Thread Ignasi Barrera 
* Improves the test order in the `BaseComputeServiceLiveTest` to avoid skipping 
so many tests when the first ones fail due to SSH connection failures.
* Improves the `BaseImageExtensionLiveTest` to let subclasses properly 
configure custom templates.
* Fixes the DigitalOcean2 live tests.

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

  https://github.com/jclouds/jclouds/pull/1019

-- Commit Summary --

  * Better order for the ComputeService live tests
  * Proper template config in the image extension live tests
  * Fix DigitalOcean2 live tests

-- File Changes --

M 
apis/ec2/src/test/java/org/jclouds/ec2/compute/extensions/EC2ImageExtensionLiveTest.java
 (6)
M 
compute/src/test/java/org/jclouds/compute/extensions/internal/BaseImageExtensionLiveTest.java
 (12)
M 
compute/src/test/java/org/jclouds/compute/internal/BaseComputeServiceLiveTest.java
 (48)
M 
providers/digitalocean2/src/main/java/org/jclouds/digitalocean2/domain/Action.java
 (4)

-- Patch Links --

https://github.com/jclouds/jclouds/pull/1019.patch
https://github.com/jclouds/jclouds/pull/1019.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/pull/1019

[jira] [Commented] (JCLOUDS-945) ListContainerOption's marker support in LocalBlobStore buggy

2016-10-13 Thread ASF subversion and git services (JIRA) 

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

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

Commit 50e6d4443343c19d037d35726597e0ff7608dede in jclouds's branch 
refs/heads/fix/AzureTemplateBuilderLiveTest from [~gaul]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=50e6d44 ]

JCLOUDS-945: fix local blobstore marker handling

Previously using prefix markers would not correctly find the next key.
Add test for this behavior.


> ListContainerOption's marker support in LocalBlobStore buggy
> 
>
> Key: JCLOUDS-945
> URL: https://issues.apache.org/jira/browse/JCLOUDS-945
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Reporter: Ka-Hing Cheung
>Assignee: Andrew Gaul
>  Labels: filesystem, transient
> Fix For: 2.0.0
>
>
> adding this test fails
> {code}
> --- 
> a/blobstore/src/test/java/org/jclouds/blobstore/integration/TransientBlobIntegrationTest.java
> +++ 
> b/blobstore/src/test/java/org/jclouds/blobstore/integration/TransientBlobIntegrationTest.java
> @@ -16,12 +16,34 @@
>   */
>  package org.jclouds.blobstore.integration;
>  
> +import org.jclouds.blobstore.BlobStore;
> +import org.jclouds.blobstore.domain.PageSet;
> +import org.jclouds.blobstore.domain.StorageMetadata;
>  import org.jclouds.blobstore.integration.internal.BaseBlobIntegrationTest;
> +import org.jclouds.blobstore.options.ListContainerOptions;
> +import org.jclouds.utils.TestUtils;
>  import org.testng.annotations.Test;
>  
> +import static org.assertj.core.api.Assertions.assertThat;
> +
>  @Test(groups = { "integration" })
>  public class TransientBlobIntegrationTest extends BaseBlobIntegrationTest {
> public TransientBlobIntegrationTest() {
>provider = "transient";
> }
> +
> +   @Test
> +   public void testListMarker() throws Exception {
> +  BlobStore blobStore = view.getBlobStore();
> +  final String container = getContainerName();
> +  try {
> + blobStore.createContainerInLocation(null, container);
> + blobStore.putBlob(container, 
> blobStore.blobBuilder("a/b").payload("").build());
> + ListContainerOptions options = new 
> ListContainerOptions().afterMarker("a/");
> + PageSet res = blobStore.list(container, 
> options);
> + assertThat(res).hasSize(1);
> +  } finally {
> + returnContainer(container);
> +  }
> +   }
>  }
> {code}



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

[jira] [Commented] (JCLOUDS-1158) DockerComputeServiceAdapter.getImage(String) doesn't work correctly for Docker on RHEL Atomic host

2016-10-13 Thread ASF subversion and git services (JIRA) 

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

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

Commit 26c060a0e899333bed560b1def58ac08634d12fd in jclouds's branch 
refs/heads/fix/AzureTemplateBuilderLiveTest from [~hendrens]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=26c060a ]

JCLOUDS-1185 Allow rangeIPv4 to be null

The default network of recently created projects have a null value for rangeIPv4
And all regions as subnets, which do have values for the rangeIPv4.

Fixes JCLOUDS-1158


> DockerComputeServiceAdapter.getImage(String) doesn't work correctly for 
> Docker on RHEL Atomic host
> --
>
> Key: JCLOUDS-1158
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1158
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-labs
>Reporter: Josef Cacek
>  Labels: docker
> Fix For: 2.0.0
>
>
> The 
> {{org.jclouds.docker.compute.strategy.DockerComputeServiceAdapter.getImage(String)}}
>  method doesn't find images when Docker from RHEL (Atomic) is used. The 
> reason is the returned Image {{repoTags}} field from the Docker server 
> contains also registry hostname. E.g.
> {code}
> "RepoTags":["docker.io/kwart/alpine-ext:3.3-ssh"]
> {code}
> The problem is in the condition used in this piece of code:
> {code}
> for (String tag : input.repoTags()) {
>if (tag.equals(imageIdOrName) || tag.equals(imageIdOrName + ":latest")) {
>   return true;
>}
> }
> {code}
> IMO, we should add also 2 more options to statement:
> {code}
> final String imageNameWithHostPrefix = "docker.io/" + imageIdOrName;
> for (String tag : input.repoTags()) {
>if (tag.equals(imageIdOrName) || tag.equals(imageIdOrName + ":latest")
>   || tag.equals(imageNameWithHostPrefix) || 
> tag.equals(imageNameWithHostPrefix + ":latest")) {
> ...
> {code}



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

[jira] [Commented] (JCLOUDS-1185) A Network rangeIPv4 may be null

2016-10-13 Thread ASF subversion and git services (JIRA) 

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

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

Commit 26c060a0e899333bed560b1def58ac08634d12fd in jclouds's branch 
refs/heads/fix/AzureTemplateBuilderLiveTest from [~hendrens]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=26c060a ]

JCLOUDS-1185 Allow rangeIPv4 to be null

The default network of recently created projects have a null value for rangeIPv4
And all regions as subnets, which do have values for the rangeIPv4.

Fixes JCLOUDS-1158


> A Network rangeIPv4 may be null
> ---
>
> Key: JCLOUDS-1185
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1185
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute, jclouds-labs-google
>Affects Versions: 2.0.0
>Reporter: Stuart Hendren
>  Labels: google-compute-engine
> Fix For: 2.0.0
>
>
> When creating an instance using the default network I get an NPE because the 
> rangeIPv4 for the default network is null. It seems this is a valid response 
> from the API now (it may not have been in the past, all legacy default 
> networks had an IP range).
> Relevant log snippets:
> Wire log of response:
> {noformat}
> 11:13:46.682 DEBUG [main]  jclouds.wire - << "{[\n]"
> 11:13:46.682 DEBUG [main]  jclouds.wire - << " "kind": "compute#network",[\n]"
> 11:13:46.682 DEBUG [main]  jclouds.wire - << " "id": 
> "2880581387445067991",[\n]"
> 11:13:46.682 DEBUG [main]  jclouds.wire - << " "creationTimestamp": 
> "2016-09-30T05:44:40.283-07:00",[\n]"
> 11:13:46.682 DEBUG [main]  jclouds.wire - << " "name": "default",[\n]"
> 11:13:46.682 DEBUG [main]  jclouds.wire - << " "description": "Default 
> network for the project",[\n]"
> 11:13:46.682 DEBUG [main]  jclouds.wire - << " "selfLink": 
> "https://www.googleapis.com/compute/v1/projects/project-name/global/networks/default",[\n]";
> 11:13:46.682 DEBUG [main]  jclouds.wire - << " "autoCreateSubnetworks": 
> true,[\n]"
> 11:13:46.682 DEBUG [main]  jclouds.wire - << " "subnetworks": [[\n]"
> 11:13:46.682 DEBUG [main]  jclouds.wire - << "  
> "https://www.googleapis.com/compute/v1/projects/project-name/regions/asia-east1/subnetworks/default",[\n]";
> 11:13:46.682 DEBUG [main]  jclouds.wire - << "  
> "https://www.googleapis.com/compute/v1/projects/project-name/regions/us-central1/subnetworks/default",[\n]";
> 11:13:46.682 DEBUG [main]  jclouds.wire - << "  
> "https://www.googleapis.com/compute/v1/projects/project-name/regions/europe-west1/subnetworks/default",[\n]";
> 11:13:46.682 DEBUG [main]  jclouds.wire - << "  
> "https://www.googleapis.com/compute/v1/projects/project-name/regions/us-west1/subnetworks/default",[\n]";
> 11:13:46.682 DEBUG [main]  jclouds.wire - << "  
> "https://www.googleapis.com/compute/v1/projects/project-name/regions/us-east1/subnetworks/default"[\n]";
> 11:13:46.682 DEBUG [main]  jclouds.wire - << " ][\n]"
> 11:13:46.682 DEBUG [main]  jclouds.wire - << "}[\n]"
> {noformat}
> NPE:
> {noformat}
> 11:13:47.589 ERROR [main]  org.jclouds.http.functions.ParseJson - Error 
> parsing input: Null rangeIPv4
> java.lang.NullPointerException: Null rangeIPv4
>   at 
> org.jclouds.googlecomputeengine.domain.AutoValue_Network.(AutoValue_Network.java:45)
>  ~[google-compute-engine-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
>   at 
> org.jclouds.googlecomputeengine.domain.Network.create(Network.java:58) 
> ~[google-compute-engine-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[na:1.8.0_73]
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[na:1.8.0_73]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[na:1.8.0_73]
>   at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_73]
>   at 
> com.google.common.reflect.Invokable$MethodInvokable.invokeInternal(Invokable.java:197)
>  ~[guava-19.0.jar:na]
>   at com.google.common.reflect.Invokable.invoke(Invokable.java:102) 
> ~[guava-19.0.jar:na]
>   at 
> org.jclouds.json.internal.DeserializationConstructorAndReflectiveTypeAdapterFactory$DeserializeIntoParameterizedConstructor.newInstance(DeserializationConstructorAndReflectiveTypeAdapterFactory.java:224)
>  ~[jclouds-core-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
>   at 
> org.jclouds.json.internal.DeserializationConstructorAndReflectiveTypeAdapterFactory$DeserializeIntoParameterizedConstructor.read(DeserializationConstructorAndReflectiveTypeAdapterFactory.java:204)
>  ~[jclouds-core-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
>   at com.google.gson.Gson.fromJson(Gson.java:810) ~[gson-2.3.1.jar:na]
>   at com.google.gson.Gson.fromJson(Gson.java:775) ~

Re: [jclouds/jclouds-labs] Fix AzureTemplateBuilderLiveTest and AzureComputeServiceLiveTest (#323)

2016-10-13 Thread Andrea Turli 
@andreaturli pushed 1 commit.

2266331  Fixed Azure ARM Image extension


-- 
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/323/files/d9600c00f8ff2ffdb925038ff3dd4cee371b2ab3..226633157222d11d6a708fedd5581e61de8672df