Virtual Machines and NetLabs 10/19/2016 - wagnerju

Virtualization Virtualization deals with “extending or replacing an existing interface so as to mimic the behavior of another system” Virtual system examples: virtual private network, virtual memory, virtual machine

Traditional software stack Component isolation with virtualization What Is Virtualization? Virtualization is the isolation of one computing resource from the others Traditional software stack Applications installed to specific hardware and OS Component isolation with virtualization Virtual Applications Any application on any computer, on demand Interface bound to process Virtual Presentation Presentation layer separate from process Operating system assigned to specific hardware Virtual Machine OS can be assigned to any desktop or server Storage assigned to specific locations Virtual Storage Storage and backup over the network Create animation to separate computing resources Network assigned to specific locations Virtual Network Localizing dispersed resources Virtualization results in more efficient resource utilization, and supports greater flexibility and simplified change management

Hardware and low-level systems software change quickly High-level software (middleware, applications) changes more slowly

Common Uses of Virtualization Access Virus-Infected Data Test Software, Upgrades, or New Configurations Run Linux on Top of Windows (or vice- versa) Run Headless For Web Development Business Continuity Virtual Desktop / VDI

Common Uses of Virtualization Run legacy software on non-legacy hardware Run multiple operating systems on the same hardware Create a manageable upgrade path

Non-virtualized Data Centers Too many servers for too little work High costs and infrastructure needs Maintenance Networking Floor space Cooling Power Disaster Recovery

Dynamic Data Center Virtualization helps us break the “one service per server” model Consolidate many services into a fewer number of machines when workload is low, reducing costs Conversely, as demand for a particular service increases, we can shift more virtual machines to run that service We can build a data center with fewer total resources, since resources are used as needed instead of being dedicated to single services

VM workload multiplexing Separate VM sizing VM multiplexing s1 s2 s3 We expect s3 < s1 + s2. Benefit of multiplexing ! Multiplex VMs’ workload on same physical server Aggregate multiple workload. Estimate total capacity need based on aggregated workload Performance level of each VM be preserved

Server Consolidation APP APP APP OS OS OS APP APP APP OS OS OS 9% Typically, server workloads only consume a small fraction of total physical server capacity, wasting hardware, space and electricity APP APP APP OS OS OS Through virtualization, these workloads can be consolidated onto fewer physical servers, saving resources and increasing flexibility 9% Utilization 6% Utilization 14% Utilization APP APP APP OS OS OS 30% Utilization

Controlling Costs Server Consolidation 11/5/2017 8:23 PM Controlling Costs Server Consolidation Physical & Virtual Management .NET IIS .NET Exchange SQL © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. 15

Controlling Costs Convert Physical Machines to Virtual Machines 11/5/2017 8:23 PM Controlling Costs Convert Physical Machines to Virtual Machines Utilize P2V technologies to assist in the transition Host Multiple Virtual Machines on Fewer Physical Machines Physical machine can host Windows, Linux, and other OS virtual machines Eliminate stand alone servers for legacy applications Purchase fewer server licenses. Reduce Power Consumption Fewer servers to power Reduced cooling © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

Example Savings Through Virtualization 11/5/2017 8:23 PM Example Savings Through Virtualization 50,000 45,000 40,00035,000 30,000 25,000 20,000 15,000 10,000 5,000 kWh/Year Virtual Servers Physical Servers 1 Server 4 Servers 10 Servers © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

Example Savings Through Virtualization 11/5/2017 8:23 PM Example Savings Through Virtualization Projected Savings Server setup Average Watts kWh/year Cost KG of CO2 Standalone IIS x10 5,001 43,839 $4,007 34,084 One Hyper-V server with 10 IIS7 virtual machines 512 4,490 $410 3,491 Savings 4,489 39,349 $3,597 30,593 Microsoft Actual Dev/Test Savings Number of Servers Hard Drive Space Rack Space Power Physical 477 systems ~$5k each 19 terabytes 30 racks 525 amps Virtual 20 systems ~$20k each 8 terabytes 2 racks 8 amps Savings ~ $2,000,000 11 terabytes 28 racks 517 amps © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

