diff options
Diffstat (limited to 'docs/usecases')
| -rw-r--r-- | docs/usecases/ConnectingVPC.rst | 4 | ||||
| -rw-r--r-- | docs/usecases/Routing.rst | 6 | ||||
| -rw-r--r-- | docs/usecases/acls.rst | 2 | ||||
| -rw-r--r-- | docs/usecases/automatingthedeployment.rst | 2 | ||||
| -rw-r--r-- | docs/usecases/contiv/BUG_REPORTS.md | 2 | ||||
| -rw-r--r-- | docs/usecases/contiv/K8s_Overview.md | 2 | ||||
| -rw-r--r-- | docs/usecases/contiv/MANUAL_INSTALL.md | 6 | ||||
| -rw-r--r-- | docs/usecases/contiv/MULTI_NIC_SETUP.md | 2 | ||||
| -rw-r--r-- | docs/usecases/contiv/VPP_PACKET_TRACING_K8S.md | 2 | ||||
| -rw-r--r-- | docs/usecases/simpleperf/iperf3.rst | 2 | ||||
| -rw-r--r-- | docs/usecases/simpleperf/trex2.rst | 4 | ||||
| -rw-r--r-- | docs/usecases/vmxnet3.rst | 2 | ||||
| -rw-r--r-- | docs/usecases/vppinazure.rst | 2 |
13 files changed, 19 insertions, 19 deletions
diff --git a/docs/usecases/ConnectingVPC.rst b/docs/usecases/ConnectingVPC.rst index 8ecb790def0..cc8c927b2cb 100644 --- a/docs/usecases/ConnectingVPC.rst +++ b/docs/usecases/ConnectingVPC.rst @@ -5,7 +5,7 @@ Interconnecting VPCs with Segment Routing & Performance Evaluation ____________________________________________________________________ -Before reading this part, you should have a minimum understading of AWS, especially on `VPC concepts <https://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html>`_. +Before reading this part, you should have a minimum understanding of AWS, especially on `VPC concepts <https://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html>`_. @@ -22,7 +22,7 @@ In our VPC we will have two instances: one, in which we will install VPP and the .. figure:: /_images/vpc_scheme.svg -Figure 2: Example of the resourses present inside our VPC +Figure 2: Example of the resources present inside our VPC Notice that the following example works with two VPCs, where in each of them there are a VM with VPP and a VM. Hence, you will have to execute the same commands also in the other VPC to make the connection between the two VPC possibile. diff --git a/docs/usecases/Routing.rst b/docs/usecases/Routing.rst index 0c5908fd57e..31929d31603 100644 --- a/docs/usecases/Routing.rst +++ b/docs/usecases/Routing.rst @@ -75,7 +75,7 @@ We see that the IP has been assigned, as well as our default gateway. Now exit this container and repeat this process with container *ctwo*, except with IP 172.16.2.2/24 and gateway 172.16.2.1. -After thats done for *both* containers, exit from the container if you're in one: +After that's done for *both* containers, exit from the container if you're in one: .. code-block:: console @@ -261,6 +261,6 @@ At long last you probably want to see some pings: rtt min/avg/max/mdev = 0.089/0.098/0.111/0.014 ms -Which should send/recieve three packets for each command. +Which should send/receive three packets for each command. -This is the end of this guide. Great work!
\ No newline at end of file +This is the end of this guide. Great work! diff --git a/docs/usecases/acls.rst b/docs/usecases/acls.rst index 36023571779..0350af2d969 100644 --- a/docs/usecases/acls.rst +++ b/docs/usecases/acls.rst @@ -482,7 +482,7 @@ Match an IPv6…. Links ~~~~~ -- `Overview of classifers <https://wiki.fd.io/view/VPP/SecurityGroups#Existing_functionality>`__ +- `Overview of classifiers <https://wiki.fd.io/view/VPP/SecurityGroups#Existing_functionality>`__ - `FD.io VPP Classifiers Overview <https://wiki.fd.io/view/VPP/Introduction_To_N-tuple_Classifiers>`__ - `FD.io VPP Classifiers CLI <https://docs.fd.io/vpp/19.04/clicmd_src_vnet_classify.html>`__ - `Sample Code from Andrew Yourt <http://stdio.be/vpp/t/aytest-bridge-tap-py.txt>`__ diff --git a/docs/usecases/automatingthedeployment.rst b/docs/usecases/automatingthedeployment.rst index 6772b18e4e5..25317e2d0a0 100644 --- a/docs/usecases/automatingthedeployment.rst +++ b/docs/usecases/automatingthedeployment.rst @@ -7,6 +7,6 @@ __________________________ -In order to make the VPP deployment easier inside AWS and Azure, we have created two different Terraform scripts, compatibles with both Public Cloud Provider. These scripts allow to automate the deployment of the resources. `Here you can find the scripts anf further informations <https://github.com/francescospinelli94/Automating-Deployment-VPP>`_. +In order to make the VPP deployment easier inside AWS and Azure, we have created two different Terraform scripts, compatibles with both Public Cloud Provider. These scripts allow to automate the deployment of the resources. `Here you can find the scripts anf further information <https://github.com/francescospinelli94/Automating-Deployment-VPP>`_. diff --git a/docs/usecases/contiv/BUG_REPORTS.md b/docs/usecases/contiv/BUG_REPORTS.md index 648e67f2422..5b9c3cf4875 100644 --- a/docs/usecases/contiv/BUG_REPORTS.md +++ b/docs/usecases/contiv/BUG_REPORTS.md @@ -283,7 +283,7 @@ Prerequisites: access to sudo. #### Setting up Prerequisites -To enable looging into a node without a password, copy your public key to the following +To enable logging into a node without a password, copy your public key to the following node: ``` ssh-copy-id <user-id>@<node-name-or-ip-address> diff --git a/docs/usecases/contiv/K8s_Overview.md b/docs/usecases/contiv/K8s_Overview.md index e3d8e1a0d44..ba3a8e12524 100644 --- a/docs/usecases/contiv/K8s_Overview.md +++ b/docs/usecases/contiv/K8s_Overview.md @@ -3,7 +3,7 @@ ## Overview -Kubernates is a container orchestration system that efficiently manages Docker containers. The Docker containers and container platforms provide many advantages over traditional virtualization. Container isolation is done on the kernel level, which eliminates the need for a guest virtual operating system, and therefore makes containers much more efficient, faster, and lightweight. The containers in Contiv/VPP are referred to as PODs. +Kubernetes is a container orchestration system that efficiently manages Docker containers. The Docker containers and container platforms provide many advantages over traditional virtualization. Container isolation is done on the kernel level, which eliminates the need for a guest virtual operating system, and therefore makes containers much more efficient, faster, and lightweight. The containers in Contiv/VPP are referred to as PODs. Contiv/VPP is a Kubernetes network plugin that uses [FD.io VPP](https://fd.io/) to provide network connectivity between PODs in a k8s cluster (k8s is an abbreviated reference for kubernates). diff --git a/docs/usecases/contiv/MANUAL_INSTALL.md b/docs/usecases/contiv/MANUAL_INSTALL.md index d91a83a610c..35506db0d16 100644 --- a/docs/usecases/contiv/MANUAL_INSTALL.md +++ b/docs/usecases/contiv/MANUAL_INSTALL.md @@ -1,9 +1,9 @@ # Manual Installation -This document describes how to clone the Contiv respository and then use [kubeadm][1] to manually install Kubernetes +This document describes how to clone the Contiv repository and then use [kubeadm][1] to manually install Kubernetes with Contiv-VPP networking on one or more bare metal or VM hosts. -## Clone the Contiv Respository -To clone the Contiv respository enter the following command: +## Clone the Contiv Repository +To clone the Contiv repository enter the following command: ``` git clone https://github.com/contiv/vpp/<repository-name> ``` diff --git a/docs/usecases/contiv/MULTI_NIC_SETUP.md b/docs/usecases/contiv/MULTI_NIC_SETUP.md index 5cbb031d290..cacbcbb464b 100644 --- a/docs/usecases/contiv/MULTI_NIC_SETUP.md +++ b/docs/usecases/contiv/MULTI_NIC_SETUP.md @@ -5,7 +5,7 @@ described [here](https://github.com/contiv/vpp/blob/master/docs/VPP_CONFIG.md#mu * For each interface owned by Linux, you need to provide individual configuration for each interface used by VPP in the Node Configuration - for thenode in the `contiv-vpp.yaml`. For example, if both `ens3` and + for the node in the `contiv-vpp.yaml`. For example, if both `ens3` and `ens4` are known to Linux, then put the following stanza into the node's NodeConfig: ``` diff --git a/docs/usecases/contiv/VPP_PACKET_TRACING_K8S.md b/docs/usecases/contiv/VPP_PACKET_TRACING_K8S.md index f7b6f4c19e8..740918197e2 100644 --- a/docs/usecases/contiv/VPP_PACKET_TRACING_K8S.md +++ b/docs/usecases/contiv/VPP_PACKET_TRACING_K8S.md @@ -113,7 +113,7 @@ wildcard-ip4-arp-publisher-pro event wait 0 0 `tapcli-rx` above is the node-level input queue for incoming packets into all the pods on the node. There is one `tapcli-rx` input queue for every node. -The following are the input and output queueus for each pod and the node: +The following are the input and output queues for each pod and the node: ``` tapcli-0-output diff --git a/docs/usecases/simpleperf/iperf3.rst b/docs/usecases/simpleperf/iperf3.rst index 1d159d0eef2..0b0de373bff 100644 --- a/docs/usecases/simpleperf/iperf3.rst +++ b/docs/usecases/simpleperf/iperf3.rst @@ -3,7 +3,7 @@ Introduction ============ -This tutorial shows how to use VPP use iperf3 and Trex to get some basic peformance +This tutorial shows how to use VPP use iperf3 and Trex to get some basic performance numbers from a few basic configurations. Four examples are shown. In the first two examples, the **iperf3** tool is used to generate traffic, and in the last two examples the Cisco's `TRex Realistic Traffic Generator <http://trex-tgn.cisco.com/>`_ is used. For diff --git a/docs/usecases/simpleperf/trex2.rst b/docs/usecases/simpleperf/trex2.rst index adb1d10c736..590bfd05629 100644 --- a/docs/usecases/simpleperf/trex2.rst +++ b/docs/usecases/simpleperf/trex2.rst @@ -56,7 +56,7 @@ In the other terminal start the TRex console. With this console we will execute # cd v2.46/ # ./trex -console - Using 'python' as Python interpeter + Using 'python' as Python interpreter Connecting to RPC server on localhost:4501 [SUCCESS] @@ -152,7 +152,7 @@ More statistics can be displayed on the TRex console using the **tui** command. trex>tui - Global Statistitcs + Global Statistics connection : localhost, Port 4501 total_tx_L2 : 2.45 Gb/sec version : STL @ v2.46 total_tx_L1 : 2.59 Gb/sec diff --git a/docs/usecases/vmxnet3.rst b/docs/usecases/vmxnet3.rst index f3ec8d4b6f6..37fdbc82b67 100644 --- a/docs/usecases/vmxnet3.rst +++ b/docs/usecases/vmxnet3.rst @@ -58,7 +58,7 @@ If you are concerned more with configuration not performance the vmxnet3 driver can be set to **interrupt** mode in VPP. This will save a great deal on battery usage. Do this with the following -VMware Workstatiom PRO 15 for Linux +VMware Workstation PRO 15 for Linux ----------------------------------- VMware Workstation does not have a menu option to change the default driver diff --git a/docs/usecases/vppinazure.rst b/docs/usecases/vppinazure.rst index b2839a124a3..f64e2a7e7d1 100644 --- a/docs/usecases/vppinazure.rst +++ b/docs/usecases/vppinazure.rst @@ -61,7 +61,7 @@ And we reboot the instance: .. code-block:: console - $ reboot istance + $ reboot instance After the reboot, we type these commands: |