Uploaded image for project: 'CloudStack'
  1. CloudStack
  2. CLOUDSTACK-8956

NSX/Nicira Plugin does not support NSX v4.2.1

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 4.4.0, 4.5.0, 4.4.1, 4.4.2, 4.4.3, 4.5.1, 4.4.4
    • 4.5.1, 4.6.1
    • VMware
    • Security Level: Public (Anyone can view this level - this is the default.)
    • None
    • OS: RHEL 6.6
    • Patch

    Description

      Description of the problem:

      Prior to version 4.2. Nicira/VmWare NSX used a variation of Open vSwitch as means of integrating SDN into hypervisor layer. Cloudstack NiciraNVP plugin was written to support OVS as a bridge to NSX.
      In version 4.2 VMware introduced NSX vSwitch as a replacement for OVS in ESX hypervisors. It is a fork of distributed vSwitch leveraging one of the recent features of ESX called opaque networks. Because of that change the current version of NiciraNVP plugin doesn’t support versions of NSX-MH above 4.2 specifically in Vsphere environment. Proposed fix will analyze a version of NVP/NSX API and use proper support for ESX hypervisors.

      vSphere hypervisor mode operations when NV is deployed onto NSX managed network changes:

      • Current mode. A portgroup = UUID of CS VM NIC is created on a local standard switch of the Hypervisor where VM is starting. VM nic is attached to that port group.
      • New mode. No additional port group is created on a HW. No port group cleanup is needed after VM/NIC is destroyed. VM is attached to 1st port group having the following attributes:
        • opaqueNetworkId string "br-int”
        • opaqueNetworkType string "nsx.network"

      If portgroup with such attributes is not found a deployment should fail with exception.

      VMware vSphere API version from 5.1 to 5.5:

      Since vSphere API version 5.5, OpaqueNetworks 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 introduces a list of available opaque networks for each host.
      If NSX API version >= 4.2 we look for a OpaqueNetworkInfo 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 setting:

      • opaqueNetworkId = "br-int"
      • opaqueNetworkType = "nsx.netork"

      Attachments

        Activity

          People

            Unassigned Unassigned
            nicolas.vazquez Nicolas Vazquez
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: