OK, so I think I've got a handle on what we need to do.
The OVA/OVFs on cloud-images.ubuntu.com specify a NIC using the "VM Network" network. We're not validating that, and not enabling you to override that. Moreover, there's absolutely no way it would work with a distributed port group.
So I'll look at doing the following:
- introduce a "network" config, via which users will be able to specify the name of the primary network to which each VM will be attached the primary network name to attach to each VM
- if "network" is unspecified, use "VM Network" if it exists; if it does not, but there is exactly one network available to the host/cluster, use that instead
- if there's no "VM Network", and no single network, we'll probably just return an error and require the user to make a choice by setting the network config
We'll need to check the type of network, and treat distributed port groups a little bit specially. I'm hoping to have this in a 2.2.3 release soon.
OK, so I think I've got a handle on what we need to do.
The OVA/OVFs on cloud-images. ubuntu. com specify a NIC using the "VM Network" network. We're not validating that, and not enabling you to override that. Moreover, there's absolutely no way it would work with a distributed port group.
So I'll look at doing the following:
- introduce a "network" config, via which users will be able to specify the name of the primary network to which each VM will be attached the primary network name to attach to each VM
- if "network" is unspecified, use "VM Network" if it exists; if it does not, but there is exactly one network available to the host/cluster, use that instead
- if there's no "VM Network", and no single network, we'll probably just return an error and require the user to make a choice by setting the network config
We'll need to check the type of network, and treat distributed port groups a little bit specially. I'm hoping to have this in a 2.2.3 release soon.