VMworld 2015: Managing vSphere 6 Deployments and Upgrades
•Download as PPTX, PDF•
2 likes•457 views
Managing vSphere 6 Deployments and Upgrades
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to VMworld 2015: Managing vSphere 6 Deployments and Upgrades
Similar to VMworld 2015: Managing vSphere 6 Deployments and Upgrades (20)
More from VMworld
More from VMworld (15)
Recently uploaded
Recently uploaded (20)
VMworld 2015: Managing vSphere 6 Deployments and Upgrades
- 1. Managing vSphere 6.0 Deployments and Upgrades, Part 2 Brian Graf, VMware, Inc Salil Suri, VMware, Inc INF5123 #INF5123
- 2. Disclaimer • This presentation may contain product features that are currently under development. • This overview of new technology represents no commitment from VMware to deliver these features in any generally available product. • Features are subject to change, and must not be included in contracts, purchase orders, or sales agreements of any kind. • Technical feasibility and market demand will affect final delivery. • Pricing and packaging for any new technologies or features discussed or presented have not been determined. CONFIDENTIAL 2
- 3. Introductions! CONFIDENTIAL 3 Brian Graf Senior Technical Marketing Manager PowerCLI, ESXi Lifecycle, ROBO @vBrianGraf VMware Blog: http://blogs.vmware.com/vSphere/ Personal Blog: http://www.vtagion.com Salil Suri Product Line Manager Core ESXi and vSphere Lifecycle @SalilSuri
- 4. Agenda 1 vSphere Upgrade Overview 2 Upgrading vSphere ESXi 3 Upgrading Virtual Machines 4 Post Upgrade Considerations 5 What’s new in Tech Preview 6 Technical Resources CONFIDENTIAL 4
- 5. VMware released vSphere 6 … CONFIDENTIAL 5
- 6. CONFIDENTIAL 6 And an important date is fast approaching… End of General Support for ESXi 5.0 and 5.1 Source: http://tinyurl.com/pyvv6v7 2016 / 08/ 24
- 7. Which often leads to conversations such as .... CONFIDENTIAL 7
- 8. CONFIDENTIAL 8 “We are currently upgrading our vSphere environment to the latest version and are finding the upgrade process complex & time consuming!”
- 9. Our Goal: vSphere upgrade should make you feel like… CONFIDENTIAL 9
- 10. vSphere Upgrade Overview CONFIDENTIAL 10 Phase 1 Upgrading vCenter Server Phase 2 Upgrading ESXi Phase 3 Upgrading Virtual Machines Phase 4 Post Upgrade Considerations : Managing vSphere Deployments & Upgrades – Part 1
- 11. Upgrading ESXi
- 12. Planning for ESXi Deployment & Upgrade CONFIDENTIAL 12 • How many hosts? • Sensitivity to downtime? • Maintenance window duration? • Choice of upgrade method? • DRS / Host Profiles in use? • VMs on shared storage? Questions Considerations
- 13. ESXi Install versus ESXi Upgrade • Traditional “OS” upgrade concerns do not apply! – Boot disk is not repartitioned – Overwrites Boot Bank contents – Configuration and VMFS volume preserved CONFIDENTIAL scratchMB storecoreBank 1 Bank 2 1GB VMFS Remainder4GB 5.5 6.0 Step 1: Save the Config (state.tgz) Step 2: Replace VIBs (overwrite) Step 3: Reboot Step 4: Config re-applied on reboot 13
- 14. ESXi Deployment methods: You have choices! CONFIDENTIAL 14 ESXi ISO VUM Auto Deploy Scripted esxcli Install Upgrade Patch UI & DRS integration Supports Rollback Optimized @ scale
- 15. Rolling Upgrades with VUM CONFIDENTIAL vCenter 6 + VUM vSphere Cluster vMotion vMotionvMotion Upgrades with no VM downtime! vMotion / Storage vMotion 15
- 16. Introducing AutoDeploy & Host Profiles CONFIDENTIAL Bare-Metal Host Out – of – Date Host (5.x) Misconfigured Host Roll-back Host (6.x) What are my ESXi Install options? What are my ESXi upgrade options? How can I keep ESXi Configuration consistent across my ESXi inventory? Oops, I applied a faulty patch. Can I roll-back? • Single workflow for various ESXi deployment, patch, & upgrade scenarios. • “Zero-Touch” & highly automatable workflow • Centralized Image & Configuration Management across your Data Center Benefits! : ‘Zero Touch’ ESXi Deployment, Configurations and Upgrades with AutoDeploy & Host Profiles
- 18. VMware Tools consumption workflow VMware Tools Team Linux community Linux kernel main MyVMware or packages.vmware.com Up streaming Tools Linux distro w/ OVT Distro’s ESXi w/ Pre-installed tools can be upgraded using VUM or API
- 19. VM Compatibility Upgrade! CONFIDENTIAL 20 Can also upgrade using default VUM baselines! Virtual Hardware is now called VM Compatibility
- 20. Extended Support Matrix CONFIDENTIAL vSphere 5.0 vHW 4 vHW 7 vHW 8 vSphere 5.1 Tools 5.1 Tools 4.x Tools 5.0 vHW 9 Virtual HardwareSupported ToolsvSphere Release upgrade vSphere 5.5 Tools 5.5 vHW 10 upgrade 21 vSphere 6.0 Tools 6.0 vHW 11 ESX 3.5 and later ESX 4.x and later ESX 5.0 and later ESX 5.1 and later ESX 5.5 and later VM Compatibility ESX 6.0 and later upgrade
- 21. Best Practices & Recommendations! • VMware Tools – Upgrade recommended! – Use open-vm-tools wherever possible. – Cross Compatibility (see VMware Interoperability Matrix) • VMware Tools 4.x is supported on ESXi 6.x. • VMware Tools 6.x is supported on ESX/ESXi 4.x. • Hardware Version or Compatibility – Upgrade Optional • Upgrade VMware Tools first • Compatibility is not Backwards Compatible CONFIDENTIAL 22 Q: Okay, but how do I know when to upgrade? A: Release Notes for VMware Tools & common versioning Coming Soon…! This is the Future and is available today! You can skip versions and save your self some effort!
- 22. Announcing VMware Tools 10.0! CONFIDENTIAL 23
- 23. 24 Roadmap The information on the roadmap is intended to outline our general product direction and it should not be relied on in making a purchasing decision. It is for informational purposes only and may not be incorporated into any contract.
- 26. VMFS Upgrade Considerations CONFIDENTIAL Feature Upgraded VMFS-5 New VMFS-5 Maximum files 30720 130689 File Block Size 1, 2, 4 or 8MB 1MB (Unified) Sub-Blocks 64KB 8KB Partition Format MBR (seamless switch to GPT if VMFS grows > 2TB) GPT Starting sector 128 2048 27
- 27. VMFS Upgrade Considerations • Upgrade all hosts to 5.x before upgrading VMFS-5. – Upgrade not allowed if 4.x hosts are accessing VMFS • There is no “undo” (one-way operation) • To fully benefit from latest VMFS 5 features: 1. Creating new VMFS 5 volume 2. Use Storage vMotion to migrate VMs 3. Schedule data migrations for non-peak hours 4. It can take a while to migrate large data files CONFIDENTIAL 28 New VMFS version coming. Upgrade to vmfs version 5 first!
- 29. vSphere Upgrade Overview: Summary Key Points: 1. Order is important! 2. Check Hardware Compatibility & Solution Interoperability before starting! 3. Choose an ESXi method which works for your environment! 4. Understand Virtual Machine upgrade requirements and choose what works for you! 5. Don’t forget about plug-ins, add-ons, VMFS, VDS, etc.! CONFIDENTIAL 30 Approach upgrades with a holistic view of your virtual Infrastructure
- 30. So #What’sNext?
- 31. “Customer Feedback” • ESXi Upgrades take too long to execute! • Why is VUM is not integrated with the Web Client? • VUM is Windows only application! It is 2015! Pain Points
- 32. Steep reduction in ESXi upgrade time! CONFIDENTIAL 33 0 500 1000 1500 2000 2500 3000 3500 vSphere 5.5 vSphere 6 vSphere 6.0 U1 * Host Evacuation time (s) Host Evacuation Mixed Load (s) • Host evacuation is ~ 50% of Time to upgrade! • Average reduction is 4-7x! • select cases 27-30x! Dramatic Time savings! vSphere 6.0 U1 & 5.5U3 ** "I just saw the VM's zip by so fast. This used to take hours. This is such a time saver, and will help everyone! …" - VMware IT teamTime (s)
- 33. Introducing Full support for VUM in the web Client! CONFIDENTIAL 34 vSphere 6.0 U1** NEW
- 34. VUM Today! 35 2015 + ESX Server Cluster Host Server ESX Server ESX Server vCenter Server w/o Update Manager • Windows Only. • Separate DB to install, maintain and upgrade! • Separate Install, Upgrade & Patch for VUM! Pain Points
- 35. VUM with fully embedded in vCSA! 36 2015 + ESX Server Cluster Host Server ESX Server ESX Server w/ Update Manager • NO Windows. • NO Separate DB • NO Separate Install, Upgrade & Patch for VUM! Customer Benefits!
- 37. Getting Started with vSphere Upgrade http://vmware.com/go/vsphere-upgrade CONFIDENTIAL 38
- 39. Other vSphere Upgrade Resources: • vSphere Documentation Center https://www.vmware.com/go/docs • VMware Compatibility Guide http://www.vmware.com/go/vcg • Product Interoperability Matrix http://www.vmware.com/go/interop CONFIDENTIAL 40
- 40. In Closing: • There has never been a better time to upgrade to vSphere 6. Start planning for it now and take a holistic approach to planning it out! It’s easy. • VCSA deserves serious consideration. This will help future proof your investments. • Several ESXi lifecycle and VUM enhancements rolling out in 6.0 U1 and more to follow! • We would love to chat and get your feedback. Let’s talk @SalilSuri & @vBrianGraf CONFIDENTIAL 41
- 43. Managing vSphere 6.0 Deployments and Upgrades, Part 2 Brian Graf, VMware, Inc Salil Suri, VMware, Inc INF5123 #INF5123
Editor's Notes
- 2
- This presentation focuses on upgrading ESXi. In preparation for a discussion on upgrading ESXi we’ll talk about how the ESXi software is packaged and distributed and cover some important distinctions related to patches and updates vs. upgrades. We’ll then go over the ESXi upgrade process and then wrap things up by reviewing important post-upgrade considerations, such as upgrading VMware Tools, Virtual Machine Hardware, VMFS volumes and Virtual Distributed Switches. Notes: Can get an updated image showing sphere 5.5?
- Before you upgrade consult the documentation. Particularly the release notes and upgrade process. Watch for things that are different. Don’t assume that because your hardware worked with the prior version it will work with the current version. Do your due diligence and verify that your hardware is listed in the compatibility guide. Know what versions of software you are running and verify interoperability with the new software before upgrading. You may need to coordinate the upgrade of other software components at the same time you upgrade vSphere. For example, VUM, View, Horizon Suite, vCD, etc.
- Before jumping into the details of the ESXi upgrade process, it’s important to understand the big picture and to know where the interdependencies are. Here we see the vSphere upgrade path, note that There are five basic phases to upgrading vSphere. (four if you don’t use VUM) Always upgrade vCenter Server first Each phase can be done independent of the other, and spaced out over time. As you progress through each phase, you can only roll back by restoring from a backup taken prior to starting the phase. In this presentation we will focus on Phases 3, 4 and 5. Phase 1 is being covered in a separate breakout session.
- This slide shows what happens on the ESXi host during an upgrade. Regardless of upgrade method, end-state of the ESXi hosts is the same!! Key point is that we do not touch your VM data store! Note that this is the same procedure regardless if you use the ESXi Installer or update manager Configuration is saved (state.tgz) Old VIBs are removed New VIBS are copied in Host reboots VMFS left intact. HD is not repartitioned. Key here is upgrades are really very simple. Nothing to be scared of.
- There are four ways to upgrade your vSphere hosts: Boot from the ISO and run the ESXi installer Import the ISO into VUM and create an upgrade baseline Save the offline depot and use ESXCLI Create answer files and boot from the ISO to perform an unattended scripted install Regardless which upgrade method you use, it entails the same basic process. Save the configuration (state.tgz), replace the VIBs, and reboot the host. The configuration is automatically restored as part of the reboot. VMFS volumes on the boot disk are left intact.
- This slide provides an overview on how to complete a rolling upgrade. Note that vCenter has already been upgraded. Things to highlight: Rolling upgrades are supported. Rolling upgrades allow you to easily upgrade large clusters without incurring VM downtime. To do this you will need to leverage the advanced vSphere features like vMotion, Storage vMotion, DRS, etc. Remember you can leverage the 60-day trial period available with the vCenter 5.0 upgrade to access to all vSphere feature Don’t upgrade VM compatibility or VMFS volumes until after all hosts have been upgraded It’s okay to upgrade tools at any time as tools are both forward and backward compatible (more later)
- To summarize when upgrading VMFS volumes: Wait until all hosts are running ESXi 5.x Remember it’s a one-way upgrade, there is no un-do The upgrade does not relay out the volume, so following an upgrade may not realize many of the improvements available in VMFS 5. If this is a concern, consider creating a new VMFS 5 volume from scratch and using storage vmotion to migrate the VMs to this volume.
- To help address the VM upgrade challenge, vSphere 5.0 formally extended the support matrix for VMs running on ESXi 5.0. ESXi 5.0 supports VMs running vHW 4, 7, and 8. In addition vSphere 5.0 supports VMs running VMware Tools 4.x as well as VMware Tools 5.0. With this extended support matrix you can continue to run older VMs in a fully tested and supported configuration w/out feeling pressure to always upgrade just to keep up with an ever increasing version number. VM upgrades are only required when necessary to benefit from the newer features and capabilities. In performing fewer upgrades there should be fewer VM reboots, which results in less overall VM downtime. vSphere 5.1 and 5.5 continue to extend the support matrix to include the latest version of VMware Tools and the newest virtual hardware version, which has is now referred to as VM “compatibility”, which we will discuss next.
- This slides discusses upgrading tools and shows the supported versions for both vSphere 4.x and 5.x. Note that VMware Tools 5.x is backward compatible with ESX/ESXi 4.x
- To summarize when upgrading VMFS volumes: Wait until all hosts are running ESXi 5.x Remember it’s a one-way upgrade, there is no un-do The upgrade does not relay out the volume, so following an upgrade may not realize many of the improvements available in VMFS 5. If this is a concern, consider creating a new VMFS 5 volume from scratch and using storage vmotion to migrate the VMs to this volume.
- Speaker notes: There are a number of considerations when upgrading an already existing VMFS-3 to VMFS-5. These considerations are listed here. VMFS-5 upgraded from VMFS-3 continues to have a file limit of 30700 rather than new file limit of 130689 for newly created VMFS-5.. - VMFS-5 upgraded from VMFS-3 continues to use previous file block size which may not be new unified 1MB file block size. - VMFS-5 upgraded from VMFS-3 continues to use 64KB sub-blocks and not new 8K sub-blocks. - VMFS-5 upgraded from VMFS-3 continues to use MBR; when VMFS5 is grown above 2TB, it automatically switches from MBR to GPT (GUID Partition Table). - VMFS-5 upgraded from VMFS-3 continue to have their partition located on sector 128; newly created VMFS5 partitions will have their partition starting at sector 2048. My understanding is that these statements are also true about upgraded VMFS-5. - Upgraded VMFS-5 can use the new 1K small-files feature. - Upgraded VMFS-5 can be grown to 64TB. - Upgrade VMFS-5 can support physical pass-thru RDMs of 64TB.
- To summarize when upgrading VMFS volumes: Wait until all hosts are running ESXi 5.x Remember it’s a one-way upgrade, there is no un-do The upgrade does not relay out the volume, so following an upgrade may not realize many of the improvements available in VMFS 5. If this is a concern, consider creating a new VMFS 5 volume from scratch and using storage vmotion to migrate the VMs to this volume.
- Before jumping into the details of the ESXi upgrade process, it’s important to understand the big picture and to know where the interdependencies are. Here we see the vSphere upgrade path, note that There are five basic phases to upgrading vSphere. (four if you don’t use VUM) Always upgrade vCenter Server first Each phase can be done independent of the other, and spaced out over time. As you progress through each phase, you can only roll back by restoring from a backup taken prior to starting the phase. In this presentation we will focus on Phases 3, 4 and 5. Phase 1 is being covered in a separate breakout session.
- Dependent on environmental variables: PowerOn/Off ratio, Cluster load, etc. Results not final, as we are still working on features. Talk about 5.5 U3 General Host Evacuation. Not necessarily upgrades. "I just saw the VM's zip by so fast. This used to take hours. This is such a time saver, and will help everyone! …" - VMware IT team
- Seamless integration with VCSA & WebClient Significantly reduce customer OPEX with API and faster upgrades Significantly reduced time to upgrade a cluster of ESXi hosts
- Seamless integration with VCSA & WebClient Significantly reduce customer OPEX with API and faster upgrades Significantly reduced time to upgrade a cluster of ESXi hosts
- Before you upgrade consult the documentation. Particularly the release notes and upgrade process. Watch for things that are different. Don’t assume that because your hardware worked with the prior version it will work with the current version. Do your due diligence and verify that your hardware is listed in the compatibility guide. Know what versions of software you are running and verify interoperability with the new software before upgrading. You may need to coordinate the upgrade of other software components at the same time you upgrade vSphere. For example, VUM, View, Horizon Suite, vCD, etc.