Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 2 Mar 2017 08:13:45 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.13047269.1488364070000.40046.1488442425399@Atlassian.JIRA>
In-Reply-To: <JIRA.13047269.1488364070000@Atlassian.JIRA>
References: <JIRA.13047269.1488364070000@Atlassian.JIRA> <JIRA.13047269.1488364070738@jira-lw-us.apache.org>
Subject: [jira] [Commented] (CLOUDSTACK-9806) Nuage domain template
 selection per VPC
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Thu, 02 Mar 2017 08:14:00 -0000


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

ASF GitHub Bot commented on CLOUDSTACK-9806:
--------------------------------------------

Github user blueorangutan commented on the issue:

    https://github.com/apache/cloudstack/pull/1981
 =20
    @borisstoyanov a Jenkins job has been kicked to build packages. I'll ke=
ep you posted as I make progress.


> Nuage domain template selection per VPC
> ---------------------------------------
>
>                 Key: CLOUDSTACK-9806
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-980=
6
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>          Components: UI
>            Reporter: Sigert Goeminne
>            Assignee: Sigert Goeminne
>
> When deploying CloudStack with Nuage VSP (Virtualized Services Plugin/Pla=
tform), the Cloud/Network Administrator has the ability to define =E2=80=9C=
Domain Templates=E2=80=9D in the Nuage VSP Platform and reuse (and instanti=
ate) those when creating networks inside CloudStack. This allows for predef=
ining advanced networking topologies in the SDN platform, and integrate tho=
se seamlessly within the CloudStack workflows, without the need of porting =
all those SDN capabilities (e.g. GRT leaking, Advanced ACL=E2=80=99s, Servi=
ce Chaining, ...) into CloudStack.
> Today this mechanism works via global settings and allows for one Nuage V=
SP Domain Template to be specified per CloudStack Network type (Shared, Iso=
lated, VPC). This is fine for most deployments but it doesn=E2=80=99t leave=
 room for hybrid deployments in which different CloudStack networks need in=
dividually differentiated SDN capabilities. Especially for VPC=E2=80=99s it=
 would be nice to have finer grained domain template control.
> With the proposed new features, we add the ability to configure a domain =
template per VPC, i.e. each VPC created in CloudStack can be configured wit=
h a different domain template. We will make this option accessible through =
the UI also, but applicable to Nuage supporting zones only.
> [Design Document|https://cwiki.apache.org/confluence/display/CLOUDSTACK/N=
uage+domain+template+selection+per+VPC]


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)