AETHER-2011 (part1)
Add basic 1.5 release documentation framework
Update edge deployment docs
- Describe different topologies and add deployment diagrams
- Split out Pronto BOM and diagrams
- Make BESS diagram a SVG
Updates to Sphinx and modules, fixed linkcheck to have a timeout/retry
for faulty webservers.
Fix spelling and formatting issue across entire site, remove "Smart
quotes" that cause the spellchecker to throw errors. Add many more
dictionary entries. Make spelling fail the build. Fix all spelling and
grammar errors that triggered failures.
Add autosectionlabel, and manage duplicate section names where they
existed.
Updated readme on image/diagram embedding
Added docs on PoE power cycle with Aruba switches (Pronto)
Change-Id: I7f9f7afae13788f9fe29bfe2683a295ba7b8914e
diff --git a/edge_deployment/vpn_bootstrap.rst b/edge_deployment/vpn_bootstrap.rst
index 35af0fd..7c48504 100644
--- a/edge_deployment/vpn_bootstrap.rst
+++ b/edge_deployment/vpn_bootstrap.rst
@@ -8,7 +8,7 @@
This section guides you through setting up a VPN connection between Aether
Central in GCP and ACE.
We will be using GitOps based Aether CI/CD system for this and what you need to do is
-create a patch for the new edge in **aether-pod-configs**, where all edge infrastructure
+create a patch for the new edge in ``aether-pod-configs``, where all edge infrastructure
configuration is stored.
Here is a brief overview of each step. Note that some of the steps described here are not
@@ -26,8 +26,8 @@
**3. Generate Ansible and Terraform configs**
In this step, you'll add Ansible and Terraform configs necessary to install and
-configure VPN softwares at the edge and set up VPN gateway, router,
-and firewall on GCP.
+configure VPN software at the edge and set up VPN gateway, router, and firewall
+on GCP.
**4. Submit your changes**
Finally, submit your aether-pod-configs changes to run the deployment job added
@@ -57,7 +57,7 @@
$ cd $WORKDIR
$ git clone "ssh://[username]@gerrit.opencord.org:29418/aether-ci-management"
-Add the jobs for the new cluster at the end of the `cd-pipeline-terraform-ace` project job list.
+Add the jobs for the new cluster at the end of the ``cd-pipeline-terraform-ace`` project job list.
Make sure to add both pre-merge and post-merge jobs.
Note that the cluster name specified here will be used in the rest of the deployment procedure.
@@ -270,7 +270,7 @@
the routing table from the management server and trying to ping to one of the
central cluster VMs.
-Be sure there are two tunnel interfaces, `gcp_tunnel1` and `gcp_tunnel2`,
+Be sure there are two tunnel interfaces, ``gcp_tunnel1`` and ``gcp_tunnel2``,
and three additional routing entries via one of the tunnel interfaces.
.. code-block:: shell