GCE API have been updated to `v1-rev59-1.20.0`.
We now can depend only on:
```xml
<dependency>
<groupId>com.google.apis</groupId>
<artifactId>google-api-services-compute</artifactId>
<version>v1-rev59-1.20.0</version>
</dependency>
```
It comes with all needed dependencies.
Closes#49.
(cherry picked from commit f95dc16)
(cherry picked from commit 4ee6c95)
To simplify plugins maintenance and provide more value in the future, we are starting to build an `elasticsearch-parent` project. This commit is the first step for this plugin to depend on this new `pom` maven project.
When upgrading to elasticsearch 1.2.1 test framework, some tests are not working anymore because of
`ElasticsearchIntegrationTest#ensureClusterSizeConsistency()` method which check that the number of started nodes
is the number of available nodes in the cluster.
Disabling them temporary.
Also, a new clientNode could be added (depends on seed). It adds a node more than expected.
(cherry picked from commit bcc2cd5)
We create branches:
* es-0.90 for elasticsearch 0.90
* es-1.0 for elasticsearch 1.0
* es-1.1 for elasticsearch 1.1
* master for elasticsearch master
We also check that before releasing we don't have a dependency to an elasticsearch SNAPSHOT version.
Add links to each version in documentation
(cherry picked from commit a51926c)
Google Compute Engine VM discovery allows to use the google APIs to perform automatic discovery (similar to multicast in non hostile
multicast environments). Here is a simple sample configuration:
```yaml
cloud:
gce:
project_id: <your-google-project-id>
zone: <your-zone>
discovery:
type: gce
```
How to start (short story)
--------------------------
* Create Google Compute Engine instance
* Install Elasticsearch
* Install Google Compute Engine Cloud plugin
* Modify `elasticsearch.yml` file
* Start Elasticsearch
Closes#1.
