You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Nicolas Vazquez (JIRA)" <ji...@apache.org> on 2015/10/16 22:15:05 UTC
[jira] [Updated] (CLOUDSTACK-8956) NSX/Nicira Plugin does not
support NSX v4.2.1
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Vazquez updated CLOUDSTACK-8956:
----------------------------------------
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 VIM jar version change from version 5.1 to 5.5 to get opaqueNetworks from HostNetworkInfo
-Modified deps/install-non-oss.sh to include vmware vim 5.5
was:
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 VIM jar version change from version 5.1 to 5.5 to get opaqueNetworks from HostNetworkInfo
-Modified deps/install-non-oss.sh to include vmware vim 5.5
> NSX/Nicira Plugin does not support NSX v4.2.1
> ---------------------------------------------
>
> Key: CLOUDSTACK-8956
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8956
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: VMware
> Affects Versions: 4.4.0, 4.5.0, 4.4.1, 4.4.2, 4.4.3, 4.5.1, 4.4.4
> Environment: OS: RHEL 6.6
> Reporter: Nicolas Vazquez
> Fix For: 4.5.1, 4.6.0
>
>
> 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 VIM jar version change from version 5.1 to 5.5 to get opaqueNetworks from HostNetworkInfo
> -Modified deps/install-non-oss.sh to include vmware vim 5.5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)