Your SlideShare is downloading. ×
VEO (Virtual Ecosystem Optimization)
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

VEO (Virtual Ecosystem Optimization)

182
views

Published on

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
182
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • I need this to pop and under the offerings title or somewhere in the graph be able to fit the bullet list for each of the solutions
  • Transcript

    • 1. vSphere 4: Virtualizing Critical Apps VMUG 2009 Presented By: Matt Cavanagh, Principal Consultant, Flytrap Technologies With Support From: Bluestripe Software & Stratus Technologies
    • 2.
      • Virtualization Adoption trend
      • Obstacles to Virtualizing Critical Apps
      • Required components for Critical Apps
      Agenda
    • 3. Slow and Challenging VM Conversion
      • Exchange Servers
      • Windows 200x Servers
      • 100s/1000s servers
      • Departmental Servers
      • 10s servers
      • First business transactions
      • Windows & Linux front ends
      • Tiers 1&2 virtualized
      • 100s/1000s servers
      • Middleware issues
      Development & Test
      • N Tiered / Web Applications
      • Win, Linux, Solaris, Z series
      • Significant non VM systems
      Recent Forrester discussions estimate lower-left quadrant is majority of today’s estimated 12-15% vm proliferation. Simple Under-utilized Apps
      • Multi platforms for Dev/Test
      • 10s servers
      Simple Heavy Load Apps Complex N tier / Web Apps Integrated Transaction Apps Virtualization Adoption Trends Easy VM conversion Adoption Complexity
    • 4.
      • Organizations conducting virtualization projects are experiencing 18% reductions in infrastructure cost and 15% savings in utility cost
      • However, improvements could be made;
      • 69% of organizations surveyed do not have the ability to discover all connections that impact application performance in virtual environments
      • 71% of organizations do not have the ability to assess interdependencies between virtual and physical systems
      • 76% of organizations do not have tools in place for the automated discovery of applications in virtualized environments
      Adoption Trends…cont….
    • 5.
      • Performance
        • Virtualization overhead too costly prior to vSphere
      • Availability
        • Critical apps typically run on either RISC based machines designed for high availability (e.g. Mainframes) or on x86 running in cluster
      • Management
        • Lack of application transaction flow visibility (55%)
        • Inability to anticipate application performance changes in P2V (49%)
        • Inability to measure end user experience (46%)
        • Inability to manage SLAs around application performance (43%)
        • Bottom Line: Co-mingling critical apps inside a virtual environment makes SLAs and debugging difficult
      Obstacles
    • 6.
      • Performance
        • Virtualization overhead too costly prior to vSphere
      • Availability
        • Critical apps typically run on either RISC based machines designed for high availability (e.g. Mainframes) or on x86 running in cluster
      • Management
        • Lack of application transaction flow visibility (55%)
        • Inability to anticipate application performance changes in P2V (49%)
        • Inability to measure end user experience (46%)
        • Inability to manage SLAs around application performance (43%)
        • Bottom Line: Co-mingling critical apps inside a virtual environment makes SLAs and debugging difficult
      Obstacles…cont…
    • 7. Obstacles…cont…
      • P2V Conversion Checklist
      • Inventory physical servers
      • Resource utilization study
      • Scheduled conversion project
      • Agreement of all departments
      Physical servers P2V Machine Conversion Virtual Servers X X Hidden Application Dependencies Surprise Application Performance Changes
      • Frustrations
      • P2V “collateral damage”
      • Don’t know real activity on Server
      • Resources ≠ Appl Performance
      • Don’t know why performance is different
    • 8.
      • Performance
        • Bare metal performance
      • Availability
        • VMware FT is good, but still lacks several components
      • Management
        • Need detailed insight into application performance across the network
        • Need ability to quickly go back to Physical (even if only for political reasons)
      Required Components
    • 9.
      • Performance
        • vSphere performance improvements now provide bare-metal equivalent performance
      • Availability
        • Stratus HA Servers provide greater than 6 x 9s reliability (99.999% +) availability through hardware fault tolerance.
      The Solution
    • 10.
      • Management
        • Software companies such as Bluestripe provide detailed insight into application performance and interdependencies.
        • Closely analyze application performance & pinch points prior to going virtual & compare this to virtual ( Bluestripe )
        • Continually monitor, root-cause problem areas quickly (Bluestripe)
        • Quickly migrate back to physical if issues appear to be related to virtualization (Acronis BR10)
      The Solution….cont…
    • 11. The Solution….cont…
    • 12.
      • Ensure CPUs support FT
      • Enable Hardware Virtualization (HV) in the BIOS
      • Recommend to turn off power management (power capping)
      • in the BIOS (performance implications)
      • Recommend to disable hyper-threading in the
      • BIOS (performance implications)
      • Physical RDM is not supported (note that Virtual RDM is supported)
      • Storage VMotion is not supported
      • N-Port ID Virtualization (NPIV) is not supported
      • vmdk must be thick-eagerzeroed (thin will be converted)
      • Gigabit NIC for FT logging (10Gbit can be used)
      • Ensure environment does not have a single point of failure
      • Primary and secondary hosts/VMs in HA-enabled cluster
      • DRS cannot be used for protected VMs (note that manual VMotion is OK)
      • Primary and secondary hosts must be on same build
      • VMs cannot have more than 1 vCPU (SMP is not supported)
      • Hot add of devices is not supported
      • Snapshots are not supported (delete them before protecting)
      • VM hardware must be a v7
      • No more than 4 (to 8) FT enabled VM primaries or secondaries on a single host
      • Para-virtualized guest OS is not supported
      • Remove 3rd party clustering before protecting with VMware FT
      VMware FT “Gotchas”
    • 13.
      • Real-time application structure mapping
      • Hop-by-hop Service Level triage
      • Drill down from application process to machine
    • 14. Report Card Definitions Grade Definition Needs Attention Specific items of concern identified Caution Potential for possible items of concern of either low criticality or further investigation needed OK Adherence to best practices guidelines with no obvious signs of items of concern No Data Unable to gather data to evaluate, or not applicable
    • 15. Report Card: Virtual Infrastructure Needs Attention Management Enable VT within BIOS for 64bit OK Troubleshooting Use fixed IP address for service console Needs Attention Troubleshooting Properly configure all service console network settings (VI2 only) OK Performance Troubleshooting Allocate sufficient service console memory resources Needs Attention Management Troubleshooting Minimize differences in number of storage paths Needs Attention Troubleshooting Minimize differences in LUNs visible across hosts OK Management Minimize differences in number of active NIC ports across hosts Needs Attention Management Troubleshooting Apply consistent naming conventions for shared storage and networks OK Management Troubleshooting Utilize uniform servers, particularly CPU types OK Management Troubleshooting Configure storage and networking consistently Needs Attention Troubleshooting Maintain the same software versions across hosts OK Performance Place host devices in proper order/location No Data Performance Troubleshooting Consider enabling Hyper Threading, if applicable Technical Analysis Status Impact Best Practice Guideline
    • 16. Report Card: Networking None Performance Adjust vSwitch network load balance settings as needed OK Performance Segment network traffic by type of workload None Management Configure using minimum number of vSwitches and physical adapters per best practices to segment VM from management traffic while allowing redundancy OK Management Performance Separate user application traffic from management traffic Needs Attention Troubleshooting Configure VMotion network properly Needs Attention Troubleshooting Set VMware HA isolation response (power off VMs?) accordingly depending on network stability (VI3 only) Not Applicable Management Use vSwitch failover options Needs Attention Management Use vSwitch port groups to segment traffic OK Performance Avoid mixing network speeds on the same vSwitch OK Performance Troubleshooting Set network adapter speeds if necessary Needs Attention Management Troubleshooting Configure vSwitches with optimal redundancy Technical Analysis Status Impact Best Practice Guideline None
      • Networking
    • 17. Existing Networking
    • 18. Proposed Network
    • 19. Report Card: Storage OK Performance Limit use of VM snapshots and independent disk REDO files OK Management Use shared storage for VMs instead of local storage Needs Attention Management Size storage LUNs appropriately OK Management Performance Allocate separate space for templates and media from VMs Needs Attention Troubleshooting Allocate space for VM snapshots and independent REDO files Needs Attention Troubleshooting Allocate space for VM memory swap (VI3 only) OK Performance Configure iSCSI properly if using software initiator (VI3 only) Not Applicable Troubleshooting Configure multipathing to storage properly Technical Analysis Status Impact Best Practice Guideline None
      • Storage
    • 20. Report Card: VMs Needs Attention Performance Install VMware Tools OK Management Deploy workloads relative to host CPU and RAM capability Caution Performance Configure and use CD-ROMs and Floppy devices properly OK Troubleshooting Use proper Guest OS type when configuring VMs Technical Analysis Status Impact Best Practice Guideline None
      • Virtual Machines
    • 21.
      • Storage:
        • Grow VMFS volumes to hold multiple VM (OS drives)
          • Rule of thumb: <= 10 VMs per VMFS volume
        • VMFS volumes should have enough free space to handle VM snapshots & vswap files.
        • ACLs on Eql array need to be modified: limit only to iqn names of ESX hosts.
        • Provide redundant connections from each ESX host to SAN fabric
      • VCMS:
        • Move Virtual Center to Windows 2003 server on ESX cluster.
          • Note: set restart priority to High in HA cluster setting
      Healthcheck Recommendations
    • 22.
      • Networking:
        • Use NIC teaming to provide network redundancy for all networks.
          • Remove existing Heartbeat network to free up NIC port
        • Upgrade SAN switch infrastructure:
          • Stackable switches with support for Jumbo Frames, Flow Control, Multicast storm control disable, STP disable
      • Virtual Machines
        • Upgrade VMware tools
      Healthcheck Recommendations