1 / 24

Network Slicing in Virtual Machines for Cloud Computing

Bilal Anwer Ankur Nayak Pradeep Patil. Network Slicing in Virtual Machines for Cloud Computing. Contents :. Motivation. Network Slicing in Cloud Computing. Experiments / Readings. Architecture. Future Work. Challenges. Conclusion. Motivation :.

evania
Download Presentation

Network Slicing in Virtual Machines for Cloud Computing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Bilal Anwer Ankur Nayak Pradeep Patil Network Slicing in Virtual Machines for Cloud Computing

  2. Contents : Motivation Network Slicing in Cloud Computing Experiments / Readings Architecture Future Work Challenges Conclusion

  3. Motivation : • Cloud computing is the technology of the future • Lack of knowledge about network behavior in cloud computing • Putting more bandwidth is not a solution. Instead, we need a better understanding about network level behavior of cloud computing infrastructure • Need a ground up study instead of studying existing infrastructure • Network is equally important as CPU (if not more since it has recurring costs), still no support/emphasis on network resource management

  4. Cloud Computing : A style of computing in which dynamically scalable and virtualized resources are provided as a service over the Internet • Infrastructure as a Service (IaaS) • Platform as a Service (PaaS) • Software as a Service (SaaS) • Different abstractions of Cloud Computing services • Amazon EC2 - Machine Level • Microsoft Azure - Services Level •  Google AppEngine - Application Level

  5. Cloud Components :

  6. Network Slicing : • Cloud is a result of many developments like • Virtualization • Low Cost hardware • Software as a Service Model etc • Virtualization is sharing of resources • reduces costs • improve resource utilization • CPU slicing is an integral part of cloud computing • Resource guarantee is only in case of CPU

  7. Choice of VM technology : • Platform should be : • Free • Open Source • Community Help • Currently used in a cloud environment • Xen fits the bill

  8. Xen Architecture :

  9. Experiments • Three experiments • Network Characteristics with varying VMs • Web server Performance with multiple VMs • Network behavior in CPU intensive applications

  10. Tools and Techniques • httperf • Linux Kernel Packet Generator • Kernel stats from /proc file system. • VM Setup • Memory = 128MB/VM • HD = 2GB • Debian ‘Etch’ based domUs

  11. Network throughput (Multiple VMs) Source 1 Computer Switch Source 2 Computer

  12. Xen Network Scheduling One Network Active VM: Full bandwidth is allocated to VM. Two Network Active VMs No certain behavior Stable domUs: Fair Share Unstable domUs: One VM hogs bandwidth Rest are starved.

  13. Web Server Performance in VMs

  14. Web Server Performance in VMs • Timeout has no effect on the connection/sec rate • After initial drop. connection/sec becomes stable.

  15. Network throughput with CPU usage

  16. Network throughput with CPU usage

  17. Experimental conclusions • Network Slicing is required since Xen does not guarantee network bandwidth. • Don’t put CPU intensive VMs with Network Intensive VMs • Web server performance drops with increasing number of VMs. (Planners need to use VM numbers)

  18. Contents : Motivation Network Slicing in Cloud Computing Experiments / Readings ARCHITECTURE Future Work Challenges Conclusion

  19. Architecture VMs VMs VMs VMs Router VMs Name Server VMs User

  20. Architecture • Proof of concept architecture implemented • Accountability and Control • Scalable • Pyro Library • Python based implementation • Control bandwidth • B = ∑Vi + ∑Ci

  21. Challenges : Xen is really difficult to set up esp. with different architectures. Problems installing different application on domUs Measurement infrastructure issues e.g. httperf Hardware resources for testing (Gigabit switch etc.)

  22. Future Work : Collecting data with more VMs Architecture extension Implementing Network Slicing in Hypervisor Storage slicing

  23. Acknowledgements Prof. Ling Liu Prof. Nick Feamster Emulab-OPS

  24. THANK YOU

More Related