parallelvirtualcluster
/
docs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Try backticks

This commit is contained in:
Joshua Boniface 2024-10-25 02:32:22 -04:00
parent 40647b785c
commit 0aaa28d5df
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/deployment/getting-started.md
View File

@ -94,6 +94,7 @@ 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: 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 # First cluster
[cluster1] [cluster1]
@ -106,7 +107,7 @@ You will also need a switch to connect the nodes, capable of vLAN trunks passing
hv1.cluster2.mydomain.tld hv1.cluster2.mydomain.tld
hv2.cluster2.mydomain.tld hv2.cluster2.mydomain.tld
hv3.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. ❕ **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.