VCenter/ESX Setup

For the purposes of this demo, VCenter it’s self is not required. All you will need is a standalone ESX server. To prevent Contractor from DHCPing your other systems, you will want to create a private network to build contractor’s targets in. This demo assumes it will be For our example name it “internal”, if you choose to name it something else, make sure that change is reflected in the name of the address block that will be created later.

After you create the network/port group, add a second interface to the contractor VM on this new network, and assign the ip to that interface.

In the /etc/subcontractor.conf file under the dhcpd section, set the listen_interface to the name of the newly created interface.

VCenter GuestIDs

By default, the resources blueprint for CentOS Assume you are using VCenter 6.7 or newer. If you are using and older version of VCenter you will need to:

cd resources
make oldvcenter
make respkg
mv *.respkg ..
cd ..

Otherwise your VCenter/ESX will give you an invalidProperty = ‘configSpec.guestId’ error when you build CentOS VMs.

Now you will need to install python3-pyvmomi:

sudo apt install -y python3-pyvmomi

return to Setup