vSphere 5

I've recorded a video which will show you the new vSphere 5 iSCSI UI support and some other usability improvements. In vSphere 5 you'll have the ability to configure dependent hardware iSCSI and software iSCSI adapters along with the network configurations and port binding in a single dialog box using the vSphere Client. Full SDK access is also available for these configurations.

If you use the software or dependent hardware iSCSI adapters, you must configure connections for the traffic between the iSCSI component and the physical network adapters. Configuring the network connection involves creating a virtual VMkernel interface for each physical network adapter and associating the interface with an appropriate iSCSI adapter.

If your host has more than one physical network adapter for software and dependent hardware iSCSI, use the adapters for multipathing. You can connect the software iSCSI adapter with any physical NICs available on your host. The dependent iSCSI adapters can be connected only with their own physical NICs.

The vSphere Web Client, the Next-generation browser-based vSphere Client. A browser-based, fully-extensible, platform-independent implementation of the vSphere Client based on Adobe Flex. The vSphere 5.0 release includes both the new browser-based client and the Windows-based client available in prior releases. In this release, the browser-based client includes a subset of the functionality available in the Windows-based client, primarily related to inventory display and virtual machine deployment and configuration.

In this video I’ll show you how to log in to vCenter Server using the vSphere Web Client and manage your vSphere inventory. Before you can start to use the Web Client you first have to verify that the vCenter Server system is registered with the client. Just open a Web browser and enter the URL for the vSphere Web Client: http://server_name:8443/vsphere-client

The vSphere Web Client has improved immense comparing to the old Web Access interface and is completely rewritten in Adobe’s Flex. It’s supported on the following browsers:
- Microsoft Internet Explorer 7 and 8
- Mozilla Firefox 3.5 and 3.6

To deploy virtual machines in the vCenter Server inventory, you can create a virtual machine or clone an existing virtual machine. It’s also possible to deploy a Virtual Machine from a Template with the vSphere Web Client. Deploying a virtual machine from a template creates a virtual machine that is a copy of the template. The new virtual machine has the virtual hardware, installed software, and other properties that are configured for the template.

USB devices attached to the client computer running the vSphere Web Client or the vSphere Client can be connected to a virtual machine and accessed within it.

 What's New in VMware vSphere 5.0 Storage

This paper focuses on the storage-specific features and enhancements that are available in vSphere 5.0 and provides an overview of how they optimize storage utilization, ease monitoring, and increase operational efficiency. Wherever possible, VMware will also provide use cases and requirements that might apply to these new functions.

 What's New in VMware vSphere 5.0 Performance

VMware vSphere 5.0, the best VMware solution for building cloud infrastructures, pushes further ahead in performance and scalability. vSphere 5.0 enables higher consolidation ratios with unequaled performance. It supports the build-out of private and hybrid clouds at even lower operational costs than before. This paper outlines many of these performance enhancements.

 What's New in VMware vSphere 5.0 Networking

With the release of VMware vSphere 5.0, VMware brings a number of powerful new features and enhancements to the networking capabilities of the vSphere platform. These new network capabilities enable customers to run business-critical applications with confidence and provide the flexibility to enable customers to respond to business needs more rapidly. All the networking capabilities discussed in this document are available only with the VMware vSphere Distributed Switch.

 What's New in VMware vSphere 5.0 Availability

VMware provides several features that can be leveraged to increase the availability of a virtualized environment. This paper presents these features as they apply to availability of the applications, the infrastructure, and the management platform.

 What's New in VMware vCloud Director 1.5 Technical Whitepaper

VMware vCloud Director is a software solution that enables enterprises and service providers to build clouds delivering Infrastructure-as-a-Service (IaaS), giving end users the agility they demand, and giving IT the efficiency they require. Only VMware vCloud Director offers the cloud without compromise—the ability to run an efficient cloud securely within a datacenter, and the option to bridge to an ecosystem of over 3,000 service-provider partners.

 What's New in VMware vCenter Site Recovery Manager 5.0 Technical Whitepaper

VMware vCenter Site Recovery Manager is the premier tool to enable you to build, manage and execute reliable disaster recovery plans for your virtual environment. Taking full advantage of the encapsulation and isolation of virtual machines, Site Recovery Manager enables simplified automation of disaster recovery. It helps meet recovery time objectives, reduces costs traditionally associated with business continuance plans and achieves low-risk and predictable results for recovery of a virtual environment. In this paper, we will provide an overview of the new capabilities of Site Recovery Manager 5.0.

 What's New in VMware Data Recovery 2.0 Technical Whitepaper

