[DOCS] Removed X-Pack installation info (elastic/x-pack-elasticsearch#4299)

Original commit: elastic/x-pack-elasticsearch@5af83b7531
This commit is contained in:
Lisa Cawley 2018-04-04 11:59:31 -07:00 committed by GitHub
parent aa5ee1ade9
commit 3e4ceec0c2
5 changed files with 19 additions and 20 deletions

View File

@ -3,8 +3,8 @@
If you want to use {xpackml} features, there must be at least one {ml} node in
your cluster and all master-eligible nodes must have {ml} enabled. By default,
when you install {xpack}, all nodes are {ml} nodes. For more information about
these settings, see <<xpack-settings>>.
all nodes are {ml} nodes. For more information about these settings, see
<<xpack-settings>>.
To use the {xpackml} features to analyze your data, you must create a job and
send your data to that job.

View File

@ -31,10 +31,7 @@ components of the Elastic Stack:
* {es} {version}, which stores the data and the analysis results
* {xpack} {version}, which includes the {ml} features for both {es} and {kib}
* {kib} {version}, which provides a helpful user interface for creating and
viewing jobs +
//ll {ml} features are available to use as an API, however this tutorial
//will focus on using the {ml} tab in the {kib} UI.
viewing jobs
See the https://www.elastic.co/support/matrix[Elastic Support Matrix] for
information about supported operating systems.
@ -47,13 +44,12 @@ single VM or even on your laptop (requires 64-bit OS).
As you add more data and your traffic grows,
you'll want to replace the single {es} instance with a cluster.
When you install {xpack} into {es} and {kib}, the {ml} features are
enabled by default. If you have multiple nodes in your cluster, you can
optionally dedicate nodes to specific purposes. If you want to control which
nodes are _machine learning nodes_ or limit which nodes run resource-intensive
When you install {es} and {kib}, the {ml} features are enabled by default. If
you have multiple nodes in your cluster, you can optionally dedicate nodes to
specific purposes. If you want to control which nodes are
_machine learning nodes_ or limit which nodes run resource-intensive
activity related to jobs, see <<xpack-settings>>.
[float]
[[ml-gs-users]]
==== Users, Roles, and Privileges

View File

@ -5,7 +5,7 @@
<titleabbrev>SQL Access Settings</titleabbrev>
++++
SQL Access is enabled by default when you install {xpack}. You can configure
SQL Access is enabled by default. You can configure
these SQL Access settings in the `elasticsearch.yml` file.
[float]
@ -13,5 +13,3 @@ these SQL Access settings in the `elasticsearch.yml` file.
==== General SQL Access Settings
`xpack.sql.enabled`::
Set to `false` to disable SQL Access on the node.

View File

@ -5,9 +5,15 @@
[partintro]
--
{xpack} is an Elastic Stack extension that bundles security, alerting,
monitoring, reporting, machine learning, and graph capabilities into one
easy-to-install package. To access this functionality, you must
<<installing-xpack-es,install {xpack} in {es}>>.
monitoring, reporting, machine learning, and graph capabilities.
* <<installing-xpack-es>>
* <<configuring-monitoring>>
* <<configuring-security>>
* <<setup-xpack-client>>
* <<settings-xpack>>
* <<bootstrap-checks-xpack>>
--
include::installing-xes.asciidoc[]

View File

@ -1,9 +1,8 @@
[[sql-getting-started]]
== Getting Started with SQL
To start using Elasticsearch SQL, first
<<installing-xpack-es, install X-Pack in Elasticsearch>>. Then create
in index with some data to experiment with:
To start using Elasticsearch SQL, create
an index with some data to experiment with:
[source,js]
--------------------------------------------------