honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
OpenSearch/x-pack/plugin/ccr/qa/multi-cluster/build.gradle

66 lines
2.3 KiB
Groovy
Raw Normal View History

Add the ability to the follow index to follow an index in a remote cluster. The follow index api completely reuses CCS infrastructure that was exposed via: https://github.com/elastic/elasticsearch/pull/29495 This means that the leader index parameter support the same ccs index to indicate that an index resides in a different cluster. I also added a qa module that smoke tests the cross cluster nature of ccr. The idea is that this test just verifies that ccr can read data from a remote leader index and that is it, no crazy randomization or indirectly testing other features.
2018-04-13 13:11:28 -04:00
import org.elasticsearch.gradle.test.RestIntegTestTask
Testclusters: convert ccr tests (#42313)
2019-05-29 09:16:04 -04:00
apply plugin: 'elasticsearch.testclusters'
Add the ability to the follow index to follow an index in a remote cluster. The follow index api completely reuses CCS infrastructure that was exposed via: https://github.com/elastic/elasticsearch/pull/29495 This means that the leader index parameter support the same ccs index to indicate that an index resides in a different cluster. I also added a qa module that smoke tests the cross cluster nature of ccr. The idea is that this test just verifies that ccr can read data from a remote leader index and that is it, no crazy randomization or indirectly testing other features.
2018-04-13 13:11:28 -04:00
apply plugin: 'elasticsearch.standalone-test'
dependencies {
Required changes after merging in master branch.
2018-08-24 01:51:26 -04:00
testCompile project(path: xpackModule('core'), configuration: 'testArtifacts')
Add the ability to the follow index to follow an index in a remote cluster. The follow index api completely reuses CCS infrastructure that was exposed via: https://github.com/elastic/elasticsearch/pull/29495 This means that the leader index parameter support the same ccs index to indicate that an index resides in a different cluster. I also added a qa module that smoke tests the cross cluster nature of ccr. The idea is that this test just verifies that ccr can read data from a remote leader index and that is it, no crazy randomization or indirectly testing other features.
2018-04-13 13:11:28 -04:00
testCompile project(path: xpackModule('ccr'), configuration: 'runtime')
[CCR] Add qa test library (#34611) * Introduced test qa lib that all CCR qa modules depend on to avoid test code duplication.
2018-10-23 17:24:32 -04:00
testCompile project(':x-pack:plugin:ccr:qa')
Add the ability to the follow index to follow an index in a remote cluster. The follow index api completely reuses CCS infrastructure that was exposed via: https://github.com/elastic/elasticsearch/pull/29495 This means that the leader index parameter support the same ccs index to indicate that an index resides in a different cluster. I also added a qa module that smoke tests the cross cluster nature of ccr. The idea is that this test just verifies that ccr can read data from a remote leader index and that is it, no crazy randomization or indirectly testing other features.
2018-04-13 13:11:28 -04:00
}
Testclusters: convert ccr tests (#42313)
2019-05-29 09:16:04 -04:00
task "leader-cluster"(type: RestIntegTestTask) {
Add the ability to the follow index to follow an index in a remote cluster. The follow index api completely reuses CCS infrastructure that was exposed via: https://github.com/elastic/elasticsearch/pull/29495 This means that the leader index parameter support the same ccs index to indicate that an index resides in a different cluster. I also added a qa module that smoke tests the cross cluster nature of ccr. The idea is that this test just verifies that ccr can read data from a remote leader index and that is it, no crazy randomization or indirectly testing other features.
2018-04-13 13:11:28 -04:00
mustRunAfter(precommit)
Testclusters: convert ccr tests (#42313)
2019-05-29 09:16:04 -04:00
runner {
systemProperty 'tests.target_cluster', 'leader'
}
Add the ability to the follow index to follow an index in a remote cluster. The follow index api completely reuses CCS infrastructure that was exposed via: https://github.com/elastic/elasticsearch/pull/29495 This means that the leader index parameter support the same ccs index to indicate that an index resides in a different cluster. I also added a qa module that smoke tests the cross cluster nature of ccr. The idea is that this test just verifies that ccr can read data from a remote leader index and that is it, no crazy randomization or indirectly testing other features.
2018-04-13 13:11:28 -04:00
}
Testclusters: convert ccr tests (#42313)
2019-05-29 09:16:04 -04:00
testClusters."leader-cluster" {
distribution = "DEFAULT"
Implement CCR licensing (#33002) This commit implements licensing for CCR. CCR will require a platinum license, and administrative endpoints will be disabled when a license is non-compliant.
2018-08-20 23:33:18 -04:00
setting 'xpack.license.self_generated.type', 'trial'
Add the ability to the follow index to follow an index in a remote cluster. The follow index api completely reuses CCS infrastructure that was exposed via: https://github.com/elastic/elasticsearch/pull/29495 This means that the leader index parameter support the same ccs index to indicate that an index resides in a different cluster. I also added a qa module that smoke tests the cross cluster nature of ccr. The idea is that this test just verifies that ccr can read data from a remote leader index and that is it, no crazy randomization or indirectly testing other features.
2018-04-13 13:11:28 -04:00
}
[CCR] Restructured QA modules (#36404) Renamed the follow qa modules: `multi-cluster-downgraded-to-basic-license` to `downgraded-to-basic-license` `multi-cluster-with-non-compliant-license` to `non-compliant-license` `multi-cluster-with-security` to `security` Moved the `chain` module into the `multi-cluster` module and changed the `multi-cluster` to start 3 clusters. Followup from #36031
2018-12-09 13:34:48 -05:00
Testclusters: convert ccr tests (#42313)
2019-05-29 09:16:04 -04:00
task "middle-cluster"(type: RestIntegTestTask) {
dependsOn "leader-cluster"
useCluster testClusters."leader-cluster"
runner {
systemProperty 'tests.target_cluster', 'middle'
nonInputProperties.systemProperty 'tests.leader_host',
"${-> testClusters."leader-cluster".getAllHttpSocketURI().get(0)}"
}
}
testClusters."middle-cluster" {
distribution = "DEFAULT"
[CCR] Restructured QA modules (#36404) Renamed the follow qa modules: `multi-cluster-downgraded-to-basic-license` to `downgraded-to-basic-license` `multi-cluster-with-non-compliant-license` to `non-compliant-license` `multi-cluster-with-security` to `security` Moved the `chain` module into the `multi-cluster` module and changed the `multi-cluster` to start 3 clusters. Followup from #36031
2018-12-09 13:34:48 -05:00
setting 'xpack.license.self_generated.type', 'trial'
Testclusters: convert ccr tests (#42313)
2019-05-29 09:16:04 -04:00
setting 'cluster.remote.leader_cluster.seeds',
{ "\"${testClusters."leader-cluster".getAllTransportPortURI().join(",")}\"" }
[CCR] Restructured QA modules (#36404) Renamed the follow qa modules: `multi-cluster-downgraded-to-basic-license` to `downgraded-to-basic-license` `multi-cluster-with-non-compliant-license` to `non-compliant-license` `multi-cluster-with-security` to `security` Moved the `chain` module into the `multi-cluster` module and changed the `multi-cluster` to start 3 clusters. Followup from #36031
2018-12-09 13:34:48 -05:00
}
Testclusters: convert ccr tests (#42313)
2019-05-29 09:16:04 -04:00
task 'follow-cluster'(type: RestIntegTestTask) {
dependsOn "leader-cluster", "middle-cluster"
useCluster testClusters."leader-cluster"
useCluster testClusters."middle-cluster"
runner {
systemProperty 'tests.target_cluster', 'follow'
nonInputProperties.systemProperty 'tests.leader_host',
"${-> testClusters."leader-cluster".getAllHttpSocketURI().get(0)}"
nonInputProperties.systemProperty 'tests.middle_host',
"${-> testClusters."middle-cluster".getAllHttpSocketURI().get(0)}"
}
[CCR] Restructured QA modules (#36404) Renamed the follow qa modules: `multi-cluster-downgraded-to-basic-license` to `downgraded-to-basic-license` `multi-cluster-with-non-compliant-license` to `non-compliant-license` `multi-cluster-with-security` to `security` Moved the `chain` module into the `multi-cluster` module and changed the `multi-cluster` to start 3 clusters. Followup from #36031
2018-12-09 13:34:48 -05:00
}
Testclusters: convert ccr tests (#42313)
2019-05-29 09:16:04 -04:00
testClusters."follow-cluster" {
distribution = "DEFAULT"
Expose CCR stats to monitoring (#33617) This commit exposes the CCR stats endpoint to monitoring collection. Co-authored-by: Martijn van Groningen <martijn.v.groningen@gmail.com>
2018-09-12 09:13:07 -04:00
setting 'xpack.monitoring.collection.enabled', 'true'
Implement CCR licensing (#33002) This commit implements licensing for CCR. CCR will require a platinum license, and administrative endpoints will be disabled when a license is non-compliant.
2018-08-20 23:33:18 -04:00
setting 'xpack.license.self_generated.type', 'trial'
Testclusters: convert ccr tests (#42313)
2019-05-29 09:16:04 -04:00
setting 'cluster.remote.leader_cluster.seeds',
{ "\"${testClusters."leader-cluster".getAllTransportPortURI().join(",")}\""}
setting 'cluster.remote.middle_cluster.seeds',
{ "\"${testClusters."middle-cluster".getAllTransportPortURI().join(",")}\""}
Add the ability to the follow index to follow an index in a remote cluster. The follow index api completely reuses CCS infrastructure that was exposed via: https://github.com/elastic/elasticsearch/pull/29495 This means that the leader index parameter support the same ccs index to indicate that an index resides in a different cluster. I also added a qa module that smoke tests the cross cluster nature of ccr. The idea is that this test just verifies that ccr can read data from a remote leader index and that is it, no crazy randomization or indirectly testing other features.
2018-04-13 13:11:28 -04:00
}
Testclusters: convert ccr tests (#42313)
2019-05-29 09:16:04 -04:00
check.dependsOn "follow-cluster"
[Backport] Replace usages RandomizedTestingTask with built-in Gradle Test (#40978) (#40993) * Replace usages RandomizedTestingTask with built-in Gradle Test (#40978) This commit replaces the existing RandomizedTestingTask and supporting code with Gradle's built-in JUnit support via the Test task type. Additionally, the previous workaround to disable all tasks named "test" and create new unit testing tasks named "unitTest" has been removed such that the "test" task now runs unit tests as per the normal Gradle Java plugin conventions. (cherry picked from commit 323f312bbc829a63056a79ebe45adced5099f6e6) * Fix forking JVM runner * Don't bump shadow plugin version
2019-04-09 14:52:50 -04:00
test.enabled = false // no unit tests for multi-cluster-search, only the rest integration test