3. Single Point of Contact and Responsibility . . . Assets Questions Systems Issues Storage Problems Network Asset Management Contract/Lease Management Case Management Vendor Dispatch History/Reports Software Release and Patch Notifications Multi-vendor Support Vendors . . . for 24x7 Delivery of Support Services Intelligent Help Desk TM (150+ 3 rd Party) Customer
8. Maturity of Virtualization Virtualization 2.0 (management layer) Virtualization 1.0 (virtual layer) Physical Resources Policies Procedures Tools 189 of 256
9.
10.
11. vSphere 4 Editions: Core Platform High Availability STANDARD ENTERPRISE PLUS VMware ESXi OR VMware ESX 4-way vSMP VC Agent 6 Physical Cores / CPU 256 GB Physical Memory VMotion ™ High Availability VMware ESXi OR VMware ESX 4-way vSMP VC Agent 12 Physical Cores / CPU 256 GB Physical Memory ADVANCED Fault Tolerance Data Recovery vShield Zones VMotion ™ High Availability VMware ESXi OR VMware ESX 8-way vSMP VC Agent 12 Physical Cores / CPU No License Memory Limit Fault Tolerance Data Recovery vShield Zones Distributed Switch DRS / DPM Storage VMotion Host Profiles High availability products for protecting critical production applications Basic consolidation of a lab or small environment Large scale management of critical production applications New – simplified licensing, per host VMotion ™ High Availability VMware ESXi OR VMware ESX 4-way vSMP VC Agent 6 Physical Cores / CPU 256 GB Physical Memory ENTERPRISE Fault Tolerance Data Recovery vShield Zones DRS / DPM Storage VMotion Update Manager Update Manager Update Manager Update Manager Thin Provisioning Thin Provisioning Thin Provisioning Thin Provisioning VCB / vStorage APIs VCB / vStorage APIs VCB / vStorage APIs VCB / vStorage APIs Hot Add Hot Add Hot Add Multi-pathing APIs
12.
13.
Editor's Notes
Administration – Specifically Provisioning/Decommissioning Lengthy turn-around time to get done and ties up administrator Overallocate resources and hold them for too long VM Sprawl/Monitoring/Performance Don’t know where VMs are and what resources are used Under-utilization, over-utilization of physical resources Can’t identify source of resource contention Physical to Virtual Migration Migrating physical servers to virtual servers Migrating VMs due to periodic replacement of physical resources Chargeback Need to know the exact resources in use by a VM to accurately bill the users If not known, users likely to request more resources and keep longer than necessary Backup and Recovery Wider risk - if a physical server with some number of VMs becomes unavailable May be paying more for licenses if using a backup client on each VM May be exceeding backup windows and/or not backing up all VMs Business Continuance/Disaster Recovery BC – planned downtime causes most service interruptions DR - Speed of recovery, reliable recovery, and non-disruptive testing Configuration Management - Updating/Patching VMs Need to know what VM is located where and whether or not it has been updated Able to automatically and quickly update/patch VMs
Managing in a virtualized environment introduces new considerations. For example, there are new items and relationships that need to be taken into account that are not present in dealing with physical assets. (use slide bullets to explain further)