1 / 76

Solutions@Work Q3 2006

Solutions@Work Q3 2006. Dario Regazzoni Andrea Siviero dregazzoni@vmware.com asiviero@vmware.com. Agenda. Virtual Center 2.0 & License server DRS HA VCB Upgrade from ESX2/VC3. Agenda. Virtual Center 2.0 & License server DRS HA VCB Upgrade from ESX2/VC3.

jason-patterson
Download Presentation

Solutions@Work Q3 2006

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. Solutions@WorkQ3 2006 Dario Regazzoni Andrea Siviero dregazzoni@vmware.com asiviero@vmware.com

  2. Agenda • Virtual Center 2.0 & License server • DRS • HA • VCB • Upgrade from ESX2/VC3

  3. Agenda • Virtual Center 2.0 & License server • DRS • HA • VCB • Upgrade from ESX2/VC3

  4. Virtual Infrastructure Object Model • Full object model for virtual infrastructure forms the foundation for VirtualCenter 2.0 • Same API exposed at VirtualCenter and ESX Server • Internal API = public API • API available at both VirtualCenter and at ESX Server hosts VMware GUI Client VMware Web Client Third-Party API ESX Server Virtual Center

  5. VirtualCenter 2.0 Inventory • VirtualCenter 2.0 Inventory provides: • More natural organization • Virtual and Physical objects organized separately • More visibility into object relationships • Greater flexibility in organizing VC objects • User defined organization model for all of the major VC objects • Simplified templates • VirtualCenter 2.0 inventory expanded to include new types of objects • Datacenter (replaces Farm) • Clusters (supports DRS and HA) • Resource Pools • Datastore, Network

  6. Topology Maps • Graphically show the relationships between: • Hosts • Virtual Machines • Networks • Datastores • Useful in clustering and VMotion scenarios • Are all my hosts hooked up to the same shared storage? • Is my cluster set up correctly to support DRS? • What hosts can my virtual machine VMotion to?

  7. VM Resource Map Example Legend = Datastore = vSwitch = VM = Managed host

  8. Host Resource Map Example

  9. Re-Designed Virtual Machine Templates • Templates are now simply “special” virtual machines in the inventory • Restricted from powering on • VM patching & updating enabled by converting to VMs, powering-on, and then re-instating as templates • Templates are always held in a VMFS or NAS (no longer on VC)

  10. Host and VM Performance Charts • Redesigned to include more data, allow customization • Subsumes details previously only in tools such as vmkusage and esxtop • Objects in the inventory and their metrics can be selected for display • Several levels of granularity & time-intervals • Real-time statistics at a 20-second sampling rate • Archived statistics for the past hour, day, month, etc. • OR for a specific time interval specified • Full exportable to Excel or HTML format

  11. Web Access Product Goals • Enable end-users to access and configure VMs through a browser with minimal installation/config • Remote Console Plug-in (for IE or Mozilla) • Removable device configuration • Power controls • Provide virtual machine administrators a convenient method for distributing virtual machines • “Bookmark” virtual machine • Complete virtual hardware configuration • Add and remove virtual hardware • Event, task and alarm logs

  12. Manage VMs with Web Access

  13. Web Access Remote Console

  14. “Bookmark” a VM • Provide limited (perhaps temporary) access to a VM • Select user interface features • Provides “bathroom door lock” security • Real security provided via VC permissions • Provide generated URL to user

  15. Better Auditing in Events

  16. Four Levels of Logging

  17. Custom Roles and Permissions • Fine-grain control over user groups and privileges • Instead of four fixed classes of users, new features include: • Individual “granular” privileges for each action in the system • User defines roles as a set of privileges • Down the tree propagation/privilege-inheritance is optional • Propagated access can be limited

  18. Types of Roles System-defined roles (cannot be modified) • No Access • Read-Only • Administrator Custom roles (VC users with appropriate privileges can create and modify), for example: • Night shift operator • Backup administrator Active Directory VirtualCenter Power on VMs Add devices Night-shiftoperator Joe Power off VMs Change memory user role privileges permission Inventory object(VM, VM group, cluster,datacenter…) User-defined roles (default privileges in each role can be modified) • Virtual Machine Administrator • Datacenter Administrator • Virtual Machine Provider • Virtual Machine Power User • Virtual Machine User • Resource Administrator

  19. Assigning a Role to a User • Choose a user or group in left panel • Choose a role in right panel • Checkmarks show which permissions the role has

  20. Creating a Custom Role • Choose the Admin screen • Right-click to add a new role • Enter a role name and choose permissions

  21. FlexNet Licensing Changes • New licensing mechanisms use FlexNet license files. • In order to upgrade from ESX 2 / VirtualCenter 1 to ESX 3 / VirtualCenter 2 customers will need update product binaries and product licenses • Encrypted content inside license files determines the type of functionality: • Feature types, evaluation vs. perpetual, & quantity (per-processor) enabled • 2 Different types of license files available for download:

  22. Served Licensing Details License server(a Windows binary) ESX Server 3.0 systems • Default is to install and configure a license server on the same system as VirtualCenter 2 • Pre-existing FlexNet license server, or installation on system independent from VirtualCenter may also be used • Centrally managed licenses can be tracked, and dynamically allocated/re-allocated to servers in 2-processor increments • Once configured, VirtualCenter & ESX Servers remain fully functional during periods of license server unavailability VirtualCenter 2.0 server License file

  23. Host-Based Licensing Details ESX Server 3.0 systems • Suitable for small environments without VirtualCenter • Requires individual license files configured on each ESX Server instead of a single, centrally managed file • Allows ESX features to be configured and changed completely independently from license server • But requires manual license allocation & tracking • Can be combined with served licensing for VirtualCenter features and/or used for subset of ESX Servers managed License file License file License file

  24. License Status

  25. License Server Availability • License Server designed to not to be a SPOF • 14-day grace period (allowed operations) • VM‘s continue to run • Virtual Center Server continues to run • ESX server hosts continue to run • Cluster for VMotion and DRS remain operational • 14-day grace period (restricted operations) • Adding hosts to VC inventory • Adding or removing host from a cluster • Adding or removing license keys • When grace period has expired • VM‘s continue to run, but cannot be rebooted • Licensed add-ons (e.g. VMotion, DRS) no longer operate

  26. Permitted Licensed Operationsif License server is unavailable

  27. Agenda • Virtual Center 2.0 & License server • DRS • HA • VCB • Upgrade from ESX2/VC3

  28. VMware DRS in action Dynamic and intelligent allocation of hardware resources to ensure optimal alignment between business and IT • Intelligent allocation of resources based on pre-defined rules and policies • Monitor utilization across resource pools • Optimize data center resources • Dynamically adjust supply based on changing demand for resources • Prioritize resources to the highest value applications • Conduct zero-downtime server maintenance Business Demand Resource Pool

  29. What Is DRS? • DRS = Distributed Resource Scheduler • Automatic virtual machine placement • Optimize load balance across hosts • Decide if, when, and where to migrate • React to dynamic load changes • Cluster-wide resource management • Scalable resource controls • Configurable automation levels • Integrated UI for all controls

  30. Key Features • Virtual machine placement • Choose initial host when VM powers on • Dynamic rebalancing using VMotion • Configurable automation levels • Manual – recommend initial host and migrations • Partial – automatic initial host, recommend migrations • Full – automatic initial host and migrations • Resource pools • Flexible grouping, sharing, and isolation • Hierarchical organization and delegation

  31. Placement Constraints • VMotion compatibility • Processor type • SAN and LAN connectivity • Anti-affinity rules • Run virtual machines on different hosts • Motivation: high-availability, clustering • Affinity rules • Run virtual machines on same host • Motivation: locality, performance benefits

  32. Resource Pools • Motivation • Allocate aggregate resources for sets of VMs • Isolation between pools, sharing within pools • Flexible hierarchical organization • Access control and delegation • What is a resource pool? • Named object with permissions • Reservation, limit, and shares for both CPU and memory • Parent pool, child pools and VMs

  33. Admin manages users Policy: Alice’s share50% more than Bob’s Users manage own virtual machines VM allocations: 30% 40% 30% Resource Pools Example Admin 300 Admin 200 Admin Alice Bob 75 Alice 400 Bob 75 Alice VM1 VM2 VM3

  34. Same policy Pools isolate users Alice still gets 50%more than Bob VM allocations: 800 Bob 30% 13% 27% 30% Example: Bob Adds Virtual Machine Admin 300 Admin 200 Admin Alice Bob 75 Alice 400 Bob 75 Alice VM4 VM1 VM2 VM3

  35. Agenda • Virtual Center 2.0 & License server • DRS • HA • VCB • Upgrade from ESX2/VC3

  36. VMware HA in action VMware HA enables cost-effective high availability for all servers • Automatic restart of virtual machines in case of server failure • No need for dedicated stand-by hardware • None of the cost and complexity of clustering X Resource Pool

  37. Why didn’t VMware HA come sooner? ESX Server 2.x ESX Server 3.0 vmx vmdk vmdk vmx nvram nvram SAN-based VMFS-2 /home VMFS-3

  38. What are the prerequisites for VMware HA? • You must be able to power on a VM from all hosts within the cluster • Access to common resources (shared storage, VM network) • Host must be configured for DNS • DNS resolution of all hosts within cluster

  39. vpxa vpxa vpxa VMap VMap VMap AvailMgr AvailMgr AvailMgr Architecture of a VMware HA cluster VC Server Virtual Machine Virtual Machine Virtual Machine

  40. What if a host is running but isolated? ? • A network failure might cause a “split-brain” condition • VMware HA waits 15 seconds before deciding that a host is isolated • This interval is not presently configurable Virtual Machine Virtual Machine Virtual Machine Virtual Machine ? Virtual Machine Virtual Machine Virtual Machine Virtual Machine

  41. Agenda • Virtual Center 2.0 & License server • DRS • HA • VCB • Upgrade from ESX2/VC3

  42. REDO VMDK VCB: How it Really Works c:\windows\pre-freeze-script.bat c:\windows\post-thaw-script.bat ESX What’s REALLY Happening Virtual Center VM1 VMSNAP SNAP ID Backup Proxy VM2 Service Console VM3 SYNC JS LIBRARY VM DNS NAME BACKUP INFO BACKUP INFO vmkernel VLUN VMFS VMDK VMDK VMDK BLOCK LIST SAN

  43. VCB: Integrations • 3 Groups: • Group 1: • VMware produced integration • Basic integration only—commandline, pre-and-post job scripts • Group 2: • Have committed to building their own integration soon after release of VCB—in some cases superior to the integration produced for Group 1. • Group 3 • Not necessarily committed to either of the above Note that some partners will be producing their own integration in addition to VMware-produced integration

  44. VCB: Integrations Group 1: • Symantec/VERITAS • NetBackup and Backup Exec • Legato Networker • Tivoli Storage Manager Group 2: • Commvault • CA Brightstor • Vizioncore • Veritas NetBackup Group 3: • HP Data Protector • SyncSort • Atempo • BackBone • Dantz • Innovation Data Processing

  45. Agenda • Virtual Center 2.0 & License server • DRS • HA • VCB • Upgrade from ESX2/VC3

  46. Before you begin • The upgrade process Read the upgrade guide Create an upgrade plan RE-READ THE UPGRADE MANUAL Perform upgrade

  47. Upgrade Guide • http://www.vmware.com/pdf/vi3_installation_guide.pdf P.87

  48. Potential problems to avoid • Clustered VMs must be in RDM • Commit or discard all REDO before uprade • Licenses for VI3 (served or host-based ?)

  49. steps to follow • Backup • Upgrade / (re)install Virtual Center • Upgrade / (re)install ESX server • Upgrade VMFS 2  VMFS 3 • Upgrade your VM’s

  50. Understanding upgrade dependencies

More Related