Improved image build & packet loss measurements

Reworked deploycentos1.sh and deploycentos2.sh which is installing
a PROX version that deals with non data plane packet counting for
improved packet loss measurements. Fixed some issues with the packer
scripts.

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

1 files changed, 12 insertions, 7 deletions

diff --git a/VNFs/DPPD-PROX/helper-scripts/openstackrapid/README b/VNFs/DPPD-PROX/helper-scripts/openstackrapid/README
index d58b4bf3..0dea6565 100644
--- a/VNFs/DPPD-PROX/helper-scripts/openstackrapid/README
+++ b/VNFs/DPPD-PROX/helper-scripts/openstackrapid/README
@@ -24,7 +24,7 @@ Copy the files in a directory on a machine that can run the OpenStack CLI
 commands and that can reach the OpenStack public network.
 
 You will need an image that has the PROX tool installed.
-A good way to do this is to use the packer tool to build an image for a target of your choice.
+The best way to do this is to use the packer tool to build an image for a target of your choice.
 You can also build this image manually by executing all the commands described in the deploycentos1.sh
 and deploycentos2.sh file.
 The default name of the qcow2 file should is rapidVM.qcow2
@@ -36,12 +36,19 @@ You should now source the proper .rc file so Packer can connect to your OpenStac
 There are 3 files: centos.json, deploycentos1.sh and deploycentos2.sh, allowing you to create
 an image automatically. Run
   # packer build centos.json
+Edit centos.json to reflect the settings of your environment: The following fields need to
+be the ID's of your system:
+  - "source_image": Needs to be the id of the Centos cloud image
+  - "flavor": Needs to be the ID of the flavor existing in your OpenStack environment that will be used
+    to start the VM in which we will install all tools
+  - "networks": ID of the network that will be used for the VM
+  - "use_floating_ip": true or false
+  - "floating_ip_pool": ID of the floating ip pool in case floating ip are being used
+  - "security_groups": ID of the security group being used
+
 Note that this procedure is not only installing the necessary tools to run PROX,
 but also does some system optimizations (tuned).
 
-Now that the image exists in OpenStack, source the openrc file of the OpenStack
-environment so that the OpenStack CLI commands can be run:
-  # source openrc
 Now you can run the createrapid.py file. Use help for more info on the usage:
   # ./createrapid.py --help
 
@@ -70,8 +77,6 @@ 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
   startup of the VMs.
-- The script also assumes some specific DPDK directory and tools which might
-  change over different DPDK release. This release has been tested with DPDK-17.02.
 - huge pages are allocated for DPDK on node 0 (hard-coded) in the VM.
 
 Note on using SRIOV ports:
@@ -100,7 +105,7 @@ 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
 different way (not using the createrapid.py). This can be useful in case you are
 not using OpenStack as a VIM or when using special configurations that cannot be
-achieved using creater needed for runrapid are:
+achieved using createrapid.py. Fields needed for runrapid are:
 * all info in the [Mx] sections
 * the key information in the [OpenStack] section
 * the total_number_of_vms information in the [rapid] section