VMware Data Recovery 2.0 is the premier tool to enable quick and simple backup, storage, and recovery of virtual machines and files within the virtual environment. With the release of version 2.0, VMware has expanded the capabilities of VMware Data Recovery in the virtual environment to attain quicker and more reliable backups with better levels of integration with VMware vCenter Server and new manageability options. This paper presents an overview of the new capabilities of VMware Data Recovery 2.0.

 VMware vSphere Storage Appliance Technical Whitepaper

In VMware vSphere 5.0, VMware is releasing a new software storage appliance to the market called the vSphere Storage Appliance. This appliance provides an alternative shared storage solution for small-to-medium business customers who might not be in a position to purchase a SAN or NAS array for their virtual infrastructure. Without shared storage configured in a vSphere environment, customers have not been able to exploit the unique features available in vSphere 5.0, such as vSphere High Availability, vSphere vMotion, and vSphere Distributed Resource Scheduler. The VSA is designed to provide shared storage for everyone. This paper presents an overview of the VSA architecture, deployment of a VSA storage cluster, and basic monitoring and managing.

 What's New in VMware vSphere 5.0 Platform

VMware vSphere 5.0 introduces many improvements and new features to extend the benefits and capabilities of vSphere 4.1. These advancements build on the core capacities in vSphere to provide improved scalability; better performance; and easier provisioning, monitoring and troubleshooting. This paper focuses on the these new features and enhancements.

So what’s the fuzz about this new vSphere 5 Storage DRS feature? This feature delivers the DRS benefits of resource aggregation, automated initial placement, and bottleneck avoidance to storage. You can group and manage similar datastores as a single load-balanced storage resource called a datastore cluster. Storage DRS makes VMDK placement and migration recommendations to avoid I/O and space utilization bottlenecks on the datastores in the cluster. Storage DRS takes care of the initial placement of virtual machines and VMDK files. This placement is based on Space and I/O capacity. Storage DRS will select the best datastore to place this virtual machine or virtual disk in the selected Datastore Cluster. When Storage DRS is set to fully automatic, it will do automated load balancing actions. Of course this can be configured as manual as well and that is actually the default today. Load balancing again is based on space and I/O capacity. If and when required Storage DRS will make recommendations based space and I/O capacity. It will however only do this when a specific threshold is reached. I’ve recorded a video which will show you how to:

- Configure a Datastore Cluster
- Set Storage DRS Automation Level
- Set Storage DRS Runtime Rules
- Create a Storage DRS Scheduled Task
- Using Storage DRS Rules
- Edit Virtual Machine Settings for a Datastore Cluster
- Apply Storage DRS Recommendations
- Add Storage to a Datastore Cluster



A datastore cluster is a collection of datastores aggregated into a single unit of consumption for an administrators. When a datastore cluster is created, Storage DRS can manage the storage resources comparable to how DRS manages compute resources in a cluster.  As with a cluster of hosts, a datastore clusters is used to aggregate storage resources, enabling smart and rapid placement of new virtual machines and virtual disk drives and load balancing of existing workloads. When you create a VM you will be able to select a Datastore Cluster as opposed to individual datastores. Storage DRS provides initial placement recommendations to datastores in a Storage DRS-enabled datastore cluster based on I/O and space capacity.

During the provisioning of a virtual machine, a datastore cluster can be selected as the target destination for this virtual machine or virtual machine disk after which a recommendation for initial placement is done based on I/O and space capacity. Initial Placement in a manual provisioning process has proven to be very complex in most environments and as such important provisioning factors like current I/O load or space utilization are often ignored. Storage DRS ensures initial placement recommendations are made in accordance with space constraints and with respect to the goals of space and I/O load balancing. Although people are really excited about automated load balancing, it is Initial Placement where most people will start off with and where most people will benefit from the most as it will reduce operational overhead associated with the provisioning of virtual machines.

Ongoing balancing recommendations are made when one or more datastores in a datastore cluster exceeds the user-configurable space utilization or I/O latency thresholds. These thresholds are typically defined during the configuration of the datastore cluster.  Storage DRS utilizes vCenter Server’s datastore utilization reporting mechanism to make recommendations whenever the configured utilized space threshold is exceeded. I/O load is evaluated by default every 8 hours currently with a default latency threshold of 15ms.  Only when this I/O latency threshold is exceeded Storage DRS will calculate all possible moves to balance the load accordingly while considering the cost and the benefit of the migration. If the benefit doesn’t last for at least 24 hours, Storage DRS will not make the recommendation.

With the release of vSphere version 5.0, VMware will also offer two new training courses. These new training courses are still in beta and will be released when vSphere 5.0 becomes general available. The two day “VMware vSphere: What's New [V5.0]” is aimed at current vSphere 4 administrators and the VMware vSphere: Install, Configure, Manage [V5.0] is the full five day course. VMware Certified Professional on vSphere 5 VCP5 certification is available at the end of August, more information can be found at vue.com (VCP510). There are different paths to VCP5 certification based on your background. Choose your path and complete the three core validation components:

