From e3f6a3a060e597e215652922f4211a7f0a8e1b01 Mon Sep 17 00:00:00 2001 From: boruszak Date: Fri, 9 Sep 2022 13:30:04 -0500 Subject: [PATCH] /docs/install/index.mdx --- website/content/docs/install/bootstrapping.mdx | 8 ++------ website/content/docs/install/cloud-auto-join.mdx | 5 ++--- website/content/docs/install/glossary.mdx | 3 +-- website/content/docs/install/manual-bootstrap.mdx | 7 ++----- website/content/docs/install/performance.mdx | 6 ++---- website/content/docs/install/ports.mdx | 5 ++--- 6 files changed, 11 insertions(+), 23 deletions(-) diff --git a/website/content/docs/install/bootstrapping.mdx b/website/content/docs/install/bootstrapping.mdx index 849a3fc3c5..23d0d1aeec 100644 --- a/website/content/docs/install/bootstrapping.mdx +++ b/website/content/docs/install/bootstrapping.mdx @@ -1,12 +1,8 @@ --- layout: docs -page_title: Bootstrapping a Datacenter +page_title: Bootstrap a Datacenter description: >- - An agent can run in both client and server mode. Server nodes are responsible - for running the consensus protocol and storing the cluster state. Before a - Consul cluster can begin to service requests, a server node must be elected - leader. Thus, the first nodes that are started are generally the server nodes. - Bootstrapping is the process of joining these server nodes into a cluster. +Bootstrapping a datacenter is the initial deployment process in Consul that starts server agents and joins them together. Learn how to automatically or manually join servers in a cluster. --- # Bootstrapping a Datacenter diff --git a/website/content/docs/install/cloud-auto-join.mdx b/website/content/docs/install/cloud-auto-join.mdx index 3d6072f9b9..47d247d2a1 100644 --- a/website/content/docs/install/cloud-auto-join.mdx +++ b/website/content/docs/install/cloud-auto-join.mdx @@ -1,9 +1,8 @@ --- layout: docs -page_title: Cloud Auto-join +page_title: Auto-join a Cloud Provider description: >- - Consul supports automatically joining a Consul datacenter using cloud metadata - on various providers. +Configure servers to auto-join clusters on startup. Use the CLI or an agent configuration file to specify either an IP address or a cloud provider for the server to join. --- # Cloud Auto-join diff --git a/website/content/docs/install/glossary.mdx b/website/content/docs/install/glossary.mdx index 703761450a..56b444eefa 100644 --- a/website/content/docs/install/glossary.mdx +++ b/website/content/docs/install/glossary.mdx @@ -2,8 +2,7 @@ layout: docs page_title: Glossary description: >- - This page collects brief definitions of some of the technical terms used in - the documentation. +The glossary is a list of technical terms with a specific meaning in Consul. Use the glossary to understand Consul concepts and study for the certification exam. --- # Consul Vocabulary diff --git a/website/content/docs/install/manual-bootstrap.mdx b/website/content/docs/install/manual-bootstrap.mdx index bb72b9aec3..25093e0d92 100644 --- a/website/content/docs/install/manual-bootstrap.mdx +++ b/website/content/docs/install/manual-bootstrap.mdx @@ -1,11 +1,8 @@ --- layout: docs -page_title: Manual Bootstrapping +page_title: Manually Bootstrap a Datacenter description: >- - When deploying Consul to a datacenter for the first time, there is an initial - bootstrapping that must be done. As of Consul 0.4, an automatic bootstrapping - is available and is the recommended approach. However, older versions only - support a manual bootstrap that is documented here. +Manually bootstrap a datacenter to deploy your Consul servers and join them together for the first time. As of Consul v0.4, automatic bootstrapping is recommended instead. --- # Manually Bootstrapping a Datacenter diff --git a/website/content/docs/install/performance.mdx b/website/content/docs/install/performance.mdx index b3e560316a..64062967ec 100644 --- a/website/content/docs/install/performance.mdx +++ b/website/content/docs/install/performance.mdx @@ -1,10 +1,8 @@ --- layout: docs -page_title: Server Performance +page_title: Server Requirements description: >- - Consul requires different amounts of compute resources, depending on cluster - size and expected workload. This guide provides guidance on choosing compute - resources. +Consul servers require computing resources to communicate and process data quickly. Learn about Consul's minimum server requirements and recommendations for different workloads. --- # Server Performance diff --git a/website/content/docs/install/ports.mdx b/website/content/docs/install/ports.mdx index 0923935ba1..bdd48c2cea 100644 --- a/website/content/docs/install/ports.mdx +++ b/website/content/docs/install/ports.mdx @@ -1,9 +1,8 @@ --- layout: docs -page_title: Required Ports +page_title: Port Requirements description: >- - Before starting Consul it is important to have the necessary bind ports - accessible. +Consul requires bind ports for directing DNS, HTTP, gRPC, Serf, and proxy requests. Learn about these reserved ports and how Consul uses them for specific communication functions. --- # Required Ports