Jenkins build is back to normal : jclouds-labs-openstack » jclouds openstack-glance api #187

See

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

See

Build failed in Jenkins: jclouds-labs-openstack-1.7.x-branch » jclouds openstack-glance api #14

See -- [...truncated 353 lines...] Downloaded: http://repo.cloudbees.com/content/repositories/central/org/apache/maven/plugins/maven-jar

Build failed in Jenkins: jclouds-labs-openstack-1.7.x-branch #14

See Changes: [Everett Toews] Naming methods consistently in the MarconiApi. -- [...truncated 489 lines...] Downloading: http://repo.cloudbees.com/content/repositories/c

Re: [DISCUSS] Apache jclouds 1.7.0 RC1

Dang. First I forgot to add rackspace-cloudqueues-uk to its parent POM [1]. When that was the only problem, I wasn't going to ask for another RC. Then I realized the method naming wasn't consistent in the MarconApi [2]. This is a much bigger issue because this will be the first release of this

Re: [jclouds-labs-openstack] Naming methods consistently in the MarconiApi. (#69)

Merged to master and 1.7.x. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/69#issuecomment-30899765

Re: [jclouds-labs-openstack] Finishes autoscale mock webserver test refactoring. (#67)

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

Re: [jclouds-labs-openstack] Naming methods consistently in the MarconiApi. (#69)

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

[jclouds-labs-openstack] Naming methods consistently in the MarconiApi. (#69)

https://issues.apache.org/jira/browse/JCLOUDS-340 You can merge this Pull Request by running: git pull https://github.com/rackerlabs/jclouds-labs-openstack marconi-method-rename Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds-labs-openstack/pull/69

Re: Where should admin tooling for jclouds go?

On Wed, Dec 18, 2013 at 08:53:26PM +0100, Andrew Phillips wrote: > >BlobStoreCli replaces some uses of the existing karaf-based jclouds-cli > >using really-executable-jar. This offers a more intuitive user > >experience and slimmer binary size. > > This is probably a different discussion, but it

Re: [jclouds-labs-openstack] Finishes autoscale mock webserver test refactoring. (#67)

Seems like I broke a test. Verifying. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/67#issuecomment-30889751

Re: Where should admin tooling for jclouds go?

On Wed, Dec 18, 2013 at 05:15:59PM -0500, David Nalley wrote: > On Wed, Dec 18, 2013 at 2:18 PM, Andrew Gaul wrote: > > To gives some scope, Maginatics hopes to release a series of tools under > > the jclouds umbrella: > > Thoughts on whether these need to go through IP Clearance? (and if so, > l

Re: Limited memory *only* in integration tests

Let's change the tests that use heap size to size their input then re-run the experiment. Also a few months ago I changed some integration tests to use smaller inputs in 0d6ef0607617f9968c9fe1267b6fef48e5d329ab and e27ae6117cc813b8c39f4514908541d839fb461a which might have also improved our memory

Re: Where should admin tooling for jclouds go?

On Wed, Dec 18, 2013 at 2:18 PM, Andrew Gaul wrote: > On Wed, Dec 18, 2013 at 07:59:48PM +0100, Andrew Phillips wrote: >> With #239 [1], we'll hopefully be able to get an interesting and useful >> benchmarking tool from Maginatics out to the wider jclouds audience. Some >> debate going on in the i

Re: [jclouds-labs-openstack] Finishes autoscale mock webserver test refactoring. (#67)

[jclouds-labs-openstack-pull-requests #126](https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack-pull-requests/126/) UNSTABLE 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-openstack/pull/6

Re: [jclouds-examples] Updates examples to use the 1.7.0 release (#26)

> I added a blurb about updating examples Thanks! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-examples/pull/26#issuecomment-30881546

Re: [jclouds-examples] Updates examples to use the 1.7.0 release (#26)

I added a blurb about updating examples to: https://wiki.apache.org/jclouds/Releasing%20jclouds --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-examples/pull/26#issuecomment-30881241

Build failed in Jenkins: jclouds-labs-openstack » jclouds openstack-glance api #186

See -- [...truncated 354 lines...] Downloaded: http://repo.cloudbees.com/content/repositories/central/org/apache/maven/plugins/maven-jar-plugin/2.4/

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

See Changes: [Everett Toews] Added rackspace-cloudqueues-uk to parent POM. -- [...truncated 493 lines...] Downloading: http://repo.cloudbees.com/content/repositories/central/aopalli

Re: [jclouds-labs-openstack] Finishes autoscale mock webserver test refactoring. (#67)

Probably. "Works on my machine" --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/67#issuecomment-30877368

Re: [jclouds-labs-openstack] Finishes autoscale mock webserver test refactoring. (#67)

> jclouds-labs-openstack-pull-requests #125 UNSTABLE Still one [failing test](https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack-pull-requests/org.apache.jclouds.labs$rackspace-autoscale/125/testReport/org.jclouds.rackspace.autoscale.v1.features/ScalingPolicyApiMockTest/testListScalingPo

Re: [jclouds-labs-openstack] Added rackspace-cloudqueues-uk to parent POM. (#68)

Merged to master and 1.7.x --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/68#issuecomment-30877031

Re: [jclouds-labs-openstack] Finishes autoscale mock webserver test refactoring. (#67)

[jclouds-labs-openstack-pull-requests #125](https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack-pull-requests/125/) UNSTABLE 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-openstack/pull/6

Re: [jclouds-labs-openstack] Finishes autoscale mock webserver test refactoring. (#67)

[jclouds-labs-openstack-pull-requests #124](https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack-pull-requests/124/) UNSTABLE 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-openstack/pull/6

Re: Where should admin tooling for jclouds go?

BlobStoreCli replaces some uses of the existing karaf-based jclouds-cli using really-executable-jar. This offers a more intuitive user experience and slimmer binary size. This is probably a different discussion, but it sounds like the feeling is that Karaf is not sufficiently improvable to ma

Re: [jclouds-labs-openstack] Finishes autoscale mock webserver test refactoring. (#67)

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

Re: [jclouds] Add BlobStoreBench to jclouds. (#239)

> Create a jclouds-tools or whatever repo and make this the first module in > there (should be doable quickly) > Decide what and how to merge any other tools into this repo +1 --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/239#issuecomment-30872278

Re: [jclouds] Add BlobStoreBench to jclouds. (#239)

> suggested we can merge some of the other repos into a tools repo. Thoughts? I think it's a good suggestion, but I agree with @andrewgaul that we ideally don't want to wait until we've decided and what and how to do the merge before getting this functionality it. I was trying to split that into

Re: Where should admin tooling for jclouds go?

On Wed, Dec 18, 2013 at 07:59:48PM +0100, Andrew Phillips wrote: > With #239 [1], we'll hopefully be able to get an interesting and useful > benchmarking tool from Maginatics out to the wider jclouds audience. Some > debate going on in the issue, though, about where the right place for this > and r

Re: [jclouds] Add BlobStoreBench to jclouds. (#239)

@jdaggett suggested we can merge some of the other repos into a tools repo. Thoughts? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/239#issuecomment-30870938

Jenkins build is back to stable : jclouds-1.6.x-branch » jclouds compute core #234

See

Where should admin tooling for jclouds go?

With #239 [1], we'll hopefully be able to get an interesting and useful benchmarking tool from Maginatics out to the wider jclouds audience. Some debate going on in the issue, though, about where the right place for this and related administrative tools and utilities should be. I personal

Re: [jclouds] Add BlobStoreBench to jclouds. (#239)

> I do not want the perfect to be the enemy of the good. I agree, but I think we can still put a little thought into where this and, indeed (as you say) related types of admin tools should go before we need to accuse ourselves of "striving for immediate perfection". I don't think the code needs

Re: [jclouds] Add BlobStoreBench to jclouds. (#239)

> +# Blobstore credentials > +IDENTITY="myidentity" > +CREDENTIAL="secretCreds" > + > +# Container used for the test. For "transient" and "filesystem" providers, > +# the container gets created at runtime. For others, it is expected to > +# be present. > +CONTAINER=jclouds-container > + > +# Start

Re: [jclouds] Add BlobStoreBench to jclouds. (#239)

> +# Licensed to the Apache Software Foundation (ASF) under one or more > +# contributor license agreements. See the NOTICE file distributed with > +# this work for additional information regarding copyright ownership. > +# The ASF licenses this file to You under the Apache License, Version 2.0 >

Re: [jclouds] Add BlobStoreBench to jclouds. (#239)

> + > jar-with-dependencies > + false > + true > + > + implementation="org.apache.maven.plugins.shade.resource.ServicesResourceTransformer"/> > + > + > + > + > + > + > + > +

Re: [jclouds] Add BlobStoreBench to jclouds. (#239)

> +import org.kohsuke.args4j.Option; > + > +import com.google.common.base.Preconditions; > +import com.google.common.base.Stopwatch; > +import com.google.common.collect.Iterables; > +import com.google.common.collect.Lists; > +import com.google.common.io.ByteStreams; > +import com.google.common.net.

Re: [jclouds] Add BlobStoreBench to jclouds. (#239)

I believe BlobStoreBench should live in the main repository in blobstore-tools as this commit does. We could recast this in karaf/cli although that has some drawbacks, including being unfriendly for developers to work with and more importantly poor user experience. This pull request raises a g

Re: Limited memory *only* in integration tests

Ignasi, have you by chance timed the differences on the tests? I can run them here, but just wanted to see if you had any data first. It is great to get a speed increase on just about anything! ;) On Wed, Dec 18, 2013 at 7:08 AM, Ignasi Barrera wrote: > Yes, removing this it speeds up a bit the

Jenkins build became unstable: jclouds-1.6.x-branch » jclouds compute core #233

See

Re: [jclouds] Add BlobStoreBench to jclouds. (#239)

Agree on trying to keep the number of repos down. And I think @abayer might not be too unhappy about trying to at least combine karaf and cli, since in practice it seems like they version in lockstep anyway. Would like to hear from @iocanel on that subject, though. My thinking behind jclouds-ex

Re: [jclouds] Add BlobStoreBench to jclouds. (#239)

Perhaps examples is not the place for this, but can we do this without more repos? /cringe --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/239#issuecomment-30862250

Re: [jclouds] Add BlobStoreBench to jclouds. (#239)

@demobox WDYT about creating a "jclouds-tools" repo for this kind of jclouds tooling? I don't think putting it in the examples project makes sense for these types of integrations. If we did this, we could reduce the number of repos by collapsing karaf/cli/chef into a single repo with subprojects

Jenkins build is back to normal : jclouds-1.6.x-branch » jcloud s3 api #232

See

Build failed in Jenkins: jclouds-1.6.x-branch » jcloud s3 api #231

See -- [...truncated 486 lines...] WARNING: provider [mock] is not setup as META-INF/services/org.jclouds.apis.ApiMetadata or META-INF/services/org.jclouds.provider

Jenkins build is back to stable : jclouds-1.6.x-branch » jclouds compute core #230

See

Re: [jclouds] Add OkHttp driver to support modern HTTP verbs (#232)

[jclouds-java-7-pull-requests #949](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/949/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/232#issuecomment-30849140

Re: [jclouds] Add OkHttp driver to support modern HTTP verbs (#232)

[jclouds-pull-requests #486](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/486/) UNSTABLE 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/pull/232#issuecomment-30849033

Re: Limited memory *only* in integration tests

Yes, removing this it speeds up a bit the tests, and also improves some tests that perform operations on big files (such as an upload). I think we could safely remove that (given that neither unit nor live tests use those options), but I'd prefer to ask first for opinions. On 18 December 2013 16:0

Re: Limited memory *only* in integration tests

Out of curiosity, Does anyone know why we are explicitly configuring the memory for the "integration" tests [1], but not for the "unit" and "live" tests? Can we just remove that line? Do you have any information on what effect that change with have? Does it speed things up? Are there any prob

Jenkins build became unstable: jclouds-1.6.x-branch » jclouds compute core #229

See

Limited memory *only* in integration tests

Out of curiosity, Does anyone know why we are explicitly configuring the memory for the "integration" tests [1], but not for the "unit" and "live" tests? Can we just remove that line? [1] https://github.com/jclouds/jclouds/blob/master/project/pom.xml#L519

Re: [jclouds] Add OkHttp driver to support modern HTTP verbs (#232)

[jclouds-java-7-pull-requests #948](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/948/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/232#issuecomment-30835200

Jenkins build is back to stable : jclouds-1.6.x-branch » jclouds compute core #226

See

Re: [jclouds] Add OkHttp driver to support modern HTTP verbs (#232)

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

Re: [jclouds] Add OkHttp driver to support modern HTTP verbs. DO NOT MERGE! (#232)

So finally, I've finished refactoring and rebasing everything to the latest version of master. Things to consider: * I've rewritten the entire `BaseHttpCommandExecutorServiceIntegrationTest` class to use mockwebserver in all tests (and also added a few more). I've taken special care in keeping

Jenkins build became unstable: jclouds-1.6.x-branch » jclouds compute core #225

See