Adding vdev support and vfio

Using vfio in stead of igb_uio. DPDK 2020.5 is NOT compiling the igb_uio
driver by default any more.
For the l3 mode, we are now using the new PROX vdev feature. This is
achieved by adding the vdev parameter in the port section of the PROX
config files. One of the advantages is that we can now ping a port
managed by PROX: the requests will be forwarded by PROX to the LINUX
stack, who will reply to the ping. A tap device is being created by PROX
to support this feature.
Installing old version of nasm since latest causes some issues.
If not pushgateway is being used, it should be commented out in the
config_file.
vfio is now loaded by specifying the module in /etc/modules-load.d
There is also an after_boot.sh script that will be run by
check_prox_system_setup.sh, which can be used for further configuration
of the instance after boot.
There is now also a file created /opt/rapid/system_ready_for_rapid by
the check_prox_system_setup.sh script. This file is created once all
configuration is done. The runrapid.py script will wait till this file
is created before executing any tests.

Change-Id: Ic5c41af82642066af42134c3323297f5a06f6f72
Signed-off-by: Luc Provoost <luc.provoost@intel.com>

1 files changed, 23 insertions, 3 deletions

diff --git a/VNFs/DPPD-PROX/helper-scripts/rapid/openstack-rapid.yaml b/VNFs/DPPD-PROX/helper-scripts/rapid/openstack-rapid.yaml
index 1c6fbee4..16df0874 100644
--- a/VNFs/DPPD-PROX/helper-scripts/rapid/openstack-rapid.yaml
+++ b/VNFs/DPPD-PROX/helper-scripts/rapid/openstack-rapid.yaml
@@ -1,7 +1,7 @@
 heat_template_version: 2015-10-15
 
 description: >
-  Template for deploying n PROX instances. Teh template allows for deploying
+  Template for deploying n PROX instances. The template allows for deploying
   multiple groups of PROX VMs. You can create a first group with certain
   flavors, availability groups, etc... Another group can be created with
   different characteristics.
@@ -50,7 +50,8 @@ resources:
           PROX_mgmt_net_id: {get_param: mgmt_net_name}
           PROX_data_net_id: {get_param: data_net_name}
           PROX_config: {get_resource: MyConfig}
-    depends_on: MyConfig
+    depends_on:
+      - MyConfig
   
   PROX2VMs:
     type: OS::Heat::ResourceGroup
@@ -69,7 +70,8 @@ resources:
           PROX_mgmt_net_id: {get_param: mgmt_net_name}
           PROX_data_net_id: {get_param: data_net_name}
           PROX_config: {get_resource: MyConfig}
-    depends_on: MyConfig
+    depends_on:
+      - MyConfig
   
   MyConfig:
     type: OS::Heat::CloudConfig
@@ -88,6 +90,24 @@ resources:
           list:  |
               rapid:rapid
           expire: False
+        write_files:
+        - path: /opt/rapid/after_boot_do_not_run.sh
+          # after_boot.sh is ran by check_prox_system_setup.sh, if it exists
+          # This can be used to fix some issues, like in the example below
+          # Remove this section or rename the file, if you do not want to run
+          # this after booting
+          content: |
+            OLDIFS="${IFS}"
+            IFS=$'\n'
+            list="$(ip route | grep via | grep -v 'dev eth0')"
+            # Delete all routes using gateway on other interfaces than eth0
+            for item in ${list}
+              do /bin/bash -c "sudo ip route del ${item}"
+            done
+            /bin/bash -c "sudo ip route add default via 10.6.6.1 dev eth0"
+            /bin/bash -c "echo nameserver 8.8.8.8 > /etc/resolv.conf"
+            IFS="${OLDIFS}"
+          permissions: '0777'
 
 outputs:
   number_of_servers: