Mastering VMware vSphere 6. Marshall Nick
Чтение книги онлайн.
Читать онлайн книгу Mastering VMware vSphere 6 - Marshall Nick страница 17
Название: Mastering VMware vSphere 6
Автор: Marshall Nick
Издательство: John Wiley & Sons Limited
Жанр: Зарубежная образовательная литература
isbn: 9781118925164
isbn:
Auto deploy dependencies
This chapter deals with ESXi host installation methods; however, vSphere Auto Deploy is dependent on host profiles, a feature of VMware vCenter. More information about installing vCenter and configuring host profiles can be found in Chapter 3.
Once you’ve completed these five steps, you’re ready to start provisioning hosts with ESXi. When everything is configured and in place, the process looks something like this:
1. When the physical server boots, the server starts a PXE boot sequence. The DHCP server assigns an IP address to the host and provides the IP address of the TFTP server as well as a boot filename to download.
2. The host contacts the TFTP server and downloads the specified filename, which contains the gPXE boot file and a gPXE configuration file.
3. gPXE executes; this causes the host to make an HTTP boot request to the Auto Deploy server. This request includes information about the host, the host hardware, and host network information. This information is written to the server console when gPXE is executing, as you can see in Figure 2.7.
4. Based on the information passed to it from gPXE (the host information shown in Figure 2.7), the Auto Deploy server matches the server against a deployment rule and assigns the correct image profile. The Auto Deploy server then streams the assigned ESXi image across the network to the physical host.
Figure 2.7 Host information is echoed to the server console when it performs a network boot.
When the host has finished executing, you have a system running ESXi. The Auto Deploy server can also automatically join the ESXi host to vCenter Server and assign a host profile (which we’ll discuss in a bit more detail in Chapter 3) for further configuration. As you can see, this system potentially offers administrators tremendous flexibility and power.
Ready to get started with provisioning ESXi hosts using Auto Deploy? Let’s start with setting up the vSphere Auto Deploy server.
Finding the vSphere Auto Deploy Server
The vSphere Auto Deploy server is where the various ESXi image profiles are stored. The image profile is transferred from this server via HTTP to a physical host when it boots. The image profile is the actual ESXi image, and it consists of multiple vSphere Installation Bundle (VIB) files. VIBs are ESXi software packages; these could be drivers, Common Information Management (CIM) providers, or other applications that extend or enhance the ESXi platform. Both VMware and VMware’s partners could distribute software as VIBs.
The vSphere Auto Deploy service is installed but not enabled by default with vCenter Server. Previous versions of vSphere required a separate install of Auto Deploy.
1. Open up the vSphere Web Client (if you haven’t installed it yet, skip ahead to Chapter 3 and then come back) and connect to vCenter Server.
2. Navigate to vCenter Inventory Lists
You’ll see information about the registered Auto Deploy service. Figure 2.8 shows the Auto Deploy screen after we installed vCenter and enabled the Auto Deploy service.
Figure 2.8 This screen provides information about the Auto Deploy server that is registered with vCenter Server.
That’s it for the Auto Deploy server itself; once it’s been installed and is up and running, there’s very little additional work or configuration required, except configuring TFTP and DHCP on your network to support vSphere Auto Deploy. The next section provides an overview of the required configurations for TFTP and DHCP.
Configuring TFTP and DHCP for Auto Deploy
The procedures for configuring TFTP and DHCP will vary based on the specific TFTP and DHCP servers you are using on your network. For example, configuring the ISC DHCP server to support vSphere Auto Deploy is dramatically different from configuring the DHCP Server service provided with Windows Server. Therefore, we can provide only high-level information in the following section. Refer to your specific vendor’s documentation for details on how the configuration is carried out.
Configuring TFTP
For TFTP, you need only upload the appropriate TFTP boot files to the TFTP directory. The Download TFTP Boot Zip link shown in Figure 2.8 provides the necessary files. Simply download the zip file using that link, unzip the file, and place the contents of the unzipped file in the TFTP directory on the TFTP server.
Configuring DHCP
For DHCP, you need to specify two additional DHCP options:
• Option 66, referred to as next-server or as Boot Server Host Name, must specify the IP address of the TFTP server.
• Option 67, called boot-filename or Bootfile Name, should contain the value undionly.kpxe.vmw-hardwired.
If you want to identify hosts by IP address in the deployment rules, then you’ll need a way to ensure that the host gets the IP address you expect. You can certainly use DHCP reservations to accomplish this, if you like; just be sure that options 66 and 67 apply to the reservation as well.
Once you’ve configured TFTP and DHCP, you’re ready to PXE boot your server, but you still need to create the image profile to deploy ESXi.
Creating an Image Profile
The process for creating an image profile may seem counterintuitive at first; it did for me. Creating an image profile involves first adding at least one software depot. A software depot could be a directory structure of files and folders on an HTTP server, or (more commonly) it could be an offline depot in the form of a zip file. You can add multiple software depots.
Some software depots will already have one or more image profiles defined, and you can define additional image profiles (usually by cloning an existing image profile). You’ll then have the ability to add software packages (in the form of VIBs) to the image profile you’ve created. Once you’ve finished adding or removing software packages or drivers from the image profile, you can export the image profile (either to an ISO or as a zip file for use as an offline depot).
All image profile tasks are accomplished using PowerCLI, so you’ll need to ensure that you have a system with PowerCLI installed in order to perform these tasks. We’ll describe PowerCLI, along with other automation tools, in more detail in Chapter 14, “Automating VMware vSphere.” I’ll walk you through creating an image profile based on the ESXi 6.0 offline depot zip file available for downloading by registered customers.
Perform the following steps to create an image profile:
1. At a PowerCLI prompt, use the Connect-VIServer cmdlet to connect to vCenter Server.
2. Use the Add-EsxSoftwareDepot command to add the ESXi 6.0 offline depot file:
Add-EsxSoftwareDepot C: \vmware-ESXi-6.0-XXXXXX-depot.zip
3. Repeat СКАЧАТЬ