1.Attend a qualifying VMware authorized course.Already a VCP4? There is no course requirement until February 29, 2012.

2.Gain hands-on experience with VMware vSphere 5.

3.Pass the VCP5 Exam.

VCP5 Exam Blueprint

At the 25th and 26th of August I'll deliver the vSphere 5 What's New training GK Nieuwegein - http://www.globalknowledge.nl/cursussen/vmware/virtualisation/vmwn.html

Ik geef een Nederlandstalige vSphere 5 ICM training bij Global Knowledge in Nieuwegein van 19 sep t/m 23 sep http://bit.ly/qZHkku

VMware vSphere: What's New [V5.0]

This hands-on training course explores new features in VMware vCenter™ Server 5.0 and VMware® ESXi™ 5.0. Topics include VMware vSphere® 5 installation and how to upgrade from vSphere 4.x to vSphere 5.0. vSphere 5.0 is the first version of vSphere to include only the ESXi hypervisor.

Objectives

• List and describe key enhancements in vSphere 5.0
• Upgrade a deployment from vSphere 4.x to vSphere 5.0
• Use Image Builder to modify and export an image profile as part of Auto Deploy
• Use Auto Deploy to Install a stateless ESXi host
• Manage a version 8 virtual machine with the next-generation Web-based VMware vSphere Client
• List and describe key networking enhancements, including the ESXi firewall and new features in vNetwork distributed switches
• Upgrade and manage a VMware vSphere VMFS5 datastore
• Understand and configure policy-driven storage management
• Create a datastore cluster and configure Storage DRS
• Configure a VMware High Availability cluster based on the new Fault Domain Manager agents
• Use the Linux-based VMware vCenter Server Appliance
  

VMware vSphere: Install, Configure, Manage [V5.0]

This hands-on training course explores installation, configuration, and management of VMware vSphere®, which consists of VMware ESXi™ and VMware vCenter™ Server. The course is based on ESXi 5.0 and vCenter Server 5.0. Completion of this course satisfies the prerequisite for taking the VMware® Certified Professional 5 exam.

Objectives

• Install and configure ESXi
• Install and configure vCenter Server components
• Configure and manage ESXi networking and storage using vCenter Server
• Deploy, manage, and migrate virtual machines
• Manage user access to the VMware infrastructure
• Use vCenter Server to monitor resource usage
• Use vCenter Server to increase scalability
• Use VMware vCenter Update Manager to apply ESXi patches
• Use vCenter Server to manage higher availability and data protection

What’s New in VMware vSphere 5?

This video will show you how to install ESXi 5.0 on a drive with an existing ESX 4.1 installation and VMFS datastore present. ESXi 5.0 uses the same installer for fresh installations and upgrades. If the installer finds an existing ESX 4.x or ESXi 4.x installation, it allows you to performs an upgrade.

During this upgrade, the ESXi installer will offer several options for preserving or discarding existing ESX host settings and VMFS datastores. If an earlier version of ESX and VMFS was found by the installer, it will show you the selected storage device contains an installation of ESX and a VMFS datastore. You can choose whether to upgrade or install and overwrite the existing installation. You can also choose whether to preserve or overwrite the existing VMFS datastore. After upgrading from ESX  4.1 to ESXi 5.0, only the relevant settings will be migrated.

UEFI virtual BIOS. Virtual machines running on ESXi 5.0 can boot from and use the Unified Extended Firmware Interface (UEFI). When you create a new virtual machine on an ESXi 5.0 host you have the option to choose for virtual machine version 8. This new version brings a lot of extra (scalability) features but there’s one other interesting new feature. The Extensible Firmware Interface can be selected to replace the BIOS of a virtual machine. EFI is the successor of the traditional BIOS which is used since the introduction of the IBM PC back in 1981. If you want to host Apple Mac OS X 10.6 in a virtual machine, you need EFI. In this video I’ll show you how to get access to the EFI interface. I’ll also show you how you can get access to the pre-OS command line environment.

When you select a guest operating system, BIOS or Extensible Firmware Interface (EFI) is selected by default, depending on which firmware the operating system uses. Mac OS X Server guest operating systems support only EFI. If the operating system supports both BIOS and EFI, you can change the default before you install the guest operating system. Use the Virtual Machine Properties dialog box at the end of the creation process or after the virtual machine is created. The Firmware selection pane is on the Options tab under Advanced > Boot Options.

vSphere 5.0 also supports booting ESXi hosts from the Unified Extensible Firmware Interface (UEFI). With UEFI you can boot systems from hard drives, CD-ROM drives, or USB media. Booting over the network requires the legacy BIOS firmware and is not available with UEFI.

