You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jclouds.apache.org by na...@apache.org on 2014/03/13 14:27:46 UTC
git commit: Updating the features section to match the website
Repository: jclouds
Updated Branches:
refs/heads/master 8dafeacfe -> b444886c5
Updating the features section to match the website
Project: http://git-wip-us.apache.org/repos/asf/jclouds/repo
Commit: http://git-wip-us.apache.org/repos/asf/jclouds/commit/b444886c
Tree: http://git-wip-us.apache.org/repos/asf/jclouds/tree/b444886c
Diff: http://git-wip-us.apache.org/repos/asf/jclouds/diff/b444886c
Branch: refs/heads/master
Commit: b444886c5c2a34f4e751066b38b24b1dcaa3f57c
Parents: 8dafeac
Author: Roman C. Coedo <ro...@gmail.com>
Authored: Thu Mar 13 08:53:48 2014 +0100
Committer: Ignasi Barrera <na...@apache.org>
Committed: Thu Mar 13 14:27:21 2014 +0100
----------------------------------------------------------------------
README.md | 17 +++++++----------
1 file changed, 7 insertions(+), 10 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/jclouds/blob/b444886c/README.md
----------------------------------------------------------------------
diff --git a/README.md b/README.md
index 96f5248..0e7f40b 100644
--- a/README.md
+++ b/README.md
@@ -12,27 +12,25 @@ Features
Even if you don't need the portable apis we provide, or could roll it your own, programming against cloud environments can be challenging. We focus on the following areas so that you can focus on using the cloud, rather than troubleshooting it!
* SIMPLE INTERFACE
-Instead of creating new object types, we reuse concepts like maps so that the programming model is familiar. In this way, you can get started without dealing with the cloud providers' REST-like apis or WebServices directly.
+Get started without dealing with REST-like APIs or WebServices. Instead of creating new object types, jclouds reuses concepts like maps so that the programming model is familiar.
* RUNTIME PORTABILITY
-We have drivers that allow you to operate in restricted environments like Google App Engine. We have very few required dependencies, so we are unlikely to clash with your app.
+jclouds drivers enable you to operate in restricted environments like Google App Engine. There are very few required dependencies, so jclouds is unlikely to clash with your app.
* DEAL WITH WEB COMPLEXITY
-Network based computing introduces issues such as transient failures and redirects.
-We handle this for you.
+jclouds handles issues such as transient failures and redirects that traditional network based computing introduces.
* UNIT TESTABILITY
-Writing tests for cloud endpoints is difficult. We provide you with Stub connections that simulate a cloud without creating network connections. In this way, you can write your unit tests without mocking complexity or the brittleness of remote connections.
+Write your unit tests without mocking complexity or the brittleness of remote connections. Writing tests for cloud endpoints is difficult. jclouds provides you with Stub connections that simulate a cloud without creating network connections.
* PERFORMANCE
-Customize configuration to match your performance needs. jclouds provides you with asynchronous commands and tunable http, date, encryption, and encryption modules.
+Customize configuration to match your performance needs. jclouds provides you with asynchronous commands, tunable http, date, and encryption modules.
* LOCATION
-All of our abstractions are location-aware. For example, you can get ISO-3166 codes to tell which country or province a cloud runs in.
+jclouds provides location-aware abstractions. For example, you can get ISO-3166 codes to tell which country or province a cloud runs in.
* QUALITY
-We test every provider with live scenarios before each release. If it doesn't pass, the provider goes into the sandbox.
-
+Every provider is tested with live scenarios before each release. If the provider doesn't pass, it goes back into the sandbox.
BlobStore
-----------
@@ -129,7 +127,6 @@ Resources
* Dev group: http://groups.google.com/group/jclouds-dev
* Twitter: http://twitter.com/jclouds
-
License
-------
Copyright (C) 2009-2013 The Apache Software Foundation
Re: git commit: Updating the features section to match the website
Posted by Ignasi Barrera <ig...@gmail.com>.
Before every release I test all the compute providers I have
credentials for. Here is a summary of the live tests results I've run:
rackspace-cloudqueues-us: Tests run: 32, Failures: 0, Errors: 0, Skipped: 0
rackspace-cloudservers-us: Tests run: 145, Failures: 10, Errors: 0, Skipped: 0
cloudsigma2-lvs - Tests run: 50, Failures: 0, Errors: 0, Skipped: 0
digitalocean: Tests run: 53, Failures: 0, Errors: 0, Skipped: 0
enterprisechef: Tests run: 47, Failures: 0, Errors: 0, Skipped: 0
chef11: Tests run: 50, Failures: 0, Errors: 0, Skipped: 0
chef10: Tests run: 50, Failures: 0, Errors: 0, Skipped: 0
joyent provider is out of date and we should consider removing it.
hpcloud-compute just launched a new offering with a new version, which
is the default for new accounts. I've created an account and I've been
able to use the compute service (by manually setting the api version
to "2" when creating the context), but many live tests are failing for
me due to floating ip and region issues (regions are different for old
and new accounts). We should give some love to the new version and try
to keep it up to date.
I don't have an AWS account so I haven't been able to live test it.
I agree with Gaul that we *must* be more serious with the live tests,
at least when releasing.
On 13 March 2014 18:01, Andrew Gaul <ga...@apache.org> wrote:
> The README.md quality section caught my eye in a recent commit. I test
> the major blobstore providers before each release but I do not believe
> we have good coverage of the compute live tests. Can someone comment on
> the state of the world there?
>
> On Thu, Mar 13, 2014 at 01:27:46PM +0000, nacx@apache.org wrote:
>> Repository: jclouds
>> Updated Branches:
>> refs/heads/master 8dafeacfe -> b444886c5
>>
>>
>> Updating the features section to match the website
>>
>>
>> Project: http://git-wip-us.apache.org/repos/asf/jclouds/repo
>> Commit: http://git-wip-us.apache.org/repos/asf/jclouds/commit/b444886c
>> Tree: http://git-wip-us.apache.org/repos/asf/jclouds/tree/b444886c
>> Diff: http://git-wip-us.apache.org/repos/asf/jclouds/diff/b444886c
>>
>> Branch: refs/heads/master
>> Commit: b444886c5c2a34f4e751066b38b24b1dcaa3f57c
>> Parents: 8dafeac
>> Author: Roman C. Coedo <ro...@gmail.com>
>> Authored: Thu Mar 13 08:53:48 2014 +0100
>> Committer: Ignasi Barrera <na...@apache.org>
>> Committed: Thu Mar 13 14:27:21 2014 +0100
>>
>> ----------------------------------------------------------------------
>> README.md | 17 +++++++----------
>> 1 file changed, 7 insertions(+), 10 deletions(-)
>> ----------------------------------------------------------------------
>>
>>
>> http://git-wip-us.apache.org/repos/asf/jclouds/blob/b444886c/README.md
>> ----------------------------------------------------------------------
>> diff --git a/README.md b/README.md
>> index 96f5248..0e7f40b 100644
>> --- a/README.md
>> +++ b/README.md
>>
>> * QUALITY
>> -We test every provider with live scenarios before each release. If it doesn't pass, the provider goes into the sandbox.
>> -
>> +Every provider is tested with live scenarios before each release. If the provider doesn't pass, it goes back into the sandbox.
>
> --
> Andrew Gaul
> http://gaul.org/
Re: git commit: Updating the features section to match the website
Posted by Andrew Gaul <ga...@apache.org>.
The README.md quality section caught my eye in a recent commit. I test
the major blobstore providers before each release but I do not believe
we have good coverage of the compute live tests. Can someone comment on
the state of the world there?
On Thu, Mar 13, 2014 at 01:27:46PM +0000, nacx@apache.org wrote:
> Repository: jclouds
> Updated Branches:
> refs/heads/master 8dafeacfe -> b444886c5
>
>
> Updating the features section to match the website
>
>
> Project: http://git-wip-us.apache.org/repos/asf/jclouds/repo
> Commit: http://git-wip-us.apache.org/repos/asf/jclouds/commit/b444886c
> Tree: http://git-wip-us.apache.org/repos/asf/jclouds/tree/b444886c
> Diff: http://git-wip-us.apache.org/repos/asf/jclouds/diff/b444886c
>
> Branch: refs/heads/master
> Commit: b444886c5c2a34f4e751066b38b24b1dcaa3f57c
> Parents: 8dafeac
> Author: Roman C. Coedo <ro...@gmail.com>
> Authored: Thu Mar 13 08:53:48 2014 +0100
> Committer: Ignasi Barrera <na...@apache.org>
> Committed: Thu Mar 13 14:27:21 2014 +0100
>
> ----------------------------------------------------------------------
> README.md | 17 +++++++----------
> 1 file changed, 7 insertions(+), 10 deletions(-)
> ----------------------------------------------------------------------
>
>
> http://git-wip-us.apache.org/repos/asf/jclouds/blob/b444886c/README.md
> ----------------------------------------------------------------------
> diff --git a/README.md b/README.md
> index 96f5248..0e7f40b 100644
> --- a/README.md
> +++ b/README.md
>
> * QUALITY
> -We test every provider with live scenarios before each release. If it doesn't pass, the provider goes into the sandbox.
> -
> +Every provider is tested with live scenarios before each release. If the provider doesn't pass, it goes back into the sandbox.
--
Andrew Gaul
http://gaul.org/