Re: [jclouds-labs-openstack] Backport JCLOUDS-630 to 1.8.x (#142)

> @@ -160,7 +163,8 @@ public void testCreate() throws Exception { >server.enqueue(addCommonHeaders(new > MockResponse().setBody(stringFromResource("/access.json"; >server.enqueue(addCommonHeaders(new MockResponse() > .setResponseCode(201) > -.addHeader(

Re: [jclouds-labs-openstack] Backport JCLOUDS-630 to 1.8.x (#142)

> + Payload payload = > newByteSourcePayload(ByteSource.wrap("swifty".getBytes())); > + payload.getContentMetadata().setExpires(expireAt); > + > + for (String regionId : regions) { > + String etag = api.getObjectApiForRegionAndContainer(regionId, > containerName) > +

Re: [jclouds-labs-openstack] JCLOUDS-630: Fixes Swift object expiration mapping (#118)

Just minor comments - +1, looks good to me. Thanks, @jdaggett! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/118#issuecomment-55482961

Re: [jclouds-labs-openstack] JCLOUDS-630: Fixes Swift object expiration mapping (#118)

> @@ -160,7 +163,8 @@ public void testCreate() throws Exception { >server.enqueue(addCommonHeaders(new > MockResponse().setBody(stringFromResource("/access.json"; >server.enqueue(addCommonHeaders(new MockResponse() > .setResponseCode(201) > -.addHeader(

Re: [jclouds-labs-openstack] JCLOUDS-630: Fixes Swift object expiration mapping (#118)

> + Payload payload = > newByteSourcePayload(ByteSource.wrap("swifty".getBytes())); > + payload.getContentMetadata().setExpires(expireAt); > + > + for (String regionId : regions) { > + String etag = api.getObjectApiForRegionAndContainer(regionId, > containerName) > +

Re: [jclouds-labs-openstack] JCLOUDS-630: Fixes Swift object expiration mapping (#118)

> + > + Payload payload = > newByteSourcePayload(ByteSource.wrap("swifty".getBytes())); > + payload.getContentMetadata().setExpires(expireAt); > + > + for (String regionId : regions) { > + String etag = api.getObjectApiForRegionAndContainer(regionId, > containerName) > +

Re: [jclouds-labs-google] JCLOUDS-703 missing imageSpaceGb from machineType (#49)

I starred and commented on the ticket as well. I'm not sure if we should pre-emptively apply this PR until we get some comment from Google on the ticket. If we remove this property and it comes back as a bug in GCE that they fix, we will have to track the resolution manually as it won't be obv

Re: [jclouds-labs-google] JCLOUDS-703 missing imageSpaceGb from machineType (#49)

I can also confirm this. I tested using curl for get, list, and aggregatedList varieties and none of them returned imageSpaceGb. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-google/pull/49#issuecomment-55471368

Re: [jclouds-labs-openstack] Fixes a few cases where the JavaDoc was wrong. (#144)

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

Re: [jclouds-labs-openstack] Fixes a few cases where the JavaDoc was wrong. (#144)

[jclouds » jclouds-labs-openstack #1720](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-openstack/1720/) SUCCESS This pull request looks good [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.com/jclo

Re: [jclouds-labs-openstack] Fixes a few cases where the JavaDoc was wrong. (#144)

merged and backported --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/144#issuecomment-55461495

Re: [jclouds-labs-openstack] Fixes a few cases where the JavaDoc was wrong. (#144)

This is only doc changes/fixes/cleanup. I will go ahead and commit in a little bit. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/144#issuecomment-55460682

[jclouds-labs-openstack] Fixes a few cases where the JavaDoc was wrong. (#144)

You can merge this Pull Request by running: git pull https://github.com/rackerlabs/jclouds-labs-openstack neutron-doc-options-fixes Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds-labs-openstack/pull/144 -- Commit Summary -- * Fixes a few cases

Re: [jclouds-labs] BlobStore API for Orion based back-ends (#45)

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

Re: [jclouds-labs] BlobStore API for Orion based back-ends (#45)

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

Re: [jclouds-labs] BlobStore API for Orion based back-ends (#45)

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

Jenkins build is back to normal : jclouds » jclouds-labs #1517

See

Re: [jclouds-labs] BlobStore API for Orion based back-ends (#45)

[jclouds-labs-pull-requests #248](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/248/) FAILURE Looks like there's a problem with this pull request --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/45#issuecomment-55436879

Build failed in Jenkins: jclouds » jclouds-labs #1516

See Changes: [timur] Initial set-up: Transfer of the current created files to jclouds-labs fork [timur] Property file addition for orion and first attempt to replace SLUG [timurhan.s] Slug header encoding fix [timurha

Re: [jclouds-labs] BlobStore API for Orion based back-ends (#45)

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

Re: [jclouds-labs] BlobStore API for Orion based back-ends (#45)

@andrewgaul, you need to use your login information to access Orion server as a Blobstore. I updated added some information about this to Orion server. Hopefully, it is understandable now. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/45#iss

Re: [jclouds-labs] BlobStore API for Orion based back-ends (#45)

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

Re: [jclouds-labs] BlobStore API for Orion based back-ends (#45)

[jclouds-labs-pull-requests #247](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/247/) FAILURE Looks like there's a problem with this pull request --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/45#issuecomment-55435172

Build failed in Jenkins: jclouds » jclouds-labs #1515

See Changes: [timur] Initial set-up: Transfer of the current created files to jclouds-labs fork [timur] Property file addition for orion and first attempt to replace SLUG [timurhan.s] Slug header encoding fix [timurha

Re: [jclouds-labs] BlobStore API for Orion based back-ends (#45)

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

[jira] [Updated] (JCLOUDS-560) Remove aliases method in OpenStack/Rackspace APIs

[ https://issues.apache.org/jira/browse/JCLOUDS-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Daggett updated JCLOUDS-560: --- Description: Technically, the following OpenStack APIs support the extensions model today: -

[jira] [Updated] (JCLOUDS-560) Remove aliases method in OpenStack/Rackspace APIs

[ https://issues.apache.org/jira/browse/JCLOUDS-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Daggett updated JCLOUDS-560: --- Description: Technically, the following OpenStack APIs support the extensions model today: -

Re: [jclouds-labs-openstack] Adds extension namespace support to Neutron (#143)

Alright! Thanks for explaining. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/143#issuecomment-55422368

Re: [jclouds-labs-openstack] Adds extension namespace support to Neutron (#143)

Yeah, what @nacx said... ;) Its consistent across the APIs. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/143#issuecomment-55418240

Re: [jclouds-labs-openstack] Adds extension namespace support to Neutron (#143)

I think it is not new. If I'm not wrong this was introduced with the 2.0 Keystone API, which looks for the extension apis, based on the extension annotation, in the service catalog. See [here](https://github.com/jclouds/jclouds/blob/master/apis/openstack-keystone/src/main/java/org/jclouds/openst

Re: [jclouds] Configures Checkstyle plugin to fail build on warnings (#464)

@demobox Yes, absolutely! Let me draft something up and get it on the wiki. I have to say that this has already helped my daily workflow! ;) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/464#issuecomment-55418060

Re: [jclouds-labs-openstack] Adds extension namespace support to Neutron (#143)

Outside of nova, is this consistent with other APIs? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/143#issuecomment-55417983

Re: [jclouds-labs-openstack] Adds extension namespace support to Neutron (#143)

@demobox @zack-shoylev Yes, this is currently how the extensions work in OpenStack Nova today. I was planning on aligning the APIs mentioned in the JIRA for the time being. I made an ignorant comment in another PR a while back stating that the extensions were broken, which was how I felt at tha

Re: [jclouds-labs-google] JCLOUDS-703 missing imageSpaceGb from machineType (#49)

This is the response I got Using API explorer machineTypes/get operations. with a new instance. 200 OK { "kind": "compute#machineType", "id": "4618642685664990776", "creationTimestamp": "2013-04-25T13:32:49.088-07:00", "name": "f1-micro", "description": "1 vCPU (shared physical core) and 0.6

Re: [jclouds-labs-openstack] Adds extension namespace support to Neutron (#143)

Seems that way. @jdaggett is this correct? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/143#issuecomment-55407659

Re: [jclouds-labs-google] JCLOUDS-703 missing imageSpaceGb from machineType (#49)

Good point, @stuarthendren! Just commented... --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-google/pull/49#issuecomment-55391800

Re: [jclouds-labs-openstack] Adds extension namespace support to Neutron (#143)

Code itself looks good to me too - can't comment on the architectural setup. @zack-shoylev: From your comment, I gather this is a different way of doing extensions than currently, or..? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/

Re: [jclouds-labs-google] JCLOUDS-703 missing imageSpaceGb from machineType (#49)

Maybe we'd more likely get a response from Google if you start, or comment on, the ticket? https://code.google.com/p/google-compute-engine/issues/detail?id=111 @nacx @ccustine @hsbhathiya @andreaturli @demobox --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jc

Re: [jclouds-labs-google] JCLOUDS-703 missing imageSpaceGb from machineType (#49)

+1 - code change looks good to me too. Obviously, it would be good to get some clarification from Google as to whether the value really will not be returned. @ccustine @hsbhathiya could you check whether you get this value or not? --- Reply to this email directly or view it on GitHub: https://gi

Re: [jclouds-labs] JCloud ProfitBricks provider implementation (#72)

Good to see you're getting progress. Just a quick note: jclouds also supports JAXB to deserialize the XML responses. If you add the proper JAXB annotations to your domain model classes, you can just annotate the methods in the API with `@JAXBResponseParser` and remove the custom parser and you'r

Re: [jclouds] Configures Checkstyle plugin to fail build on warnings (#464)

Bearing in mind the recent question on the dev list: would it make sense to add a short note to the dev wiki explaining that we enable Checkstyle by default, and that you will have to be Checkstyle-compliant for your PR to get in, but that you can disable it locally if you really want to? --- R

Re: [jclouds-labs] JCloud ProfitBricks provider implementation (#72)

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