Github user nvazquez commented on the pull request:
https://github.com/apache/cloudstack/pull/935#issuecomment-150012697
### VMware vSphere API version from 5.1 to 5.5:
Since vSphere API version 5.5,
[OpaqueNetworks](https://www.vmware.com/support/developer/converter-sdk/conv55_apireference/vim.OpaqueNetwork.html)
are introduced.
Its description says:
> This interface defines an opaque network, in the sense that the detail
and configuration of the network is unknown to vShpere and is managed by a
management plane outside of vSphere. However, the identifier and name of these
networks is made available to vSphere so that host and virtual machine virtual
ethernet device can connect to them.
In order to connect a vm's virtual ethernet device to the proper opaque
network when deploying a vm into a NSX managed network, we first need to look
for a particular opaque network on hosts. This opaque network's id has to be
**"br-int"** and its type **"nsx.network"**.
Since vSphere API version 5.5
[HostNetworkInfo](https://www.vmware.com/support/developer/converter-sdk/conv55_apireference/vim.host.NetworkInfo.html#opaqueNetwork)
introduces a list of available opaque networks for each host.
If NSX API version >= 4.2 we look for a
[OpaqueNetworkInfo](https://www.vmware.com/support/developer/converter-sdk/conv55_apireference/vim.host.OpaqueNetworkInfo.html)
which satisfies:
* opaqueNetworkId = "br-int"
* opaqueNetworkType = "nsx.netork"
If that opaque network is found, then we need to attach vm's NIC to a
virtual ethernet device which support this, so we use
[VirtualEthernetCardOpaqueNetworkBackingInfo](https://www.vmware.com/support/developer/converter-sdk/conv55_apireference/vim.vm.device.VirtualEthernetCard.OpaqueNetworkBackingInfo.html)
setting:
* opaqueNetworkId = "br-int"
* opaqueNetworkType = "nsx.netork"
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
