SERVER VIRTUALIZATION

Transcription

1 SERVER VIRTUALIZATION Isaac Rozenfeld Technical Specialist, OS Ambassador Sun Microsystems, Inc. New York City Technology Forum November 1st, 2007

2 Agenda What is Virtualization? > Why virtualize now? Virtualization Technologies > In the Hardware > In the Operating System Virtualization Business Assessments > Chris Theon Lessons Learned From in-house Deployments > Marcos Merced

3 The Data Center Today Server sprawl is hard to manage. Deployment takes too much time Single application per server App Server Mail Server Database Database Service Application OS Server Average server utilization varies between 5 to 15 % Storage Data Center Management App Server NETWORK Developer Client

4 Virtualize Everywhere! Priority 1: Maximize system resources across entire Data Center Network Web Developer Priority 2: Quickly (re)deploy new applications App Server ERP App Mail Server Server CRM Database ERP Database Service Application OS Server Priority 3: Provide business-continuity capabilities Storage Data Center Management Client

5 A (Very) Brief History...

6 Some History Virtualization technology is NOT a new idea > Goes back to 30+ years; now on multiple platforms New needs, current economics all warrant renewed emphasis > > > > > Increased server sprawl Rising energy costs Need for rapid re-deployment of existing assets Dependencies on software that is no longer supported Modernization of operating environments, architectures Solutions vary across different platforms > Different benefits (and limitations)

7 What Is Involved? Generally: An illusion of a dedicated computer for multiple instances, with no awareness of each other > Of your application service > Of an Operating System > Physical or Logical Partitioning > Hardware and/or firmware capability > Virtual Machines > Host OS ( hypervisor ) software & Guest OS software > I/O Subsystem Layers (disk, network) & Interfaces > Modern CPUs, Memory Address Space management > Examples: AMD-V, Intel VT, SPARC, POWER

8 What Is Involved? Generally: An illusion of a dedicated computer for multiple instances, with no awareness of each other > Of your application service > Of an Operating System > Physical or Logical Partitioning > Hardware and/or firmware capability > Virtual Machines > Host OS ( hypervisor ) software & Guest OS software > Basic distinction between these: architectural limits on number of OS instances or concurrent environments Goals: > Secure, isolated boundary for one or more environments formulating all that's necessary for an illusion to seem real ;-)

9 Motivating Factors

10 Use Cases Server Consolidation Testing and Development Fail-over through replication Provisioning of compute resources Legacy Applications Secure Execution

11 Case Study: Server Consolidation Interest in improving resource utilization > Want better ROI and do more with what we already have An approach may involve: > Multiple workloads working concurrently > Without awareness of (or interference with) each other > Virtualization: UID collisions, naming conventions, port conflicts > Analysis of Service Level Agreements (SLAs) > Resource Management technologies and Workload Managers help > Chargeback Analysis > To ensure appropriate distribution of costs for shared services > Reliability, Availability and Serviceability (important) > Fewer single points of failure introduce the need for stringent process, policies

12 Server Consolidation Operational Maturity > Fewer software/operating system versions (as needed) > Different OS, kernels > Workload-favorable kernel tunable parameters > Helps minimize risk through minimization efforts Auditors will probably buy you lunch! Additional Benefits > Agile upgradability, deployment, provisioning > Use legacy OS application environments on newer hardware > Ex: VMware, Xen, Trigence, Parallels, Solaris BrandZ, Microsoft Virtual Server > Better performance per watt, per RU > Pave the way for workload mobility

13 Navigating The Solution Set

14 Choosing The Right Solution For You What is driving the need? > Some needs have overlapping solutions > Choice or combination of technologies possible > Some virtualization technologies do not fit some of the needs > Don't belong in the set of solutions you can choose from Our Task (as engineers) > Find the right combination to solve the problem Our Task (as architects) > Ensure the Big Picture is top of mind > Keep things in scope

15 Sweet Spots *Not an exhaustive representation Hard Partitions Virtual Machines OS Virtualization Resource Management App OS Server Multiple OSes Single OS Trend to flexibility Trend to isolation Trend to observability > Very High RAS > Ability to live migrate an OS > Very Scalable > Ability to run different OS > Mature Technology > Ability to run different OS versions or kernel patch revisions versions and types > De-couples OS and HW versions > Very scalable and low overhead > Single OS to manage > Cleanly divides system and application administration > Fine grained resource management > Very scalable and low overhead > Single OS to manage > Fine grained resource management

16 Application (Service) Perspective

17 Example: BrandZ (Branded Zones) (v880-room2-rack5-1; ) dns1 zone (dnsserver1) web1 zone (foo.org) web2 zone (bar.net) Linux zone (linux) zone root: /zone/dns1 zone root: /zone/web1 zone root: /zone/web2 zone root: /zone/lx login services login services login services network services network services network services core services core services core services zoneadmd zoneadmd zoneadmd pool1 (4 CPU), FSS ce0:3 zcons ce0:2 ce0:1 60 (NIS, xinetd, autofs) zoneadmd pool2 (4 CPU) zone management (zonecfg(1m), zoneadm(1m), zlogin(1),...) core services remote admin/monitoring platform administration (inetd, rpcbind, sshd,...) (SNMP, SunMC, WBEM) (syseventd, devfsadm, ifconfig, metadb,...) storage complex network device network device network device (hme0) (ce0) (ce1) Application Environment Linux core services (inetd) hme0:2 zcons 30 /usr hme0:1 (inetd) zcons /usr 10 (IWS) hme0:3 (inetd) (OpenSSH 3.6, acroread,matlab, yum, pandora) /usr (Apache, Tomcat) zcons (named) linux user apps (SSH sshd, telnetd) Virtual Platform (SSH sshd) /usr (SSH sshd) ce1:1 Global zone

18 In Summary Important Considerations Security, Privileges, Isolation > Network services in virtualized environments, limiting risks that can affect other workloads, systems in case of a security violation > Applications requiring exclusive access can be virtualized and ran concurrently on the same system Capacity Planning > Virtualized environments and newer hardware may require newer approaches; resource modeling tools help Management & Infrastructure ISVs > While a virtualized environment is presented to applications, certain pieces of the infrastructure stack may need to be virtualization-aware (i.e. newer versions)

19 Q&A Additional Resources: > Slicing and Dicing Servers: A Guide to Virtualization and Containment Technologies Dr. Harry Foxwell, Isaac Rozenfeld October 2005 > > Jeff Savit's Virtually All The Time Blog > > Various vendors' websites > Various open-source communities Questions? Thank You!

20 SERVER VIRTUALIZATION Isaac Rozenfeld Technical Specialist, OS Ambassador Sun Microsystems, Inc. New York City Technology Forum November 1st, 2007