summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorBartek Grzybowski <b.grzybowski@partner.samsung.com>2020-01-20 10:40:26 +0000
committerGerrit Code Review <gerrit@onap.org>2020-01-20 10:40:26 +0000
commit694656b0fd93183b99a1065dd9dafaf367e14552 (patch)
tree92daf8dc584aca8f70afc791c9c512548e559ac3 /docs
parent23ba267911f1b9b7120ea45f9f40f27ed144ade8 (diff)
parentfd2a5066ec0a3f13fb52b6d0bb2fb84e52dc31a8 (diff)
Merge "Add robot config at onap install"
Diffstat (limited to 'docs')
-rw-r--r--docs/vFWCL-notes.rst9
1 files changed, 5 insertions, 4 deletions
diff --git a/docs/vFWCL-notes.rst b/docs/vFWCL-notes.rst
index 2d6fd6fb..d8c76252 100644
--- a/docs/vFWCL-notes.rst
+++ b/docs/vFWCL-notes.rst
@@ -148,9 +148,10 @@ for this reason we are patching *base_vfw.yaml* for all vFW VMs with following c
# nasty hack to bypass cloud-init issues
sed -i '1i nameserver 8.8.8.8' /etc/resolv.conf
- iface_correct=`ip a | grep 10.8.8 | awk {'print $7'}`
- route add default gw 10.8.8.1 ${iface_correct}
+ iface_correct=`ip a | grep <network_prefix> | awk {'print $7'}`
+ route add default gw <network_prefix>.1 ${iface_correct}
+Network prefix variable is in our case "10.8.8".
Lets treat it as an example of how these two problems can be fixed. Feel free to adjust private/public key and skip cloud-init problem if you don't have it.
Our helping script with above setting is fixing both issues (a) and (b) for us.
@@ -158,7 +159,7 @@ Our helping script with above setting is fixing both issues (a) and (b) for us.
::
# copy offline-installer repo into infra node and run following script from patches folder
- ./update_robot.sh
+ ./update_robot.sh <namespace> <network_prefix>
**drools**
@@ -170,7 +171,7 @@ One can fix it by running following script.
::
# copy offline-installer repo into infra node and run following script from patches folder
- ./update_policy.sh
+ ./update_policy.sh <namespace>
.. note:: This script is also restarting policy, there is some small chance that drools will be marked as sick during interval its being restarted and redeployed. If it happens, just try again.