Commit Graph

210 Commits

Author SHA1 Message Date
Robert Muir 2f00ebbabc Use ThirdParty annotation and remove duplicate test config.
See https://github.com/elastic/elasticsearch-parent/issues/41
2015-05-13 22:33:38 -04:00
Robert Muir c1f25b0245 enable security manager in tests 2015-05-13 13:32:01 -04:00
Robert Muir 98b765839f Mark frequently failing test methods AwaitsFix until #211 is sorted out. 2015-05-12 20:58:07 -04:00
Robert Muir 8ce8527af9 disable security manager until #210 has been addressed. 2015-05-11 21:32:47 -04:00
Robert Muir 963f60f4d4 remove unnecessary prop 2015-05-11 21:26:09 -04:00
Robert Muir 2e7726791d Remove outdated policy file 2015-05-11 19:44:53 -04:00
Robert Muir 5e672bdd55 enable security manager in tests 2015-05-11 19:39:51 -04:00
Robert Muir ae323a4742 Merge pull request #208 from rmuir/disable_response_metadata_cache
Disable response metadata cache.
2015-05-11 08:54:07 -04:00
Robert Muir d8283abf08 Disable response metadata cache in this ClientConfiguration as well. 2015-05-08 12:41:43 -04:00
Robert Muir a36de1b4e3 Disable response metadata cache.
This cache is only used for diagnostic purposes, but
can force objects from every response to the old generation.

Fixes #193
2015-05-08 12:32:26 -04:00
Robert Muir 3aab63cfa2 Tests: set path.home in AbstractAwsTest 2015-05-05 14:14:51 -04:00
Robert Muir 8ed09b20cf Tests: fix compilation error 2015-05-05 14:11:07 -04:00
David Pilato e00c099f18 Fix non working update dynamic settings
Described in https://github.com/elastic/elasticsearch/issues/10614, it's not possible with cloud discovery plugin to update dynamic settings anymore.

```sh
curl -XPUT localhost:9200/_cluster/settings -d '{
    "persistent" : {
        "discovery.zen.minimum_master_nodes" : 3
    },
    "transient" : {
        "discovery.zen.minimum_master_nodes" : 3
    }
}'
```

gives

```json
{"acknowledged":true,"persistent":{},"transient":{}}
```

This patch makes that working again.

(cherry picked from commit 37d6897)
(cherry picked from commit 7a8c7b0ed5601dc71b8d3376cd197b8e0db2bbbd)

Conflicts:
	src/main/java/org/elasticsearch/discovery/ec2/Ec2Discovery.java
2015-04-29 13:51:49 +02:00
David Pilato 16d376e714 [test] Cleanup Directory and Searcher mock code
Related to https://github.com/elastic/elasticsearch/pull/10853

Closes #205.
2015-04-29 11:24:54 +02:00
David Pilato 899e84c01e Remove `ElasticsearchIllegalArgumentException` and `ElasticsearchIllegalStateException` in favor of the JDK one
Related to https://github.com/elastic/elasticsearch/issues/10794

Closes #204.
2015-04-29 11:22:28 +02:00
David Pilato 39776944d5 Add EC2/S3 Signer API setting
If you are using a compatible EC2 or S3 service, they might be using an older API to sign the requests.

You can set your compatible signer API using `cloud.aws.signer` (or `cloud.aws.ec2.signer` and `cloud.aws.s3.signer`) with the right signer to use.

Defaults to `AWS4SignerType`.

Supported today (time when this commit is done):

* `QueryStringSignerType`
* `AWS3SignerType`
* `AWS4SignerType`
* `NoOpSignerType`

Closes #155.
(cherry picked from commit 33b18b4)
(cherry picked from commit 9809af5)
2015-04-24 12:47:11 +02:00
David Pilato a723875148 update documentation with release 2.5.0 2015-03-25 10:35:48 +01:00
David Pilato 09993f30bf Update aws-sdk-java to 1.9.23
Release notes:

