[jira] [Assigned] (JCLOUDS-704) Unable to create Virtual guest in SoftLayer

[Ignasi Barrera (JIRA)]

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

Ignasi Barrera reassigned JCLOUDS-704:
--

Assignee: Andrea Turli

> Unable to create Virtual guest in SoftLayer
> ---
>
> Key: JCLOUDS-704
> URL: https://issues.apache.org/jira/browse/JCLOUDS-704
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute
>Affects Versions: 1.8.1
> Environment: provider: Softlayer
> JDK:  1.7
> provider/softlayer code deployed from github branch master.
>Reporter: Jaiganesh Mathaiyan
>Assignee: Andrea Turli
>Priority: Blocker
>
> Error while creating a virtual guest in softlayer
> 2014-09-04 15:29:45,812 [main] DEBUG SLF4JLogger Sending request -1350657235: 
> POST 
> https://api.softlayer.com/rest/v3/SoftLayer_Product_Order/placeOrder.json 
> HTTP/1.1
> 2014-09-04 15:29:48,963 [main] DEBUG SLF4JLogger Receiving response 
> -1350657235: HTTP/1.1 200 OK
> java.lang.IndexOutOfBoundsException: position (0) must be less than the 
> number of elements that remained (0)
> at com.google.common.collect.Iterators.get(Iterators.java:813)
> at com.google.common.collect.Iterables.get(Iterables.java:728)
> at 
> org.jclouds.softlayer.compute.strategy.SoftLayerComputeServiceAdapter.createNodeWithGroupEncodedIntoName(SoftLayerComputeServiceAdapter.java:129)
>   
> Code snippet
> //inst is a local object to contain the template information
> inst.setArchitecture(ArchitectureEnum.BIT64.getNumber());
> inst.setVcpus(1);
> inst.setMemory(512);
> inst.setZone("138124");
> inst.setName("abcd");
> inst.setOsFamily("RHEL");
> .
> .
> .
> templateBuilder = templateBuilder.from("minRam="
>   + (int) inst.getMemory()
>   + ",os64Bit="
>   + inst.getArchitecture().equals(
>   
> ArchitectureEnum.BIT64.getNumber()) + ",minCores="
>   + inst.getVcpus() + ",osFamily=" + 
> inst.getOsFamily()
>   + ",locationId=" + location);
>   templateBuilder = templateBuilder.smallest();
> .
> .
> .
> template.getOptions().as(SoftLayerTemplateOptions.class).domainName("me.org");
> 
> template.getOptions().as(SoftLayerTemplateOptions.class).networks("253152","260523");
> NodeAndInitialCredentials guest = 
> adapter.createNodeWithGroupEncodedIntoName(group, name, template);



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

Jenkins build is back to normal : jclouds-labs-openstack #449

[jenkins-no-reply]

See 

Jenkins build is back to normal : jclouds-labs-openstack » jclouds openstack-swift api #449

[jenkins-no-reply]

See 

