Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Mon, 28 Dec 2015 10:22:50 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12914114.1447855556000.14763.1451298170467@Atlassian.JIRA>
In-Reply-To: <JIRA.12914114.1447855556000@Atlassian.JIRA>
References: <JIRA.12914114.1447855556000@Atlassian.JIRA>
 <JIRA.12914114.1447855556934@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-9074) Support shared networking in
 NiciraNVP Plugin
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

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

Commit 0b20ed4074484113973d8f447b8b8a79c778210d in cloudstack's branch refs=
/heads/master from [~nicolas.vazquez]
[ https://git-wip-us.apache.org/repos/asf?p=3Dcloudstack.git;h=3D0b20ed4 ]

CLOUDSTACK-9074: Add NetworkGuruAdditionalFunctions license


> Support shared networking in NiciraNVP Plugin
> ---------------------------------------------
>
>                 Key: CLOUDSTACK-9074
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-907=
4
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>    Affects Versions: 4.7.0
>            Reporter: Nicolas Vazquez
>             Fix For: 4.7.0
>
>
> h3. Introduction
> Currently NiciraNVP plugin supports only Isolated networking. In this mod=
e of operations networks are assigned to individual Cloudstack accounts and=
 on NSX side are completely isolated on the L3 level. Many use cases especi=
ally in corporate environment call for shared networking mode support. In s=
ome circumstances there also may be a need to translate shared NSX network =
over to a physical VLAN via L2 NSX gateway.
> Features that will be introduced to support Cloudstack shared networks in=
 two modes of NiciraNVP plugin:
> * Shared networks mapped to a physical VLAN with L2 NSX gateway
> * Shared networks within the same L3 NSX domain. Multiple L3 NSX domains =
will be supported.
> h3. Features
> h4. 1) Shared networking model support
> # Support native Cloudstack shared network in NiciraNVP plugin.
> # Current code that implements isolated networking mode support will stay=
 intact.
> # Designate network service offering by configuring VirtualNetworking pro=
vider with NiciraNVP.
> # Static/Source NAT is not used and ignored if defined in the network off=
ering.
> # Nicira_vvp_router_map table will support non-unique logical routers to =
implement L3 NSX routing domains where multiple Cloudstack networks are att=
ached to the same logical router.
> # Shared network with NSX based Virtual networking will go through the fo=
llowing states:
> ## Allocated
> ## Implementing
> ## Implemented
> ## Destroy
> h4. 2) Support NSX L2 gateways for L2 based VLANs mapped to a physical ne=
twork
> # Optional L2gatewayserviceuuid parameter for NiciraNVP controller
> # VLAN ID of a Shared network represents VLAN to pass through L2 gateway =
similar to native Cloudstack shared networking
> # NSX workflow for network allocation
> ## Check if l2gatewayservice defined
> ## Create record in networks table
> ### NiciraNvpGuestNetworkGuru as Guru_name
> ### Lswitch as broadcast_doamin
> ### Vlan://vlan_id as broadcast_uri
> ## Create record in VLAN table
> # NSX workflow for network implementation
> ## Check if l2gatewayservice defined and valid
> ## Create logical switch
> ## Map logical switch to L2gateway service assigning shared network VLAN =
ID
> # NSX workflow for NIC management and/or hypervisor support
> ## No changes from current implementation
> h4. 3) Support NSX L3 multiple routing domains
> # VLAN ID of a Shared network represents an UUID of a NSX virtual router =
of a particular routing domain. We will support UUID style notation for VLA=
N ID. l3gatewayservice option is not used in shared networking
> # It is assumed that if connectivity to the physical networking is requir=
ed then logical router is configured and connected to the physical network =
in advance. NiciraNVP plugin will not perform any task beyond basic connect=
ivity to the logical router
> # Support NSX L3 multiple routing domains
> # NSX workflow for network allocation
> ## Create record in networks table
> ### NiciraNvpGuestNetworkGuru as Guru_name
> ### Lswitch as broadcast_domain
> ### NULL as broadcast_uri
> ## Create record in VLAN table
> ## Create record in nicira_nvp_router_map table
> # NSX workflow for network implementation
> ## Check if logical router exists on NSX side which UUID matches the one =
defined during shared network creation. This mode is activated if VLAN ID s=
upplied in UUID style notation
> ## Create logical switch
> ## Attach logical switch to the logical router
> ## Assign shared network default gateway to the inside port of the logica=
l router
> # NSX workflow for NIC management and/or hypervisor support
> ## No changes from current implementation
> h4. 4) API Changes
> # Existing API addNiciraNvpDevices will be updated
> ## Adding 1 new optional parameter =E2=80=93 l2gatewayserviceuuid
> ## Adding 1 new response tag =E2=80=93 l2gatewayserviceuuid
> # Existing API listNiciraNvpDevices will be updated
> ## Adding 1 new response tag =E2=80=93 l2gatewayserviceuuid
> # Existing API listNics will be updated
> ## Adding 2 new optional response tag =E2=80=93 nsxlogicalswitch, nsxlogi=
calswitchport


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