I should also note that I'm using a vlan network - the only type of network supported by the vmware_dvs driver - so there's no confusion about the type driver involved.
When vmware_dvs is configured, nova should receive a VIF type of 'dvs', but receives a 'unbound' value instead, which is the immediate cause of the error.
My setup is using the ml2 plugin, with both vmware_dvs and openvswitch mechanism drivers enabled. This is the ml2 section of my ml2_conf.ini:
[ml2] network_ types = vlan,vxlan,gre dvs,openvswitch ,l2population
type_drivers = vlan,vxlan,gre,flat
tenant_
mechanism_drivers = vmware_
extension_drivers = port_security
I should also note that I'm using a vlan network - the only type of network supported by the vmware_dvs driver - so there's no confusion about the type driver involved.
When vmware_dvs is configured, nova should receive a VIF type of 'dvs', but receives a 'unbound' value instead, which is the immediate cause of the error.