aboutsummaryrefslogtreecommitdiffstats
path: root/bootstrap
diff options
context:
space:
mode:
authormrichomme <morgan.richomme@orange.com>2020-03-19 19:02:41 +0100
committermrichomme <morgan.richomme@orange.com>2020-03-31 14:20:36 +0200
commitefb859d2581a42ea0de4d56646e89848e722c59e (patch)
treee4bb88f7bc778d1e640637ac79d74ca9f66eb05d /bootstrap
parent22872ddddd3c4e3646a2d01d42b534fdea469b8d (diff)
fix integration doc warning
Issue-ID: INT-1490 Signed-off-by: mrichomme <morgan.richomme@orange.com> Change-Id: I9153da660ae469c0bd3ed51cfebd912b6e4b9bf2 Signed-off-by: mrichomme <morgan.richomme@orange.com>
Diffstat (limited to 'bootstrap')
-rw-r--r--bootstrap/codesearch/README.rst1
-rw-r--r--bootstrap/vagrant-minimal-onap/README.rst4
2 files changed, 5 insertions, 0 deletions
diff --git a/bootstrap/codesearch/README.rst b/bootstrap/codesearch/README.rst
index 78262b268..10e5b8c13 100644
--- a/bootstrap/codesearch/README.rst
+++ b/bootstrap/codesearch/README.rst
@@ -55,6 +55,7 @@ useful in case there are multiple providers available.
(`integration/bootstrap/codesearch`).
.. code-block:: sh
+
vagrant up --provider=libvirt
This will:
diff --git a/bootstrap/vagrant-minimal-onap/README.rst b/bootstrap/vagrant-minimal-onap/README.rst
index 1315a00e8..8a9850d4e 100644
--- a/bootstrap/vagrant-minimal-onap/README.rst
+++ b/bootstrap/vagrant-minimal-onap/README.rst
@@ -29,6 +29,7 @@ Quickstart
Following set of commands can be used to prepare a machine running Ubuntu 18.04 for this setup:
.. code-block:: sh
+
sudo sed -i'.bak' 's/^#.*deb-src/deb-src/' /etc/apt/sources.list
sudo apt-get update
sudo apt-get build-dep vagrant ruby-libvirt
@@ -113,6 +114,7 @@ useful in case there are multiple providers available.
(`integration/bootstrap/vagrant-minimal-onap`).
.. code-block:: sh
+
vagrant up --provider=libvirt
@@ -123,11 +125,13 @@ Once ready (bringing up machines might initially take some time), tools for clus
be available on Operator's machine. It can be accessed by executing:
.. code-block:: sh
+
vagrant ssh operator
Although appropriate context is set for `kubectl` on login, when interacting with the cluster the
`onap` namespace has to be explicitly specified. Example:
.. code-block:: sh
+
# Operator's machine shell
kubectl -nonap get pods