diff options
| author |   Denis Kasanic <d.kasanic@partner.samsung.com> | 2019-12-04 13:40:07 +0100 |
|---|---|---|
| committer | Denis Kasanic <d.kasanic@partner.samsung.com> | 2019-12-18 10:24:58 +0000 |
| commit | fd2a5066ec0a3f13fb52b6d0bb2fb84e52dc31a8 (patch) | |
| tree | d5332ab5e04cf097221b47541a4d99427a0feeb9 /docs/vFWCL-notes.rst | |
| parent | 610ddff2d54cece28af56cc7bbf01ed524ecce9c (diff) | |
Add robot config at onap install
Change onap network cidr to /16 due to robot hardcoded config.
Adding onap network id to configuration at installation part.
Adding optional connection to demo usecases network at deploy step
Update patch scripts for specify network and kubernetes namespace
Enable config_drive parameter at openstack instances deploying to get openstack metadata
Issue-ID: OOM-1996
Signed-off-by: Denis Kasanic <d.kasanic@partner.samsung.com>
Change-Id: I4403e8ca0f385060ac815372ffd91eda60026ddb
Diffstat (limited to 'docs/vFWCL-notes.rst')
| -rw-r--r-- | docs/vFWCL-notes.rst | 9 |
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. |