summaryrefslogtreecommitdiffstats
path: root/VNFs/DPPD-PROX/helper-scripts/openstackrapid/README
diff options
context:
space:
mode:
Diffstat (limited to 'VNFs/DPPD-PROX/helper-scripts/openstackrapid/README')
-rw-r--r--VNFs/DPPD-PROX/helper-scripts/openstackrapid/README24
1 files changed, 18 insertions, 6 deletions
diff --git a/VNFs/DPPD-PROX/helper-scripts/openstackrapid/README b/VNFs/DPPD-PROX/helper-scripts/openstackrapid/README
index c29532ac..3123a0e2 100644
--- a/VNFs/DPPD-PROX/helper-scripts/openstackrapid/README
+++ b/VNFs/DPPD-PROX/helper-scripts/openstackrapid/README
@@ -41,17 +41,19 @@ createrapid.py will use the OpenStack CLI to create the flavor, key-pair, networ
stack, ...
It will create a <STACK>.env file containing all info that will be used by runrapid.py
to actually run the tests. Logging can be found in the CREATE<STACK>.log file
+You can use floating IP addresses by specifying the floating IP network
+--floating_network NETWORK
+or directly connect throught the INTERNAL_NETWORK by using the following parameter:
+--floating_network NO
Now you can run the runrapid.py file. Use help for more info on the usage:
# ./runrapid.py --help
The script will connect to all VMs that have been instantiated and it will launch
-PROX in all VMs.
-This will be done through the floating IP assigned to the VMs. You need to make sure
-that floating IPs are working on your OpenStack deployment.
+PROX in all VMs. This will be done through the admin IP assigned to the VMs.
Once that is done it will connect to the PROX tcp socket and start sending
commands to run the actual test.
It will print test results on the screen while running.
-The actual test that is running is decribed in <TEST>.test.
+The actual test that is running is described in <TEST>.test.
Notes about prox_user_data.sh script:
- The script contains commands that will be executed using cloud-init at
@@ -61,8 +63,8 @@ Notes about prox_user_data.sh script:
- huge pages are allocated for DPDK on node 0 (hard-coded) in the VM.
Note on using SRIOV ports:
-Before running createrapid, it is best to already create the network, subnet and ports
-manually by entering the following commands (change the parameters to your needs):
+Before running createrapid, make sure the network, subnet and ports are already created
+This can be done as follows (change the parameters to your needs):
openstack network create --share --external --provider-network-type flat --provider-physical-network physnet2 fast-network
openstack subnet create --network fast-network --subnet-range 20.20.20.0/24 --gateway none fast-subnet
openstack port create --network fast-network --vnic-type direct --fixed-ip subnet=fast-subnet Port1
@@ -71,6 +73,16 @@ openstack port create --network fast-network --vnic-type direct --fixed-ip subne
Make sure to use the network and subnet in the createrapid parameters list. Port1, Port2 and Port3
are being used in the yaml files.
+Note when doing tests using the gateway functionality on OVS:
+When a GW VM is sending packets on behalf of another VM (e.g. the generator), we need to make sure the OVS
+will allow those packets to go through. Therefore you need to the IP address of the generator in the
+"allowed address pairs" of the GW VM.
+
+Note when doing tests using encryption on OVS:
+Your OVS configuration might block encrypted packets. To allow packets to go through,
+you can disable port_security. You can do this by using the following commands
+neutron port-update xxxxxx --no-security-groups
+neutron port-update xxxxxx --port_security_enabled=False
An example of the env file generated by createrapid.py can be found below.
Note that this file can be created manually in case the stack is created in a