The element name and Description should also indicate that this is a CPU. The first item in this section is usually the CPU. Each hardware component is listed in the VirtualHardwareSection right after the System lines. Feel free to edit the capacity and diskID to match the size of disks you'd like to deploy. Your Disk Section should now look as follows.
In order to to this, add in the following lines to the Disk Section Since the ESXi host image is already on the first VMDK, we will leave that in place and add in a few blank disk options. Keep in mind that if you define more than 13 options, you may see some odd graphical glitches while scrolling through the options in the vCenter GUI, so if you to avoid this, keep the deployment options to a max of 13. You can add more deployment options, take some away, and edit any of the ids, labels, and descriptions. Placement of Deployment Options Section below It's not required, but it keeps things tidy.
The strings section allows us to create longer labels in a separate section of the file, keeping the main Deployment Options section cleaner. I've chosen to label these based upon the VM configuration (vCPU-RAM-DiskSize-NICs) to make identifying them across the OVF file easier. You'll want to set a unique label and description too as this is what is displayed in the GUI during deployment. Each configuration item consists of an id, description, and label. This is where we define all of the deployment options we want our OVA to have. Small Disks (8GB and 100GB).Ģ vCPUs and 8GB of RAM.
I put this immediately following the DiskSection. The first thing we need to do is paste in our Deployment Options section. I will be using Atom for this guide but vi, emacs, notepad, and sublime are all great alternatives. Using the OVF file that you have extracted from the OVA file (Not sure how to do this step? Learn about it here), open this up in a text editor of your choice. This guide will expand upon this and take an even deeper look into editing OVF files.
William Lam has a great write-up on this topic.
0 kommentar(er)