So what does Profile-Driven Storage try to achieve? Very simply - minimize the amount of time required to provision virtual machines. Provisioning virtual machines isn’t only just selecting a random datastore. You will need to know what the requirements are of the virtual machine and then select the appropriate volume to the best of your knowledge. Profile-Driven Storage tries to help with that by providing better insight into storage characteristics and allowing for custom-tags and linking virtual machines to profiles. vSphere Storage APIs for Storage Awareness is a new set of APIs which will enable vCenter to see the capabilities of the storage array LUNs/datastores, making it much easier to select the appropriate disk for virtual machine placement. Storage capabilities, such as RAID level, Thin or Thick Provisioned, Replication State and much more can now be made visible within vCenter. vSphere Storage APIs for Storage Awareness eliminates the need for maintaining massive spreadsheets detailing the storage capabilities of each LUN needed to guarantee the correct SLA to virtual machines. It helps SDRS make a decision about where to Storage vMotion a VM too, because if two datastore are backed by the same set of spindles, then it doesn’t make sense to move the VM to the other datastore.

With Storage Awareness APIs, storage vendors can provide vSphere with information about the storage environment. It enables tighter integration between storage and the virtual infrastructure. Information about storage health status, configuration info, capacity and thin provisioning info etc For the first time we have an end to end story, i.e. storage array informs VASA storage provider of capabilities & then the storage provider informs vCenter, so now users can see storage array capabilities from vSphere client. Through the new VM Storage Profile-Driven Storageles, these storage capabilities can then be displayed in vCenter to assist administrators in choosing the right storage in terms of space, performance and SLA requirements. This information enables the administrator to take the appropriate actions based on health & usage information.

Currently we identify the requirements of the virtual machine, try to find the optimal datastore based on the requirements and create the virtual machine or disk. In some cases customers even periodically check if VMs are compliant but in many cases this is neglected. Storage DRS only solves that problem partly. We will need to manually identify the correct datastore cluster, and even when grouping datastores into a datastore cluster, we need to manually verify if all LUNs are “alike”. When using Profile-Driven Storage and Storage DRS together, these problems are solved. A datastore cluster can be created based on the characteristics provided through VASA or the custom tags. When deploying virtual machines, a storage profile can be selected ensuring that the virtual will be on compliant storage.

VMware HA clusters enable a collection of ESXi hosts to work together so that, as a group, they provide higher levels of availability for virtual machines than each ESXi host could provide individually. When you plan the creation and usage of a new VMware HA cluster, the options you select affect the way that cluster responds to failures of hosts or virtual machines.

Before creating a VMware HA cluster, you should be aware of how VMware HA identifies host failures and isolation and responds to these situations. You also should know how admission control works so that you can choose the policy that best fits your failover needs. After a cluster has been established, you can customize its behavior with advanced attributes and optimize its performance by following recommended best practices.

VMware HA provides high availability for virtual machines by pooling them and the hosts they reside on into a cluster. Hosts in the cluster are monitored and in the event of a failure, the virtual machines on a failed host are restarted on alternate hosts.

When you create a VMware HA cluster, a single host is chosen as the master host to communicate with vCenter Server and to monitor the state of the other, slave, hosts and their virtual machines. Different types of host failures are possible and must be detected and appropriately dealt with. To do this, the master host must distinguish between a failed host and one that is in a network partition. Datastore heartbeating is used to do this.

Auto Deploy is a new method for provisioning ESXi hosts in vSphere 5.0.  At a high level the ESXi host boots over the network (using PXE/gPXE), contacts the Auto Deploy Server which loads ESXi into the hosts memory.  After loading the ESXi image the Auto Deploy Server coordinates with vCenter Server to configure the host (using Host Profiles and Answer Files (answer files are new in 5.0).  Auto Deploy eliminates the need for a dedicated boot device, enables rapid deployment for many hosts, and also simplifies ESXi host management by eliminating the need to maintain a separate “boot image” for each host.

Image profiles and VIBs are available in software depots from VMware or from VMware partners, and managed using the Image Builder PowerCLI. You can use software depots, image profiles, and software packages (VIBs) to specify the software you want to use during installation or upgrade of an ESXi host. Understanding how depots, profiles, and VIBs are structured and where you can use them is a prerequisite for in-memory installation of a custom ESXi ISO, for provisioning ESXi hosts using VMware Auto Deploy, and for some custom upgrade operations.

VIB A VIB is an ESXi software package. VMware and its partners package solutions, drivers, CIM providers, and applications that extend the ESXi platform as VIBs.
VIBs can be used to create and customize ISO images or installed asynchronously onto ESXi hosts. VIBs are available from software depots.

Image Profile An image profile defines an ESXi image and consists of VIBs (software packages). An image profile always includes a base VIB, and might include
additional VIBs. You examine and define an image profile using the Image Builder PowerCLI.