Image is finalized with necessary README files

On Image Conversions

We received .ova compressed images and tested them on VirtualBox using internal network to see if MongoDB receives the data. Only change we introduced to the images is the name of the network interface (ens3 now). Then we converted vmdk images of VirtualBox to "qcow2" raw images via qemu-img convert (that increased images sizes to 3+ GB). Then using the same tool we converted the images to .img (raw) files (made them 10+ GB), and compressed them via qemu-img commands again (down to 1.5-2.0 GB). Raw images are shared in the dropbox folder below, which is the same folder that Jibo shared (Jeremy and Wendy are added in there):

We received .ova compressed images and tested them on VirtualBox using internal network to see if MongoDB receives the data. Only change we introduced to the images is the name of the network interface (ens3 now). Then we converted vmdk images of VirtualBox to "qcow2" raw images via qemu-img convert (that increased images sizes to 3+ GB). Then using the same tool we converted the images to .img (raw) files (made them 10+ GB), and compressed them via qemu-img convert commands again (down to 1.5-2.0 GB). Raw images are also shared in the dropbox folder below, which is the same folder that Jibo shared (Jeremy and Wendy are added in there):

https://www.dropbox.com/sh/wxulve1zsbp0q3n/AABhWGI_n3kj6B-kID2voyWWa?dl=0

On Deployment of ADEVS and QEMU

Please see http://web.ornl.gov/~nutarojj/adevs/ on how to install ADEVS and QEMU, and patch QEMU. 

It is already deployed in this image but if you would like to see, go to:

http://web.ornl.gov/~nutarojj/adevs/ on how to install ADEVS and QEMU, and patch QEMU. 

Please see README files in the folders for the test-case deployments. 

Change the Makefile pointing to your ADEVS path. Please also make sure that qemu binaries are in your environment PATH. 

The following steps are all done in this image. The process is:

Change the Makefile pointing to the ADEVS path. Please also make sure that qemu binaries are in your environment PATH. 

To build and run the test case 1:

For example  enter ./a.out 250000000 0.0 /home/ozi/documents/images/ to run the test case with 3G cellular (minimum of 2Gbit/second) network (which is 250000000 bytes/second) and 0 percent data loss rate. The path (3rd argument) should point to the images folder you downloaded from Dropbox. You can also introduce different loss rates.

When images are up and running, assign their ip addresses via sudo ifconfig ens3 10.0.2.x. We tested historian as 2, forwarder as 3.  

We tested historian as 10.0.2.2, forwarder as 10.0.2.3. Their ips are assigned in .profile files of images that is why password is prompted twice on login.   

NOTE: MongoDB in the Historian will receive all the network packets and log them. You can delete all the data beforehand and have a clean start. Make sure that you close the historian properly (sudo poweroff) so that image will keep all the data. There is no time limit in ADEVS, it will simulate them forever unless you close the images. After images are closed, you can start the historian seperately and analyze the MongoDB. If you prefer to work with VirtualBox again during the analysis you can convert .img file to .vdi via VBoxManage commands.   

NOTE: MongoDB in the Historian will receive all the network packets and log them. You can delete all the data beforehand and have a clean start or use HistorianRaw.img in /home/adevs/Documents/images and copy it as Historian.img. Make sure that you close the historian properly (sudo poweroff) so that image will keep all the data. There is no time limit in ADEVS, it will simulate them forever unless you close the images. After images are closed, you can start the historian seperately and analyze the MongoDB.

Change the Makefile pointing to your ADEVS path. Please also make sure that qemu binaries are linked in your environment (PATH). 

The following changes are done in this image.

Change the Makefile pointing to the ADEVS path. Please also make sure that qemu binaries are linked in your environment (PATH). 

To build and run the test case 2:

For example  enter ./a.out 2500000000 0.0 1000000000 0.0 /home/ozi/documents/images/ to run the test case with 3G cellular (minimum of 2Gbit/second) network (which is 2500000000 bytes/second) and 0 percent data loss rate from the first forwarder, and with 1GB (1000000000 byte/second) and 0 percent loss rate from the second forwarder. The path (5th argument) should point to the images folder you downloaded from Dropbox.

When images are up and running, log in, and assign their ip addresses via sudo ifconfig ens3 10.0.2.x. We tested historian as 2, forwarder-1 as 3, and forwarder-2 as 4.  

We tested historian as 10.0.2.2, forwarder-1 as 10.0.2.3, and forwarder-2 as 10.0.2.4.  Their ips are assigned in .profile files of images that is why password is prompted twice on login.   

NOTE: MongoDB in the Historian will receive all the network packets and log them. You can delete all the data beforehand in the MongoDB and have a clean start. Make sure that you close the historian properly (sudo poweroff) so that image will keep all the data. There is no time limit in ADEVS, it will simulate them forever unless you close the images. After images are closed, you can start the historian seperately and analyze the MongoDB. If you prefer to work with VirtualBox again during the analysis you can convert .img file to .vdi via VBoxManage commands.     

NOTE: MongoDB in the Historian will receive all the network packets and log them. You can delete all the data beforehand in the MongoDB and have a clean start or copy HistorianRaw.img as Historian.img in the /home/adevs/images folder. Make sure that you close the historian properly (sudo poweroff) so that image will keep all the data. There is no time limit in ADEVS, it will simulate them forever unless you close the images. After images are closed, you can start the historian seperately and analyze the MongoDB.