Getting Started with VMWARE VSPHERE

First, Autodeploy

1. Install the Autodeploy component on a server that already has vcentserver. Enter the user name and password for Vcentserver to verify.

2. Install the WMware POWERCLI command line management component. There is no dependency on the installed server and no restrictions are required.

3. Configure the Install Tftpserver component on the server. and runs normally. Under the TFTP service root directory. Add a boot boot file. (Launch the boot file and use the vsphere client component to log in to Vcentserver under the Autodeploy project.) TFTP file content on click Download Save to local)

4, configuring DHCP services, typically with Windows Server's own DHCP service. Note the 66th item (next-server) of the service that configures DHCP. The content indicates the IP address of the TFTP server or, in conjunction with the DNS service, indicates the preparation name of the TFTP server. Note the 67th item (BOOT-FILENAME) that configures the DHCP service indicates the name of the file that the boot server needs to boot under the TFTP root directory. This is usually: undionly.kpxe.vmw-hardwired

5, create Autodeploy boot image profile, can also be downloaded from the WMware official. The name is generally vmware-esxi-5.5.0-xxxxxx-depot.zip or update-from-esxi5.5-5.5_update-xxxx.zip

6. Use the POWERCLI command line tool just installed. Load the configuration image file. Before loading the image, change the permissions on the POWERCLI command line first. The specific command is: Set-executionpolicy unrestricted. and enter Y to agree to the change.

6.1 Command line login Vcenterserver server. Specific command: Connect-viserver-server 192.0.0.0-user admin-password xxxxxx

6.2 Add image files to Autodeploy repository after login. The command is: Add-esxsoftwaredepot d:\xxxxxx.zip

You can also add content on the network. Example: Add-esxsoftwaredepothttp://hostupdate.vmware.com/software/vum/production/main/vmw-depot-index.xml

6.3 Finally use the Get-esximageprofile command. Query the image list to determine if the configuration image file was added successfully.

7, you can clone the image that you just added to the offline library as your own custom image file to create a new image configuration file.

New-esximageprofile-cloneprofile "Esxi-5.5.0-xxxxx-standard"-name "My_custom_profile"

8. Export the new custom image file that you just cloned to your local hard drive, and generally modify and add the import again at any time later.

Export-esximageprofile-imageprofile "My_custom_profile"-exporttobundle-filepath "D:\ZIPfile-offline-depot.zip"

9. Establish the Deployment rules:

9.1: Execute command in currently logged in POWERCLI session: New-deployrule-name "Img_rule"-item "My_custom_profile"-pattern "Vendor=cisco", "ipv4= 10.1.1.225,10.1.1.250 "

This rule assigns the image profile My_custom_profile to all hosts that have a vendor string of "Cisco". and set their IP address to 10.1.1.225 or 10.1.1.250. Alternatively, you can specify an IP address range, such as 10.1.1.225-10.1.1.250 (a hyphen separates the IP address from the start and end range).

9.2: Next, create an immature rule to assign the ESXi host to a cluster of vcenterserver.

New-deployrule-name "Default_cluster"-item "Cluster-1"-allhosts

On the vcenterserver of the initial automatic deployment server, this rule is assigned to all hosts included in its cluster Cluster-1 (the automatic deployment server must be registered on a Vcenterserver instance).

9.3: Add these rules to a valid rule set.

Add-deployrule Img_rule

Add-deployrule Default_cluster

As soon as you add a deployment rule to a valid rule set, VSphere Autodeploy uploads the VIB to the automatic deployment server when necessary to meet the requirements of the defined rule.

10. Use the Get-deployruleset command to confirm that these rules have been added to the active rule set. You can start the hardware instance to start Autodeploy the automatic deployment process.

Questions:

First, the pattern project in the deployment rule. Which Vendor=cisco. So the question is: Is there a list in the Autodeploy service that specifies only the parameters for this option? such as Cisco such as HP. What if our device is not on this list? If this parameter can be set manually. So the question is how do we set this parameter on the hardware instance. It's in the BIOS. Or is it in the NIC information? or some of the equipment itself is fixed and cannot be modified. Wouldn't that greatly limit the flexibility of deployment?

Second, new-deployrule-name "Default_cluster"-item "Cluster-1"-allhosts where item item CLUSTER-1 Is this parameter the name of a data center or cluster under Vcenterserver management? (Tested, yes.) ）

Third, the relationship between the various components and data communication needs to be collated.

Getting Started with VMWARE VSPHERE