Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 18 Nov 2015 12:14:11 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12905288.1444935047000.105634.1447848851618@Atlassian.JIRA>
In-Reply-To: <JIRA.12905288.1444935047000@Atlassian.JIRA>
References: <JIRA.12905288.1444935047000@Atlassian.JIRA>
 <JIRA.12905288.1444935047327@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-8956) NSX/Nicira Plugin does not
 support NSX v4.2.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8956?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=
=3D15010866#comment-15010866 ]=20

ASF subversion and git services commented on CLOUDSTACK-8956:
-------------------------------------------------------------

Commit e1d1a403257d94790bb44180b4584ed967d73fec in cloudstack's branch refs=
/heads/master from nvazquez
[ https://git-wip-us.apache.org/repos/asf?p=3Dcloudstack.git;h=3De1d1a40 ]

CLOUDSTACK-8956: Deploy VM on NSX managed network changes if NSX Api Versio=
n >=3D 4.2: has to connect to "br-int" of "nsx.network" type


> NSX/Nicira Plugin does not support NSX v4.2.1
> ---------------------------------------------
>
>                 Key: CLOUDSTACK-8956
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-895=
6
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>          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
>
>
> h3. 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 plu=
gin 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 c=
urrent version of NiciraNVP plugin doesn=E2=80=99t 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 n=
etwork changes:
> * Current mode. A portgroup =3D UUID of CS VM NIC is created on a local s=
tandard switch of the Hypervisor where VM is starting. VM nic is attached t=
o that port group.
> * New mode. No additional port group is created on a HW. No port group cl=
eanup is needed after VM/NIC is destroyed. VM is attached to 1st port group=
 having the following attributes:
> ** opaqueNetworkId string "br-int=E2=80=9D
> ** opaqueNetworkType string "nsx.network"
> If portgroup with such attributes is not found a deployment should fail w=
ith exception.
> h3. VMware vSphere API version from 5.1 to 5.5:
> Since vSphere API version 5.5, [OpaqueNetworks|https://www.vmware.com/sup=
port/developer/converter-sdk/conv55_apireference/vim.OpaqueNetwork.html] ar=
e introduced.=20
> Its description says:=20
> bq. This interface defines an opaque network, in the sense that the detai=
l 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 machin=
e virtual ethernet device can connect to them.
> In order to connect a vm's virtual ethernet device to the proper opaque n=
etwork when deploying a vm into a NSX managed network, we first need to loo=
k 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/sup=
port/developer/converter-sdk/conv55_apireference/vim.host.NetworkInfo.html#=
opaqueNetwork] introduces a list of available opaque networks for each host=
.=20
> If NSX API version >=3D 4.2 we look for a [OpaqueNetworkInfo|https://www.=
vmware.com/support/developer/converter-sdk/conv55_apireference/vim.host.Opa=
queNetworkInfo.html] which satisfies:
> * opaqueNetworkId =3D "br-int"
> * opaqueNetworkType =3D "nsx.netork"
> If that opaque network is found, then we need to attach vm's NIC to a vir=
tual ethernet device which support this, so we use [VirtualEthernetCardOpaq=
ueNetworkBackingInfo|https://www.vmware.com/support/developer/converter-sdk=
/conv55_apireference/vim.vm.device.VirtualEthernetCard.OpaqueNetworkBacking=
Info.html] setting:
> * opaqueNetworkId =3D "br-int"
> * opaqueNetworkType =3D "nsx.netork"


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)