Re: [jclouds] JCLOUDS-706: Upgrade Azure API to 2012-02-12 (#508)

[BuildHive]

[jclouds » jclouds 
#1596](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1596/) UNSTABLE
Looks like there's a problem with this pull request
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/508#issuecomment-54575667

Jenkins build is still unstable: jclouds » jclouds #1596

[BuildHive]

See 

[jira] [Commented] (JCLOUDS-641) rackspace-cloudfiles-us integration tests fail

[Andrew Gaul (JIRA)]

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

Andrew Gaul commented on JCLOUDS-641:
-

[~jdaggett] Any updates on this issue?  I consider this a possible blocker for 
1.8.1 and certainly for any further progress integrating the new swift provider 
in core.

> rackspace-cloudfiles-us integration tests fail
> --
>
> Key: JCLOUDS-641
> URL: https://issues.apache.org/jira/browse/JCLOUDS-641
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-labs-openstack
>Affects Versions: 1.8.0
>Reporter: Andrew Gaul
>Assignee: Jeremy Daggett
>  Labels: swift
>
> {noformat}
> $ mvn integration-test -pl :rackspace-cloudfiles-us -Plive  
> -Dtest.rackspace-cloudfiles-us.identity="${JCLOUDS_IDENTITY}"  
> -Dtest.rackspace-cloudfiles-us.credential="${JCLOUDS_CREDENTIAL}"
> ...
> Failed tests:
>   
> CloudFilesUSBlobIntegrationLiveTest>BaseBlobIntegrationTest.testGetRange:373 
> » NullPointer
>   
> CloudFilesUSBlobIntegrationLiveTest>BaseBlobIntegrationTest.deleteObject:440->BaseBlobIntegrationTest.assertContainerEmptyDeleting:456
>  deleting qu?stion, we still have 1 blobs left in container gaul-blobstore0, 
> using encoding UTF-8 expected [0] but found [1]
>   
> CloudFilesUSBlobIntegrationLiveTest>BaseBlobIntegrationTest.testMetadata:605->BaseBlobIntegrationTest.validateMetadata:621
>  » NullPointer
>   
> CloudFilesUSBlobIntegrationLiveTest>BaseBlobIntegrationTest.deleteObject:440->BaseBlobIntegrationTest.assertContainerEmptyDeleting:456
>  deleting path/foo, we still have 1 blobs left in container gaul-blobstore2, 
> using encoding UTF-8 expected [0] but found [1]
>   
> CloudFilesUSBlobIntegrationLiveTest>BaseBlobIntegrationTest.testGetIfModifiedSince:213->BaseBlobIntegrationTest.addObjectAndValidateContent:398->BaseBlobStoreIntegrationTest.validateContent:293
>  null
>   
> CloudFilesUSBlobIntegrationLiveTest>BaseBlobIntegrationTest.testGetIfNoneMatch:348->BaseBlobStoreIntegrationTest.validateContent:293
>  null
>   
> CloudFilesUSBlobIntegrationLiveTest>BaseBlobIntegrationTest.testPutObjectStream:516
>  » HttpResponse
>   
> CloudFilesUSContainerIntegrationLiveTest>BaseContainerIntegrationTest.deleteContainerIfEmptyWithContents:301
>  » IllegalState
>   
> CloudFilesUSBlobIntegrationLiveTest>BaseBlobIntegrationTest.deleteObject:438->BaseBlobStoreIntegrationTest.addBlobToContainer:269->BaseBlobStoreIntegrationTest.addBlobToContainer:281
>  » HttpResponse
>   
> CloudFilesUSBlobIntegrationLiveTest>BaseBlobIntegrationTest.deleteObject:440->BaseBlobIntegrationTest.assertContainerEmptyDeleting:456
>  deleting p|pe, we still have 3 blobs left in container gaul-blobstore5, 
> using encoding UTF-8 expected [0] but found [3]
>   
> CloudFilesUSBlobSignerLiveTest>BaseBlobSignerLiveTest.testSignGetUrlWithTime:92
>  » Authorization
>   
> CloudFilesUSBlobSignerLiveTest>BaseBlobSignerLiveTest.testSignPutUrlWithTime:140
>  » Authorization
>   
> CloudFilesUSContainerIntegrationLiveTest>BaseContainerIntegrationTest.testDirectory:206
>  []
>   
> CloudFilesUSContainerIntegrationLiveTest>BaseContainerIntegrationTest.testListContainerPrefix:241
>  expected [10] but found [0]
>   
> CloudFilesUSContainerIntegrationLiveTest>BaseContainerIntegrationTest.testListContainerMarker:119->BaseContainerIntegrationTest.addAlphabetUnderRoot:340->BaseContainerIntegrationTest.assertContainerSize:345->BaseBlobStoreIntegrationTest.assertConsistencyAware:248->BaseBlobStoreIntegrationTest.assertConsistencyAware:235
>  expected [26] but found [19]
>   
> CloudFilesUSContainerIntegrationLiveTest>BaseContainerIntegrationTest.testListContainerMaxResults:252->BaseContainerIntegrationTest.addAlphabetUnderRoot:340->BaseContainerIntegrationTest.assertContainerSize:345->BaseBlobStoreIntegrationTest.assertConsistencyAware:248->BaseBlobStoreIntegrationTest.assertConsistencyAware:235
>  expected [26] but found [0]
>   
> CloudFilesUSContainerIntegrationLiveTest>SwiftContainerIntegrationLiveTest.testListRootUsesDelimiter:50
>  expected [16] but found [13] expected [true] but found [false]
> Tests run: 55, Failures: 17, Errors: 0, Skipped: 6
> {noformat}



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

Re: [jclouds] JCLOUDS-706: Upgrade Azure API to 2012-02-12 (#508)

[CloudBees pull request builder plugin]

[jclouds-pull-requests 
#1146](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1146/) SUCCESS
This pull request looks good

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/508#issuecomment-54573733

Build failed in Jenkins: jclouds-labs-openstack #448

[jenkins-no-reply]

See 

--
[...truncated 1476 lines...]
[WARNING] 
:
 warning: Cannot find annotation method 'value()' in type 'GuardedBy'
[WARNING] 
:
 warning: Cannot find annotation method 'value()' in type 'GuardedBy'
[WARNING] 
:
 warning: Cannot find annotation method 'value()' in type 'GuardedBy'
[WARNING] 
:
 warning: Cannot find annotation method 'value()' in type 'GuardedBy'
[WARNING] 
:
 warning: Cannot find annotation method 'value()' in type 'GuardedBy'
[WARNING] 
:
 warning: Cannot find annotation method 'value()' in type 'GuardedBy'
[WARNING] 
:
 warning: Cannot find annotation method 'value()' in type 'GuardedBy'
[WARNING] 
:
 warning: Cannot find annotation method 'value()' in type 'GuardedBy'
[WARNING] 
:
 warning: Cannot find annotation method 'value()' in type 'GuardedBy'
[WARNING] 
:
 warning: Cannot find annotation method 'value()' in type 'GuardedBy'
[WARNING] 
:
 warning: Cannot find annotation method 'value()' in type 'GuardedBy'
[WARNING] 
:
 warning: Cannot find annotation method 'value()' in type 'GuardedBy'
[WARNING] 
:
 warning: Cannot find annotation method 'value()' in type 'GuardedBy'
[WARNING] 
:
 warning: Cannot find annotation method 'value()' in type 'GuardedBy'
[WARNING] 
:
 warning: Cannot find annotation method 'value()' in type 'GuardedBy'
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-source-plugin:2.2:jar-no-fork (attach-sources) @ 
openstack-neutron ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-surefire-plugin:2.17:test (integration) @ openstack-neutron ---
[JENKINS] Recording test results[INFO] 
[INFO] --- maven-duplicate-finder-plugin:1.0.5:check (default) @ 
openstack-neutron ---

[INFO] Checking compile classpath
[INFO] Checking runtime classpath
[INFO] Checking test classpath
[INFO] 
[INFO] --- maven-install-plugin:2.4:install (default-install) @ 
openstack-neutron ---
[INFO] Installing 

Build failed in Jenkins: jclouds-labs-openstack » jclouds openstack-swift api #448

[jenkins-no-reply]

See 


--
[INFO] 
[INFO] 
[INFO] Building jclouds openstack-swift api 2.0.0-SNAPSHOT
[INFO] 
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
https://repository-jclouds.forge.cloudbees.com/snapshot/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
http://repository.apache.org/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/maven-metadata.xml
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/maven-metadata.xml
 (2 KB at 6.1 KB/sec)
Downloaded: 
http://repository.apache.org/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/maven-metadata.xml
 (2 KB at 4.1 KB/sec)
Downloading: 
https://repository-jclouds.forge.cloudbees.com/snapshot/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/jclouds-blobstore-2.0.0-20140905.003142-33.pom
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/jclouds-blobstore-2.0.0-20140905.003142-33.pom
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/jclouds-blobstore-2.0.0-20140905.003142-33.pom
 (4 KB at 18.5 KB/sec)
Downloading: 
https://repository-jclouds.forge.cloudbees.com/snapshot/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
http://repository.apache.org/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/maven-metadata.xml
Downloaded: 
http://repository.apache.org/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/maven-metadata.xml
 (2 KB at 6.8 KB/sec)
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/maven-metadata.xml
 (2 KB at 6.6 KB/sec)
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/jclouds-blobstore-2.0.0-20140905.003142-33.jar
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/jclouds-blobstore-2.0.0-20140905.003142-33-tests.jar
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/jclouds-blobstore-2.0.0-20140905.003142-33.jar
 (169 KB at 128.8 KB/sec)
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/jclouds-blobstore-2.0.0-20140905.003142-33-tests.jar
 (114 KB at 86.8 KB/sec)
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ openstack-swift ---
[INFO] Deleting 

[INFO] 
[INFO] --- maven-enforcer-plugin:1.1.1:enforce (enforce-banned-dependencies) @ 
openstack-swift ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.1.1:enforce (enforce-java) @ openstack-swift 
---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
openstack-swift ---
Downloading: 
https://repository-jclouds.forge.cloudbees.com/snapshot/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
http://repository.apache.org/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/maven-metadata.xml
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/maven-metadata.xml
 (2 KB at 1.8 KB/sec)
Downloaded: 
http://repository.apache.org/snapshots/org/apache/jclouds/jclouds-blobstore/2.0.0-SNAPSHOT/maven-metadata.xml
 (2 KB at 1.6 KB/sec)
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
openstack-swift ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
openstack-swift ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 44 source files to 

Jenkins build is back to stable : jclouds » jclouds compute core #2741

[jenkins-no-reply]

See 

Jenkins build is back to stable : jclouds #2741

[jenkins-no-reply]

See 

Jenkins build is still unstable: jclouds » jclouds #1595

[BuildHive]

See 

Re: [jclouds-labs-google] JCLOUDS-458:Added Blobstore Abstraction (#48)

[Andrew Gaul]

> +import org.jclouds.googlecloudstorage.options.ListObjectOptions;
> +import org.jclouds.http.HttpResponseException;
> +import org.jclouds.http.internal.PayloadEnclosingImpl;
> +
> +import com.google.common.base.Charsets;
> +import com.google.common.base.Function;
> +import com.google.common.base.Supplier;
> +import com.google.common.collect.ImmutableSet;
> +import com.google.common.collect.Iterables;
> +import com.google.common.hash.HashCode;
> +import com.google.inject.Inject;
> +import com.google.inject.Provider;
> +
> +@Singleton
> +public class GCSBlobStore extends BaseBlobStore {
> +   private final String PROJECT_ID = 
> System.getProperty("test.google-cloud-storage.project-number");

Also how would this work if a user had multiple GCS BlobStore with different 
project numbers?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/48/files#r17153263

Re: [jclouds-labs-google] JCLOUDS-458:Added Blobstore Abstraction (#48)

[Andrew Gaul]

> +import org.jclouds.googlecloudstorage.options.ListObjectOptions;
> +import org.jclouds.http.HttpResponseException;
> +import org.jclouds.http.internal.PayloadEnclosingImpl;
> +
> +import com.google.common.base.Charsets;
> +import com.google.common.base.Function;
> +import com.google.common.base.Supplier;
> +import com.google.common.collect.ImmutableSet;
> +import com.google.common.collect.Iterables;
> +import com.google.common.hash.HashCode;
> +import com.google.inject.Inject;
> +import com.google.inject.Provider;
> +
> +@Singleton
> +public class GCSBlobStore extends BaseBlobStore {
> +   private final String PROJECT_ID = 
> System.getProperty("test.google-cloud-storage.project-number");

Should the main code rely on a test property?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/48/files#r17153105

Re: [jclouds] JCLOUDS-706: Upgrade Azure API to 2012-02-12 (#508)

[CloudBees pull request builder plugin]

[jclouds-pull-requests-java-6 
#57](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests-java-6/57/) 
SUCCESS
This pull request looks good

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/508#issuecomment-54566458

Re: [jclouds] JCLOUDS-706: Upgrade Azure API to 2012-02-12 (#508)

[Andrew Gaul]

Successfully ran integration tests.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/508#issuecomment-54566376

[jclouds] JCLOUDS-706: Upgrade Azure API to 2012-02-12 (#508)

[Andrew Gaul]

This will allow use of Azure after August 2015:

http://blogs.msdn.com/b/windowsazurestorage/archive/2014/08/05/microsoft-azure-storage-service-version-removal.aspx
You can merge this Pull Request by running:

  git pull https://github.com/andrewgaul/jclouds azure-version

Or you can view, comment on it, or merge it online at:

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

-- Commit Summary --

  * JCLOUDS-706: Upgrade Azure API to 2012-02-12

-- File Changes --

M providers/azureblob/pom.xml (2)
M 
providers/azureblob/src/main/java/org/jclouds/azureblob/AzureBlobApiMetadata.java
 (2)
M 
providers/azureblob/src/main/java/org/jclouds/azureblob/AzureBlobAsyncClient.java
 (2)
M 
providers/azureblob/src/test/java/org/jclouds/azureblob/AzureBlobAsyncClientTest.java
 (38)
M 
providers/azureblob/src/test/java/org/jclouds/azureblob/blobstore/AzureBlobRequestSignerTest.java
 (12)

-- Patch Links --

https://github.com/jclouds/jclouds/pull/508.patch
https://github.com/jclouds/jclouds/pull/508.diff

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/508

[jira] [Created] (JCLOUDS-706) Upgrade Azure API version to 2012-02-12

[Andrew Gaul (JIRA)]

Andrew Gaul created JCLOUDS-706:
---

 Summary: Upgrade Azure API version to 2012-02-12
 Key: JCLOUDS-706
 URL: https://issues.apache.org/jira/browse/JCLOUDS-706
 Project: jclouds
  Issue Type: Improvement
  Components: jclouds-blobstore
Affects Versions: 1.8.0
Reporter: Andrew Gaul
Assignee: Andrew Gaul


Microsoft plans to remove support for the API version jclouds depends on:

http://blogs.msdn.com/b/windowsazurestorage/archive/2014/08/05/microsoft-azure-storage-service-version-removal.aspx



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

Jenkins build became unstable: jclouds » jclouds #1594

[BuildHive]

See 

Re: [jclouds] Remove ByteStreams2.asByteSource (#507)

[Andrew Gaul]

Pushed to master as 8613967820b3918a8b930f41179205675925f5d6.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/507#issuecomment-54563906

Re: [jclouds] Use try-with-resources where appropriate (#506)

[Andrew Gaul]

Also agree that we should not change examples until 2.0 releases.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/506#issuecomment-54555176

Re: [jclouds] Use try-with-resources where appropriate (#506)

[Andrew Gaul]

We could defer merging this until later in the 2.0 cycle to minimize 
backporting pain.  maven-compiler-plugin enforces the correct subset of 
language features but cannot enforce the correct subset of library interfaces.  
animal-sniffer-maven-plugin does this library enforcement but I have had poor 
experiences configuring it.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/506#issuecomment-54555089

[jira] [Updated] (JCLOUDS-704) Unable to create Virtual guest in SoftLayer

[Jaiganesh Mathaiyan (JIRA)]

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

Jaiganesh Mathaiyan updated JCLOUDS-704:

Description: 
Error while creating a virtual guest in softlayer
2014-09-04 15:29:45,812 [main] DEBUG SLF4JLogger Sending request -1350657235: 
POST https://api.softlayer.com/rest/v3/SoftLayer_Product_Order/placeOrder.json 
HTTP/1.1
2014-09-04 15:29:48,963 [main] DEBUG SLF4JLogger Receiving response 
-1350657235: HTTP/1.1 200 OK
java.lang.IndexOutOfBoundsException: position (0) must be less than the number 
of elements that remained (0)
at com.google.common.collect.Iterators.get(Iterators.java:813)
at com.google.common.collect.Iterables.get(Iterables.java:728)
at 
org.jclouds.softlayer.compute.strategy.SoftLayerComputeServiceAdapter.createNodeWithGroupEncodedIntoName(SoftLayerComputeServiceAdapter.java:129)
  


Code snippet

//inst is a local object to contain the template information
inst.setArchitecture(ArchitectureEnum.BIT64.getNumber());
inst.setVcpus(1);
inst.setMemory(512);
inst.setZone("138124");
inst.setName("abcd");
inst.setOsFamily("RHEL");
.
.
.
templateBuilder = templateBuilder.from("minRam="
+ (int) inst.getMemory()
+ ",os64Bit="
+ inst.getArchitecture().equals(

ArchitectureEnum.BIT64.getNumber()) + ",minCores="
+ inst.getVcpus() + ",osFamily=" + 
inst.getOsFamily()
+ ",locationId=" + location);
templateBuilder = templateBuilder.smallest();

.
.
.
template.getOptions().as(SoftLayerTemplateOptions.class).domainName("me.org");

template.getOptions().as(SoftLayerTemplateOptions.class).networks("253152","260523");

NodeAndInitialCredentials guest = 
adapter.createNodeWithGroupEncodedIntoName(group, name, template);


  was:
Error while creating a virtual guest in softlayer
2014-09-04 15:29:45,812 [main] DEBUG SLF4JLogger Sending request -1350657235: 
POST https://api.softlayer.com/rest/v3/SoftLayer_Product_Order/placeOrder.json 
HTTP/1.1
2014-09-04 15:29:48,963 [main] DEBUG SLF4JLogger Receiving response 
-1350657235: HTTP/1.1 200 OK
java.lang.IndexOutOfBoundsException: position (0) must be less than the number 
of elements that remained (0)
at com.google.common.collect.Iterators.get(Iterators.java:813)
at com.google.common.collect.Iterables.get(Iterables.java:728)
at 
org.jclouds.softlayer.compute.strategy.SoftLayerComputeServiceAdapter.createNodeWithGroupEncodedIntoName(SoftLayerComputeServiceAdapter.java:129)
at 
com.cisco.vnmc.hcloud.cpm.service.providers.softlayer.SLProviderOps.getLocation(SLProviderOps.java:118)
at 
com.cisco.vnmc.hcloud.cpm.service.providers.softlayer.SLProviderOps.getRegions(SLProviderOps.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)


Code snippet

//inst is a local object to contain the template information
inst.setArchitecture(ArchitectureEnum.BIT64.getNumber());
inst.setVcpus(1);
inst.setMemory(512);
inst.setZone("138124");
inst.setName("abcd");
inst.setOsFamily("RHEL");
.
.
.
templateBuilder = templateBuilder.from("minRam="
+ (int) inst.getMemory()
+ ",os64Bit="
+ inst.getArchitecture().equals(

ArchitectureEnum.BIT64.getNumber()) + ",minCores="
+ inst.getVcpus() + ",osFamily=" + 
inst.getOsFamily()
+ ",locationId=" + location);
templateBuilder = templateBuilder.smallest();

.
.
.
template.getOptions().as(SoftLayerTemplateOptions.class).domainName("me.org");

template.getOptions().as(SoftLayerTemplateOptions.class).networks("253152","260523");

NodeAndInitialCredentials guest = 
adapter.createNodeWithGroupEncodedIntoName(group, name, template);



> Unable to create Virtual guest in SoftLayer
> ---
>
> Key: JCLOUDS-704
> URL: https://issues.apache.org/jira/browse/JCLOUDS-704
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute
>Affects Versions: 1.8.1
> Environment: provider: Softlayer
> JDK:  1.7
> provider/softlayer code deployed from github branch master.
>Reporter: Jaiganesh Mathaiyan
>Priority: Blocker
>
> Error while creating a virtual guest in softlayer
> 2014-09-04 15:29:45,812 [main] DEBUG SLF4JLogger Sending request -1350657235: 
> POST 
> https://api.softlayer.com/rest/v3/SoftLayer_Product_Order/placeOrder.json 
> HTTP/1.1
> 2014-09-04 15:29:48,963 [main] DEBUG SLF4JLogger Receiving res

[jira] [Created] (JCLOUDS-705) Support OpenStack Swift Storage Policies

[Jeremy Daggett (JIRA)]

Jeremy Daggett created JCLOUDS-705:
--

 Summary: Support OpenStack Swift Storage Policies
 Key: JCLOUDS-705
 URL: https://issues.apache.org/jira/browse/JCLOUDS-705
 Project: jclouds
  Issue Type: New Feature
  Components: jclouds-labs-openstack
Reporter: Jeremy Daggett
Assignee: Jeremy Daggett


http://docs.openstack.org/developer/swift/overview_policies.html



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

[jira] [Updated] (JCLOUDS-704) Unable to create Virtual guest in SoftLayer

[Andrew Phillips (JIRA)]

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

Andrew Phillips updated JCLOUDS-704:

Summary: Unable to create Virtual guest in SoftLayer  (was: Create Virtual 
guest throws error)

> Unable to create Virtual guest in SoftLayer
> ---
>
> Key: JCLOUDS-704
> URL: https://issues.apache.org/jira/browse/JCLOUDS-704
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute
>Affects Versions: 1.8.1
> Environment: provider: Softlayer
> JDK:  1.7
> provider/softlayer code deployed from github branch master.
>Reporter: Jaiganesh Mathaiyan
>Priority: Blocker
>
> Error while creating a virtual guest in softlayer
> 2014-09-04 15:29:45,812 [main] DEBUG SLF4JLogger Sending request -1350657235: 
> POST 
> https://api.softlayer.com/rest/v3/SoftLayer_Product_Order/placeOrder.json 
> HTTP/1.1
> 2014-09-04 15:29:48,963 [main] DEBUG SLF4JLogger Receiving response 
> -1350657235: HTTP/1.1 200 OK
> java.lang.IndexOutOfBoundsException: position (0) must be less than the 
> number of elements that remained (0)
> at com.google.common.collect.Iterators.get(Iterators.java:813)
> at com.google.common.collect.Iterables.get(Iterables.java:728)
> at 
> org.jclouds.softlayer.compute.strategy.SoftLayerComputeServiceAdapter.createNodeWithGroupEncodedIntoName(SoftLayerComputeServiceAdapter.java:129)
> at 
> com.cisco.vnmc.hcloud.cpm.service.providers.softlayer.SLProviderOps.getLocation(SLProviderOps.java:118)
> at 
> com.cisco.vnmc.hcloud.cpm.service.providers.softlayer.SLProviderOps.getRegions(SLProviderOps.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> Code snippet
> //inst is a local object to contain the template information
> inst.setArchitecture(ArchitectureEnum.BIT64.getNumber());
> inst.setVcpus(1);
> inst.setMemory(512);
> inst.setZone("138124");
> inst.setName("abcd");
> inst.setOsFamily("RHEL");
> .
> .
> .
> templateBuilder = templateBuilder.from("minRam="
>   + (int) inst.getMemory()
>   + ",os64Bit="
>   + inst.getArchitecture().equals(
>   
> ArchitectureEnum.BIT64.getNumber()) + ",minCores="
>   + inst.getVcpus() + ",osFamily=" + 
> inst.getOsFamily()
>   + ",locationId=" + location);
>   templateBuilder = templateBuilder.smallest();
> .
> .
> .
> template.getOptions().as(SoftLayerTemplateOptions.class).domainName("me.org");
> 
> template.getOptions().as(SoftLayerTemplateOptions.class).networks("253152","260523");
> NodeAndInitialCredentials guest = 
> adapter.createNodeWithGroupEncodedIntoName(group, name, template);



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

Re: [jclouds-labs-openstack] Cleans up neutron code (#139)

[Andrew Phillips]

Thanks for the changes, @zack-shoylev! Still a couple of [Checkstyle 
violations](https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack-pull-requests/405/violations/),
 by the way...but they don't seem to be related to this PR..?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/139#issuecomment-54551288

Re: [jclouds-labs-openstack] Cleans up neutron code (#139)

[Andrew Phillips]

> @@ -40,7 +40,7 @@ public String toString() {
>return name;
> }
>  
> -   /**

> was OK here, so why the change?

Originally my review comment, @jdaggett ;-) I made it because this seems like a 
comment for a jclouds-dev, not something a **user** of jclouds would expect in 
the Javadoc.

A user-facing description would be something like "Converts a string 
representation to the appropriate enum, with A, B and C special features" or 
so. But I don't really think we need that?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/139/files#r17145229

[jira] [Updated] (JCLOUDS-704) Create Virtual guest throws error

[Jaiganesh Mathaiyan (JIRA)]

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

Jaiganesh Mathaiyan updated JCLOUDS-704:

Environment: 
provider: Softlayer
JDK:  1.7
provider/softlayer code deployed from github branch master.

  was:
provider: Softlayer
JDK:  1.7


> Create Virtual guest throws error
> -
>
> Key: JCLOUDS-704
> URL: https://issues.apache.org/jira/browse/JCLOUDS-704
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute
>Affects Versions: 1.8.1
> Environment: provider: Softlayer
> JDK:  1.7
> provider/softlayer code deployed from github branch master.
>Reporter: Jaiganesh Mathaiyan
>Priority: Blocker
>
> Error while creating a virtual guest in softlayer
> 2014-09-04 15:29:45,812 [main] DEBUG SLF4JLogger Sending request -1350657235: 
> POST 
> https://api.softlayer.com/rest/v3/SoftLayer_Product_Order/placeOrder.json 
> HTTP/1.1
> 2014-09-04 15:29:48,963 [main] DEBUG SLF4JLogger Receiving response 
> -1350657235: HTTP/1.1 200 OK
> java.lang.IndexOutOfBoundsException: position (0) must be less than the 
> number of elements that remained (0)
> at com.google.common.collect.Iterators.get(Iterators.java:813)
> at com.google.common.collect.Iterables.get(Iterables.java:728)
> at 
> org.jclouds.softlayer.compute.strategy.SoftLayerComputeServiceAdapter.createNodeWithGroupEncodedIntoName(SoftLayerComputeServiceAdapter.java:129)
> at 
> com.cisco.vnmc.hcloud.cpm.service.providers.softlayer.SLProviderOps.getLocation(SLProviderOps.java:118)
> at 
> com.cisco.vnmc.hcloud.cpm.service.providers.softlayer.SLProviderOps.getRegions(SLProviderOps.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> Code snippet
> //inst is a local object to contain the template information
> inst.setArchitecture(ArchitectureEnum.BIT64.getNumber());
> inst.setVcpus(1);
> inst.setMemory(512);
> inst.setZone("138124");
> inst.setName("abcd");
> inst.setOsFamily("RHEL");
> .
> .
> .
> templateBuilder = templateBuilder.from("minRam="
>   + (int) inst.getMemory()
>   + ",os64Bit="
>   + inst.getArchitecture().equals(
>   
> ArchitectureEnum.BIT64.getNumber()) + ",minCores="
>   + inst.getVcpus() + ",osFamily=" + 
> inst.getOsFamily()
>   + ",locationId=" + location);
>   templateBuilder = templateBuilder.smallest();
> .
> .
> .
> template.getOptions().as(SoftLayerTemplateOptions.class).domainName("me.org");
> 
> template.getOptions().as(SoftLayerTemplateOptions.class).networks("253152","260523");
> NodeAndInitialCredentials guest = 
> adapter.createNodeWithGroupEncodedIntoName(group, name, template);



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

[jira] [Created] (JCLOUDS-704) Create Virtual guest throws error

[Jaiganesh Mathaiyan (JIRA)]

Jaiganesh Mathaiyan created JCLOUDS-704:
---

 Summary: Create Virtual guest throws error
 Key: JCLOUDS-704
 URL: https://issues.apache.org/jira/browse/JCLOUDS-704
 Project: jclouds
  Issue Type: Bug
  Components: jclouds-compute
Affects Versions: 1.8.1
 Environment: provider: Softlayer
JDK:  1.7
Reporter: Jaiganesh Mathaiyan
Priority: Blocker


Error while creating a virtual guest in softlayer
2014-09-04 15:29:45,812 [main] DEBUG SLF4JLogger Sending request -1350657235: 
POST https://api.softlayer.com/rest/v3/SoftLayer_Product_Order/placeOrder.json 
HTTP/1.1
2014-09-04 15:29:48,963 [main] DEBUG SLF4JLogger Receiving response 
-1350657235: HTTP/1.1 200 OK
java.lang.IndexOutOfBoundsException: position (0) must be less than the number 
of elements that remained (0)
at com.google.common.collect.Iterators.get(Iterators.java:813)
at com.google.common.collect.Iterables.get(Iterables.java:728)
at 
org.jclouds.softlayer.compute.strategy.SoftLayerComputeServiceAdapter.createNodeWithGroupEncodedIntoName(SoftLayerComputeServiceAdapter.java:129)
at 
com.cisco.vnmc.hcloud.cpm.service.providers.softlayer.SLProviderOps.getLocation(SLProviderOps.java:118)
at 
com.cisco.vnmc.hcloud.cpm.service.providers.softlayer.SLProviderOps.getRegions(SLProviderOps.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)


Code snippet

//inst is a local object to contain the template information
inst.setArchitecture(ArchitectureEnum.BIT64.getNumber());
inst.setVcpus(1);
inst.setMemory(512);
inst.setZone("138124");
inst.setName("abcd");
inst.setOsFamily("RHEL");
.
.
.
templateBuilder = templateBuilder.from("minRam="
+ (int) inst.getMemory()
+ ",os64Bit="
+ inst.getArchitecture().equals(

ArchitectureEnum.BIT64.getNumber()) + ",minCores="
+ inst.getVcpus() + ",osFamily=" + 
inst.getOsFamily()
+ ",locationId=" + location);
templateBuilder = templateBuilder.smallest();

.
.
.
template.getOptions().as(SoftLayerTemplateOptions.class).domainName("me.org");

template.getOptions().as(SoftLayerTemplateOptions.class).networks("253152","260523");

NodeAndInitialCredentials guest = 
adapter.createNodeWithGroupEncodedIntoName(group, name, template);




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

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[Andrew Phillips]

> Already deployed it :)

I noticed...but we can always apply a little edit here and there if we think 
that's merited ;-)

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124#issuecomment-54546199

Re: [jclouds] Remove ByteStreams2.asByteSource (#507)

[Andrew Phillips]

+1 - looks good to me. Can't see if there are any Checkstyle violations due to 
our hanging MWS test issue...could you kindly run that locally (if not done 
already) to check?

Thanks, @andrewgaul!

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/507#issuecomment-54546064

Re: [jclouds-examples] The start of examples for OpenStack (#62)

[Everett Toews]

Thanks @nacx! Fixed and merged.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/62#issuecomment-54543435

Re: [jclouds] JCLOUDS-686: Remove changesSince() query from base PaginationOptions (#499)

[Everett Toews]

> @@ -44,7 +42,12 @@ public PaginationOptions queryParameters(Multimap String> queryParams) {
>  
> /**
>  * Only return objects changed since this time.
> +*
> +* @deprecated The {@code changes-since} query does not apply to all 
> OpenStack APIs. Please refer to the OpenStack
> +* Nova {@code ListOptions.changesSince(Date)} and Glance 
> {@code ListImageOptions.changesSince(Date)}.
> +* This option is deprecated in jclouds 2.0 and will be 
> removed in jclouds 3.0.

My preference would be for deprecated in 2.0 and remove in 2.1 but that's just 
me. We have no guidelines about the amount of time we allow users to deal with 
breaking changes. It's totally your call.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/499/files#r17137263

Re: [jclouds] Use try-with-resources where appropriate (#506)

[Andrew Phillips]

> from here on out will require removing these changes while backporting. 
> Correct?

Yes, I think so. Hopefully we can ensure we submit PRs also for the backports, 
then the Java 6 builder should start failing horribly if we try to use these 
constructs.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/506#issuecomment-54516636

Re: [jclouds] Use try-with-resources where appropriate (#506)

[Andrew Phillips]

The MWS test issue is hanging the PR builder :-(
```
Starting test 
testZeroLengthPutHasContentLengthHeader(org.jclouds.s3.S3ClientMockTest)
Sep 04, 2014 12:49:21 AM com.squareup.okhttp.mockwebserver.MockWebServer$3 
processOneRequest
INFO: Received request: PUT /bucket/object HTTP/1.1 and responded: HTTP/1.1 200 
OK
```

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/506#issuecomment-54509232

Re: [jclouds-labs-openstack] Glance API ListImageOptions should support changesSince() (#137)

[Jeremy Daggett]

Pushed to master 9782342

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/137#issuecomment-54510551

Jenkins build became unstable: jclouds » jclouds compute core #2740

[jenkins-no-reply]

See 

Jenkins build became unstable: jclouds #2740

[jenkins-no-reply]

See 

Re: [jclouds] JCLOUDS-686: Remove changesSince() query from base PaginationOptions (#499)

[Jeremy Daggett]

> @@ -44,7 +42,12 @@ public PaginationOptions queryParameters(Multimap String> queryParams) {
>  
> /**
>  * Only return objects changed since this time.
> +*
> +* @deprecated The {@code changes-since} query does not apply to all 
> OpenStack APIs. Please refer to the OpenStack
> +* Nova {@code ListOptions.changesSince(Date)} and Glance 
> {@code ListImageOptions.changesSince(Date)}.
> +* This option is deprecated in jclouds 2.0 and will be 
> removed in jclouds 3.0.

@everett-toews Deprecated in 1.8 remove in 2.0 given the versioning discussion?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/499/files#r17127759

Re: [jclouds-labs-openstack] Glance API ListImageOptions should support changesSince() (#137)

[Jeremy Daggett]

Closed #137.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/137#event-161314564

[jira] [Commented] (JCLOUDS-686) Remove OpenStack PaginationOptions.changesSince()

[ASF subversion and git services (JIRA)]

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

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

Commit 978234238abc5f2a8771dffca054feb3a22dfb3c in jclouds-labs-openstack's 
branch refs/heads/master from [~jdaggett]
[ 
https://git-wip-us.apache.org/repos/asf?p=jclouds-labs-openstack.git;h=9782342 ]

JCLOUDS-686: Glance API ListImageOptions should support changesSince()


> Remove OpenStack PaginationOptions.changesSince()
> -
>
> Key: JCLOUDS-686
> URL: https://issues.apache.org/jira/browse/JCLOUDS-686
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-core, jclouds-labs-openstack
>Affects Versions: 1.6.0, 1.7.0, 1.8.0
>Reporter: Jeremy Daggett
>Assignee: Jeremy Daggett
>  Labels: openstack
> Fix For: 2.0.0
>
>
> The base OpenStack 
> [{{PaginationOptions}}|https://github.com/jclouds/jclouds/blob/master/apis/openstack-keystone/src/main/java/org/jclouds/openstack/v2_0/options/PaginationOptions.java]
>  class provides a [{{changesSince(Date 
> ifModifiedSince)}}|https://github.com/jclouds/jclouds/blob/master/apis/openstack-keystone/src/main/java/org/jclouds/openstack/v2_0/options/PaginationOptions.java#L48]
>  query that is specific to the [Nova 
> API|http://docs.openstack.org/api/openstack-compute/2/content/ChangesSince.html].
>  The Nova [{{ListOptions.changesSince(Date 
> ifModifiedSince)}}|https://github.com/jclouds/jclouds/blob/master/apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/options/ListOptions.java#L47]
>  method should be replaced with the superclass implementation.
> The base {{PaginationOptions}} should provide {{limit(int limit)}} and 
> {{marker(String marker)}} queries, since they are common for pagination 
> across the OpenStack APIs (to date).



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

Re: [jclouds-labs-openstack] Cleans up neutron code (#139)

[Zack Shoylev]

Thanks @jdaggett !

I will be sitting on this one for a bit to figure out if we want to rename 
createOptions/updateOptions.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/139#issuecomment-54509797

Re: [jclouds] Remove ByteStreams2.asByteSource (#507)

[CloudBees pull request builder plugin]

[jclouds-pull-requests 
#1145](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1145/) ABORTED


---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/507#issuecomment-54509746

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[Zack Shoylev]

Already deployed it :) but will consider adding some more to illustrate the 
"create for create" example.
About fonts: I don't like using that much outside code blocks, but I see what 
you are saying with regards to consistency. Hmm.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124#issuecomment-54509614

Re: [jclouds] Use try-with-resources where appropriate (#506)

[CloudBees pull request builder plugin]

[jclouds-pull-requests 
#1143](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1143/) ABORTED


---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/506#issuecomment-54509589

Re: [jclouds] Ensure that Content-MD5 has 128 bits (#504)

[Andrew Phillips]

> jclouds-pull-requests #1139 ABORTED

```
Build timed out due to Global Timeout (after 1440 minutes). Marking the build 
as aborted.
```
It's that MWS test again :-(

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/504#issuecomment-54509505

Re: [jclouds] Nova API Updates (#505)

[Jeremy Daggett]

Closed #505.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/505#event-161308844

Re: [jclouds-labs-openstack] Glance API ListImageOptions should support changesSince() (#137)

[CloudBees pull request builder plugin]

[jclouds-labs-openstack-pull-requests 
#407](https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack-pull-requests/407/)
 SUCCESS
This pull request looks good

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/137#issuecomment-54509027

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[Andrew Phillips]

Thanks, @zack-shoylev! Great to see more posts on the blog. Just a bunch of 
minor comments, many of them around code font (or not) for things like classes. 
I have no strong preference either way, but it would be good to be consistent 
with other blog posts...

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124#issuecomment-54508957

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[Andrew Phillips]

> +In this case, it was easy to add support for this call by using a [map 
> binder](https://github.com/jclouds/jclouds/blob/master/apis/openstack-trove/src/main/java/org/jclouds/openstack/trove/v1/binders/BindCreateUserToJson.java).
> +
> +However, some APIs send or receive significantly more complex JSON 
> structures. Recent work on Neutron has shown that there are benefits to 
> increased consistency among the domain classes and the OpenStack API calls 
> that use them.
> +
> +Current implementations have the following two issues :
> +
> +1. Heavy use of map-binders and parsers to transform JSON. Map-binders use  
> annotation-selected classes to map method data (such as the data in the 
> create-user call above) to the JSON required by the service. The 
> [parsers](https://github.com/jclouds/jclouds-labs-openstack/blob/master/openstack-neutron/src/main/java/org/jclouds/openstack/neutron/v2_0/functions/ParseNetworkDetails.java)
>  apply the reverse transformation: from JSON to domain objects.
> +2. Lack of consistent, concise, and user-friendly way to use domain objects 
> in create/update/list methods.
> +
> +In addition to fixing these issues, jclouds wants to provide developers with 
> some compiler checks and other syntactic sugar (fluent builders), while also 
> supporting different updating, creating, or listing validation strategies.
> +
> +We want to
> +
> +1. Ensure object immutability.
> +2. Utilize the fluent builder pattern.
> +3. Ensure that "create" objects can only be used for create; update for 
> update; and listed resources cannot be directly sent back to the service.

This seems to be the most important part in terms of why we need 
CreateOptions/CreateRequest/whatever. Would it make sense to illustrate what 
the problem is here by extending the code sample below?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124/files#r17126556

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[Andrew Phillips]

> +Some [simpler 
> classes](https://github.com/jclouds/jclouds-labs-openstack/blob/master/openstack-neutron/src/main/java/org/jclouds/openstack/neutron/v2/domain/AddressPair.java)
>  implement the regular fluent builder pattern. 
> +
> +In [other 
> cases](https://github.com/jclouds/jclouds-labs-openstack/blob/master/openstack-neutron/src/main/java/org/jclouds/openstack/neutron/v2/features/NetworkApi.java),
>  the same domain class has several different purposes, such as making sure 
> users have different Network-subtype object instances for updating, creating, 
> and listing networks:
> +
> +1. Listing networks returns a Network or a list of Networks.
> +2. Updating a network requires Network.UpdateOptions.
> +3. Creating a network requires Network.CreateOptions.
> +
> +CreateOptions and UpdateOptions extend Network and implement their own copy 
> constructors, with custom validation, if needed.
> +
> +To instantiate these create or update-specific objects, developers have 
> access to CreateBuilder and UpdateBuilder, which both extend the regular 
> Network builder abstract class. The only code these special builders 
> implement: the constructor (taking as parameters any required properties), a 
> build() method returning the create or update object, and also self(). The 
> self method is needed to make sure we can reuse most of the Builder code, but 
> still be able to chain the fluent builder methods.
> +
> +This is how it all works out from the developer's perspective:
> +
> +{% highlight Java %}
> +Network.CreateOptions createNetwork = Network.createOptions("jclouds-wibble")

Interesting example: here, the domain object subtypes are pretty visible. Is 
that the intention? Or so you see people calling the API call directly, without 
creating this intervening object and (thus) exposing this subtype?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124/files#r17126468

Re: [jclouds] Ensure that Content-MD5 has 128 bits (#504)

[CloudBees pull request builder plugin]

[jclouds-pull-requests 
#1139](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1139/) ABORTED


---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/504#issuecomment-54508329

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[Andrew Phillips]

> +
> +We want to
> +
> +1. Ensure object immutability.
> +2. Utilize the fluent builder pattern.
> +3. Ensure that "create" objects can only be used for create; update for 
> update; and listed resources cannot be directly sent back to the service.
> +4. Reuse code and keep domain classes 
> [DRY](http://en.wikipedia.org/wiki/Don't_repeat_yourself).
> +5. Allow using different validation strategies (for example, create vs 
> update).
> +
> +We have been able to identify a pattern that addresses these issues. Here is 
> some [sample 
> code](https://github.com/jclouds/jclouds-labs-openstack/blob/master/openstack-neutron/src/main/java/org/jclouds/openstack/neutron/v2/domain/Router.java).
> +
> +This approach reuses code by having 
> [GSON](https://code.google.com/p/google-gson/) handle the domain objects 
> directly, as much as possible, both for serialization and deserialization, 
> thus eliminating map-binders and parsers in most cases. The domain classes 
> annotate their member variables using the @Named (for serialization) and 
> @ConstructorProperties (for deserialization) annotations.
> +
> +Many of the JSON attributes in Neutron are optional. GSON's jclouds 
> configuration supports such optional values by using @Nullable and boxed 
> types. An alternate supported method, more convoluted, implements Optional 
> private member variables and getter return types.
> +
> +To ensure immutability, users have no access to a constructor or setters, 
> and instead they must instantiate domain objects by using a slightly modified 
> Builder pattern. The builder pattern also provides proper validation and 
> user-friendliness.

[minor] lowercase "builder"?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124/files#r17126377

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[Andrew Phillips]

> +
> +In addition to fixing these issues, jclouds wants to provide developers with 
> some compiler checks and other syntactic sugar (fluent builders), while also 
> supporting different updating, creating, or listing validation strategies.
> +
> +We want to
> +
> +1. Ensure object immutability.
> +2. Utilize the fluent builder pattern.
> +3. Ensure that "create" objects can only be used for create; update for 
> update; and listed resources cannot be directly sent back to the service.
> +4. Reuse code and keep domain classes 
> [DRY](http://en.wikipedia.org/wiki/Don't_repeat_yourself).
> +5. Allow using different validation strategies (for example, create vs 
> update).
> +
> +We have been able to identify a pattern that addresses these issues. Here is 
> some [sample 
> code](https://github.com/jclouds/jclouds-labs-openstack/blob/master/openstack-neutron/src/main/java/org/jclouds/openstack/neutron/v2/domain/Router.java).
> +
> +This approach reuses code by having 
> [GSON](https://code.google.com/p/google-gson/) handle the domain objects 
> directly, as much as possible, both for serialization and deserialization, 
> thus eliminating map-binders and parsers in most cases. The domain classes 
> annotate their member variables using the @Named (for serialization) and 
> @ConstructorProperties (for deserialization) annotations.
> +
> +Many of the JSON attributes in Neutron are optional. GSON's jclouds 
> configuration supports such optional values by using @Nullable and boxed 
> types. An alternate supported method, more convoluted, implements Optional 
> private member variables and getter return types.

Code font for `@Nullable` and `Optional`?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124/files#r17126365

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[Andrew Phillips]

> +1. Heavy use of map-binders and parsers to transform JSON. Map-binders use  
> annotation-selected classes to map method data (such as the data in the 
> create-user call above) to the JSON required by the service. The 
> [parsers](https://github.com/jclouds/jclouds-labs-openstack/blob/master/openstack-neutron/src/main/java/org/jclouds/openstack/neutron/v2_0/functions/ParseNetworkDetails.java)
>  apply the reverse transformation: from JSON to domain objects.
> +2. Lack of consistent, concise, and user-friendly way to use domain objects 
> in create/update/list methods.
> +
> +In addition to fixing these issues, jclouds wants to provide developers with 
> some compiler checks and other syntactic sugar (fluent builders), while also 
> supporting different updating, creating, or listing validation strategies.
> +
> +We want to
> +
> +1. Ensure object immutability.
> +2. Utilize the fluent builder pattern.
> +3. Ensure that "create" objects can only be used for create; update for 
> update; and listed resources cannot be directly sent back to the service.
> +4. Reuse code and keep domain classes 
> [DRY](http://en.wikipedia.org/wiki/Don't_repeat_yourself).
> +5. Allow using different validation strategies (for example, create vs 
> update).
> +
> +We have been able to identify a pattern that addresses these issues. Here is 
> some [sample 
> code](https://github.com/jclouds/jclouds-labs-openstack/blob/master/openstack-neutron/src/main/java/org/jclouds/openstack/neutron/v2/domain/Router.java).
> +
> +This approach reuses code by having 
> [GSON](https://code.google.com/p/google-gson/) handle the domain objects 
> directly, as much as possible, both for serialization and deserialization, 
> thus eliminating map-binders and parsers in most cases. The domain classes 
> annotate their member variables using the @Named (for serialization) and 
> @ConstructorProperties (for deserialization) annotations.

[minor] I think they refer to it as "Gson"?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124/files#r17126331

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[Andrew Phillips]

> +Current implementations have the following two issues :
> +
> +1. Heavy use of map-binders and parsers to transform JSON. Map-binders use  
> annotation-selected classes to map method data (such as the data in the 
> create-user call above) to the JSON required by the service. The 
> [parsers](https://github.com/jclouds/jclouds-labs-openstack/blob/master/openstack-neutron/src/main/java/org/jclouds/openstack/neutron/v2_0/functions/ParseNetworkDetails.java)
>  apply the reverse transformation: from JSON to domain objects.
> +2. Lack of consistent, concise, and user-friendly way to use domain objects 
> in create/update/list methods.
> +
> +In addition to fixing these issues, jclouds wants to provide developers with 
> some compiler checks and other syntactic sugar (fluent builders), while also 
> supporting different updating, creating, or listing validation strategies.
> +
> +We want to
> +
> +1. Ensure object immutability.
> +2. Utilize the fluent builder pattern.
> +3. Ensure that "create" objects can only be used for create; update for 
> update; and listed resources cannot be directly sent back to the service.
> +4. Reuse code and keep domain classes 
> [DRY](http://en.wikipedia.org/wiki/Don't_repeat_yourself).
> +5. Allow using different validation strategies (for example, create vs 
> update).
> +
> +We have been able to identify a pattern that addresses these issues. Here is 
> some [sample 
> code](https://github.com/jclouds/jclouds-labs-openstack/blob/master/openstack-neutron/src/main/java/org/jclouds/openstack/neutron/v2/domain/Router.java).

Include the relevant snippet of the sample code here? Or is it too long?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124/files#r17126300

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[Andrew Phillips]

> +
> +To parse the response, jclouds uses [domain 
> classes](https://github.com/jclouds/jclouds/blob/master/apis/openstack-trove/src/main/java/org/jclouds/openstack/trove/v1/domain/User.java)
>  to represent the JSON data returned by the service. The array of "users" is 
> unwrapped into individual User domain objects. Conversely, when creating 
> users, domain objects are transformed into a JSON request body. 
> +
> +Because of the relative simplicity of user creation in trove, jclouds 
> developers can use a create method in the features package without having to 
> build an instance of the User class. For example, the developer might use a 
> method such as
> +
> +{% highlight Java %}
> +boolean create(String userName, String password, String databaseName);
> +{% endhighlight %}
> +
> +In this case, it was easy to add support for this call by using a [map 
> binder](https://github.com/jclouds/jclouds/blob/master/apis/openstack-trove/src/main/java/org/jclouds/openstack/trove/v1/binders/BindCreateUserToJson.java).
> +
> +However, some APIs send or receive significantly more complex JSON 
> structures. Recent work on Neutron has shown that there are benefits to 
> increased consistency among the domain classes and the OpenStack API calls 
> that use them.
> +
> +Current implementations have the following two issues :
> +
> +1. Heavy use of map-binders and parsers to transform JSON. Map-binders use  
> annotation-selected classes to map method data (such as the data in the 
> create-user call above) to the JSON required by the service. The 
> [parsers](https://github.com/jclouds/jclouds-labs-openstack/blob/master/openstack-neutron/src/main/java/org/jclouds/openstack/neutron/v2_0/functions/ParseNetworkDetails.java)
>  apply the reverse transformation: from JSON to domain objects.

[minor] Too many spaces between "use" and "annotation-selected"

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124/files#r17126267

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[Andrew Phillips]

> +}
> +]
> +}
> +{% endhighlight %}
> +
> +To parse the response, jclouds uses [domain 
> classes](https://github.com/jclouds/jclouds/blob/master/apis/openstack-trove/src/main/java/org/jclouds/openstack/trove/v1/domain/User.java)
>  to represent the JSON data returned by the service. The array of "users" is 
> unwrapped into individual User domain objects. Conversely, when creating 
> users, domain objects are transformed into a JSON request body. 
> +
> +Because of the relative simplicity of user creation in trove, jclouds 
> developers can use a create method in the features package without having to 
> build an instance of the User class. For example, the developer might use a 
> method such as
> +
> +{% highlight Java %}
> +boolean create(String userName, String password, String databaseName);
> +{% endhighlight %}
> +
> +In this case, it was easy to add support for this call by using a [map 
> binder](https://github.com/jclouds/jclouds/blob/master/apis/openstack-trove/src/main/java/org/jclouds/openstack/trove/v1/binders/BindCreateUserToJson.java).
> +
> +However, some APIs send or receive significantly more complex JSON 
> structures. Recent work on Neutron has shown that there are benefits to 
> increased consistency among the domain classes and the OpenStack API calls 
> that use them.

[minor] Add link to Neutron? Extra PR for the API ;-)

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124/files#r17126250

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[Andrew Phillips]

> +{
> +"databases": [
> +{
> +"name": "sampledb"
> +}
> +],
> +"host": "%",
> +"name": "demouser"
> +}
> +]
> +}
> +{% endhighlight %}
> +
> +To parse the response, jclouds uses [domain 
> classes](https://github.com/jclouds/jclouds/blob/master/apis/openstack-trove/src/main/java/org/jclouds/openstack/trove/v1/domain/User.java)
>  to represent the JSON data returned by the service. The array of "users" is 
> unwrapped into individual User domain objects. Conversely, when creating 
> users, domain objects are transformed into a JSON request body. 
> +
> +Because of the relative simplicity of user creation in trove, jclouds 
> developers can use a create method in the features package without having to 
> build an instance of the User class. For example, the developer might use a 
> method such as

[minor] "Trove"? And `User` again?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124/files#r17126236

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[Andrew Phillips]

> +"host": "%"
> +}, 
> +{
> +"databases": [
> +{
> +"name": "sampledb"
> +}
> +],
> +"host": "%",
> +"name": "demouser"
> +}
> +]
> +}
> +{% endhighlight %}
> +
> +To parse the response, jclouds uses [domain 
> classes](https://github.com/jclouds/jclouds/blob/master/apis/openstack-trove/src/main/java/org/jclouds/openstack/trove/v1/domain/User.java)
>  to represent the JSON data returned by the service. The array of "users" is 
> unwrapped into individual User domain objects. Conversely, when creating 
> users, domain objects are transformed into a JSON request body. 

[minor] `User` instead of User?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124/files#r17126220

Re: [jclouds-labs-openstack] OpenStack Heat Support (#138)

[Jeremy Daggett]

@nacx I made your suggested changes, thx!

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/138#issuecomment-54504007

Re: [jclouds-labs-openstack] OpenStack Heat Support (#138)

[CloudBees pull request builder plugin]

[jclouds-labs-openstack-pull-requests 
#406](https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack-pull-requests/406/)
 SUCCESS
This pull request looks good

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/138#issuecomment-54502375

Re: [jclouds-labs-openstack] OpenStack Heat Support (#138)

[Everett Toews]

@sharwell In jclouds we refer to the code names for the OpenStack projects in 
the code. Naming it Heat here keeps it consistent with the rest of the code. In 
documentation we'll refer to it as both.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/138#issuecomment-54501474

Re: [jclouds-labs-openstack] OpenStack Heat Support (#138)

[Sam Harwell]

Considering that both OpenStack and Rackspace now refer to this service as 
"Orchestration", would it make sense to rename this feature for consistency 
prior to its introduction in jclouds?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/138#issuecomment-54497339

Re: [jclouds] Use try-with-resources where appropriate (#506)

[Everett Toews]

Just to be clear, after this merges, any changes to these classes that needs to 
be backported to 1.8.x from here on out will require removing these changes 
while backporting. Correct?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/506#issuecomment-54495608

Re: [jclouds] Use try-with-resources where appropriate (#506)

[Everett Toews]

My preference too is to not use any Java 7 specific features in the examples 
until we've released 2.0.0. The examples really should be consistent with the 
language level we support.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/506#issuecomment-54495024

Re: [jclouds-examples] Updated Clojure and jclouds versions (#53)

[Everett Toews]

Closed #53.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/53#event-161258946

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[Zack Shoylev]

Closed #124.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124#event-161253336

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[Zack Shoylev]

Website deployed. It seems to not be completely broken so far.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124#issuecomment-54493351

Re: [jclouds] Use try-with-resources where appropriate (#506)

[Andrew Phillips]

Yay Java 7! Thanks, @andrewgaul! I was going to make the same comment @nacx 
made about the examples, but I guess we should only do that when we release a 
new version that _only_ supports Java 7..?

+1 from me too, by the way.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/506#issuecomment-54492984

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[Zack Shoylev]

merged

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124#issuecomment-54491307

[jira] [Commented] (JCLOUDS-703) Google Hardware no longer supports images

[Stuart Hendren (JIRA)]

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

Stuart Hendren commented on JCLOUDS-703:


There's a relevant TODO in MachineTypeInZoneToHardware line 71

// TODO Figure out a robust way to deal with machineTypes with imageSizeGb==0 
rather than just blocking them.



> Google Hardware no longer supports images
> -
>
> Key: JCLOUDS-703
> URL: https://issues.apache.org/jira/browse/JCLOUDS-703
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-labs-google
>Affects Versions: 1.8.0
> Environment: Java 1.8
>Reporter: Stuart Hendren
>Priority: Critical
> Fix For: 1.8.1, 2.0.0
>
>
> All Google hardware now has the AlwaysFalse predicate for supportsImage().
> This seems to be because the response for MachineType is missing a value for 
> "imageSpaceGb", which gets assigned 0 in the MachineType class and this 
> results in the AlwaysFalse predicate.
> Current example machine type return taken from a response to GET 
> https://www.googleapis.com/compute/v1/projects/project/zones/zone/machineTypes:
> {noformat}
> {
>"kind": "compute#machineType",
>"id": "7224129552184485774",
>"creationTimestamp": "2013-04-25T13:32:45.550-07:00",
>"name": "g1-small",
>"description": "1 vCPU (shared physical core) and 1.7 GB RAM",
>"guestCpus": 1,
>"memoryMb": 1740,
>"maximumPersistentDisks": 4,
>"maximumPersistentDisksSizeGb": "3072",
>"zone": "europe-west1-a",
>"selfLink": 
> "https://www.googleapis.com/compute/v1/projects/cold-front/zones/europe-west1-a/machineTypes/g1-small";
>   }
> {noformat}



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

Re: [jclouds-labs-openstack] Cleans up neutron code (#139)

[Zack Shoylev]

@jdaggett let me know if my comments answer your questions or if there is 
anything else. Thanks!

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/139#issuecomment-54480981

[jira] [Created] (JCLOUDS-703) Google Hardware no longer supports images

[Stuart Hendren (JIRA)]

Stuart Hendren created JCLOUDS-703:
--

 Summary: Google Hardware no longer supports images
 Key: JCLOUDS-703
 URL: https://issues.apache.org/jira/browse/JCLOUDS-703
 Project: jclouds
  Issue Type: Bug
  Components: jclouds-labs-google
Affects Versions: 1.8.0
 Environment: Java 1.8
Reporter: Stuart Hendren
Priority: Critical
 Fix For: 1.8.1, 2.0.0


All Google hardware now has the AlwaysFalse predicate for supportsImage().

This seems to be because the response for MachineType is missing a value for 
"imageSpaceGb", which gets assigned 0 in the MachineType class and this results 
in the AlwaysFalse predicate.

Current example machine type return taken from a response to GET 
https://www.googleapis.com/compute/v1/projects/project/zones/zone/machineTypes:

{noformat}
{
   "kind": "compute#machineType",
   "id": "7224129552184485774",
   "creationTimestamp": "2013-04-25T13:32:45.550-07:00",
   "name": "g1-small",
   "description": "1 vCPU (shared physical core) and 1.7 GB RAM",
   "guestCpus": 1,
   "memoryMb": 1740,
   "maximumPersistentDisks": 4,
   "maximumPersistentDisksSizeGb": "3072",
   "zone": "europe-west1-a",
   "selfLink": 
"https://www.googleapis.com/compute/v1/projects/cold-front/zones/europe-west1-a/machineTypes/g1-small";
  }
{noformat}



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

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[Everett Toews]

Merge and publish!

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124#issuecomment-54484345

Re: [jclouds-labs-openstack] Cleans up neutron code (#139)

[CloudBees pull request builder plugin]

[jclouds-labs-openstack-pull-requests 
#405](https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack-pull-requests/405/)
 SUCCESS
This pull request looks good

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/139#issuecomment-54482376

Re: [jclouds-labs-openstack] Cleans up neutron code (#139)

[BuildHive]

[jclouds » jclouds-labs-openstack 
#1674](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-openstack/1674/)
 SUCCESS
This pull request looks good
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/139#issuecomment-54482076

Re: [jclouds] Implemented compute attach interfaces extension. (#497)

[Ignasi Barrera]

No @RoadRoller. The PR is very welcome! I wasn't sure if the expect tests were 
complete or no and just wanted to leave the note. Thanks!

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/497#issuecomment-54479743

Re: [jclouds-labs-openstack] Cleans up neutron code (#139)

[Zack Shoylev]

>  
> - Rule newSecGroupRule = null;
> - for(Rule sgr : securityGroup.getRules()) {
> -if(sgr.getId().equals(rule.getId())) {
> -   newSecGroupRule = sgr;
> -   break;
> -}
> - }
> - assertNotNull(newSecGroupRule, "Did not find the new rule in the 
> group.");
> +assertEquals(securityGroup.getRules().size(), 3);

What do you mean? The error message was supposed to have been removed, as the 
default message is better.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/139/files#r17113690

Re: [jclouds] Implemented compute attach interfaces extension. (#497)

[Tarasenko Evgeny]

@nacx I understand that tests in incomplete, but in this month I'm have no free 
time to do it. I suppose I return to it work in October. 

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/497#issuecomment-54473842

Re: [jclouds-labs-openstack] OpenStack Heat Support (#138)

[Ignasi Barrera]

> +  test
> +
> +
> +  ch.qos.logback
> +  logback-classic
> +  test
> +
> +
> +  com.squareup.okhttp
> +  mockwebserver
> +  test
> +
> +
> +  org.yaml
> +  snakeyaml
> +  1.13

I assume this will be needed if we're going to parse the Heat templates. Better 
comment/remove it until it is actually needed?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/138/files#r17110319

Re: [jclouds-labs-openstack] OpenStack Heat Support (#138)

[Ignasi Barrera]

> +target/test-data/jclouds.log
> +
> +
> +%d %-5p [%c] [%thread] %m%n
> +
> +
> +
> +
> +target/test-data/jclouds-wire.log
> +
> +
> +%d %-5p [%c] [%thread] %m%n
> +
> +
> +
> +

Remove this appender?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/138/files#r17110252

Re: [jclouds-labs-openstack] OpenStack Heat Support (#138)

[Ignasi Barrera]

> +
> + /*
> +  * Check response
> +  */
> + assertThat(resourceTypes).isNotEmpty();
> + assertThat(resourceTypes.size()).isEqualTo(20);
> +
> +  } finally {
> + server.shutdown();
> +  }
> +   }
> +
> +   public void testListTypesIsEmpty() throws Exception {
> +  MockWebServer server = mockOpenStackServer();
> +  server.enqueue(addCommonHeaders(new 
> MockResponse().setBody(stringFromResource("/access.json";
> +  server.enqueue(addCommonHeaders(new 
> MockResponse().setResponseCode(404).setBody(stringFromResource("/resource_type_list_response.json";

Should the body be removed here? I assume that the server won't send a body on 
a 404.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/138/files#r17110227

Re: [jclouds] Implemented compute attach interfaces extension. (#497)

[Ignasi Barrera]

> +.method("GET")
> +.endpoint(
> +  
> "https://az-1.region-a.geo-1.compute.hpcloudsvc.com/v2/3456/servers/instance-1/os-interface/ce531f90-199f-48c0-816c-13e38010b442";)
> +.addHeader("Accept", 
> "application/json").addHeader("X-Auth-Token", authToken).build();
> +
> +  HttpResponse listResponse = HttpResponse.builder().statusCode(200)
> +
> .payload(payloadFromResource("/attach_interface_details.json")).build();
> +
> +  NovaApi novaApi = 
> requestsSendResponses(keystoneAuthWithUsernameAndPasswordAndTenantName,
> +responseWithKeystoneAccess, extensionsOfNovaRequest, 
> extensionsOfNovaResponse, list, listResponse);
> +
> +  InterfaceAttachment interfaceAttachment = 
> novaApi.getAttachInterfaceApi("az-1.region-a.geo-1").get()
> +.get("instance-1", "ce531f90-199f-48c0-816c-13e38010b442");
> +
> +  assertEquals(interfaceAttachment, testInterfaceAttachment());
> +   }

There should be also tests for the `create` and `delete` methods, as long as 
tests that verify the fallbacks. The `list`, `get`and `delete`methods define a 
fallback, and there should be the corresponding tests to assert that jclouds 
returns the expected value.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/497/files#r17109741

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[Zack Shoylev]

Alright, problems with the PR build script seem fixed now. This also seems good 
to merge. Should I merge it? Is there anything else that needs to be done? The 
front page has a link to the blog I think.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124#issuecomment-54461023

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[jclouds-commentator]

  Go to 
http://306ae818722ae6b78b92-2e69301a260e5804fbad8c2752c99931.r57.cf5.rackcdn.com/
 to review your changes.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124#issuecomment-54458152

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[CloudBees pull request builder plugin]

[jclouds-site-pull-requests 
#395](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/395/) 
SUCCESS
This pull request looks good

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124#issuecomment-54457891

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[Zack Shoylev]

Reopened #124.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124#event-161132059

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[Zack Shoylev]

Closed #124.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124#event-161132054

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[jclouds-commentator]

 to review your changes.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124#issuecomment-54454813

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[CloudBees pull request builder plugin]

[jclouds-site-pull-requests 
#394](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/394/) 
SUCCESS
This pull request looks good

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124#issuecomment-54454709

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[Zack Shoylev]

Reopened #124.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124#event-161122494

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[jclouds-commentator]

 to review your changes.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124#issuecomment-54454032

Re: [jclouds-site] Domain classes, better builders blog post. (#124)

[CloudBees pull request builder plugin]

[jclouds-site-pull-requests 
#393](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/393/) 
SUCCESS
This pull request looks good

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124#issuecomment-54453827

[jira] [Commented] (JCLOUDS-687) Configurable API/Provider Default Page Size

[Andrey Trubitsyn (JIRA)]

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

Andrey Trubitsyn commented on JCLOUDS-687:
--

Hi Guys,

Thank you for your feedback. 

As I could understand the problem is the next:
OpenStack APIs (nova, neutron, etc.) have list(PaginationOptions o) methods 
which by default return all requested entities. (if pagination is disabled at 
the server side)
For example
Ports list(PaginationOptions options) in PortApi returns all entities if it is 
called list(new PaginationOptions()). And if there are a lot of ports it could 
be a problem to pull all of them. I think it would be useful to set "limit" to 
a value by default.

I don't think we should use a global core constant for that ( as you pointed ). 
Also I think "core" is not proper module for that. I would like to go through 
jclouds-labs-openstack and add a default value for "limit" parameter in 
PaginationOptions, ListContainerOptions, ... (all *Option classes that set 
"limit" parameter). 

But I am not sure about the correct place for the default "page_size" values in 
openstack APIs. May be it is ok to have the default "page_size" value in every 
API?





> Configurable API/Provider Default Page Size
> ---
>
> Key: JCLOUDS-687
> URL: https://issues.apache.org/jira/browse/JCLOUDS-687
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-core
>Affects Versions: 1.6.0, 1.7.0, 1.8.0
>Reporter: Jeremy Daggett
>Assignee: Jeremy Daggett
>Priority: Minor
>  Labels: jclouds, openstack
> Fix For: 2.0.0
>
>
> Each OpenStack API has a default page size that can be returned by the 
> service. The page sizes differ between APIs and there should be a way to 
> reflect this in API/provider configuration. The page size is typically used 
> in the list/get related operations.
> The opportunity arises to expand this to all APIs that have a default page 
> size by introducing a new constant "PROPERTY_PAGE_SIZE" or 
> "PROPERTY_DEFAULT_PAGE_SIZE" to the {{org.jclouds.Constants}} class.



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

Re: [jclouds] Use try-with-resources where appropriate (#506)

[Ignasi Barrera]

+1. In fact this is something we could also apply to the jclouds context in our 
examples. This way people won't forget to close the context, leaving the 
executors running and the program hanging until killed.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/506#issuecomment-54442832

Re: [jclouds-examples] The start of examples for OpenStack (#62)

[Ignasi Barrera]

> @@ -0,0 +1,109 @@
> +package org.jclouds.examples.openstack.identity;

Add the ASF header

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/62/files#r17104159

Re: [jclouds-examples] The start of examples for OpenStack (#62)

[Ignasi Barrera]

> @@ -0,0 +1,64 @@
> +# Rackspace Examples

OpenStack?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/62/files#r17103832

Re: [jclouds-examples] The start of examples for OpenStack (#62)

[Ignasi Barrera]

> +the License.  You may obtain a copy of the License at
> +
> +http://www.apache.org/licenses/LICENSE-2.0
> +
> +Unless required by applicable law or agreed to in writing, software
> +distributed under the License is distributed on an "AS IS" BASIS,
> +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> +See the License for the specific language governing permissions and
> +limitations under the License.
> +
> +-->
> +http://maven.apache.org/POM/4.0.0"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> +  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> +  4.0.0
> +  org.apache.jclouds.examples
> +  rackspace-examples

openstack-examples here too

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/62/files#r17103863