honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-02-05 20:48:22 +00:00
Code Issues Packages Projects Releases Wiki Activity
OpenSearch/docs/plugins/discovery.asciidoc

40 lines
1.1 KiB
Plaintext
Raw Normal View History

Docs: Prepare plugin and integration docs for 2.0 * Centralised plugin docs in docs/plugins/ * Moved integrations into same docs * Moved community clients into the clients section of the docs * Removed docs/community Closes #11734 Closes #11724 Closes #11636 Closes #11635 Closes #11632 Closes #11630 Closes #12046 Closes #12438 Closes #12579
2015-08-15 18:00:55 +02:00
[[discovery]]
== Discovery Plugins
Align docs etc with new discovery setting names (#38492) In #38333 and #38350 we moved away from the `discovery.zen` settings namespace since these settings have an effect even though Zen Discovery itself is being phased out. This change aligns the documentation and the names of related classes and methods with the newly-introduced naming conventions.
2019-02-06 11:34:38 +00:00
Discovery plugins extend Elasticsearch by adding new seed hosts providers that
can be used to extend the {ref}/modules-discovery.html[cluster formation
module].
Docs: Prepare plugin and integration docs for 2.0 * Centralised plugin docs in docs/plugins/ * Moved integrations into same docs * Moved community clients into the clients section of the docs * Removed docs/community Closes #11734 Closes #11724 Closes #11636 Closes #11635 Closes #11632 Closes #11630 Closes #12046 Closes #12438 Closes #12579
2015-08-15 18:00:55 +02:00
[float]
==== Core discovery plugins
The core discovery plugins are:
[plugin] split cloud-aws in repository-s3 and discovery-ec2 Until now we had a cloud-aws plugin which is providing 2 disctinct features: * discovery on EC2 * snapshot/restore on S3 This commit splits the plugin by feature so people can use either one or the other or both features. Doc is updated accordingly.
2015-08-25 00:10:20 +02:00
<<discovery-ec2,EC2 discovery>>::
Docs: Prepare plugin and integration docs for 2.0 * Centralised plugin docs in docs/plugins/ * Moved integrations into same docs * Moved community clients into the clients section of the docs * Removed docs/community Closes #11734 Closes #11724 Closes #11636 Closes #11635 Closes #11632 Closes #11630 Closes #12046 Closes #12438 Closes #12579
2015-08-15 18:00:55 +02:00
[Zen2] Update documentation for Zen2 (#34714) This commit overhauls the documentation of discovery and cluster coordination, removing mention of the Zen Discovery module and replacing it with docs for the new cluster coordination mechanism introduced in 7.0. Relates #32006
2018-12-20 13:02:44 +00:00
The EC2 discovery plugin uses the https://github.com/aws/aws-sdk-java[AWS API]
Align docs etc with new discovery setting names (#38492) In #38333 and #38350 we moved away from the `discovery.zen` settings namespace since these settings have an effect even though Zen Discovery itself is being phased out. This change aligns the documentation and the names of related classes and methods with the newly-introduced naming conventions.
2019-02-06 11:34:38 +00:00
to identify the addresses of seed hosts.
Docs: Prepare plugin and integration docs for 2.0 * Centralised plugin docs in docs/plugins/ * Moved integrations into same docs * Moved community clients into the clients section of the docs * Removed docs/community Closes #11734 Closes #11724 Closes #11636 Closes #11635 Closes #11632 Closes #11630 Closes #12046 Closes #12438 Closes #12579
2015-08-15 18:00:55 +02:00
Fix documentation filenames
2016-06-30 15:26:54 +02:00
<<discovery-azure-classic,Azure Classic discovery>>::
Docs: Prepare plugin and integration docs for 2.0 * Centralised plugin docs in docs/plugins/ * Moved integrations into same docs * Moved community clients into the clients section of the docs * Removed docs/community Closes #11734 Closes #11724 Closes #11636 Closes #11635 Closes #11632 Closes #11630 Closes #12046 Closes #12438 Closes #12579
2015-08-15 18:00:55 +02:00
Align docs etc with new discovery setting names (#38492) In #38333 and #38350 we moved away from the `discovery.zen` settings namespace since these settings have an effect even though Zen Discovery itself is being phased out. This change aligns the documentation and the names of related classes and methods with the newly-introduced naming conventions.
2019-02-06 11:34:38 +00:00
The Azure Classic discovery plugin uses the Azure Classic API to identify the
addresses of seed hosts.
Docs: Prepare plugin and integration docs for 2.0 * Centralised plugin docs in docs/plugins/ * Moved integrations into same docs * Moved community clients into the clients section of the docs * Removed docs/community Closes #11734 Closes #11724 Closes #11636 Closes #11635 Closes #11632 Closes #11630 Closes #12046 Closes #12438 Closes #12579
2015-08-15 18:00:55 +02:00
Rename cloud-gce plugin to discovery-gce plugin Follow up azure and aws splits, we need to be consistent and rename `cloud-gce` to `discovery-gce`.
2015-09-26 11:53:21 +02:00
<<discovery-gce,GCE discovery>>::
Docs: Prepare plugin and integration docs for 2.0 * Centralised plugin docs in docs/plugins/ * Moved integrations into same docs * Moved community clients into the clients section of the docs * Removed docs/community Closes #11734 Closes #11724 Closes #11636 Closes #11635 Closes #11632 Closes #11630 Closes #12046 Closes #12438 Closes #12579
2015-08-15 18:00:55 +02:00
Align docs etc with new discovery setting names (#38492) In #38333 and #38350 we moved away from the `discovery.zen` settings namespace since these settings have an effect even though Zen Discovery itself is being phased out. This change aligns the documentation and the names of related classes and methods with the newly-introduced naming conventions.
2019-02-06 11:34:38 +00:00
The Google Compute Engine discovery plugin uses the GCE API to identify the
addresses of seed hosts.
Docs: Prepare plugin and integration docs for 2.0 * Centralised plugin docs in docs/plugins/ * Moved integrations into same docs * Moved community clients into the clients section of the docs * Removed docs/community Closes #11734 Closes #11724 Closes #11636 Closes #11635 Closes #11632 Closes #11630 Closes #12046 Closes #12438 Closes #12579
2015-08-15 18:00:55 +02:00
[float]
==== Community contributed discovery plugins
Align docs etc with new discovery setting names (#38492) In #38333 and #38350 we moved away from the `discovery.zen` settings namespace since these settings have an effect even though Zen Discovery itself is being phased out. This change aligns the documentation and the names of related classes and methods with the newly-introduced naming conventions.
2019-02-06 11:34:38 +00:00
The following discovery plugins have been contributed by our community:
Docs: Prepare plugin and integration docs for 2.0 * Centralised plugin docs in docs/plugins/ * Moved integrations into same docs * Moved community clients into the clients section of the docs * Removed docs/community Closes #11734 Closes #11724 Closes #11636 Closes #11635 Closes #11632 Closes #11630 Closes #12046 Closes #12438 Closes #12579
2015-08-15 18:00:55 +02:00
Add Kubernetes discovery community plugin
2015-11-25 12:54:29 +00:00
* https://github.com/fabric8io/elasticsearch-cloud-kubernetes[Kubernetes Discovery Plugin] (by Jimmi Dyson, http://fabric8.io[fabric8])
Docs: Prepare plugin and integration docs for 2.0 * Centralised plugin docs in docs/plugins/ * Moved integrations into same docs * Moved community clients into the clients section of the docs * Removed docs/community Closes #11734 Closes #11724 Closes #11636 Closes #11635 Closes #11632 Closes #11630 Closes #12046 Closes #12438 Closes #12579
2015-08-15 18:00:55 +02:00
[plugin] split cloud-aws in repository-s3 and discovery-ec2 Until now we had a cloud-aws plugin which is providing 2 disctinct features: * discovery on EC2 * snapshot/restore on S3 This commit splits the plugin by feature so people can use either one or the other or both features. Doc is updated accordingly.
2015-08-25 00:10:20 +02:00
include::discovery-ec2.asciidoc[]
Docs: Prepare plugin and integration docs for 2.0 * Centralised plugin docs in docs/plugins/ * Moved integrations into same docs * Moved community clients into the clients section of the docs * Removed docs/community Closes #11734 Closes #11724 Closes #11636 Closes #11635 Closes #11632 Closes #11630 Closes #12046 Closes #12438 Closes #12579
2015-08-15 18:00:55 +02:00
Deprecate discovery-azure and rename it to discovery-azure-classic As discussed at https://github.com/elastic/elasticsearch-cloud-azure/issues/91#issuecomment-229113595, we know that the current `discovery-azure` plugin only works with Azure Classic VMs / Services (which is somehow Legacy now). The proposal here is to rename `discovery-azure` to `discovery-azure-classic` in case some users are using it. And deprecate it for 5.0. Closes #19144.
2016-06-30 14:39:23 +02:00
include::discovery-azure-classic.asciidoc[]
Docs: Prepare plugin and integration docs for 2.0 * Centralised plugin docs in docs/plugins/ * Moved integrations into same docs * Moved community clients into the clients section of the docs * Removed docs/community Closes #11734 Closes #11724 Closes #11636 Closes #11635 Closes #11632 Closes #11630 Closes #12046 Closes #12438 Closes #12579
2015-08-15 18:00:55 +02:00
Rename cloud-gce plugin to discovery-gce plugin Follow up azure and aws splits, we need to be consistent and rename `cloud-gce` to `discovery-gce`.
2015-09-26 11:53:21 +02:00
include::discovery-gce.asciidoc[]
Reference in New Issue Copy Permalink