HP ProLiant s6500 Deploying and updating VMware vSphere 5.0 on ProLiant server - Page 4
SAN configuration, HP custom image updates, Auto Deploy and ESXi 5.0, VMware ESXi Image Builder - installation guide
View all HP ProLiant s6500 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 4 highlights
If you use the VMware base image, the HP WBEM providers are not included, resulting in extra installation steps to install them separately. SAN configuration One common implementation for ESXi is a boot from SAN configuration. Installing ESXi in this configuration means that the enabling device drivers must be available in the ESXi installation images. To simplify installing a boot from SAN configuration on ProLiant servers, we include the required drivers (FC, FCoE, and iSCSI) for both embedded and supported optional devices that provide SAN connectivity. The result is a seamless process for setting up a boot from SAN ESXi environment on ProLiant servers. HP custom image updates We release new custom ESXi images whenever there is a need to update any critical components of the image. VMware typically releases major, minor, or updated releases of ESXi several times a year. HP does not deliver a new custom image based on VMware patches or hot fixes. When we introduce a new server that needs a new or updated networking driver, we release a custom ESXi image that includes the drivers. You can get HP custom ESXi images from the HP Software Depot website: https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=HPVM09 From this site, you can also download your required version of ESXi. Auto Deploy and ESXi 5.0 The new vSphere 5.0 Auto Deploy feature lets you deploy ESXi 5.0 on one or more servers directly into system memory each time they boot. This means you are not required to install ESXi 5.0 into a server local or remote storage. Using Auto Deploy, you can specify the image profile to deploy and the hosts to provision. An image profile specifies the base image and additional driver VIBs, HP VIBs, and other third-party VIBs to deploy to the host. Auto Deploy uses a PXE boot infrastructure along with vSphere host profiles to provision and customize hosts. You can deploy HP management components as part of the Auto Deploy option by including them in the image profile, which results in a fully managed HP server operating in stateless mode. The HP Online Depot offers HP-specific components for use with vSphere 5.0 Auto Deploy. Auto Deploy uses the information in image profiles and host profiles to provision the ESXi host. Image profiles specify the software to load on the host and the host profile specifies the host configuration information. The administrator defines rules that map hosts to image profiles and host profiles. You can install the auto deploy tools on the vCenter server. The VMware Linux based vCenter appliance also includes them. For more information about using Auto Deploy, see the vSphere Installation and Setup Guide at http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-installationsetup-guide.pdf. For more information about the VMware Linux based vCenter appliance, see http://vmwire.com/2011/07/15/vsphere-vcenter-server-linux-virtual-appliance-quick-start-guide/. VMware ESXi Image Builder VMware ESXi Image Builder lets you create a custom ISO, create or edit an image profile for auto deploy, or create an offline deposit .zip for VMware Update Manager (VUM). VMware Image Builder is an extension to Power Shell for Windows. 4