New AWS cloud plugin, removed old cloud plugin

Elastic Stack Elasticsearch
1

Hi,

The last feature of 0.9 is done. It includes removing the old cloud
plugin (based on jclouds) and implementing an AWS specific cloud plugin. The
issue and the description on how to use the new cloud-aws plugin is here:
http://github.com/elasticsearch/elasticsearch/issues/264.

I ended up using the formal AWS SDK from amazon, though I am still not

very happy with it (does not use non blocking IO), but for now, its good,
and you can't go wrong by going directly to the source (one would hope...).

One of the nice things about it is that there are specific amazon

settings now to better control both the gateway and the discovery. And, I
have some nice ideas on how to implement more "native" cloud support with
the AWS specific plugin. Stay tunes (post 0.9).

This is the last feature for 0.9, I will start working on the docs for

0.9, and expect it to be released in the next couple of days. I would really
really appreciate people test driving this new cloud-aws plugin to flush out
possible problems before 0.9 is released.

Now that the list of cloud providers has been reduced to AWS, which

seems to be the most popular one ;). Are you using other cloud providers? On
my list I have rackspace next, but would revise it based on demand.

-shay.banon

2

We are planning to deploy to EC2 using Scalr to control instances. Scalr
also supports RackSpace, so that would be where I would want to test next.

-- jim

On Sat, Jul 24, 2010 at 4:58 PM, Shay Banon shay.banon@elasticsearch.comwrote:

Hi,

The last feature of 0.9 is done. It includes removing the old cloud
plugin (based on jclouds) and implementing an AWS specific cloud plugin. The
issue and the description on how to use the new cloud-aws plugin is here:
AWS Cloud Plugin: Implement AWS specific cloud plugin with S3 gateway and EC2 discovery · Issue #264 · elastic/elasticsearch · GitHub.

I ended up using the formal AWS SDK from amazon, though I am still not

very happy with it (does not use non blocking IO), but for now, its good,
and you can't go wrong by going directly to the source (one would hope...).

One of the nice things about it is that there are specific amazon

settings now to better control both the gateway and the discovery. And, I
have some nice ideas on how to implement more "native" cloud support with
the AWS specific plugin. Stay tunes (post 0.9).

This is the last feature for 0.9, I will start working on the docs for

0.9, and expect it to be released in the next couple of days. I would really
really appreciate people test driving this new cloud-aws plugin to flush out
possible problems before 0.9 is released.

Now that the list of cloud providers has been reduced to AWS, which

seems to be the most popular one ;). Are you using other cloud providers? On
my list I have rackspace next, but would revise it based on demand.

-shay.banon