From ecffc2412cfa3ffdf4308133016132b53e5bf630 Mon Sep 17 00:00:00 2001 From: "Joshua M. Boniface" Date: Fri, 25 Oct 2024 02:35:07 -0400 Subject: [PATCH] Try more spaces --- docs/deployment/getting-started.md | 21 ++++++++++----------- 1 file changed, 10 insertions(+), 11 deletions(-) diff --git a/docs/deployment/getting-started.md b/docs/deployment/getting-started.md index 47d2562..75091c6 100644 --- a/docs/deployment/getting-started.md +++ b/docs/deployment/getting-started.md @@ -94,18 +94,17 @@ You will also need a switch to connect the nodes, capable of vLAN trunks passing 0. In your local repository, edit the `hosts` file and add a new cluster. How you do so is technically up to you, but for those without advanced Ansible experience, the following format is simplest: + # First cluster + [cluster1] + hv1.cluster1.mydomain.tld + hv2.cluster1.mydomain.tld + hv3.cluster1.mydomain.tld - # First cluster - [cluster1] - hv1.cluster1.mydomain.tld - hv2.cluster1.mydomain.tld - hv3.cluster1.mydomain.tld - - # Second cluster - [cluster2] - hv1.cluster2.mydomain.tld - hv2.cluster2.mydomain.tld - hv3.cluster2.mydomain.tld + # Second cluster + [cluster2] + hv1.cluster2.mydomain.tld + hv2.cluster2.mydomain.tld + hv3.cluster2.mydomain.tld ❕ **NOTE** The hostnames given here must be the actual reachable FQDNs of the hypervisor nodes in the "upstream" network; if they do not resolve in DNS, you can use the `ansible_host=` per-entry variable to set the IP address in the "upstream" network for each node.