Renaming A VSwitch In VMWare ESXi
vmware/esxi-version: set to select-vendor, or to a preciseBootEnv that exists on the system (eg esxi_670u2-13006603_vmware),this is an enum type of curated an supported BootEnvs by RackN
Renaming a vSwitch in VMWare ESXi
vmware/esxi-version-vendor-map: this is a mapping of which BootEnv touse by default when a machine Vendor and Model has been automaticallyClassified - it allows for single workflows to address heterogeneouspools of hardware - see the Param documentation below for more details
Setting the vmware/esxi-version Param to select-vendor will enableautomatic selection of the ISO based on the Vendor and Model (if appropriate)of the hardware, dynamically. This pattern allows operators to have a poolof heterogenous hardware, and map VMware ESXi ISO versions to the vendors,allowing for appropriate custom vendor ISOs to be used for each hardwaretype.
This map is maintained in the vmware/esxi-version-vendor-map, which carriesa default set defined by RackN. Should you want to specify precise versionsto use, you can set this Param to a map structure of your choosing. Set thisdirectly on the Machine as a Param, or via Profiles that are added to themachine (including global, if appropriate).
The RackN VMware plugin also supports applying a patch version to the base installISO at installation time. The patching system relies on two separate sets ofmaps to specify where to find the Patches and related information (theesxi/patch-map, and the actual patch to install (via the vmware/esxi-version-vendor-mapparam).
There is a script that is distributed with the vmware plugin namedmake-esxi.sh. This script combines the previous two scripts capabilitiesin to a single tool. The previous scripts were make-esxi-bootenvs.sh andmake-esxi-content-pack.sh.
Remove all vmware/esxi-version Params from your Machines orprofiles. The naming structure of the BootEnvs has changed to bemore structured and predictable. This causes the Param enumstructure from the OLD versions to NOT BE COMPATIBLE with the new.
This param should not be manipulated directly the Vendor Map system usesit to set the selected vendor for the ESXi bootenv. This is subsequentlyused by the Patch system - if patches need to be applied - to insure thecorrect patch set is referenced in the vmware/esxi-version-vendor-map
If the operator specifies select-vendor then the latest Vendorspecific BootEnv / ISO combo will be used according to the Parammap vmware/esxi-version-vendor-map. The vendor versionrequires gohai-inventory to match DMI->System->Manufacturerappropriately.
This Param is used by setting the control Param vmware/esxi-version toselect-vendor. The template vmware-esxi-selector.tmpl will then usethis map to determine the best Vendor specific BootEnv/ISO to install on thesystem.
The operator can also choose to override this map Param with a set ofvalues specific to use requirements. However, the structure mustremain the same, and vendor Manufacturer information must be supportedin the vmware-esxi-selector.tmpl template.
This tasks calls the vmware-esxi-selector.tmpl which implements theautomatic ESXi install based on the hardware vendor of the machine(if vmware/esxi-version is set to select-vendor), and the mapof Param values (vmware/esxi-version-vendor-map).
You now get a summary screen, notice the "automatically create a default port group" is ticked, you can leave this as we will make use of this group. Click next to create the DvSwitch. After renaming the dvSwitch to "dvswitch-NIC2" and renaming the port group to "Private" (you can do this by right-clicking each item and selecting edit settings, then change the name at the top", you should have something like below