Academia.eduAcademia.edu

Figure 1 – uploaded by Pericherla S Suryateja

See full PDFdownloadDownload figure
Table 1. Comparison of existing cases in literature.

Table 1 Comparison of existing cases in literature.

Related Figures (73)

The rest of the paper is organized as follows. Section 2 presents the related work involving OpenStack. Section 3 describes the experimental design, the hardware configuration and operating system choice. Section 4 presents the results obtained from observation and discuss those results. Section 5 concludes the paper. Figure 1. OpenStack, Eucalyptus, OpenNebula, CloudStack and Xen from Google Trends.
The rest of the paper is organized as follows. Section 2 presents the related work involving OpenStack. Section 3 describes the experimental design, the hardware configuration and operating system choice. Section 4 presents the results obtained from observation and discuss those results. Section 5 concludes the paper. Figure 1. OpenStack, Eucalyptus, OpenNebula, CloudStack and Xen from Google Trends.
Sefraoui et al. (2012) [2] provides a comparative study of cloud platforms like Eucalyptus, OpenNebula, and OpenStack. They aim to signify the importance of open source solutions over role of OpenStack in establishing private clouds. Nasim and Kassler (2014) infrastructure on the performance of Open-Stack by conducting experiments commercial solutions. They stress on the 3] demonstrated the effect of underlying on two separate test beds. They deployed OpenStack on virtual environment and also on dedicated hardware. From the experimental results, they conclude that performance of OpenStack on dedicated hardware is far greater than performance on virtual infrastructure. They measured the performance of CPU, data transfer rate and bandwidth in the OpenStack installations in the two test beds. Gebreyohannes (2014) [4] studied the performance of OpenStack Neutron, Using the IPERF bench-marking tool, the internal network performance o the net-work component in OpenStack. f OpenStack was analyzed based on the parameters like packet loss, packet delay and throughput. From the experiments conducted, author concluded that OpenStack Neutron was scalable and it offers performance with no network b andwidth bottleneck.
Sefraoui et al. (2012) [2] provides a comparative study of cloud platforms like Eucalyptus, OpenNebula, and OpenStack. They aim to signify the importance of open source solutions over role of OpenStack in establishing private clouds. Nasim and Kassler (2014) infrastructure on the performance of Open-Stack by conducting experiments commercial solutions. They stress on the 3] demonstrated the effect of underlying on two separate test beds. They deployed OpenStack on virtual environment and also on dedicated hardware. From the experimental results, they conclude that performance of OpenStack on dedicated hardware is far greater than performance on virtual infrastructure. They measured the performance of CPU, data transfer rate and bandwidth in the OpenStack installations in the two test beds. Gebreyohannes (2014) [4] studied the performance of OpenStack Neutron, Using the IPERF bench-marking tool, the internal network performance o the net-work component in OpenStack. f OpenStack was analyzed based on the parameters like packet loss, packet delay and throughput. From the experiments conducted, author concluded that OpenStack Neutron was scalable and it offers performance with no network b andwidth bottleneck.
Table 2. Hardware configuration.
Table 2. Hardware configuration.
Table 3. Memory utilization in scenario 1.
Table 3. Memory utilization in scenario 1.
Resource utilization is measured across a VM and a standalone machine with same underlying hardware. Resources monitored are CPU, memory, disk I/O, network, and I/O requests. CPU utilization, disk I/O, network, and I/O requests are monitored using dstat command (Linux) and memory usage is retrieved using free command (Linux). The operating systems used are Ubuntu Server 16.04 as shown in Figure 4a. and Ubuntu Desktop 16.04 as shown in Figure 4b. The VM is also created on the standalone machine with the host operating system as Ubuntu Desktop 16.04 and guest operating system as Ubuntu Server 16.04 as shown in Figure 4c. The configuration of VM created in this scenario is similar to that of the VM created in scenario 1. VM was created using VirtualBox. Hardware configuration details are same as mentioned for standalone machine in scenario |.
Resource utilization is measured across a VM and a standalone machine with same underlying hardware. Resources monitored are CPU, memory, disk I/O, network, and I/O requests. CPU utilization, disk I/O, network, and I/O requests are monitored using dstat command (Linux) and memory usage is retrieved using free command (Linux). The operating systems used are Ubuntu Server 16.04 as shown in Figure 4a. and Ubuntu Desktop 16.04 as shown in Figure 4b. The VM is also created on the standalone machine with the host operating system as Ubuntu Desktop 16.04 and guest operating system as Ubuntu Server 16.04 as shown in Figure 4c. The configuration of VM created in this scenario is similar to that of the VM created in scenario 1. VM was created using VirtualBox. Hardware configuration details are same as mentioned for standalone machine in scenario |.
4- Results and Discussion
4- Results and Discussion
Figure 5. CPU utilization in VM before OpenStack installation. The CPU utilization in the VM before installing OpenStack is presented in Figure 5 and the CPU utilization in the VM after installing OpenStack is presented in Figure 6. On x-axis, we can see number of frames and y-axis represents percentage of CPU utilized. The CPU utilization in the standalone machine before installing OpenStack is presented in Figure 7 and the CPU utilization in the standalone machine after installing OpenStack is presented in Figure 8. On x- axis, we can see number of frames and y-axis represents percentage of CPU utilized.
Figure 5. CPU utilization in VM before OpenStack installation. The CPU utilization in the VM before installing OpenStack is presented in Figure 5 and the CPU utilization in the VM after installing OpenStack is presented in Figure 6. On x-axis, we can see number of frames and y-axis represents percentage of CPU utilized. The CPU utilization in the standalone machine before installing OpenStack is presented in Figure 7 and the CPU utilization in the standalone machine after installing OpenStack is presented in Figure 8. On x- axis, we can see number of frames and y-axis represents percentage of CPU utilized.
Figure 6. CPU utilization in VM after OpenStack installation.
Figure 6. CPU utilization in VM after OpenStack installation.
Figure 7. CPU utilization in standalone machine before OpenStack installation.
Figure 7. CPU utilization in standalone machine before OpenStack installation.
A combined plot of CPU utilization in VM before and after installing OpenStack is presented in Figure 9 and a combined plot of CPU utilization in standalone machine before and after OpenStack installation is presented in Figure 10. On x-axis, we can see number of frames and y-axis represents percentage of CPU utilized. A combined plot of CPU utilization in VM and the standalone machine before installing OpenStack is given in Figure 11 and a combined plot of CPU utilization in VM and the standalone machine after installing OpenStack is given in Figure 12. On x-axis, we can see number of frames and y-axis represents percentage of CPU utilized.
A combined plot of CPU utilization in VM before and after installing OpenStack is presented in Figure 9 and a combined plot of CPU utilization in standalone machine before and after OpenStack installation is presented in Figure 10. On x-axis, we can see number of frames and y-axis represents percentage of CPU utilized. A combined plot of CPU utilization in VM and the standalone machine before installing OpenStack is given in Figure 11 and a combined plot of CPU utilization in VM and the standalone machine after installing OpenStack is given in Figure 12. On x-axis, we can see number of frames and y-axis represents percentage of CPU utilized.
Figure 9. CPU utilization in VM before and after OpenStack installation.
Figure 9. CPU utilization in VM before and after OpenStack installation.
Table 4. Memory utilization in scenario 2. The CPU utilization in standalone machine with Ubuntu Server OS before installing OpenStack (S2.1) is presented in Figure 13. On x-axis, we can see number of frames and y-axis represents percentage of CPU utilized. The disk reads and writes before installing OpenStack are given in Figure 14a and Figure 14b. On x-axis, number of frames are represented and y-axis represents data transferred in bytes. The network usage in terms of bytes received and sent before installing OpenStack are presented in Figure 15a and Figure 15b. On x-axis, number of frames are being represented and y-axis represents data transferred in bytes. The number of I/O requests i.e., read requests and write requests before installing OpenStack are given in Figure 16a and Figure 16b.
Table 4. Memory utilization in scenario 2. The CPU utilization in standalone machine with Ubuntu Server OS before installing OpenStack (S2.1) is presented in Figure 13. On x-axis, we can see number of frames and y-axis represents percentage of CPU utilized. The disk reads and writes before installing OpenStack are given in Figure 14a and Figure 14b. On x-axis, number of frames are represented and y-axis represents data transferred in bytes. The network usage in terms of bytes received and sent before installing OpenStack are presented in Figure 15a and Figure 15b. On x-axis, number of frames are being represented and y-axis represents data transferred in bytes. The number of I/O requests i.e., read requests and write requests before installing OpenStack are given in Figure 16a and Figure 16b.
Figure 11. CPU utilization in VM and standalone machine before installing OpenStack.
Figure 11. CPU utilization in VM and standalone machine before installing OpenStack.
Figure 12. CPU utilization in VM and standalone machine after installing OpenStack.
Figure 12. CPU utilization in VM and standalone machine after installing OpenStack.
Figure 13. CPU utilization in 82.1.
Figure 13. CPU utilization in 82.1.
Figure 14b. Disk writes in 82.1.
Figure 14b. Disk writes in 82.1.
Figure 14a. Disk reads in S2.1.
Figure 14a. Disk reads in S2.1.
Figure 15a. Network bytes received in 82.1.
Figure 15a. Network bytes received in 82.1.
Figure 16a. I/O read requests S2.1.
Figure 16a. I/O read requests S2.1.
The CPU utilization in standalone machine with Ubuntu Server OS after installing OpenStack (S2.2) is presented in Figure 17. On x-axis, we can see number of frames and y-axis represents percentage of CPU utilized. The disk reads and writes after installing OpenStack are given in Figure 18a and Figure 18b. On x-axis, number of frames are represented and y-axis represents data transferred in bytes. The network usage in terms of bytes received and sent after installing OpenStack are presented in Figure 19a and Figure 19b. On x-axis, number of frames are being represented and y-axis represents data transferred in bytes. The number of I/O requests i.e., read requests and write requests after installing OpenStack are given in Figure 20a and Figure 20b.
The CPU utilization in standalone machine with Ubuntu Server OS after installing OpenStack (S2.2) is presented in Figure 17. On x-axis, we can see number of frames and y-axis represents percentage of CPU utilized. The disk reads and writes after installing OpenStack are given in Figure 18a and Figure 18b. On x-axis, number of frames are represented and y-axis represents data transferred in bytes. The network usage in terms of bytes received and sent after installing OpenStack are presented in Figure 19a and Figure 19b. On x-axis, number of frames are being represented and y-axis represents data transferred in bytes. The number of I/O requests i.e., read requests and write requests after installing OpenStack are given in Figure 20a and Figure 20b.
Figure 18a. Disk reads in S2.2.
Figure 18a. Disk reads in S2.2.
Figure 17. CPU utilization in S2.2.
Figure 17. CPU utilization in S2.2.
Figure 18b. Disk writes in $2.2.
Figure 18b. Disk writes in $2.2.
Figure 19a. Network bytes received in S2.2.
Figure 19a. Network bytes received in S2.2.
Figure 19b. Network bytes sent in S2.2.
Figure 19b. Network bytes sent in S2.2.
Figure 21. CPU utilization in 82.3.
Figure 21. CPU utilization in 82.3.
The CPU utilization in standalone machine with Ubuntu Desktop OS before installing OpenStack (S2.3) is presented in Figure 21. On x-axis, we can see number of frames and y-axis represents percentage of CPU utilized. The disk reads and writes before installing OpenStack are given in Figure 22a and Figure 22b. On x-axis, number of frames are represented and y-axis represents data transferred in bytes. The network usage in terms of bytes received and sent before installing Open-Stack are presented in Figure 23a and Figure 23b. On x-axis, number of frames are being represented and y-axis represents data transferred in bytes. The number of I/O requests i.e., read requests and write requests before installing OpenStack are given in Figure 24a and Figure 24b.
The CPU utilization in standalone machine with Ubuntu Desktop OS before installing OpenStack (S2.3) is presented in Figure 21. On x-axis, we can see number of frames and y-axis represents percentage of CPU utilized. The disk reads and writes before installing OpenStack are given in Figure 22a and Figure 22b. On x-axis, number of frames are represented and y-axis represents data transferred in bytes. The network usage in terms of bytes received and sent before installing Open-Stack are presented in Figure 23a and Figure 23b. On x-axis, number of frames are being represented and y-axis represents data transferred in bytes. The number of I/O requests i.e., read requests and write requests before installing OpenStack are given in Figure 24a and Figure 24b.
Figure 22b. Disk writes in S2.3. Figure 23a. Network bytes received in 82.3.
Figure 22b. Disk writes in S2.3. Figure 23a. Network bytes received in 82.3.
Figure 24b. I/O write requests S2.3. Figure 23b. Network bytes sent in 82.3.
Figure 24b. I/O write requests S2.3. Figure 23b. Network bytes sent in 82.3.
The CPU utilization in standalone machine with Ubuntu Desktop OS after installing OpenStack (S2.4) is presentec in Figure 25. On x-axis, we can see number of frames and y-axis represents percentage of CPU utilized. The disk read. and writes after installing OpenStack are given in Figure 26a and Figure 26b. On x-axis, number of frames ar represented and y-axis represents data transferred in bytes. The network usage in terms of bytes received and sent afte: installing OpenStack are presented in Figure 27a and Figure 27b. On x-axis, number of frames are being representec and y-axis represents data transferred in bytes. The number of I/O requests i.e., read requests and write requests afte: installing OpenStack are given in Figure 28a and Figure 28b. Figure 26b. Disk writes in $2.4.
The CPU utilization in standalone machine with Ubuntu Desktop OS after installing OpenStack (S2.4) is presentec in Figure 25. On x-axis, we can see number of frames and y-axis represents percentage of CPU utilized. The disk read. and writes after installing OpenStack are given in Figure 26a and Figure 26b. On x-axis, number of frames ar represented and y-axis represents data transferred in bytes. The network usage in terms of bytes received and sent afte: installing OpenStack are presented in Figure 27a and Figure 27b. On x-axis, number of frames are being representec and y-axis represents data transferred in bytes. The number of I/O requests i.e., read requests and write requests afte: installing OpenStack are given in Figure 28a and Figure 28b. Figure 26b. Disk writes in $2.4.
Figure 27b. Network bytes sent in 82.4.
Figure 27b. Network bytes sent in 82.4.
Figure 27a. Network bytes received in 82.4.
Figure 27a. Network bytes received in 82.4.
Figure 28a. I/O read requests S2.4.
Figure 28a. I/O read requests S2.4.
The CPU utilization in VM with Ubuntu Desktop host operating system before installing OpenStack (S2.5) is presented in Figure 29. On x-axis, we can see number of frames and y-axis represents percentage of CPU utilized. The disk reads and writes before installing OpenStack are given in Figures 30a and 30b. On x-axis, number of frames are represented and y-axis represents data transferred in bytes. The network usage in terms of bytes received and sent before installing OpenStack are presented in Figures 31a and 31b. On x-axis, number of frames are being represented and y-axis represents data transferred in bytes. The number of I/O requests i.e., read requests and write requests before installing Open-Stack are given in Figures 32a and 32b.
The CPU utilization in VM with Ubuntu Desktop host operating system before installing OpenStack (S2.5) is presented in Figure 29. On x-axis, we can see number of frames and y-axis represents percentage of CPU utilized. The disk reads and writes before installing OpenStack are given in Figures 30a and 30b. On x-axis, number of frames are represented and y-axis represents data transferred in bytes. The network usage in terms of bytes received and sent before installing OpenStack are presented in Figures 31a and 31b. On x-axis, number of frames are being represented and y-axis represents data transferred in bytes. The number of I/O requests i.e., read requests and write requests before installing Open-Stack are given in Figures 32a and 32b.
Figure 30a. Disk reads in 82.5.
Figure 30a. Disk reads in 82.5.
Figure 30b. Disk writes in $2.5. Figure 31a. Network bytes received in 82.5.
Figure 30b. Disk writes in $2.5. Figure 31a. Network bytes received in 82.5.
Figure 31b. Network bytes sent in S2.5.
Figure 31b. Network bytes sent in S2.5.
The CPU utilization in VM with Ubuntu Desktop host operating system after installing OpenStack (S2.6) is presented in Figure 33. On x-axis, we can see number of frames and y-axis represents percentage of CPU utilized. The disk reads and writes after installing OpenStack are given in Figures 34a and 34b. On x-axis, number of frames are represented and y-axis represents data transferred in bytes. The network usage in terms of bytes received and sent after installing OpenStack are presented in Figures 35a and 35b. On x-axis, number of frames are being represented and y- axis rep-resents data transferred in bytes. The number of I/O requests i.e., read requests and write requests after installing OpenStack are given in Figures 36a and 36b.
The CPU utilization in VM with Ubuntu Desktop host operating system after installing OpenStack (S2.6) is presented in Figure 33. On x-axis, we can see number of frames and y-axis represents percentage of CPU utilized. The disk reads and writes after installing OpenStack are given in Figures 34a and 34b. On x-axis, number of frames are represented and y-axis represents data transferred in bytes. The network usage in terms of bytes received and sent after installing OpenStack are presented in Figures 35a and 35b. On x-axis, number of frames are being represented and y- axis rep-resents data transferred in bytes. The number of I/O requests i.e., read requests and write requests after installing OpenStack are given in Figures 36a and 36b.
Figure 33. CPU utilization in 82.6.
Figure 33. CPU utilization in 82.6.
Figure 34b. Disk writes in S2.6. Figure 35a. Network bytes received in S2.6.
Figure 34b. Disk writes in S2.6. Figure 35a. Network bytes received in S2.6.
Figure 35b. Network bytes sent in 82.6.
Figure 35b. Network bytes sent in 82.6.
The CPU utilization in standalone machine with Ubuntu Server OS is given in Figure 37. Similarly, CPU utilization in standalone machine with Ubuntu Desktop OS is given in Figure 38 and CPU utilization in Ubuntu VM i: given in Figure 39. The overall comparison of CPU utilization in standalone machine with Ubuntu Server OS, Ubuntu Desktop OS and in Ubuntu VM before installing OpenStack is presented in Figure 40 and the comparison of CPL utilization in standalone machine with Ubuntu Server OS, Ubuntu Desktop OS and in Ubuntu VM after installing OpenStack is presented in Figure 41.
The CPU utilization in standalone machine with Ubuntu Server OS is given in Figure 37. Similarly, CPU utilization in standalone machine with Ubuntu Desktop OS is given in Figure 38 and CPU utilization in Ubuntu VM i: given in Figure 39. The overall comparison of CPU utilization in standalone machine with Ubuntu Server OS, Ubuntu Desktop OS and in Ubuntu VM before installing OpenStack is presented in Figure 40 and the comparison of CPL utilization in standalone machine with Ubuntu Server OS, Ubuntu Desktop OS and in Ubuntu VM after installing OpenStack is presented in Figure 41.
Figure 37. Ubuntu Server CPU utilization before and after installing OpenStack.
Figure 37. Ubuntu Server CPU utilization before and after installing OpenStack.
Figure 38. Ubuntu Desktop CPU utilization before and after installing OpenStack.
Figure 38. Ubuntu Desktop CPU utilization before and after installing OpenStack.
Figure 39. Ubuntu VM CPU utilization before and after installing OpenStack.
Figure 39. Ubuntu VM CPU utilization before and after installing OpenStack.
Figure 40. Ubuntu Server, Desktop, and VM CPU utilization before OpenStack installation.
Figure 40. Ubuntu Server, Desktop, and VM CPU utilization before OpenStack installation.
Figure 41. Ubuntu Server, Desktop, and VM CPU utilization after OpenStack installation.
Figure 41. Ubuntu Server, Desktop, and VM CPU utilization after OpenStack installation.
Table 5. Comparison of existing cases in literature. 5- Conclusion
Table 5. Comparison of existing cases in literature. 5- Conclusion
Related topics:
Computer ScienceHardware Virtualization
580 California St., Suite 400
San Francisco, CA, 94104
© 2025 Academia. All rights reserved