ThRee Virtualization Approaches Full Virtualization Paravirtualization Hardware-assisted Virtualization

Full Virtualization Everything is virtualized Full hardware emulation Emulation = latency

Privileged Instructions Privileged instructions: OS kernel and device driver access to system hardware Trapped and emulated by VMM http://en.wikipedia.org/wiki/Ring_%28computer_security%29 Privilege rings for the x86 available in protected mode Microsoft's Ring-1 design structure as part of their NGSCB initiative and hypervisors embedded in firmware such as Intel VT-x (formerly Vanderpool).

Pros and Cons – Full Virtualization Disaster recovery, failover Virtual appliance deployment Legacy code on non-legacy hardware Cons – LATENCY of core four resources RAM performance reduced 25% to 75% Disk I/O degraded from 5% to 20% Network performance decreased up to 10% CPU privileged instruction dings nearing 1% to 7%

Paravirtualization Requirements: OS or system devices are virtualization aware Requirements: OS level – recompiled kernel Device level – paravirtualized or “enlightened” device drivers

Paravirtualization Pro: fast Con: requires a specially modified guest OS, thus precludes the ability to run off-the-shelf and legacy OS in paravirtual environments

Hardware-assisted Virtualization Server hardware is virtualization aware Hypervisor and VMM load at privilege Ring -1 (firmware) Removes CPU emulation bottleneck Memory virtualization coming in quad core AMD and Intel CPUs

Netlabs Good afternoon. My name is Michael Borokhovich, I'm a Master degree student at the Ben Gurion University in Israel.   I'm going to present a paper that I wrote with Dr. Chen Avin and Dr. Arie Goldfel. Our paper describes the case study of developing, deploying and exploiting a virtual computer networks laboratory. Such a laboratory can be used for teaching Computer Networks and Network Programming courses. The main contribution of our work is providing an example of using virtualization to create an excellent learning facility along with saving costs, space, and energy.

Introduction The Student need for computer labs CIT CIS OTFI Nursing Electronics Architecture Graphics Design So, why do we need a computer networks laboratory. We want to learn how do computers exchange the information in the internet, how the routers on the way know the routes to the destination. We want to learn how to configure those routers and computers to allow them to communicate. In addition we want to measure information rates and many other important papameters.

Working in Typical CIT Lab Assignment document Build network Configure devices IP Addresses Routing protocols Security Test and Capture data Device Interface IP Address Subnet Mask S1 VLAN 1 10.10.10.2 255.255.255.0 PC1 NIC 10.10.10.10 PC2 10.10.10.11 Before each lab session – assignment document with instructions Capture messages (investigate message fields) Take measurements (time…)

Physical (real) lab Pros: Real equipment “Hands on” Cons: Cost Space Time Energy

Simulation (GNS3, Packet Tracer) Pros: Scalable Cost effective Cons: Not a real equipment Not a “hands on” Simulation tools can be limited

Virtual Lab Design Instead of real Network Labs – virtual NetLabs Virtual Machines Real Equipment

Students’ Perspective Almost the same as real

Students’ Perspective Anytime, anywhere On Campus Home Off Campus

Students’ Perspective Building Networks

Students’ Perspective Access Remote access (VNC) through NetLabs Web Interface http://netlabs.cod.edu/ Requires JAVA

Students’ Perspective Virtual Workstations Graphical Desktop Real Hardware

Administrator’s Perspective ESXi Netlabs Administration

System Features Capacity –Hundreds of virtual machines Flexibility – any network topology Remote Access – anytime, anywhere Simple Administration Fast Failure Recovery - everyone can be an administrator or a “root” user In class lab sessions

Conclusions & Future Work Excellent students’ feedbacks Almost full “hands on” lab Saving cost, space, time and energy Easy administration Future work Additional course being developed Increase system capacity Graphical interface to create topologies