aboutsummaryrefslogtreecommitdiffstats
path: root/docs/reference/vppvagrant
diff options
context:
space:
mode:
Diffstat (limited to 'docs/reference/vppvagrant')
-rw-r--r--docs/reference/vppvagrant/VagrantVMSetup.rst12
-rw-r--r--docs/reference/vppvagrant/boxSetup.rst8
-rw-r--r--docs/reference/vppvagrant/installingVboxVagrant.rst6
-rw-r--r--docs/reference/vppvagrant/settingENV.rst2
4 files changed, 14 insertions, 14 deletions
diff --git a/docs/reference/vppvagrant/VagrantVMSetup.rst b/docs/reference/vppvagrant/VagrantVMSetup.rst
index 769c6186170..f9f4304ed94 100644
--- a/docs/reference/vppvagrant/VagrantVMSetup.rst
+++ b/docs/reference/vppvagrant/VagrantVMSetup.rst
@@ -6,7 +6,7 @@ Accessing your VM
^^^^^^^^^^^^^^^^^
ssh into the newly created box:
-.. code-block:: console
+.. code-block:: shell
$ vagrant ssh <id>
@@ -28,7 +28,7 @@ Sample output looks like:
Become the root with:
-.. code-block:: console
+.. code-block:: shell
$ sudo bash
@@ -38,19 +38,19 @@ When you ssh into your Vagrant box you will be placed in the directory */home/va
For Ubuntu systems:
-.. code-block:: console
+.. code-block:: shell
# dpkg -i *.deb
For CentOS systems:
-.. code-block:: console
+.. code-block:: shell
# rpm -Uvh *.rpm
Since VPP is now installed, you can start running VPP with:
-.. code-block:: console
+.. code-block:: shell
- # service vpp start \ No newline at end of file
+ # service vpp start
diff --git a/docs/reference/vppvagrant/boxSetup.rst b/docs/reference/vppvagrant/boxSetup.rst
index d23033da856..374ba349458 100644
--- a/docs/reference/vppvagrant/boxSetup.rst
+++ b/docs/reference/vppvagrant/boxSetup.rst
@@ -82,7 +82,7 @@ __________
Once you're satisfied with your *Vagrantfile*, boot the box with:
-.. code-block:: console
+.. code-block:: shell
$ vagrant up
@@ -106,19 +106,19 @@ To confirm it is up, show the status and information of Vagrant boxes with:
To poweroff your VM, type:
- .. code-block:: console
+ .. code-block:: shell
$ vagrant halt <id>
To resume your VM, type:
- .. code-block:: console
+ .. code-block:: shell
$ vagrant resume <id>
To destroy your VM, type:
- .. code-block:: console
+ .. code-block:: shell
$ vagrant destroy <id>
diff --git a/docs/reference/vppvagrant/installingVboxVagrant.rst b/docs/reference/vppvagrant/installingVboxVagrant.rst
index 1bd4ba076d7..018ce6cfb53 100644
--- a/docs/reference/vppvagrant/installingVboxVagrant.rst
+++ b/docs/reference/vppvagrant/installingVboxVagrant.rst
@@ -15,7 +15,7 @@ If you're on CentOS, follow the `steps here <https://wiki.centos.org/HowTos/Virt
If you're on Ubuntu, perform:
-.. code-block:: console
+.. code-block:: shell
$ sudo apt-get install virtualbox
@@ -24,13 +24,13 @@ __________________
Here we are on a 64-bit version of CentOS, downloading and installing Vagrant 2.1.2:
-.. code-block:: console
+.. code-block:: shell
$ yum -y install https://releases.hashicorp.com/vagrant/2.1.2/vagrant_2.1.2_x86_64.rpm
This is a similar command, but on a 64-bit version of Debian:
-.. code-block:: console
+.. code-block:: shell
$ sudo apt-get install https://releases.hashicorp.com/vagrant/2.1.2/vagrant_2.1.2_x86_64.deb
diff --git a/docs/reference/vppvagrant/settingENV.rst b/docs/reference/vppvagrant/settingENV.rst
index 269b36bda84..8bd7847d36c 100644
--- a/docs/reference/vppvagrant/settingENV.rst
+++ b/docs/reference/vppvagrant/settingENV.rst
@@ -24,6 +24,6 @@ Adding your own ENV variables is easy. For example, if you wanted to setup proxi
Once you're finished with *env.sh* script, and you are in the directory containing *env.sh*, run the script to set the ENV variables with:
-.. code-block:: console
+.. code-block:: shell
$ source ./env.sh