vsphere-bootorder-change

Migrate virtual NIC (vmk) from Standard vSwitch to Distributed vSwitch

This task is a nasty hack that runs Powershell against a vSphere service and modifies the Virtual Machine's boot order. Why does VMware have to make this so hard?

This Task has two modes for defining the Virtual machines to target:

• dynamic - all DRP based Cluster managed Virtual machines (default mode)
• list based - an explicit list defined by vsphere/virtual-machines

Notes for each mode are below.

Dynamic mode:

Must be run from the Cluster, and the Resource Broker must be defined as "broker/name" on the Cluster. Each Machine in the Cluster MUST have it's Cluster specific Profile attached to the Machine to identify it.

In the Dynamic Cluster mode, the Cluster must be set up correctly, with the Cluster defined as Cluster.Meta.machine-role set to cluster. The Cluster must have broker/name set directly or indirectly via Profiles, to determine the Resource Broker to operate against.

The Resource Broker must have the Broker Profile attached to it to extract the vSphere Node, User, and Password connection details.

Each Virtual Machine must also have the Cluster named Profile attached to the Machine to be able to identify that it belongs in the named Cluster. This is how the Machines target list is dynamically determined.

List Based mode:

The operator must specify the Virtual Machines to target in the string list type Param named vsphere/virtual-machines.

In addition, the connection details (vsphere service host, user, and password credentials) must be specified in teh vsphere/server, vsphere/user, and vsphere/password Params.

!!! note Requires that the task-library Content bundle be installed (in the Catalog) for the Powershell/PowerCLI dependency requirements if needed in the context that the Task is running.