* [1.9.23](https://aws.amazon.com/releasenotes/Java/0061646886197506)
* [1.9.22](https://aws.amazon.com/releasenotes/Java/9983269688843537)
* [1.9.21](https://aws.amazon.com/releasenotes/Java/0068314282259743)
* [1.9.20.1](https://aws.amazon.com/releasenotes/Java/1468424988909152)
* [1.9.20](https://aws.amazon.com/releasenotes/Java/4095479451567110)
* [1.9.19](https://aws.amazon.com/releasenotes/Java/7152067748916749)
* [1.9.18](https://aws.amazon.com/releasenotes/Java/8255923333358616)
* [1.9.17](https://aws.amazon.com/releasenotes/Java/7976814583460560)
* [1.9.16](https://aws.amazon.com/releasenotes/Java/7930704610010512)
* [1.9.15](https://aws.amazon.com/releasenotes/Java/7196148869312092)
* [1.9.14](https://aws.amazon.com/releasenotes/Java/5550164873229724)
* [1.9.13](https://aws.amazon.com/releasenotes/Java/4588838060473154)
* [1.9.12](https://aws.amazon.com/releasenotes/Java/4184046784243318)
* [1.9.11](https://aws.amazon.com/releasenotes/Java/4181470878749498)
* [1.9.10](https://aws.amazon.com/releasenotes/Java/7263787800932935)
* [1.9.9](https://aws.amazon.com/releasenotes/Java/1369906126177804)

(cherry picked from commit 16a2f39)
(cherry picked from commit 5e13c68)
(cherry picked from commit 471f755)
2015-03-25 10:06:05 +01:00
David Pilato 6f403f3c73 Move to elastic owner
(cherry picked from commit ec9d00f)
(cherry picked from commit 2a4642e)
2015-03-25 09:57:24 +01:00
David Pilato 9f87d180f3 Move parent after artifact coordinates 2015-03-25 09:56:34 +01:00
David Pilato 6f1efd24e4 Create `es-1.5` branch 2015-03-16 12:42:08 -07:00
paul-e-cooley cb7beec5b2 Separate proxy traffic for ec2 and s3
Based on PR #178 by @paul-e-cooley. Thanks Paul!

In addition to:

```yaml
cloud:
    aws:
        protocol: https
        proxy_host: proxy1.company.com
        proxy_port: 8083
```

You can also set different proxies for `ec2` and `s3`:

```yaml
cloud:
    aws:
        s3:
            proxy_host: proxy1.company.com
            proxy_port: 8083
        ec2:
            proxy_host: proxy2.company.com
            proxy_port: 8083
```

PR rebased on master and lastest changes about component settings removal.
Documentation added.
Changes in tests. If a proxy is provided we run the tests, otherwise we ignore the test.

Closes #177.
2015-03-09 14:19:11 -07:00
David Pilato 7a7de12538 Remove component settings from AbstractComponent
Related to elasticsearch/elasticsearch#9919

Closes #182.
2015-02-27 16:32:50 +01:00
Igor Motov 20a99919bf Update settings filter
Update settings filter to match elasticsearch/elasticsearch#9748
2015-02-24 13:24:02 -05:00
Jerry 3a4e472752 [doc] secret_key: <access key> should be <secret key>
Closes #168.
2015-02-19 21:34:03 +01:00
David Pilato de2ab73c8a Simplify region setting code 2015-02-19 21:26:45 +01:00
Marcin Matlaszek 68fea581a2 Fix region settings for s3 snapshot repository in eu-west-1
Closes #169.
2015-02-19 21:26:38 +01:00
David Pilato 4c02a017b4 Wrong endpoint for `cn-north-1`
Commit ea9609c642 does not work as expected.

China is not part of the [S3 regions](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region) but part of [Isolated Regions](http://docs.aws.amazon.com/general/latest/gr/isolated_regions.html).

The patch uses for S3 `s3-cn-north-1.amazonaws.com` which is wrong because in that case the end point is `s3.cn-north-1.amazonaws.com.cn`.
Same goes for EC2 which was `ec2.cn-north-1.amazonaws.com` but should be `ec2.cn-north-1.amazonaws.com.cn`.

Related documentation:

* http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region
* http://docs.aws.amazon.com/general/latest/gr/rande.html#ec2_region
* http://docs.aws.amazon.com/general/latest/gr/isolated_regions.html

Closing #156
(cherry picked from commit 491a59b)
(cherry picked from commit f12cacc)
2015-02-19 16:50:48 +01:00
Andreas Kohn c7187f2db5 Remove an excess quote character in an exception message 2015-02-19 16:15:14 +01:00
Serhiy Suprun e05036f257 Fixed address resolution 2015-02-18 16:50:58 +02:00
David Pilato e6080e9017 Move AwsEc2UnicastHostsProvider to Ec2DiscoveryModule
Related to https://github.com/elasticsearch/elasticsearch/pull/9099
2015-01-30 11:14:40 +01:00
David Pilato 377e7e0c78 Fix typo (azure -> s3) 2015-01-02 23:09:36 +01:00
David Pilato ea9609c642 Add China region for s3 and ec2
China region name is `cn-north-1`.

Closes #156.
2015-01-02 22:28:50 +01:00
David Pilato a76e93502f Implement BlobContainer.move()
In elasticsearch master (2.0) a new method `move(String sourceBlobName, String targetBlobName)` has been added to `BlobContainer`.

Closes #152.
2015-01-02 22:16:59 +01:00
David Pilato d36e24a626 Add sonatype snapshot repository 2015-01-02 21:10:01 +01:00
David Pilato 2df835008e Depend on elasticsearch-parent
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.
2014-12-17 10:18:59 +01:00
Adrien Grand 50e5149485 Upgrade to Lucene 5.0.0-snapshot-1642891 2014-12-02 18:19:35 +01:00
tlrx 849e697385 Update AWS SDK to 1.9.8
Closes #148
2014-11-26 16:47:15 +01:00
tlrx 77e9d7f16f Merge branch 'split-aws-java-sdk' of https://github.com/Collaborne/elasticsearch-cloud-aws into Collaborne-split-aws-java-sdk 2014-11-26 16:44:44 +01:00
tlrx d0c712299b Merge #137
Closes #136
2014-11-26 16:38:37 +01:00
tlrx f4057f2a83 Remove unnecessary settings in test method 2014-11-26 12:48:45 +01:00
tlrx d680b94eb7 Fix unit tests and some bugs introduced by #128
Closes #119, #147
2014-11-26 11:04:29 +01:00
tlrx 61a307f28d Merge branch 'brutasse-feature/per-repo-endpoint' 2014-11-26 10:58:01 +01:00
tlrx 20576820a6 Merge branch 'feature/per-repo-endpoint' of https://github.com/brutasse/elasticsearch-cloud-aws into brutasse-feature/per-repo-endpoint 2014-11-26 10:57:20 +01:00
David Pilato fca3addbaf Fix latest plugin version 2014-11-24 18:16:35 +01:00
David Pilato 9f359bcd62 update documentation with release 2.4.1 2014-11-24 17:30:33 +01:00
David Pilato 66cedb350e AwsEc2UnicastHostsProvider should use version.minimumCompatibilityVersion()
The AwsEc2UnicastHostsProvider creates DiscoveryNodes that are used as an initial seed for unicast based discovery. At the moment it uses Version.CURRENT (see [1]) for those DiscoveryNode object, which confuses the backwards compatibility layer to think this nodes are of the latest version. This causes new nodes to fail to join old nodes as the ping serialization goes wrong. Instead we should use version.minimumCompatibilityVersion(). See [2]

[1] https://github.com/elasticsearch/elasticsearch-cloud-aws/blob/es-1.x/src/main/java/org/elasticsearch/discovery/ec2/AwsEc2UnicastHostsProvider.java#L165
[2] https://github.com/elasticsearch/elasticsearch/blob/master/src/main/java/org/elasticsearch/discovery/zen/ping/unicast/UnicastZenPing.java#L130

Ps. this was reported on the mailing list. See: https://groups.google.com/forum/#!msg/elasticsearch/8pUwFld88tI/7jRuG6hqtbAJ

Closes #143.
2014-11-24 16:06:11 +01:00
Michael McCandless 3f8a053da8 Upgrade to Lucene 5.0.0-snapshot-1641343 2014-11-24 05:52:10 -05:00
Bruno Renié 30d80cc27d Allow per-repo protocols
Also add an integration test for custom endpoints/protocols.
2014-11-21 18:05:48 +01:00
Bruno Renié 2203f439e2 Merge branch 'master' into feature/per-repo-endpoint
Conflicts:
	src/main/java/org/elasticsearch/cloud/aws/AwsS3Service.java
	src/main/java/org/elasticsearch/cloud/aws/InternalAwsS3Service.java
	src/main/java/org/elasticsearch/repositories/s3/S3Repository.java
2014-11-21 11:00:01 +01:00