diff options
Diffstat (limited to 'VNFs/DPPD-PROX/helper-scripts/openstackrapid/README')
| -rw-r--r-- | VNFs/DPPD-PROX/helper-scripts/openstackrapid/README | 31 |
1 files changed, 25 insertions, 6 deletions
diff --git a/VNFs/DPPD-PROX/helper-scripts/openstackrapid/README b/VNFs/DPPD-PROX/helper-scripts/openstackrapid/README index 2dac5b69..cc940fc6 100644 --- a/VNFs/DPPD-PROX/helper-scripts/openstackrapid/README +++ b/VNFs/DPPD-PROX/helper-scripts/openstackrapid/README @@ -21,8 +21,9 @@ rapid is a set of files offering an easy way to do a sanity check of the dataplane performance of an OpenStack environment. Copy the files in a directory on a machine that can run the OpenStack CLI -commands and that can reach the OpenStack public network. Also create a qcow2 -image in the same directory with the following characteristics: +commands and that can reach the OpenStack public network. +One option is to create a qcow2 image in the same directory with the +following characteristics: * Name of the qcow2 file should be: rapidVM.qcow2 This default name can be overruled on the rapid command line (--image_file) * Should have DPDK and PROX installed. PROX should be in /root/prox/ directory @@ -31,8 +32,19 @@ image in the same directory with the following characteristics: * Compile prox with 'make crc=soft'. This is a workaround for some cases where the crc calculation offload is not working as expected. * Compile dpdk to support AESN-NI Multi Buffer Crypto Poll Mode Driver: http://dpdk.org/doc/guides/cryptodevs/aesni_mb.html -Source the openrc file of the OpenStack environment so that the OpenStack CLI -commands can be run: +Alternatively, you can create an image in OpenStack using Packer and then specify +the image to be used as a parameter to createrapid.py. First step is to upload an +existing CentOs cloud image from the internet into OpenStack. +Check out: https://cloud.centos.org/centos/7/images/ +You should now source the proper .rc file so Packer can connect to your OpenStack. +There are 2 files: centos.json and deploycentos.sh, allowing you to create +an image automatically. Run + # packer build centos.json +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 @@ -45,6 +57,10 @@ 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 +/etc/resolv.conf will contain DNS info from the "best" interface. Since we are +deploying VMs with multiple interface on different networks, this info might be +taken from the "wrong" network (e.g. the dataplane network). It is good to provide +also a working DNS on that network. Now you can run the runrapid.py file. Use help for more info on the usage: # ./runrapid.py --help @@ -88,8 +104,11 @@ 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 createrapid.py. Only the [Mx] sections are used as -input for runrapid.py. +achieved using creater 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 + [DEFAULT] admin_ip = none |